2.2 The Genesis Partition

     

The Genesis Partition gets its name from the biblical story of the beginning of time. In our case, the Genesis Partition is simply the first partition that is created. When we discussed designing a Complex Profile, we realized that when we have 16 cells , there are 65,536 possible cell combinations. Trying to create a complex profile from the GSP, which is a simple terminal-based interface, would be somewhat tiresome. Consequently, the Genesis Partition is simply a one-cell partition that allows us to boot a partition and install an operating system. The Genesis Partition is the only partition created on the GSP. All other partition configuration is performed via Partition Manager commands run from an operating system . Once we have created the Genesis Partition, we can boot the system from an install server and install HP-UX. From that initial operating system installation, we can create a new partition, and from there we can create other partitions as we see fit. After the initial installation is complete, the Genesis Partition is of no special significance. It is in no way more important than any other partition; partition 0 doesn't even have to exist.

2.2.1 Ensure that all cells are inactive

In order to create the Genesis Partition, all cells must be inactive and shut down ready-for-reconfig . You will have to take my word for the fact that I have shut down all my partitions using the shutdown “RH now command:

 

 root@uksd4 #  shutdown -RH now  SHUTDOWN PROGRAM 11/07/03 22:33:07 GMT Broadcast Message from root (console) Fri Nov 7 22:33:07... SYSTEM BEING BROUGHT DOWN NOW ! ! ! 

We can check the status of the cells/partitions by using the VFP:

 

 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>  vfp  Partition VFP's available:      #   Name     ---  ----      0)  uksd1      1)  uksd2      2)  uksd3      3)  uksd4      S)  System (all chassis codes)      Q)  Quit GSP:VFP>  s  E indicates error since last boot   #  Partition state               Activity   -  ---------------               --------   0  Cell(s) Booting:    677 Logs   1  Cell(s) Booting:    716 Logs   2  Cell(s) Booting:    685 Logs   3  Cell(s) Booting:    276 Logs GSP:VFP (^B to Quit) > 

It may seem strange that the cells for each partition are trying to boot, but they aren't. When we look at an individual partition, we can see the actual state of the cells:

 

 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>  vfp  Partition VFP's available:      #   Name     ---  ----      0)  uksd1      1)  uksd2      2)  uksd3      3)  uksd4      S)  System (all chassis codes)      Q)  Quit GSP:VFP>   E indicates error since last boot      Partition 0  state            Activity      ------------------            --------      Cell(s) Booting:    677 Logs   #  Cell state                    Activity   -  ----------                    --------   0  Boot Is Blocked (BIB)         Cell firmware                    677  Logs GSP:VFP (^B to Quit) > 

Only at this point (when all cells are inactive) can we proceed with creating the Genesis Partition.

2.2.2 Creating the Genesis Partition

If we attempt to create the Genesis Partition while partitions are active, it will fail. To create the Genesis Partition, we use the GSP CC command:

 

 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>  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: 

As you can see, the GSP is able to restore the previous incarnation of Complex Profile. We will choose option G (Build genesis complex profile) :

 

 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: 

The initial questions relating to the creation of the Genesis Partition are relatively simple; the GSP only needs to know which single cell will be the initial cell that will form partition 0. This cell must be Core Cell capable; in other words, at least one CPU (preferably at least two), at least one Rank/Echelon of RAM (preferably at least two) connected to an IO cardcage that has a Core IO card installed in slot 0. If you know all this information, you can proceed with creating the Genesis Partition:

 

 Choose the cell to use.     Enter cabinet number:   Enter slot number:   Do you want to modify the complex profile? (Y/[N])  y  -> The complex profile will be modified. GSP:CM> 

I have chosen to select cell 0 for partition 0. It is not important which cell forms the Genesis Partition, as long as it is Core Cell capable. The GSP will check that it meets the criteria we mentioned previously. Assuming that the cell passes those tests, the Genesis Partition has now been created. In total, all the tasks from issuing the CC command took approximately 10 seconds. This is the only partition configuration we can perform from the GSP. We can now view the resulting Complex Profile:

 

 GSP:CM>  cp  -------------------------------------------------------------------------------- Cabinet    0       1       2       3       4       5       6       7 --------+--------+--------+--------+--------+--------+--------+--------+--------  Slot   0123456701234567012345670123456701234567012345670123456701234567 --------+--------+--------+--------+--------+--------+--------+--------+-------- 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:   Do you want to boot partition number 0? (Y/[N])  y  -> The selected partition will be booted. GSP:CM> 

