Console snippets
NOTICE: VxVM vxdmp V-5-0-1990 driver version VxVM 7.4.1.2901 Multipathing Driver installed
NOTICE: VxVM vxio V-5-0-1990 driver version VxVM 7.4.1.2901 I/O driver installed
NOTICE: VxVM vxspec V-5-0-1990 driver version VxVM 7.4.1.2901 control/status driver installed
Sep 9 13:44:57 svc.startd[14]: svc:/system/dump:config: Method "/lib/svc/method/svc-dump-config" failed with exit status 96.
Sep 9 13:44:57 svc.startd[14]: system/dump:config misconfigured: transitioned to maintenance (see 'svcs -xv' for details)
VxVM sysboot INFO V-5-2-3409 starting in boot mode...
Sep 9 13:45:12 svc.startd[14]: svc:/system/swap:default: Method "/usr/sbin/swapadd" failed with exit status 2.
Sep 9 13:45:12 svc.startd[14]: svc:/system/swap:default: Method "/usr/sbin/swapadd" failed with exit status 2.
Sep 9 13:45:13 svc.startd[14]: svc:/system/swap:default: Method "/usr/sbin/swapadd" failed with exit status 2.
Sep 9 13:45:13 svc.startd[14]: system/swap:default failed: transitioned to maintenance (see 'svcs -xv' for details)
This is when Veritas DMP is discovering the enclosure:
Enter user name for system maintenance (control-d to bypass): root
NOTICE: VxVM vxdmp V-5-0-34 [Info] added disk array 0204204072ca, datype = StorwizeV7000
NOTE: The swap and dump devices are on SAN attached storage and managed as dmp_native_support pseudo devices, as these are ZFS zpools.
# vxdmpadm gettune dmp_native_support
This tunable is turned on
# vxdmpadm native ls
The above command will list the uninitialized VxVM disks and ZFS disks.
Solaris Release Differences:
On Solaris 11.3, the swap and dump device config are done via the dumpadm:default SMF service.
This is executed after vxvm-startup2, so everything works fine.
On Solaris 11.4, the dump/swap config has been redesigned and split into a few SMF services including swap:default and dump:config, which are executed before the Veritas dmp devices are created (vxvm-startup2).
This will cause an issue, if the Veritas dmp managed devices are used for swap or dump.
The order of execution among the SMF services is not committed.
3rd party software should not assume, that they will work the same across OS versions.
Recommendation from Oracle:
SMF dependency rules should be created, if a particular order is required.
Veritas could create a customized SMF profile at the site-profile layer, that includes a "require_all" dependency on the services that create the dmp devices (e.g. vxvm-sysboot, vxvm-startup2) and place it in /etc/svc/profile/site directory indicating that the swap service depends on it.
If VxDMP Multipathing is supported for DMP devices, then a similar SMF profile needs to be created for dump:config.
Sample xml profile for swap:
name='system/swap'
type='service'
version='1'>
name='vxvm-startup2'
grouping='require_all'
restart_on='none'
type='service'>
----------------------------
Veritas engineering is reviewing the Oracle recommendations to see what could be implemented to handle the Solaris 11.4 boot services changes