Hp Ux Ioscan



Hi I had to reboot my rx6660 (HP-UX 11.31) to see 4 new SAN LUNs. The 'ioscan -fnC disk' did not work. I always told proudly that 'HP-UX reboot is not required to configure new SAN LUNs' but it seems that has changed. Perhaps the 'rescan' must be done by 'scsimgr' command? Global Cell Number Format. The global cell number format is identical to the cells' HP-UX hardware path, as reported by the HP-UX ioscan command. In global format, each cell is given a single unique number that indicates the relative location of the cell in the entire server complex.

  1. Hp-ux Ioscan
  2. Scan For New Disk
  3. Linux Scan For New Disk
  4. Linux Disk Scan

Use the cell and I/O chassis notation described in thissection when you manage, configure, and inquire about cells and I/O chassisusing the nPartition configuration commands.

Details are in the “Cell Specification Formats” and “I/O Specification Format” sections that follow.

Use either of the following two formats to specify cellswhen using the nPartition configuration commands: “Global Cell Number Format” or “Cell Hardware Location Format”.

  • Global Cell Number Format. The global cell number format is identical to the cells' HP-UXhardware path, as reported by the HP-UX ioscan command.In global format, each cell is given a single unique number that indicatesthe relative location of the cell in the entire server complex.

    Table A-1 Cell IDs in Global Cell Number Format

    Cell Slot01234567

    Global Formatfor rp7405/rp7410, rp7420, rp7440, rx7620, and rx7640

    01

    Global Formatfor rp8400, rp8420, rp8440, rx8620, and rx8640

    0123
    Superdome Cabinet0 Global Format01234567

    Superdome Cabinet1 Global Format

    89101112131415
  • Cell Hardware Location Format. In cell hardware location format, each cell is identified using twonumbers that specify the cabinet and the cell slot with the cabinet wherethe cell resides: cabinet/slot.

    Table A-2 Cell IDs in Hardware Location Format

    Cell Slot01234567

    Hardware LocationFormat for rp7405/rp7410, rp7420, rp7440, rx7620, and rx7640

    0/00/1

    Hardware LocationFormat for rp8400, rp8420, rp8440, rx8620, and rx8640

    0/00/10/20/3

    Superdome Cabinet0 Hardware Location Format

    0/00/10/20/30/40/50/60/7

    Superdome Cabinet1 Hardware Location Format

    1/01/11/21/31/41/51/61/7

Both cell ID formats specify the location of a cell ina complex. For example, parstatus -c9 and parstatus-c1/1 specify the same cell.

# parstatus -c9[Cell] CPU Memory Use OK/ (GB) Core On Hardware Actual Deconf/ OK/ Cell Next ParLocation Usage Max Deconf Connected To Capable Boot Num cab1,cell1 active base 4/0/4 8.2/ 0.0 - no yes 1# parstatus -c1/1[Cell] CPU Memory Use OK/ (GB) Core On Hardware Actual Deconf/ OK/ Cell Next ParLocation Usage Max Deconf Connected To Capable Boot Num cab1,cell1 active base 4/0/4 8.2/ 0.0 - no yes 1#

Use the following I/O hardware location format when specifyingan I/O chassis to the nPartition configuration commands:

Hp-ux Ioscan

cabinet/bay/chassis

Drive

The cabinet, bay,and chassis fields specify the physical location ofthe I/O chassis. The values of these fields are as follows.

  • cabinet

    specifies the cabinet number where the I/O chassis resides.

    On HP rp7405/rp7410, rp7420, rp7440, rx7620, rx7640, rp8400,rp8420, rp8440, rx8620, and rx8640 servers, the server cabinet number alwaysis 0.

    In HP rp8400, rp8420, rp8440, rx8620, and rx8640 complexesthe I/O Expansion cabinet, if present, is 8.

    On HP Superdome servers, the cabinet number can be:

    • 1 — the rightCompute cabinet, if present.

    • 9 — an I/O Expansioncabinet, if present.

  • bay

    specifies the I/O bay (within a cabinet) where the I/Ochassis resides.

    On HP rp7405/rp7410, rp7420, rp7440, rx7620, rx7640, rp8400,rp8420, rp8440, rx8620, and rx8640 servers, the bay number always is 0.

    On HP Superdome servers, the bay number can be:

    • 0 — the frontbay of a Compute cabinet, or the bottom bay of an I/O Expansion cabinet.

    • 1 — the rearbay of a Compute cabinet, or the middle bay of an I/O Expansion cabinet.

  • chassis

    specifies the I/O chassis (within a bay).

    On HP rp7405/rp7410, rp7420, rx7620, rp8400, rp8420, andrx8620 servers, the chassis number is:

    • 0 — Chassis 0,which connects to cell 0 and is the left chassis as viewed from the cabinetrear: the left eight PCI card slots.

    • 1 — Chassis 1,which connects to cell 1 and is the right chassis as viewed from the cabinetrear: the right eight PCI card slots.

    On HP Superdome servers, the chassis number is:

    • 1 — Chassis 1,the left chassis in the bay, as viewed when facing the bay/chassis.

    • 3 — Chassis 3,the right chassis in the bay, as viewed when facing the bay/chassis.

    In HP Superdome servers all chassis are 12-slot I/O chassis,both in Compute cabinets and in I/O Expansion cabinets.