This is when it is ideal to have at least three of the screens we mentioned previously (Console, VFP, and Command Menu screens) in order to flip between the screens easily. We issue the BO command from the Command Menu screen, and then we want to monitor the boot-up of the partition from the VFP screen, and we interact with the boot-up of HP-UX from the Console screen. Here I have interacted with the boot-up of HP-UX in the Console screen:

 

 GSP:CM>  ma  GSP:CM>     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:   Connecting to Console: Partition 0         (Use ^B to return to main menu.)         [A few lines of context from the console log:] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -      MFG menu                          Displays manufacturing commands      DIsplay                           Redisplay the current menu      HElp [<menu><command>]           Display help for menu or command      REBOOT                            Restart Partition      RECONFIGRESET                     Reset to allow Reconfig Complex Profile ---- Main Menu: Enter command or menu > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Main Menu: Enter command or menu > Main Menu: Enter command or menu >  main  ---- Main Menu ----------------------------------------------------------      Command                          Description      -------                          -----------      BOot [PRIHAAALT<path>]        Boot from specified path      PAth [PRIHAAALT] [<path>]      Display or modify a path      SEArch [ALL<cell><path>]       Search for boot devices      ScRoll [ONOFF]                  Display or change scrolling capability      COnfiguration menu               Displays or sets boot values      INformation menu                 Displays hardware information      SERvice menu                     Displays service commands      DeBug menu                       Displays debug commands      MFG menu                         Displays manufacturing commands      DIsplay                          Redisplay the current menu      HElp [<menu><command>]          Display help for menu or command      REBOOT                           Restart Partition      RECONFIGRESET                    Reset to allow Reconfig Complex Profile ---- Main Menu: Enter command or menu > 

As you can see, the interface looks similar to the BCH from a traditional HP-UX server. Apart from some slight changes during the initial Power-On Self Test phase, the boot-up of a partition is extremely similar to the boot-up of a traditional server. Returning to the BCH interface, we can check whether any of the old boot paths were retained.

 

 Main Menu: Enter command or menu >  path  Primary Boot Path:  0/0/1/0/0.6 0/0/1/0/0.6    (hex) HA Alternate Boot Path:  0/0/1/0/0.6 0/0/1/0/0.6    (hex) Alternate Boot Path:  0/0/1/0/0.5 0/0/1/0/0.5    (hex) Main Menu: Enter command or menu > 

As you can see, they have taken some default values that mean nothing to us. At this stage, we have two choices: (1) we can reinstall HP-UX, or (2) we can boot the original HP-UX, which is still located on the original root disk. Changing the complex profile has not changed the fundamental operating system stored on disk; it is still on disk and will quite happily run with this new partition configuration. If we think about it, it is akin to shutting down a traditional server adding/removing some CPU, RAM, and/or IO cards and booting the server again. HP-UX will discover the hardware during the IO discovery phase and use what it finds. Some devices may be missing if the previous partition had additional IO cardcages. This may affect the activation of volume groups, activating LAN cards and other hardware related configuration, but in essence we can simply use the operating system that was installed previously on the disk attached to the IO cardcage for this cell.

If there is no operating system available, we will have to install it. In such a situation, we will need access to a boot device. Here we can see the SEARCH command from the BCH.

 

 Main Menu: Enter command or menu >  search  Searching for potential boot device(s) This may take several minutes. To discontinue search, press any key (termination may not be immediate).    Path#  Device Path (dec)                      Device Type    -----  -----------------                      -----------    P0     0/0/1/0/0.1                            Random access media    P1     0/0/1/0/0.0                            Random access media           0/0/8/0/0.0                            Fibre Channel Protocol    P2     0/0/11/0/0.3                           Sequential access media    P3     0/0/11/0/0.1                           Random access media           0/0/14/0/0.0                           Fibre Channel Protocol Main Menu: Enter command or menu > 

