Removing LUNs dynamically from an existing target ID

Article:HOWTO74817  |  Created: 2012-03-26  |  Updated: 2012-03-27  |  Article URL http://www.symantec.com/docs/HOWTO74817
Article Type
How To


Environment


Removing LUNs dynamically from an existing target ID

See Reconfiguring a LUN online that is under DMP control

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.

To remove LUNs dynamically from an existing 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. Identify which LUNs to remove from 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.

  3. 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 disk group, enter the following command to remove the LUNs from the disk group. 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
  4. For LUNs using AIX LVM over DMP devices, remove the device from the LVM volume group.

    # reducevg vgname pvname
  5. Using the AVID or LUN index, use Storage Array Management to unmap or unmask the LUNs you identified in step 2.

  6. Remove the LUNs from the vxdisk list. Enter the following command on all nodes in a cluster:

    # vxdisk rm da-name

    This is a required step. If you do not perform this step, the DMP device tree shows ghost paths.

  7. Clean up the AIX SCSI device tree for the devices that you removed in step 6.

    See Cleaning up the operating system device tree after removing LUNs

    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.

  8. Scan the operating system device tree.

    See Scanning an operating system device tree after adding or removing LUNs

  9. 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
  10. Refresh the DMP device name database using the following command:

    # vxddladm assign names
  11. Verify that the LUNs were removed cleanly by answering the following questions:

    • Is the device tree clean?

      After the LUN is removed cleanly, there should be no hdisk entries in the "Defined" state.

    • 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.


Legacy ID



uxrt-60_v27390292_v71682875


Article URL http://www.symantec.com/docs/HOWTO74817


Terms of use for this information are found in Legal Notices