Adding new LUNs dynamically to a new target ID

In this case, a new group of LUNs is mapped to the host via multiple HBA ports. An operating system device scan is issued for the LUNs to be recognized and added to DMP control.

The high-level procedure and the SFCFSHA commands are generic. However, the operating system commands may vary depending on the Solaris version. For example, the following procedure uses Solaris 10 with the Leadville stack.

To add new LUNs dynamically to a new target ID

  1. Prior to 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 to on.

    # vxdmpadm settune dmp_cache_open=on
  2. If DMP co-exists with EMC PowerPath, make sure the dmp_monitor_osevent parameter is set to off. The vxesd daemon will not monitor operating system events.

    If you install DMP on a system that already has PowerPath installed, DMP sets the dmp_monitor_osevent to off by default.

    # vxdmpadm gettune dmp_monitor_osevent

    If required, turn off the dmp_monitor_osevent parameter explicitly:

    # vxdmpadm settune dmp_monitor_osevent=off
  3. Identify which LUNs to add to the host. Do one of the following:
    • Use 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.

  4. Map/mask the LUNs to the new target IDs on multiple hosts.
  5. Scan the operating system device.

    Repeat step 3 and step 4 until you see that all the LUNs have been added.

  6. Use SFCFSHA 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
  7. Refresh the DMP device name database using the following command:
    # vxddladm assign names
  8. Verify that the LUNs were added correctly by answering the following questions:
    • Do the newly provisioned LUNs appear in the vxdisk list output?

    • Are the configured paths present for each LUN?

    If the answer to any of these questions is "No," return to step 3 and begin the procedure again.

    If the answer to all of the questions is "Yes," the LUNs have been successfully added. You can now add the LUNs to a disk group, create new volumes, or grow existing volumes.

    If the dmp_native_support tunable is set to ON and the new LUN does not have a VxVM label or is not claimed by a TPD driver then the LUN is available for use by LVM.

More Information

Scanning an operating system device tree after adding or removing LUNs