This all looks quite familiar. If I had a local device such as a CD/DVD drive and I were going to install HP-UX from that device, I would simply boot from one of the devices listed above. Let's try to SEARCH for an install server attached to our LAN. The traditional method to do this would be with the BCH command SEARCH LAN INSTALL .

 

 Main Menu: Enter command or menu >  search lan install  ERROR: Unknown device Search Table has been cleared Main Menu: Enter command or menu > 

As you can see, a Node Partition has no concept of the logical device known as LAN . It is too much for the boot interface in a server complex to be able to traverse every possible cell in our partition looking for a LAN card. Consequently, I need to have done my homework earlier and know the hardware path to a LAN card connected to a network where an Install server is located. My only other option is to use the Information Menu, which can tell me which cards are installed in which slots:

 

 Main Menu: Enter command or menu >  in  ---- Information Menu -------------------------------------------------------      Command                           Description      -------                           -----------      ALL [<cell>]                   Display all of the information      BootINfo                       Display boot-related information      CAche [<cell>]                 Display cache information      ChipRevisions [<cell>]         Display revisions of major VLSI      ComplexID                      Display Complex information      FabricInfo                     Display Fabric information      FRU [<cell>] [CPUMEM]         Display FRU information      FwrVersion [<cell>]            Display version for PDC, ICM, and Complex      IO [<cell>]                    Display I/O interface information      MEmory [<cell>]                Display memory information      PRocessor [<cell>]             Display processor information      BOot [PRIHAAALT<path>]      Boot from specified path      DIsplay                        Redisplay the current menu      HElp [<command>]               Display help for specified command      REBOOT                         Restart Partition      RECONFIGRESET                  Reset to allow Reconfig Complex Profile      MAin                           Return to Main Menu ---- Information Menu: Enter command > Information Menu: Enter command >  io 0  I/O CHASSIS INFORMATION    Cell Info             I/O Chassis Info Cell   Cab/Slot        Cab    Bay   Chassis ----   --------        ---    ---   -------   0      0/0            0      1      3 I/O MODULE INFORMATION                     Path            Slot   Rope                         IODC Type                (dec)            #      #     HVERSION   SVERSION   Vers ----                -----           ----   ----   --------   --------   ---- System Bus Adapter  0/0                            0x8040     0x0c18    0x00 Local Bus Adapter   0/0/0            0       0     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/1            1       1     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/2            2       2     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/3            3       3     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/4            4       4     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/6            5       6     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/8            11      8     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/9            10      9     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/10           9      10     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/11           8      11     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/12           7      12     0x7820     0x0a18    0x00 Local Bus Adapter   0/0/14           6      14     0x7820     0x0a18    0x00 PCI DEVICE INFORMATION                             Path             Bus    Slot      Vendor   Device Description                 (dec)             #      #          Id       Id -----------                 -----            ---   ------     ------   ------ Comm. serial cntlr          0/0/0/0/0        0       0        0x103c   0x1048 Ethernet cntlr              0/0/0/1/0        0       0        0x1011   0x0019 SCSI bus cntlr              0/0/1/0/0        8       1        0x1000   0x000c SCSI bus cntlr              0/0/3/0/0        24      3        0x1000   0x000f SCSI bus cntlr              0/0/3/0/1        24      3        0x1000   0x000f Fibre channel               0/0/8/0/0        64     11        0x103c   0x1028 Ethernet cntlr              0/0/9/0/0        72     10        0x1011   0x0019 SCSI bus cntlr              0/0/10/0/0       80      9        0x1000   0x000f SCSI bus cntlr              0/0/10/0/1       80      9        0x1000   0x000f SCSI bus cntlr              0/0/11/0/0       88      8        0x1000   0x000f Fibre channel               0/0/14/0/0       112     6        0x103c   0x1028 Information Menu: Enter command > 

