|
|
United States-English | |
|
|
 |
|
HP-UX 11i December 2002 Release Notes: HP-UX Servers and Workstations > Chapter 4 nPartition (Hard
Partition) Systems
New and Modified Hard Partition Commands |
|
|
new at 11i |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Command | Description |
|---|---|
Creates a new partition. | |
| parmodify(1M) | Modifies an existing partition. |
| parstatus(1) | Provides information about an entire Superdome complex, including partition information and available resources in the complex. |
| parremove(1M) | Removes an existing partition. |
| parunlock(1M) | Unlocks the Stable Complex Configuration Data or Partition Configuration Data. |
| fruled(1) | Turns locator LEDs on/off for cells, cabinets and I/O chassis. |
| frupower(1M) | Enables or disables power to a cell or I/O chassis, or displays the power status of cells or I/O chassis. |
The commands shutdown and reboot have been modified for systems that support hard partitions. Two new options, -R and -H, have been added to both these commands.
The -R option is used to shut down the system to a "ready to reconfig" state and reboot automatically. The -R -H option is used to shut down the system to a "ready to reconfig" state but without rebooting. A partition must be put into the “ready to reconfig” state before its newly assigned cells can be activated. (A normal reboot will not activate newly assigned cells.) The “ready to config” state is also necessary to complete the removal of active cells that have been unassigned from the partition. The commands' default behaviors, or the behaviors of all the other existing options, remain unchanged.
The interpretation of Autoboot and Autosearch in the command setboot has changed for systems that support hard partitions. The firmware interprets the bits in combination and not individually as done before.
In order to approximate the traditional behavior of setboot, the user input for the Autoboot and Autosearch flags is internally mapped to the right combination to achieve the desired behavior. This mapping should be transparent to the user of setboot, but it might not be so apparent to those accessing the firmware using other means. For the primary path, the boot action corresponds to the Autoboot and Autosearch flags in the following manner:
Table 4-3 nPartition Boot Actions
AutoBoot | AutoSearch | nPartition Boot Action |
|---|---|---|
off | off | Go to the Boot Console Handler (BCH) and prompt the user. |
on | off | Attempt the primary path; on failure go to BCH. |
on | on | Attempt to boot the PRI boot path; if fail to boot PRI, attempt to perform the HAA boot path's boot action. |
off | on | Skip the PRI boot path; attempt to perform the HAA boot path's boot action. |
Additionally, systems with hard partitions support a boot action for each path. However, boot actions for paths other than the primary path cannot be set using setboot. (In this case, the default boot action for boot paths on nPartitions is “skip this device and try next path,” [a path flag value of 2.]) Instead, setting both the Autosearch and Autoboot flags to “on” (setboot -b on -s on) means that if the PRI path fails to boot, then booting the HAA boot path will not be attempted unless the HAA path flag is set to a non-default value (such as 1 or 2, which attempt booting HAA).
In the default case (when the HAA boot path is not set to "boot from the path"), specifying setboot -b on -s on will not cause an alternate path to be automatically booted when the primary path fails. Instead the user will be prompted.
Eight new manpages document the syntax and usage of the new commands. The reboot(1M) and shutdown(1M) manpages have been updated to document the -R and -H options, and the setboot(1M) manpage has been updated as well.
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
