README for ibmpfe.essutil.rte The following files are included in this LPP file: /usr/lpp/ibmpfe.essutil/README /usr/lib/methods/scsimap /usr/lib/methods/fcmap /usr/bin/lsess /usr/bin/ls2105 /usr/bin/lssdd /usr/bin/lsvp /usr/bin/get_ess_port /usr/bin/get_ess_vpd /usr/bin/get_ess_cudv To install you will need to do the following: Use smitty to install ibmpfe.essutil.rte fileset. For SCSI device support: Use smitty to install ibmpfe.essutil.scsi.data fileset. For FC device support: Use smitty to install ibmpfe.essutil.fibre.data fileset. You can install both SCSI and FC support, however to avoid the error message described later in the README you should only install support for devices you have (or intend to have) configured. Header definitions: Disk - hdisk name assigned by the host Location - physical location code of host adapter lun is accessed through LUN SN - unique serial number for each lun within the ESS Type - device and model Size - configured capacity of lun in giga bytes LSS - logical subsystem where lun resides Vol - volume number within the LSS Rank - unique identifier for each raid-array with the ESS C/A - cluster and adapter accessing the array S - shared by two or more ESS ports, Yes or No Connection - physical location code of ESS adapter lun is accessed through The following four programs can be run from the command line: lsess ls2105 lssdd lsvp Descriptions and Examples: lsess: This program displays data collected from the fcmap and scsimap program invoked by cfgmgr. fcmap and scsimap issue scsi commands directly to the disks (inquery, read capacity, and log sense) to collect the information displayed. To run lsess you will need to either re-boot the host or run cfgmgr with all 2105 vg's offline. This is only necessary for the initial run. Warning: Information displayed by lsess can become out of data if paths are configured directly (i.e. cfgmgr -l fcs0). If this occurs this data will not be refreshed until the host is rebooted or cfgmgr is run with all volume groups offline. # lsess Disk Location LUN SN Type Size LSS Vol Rank C/A S Connection ------ ------------ -------- ------------ ---- --- --- ---- --- - ----------- hdisk1 10-68-01[FC] 008FC106 IBM 2105-E20 2.0 10 8 1001 01 Y R1-B2-H4-ZA ls2105 and lssdd: These programs format data collected by AIX and stored in the ODM when the disks were configured to the host. The last four columns contain data collected from lsess (because it is not available from AIX). # ls2105 Hostname VG hdisk Location LUN SN S Connection Size LSS Vol Rank -------- -- ----- -------- ------ - ---------- ---- --- --- ---- hashark1 None hdisk1 10-68-01 008FC106 Y R1-B2-H4-ZA 2.0 10 8 1001 # lssdd Hostname VG vpath hdisk Location LUN SN S Connection Size LSS Vol Rank -------- -- ----- ----- -------- ------ - ---------- ---- --- --- ---- hashark1 sharkvg vpath0 hdisk1 10-68-01 008FC106 Y R1-B2-H4-ZA 2.0 10 8 1001 hashark1 sharkvg vpath0 hdisk9 10-68-01 008FC106 Y R1-B1-H4-ZA 2.0 10 8 1001 lsvp: This program shows vpath status from an ESS physical location code perspective. Included is the capability to set SDD paths offline using an ESS location code. Usage: lsvp [-adt] [-o] [-l location_code] -a Display SDD logical path to ESS physical location code -d Display path status for each vpath device -t Test physical access to hdisks, can only be used with -d option -o Attempts to set all SDD paths ONLINE -l Set SDD paths OFFLINE for specified ESS location code location_code must be in one of the following formats: single port = R1-Bx-Hy-Zz all ports on card = R1-Bx-Hy all ports on bay = R1-Bx # lsvp -d BAY-1(B1) BAY-2(B2) BAY-3(B3) BAY-4(B4) H1 H2 H3 H4 H1 H2 H3 H4 H1 H2 H3 H4 H1 H2 H3 H4 A B A B A B A B A B A B A B A B A B A B A B A B A B A B A B A B 0 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 1 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 2 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 3 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 4 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 5 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 6 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 7 - - - - - - Y - - - - - - - Y - - - - - - - Y - - - - - - - Y - 8 - - - - - - O - - - - - - - O - - - - - - - O - - - - - - - O - 9 - - - - - - O - - - - - - - O - - - - - - - O - - - - - - - O - 10 - - - - - - O - - - - - - - O - - - - - - - O - - - - - - - O - 11 - - - - - - O - - - - - - - O - - - - - - - O - - - - - - - O - Y = online/open O = online/closed N = offline X = not-available - = path not configured ? = path information not available PD = path down ls2105, lssdd, and lsvp do not require a re-boot or vg's to be offline for initial run, however they do require the ibm2105.rte package to be at 32.6.100.3 or above. If lsess has not been run the lssdd output will not contain LSS, Volume, and Rank information. If you are getting one of the following errors when running cfgmgr it is because your 2105 devices are either all native SCSI or all FC. Method error (/usr/lib/methods/scsimap >> /var/adm/essmap.out): 0514-023 The specified device does not exist in the customized device configuration database. Method error (/usr/lib/methods/fcmap >> /var/adm/essmap.out): 0514-023 The specified device does not exist in the customized device configuration database. If you do not intend to have a mix of 2105-SCSI and 2105-FC then you can eliminate the error message by removing the package you are not using. For all 2105-SCSI configurations: Use smitty to remove ibmpfe.essutil.fibre.data fileset. For all 2105-FC configurations: Use smitty to remove ibmpfe.essutil.scsi.data fileset.