I can see that I have a LAN card at Hardware Path 0/0/0/1/0. I can attempt to boot from it:

 

 Main Menu: Enter command or menu >  boot 0/0/0/1/0  BCH Directed Boot Path: 0/0/0/1/0.0  Do you wish to stop at the ISL prompt prior to booting? (y/n) >> n Initializing boot Device. Boot IO Dependent Code (IODC) Revision 2 ... NOTE:        The console firmware terminal type is currently set to "vt100". If you        are using any other type of terminal you will see "garbage" on the        screen following this message.        If this is the case, you will need to either change the terminal type        set in the firmware via GSP (if your GSP firmware version supports        this feature), or change your terminal emulation to match the        firmware. In either case you will need to restart if your terminal and        the firmware terminal type do not match.        Press the 'b' key if you want to reboot now.                         Welcome to Ignite-UX!  Use the <tab> key to navigate between fields, and the arrow keys  within fields. Use the <return/enter> key to select an item.  Use the <return/enter> or <space-bar> to pop-up a choices list. If the  menus are not clear, select the "Help" item for more information.  Hardware Summary:         System Model: 9000/800/SD32000  +---------------------+----------------+-------------------+ [ S  c  an Again  ]   Disks: 3 ( 101.7GB)   Floppies: 0    LAN cards:   2       CD/DVDs:        1     Tapes:    1    Memory:    4096Mb    Graphics Ports: 0     IO Buses: 8    CPUs:        4     [ H/W  D  etails ]  +---------------------+----------------+-------------------+                        [  I  nstall HP-UX       ]                        [  R  un a Recovery Shell   ]                        [  A  dvanced Options      ]           [  Re  b  oot  ]                              [  H  elp  ] 

As we can see, we have now found an Ignite/UX install server from which we can boot and install the operating system. Once the operating system is installed and we have customized it as we see fit, HP-UX will boot. That would be the time to add additional partitions and modify the existing partition, if that is appropriate. The additional partition-related tasks are not performed from the GSP but from the operating system we have just installed.

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.


Before we leave this section, let me say just a few words regarding the Information Menu in the BCH. This is a good place to gather additional information and consolidate your existing cell-related device information, e.g., CPU and memory:

 

 Information Menu: Enter command >  me 0  CELL MEMORY INFORMATION Memory Information for Cell:  0   Cab/Slot:  0/ 0      ---- DIMM A ----   ---- DIMM B ----   ---- DIMM C ---  ---- DIMM D ----       DIMM  Current      DIMM  Current      DIMM  Current    DIMM  Current Rank  Size  Status       Size  Status       Size  Status     Size  Status ---- ------ ----------  ------ ----------  ------ --------  ------ ----------   0   512MB Active       512MB Active       512MB Active     512MB Active   1   512MB Active       512MB Active       512MB Active     512MB Active   2    ---                ---                ---              ---   3    ---                ---                ---              ---   4    ---                ---                ---              ---   5    ---                ---                ---              ---   6    ---                ---                ---              ---   7    ---                ---                ---              ---        Cell Total Memory:     4096 MB       Cell Active Memory:     4096 MB Cell Deconfigured Memory:        0 MB * status is scheduled to change on next boot. Information Menu: Enter command > 

Here, I am looking at my current memory compliment confirming my use of four 512MB DIMMs per Rank .

 

 Information Menu: Enter command >  pr  PROCESSOR INFORMATION         Cab/                                                     Processor  Cell   Slot   CPU    Speed     HVERSION   SVERSION   CVERSION     State  ----   ----   ---   --------   --------   --------   --------  --------------    0    0/0     0     552 MHz    0x5c70     0x0491     0x0301    Active                 1     552 MHz    0x5c70     0x0491     0x0301    Idle                 2     552 MHz    0x5c70     0x0491     0x0301    Idle                 3     552 MHz    0x5c70     0x0491     0x0301    Idle              Partition Total Cells: 1         Partition Total Processors: 4        Partition Active Processors: 4  Partition Deconfigured Processors: 0 Information Menu: Enter command > 

I will let you explore other Information Menu commands in your own time.

2.2.2.1 BOOT ACTIONS

Once HP-UX has installed and rebooted, you may want to check the state of you Boot Paths. The install process should have set your Primary Boot Path to be the disk you specified as your root disk during the installation.

 

 root@uksd1 #  setboot  Primary bootpath : 0/0/1/0/0.0.0 Alternate bootpath : 0/0/1/0/0.5.0 Autoboot is OFF (disabled) Autosearch is OFF (disabled) Note: The interpretation of Autoboot and Autosearch has changed for systems that support hardware partitions. Please refer to the manpage. root@uksd1 # 