The example below shows the parstatus commandlisting details about two different I/O chassis (cabinet 0/bay 0/chassis 1,and cabinet 0/bay 1/chassis 3).

# parstatus -i0/0/1[Chassis] Core Connected ParHardware Location Usage IO To Num cab0,bay0,chassis1 absent - - -# parstatus -i0/1/3[Chassis] Core Connected ParHardware Location Usage IO To Num cab0,bay1,chassis3 active yes cab0,cell0 0#

Use the parstatus -I command to listall I/O chassis within a server complex, regardless of the chassis cell connectionsand nPartition assignments.

Use the HP-UX rad -q command or olrad-q command to list the currently available PCI I/O slots in thelocal nPartition and their status. The rad command is availablewith HP-UX B.11.11, and olrad is available with HP-UX B.11.23and HP-UX B.11.31.

In Example A-1, boththe parstatus and rad commands showdetails for various chassis and slots, including chassis 0/1/3.

Scan For New Disk

Example A-1 I/O Specification Formats for Cabinets, Bays, and Chassis

Linux Scan For New Disk

# parstatus -I1[Chassis] Core Connected ParHardware Location Usage IO To Num cab0,bay0,chassis0 absent - - -cab0,bay0,chassis1 absent - - -cab0,bay0,chassis2 absent - - -cab0,bay0,chassis3 inactive yes cab0,cell4 -cab0,bay1,chassis0 absent - - -cab0,bay1,chassis1 absent - - -cab0,bay1,chassis2 absent - - -cab0,bay1,chassis3 active yes cab0,cell0 0cab1,bay0,chassis0 absent - - -cab1,bay0,chassis1 inactive - - -cab1,bay0,chassis2 absent - - -cab1,bay0,chassis3 absent - - -cab1,bay1,chassis0 absent - - -cab1,bay1,chassis1 absent - - -cab1,bay1,chassis2 absent - - -cab1,bay1,chassis3 active yes cab1,cell2 1cab8,bay0,chassis1 inactive - - -cab8,bay0,chassis3 active yes cab0,cell2 0cab8,bay1,chassis1 inactive yes cab1,cell0 -cab8,bay1,chassis3 inactive - - -cab8,bay2,chassis1 absent - - -cab8,bay2,chassis3 absent - - -cab8,bay3,chassis1 absent - - -cab8,bay3,chassis3 absent - - -# rad -q2 Driver(s)Slot Path Bus Speed Power Occupied Suspended Capable0-1-3-0 0/0/0 0 33 On Yes No No0-1-3-1 0/0/1/0 8 33 On No N/A N/A0-1-3-2 0/0/2/0 16 33 On No N/A N/A0-1-3-3 0/0/3/0 24 33 On No N/A N/A0-1-3-4 0/0/4/0 32 33 On No N/A N/A0-1-3-5 0/0/6/0 48 33 On Yes No Yes0-1-3-6 0/0/14/0 112 33 On No N/A N/A0-1-3-7 0/0/12/0 96 33 On No N/A N/A0-1-3-8 0/0/11/0 88 33 On Yes No Yes0-1-3-9 0/0/10/0 80 33 On No N/A N/A0-1-3-10 0/0/9/0 72 33 On No N/A N/A0-1-3-11 0/0/8/0 64 33 On No N/A N/A8-0-3-0 2/0/0 0 33 On Yes No No8-0-3-1 2/0/1/0 8 33 On No N/A N/A8-0-3-2 2/0/2/0 16 33 On No N/A N/A8-0-3-3 2/0/3/0 24 33 On No N/A N/A8-0-3-4 2/0/4/0 32 33 On No N/A N/A8-0-3-5 2/0/6/0 48 33 On No N/A N/A8-0-3-6 2/0/14/0 112 33 On Yes No Yes8-0-3-7 2/0/12/0 96 33 On No N/A N/A8-0-3-8 2/0/11/0 88 33 On No N/A N/A8-0-3-9 2/0/10/0 80 33 On No N/A N/A8-0-3-10 2/0/9/0 72 33 On No N/A N/A8-0-3-11 2/0/8/0 64 33 On No N/A N/A#

Linux Disk Scan

The parstatus -I command reports cabinet0, bay 1, chassis 3 as cab0,bay1,chassis3.

The rad -q command and olrad-q command report cabinet 0, bay 1, chassis 3 as 0-1-3.