You are here

Create Genesis partition and Configure Npartitions in a SD3200

Here, we go over the procedure of configuring a SD3200 from the beginning, we create a genesis partition, configure Partition 0, upgrade the firmware on the cells, and finally create the rest of Npars

First we need to have all our partitions ready for reconfiguration spinning on BIB.

We can do a shutdown with reconfig from the OS with:

#shutdown -RH now

Or wi can shutdown the OS normally and the do a RR from the gsp cm> .

We need to check the status of our partitions:

GSP> vfp

Partition VFP's available:

# Name
--- ----
0) sheepbox
1) drogship
3) diehard
4) suarezbox
5) tripper
S) System (all chassis codes)
Q) Quit

GSP:VFP> s

E indicates error since last boot
# Partition state Activity
- --------------- --------
0 Cell(s) Booting: 1495 Logs
1 Cell(s) Booting: 894 Logs
3 Cell(s) Booting: 1218 Logs
4 Cell(s) Booting: 1491 Logs
5 Cell(s) Booting: 783 Logs

GSP:VFP (^B to Quit) >

They have to be in the cells booting state, if we select a partition it has to be blocked at boot (BIB):

GSP> vfp

Partition VFP's available:

# Name
--- ----
0) sheepbox
Partition VFP's available:

# Name
--- ----
0) sheepbox
1) drogship
3) diehard
4) suarezbox
5) tripper
S) System (all chassis codes)
Q) Quit

GSP:VFP> 0

E indicates error since last boot
Partition 0 state Activity
------------------ --------
Cell(s) Booting: 1495 Logs

# Cell state Activity
- ---------- --------
0 Boot Is Blocked (BIB) Cell firmware 872 Logs
2 Boot Is Blocked (BIB) Cell firmware 620 Logs

GSP:VFP (^B to Quit) >

Once we check all the cells are in the BIB state, we can start creating the genesis partition,we are going to use cell 0/4

GSP> cm

Enter HE to get a list of available commands

GSP:CM> cc

This command allows you to change the complex profile.

WARNING: You must either shut down the OSs for reconfiguration or
execute the RR (reset for reconfiguration) command for all
partitions before executing this command.

G - Build genesis complex profile
L - Restore last complex profile
Select profile to build or restore: G

Building a genesis complex profile will create a complex profile
consisting of one partition with a single cell.

Choose the cell to use.

Enter cabinet number: 0
Enter slot number: 4

Do you want to modify the complex profile? (Y/[N]) y

-> The complex profile will be modified.
GSP:CM> cp

--------------------------------------------------------------------------------
Cabinet | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7
--------+--------+--------+--------+--------+--------+--------+--------+--------
Slot |01234567|01234567|01234567|01234567|01234567|01234567|01234567|01234567
--------+--------+--------+--------+--------+--------+--------+--------+--------
Part 0 |....X...|........|........|........|........|........|........|........

GSP:CM>

As you can see, we only have one partition with one cell as its only member. This cell is in the Boot-Is-Blocked (BIB) state. Essentially, when the cell(s) in a partition are in the BIB state, they are waiting for someone to give them a little nudge in order to start booting the operating system. There are reasons why a cell will remain in the BIB state; we talk about that later. To boot the partition, we use the GSP BO command:

GSP:CM> bo

This command boots the selected partition.

# Name
--- ----
0) Partition 0

Select a partition number: 0

Do you want to boot partition number 0? (Y/[N])

Once we select the BO command we can check in VFP everything is ok, and the go to the console and install or boot(if we had previous install) the hp-ux OS:

GSP:VFP (^B to Quit) >

GSP MAIN MENU:

CO: Consoles
VFP: Virtual Front Panel
CM: Command Menu
CL: Console Logs
SL: Show chassis Logs
HE: Help
X: Exit Connection

GSP> co

Partitions available:

# Name
--- ----
0) Partition 0
Q) Quit

Please select partition number: 0

Connecting to Console: Partition 0

(Use ^B to return to main menu.)
Main Menu: Enter command or menu > SEA all

Searching for potential boot device(s)
This may take several minutes.

To discontinue search, press any key (termination may not be immediate).

IODC
Path# Device Path (dec) Device Type Rev
----- ----------------- ----------- ----
P0 4/0/1/0/0.8 Random access media 4
4/0/3/0/0.0 Fibre Channel Protocol 8
4/0/4/0/0/4/0.0 Fibre Channel Protocol 13
4/0/6/0/0.0 Fibre Channel Protocol 8
P1 4/0/8/0/0.8 Random access media 4
P2 4/0/11/0/0.3 Sequential access media 4