Notice that Autoboot and Autosearch are both OFF . You can also see the Note regarding the change to the meaning of these parameters. We can still modify these parameters via the setboot command.

 

 root@uksd1 #  setboot -b on  root@uksd1 #  setboot -s on  root@uksd1 #  setboot  Primary bootpath : 0/0/1/0/0.0.0 Alternate bootpath : 0/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. root@uksd1 # 

However, there are two new concepts related to booting that are new with Node Partitionable servers. This first new concept is in relation to the number of Boot Paths available to us. Instead of having only a Primary (PRI) and an Alternate (ALT) Boot Path, we have an additional Boot Path ”a High Availability Alternate (HAA). By default, this device is searched second in the list of boot devices. To set the HAA Boot Path, we need to use either the BCH PATH HAA <path> command or the Partition Manager parmodify command.

 

 root@uksd1 #  parstatus -w  The local partition number is 0. root@uksd1 #  parstatus -Vp 0  [Partition] Partition Number       : 0 Partition Name         : Partition 0 Status                 : active IP address             : 0.0.0.0 Primary Boot Path      : 0/0/1/0/0.0.0 Alternate Boot Path    : 0/0/1/0/0.5.0   HA Alternate Boot Path : 0/0/1/0/0.6.0   PDC Revision           : 35.4 IODCH Version          : 5C70 CPU Speed              : 552 MHz Core Cell              : cab0,cell0 [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 core  4/0/4    4.0/ 0.0 cab0,bay1,chassis3  yes     yes  0 [Chassis]                                  Core Connected  Par Hardware Location   Usage        IO   To         Num =================== ============ ==== ========== === cab0,bay1,chassis3  active       yes  cab0,cell0 0 root@uksd1 # root@uksd1 #   parmodify -p 0 -s 0/0/1/0/0.1.0   Command succeeded. root@uksd1 #   parstatus -Vp 0   [Partition] Partition Number       : 0 Partition Name         : Partition 0 Status                 : active IP address             : 0.0.0.0 Primary Boot Path      : 0/0/1/0/0.0.0 Alternate Boot Path    : 0/0/1/0/0.5.0   HA Alternate Boot Path : 0/0/1/0/0.1.0   PDC Revision           : 35.4 IODCH Version          : 5C70 CPU Speed              : 552 MHz Core Cell              : cab0,cell0 [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 core  4/0/4    4.0/ 0.0 cab0,bay1,chassis3  yes     yes  0 [Chassis]                                  Core Connected  Par Hardware Location   Usage        IO   To         Num =================== ============ ==== ========== === cab0,bay1,chassis3  active       yes  cab0,cell0 0 root@uksd1 # 

To set the Alternate Boot Path with parmodify , we would use the “t <path> option.

 

 root@uksd1 #  ioscan -fnkC tape  Class     I  H/W Path        Driver S/W State   H/W Type     Description ======================================================================== tape      3  0/0/11/0/0.3.0  stape CLAIMED     DEVICE       HP      C1537A                             /dev/rmt/3m            /dev/rmt/c6t3d0BESTn                             /dev/rmt/3mb           /dev/rmt/c6t3d0BESTnb                             /dev/rmt/3mn           /dev/rmt/c6t3d0DDS                             /dev/rmt/3mnb          /dev/rmt/c6t3d0DDSb                             /dev/rmt/c6t3d0BEST    /dev/rmt/c6t3d0DDSn                             /dev/rmt/c6t3d0BESTb   /dev/rmt/c6t3d0DDSnb root@uksd1 #  parmodify -p 0 -s 0/0/11/0/0.3.0  Command succeeded. root@uksd1 #  parstatus -Vp 0  [Partition] Partition Number       : 0 Partition Name         : Partition 0 Status                 : active IP address             : 0.0.0.0 Primary Boot Path      : 0/0/1/0/0.0.0   Alternate Boot Path    : 0/0/1/0/0.5.0   HA Alternate Boot Path : 0/0/11/0/0.3.0 PDC Revision           : 35.4 IODCH Version          : 5C70 CPU Speed              : 552 MHz Core Cell              : cab0,cell0 [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 core  4/0/4    4.0/ 0.0 cab0,bay1,chassis3  yes     yes  0 [Chassis]                                  Core Connected  Par Hardware Location   Usage        IO   To         Num =================== ============ ==== ========== === cab0,bay1,chassis3  active       yes  cab0,cell0 0 root@uksd1 # 

