Description

The boot sequence has changed for Solaris Local Zones related Service Management Facility (SMF) services in Solaris 11.4.

See related article:

Solaris 11.4 introduced changes to the boot sequence for Solaris Zone related services impacting Veritas vxodm startup
 

To ensure the Solaris Local Zones do not start before the required Veritas SMF services have all been started, Veritas recommends setting the "autoboot" zonecfg attribute to "false".
 

Steps:
 

1.] Run the zonecfg command against the Solaris Local Zone to be updated

Sample syntax

# zonecfg -z ldom06_zone15


At the zonecfg prompt, type the following syntax to disable autoboot (autostarting) of the Solaris Local Zone:

zonecfg:ldom06_zone15> set autoboot=false
 

2.] The autoboot attribute will not be displayed when set to "false" with the zonecfg "info" argument

zonecfg:ldom06_zone15> info
zonename: ldom06_zone15
zonepath: /export/zones/ldom06_zone15
brand: solaris
bootargs: -m verbose
fs-allowed: vxfs,odm
fs 0:
        dir: /etc/vx/licenses/lic
        special: /etc/vx/licenses/lic
        type: lofs
        options: []
net 0:
        physical: vnic15
anet 0:
        linkname: net0
        configure-allowed-address: true
smf-dependency 0:
        name: vxodm
        fmri: svc:/system/vxodm:default
device 0:
        match: /dev/llt
device 1:
        match: /dev/lmx
device 2:
        match: /dev/odm/*
device 3:
        match: /dev/vxportal
device 4:
        match: /dev/fdd
device 5:
        match: /dev/vx/rdsk/Zone15_Dg/Zone15_Dg_Vol
device 6:
        match: /dev/vx/dsk/Zone15_Dg/Zone15_Dg_Vol

3.] Verify & commit the zonecfg configuration changes and exit.

zonecfg:ldom06_zone15> verify
zonecfg:ldom06_zone15> commit
zonecfg:ldom06_zone15> exit
 

NOTE: The Solaris Local Zone will no longer start (boot) automatically when the server restarts.

The "zoneadm -z boot" syntax will still enable the user to start the Solaris Local Zone, however, requires manual intervention or automation via the Veritas Cluster Server (VCS) Zone Agent.

Figure 1.0

Veritas had to make a change to the SMF "/var/svc/manifest/system/vxodm/odm.xml" manifest file, ensuring Veritas vxodm (VERITAS Oracle Disk Manager) doesn't go into maintenance mode..
 

See related articles for more details:

How to change the Veritas vxodm Solaris 11.4 SMF service dependent links for SMF "svc:/system/zones:default" service

How to add a Solaris 11.4 SMF dependency within a Solaris Local Zone using zonecfg for Veritas vxodm service "svc:/system/vxodm:default"