Search terminated.

Main Menu: Enter command or menu > bo p0

BCH Directed Boot Path: 4/0/1/0/0.8

Do you wish to stop at the ISL prompt prior to booting? (y/n) >> y

Initializing boot Device.

Boot IO Dependent Code (IODC) Revision 4

Boot Path Initialized.

HARD Booted.

ISL Revision A.00.43 Apr 12, 2000

ISL> hpux -is

Boot
: disk(4/0/1/0/0.8.0.0.0.0.0;0)/stand/vmunix
10903552 + 2302064 + 4626368 start 0x41db568

IMPORTANT

The only partition created from the GSP is the Genesis Partition. All subsequent partition configurations are performed via the Partition Manager software, which requires an operating system to be up and running.

We are going to boot from a previous installation, and once we are in single user, using the parmodify command we can create the resto of out partitions:

# parstatus -C
[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 inactive 4/0/4 8.0/ 0.0 cab0,bay1,chassis3 yes - -
cab0,cell1 inactive 4/0/4 10.0/ 0.0 cab0,bay0,chassis3 yes - -
cab0,cell2 inactive 4/0/4 8.0/ 0.0 - no - -
cab0,cell3 inactive 4/0/4 10.0/ 0.0 - no - -
cab0,cell4 active core 4/0/4 10.0/ 0.0 cab0,bay0,chassis1 yes yes 0
cab0,cell5 inactive 4/0/4 12.0/ 0.0 cab8,bay0,chassis1 yes - -
cab0,cell6 inactive 4/0/4 10.0/ 0.0 cab0,bay1,chassis1 yes - -
cab0,cell7 inactive 4/0/4 10.0/ 0.0 cab8,bay0,chassis3 yes - -

#

As you can see we have only cell4 in use for our npar 0, I'm going to finish first with partition 0, I want to add another cell to the partition, it's partition 6.

So first I add cell 0/6:

# parmodify -p 0 -a 0/6:::

In order to activate any cell that has been newly added,
reboot the partition with the -R option.
Command succeeded.

Now I'm going to correct setboot, so it point's to my boot disk, and also enable autoboot and autosearch while we are at it:

# setboot
Primary bootpath : 4/0/1/0/0.6.0
Alternate bootpath : 4/0/1/0/0.5.0
# lvlnboot -v vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t8d0 (4/0/1/0/0.8.0) -- Boot Disk
/dev/dsk/c1t8d0 (4/0/8/0/0.8.0)
Boot: lvol1 on: /dev/dsk/c0t8d0
Root: lvol3 on: /dev/dsk/c0t8d0
Swap: lvol9 on: /dev/dsk/c0t8d0
Dump: lvol9 on: /dev/dsk/c0t8d0, 0
# setboot -p 4/0/1/0/0.8.0
# setboot -b on
# setboot -s on
# setboot
Primary bootpath : 4/0/1/0/0.8.0
Alternate bootpath : 4/0/1/0/0.5.0

Autoboot is ON (enabled)
Autosearch is ON (enabled)

Note: The interpretation of Autoboot and Autosearch has changed for
systems that support hardware partitions. Please refer to the manpage.

Now we are ready to reboot the server for reconfig, so it adds cell0/6 to partition 0:

# shutdown -R now

SHUTDOWN PROGRAM
04/11/12 10:58:55 METDST

Closing open logical volumes...
Done

Cells has been reset and are ready for reconfiguration (Boot Is Blocked (BIB) is set).

Please check Virtual Front Panel (VFP) for reset status.

On the VFP we can see the cell6 has joined:

Partition 0 state Activity
------------------ --------
HPUX Launch Processor display_activity update 143 Logs

# Cell state Activity
- ---------- --------
4 Cell has joined partition
6 Cell has joined partition

Once the Os has booted, we check with parstatus:

root@lsdbox:/> parstatus -C
[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 inactive 4/0/4 8.0/ 0.0 cab0,bay1,chassis3 yes - -
cab0,cell1 inactive 4/0/4 10.0/ 0.0 cab0,bay0,chassis3 yes - -
cab0,cell2 inactive 4/0/4 8.0/ 0.0 - no - -
cab0,cell3 inactive 4/0/4 10.0/ 0.0 - no - -
cab0,cell4 active core 4/0/4 10.0/ 0.0 cab0,bay0,chassis1 yes yes 0
cab0,cell5 inactive 4/0/4 12.0/ 0.0 cab8,bay0,chassis1 yes - -
cab0,cell6 active base 4/0/4 10.0/ 0.0 cab0,bay1,chassis1 yes yes 0
cab0,cell7 inactive 4/0/4 10.0/ 0.0 cab8,bay0,chassis3 yes - -

We have to cells 0/4 and 0/6 ,and 2 io-chassis 0-0-1 and 0-1-1

First I'm going to use the 2 new disks that are connected to the io chassis in the new cell we added 0/6, to do a mirror of my current os disks, so even if I loose and IO chassis I can still boot the OS from the mirror disks. I'm going to jump the mirror process, and continue when the mirror is ready

root@lsdbox:/> lvlnboot -vR /dev/vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t8d0 (4/0/1/0/0.8.0) -- Boot Disk
/dev/dsk/c1t8d0 (4/0/8/0/0.8.0)
/dev/dsk/c15t8d0 (6/0/1/0/0.8.0) -- Boot Disk
/dev/dsk/c16t8d0 (6/0/8/0/0.8.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t8d0
/dev/dsk/c15t8d0
Root: lvol3 on: /dev/dsk/c0t8d0
/dev/dsk/c15t8d0
Swap: lvol9 on: /dev/dsk/c0t8d0
/dev/dsk/c15t8d0
Dump: lvol9 on: /dev/dsk/c0t8d0, 0

We are going to change the alternate and HA alternate boot path,add an alternate core cell, and also configure a name for the partition:

root@lsdbox:/> parmodify -p 0 -s 6/0/1/0/0.8.0 -t 6/0/1/0/0.8.0
Command succeeded.
root@lsdbox:/> parmodify -p 0 -P bluemagic
Command succeeded.
root@lsdbox:/> parmodify -p -r 0/4 -r 0/6
Command succeeded.
root@lsdbox:/> parstatus -V -p 0
[Partition]
Partition Number : 0
Partition Name : bluemagic
Status : active
IP address : 0.0.0.0
Primary Boot Path : 4/0/1/0/0.8.0
Alternate Boot Path : 6/0/1/0/0.8.0
HA Alternate Boot Path : 6/0/1/0/0.8.0
PDC Revision : 36.8
IODCH Version : 5EA0
CPU Speed : 875 MHz
Core Cell : cab0,cell4
Core Cell Alternate [1]: cab0,cell6

[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell4 active core 4/0/4 10.0/ 0.0 cab0,bay0,chassis1 yes yes 0
cab0,cell6 active base 4/0/4 10.0/ 0.0 cab0,bay1,chassis1 yes yes 0

[Chassis]
Core Connected Par
Hardware Location Usage IO To Num
=================== ============ ==== ========== ===
cab0,bay0,chassis1 active yes cab0,cell4 0
cab0,bay1,chassis1 active yes cab0,cell6 0

We would just to configure one thing more that is the BCH behavior on booting the specified boot devices, from the bch:

Main Menu: Enter command or menu > ma

---- Main Menu ---------------------------------------------------------------

Command Description
------- -----------
BOot [PRI|HAA|ALT|] Boot from specified path
PAth [PRI|HAA|ALT] [] Display or modify a path
SEArch [ALL||] Search for boot devices
ScRoll [ON|OFF] Display or change scrolling capability

COnfiguration menu Displays or sets boot values
INformation menu Displays hardware information
SERvice menu Displays service commands

DIsplay Redisplay the current menu
HElp [|] Display help for menu or command
REBOOT Restart Partition
RECONFIGRESET Reset to allow Reconfig Complex Profile
----
Main Menu: Enter command or menu > CO

---- Configuration Menu ------------------------------------------------------

Command Description
------- -----------
BootID [[[]]] Display or set Boot Identifier
BootTimer [0-200] Seconds allowed for boot attempt
CEllConfig [] [ON|OFF] Config/Deconfig cell
COreCell [ ] Display or set core cell
CPUconfig [[[ON|OFF]]] Config/Deconfig processor
DataPrefetch [ENABLE|DISABLE] Display or set data prefetch behavior
DEfault Set the Partition to predefined values
FastBoot [test][RUN|SKIP] Display or set boot tests execution
KGMemory [] Display or set KGMemory requirement
PathFlags [PRI|HAA|ALT] [] Display or set Boot Path Flags
PD [] Display or set Partition name values
ResTart [ON|OFF] Set Partition Restart Policy
TIme [cn:yr:mo:dy:hr:mn:[ss]] Read or set the real time clock

BOot [PRI|HAA|ALT|] Boot from specified path
DIsplay Redisplay the current menu
HElp [] Display help for specified command
REBOOT Restart Partition
RECONFIGRESET Reset to allow Reconfig Complex Profile
MAin Return to Main Menu

Because we only have a 2 way mirror and to real devices we are going to configure the primary and HAA boot order, if none of them boot stay at the BCH:

Configuration Menu: Enter command > PathFlags pri 2

Primary Boot Path Action
Boot Actions: Boot from this path.
If unsuccessful, go to next path.

Configuration Menu: Enter command > PathFlags HAA 2

HA Alternate Boot Path Action
Boot Actions: Boot from this path.
If unsuccessful, go to next path.

Configuration Menu: Enter command > PathFlags ALT 0

Alternate Boot Path Action
Boot Actions: Go to BCH.

Configuration Menu: Enter command > PathFlags

Primary Boot Path Action
Boot Actions: Boot from this path.
If unsuccessful, go to next path.

HA Alternate Boot Path Action
Boot Actions: Boot from this path.
If unsuccessful, go to next path.

Alternate Boot Path Action
Boot Actions: Go to BCH.

Now that we have our partition 0 ready time to create a new partition, this partition has cells 5 cells(0 1 2 3 7)

Lets start:

#parcreate -P substanceD -c 0/0::: -c 0/1::: -c 0/2::: -c 0/3::: -c 0/7::: -b 0/0/1/0/0.8.0 -s 0/0/8/0/0.8.0 -r 0/0 -r 0/1 (with -r we choose the order of the core cells)

Error: There are incompatible cells:
Global cell 0, cabinet 0, cell 0 - IODC version 24224 PDC major 35
Global cell 1, cabinet 0, cell 1 - IODC version 24224 PDC major 35
Global cell 2, cabinet 0, cell 2 - IODC version 24224 PDC major 35
Global cell 3, cabinet 0, cell 3 - IODC version 24224 PDC major 35
Global cell 7, cabinet 0, cell 7 - IODC version 24224 PDC major 36
Command failed.
root@lsdbox:/>

As you can see I forgot to check that the firmware version of all the cells was the same before adding them to the partition, if we check with sysrev you can see that cell 7 has another firware revision:

GSP:CM> sysrev
Utility Subsystem FW Revision Level: 7.34

| Cabinet #0 | Cab #8 |
-----------------------+-----------------+--------+
| PDC | PDHC | |
Cell (slot 0) | 35.4 | 7.8 | |
Cell (slot 1) | 35.4 | 7.8 | |
Cell (slot 2) | 35.4 | 7.8 | |
Cell (slot 3) | 35.4 | 7.8 | |
Cell (slot 4) | 36.8 | 7.10 | |
Cell (slot 5) | 36.8 | 7.10 | |
Cell (slot 6) | 36.8 | 7.10 | |
Cell (slot 7) | 36.1 | 7.10 | |
| | |
GSP | 7.34 | |
CLU | 7.8 | 7.8 |
PM | 7.16 | 7.16 |
CIO (bay 0, chassis 1) | 7.4 | 7.4 |
CIO (bay 0, chassis 3) | 7.4 | 7.4 |
CIO (bay 1, chassis 1) | 7.4 | |
CIO (bay 1, chassis 3) | 7.4 | |

So for the moment I'm going to create the partition without cell 7, and once I upgrade the firmware I will add the cell:

#parcreate -P substanceD -c 0/0::: -c 0/1::: -c 0/2::: -c 0/3::: -b 0/0/1/0/0.8.0 -s 0/0/8/0/0.8.0 -r 0/0 -r 0/1
Partition Created. The partition number is: 1
root@lsdbox:/> parstatus -V -p 1
[Partition]
Partition Number : 1
Partition Name : substanceD
Status : inactive
IP address : 0.0.0.0
Primary Boot Path : 0/0/1/0/0.8.0
Alternate Boot Path : 0/0/8/0/0.8.0
HA Alternate Boot Path : 0/0/0/0/0.0.0
PDC Revision : 35.4
IODCH Version : 5EA0
CPU Speed : 875 MHz
Core Cell : ?
Core Cell Alternate [1]: cab0,cell1

[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 inactive 4/0/4 8.0/ 0.0 cab0,bay1,chassis3 yes yes 1
cab0,cell1 inactive 4/0/4 10.0/ 0.0 cab0,bay0,chassis3 yes yes 1
cab0,cell2 inactive 4/0/4 8.0/ 0.0 - no yes 1
cab0,cell3 inactive 4/0/4 10.0/ 0.0 - no yes 1

Before booting the cell so I can benefit from all the cells being in BIB, i'm going to update the firmware on all cells on partition 1 and also on cell 7:

Partition 1 state Activity
------------------ --------
Cell(s) Booting: 894 Logs

# Cell state Activity
- ---------- --------
0 Boot Is Blocked (BIB) Cell firmware 872 Logs
1 Boot Is Blocked (BIB) Cell firmware 723 Logs
2 Boot Is Blocked (BIB) Cell firmware 620 Logs
3 Boot Is Blocked (BIB) Cell firmware 494 Logs

We go into our SMS box:

root@sdorpe1:/opt/fwuu> strings /opt/fwuu/fwuu | grep A.00.
root@sdorpe1:/opt/fwuu> strings fwuu | grep .00.
P.00.01
P.00.01
@(#)FWUU: Revision Code P.00.01 (06/29/2001)
root@sdorpe1:/opt/fwuu> ls
PDC_36.8_release_notes_external.txt clu.7.8.frm hd.bin.36.8.frm quickref-fwuu.txt
Util_7.34_release_notes_external.txt fwuu pdhc.7.10.frm readme
cio.7.4.frm gsp.7.34.frm pm.7.16.frm
root@sdorpe1:/opt/fwuu> fwuu
sh: fwuu: not found.
root@sdorpe1:/opt/fwuu> ./fwuu

*********************************************************************
***** *****
***** Firmware Update Utility *****
***** *****
***** (C) Copyright Hewlett-Packard Co 1999 *****
***** All Rights Reserved *****
***** *****
***** THIS PROGRAM IS NOT LICENSED TO CUSTOMERS *****
***** *****
***** This program is intended for use by trained HP support *****
***** personnel only. HP shall not be liable for any damages *****
***** resulting from unauthorized use of this program. This *****
***** program is the property of HP. *****
***** *****
***** Version P.00.01 *****
***** *****
*********************************************************************

Please enter address of Halfdome system: 10.10.5.6
System successfully connected to "10.10.5.6"
System Utilities Board Firmware Update - header version 0.1

Maximum USB transfer size is 4100

Retrieving Complex Profile Information......

Complex Name: sdopemine
Model String: 9000/800/SD32000
Original Product Number: A5201A
Current Product Number: A5201A
Serial Number: DEHGBHLSD81

Firmware files found in "." directory:

Firmware
Filename Entity Type Revision Hversion
________________________ ___________ ________ _________
cio.7.4.frm CIO 7.4 0x42
clu.7.8.frm CLU 7.8 0x42
gsp.7.34.frm GSP 7.34 0x42
hd.bin.36.8.frm PDC 36.8 0x5c7
pdhc.7.10.frm PDHC 7.10 0x42
pm.7.16.frm PM 7.16 0x44

Listing flash handle map of remote system "10.10.5.6":

Flash Firmware
Cabinet Entity Type Handle Cell# CIO# Revision Hversion
_______ ___________ ______ _____ ____ ________ __________
0 GSP 576 N/A N/A 7.34 0x42
0 PM 640 N/A N/A 7.16 0x42
0 CLU 704 N/A N/A 7.8 0x42
0 CIO 769 4 1 7.4 0x42
0 CIO 771 1 3 7.4 0x42
0 CIO 773 6 5 7.4 0x42
0 CIO 775 0 7 7.4 0x42
0 PDHC 1088 0 N/A 7.8 0x42
0 PDC 1152 0 N/A 35.4 0x05EA
0 PDHC 1089 1 N/A 7.8 0x42
0 PDC 1153 1 N/A 35.4 0x05EA
0 PDHC 1090 2 N/A 7.8 0x42
0 PDC 1154 2 N/A 35.4 0x05EA
0 PDHC 1091 3 N/A 7.8 0x42
0 PDC 1155 3 N/A 35.4 0x05EA
0 PDHC 1092 4 N/A 7.10 0x42
0 PDC 1156 4 N/A 36.8 0x05EA
0 PDHC 1093 5 N/A 7.10 0x42
0 PDC 1157 5 N/A 36.8 0x05EA
0 PDHC 1094 6 N/A 7.10 0x42

Continue (yes/no)? [Y]: y

Flash Firmware
Cabinet Entity Type Handle Cell# CIO# Revision Hversion
_______ ___________ ______ _____ ____ ________ __________
0 PDC 1158 6 N/A 36.8 0x05EA
0 PDHC 1095 7 N/A 7.10 0x42
0 PDC 1159 7 N/A 36.1 0x05EA
8 PM 33408 N/A N/A 7.16 0x42
8 CLU 33472 N/A N/A 7.8 0x42
8 CIO 33537 5 1 7.4 0x42
8 CIO 33539 7 3 7.4 0x42

Type HELP for command information.o

No we are going to update the pdc on cell 7 using the flash handle 1159 and the 36.8 firmware

FWUU>update 1159 hd.bin.36.8.frm
1 flash handles are to be updated

Checking power state of cell 1159 .....
Checking PDHC BIB state of cell 1159 ......

Updating firmware................
Percentage Complete
0 %
Percentage Complete
100 %

Flash Update
Cabinet Entity Type Handle Firmware File Status
_______ ___________ ______ ______________________ _________
0 PDC 1159 hd.bin.36.8.frm PASSED

Now we can check it updated the PDC on the cell ok:

FWUU>DISPMAP

Listing flash handle map of remote system "10.10.5.6":

Flash Firmware
Cabinet Entity Type Handle Cell# CIO# Revision Hversion
_______ ___________ ______ _____ ____ ________ __________
0 GSP 576 N/A N/A 7.34 0x42
0 PM 640 N/A N/A 7.16 0x42
0 CLU 704 N/A N/A 7.8 0x42
0 CIO 769 4 1 7.4 0x42
0 CIO 771 1 3 7.4 0x42
0 CIO 773 6 5 7.4 0x42
0 CIO 775 0 7 7.4 0x42
0 PDHC 1088 0 N/A 7.8 0x42
0 PDC 1152 0 N/A 35.4 0x05EA
0 PDHC 1089 1 N/A 7.8 0x42
0 PDC 1153 1 N/A 35.4 0x05EA
0 PDHC 1090 2 N/A 7.8 0x42
0 PDC 1154 2 N/A 35.4 0x05EA
0 PDHC 1091 3 N/A 7.8 0x42
0 PDC 1155 3 N/A 35.4 0x05EA
0 PDHC 1092 4 N/A 7.10 0x42
0 PDC 1156 4 N/A 36.8 0x05EA
0 PDHC 1093 5 N/A 7.10 0x42
0 PDC 1157 5 N/A 36.8 0x05EA
0 PDHC 1094 6 N/A 7.10 0x42

You can also do several at the same time:

FWUU>update 1152 1153 1154 1155 hd.bin.36.8.frm
4 flash handles are to be updated

Checking power state of cell 1152 .....
Checking PDHC BIB state of cell 1152 ......

Checking power state of cell 1153 .....
Checking PDHC BIB state of cell 1153 ......

Checking power state of cell 1154 .....
Checking PDHC BIB state of cell 1154 ......

Checking power state of cell 1155 .....
Checking PDHC BIB state of cell 1155 ......

Updating firmware................
Percentage Complete
0 %
Percentage Complete
100 %

Flash Update
Cabinet Entity Type Handle Firmware File Status
_______ ___________ ______ ______________________ _________
0 PDC 1152 hd.bin.36.8.frm PASSED
0 PDC 1153 hd.bin.36.8.frm PASSED
0 PDC 1154 hd.bin.36.8.frm PASSED
0 PDC 1155 hd.bin.36.8.frm PASSED

FWUU>dispmap

Listing flash handle map of remote system "10.10.5.6":

Flash Firmware
Cabinet Entity Type Handle Cell# CIO# Revision Hversion
_______ ___________ ______ _____ ____ ________ __________
0 GSP 576 N/A N/A 7.34 0x42
0 PM 640 N/A N/A 7.16 0x42
0 CLU 704 N/A N/A 7.8 0x42
0 CIO 769 4 1 7.4 0x42
0 CIO 773 6 5 7.4 0x42
0 PDHC 1088 0 N/A 7.8 0x42
0 PDC 1152 0 N/A 36.8 0x05EA
0 PDHC 1089 1 N/A 7.8 0x42
0 PDC 1153 1 N/A 36.8 0x05EA
0 PDHC 1090 2 N/A 7.8 0x42
0 PDC 1154 2 N/A 36.8 0x05EA
0 PDHC 1091 3 N/A 7.8 0x42
0 PDC 1155 3 N/A 36.8 0x05EA
0 PDHC 1092 4 N/A 7.10 0x42
0 PDC 1156 4 N/A 36.8 0x05EA
0 PDHC 1093 5 N/A 7.10 0x42
0 PDC 1157 5 N/A 36.8 0x05EA
0 PDHC 1094 6 N/A 7.10 0x42
0 PDC 1158 6 N/A 36.8 0x05EA
0 PDHC 1095 7 N/A 7.10 0x42

Continue (yes/no)? [Y]: y

Flash Firmware
Cabinet Entity Type Handle Cell# CIO# Revision Hversion
_______ ___________ ______ _____ ____ ________ __________
0 PDC 1159 7 N/A 36.8 0x05EA
8 PM 33408 N/A N/A 7.16 0x42
8 CLU 33472 N/A N/A 7.8 0x42
8 CIO 33537 5 1 7.4 0x42
8 CIO 33539 7 3 7.4 0x42

Ok , we have all the PDC firmware level, now we are going to update the pdhc on the cells to revision 7.10, after updating the PDC the cells reset and go to the BIB state again, we have to check in the vfp of the GSP, to check they have reached BIB before we continue updating the PDC

FWUU>update 1088 1089 1090 1091 pdhc.7.10.frm
4 flash handles are to be updated

Checking power state of cell 1088 .....
Checking PDHC BIB state of cell 1088 ......

Checking power state of cell 1089 .....
Checking PDHC BIB state of cell 1089 ......

Checking power state of cell 1090 .....
Checking PDHC BIB state of cell 1090 ......

Checking power state of cell 1091 .....
Checking PDHC BIB state of cell 1091 ......

Updating firmware................
Percentage Complete
100 %

Flash Update
Cabinet Entity Type Handle Firmware File Status
_______ ___________ ______ ______________________ _________
0 PDHC 1088 pdhc.7.10.frm PASSED
0 PDHC 1089 pdhc.7.10.frm PASSED
0 PDHC 1090 pdhc.7.10.frm PASSED
0 PDHC 1091 pdhc.7.10.frm PASSED

Resetting entity(s) requested for update.....
Continue (yes/no)? [Y]: y

Successful reset of all entity(s).

Now if we check with sysrev we have all the cells with the same PDC/PDH:

GSP:CM> sysrev
Utility Subsystem FW Revision Level: 7.34

| Cabinet #0 | Cab #8 |
-----------------------+-----------------+--------+
| PDC | PDHC | |
Cell (slot 0) | 36.8 | 7.10 | |
Cell (slot 1) | 36.8 | 7.10 | |
Cell (slot 2) | 36.8 | 7.10 | |
Cell (slot 3) | 36.8 | 7.10 | |
Cell (slot 4) | 36.8 | 7.10 | |
Cell (slot 5) | 36.8 | 7.10 | |
Cell (slot 6) | 36.8 | 7.10 | |
Cell (slot 7) | 36.8 | 7.10 | |
| | |
GSP | 7.34 | |
CLU | 7.8 | 7.8 |
PM | 7.16 | 7.16 |
CIO (bay 0, chassis 1) | 7.4 | 7.4 |
CIO (bay 0, chassis 3) | 7.4 | 7.4 |
CIO (bay 1, chassis 1) | 7.4 | |
CIO (bay 1, chassis 3) | 7.4 | |

Now that we have leveled out the firmware, we can add cell 0/7 to partition 1:

root@lsdbox:/> parmodify -p 1 -a 0/7:::
Command succeeded.
root@lsdbox:/> parstatus -V -p 1
[Partition]
Partition Number : 1
Partition Name : substanceD
Status : inactive
IP address : 0.0.0.0
Primary Boot Path : 0/0/1/0/0.8.0
Alternate Boot Path : 0/0/8/0/0.8.0
HA Alternate Boot Path : 0/0/0/0/0.0.0
PDC Revision : 36.8
IODCH Version : 5EA0
CPU Speed : 875 MHz
Core Cell : ?
Core Cell Alternate [1]: cab0,cell1

[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 inactive 4/0/4 8.0/ 0.0 cab0,bay1,chassis3 yes yes 1
cab0,cell1 inactive 4/0/4 10.0/ 0.0 cab0,bay0,chassis3 yes yes 1
cab0,cell2 inactive 4/0/4 8.0/ 0.0 - no yes 1
cab0,cell3 inactive 4/0/4 10.0/ 0.0 - no yes 1
cab0,cell7 inactive 4/0/4 10.0/ 0.0 cab8,bay0,chassis3 yes yes 1

[Chassis]
Core Connected Par
Hardware Location Usage IO To Num
=================== ============ ==== ========== ===
cab0,bay1,chassis3 inactive yes cab0,cell0 1
cab0,bay0,chassis3 inactive yes cab0,cell1 1
cab8,bay0,chassis3 inactive yes cab0,cell7 1

We are ready to boot the partition:

Partition 1 state Activity
------------------ --------
Cell(s) Booting: 3981 Logs

# Cell state Activity
- ---------- --------
0 Boot Is Blocked (BIB) Cell PDH controller utility 893 Logs
1 Boot Is Blocked (BIB) Cell PDH controller utility 881 Logs
2 Boot Is Blocked (BIB) Cell PDH controller utility 641 Logs
3 Boot Is Blocked (BIB) Cell PDH controller utility 652 Logs
7 Boot Is Blocked (BIB) Cell firmware 783 Logs

we give it the boot command:

GSP:CM> bo

This command boots the selected partition.

# Name
--- ----
0) bluemagic
1) substanceD

Select a partition number: 1

Do you want to boot partition number 1? (Y/[N]) y

-> The selected partition will be booted.
GSP:CM>

Once it boots we have:

root@/> parstatus -V -p 1
[Partition]
Partition Number : 1
Partition Name : substanceD
Status : active
IP address : 0.0.0.0
Primary Boot Path : 0/0/1/0/0.8.0
Alternate Boot Path : 0/0/8/0/0.8.0
HA Alternate Boot Path : 0/0/0/0/0.0.0
PDC Revision : 36.8
IODCH Version : 5EA0
CPU Speed : 875 MHz
Core Cell : cab0,cell1
Core Cell Alternate [1]: cab0,cell0
Core Cell Alternate [2]: cab0,cell1
Core Cell Alternate [3]: cab0,cell7

[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 active base 4/0/4 8.0/ 0.0 cab0,bay1,chassis3 yes yes 1
cab0,cell1 active core 4/0/4 10.0/ 0.0 cab0,bay0,chassis3 yes yes 1
cab0,cell2 active base 4/0/4 8.0/ 0.0 - no yes 1
cab0,cell3 active base 4/0/4 10.0/ 0.0 - no yes 1
cab0,cell7 active base 4/0/4 10.0/ 0.0 cab8,bay0,chassis3 yes yes 1

[Chassis]
Core Connected Par
Hardware Location Usage IO To Num
=================== ============ ==== ========== ===
cab0,bay1,chassis3 active yes cab0,cell0 1
cab0,bay0,chassis3 active yes cab0,cell1 1
cab8,bay0,chassis3 active yes cab0,cell7 1

And we can finally create our third partition with the only cell we have left, cell 5:

# parstatus -C
[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 active base 4/0/4 8.0/ 0.0 cab0,bay1,chassis3 yes yes 1
cab0,cell1 active core 4/0/4 10.0/ 0.0 cab0,bay0,chassis3 yes yes 1
cab0,cell2 active base 4/0/4 8.0/ 0.0 - no yes 1
cab0,cell3 active base 4/0/4 10.0/ 0.0 - no yes 1
cab0,cell4 active core 4/0/4 10.0/ 0.0 cab0,bay0,chassis1 yes yes 0
cab0,cell5 inactive 4/0/4 12.0/ 0.0 cab8,bay0,chassis1 yes - -
cab0,cell6 active base 4/0/4 10.0/ 0.0 cab0,bay1,chassis1 yes yes 0
cab0,cell7 active base 4/0/4 10.0/ 0.0 cab8,bay0,chassis3 yes yes 1

We use the -B option, what this does ir remove the BIB from the cell specified in the parcreate command, so the partition will boot automaticly when created:

# parcreate -P blueSoma -c 0/5::: -b 5/0/8/0/0.8.0 -B
Partition Created. The partition number is: 2
# parstatus -V -p 2
[Partition]
Partition Number : 2
Partition Name : blueSoma
Status : active
IP address : 0.0.0.0
Primary Boot Path : 5/0/8/0/0.8.0
Alternate Boot Path : 0/0/0/0/0.0.0
HA Alternate Boot Path : 0/0/0/0/0.0.0
PDC Revision : 36.8
IODCH Version : 5EA0
CPU Speed : 875 MHz
Core Cell : cab0,cell5

[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell5 active core 4/0/4 12.0/ 0.0 cab8,bay0,chassis1 yes yes 2

[Chassis]
Core Connected Par
Hardware Location Usage IO To Num
=================== ============ ==== ========== ===
cab8,bay0,chassis1 active yes cab0,cell5 2

Unix Systems: 

Add new comment

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.

Fatal error: Class CToolsCssCache contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (DrupalCacheInterface::__construct) in /homepages/37/d228974590/htdocs/sites/all/modules/ctools/includes/css-cache.inc on line 52