Here's how I remember the options to parmodify :

  • Primary = Boot = -b <path>

  • HA Alternate = Second = -s <path>

  • Alternate = Third = -t <path>

The second new concept is related to the behavior of the search algorithm when searching the three available boot devices. This is known as PATHFLAGS . The PATHFLAGS affect how the boot interface interprets the three boot paths available to it. Remember, the three boot paths in order are:

  1. Primary (PRI)

  2. High-Availability Alternate (HAA)

  3. Alternate (ALT)

By default, the boot interface will go to the next boot path if the current path fails to boot the operating system. The PATHFLAGS can change this behavior. A PATHFLAG is a numeric value associated with each boot path. The available PATHFLAGs are:

: Go to BCH; if this path is accepted, stop at the Boot Console Handler.

1 : Boot from this path; if unsuccessful , go to BCH.

2 : Boot from this path; if unsuccessful, go to the next path (default).

3 : Skip this path, and go to the next path.

The only place to directly set/modify the PATHFLAGS is from the BCH Configuration screen. If this is the first time you have experienced this, you will need to reboot HP-UX in order to interact with BCH:

 

 Main Menu: Enter command or menu >  co  ---- Configuration Menu -----------------------------------------------------     Command                           Description     -------                           -----------     BootID [<cell>[<proc>[<bootid>]]] Display or set Boot Identifier     BootTimer [0-200]                 Seconds allowed for boot attempt     CEllConfig [<cell>] [ONOFF]      Config/Deconfig cell     COreCell [<choice> <cell>]        Display or set core cell     CPUconfig [<cell>[<cpu>[ONOFF]]] Config/Deconfig processor     DataPrefetch [ENABLEDISABLE]     Display or set data prefetch behavior     DEfault                           Set the Partition to predefined values     FastBoot [test][RUNSKIP]         Display or set boot tests execution     KGMemory [<value>]                Display or set KGMemory requirement     PathFlags [PRIHAAALT] [<value>] Display or set Boot Path Flags     PD [<name>]                       Display or set Partition name values     ResTart [ONOFF]                  Set Partition Restart Policy     TIme [cn:yr:mo:dy:hr:mn:[ss]]     Read or set the real time clock     BOot [PRIHAAALT<path>]         Boot from specified path     DIsplay                           Redisplay the current menu     HElp [<command>]                  Display help for specified command     REBOOT                            Restart Partition     RECONFIGRESET                     Reset to allow Reconfig Complex Profile     MAin                              Return to Main Menu ---- Configuration Menu: Enter command > Configuration Menu: Enter command >  pf  Primary Boot Path Action           Boot Actions:  Boot from this path.                          If unsuccessful, go to next path. HA Alternate Boot Path Action           Boot Actions:  Go to BCH.    Alternate Boot Path Action           Boot Actions:  Go to BCH. Configuration Menu: Enter command > 

On a preconfigured server complex, the PATHFLAGS for all three Boot Paths should be 2 (Boot from this path; if unsuccessful, go to the next path). To change a path, we use the PF command for each Boot Path:

 

 Configuration Menu: Enter command >  pf pri 2  Primary Boot Path Action           Boot Actions:  Boot from this path.                          If unsuccessful, go to next path. Configuration Menu: Enter command >  pf haa 2  HA Alternate Boot Path Action           Boot Actions:  Boot from this path.                          If unsuccessful, go to next path. Configuration Menu: Enter command >  pf alt 2  Alternate Boot Path Action           Boot Actions:  Boot from this path.                          If unsuccessful, go to next path. Configuration Menu: Enter command >  pf  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:  Boot from this path.                          If unsuccessful, go to next path. Configuration Menu: Enter command > 

In some instances it may be appropriate to change the PATHFLAGS for a particular Boot Path, e.g., due to a hardware failure or testing, where you don't want to change the actual Boot Paths themselves .

Before we look at the Partition Manager software, we should discuss some important concepts regarding the state of cells during the initial boot of a partition. This discussion will help to explain the need for certain options when adding, removing and modifying cells in a partition.



HP-UX CSE(c) Official Study Guide and Desk Reference
HP-UX CSE(c) Official Study Guide and Desk Reference
ISBN: N/A
EAN: N/A
Year: 2006
Pages: 434

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net