Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Dynamic Multi-Pathing Administrator's Guide - Solaris
Last Published:
2025-04-14
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: Solaris
- Understanding DMP
- How DMP works
- Disk device naming in DMP
- Setting up DMP to manage native devices
- Using Dynamic Multi-Pathing (DMP) devices with Oracle Automatic Storage Management (ASM)
- Administering DMP
- Managing DMP devices for the ZFS root pool
- Administering DMP using the vxdmpadm utility
- Gathering and displaying I/O statistics
- Specifying the I/O policy
- Administering disks
- Discovering and configuring newly added disk devices
- About discovering disks and dynamically adding disk arrays
- How to administer the Device Discovery Layer
- Changing the disk device naming scheme
- Dynamic Reconfiguration of devices
- About the DMPDR utility
- Reconfiguring a LUN online that is under DMP control using the Dynamic Reconfiguration tool
- Manually reconfiguring a LUN online that is under DMP control
- Event monitoring
- Performance monitoring and tuning
- Appendix A. DMP troubleshooting
- Appendix B. Reference
Updating the boot device settings
For the system to be bootable with the mirror disk, update the eeprom variable boot-device
with the paths of the mirrored DMP device.
The boot-device variable has a string limit. To add multiple physical path names without exceeding the string limit, use aliases for the physical paths.
To configure a mirror for the ZFS root pool using a DMP device.
- Display the subpaths of the DMP device.
# vxdmpadm getsubpaths dmpnodename=hitachi_vsp0_00f3
NAME STATE[A] PATH-TYPE[M] CTLR-NAME ENCLR-TYPE ENCLR-NAME ATTRS ======================================================================================== c3t50060E8006D43C20d3s2 ENABLED(A) - c3 Hitachi_VSP hitachi_vsp0 - c3t50060E8006D43C30d3s2 ENABLED(A) - c3 Hitachi_VSP hitachi_vsp0 - c4t50060E8006D43C20d3s2 ENABLED(A) - c4 Hitachi_VSP hitachi_vsp0 - c4t50060E8006D43C30d3s2 ENABLED(A) - c4 Hitachi_VSP hitachi_vsp0 -
- Obtain the physical path of each of the active enabled paths in step 1.
# readlink /dev/dsk/c3t50060E8006D43C20d3s0 ../../devices/pci@780/SUNW,qlc@0/fp@0,0/ssd@w5006016141e048ee,2:a
- Display the settings for the boot-device variable. The command shows the physical path for the existing boot device.
# eeprom boot-device boot-device=/pci@780/SUNW,qlc@0/fp@0,0/ssd@w5006016941e048ee,4:a
- To ensure that the eeprom boot-device settings are persistent, disable the ldmd services before changing the settings.
# svcs disable svc:/ldoms/ldmd:default
- Make sure that the attribute use-nvramrc? is set to true.
# eeprom use-nvramrc? use-nvramrc?=true
- Create aliases for the physical paths using the devalias command. The following command shows creation of aliases vxdmp1 and vxdmp2 for two paths of root disk:
# eeprom "nvramrc=devalias vxdmp1 /pci@780/SUNW,qlc@0/fp@0,0/disk@w5006016941e048ee,4:a \ vxdmp2 /pci@780/SUNW,qlc@0/fp@0,0/disk@w5006016141e048ee,2:a"
- Add the device alias for each physical path to the boot device, to enable booting from the path.
# eeprom "boot-device=vxdmp1 vxdmp2"
- Verify that the paths are added to the boot-device variable.
# eeprom boot-device boot-device=vxdmp1 vxdmp2
- Enable the ldmd services as follows:
# svcs enable svc:/ldoms/ldmd:default