Storage Foundation 5.0 MP3 Lun reconfiguration guidelines on AIX

book

Article ID: 100020588

calendar_today

Updated On:

Description

Error Message

LABEL:          VXVM_VXDMP
IDENTIFIER:     B258EF25
Date/Time:       Fri Apr 26 07:26:34 2005
Sequence Number: 527459
Machine Id:      00335D0B4C00
Node Id:         system-name
Class:           S
Type:            TEMP
Resource Name:   VxDRV:vxdmp

Description
Messages reported by vxdmp driver

Probable Causes
Attempt to disable last path to a device
Failure of Open or Close to a device
Path failure to one or more devices

User Causes
Disabling the last path to the controller
Trying to access the device which does not exist
Attempt to unload the vxdmp driver
        Recommended Actions
        Verify whether trying to disable the last access path to a device
        CHECK CABLES AND THEIR CONNECTIONS

Failure Causes
Bad Disk
Adapter Error
Cable or Disk Failure

        Recommended Actions
        Verify whether trying to disable the last access path to a device
        CHECK CABLES AND THEIR CONNECTIONS
        VERIFY DEVICE NAME IS VALID

Detail Data
DESCRIPTION
NOTE VxVM vxdmp V-5-0-34 added disk array 0581D, datype = GENESIS
 

Resolution

 

IMPORTANT !   Please run ‘vxdisk rm ’ prior to removing a LUN from a server. Please ensure you apply at least SF 5.0
 
Please capture the /etc/vx/diag.d/vxasldebug output prior to adding or removing any LUNs
1.)      Identity the LUNs to be removed from the host:
-          Use the Storage Array Management interface to identify the LUNs to be removed
# vxdisk –e –o alldgs list
# vxdisk –x LUN_SERIAL_NO –x CAB_SERIAL_NO –x UDID –p list      “New to 5.0MP3”
# lscfg –vl                         The ‘lscfg’ command should display the LUN Serial
 
2.)      Ensure the LUNs to be removed are not part of any diskgroup
# vxdg –g rmdisk
 
3.)      Close and remove the LUNs at the VxVM layer
# vxdisk rm
 
Note: This step is essential. If you do not perform this step, Volume Manager (VxVM) will leave the device in an open state, possibly resulting in duplicate/ghost paths reported by ‘vxdisk list’ or NONAME entries. 5.0 MP3 include the NEW Data Corruption Prevention feature
4.)      Close the related paths for the respective da-names for the removed LUNs
               # vxdmpadm getsubpaths dmpnodename=
            # vxdmpadm –f disable path=      Path being the OS native name, ie hdisk16
              
5.)  Mask the LUNs at the Storage Layer
               Using the appropriate Storage Array Management interface remove access for the required LUNs from
 
6.)  Clean up the AIX device tree
               # lsdev –Cc disk
            # rmdev –dl
            # cfgmgr -v
 
7.)  Update VxVM
               # vxdisk scandisks        As of 5.0 MP3, both the DMP and VXVM incore
 
8.)  Refresh the /etc/vx/disk.info file ( if the persistence option with vxddladm has been enabled )
               # vxddladm assign names         NEW to 5.0
     Questions: Is the device tree clean? Is the ‘vxdisk list’ output correct? Is the ‘vxdisk path’ output correct? Were all the
 
SYMANTEC SF 5.0MP3 AIX LUN RECONFIGURATION GUIDELINES
- Prior to the provisioning of NEW luns, please ensure the AIX device tree is clean, the ‘vxdisk list’ command looks
correct and the /etc/vx/disk.info file has been refreshed (if it exists)
- Please capture the /etc/vx/diag.d/vxasldebug output prior to adding or removing any LUNs
- 5.0 MP3 introduces the ‘vxdisk –x –p list’ enhanced command syntax to customize the standard ‘vxdisk list’ output. 5.0 MP3 also introduces the NEW ‘vxlist’ command to enable the System Administrators to work more closely with the Storage Administrators.
- To perform online LUN addition:
1.) Refresh the /etc/vx/disk.info file ( if the persistence option with vxddladm has been enabled )
        # vxdisk –x LUN_SERIAL_NO –x CAB_SERIAL_NO –x UDID –p list      NEW to 5.0 MP3
      # grep –i 0xffffffff /etc/vx/disk.info         If entries are reported, then the disk.info has not been updated
      # vxddladm assign names                                 NEW to 5.0 MP3
2.) Clean up the AIX device tree and VxVM
      # lsdev –Cc disk
      # cfgmgr –v
      # vxdisk scandisks
3.) Identity the LUNs to be presented to the host:
      # vxdisk –e –o alldgs list           Capture what VxVM is able to see prior to presenting the NEW
      Use the Storage Array Management interface to identify the LUNs to be presented
Symantec recommend you use the EBN_AVID ( Array Volume ID ) naming scheme where possible. The AVID will be useful for
4.) Device Discovery:
        # cfgmgr –v
      # vxdisk scandisks                   Update VxVM, scan for new devices
5.) Confirm the NEW LUNs are visible to the host:
      # lsdev –Cc disk
      # vxdisk –e –o alldgs list                       Capture what VxVM is able to see prior to presenting the NEW
6.) Capture the special 5.0 MP3 related output ‘vxlist path’ and ‘vxdisk –x ….’
        # vxlist path                  NEW to 5.0 MP3
      # vxdisk –x LUN_SERIAL_NO –x CAB_SERIAL_NO –x UDID –p list                  NEW to 5.0 MP3
 
Note: Please record the date and time of when the new LUNs were provisioned, along with their corresponding serial numbers .
 

Applies To

AIX 5.3 running 5.0MP3

Issue/Introduction

Storage Foundation 5.0 MP3 Lun reconfiguration guidelines on AIX Best Practice Guidelines:
System administrators and storage administrators may need to modify the set of LUNs provisioned to a server. By following the guidelines shown, you should be able to dynamically change the LUN assignments without performing a reconfiguration reboot