Professional Documents
Culture Documents
Npars, Vpars HPUX
Npars, Vpars HPUX
Remote Partition
Remote partitions are all other partitions within a complex, excluding the
partition that the user is logged into.
Active Partitions
Any partition that is either booted to BCH or OS.
Inactive Partitions
Any partition either un-initialized or at BIB, (reset for recon fig).
Genesis Partition
- The first partition created on a complex, a single cell partition.
- Created using the MP> cc command. Addition partitions can only be
created in HPUX.
Core cells
One cell serves as the core cell in a partition, there can be alternates.
Active Cells: Cells that have joined a partition, and are past BIB.
Inactive Cells: cells that failed to join a partition or deconfigured for boot.
Free Cells: not assigned to a partition.
Partition Numbers
Are determined automatically when the partition is created.
The lowest available number is used.
Hardware
Each partition contains at least one cell board, PCI domain and core IO.
Note:
-
BCH /EFI
BIB
rr equivalent commands
BCH = reconfigreset
EFI = resetreconfig
HPUX = shutdown R -H
Note:
-
rs equivalent commands
BCH = reboot
EFI = reset
SAC = restart
HPUX = shutdown r
Linux = shutdown r
GSP/MP:CM>rr
GSP/MP:CM>rs
HAA -- The high-availability alternate boot path. A mirror of the root volume.
setboot does not support this path.
ALT -- The alternate boot path. Typically this is for install or recovery media (DAT
or CD-ROM).
Each boot path (PRI, HAA, ALT) has a boot action that is set through its path flags.
When a hard partition boots to BCH, the BCH interface performs the boot action for each of
the paths, if necessary, in this order: 1) PRI boot action, 2) HAA action, 3) ALT action
= setboot -b on -s off
= setboot -b on -s on)
You can set path flags from the partitions BCH interface or from HP-UX running on the
partition.
HP-UX -- The setboot command affects the local partitions PRI boot actions only.
Golden Profile
- Copies of the complex profile are saved on both the MP and on the cell boards.
- If copies of the profile do not match, between cells and the MP, the golden copy is
used to update all entities.
- The golden copy will always be on the MP, unless the MP has been replaced or has just
lost its copy.
- Cell boards may supply the golden copy back to a MP if each cell board in the complex
has an identical copy.
- If the MP does not contain a valid copy of the profile and the profile
checksums dont match on the cells its time to rebuild!!!
nPartitions
Overview
Complex
ProfileC data
nPartitions
Overview
Complex
Profile Group
Group C Data
# parcreate -c 0:base:y:ri
# parmodify -p1 -a 3:base:y:ri
# parmodify -p1 -d 3
# parmodify p0 m 4:base:n:ri
# parremove -F -p1
The target nPartition can be a remote nPartition in the local complex, such
as when adding a cell to another nPartition in the server.
Modify cell 6 to be inactive (not used) the next time the nPartition is booted:
parmodify -p2 -m6::n::0GB
Cell 6 is assigned to nPartition 2 (-p2) and now has a n use-on-next-boot
setting and no CLM.
The type and failure-usage are the defaults because they were not explicitly
specified..
nPartition Administration
Example: CLM Configurations
To modify the cell local memory (CLM) value for a cell assigned to an
nPartition:
parmodify -p0 -m0/1::::4GB
This modifies cell 0/1 (cabinet 0, cell 1) to have a requested CLM amount of 4
GBytes. This cell already was assigned to nPartition 0 (-p0). The new CLM
value is used the next time nPartition 0 boots.
To create a new nPartition:
parcreate -P MyNpar -L 50% -c1/0::: -c1/1::: -c1/2::::100% -c1/3::::100%
This creates a new nPartition with four cells (1/01/3). The cells 1/0 and 1/1 are
assigned a 50% CLM value (the default CLM specified by -L) and cells 1/2 and
1/3 are assigned 100% CLM.