InfoScale™ 9.0 Dynamic Multi-Pathing Administrator's Guide - Solaris
- Understanding DMP
- About Dynamic Multi-Pathing (DMP)
- How DMP works
- Multi-controller ALUA support
- Multiple paths to disk arrays
- Device discovery
- Disk devices
- Disk device naming in DMP
- Setting up DMP to manage native devices
- About setting up DMP to manage native devices
- Displaying the native multi-pathing configuration
- Migrating ZFS pools to DMP
- Migrating to DMP from EMC PowerPath
- Migrating to DMP from Hitachi Data Link Manager (HDLM)
- Migrating to DMP from Solaris Multiplexed I/O (MPxIO)
- Using Dynamic Multi-Pathing (DMP) devices with Oracle Automatic Storage Management (ASM)
- Enabling Dynamic Multi-Pathing (DMP) devices for use with Oracle Automatic Storage Management (ASM)
- Removing Dynamic Multi-Pathing (DMP) devices from the listing of Oracle Automatic Storage Management (ASM) disks
- Migrating Oracle Automatic Storage Management (ASM) disk groups on operating system devices to Dynamic Multi-Pathing (DMP) devices
- Enabling and disabling DMP support for the ZFS root pool
- Adding DMP devices to an existing ZFS pool or creating a new ZFS pool
- Removing DMP support for native devices
- Administering DMP
- About enabling and disabling I/O for controllers and storage processors
- About displaying DMP database information
- Displaying the paths to a disk
- Setting customized names for DMP nodes
- Managing DMP devices for the ZFS root pool
- Administering DMP using the vxdmpadm utility
- Retrieving information about a DMP node
- Displaying consolidated information about the DMP nodes
- Displaying the members of a LUN group
- Displaying paths controlled by a DMP node, controller, enclosure, or array port
- Displaying information about controllers
- Displaying information about enclosures
- Displaying information about array ports
- User-friendly CLI outputs for ALUA arrays
- Displaying information about devices controlled by third-party drivers
- Displaying extended device attributes
- Suppressing or including devices from VxVM control
- Gathering and displaying I/O statistics
- Setting the attributes of the paths to an enclosure
- Displaying the redundancy level of a device or enclosure
- Specifying the minimum number of active paths
- Displaying the I/O policy
- Specifying the I/O policy
- Disabling I/O for paths, controllers, array ports, or DMP nodes
- Enabling I/O for paths, controllers, array ports, or DMP nodes
- Renaming an enclosure
- Configuring the response to I/O failures
- Configuring the I/O throttling mechanism
- Configuring Subpaths Failover Groups (SFG)
- Configuring Low Impact Path Probing (LIPP)
- Displaying recovery option values
- Configuring DMP path restoration policies
- Stopping the DMP path restoration thread
- Displaying the status of the DMP path restoration thread
- Configuring Array Policy Modules
- Configuring latency threshold tunable for metro/geo array
- Administering disks
- About disk management
- Discovering and configuring newly added disk devices
- Partial device discovery
- About discovering disks and dynamically adding disk arrays
- About third-party driver coexistence
- How to administer the Device Discovery Layer
- Listing all the devices including iSCSI
- Listing all the Host Bus Adapters including iSCSI
- Listing the ports configured on a Host Bus Adapter
- Listing the targets configured from a Host Bus Adapter or a port
- Listing the devices configured from a Host Bus Adapter and target
- Getting or setting the iSCSI operational parameters
- Listing all supported disk arrays
- Excluding support for a disk array library
- Re-including support for an excluded disk array library
- Listing excluded disk arrays
- Listing disks claimed in the DISKS category
- Displaying details about an Array Support Library
- Adding unsupported disk arrays to the DISKS category
- Removing disks from the DISKS category
- Foreign devices
- VxVM coexistence with ZFS
- Changing the disk device naming scheme
- Discovering the association between enclosure-based disk names and OS-based disk names
- Dynamic Reconfiguration of devices
- About online Dynamic Reconfiguration
- 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
- Overview of manually reconfiguring a LUN
- Manually removing LUNs dynamically from an existing target ID
- Manually adding new LUNs dynamically to a new target ID
- About detecting target ID reuse if the operating system device tree is not cleaned up
- Scanning an operating system device tree after adding or removing LUNs
- Manually cleaning up the operating system device tree after removing LUNs
- Manually replacing a host bus adapter on an M5000 server
- Changing the characteristics of a LUN from the array side
- Upgrading the array controller firmware online
- Event monitoring
- About the Dynamic Multi-Pathing (DMP) event source daemon (vxesd)
- Fabric Monitoring and proactive error detection
- Dynamic Multi-Pathing (DMP) automated device discovery
- Dynamic Multi-Pathing (DMP) discovery of iSCSI and SAN Fibre Channel topology
- DMP event logging
- Starting and stopping the Dynamic Multi-Pathing (DMP) event source daemon
- Performance monitoring and tuning
- About tuning Dynamic Multi-Pathing (DMP) with templates
- DMP tuning templates
- Example DMP tuning template
- Tuning a DMP host with a configuration attribute template
- Managing the DMP configuration files
- Resetting the DMP tunable parameters and attributes to the default values
- DMP tunable parameters and attributes that are supported for templates
- DMP tunable parameters
- Appendix A. DMP troubleshooting
- Appendix B. Reference
Manually removing LUNs dynamically from an existing target ID
In this case, a group of LUNs is unmapped from the host HBA ports and an operating system device scan is issued. To add subsequent LUNs seamlessly, perform additional steps to clean up the operating system device tree.
The high-level procedure and the DMP commands are generic. However, the operating system commands may vary depending on the Solaris version. For example, the following procedure uses Solaris 11 with the Leadville stack.
To remove LUNs dynamically from an existing target ID
- Before any dynamic reconfiguration, ensure that the dmp_cache_open tunable is set to
on. This setting is the default.# vxdmpadm gettune dmp_cache_open
If the tunable is set to
off, set the dmp_cache_open tunable toon.# vxdmpadm settune dmp_cache_open=on
- Identify which LUNs to remove from the host. Do one of the following:
Use the Storage Array Management to identify the Array Volume ID (AVID) for the LUNs.
If the array does not report the AVID, use the LUN index.
- For LUNs under VxVM, perform the following steps:
Evacuate the data from the LUNs using the vxevac command.
See the vxevac(1M) online manual page.
After the data has been evacuated, enter the following command to remove the LUNs from the disk group:
# vxdg -g diskgroup rmdisk da-name
If the data has not been evacuated and the LUN is part of a subdisk or a disk group, remove the LUNs from the disk group using the following command. If the disk is part of a shared disk group, you must use the -k option to force the removal.
# vxdg -g diskgroup -k rmdisk da-name
- For LUNs that are in use by ZFS, either export or destroy the zpool.
- Using the AVID or the LUN index, use the Storage Array Management to unmap or unmask the LUNs you identified in step 2.
- Remove the LUNs from the vxdisk list. Enter the following command on all nodes in a cluster:
# vxdisk rm da-name
This step is required. If you do not perform this step, the DMP device tree shows ghost paths.
- Clean up the Solaris SCSI device tree for the devices that you removed in step 6.
This step is required. You must clean up the operating system SCSI device tree to release the SCSI target ID for reuse if a new LUN is added to the host later.
- Scan the operating system device tree.
- Use DMP to perform a device scan. You must perform this operation on all nodes in a cluster. Enter one of the following commands:
# vxdctl enable
# vxdisk scandisks
- Refresh the DMP device name database using the following command:
# vxddladm assign names
- Verify that the LUNs were removed cleanly by answering the following questions:
Is the device tree clean?
Verify that the operating system metanodes are removed from the /dev directory.
Were all the appropriate LUNs removed?
Use the DMP disk reporting tools such as the vxdisk list command output to determine if the LUNs have been cleaned up successfully.
Is the vxdisk list output correct?
Verify that the vxdisk list output shows the correct number of paths and does not include any ghost disks.
If the answer to any of these questions is "No," return to step 5 and perform the required steps.
If the answer to all of the questions is "Yes," the LUN remove operation is successful.