Step 7 - Identify the Physical Device Name of the New LUN - Parallel Upgrade Tool (PUT)

Parallel Upgrade Tool (PUT) Reference

Product
Parallel Upgrade Tool (PUT)
Release Number
3.09
Published
February 2020
Language
English (United States)
Last Update
2020-02-24
dita:mapPath
ows1493317469465.ditamap
dita:ditavalPath
ows1493317469465.ditaval
dita:id
B035-5716
Product Category
Software
Teradata Tools and Utilities
When the new LUN has been created, you must determine the device name assigned to that LUN. This name will be used in subsequent recovery steps.
For 6250 and 6750 array models, teradata-multipath is used as the multi-pathing driver. For these arrays, /dev/tdmp is used as the device name to access the LUNs.
  1. Select the instructions, as required.
    Device Name Format Action
    /dev/sd
    1. To display device information for the arrays and controllers, use the mppUtil -S command.
    2. Locate the device line entry showing the disk array name for the disk array with the new LUN.
    3. Record the disk array name for the disk array with the new LUN.

      For example: H10C0T1 Active Active DAMC070-2

    4. Record the numbers in the device-id.

      For example, H10C0T1 provides: “10”, “0”, and “1.”

    5. To display device information for all SCSI devices, use the lsscsi command.

      The first column of the output lists the SCSI device ids of all the LUNS present on the node.

    6. Locate the SCSI-id matching the disk array and LUN number of the new LUN. The LUN number was the value recorded at the end of Step 5.

      For example, if the new LUN is LUN 18 then the entry is: .

      [10:0:1:18] disk LSI VirtualDisk 0623 /dev/sdaz

      The 10:0:1:18 is the combination of the disk array target id plus the LUN number.

    7. Record the /dev/sd entry for the device.

      For example, /dev/sdaz.

    /dev/tdmp
    1. Use the SMdevices command to determine the /dev/sd entries associated with the LUN that was created. The format is as follows: .

      SMdevices | grep "DAMC001-2-2, Volume 22,"

      Output:

       /dev/sdkm (/dev/sg164) [Storage Array DAMC001-2-2, Volume 22, LUN 22, Volume ID
      <60080e5000292e200000238e52712412>, Preferred Path (Controller-B): Owning controller - Active/Optimized]
      /dev/sdbs (/dev/sg4) [Storage Array DAMC001-2-2, Volume 22, LUN 22, Volume ID
      <60080e5000292e200000238e52712412>, Alternate Path (Controller-A): Non owning controller - Active/Non-optimized]
    2. Record the two /dev/sd device entries.

      In this example, /dev/sdkm and /dev/sdbs.

    3. To map /dev/sd device entries to the tdmp entry, use the tdmputil command, selecting one of the /dev/sd entries to use in the command:

      tdmputil -l | grep sdkm

      The output gives the tdmp device name associated with the sd entries.

      tdmpbo | sdbs 7:1 59973 0 1 .... ------- | sdkm 9:1 1027212 1 0 .... -------

      This show us that /dev/tdmpbo is the device associated with the new LUN.

    This step provides either the /dev/sd or /dev/tdmp device name associated with the new LUN. Use this information in steps 8 and 9.