HP

AutoPath

To remove hdisks corresponding to Hitachi Lightning and HP 

 # lsdev -CtHitachi* -Fname | xargs -n1 rmdev -dl

To remove all the dlm drives from the system 

 # dlmrmdev

To get the detailed information of all the LUNS 

 # xpinfo -l

 Scanning disk devices...

Device File : /dev/rhdisk17 Model : XP1024 

       Port : CL1E                                  Serial # : 00040318

Host Target : --- Code Rev : 2108 

  Array LUN : 00                                   Subsystem : 0004
    CU:LDev : 00:69                                 CT Group : ---
       Type : OPEN-V                               CA Volume : SMPL
       Size : ---                                 BC0 (MU#0) : SMPL
       ALPA : e1                                  BC1 (MU#1) : SMPL
    Loop Id : 04                                  BC2 (MU#2) : SMPL
    SCSI Id : 0x610813                            RAID Level : RAID5
     FC-LUN : 0000000000000000                    RAID Group : 2-9
   Port WWN : 50060e80039d7e04                      ACP Pair : 2
 Disk Mechs : R1408  R1508  R1608  R1708

Device File : /dev/rhdisk2 Model : XP1024 

       Port : CL2E                                  Serial # : 00040318

Host Target : --- Code Rev : 2108 

  Array LUN : 00                                   Subsystem : 0004
    CU:LDev : 00:69                                 CT Group : ---
       Type : OPEN-V                               CA Volume : SMPL
       Size : ---                                 BC0 (MU#0) : SMPL
       ALPA : c9                                  BC1 (MU#1) : SMPL
    Loop Id : 14                                  BC2 (MU#2) : SMPL
    SCSI Id : 0x620813                            RAID Level : RAID5
     FC-LUN : 0000000000000000                    RAID Group : 2-9
   Port WWN : 50060e80039d7e14                      ACP Pair : 2
 Disk Mechs : R1408  R1508  R1608  R1708

There are two ways to limit the DLM drivers managed by HDLM: 

 - Define the disks (hdisk) that you would like the DLM driver to recognize in the
 /usr/DynamicLinkManager/drv/dlmfdrv.conf file.
 - Define the disks that you would not like the DLM driver to recognize in the
 /usr/DynamicLinkManager/drv/dlmfdrv.unconf file.

A specification in the dlmfdrv.unconf file has priority over a specification in the dlmfdrv.conf file. Therefore, if the same disk is defined in both the dlmfdrv.conf and dlmfdrv.unconf files, the DLM driver will not recognize the defined disk

To start or stop the HDLM Manager 

 # startsrc -s DLMManager
 # stopsrc -s DLMManager

To list all the HDLM drivers 

 # lsdev -C | grep dlm
 dlmadrv Available DLM Alert Driver
 dlmfdrv Available DLM Driver
 dlmfdrv5 Available DLM Driver
  • dlmfdrv is the driver instance for internal management.
  • dlmfdrv5 (5 indicate the instance numbers of drivers)
  • dlmadrv is the file name of the DLM alert driver.

HDLM Commands operation 

 # dlnkmgr operation-name [parameter [parameter-value]]

To clears statistics such as the path error count 

 # dlnkmgr clear -pdst

To make an online path to offline 

 # dlnkmgr offline -pathid 1 -s
 KAPL01022-I 1 path(s) were processed. Operation name = offline
 KAPL01001-I The DLM command completed successfully. Operation name =
 offline

To set various options 

 # dlnkmgr set <parameters>

Parameters for the Set Command 

   -lb{on|off}  Enables or disables the load balancing function. Default = on.
   -ellv log-level  The level of error information you want to collect 
                   in the error log. Default = 3
   -afb{on[-intvl execution- interval]|off} on: Enables automatic failback
                  execution interval: in minutes. Can be set from 1 to 1440 minutes.

To display the path or drive details 

 # dlnkmgr view -path 
 # dlnkmgr view -drv

Problem: In AIX, hdisk devices are getting PVIDs instead of dlmfdrv drives.

Sol: Make sure the the hdisk names which are to be controlled by DLM are there in /usr/DynamicLinkManager/drv/dlmfdrv.conf file. If any of the hdisk names are missing, add it there.

XP Storage works XP series storage

HP XP 1024 - Creating Business copy 

 Creating LUSE Volume
  Login to Storage work command view GUI
  Click on LUN and VOL management
  Click on Vol Management ICON
  Expand LDEV
  Select the appropriate CU unit (ie. CU-8) (which has enough LDEV we required)
  select the starting LDEV and number of counts (for total size) and click set and apply
  The above step create the LUSE volume
 Assinging LUSE Volume PATH
   Click on LUN management ICON
   Expand the Fibre
   Expand the appropriate controller (ie. CL1-R)
   Select the appropriate system
   On the LDEV section select the CU (ie. CU-8)
   Select the LUSE name created in the LDEV section
   Go to LUN section and go to the last empty field and click on the "Add LU path"
   Copy the Path and paste in to other alternate path control unit (ie CL2-R)
   click on apply
   This process create the 2 paths to the created  LUN

  Creating Business copy
    Click on the BC tab
    Select the system LUN which you want to create the BC ( CL1-A -> systemname001 -> LUSE name ) 
    Right click on the LUSE and select create pair
    Select the port (CL1-R)
    Select the LUSE created from above process and click on set and apply