LDOM: Solaris 11 SRU 11.3.33.5 preventing user adding new Virtual Disk Backend (vdsdev) using a DMP device

book

Article ID: 100045106

calendar_today

Updated On:

Description

Error Message

 

# vxdisksetup -i emc_clariion0_631

# vxdg init datadg emc_clariion0_631

# vxdg deport datadg

# ldm add-vdsdev /dev/vx/dmp/emc_clariion0_631s2 scrappy631@primary-vds0
Path /dev/vx/dmp/emc_clariion0_631s2 is only read accessible on service domain primary

 

Cause

 

* 3969967 (Tracking ID: 3844883)

SYMPTOM:

adding Dynamic Multi-Pathing(DMP) controlled device to guest domain might fail with below error: Path /dev/vx/rdmp/** is only read accessible on service domain primary

DESCRIPTION:

There is a compatibility issue between Veritas Volume Manager(VxVM) 6.x and Solaris 11.3 and above. the APIs was private and not suitable for LDI framework, which caused the issue.

RESOLUTION:

More code changes are done to compatible with LDI framework.

 

 

Resolution

 

Veritas engineering have created Private Hot-fix for Solaris 11. Please contact Veritas technical support to obtain the private hot-fix


Volume Manager 6.2.1 Hot Fix 802
 

The Private hot-fix needs to be installed in the I/O domains and eventually the LDOM GUESTs (less critical).
 
The fix will allow the Virtual Disk Backend (vdsdev) to be presented using Veritas DMP.
 
The fix needs to be applied to the control (Primary) & service (if configured) domain(s).
 
If you also have a service I/O domain, presenting the same physical device paths up into the GUEST LDOM domains, no downtime should be encountered for the GUEST domains.
 
Please ensure the vdc.conf has been correctly populated with the virtual disk IDs within the LDOM GUEST domains, so DMP works correctly.
 
 
LDOM: Oracle VM Server for SPARC - Solaris 11.3 SRU 18.0.6 provides a design change to handle the loss of Primary (Control) and Service I/O Domains when using Veritas DMP
 
https://www.veritas.com/support/en_US/article.100033972

 
 
STEPS
 
If the Service Domain (SDOM) does not exist, please ensure the GUEST LDOMs are stopped cleanly.
 
 
1.] Apply VxVM private hot-fix to the CDOM and reboot

2.] Apply VxVM private hot-fix to the SDOM and reboot
 
3.] Long-term patch the LDOM guests
 
 
Please remember that Solaris MPGROUPs are not supported with Solaris 11 LDOM GUESTs.

Veritas DMP must be used when presenting the vdsdev backend devices from the Control (Primary) & Service (Alternate) I/O domains.


Once the hotfix has been applied and the system has been rebooted, the ldm add-vdsdev command will now work.


To illustrate the fix works:
 

# ldm add-vdsdev /dev/vx/dmp/emc_clariion0_631s2  scrappy631@primary-vds0

# vxdg import datadg
# vxdg deport datadg

# ldm rm-vdsdev scrappy631@primary-vds0

# ldm add-vdsdev /dev/vx/dmp/emc_clariion0_631s2  scrappy631@primary-vds0

# vxdg import datadg

# ldm rm-vdsdev scrappy631@primary-vds0

# ldm add-vdsdev /dev/vx/dmp/emc_clariion0_631s2  scrappy631@primary-vds0


 

Issue/Introduction


After upgrading Solaris to SRU 11.3.33.5 in the Primary control domain (LDOM), the user can no longer add new vdsdevs (Virtual Disk Backend) using a DMP backend device.
The Backend can be:
- A physical disk/LUN
- A slice of a physical disk/LUN
- A file
- A volume (vxvm/SVM/ZFS)
- A pseudo device


LDOMs known as Oracle VM Server for Sparc

Oracle's server virtualization and partitioning technology for SPARC. Provides the ability to split a single physical system into multiple, independent virtual systems (known as logical domains).

Figure 1.0

User-added image Enables a system to run and deploy different Operating System instances simultaneously on a single server