Technical data

An Overview of nPartition Boot and Reset
Boot Process for nPartitions, Cells, and HP-UX
HP System Partitions Guide: Administration for nPartitions, rev 5.1 167
Following this, any I/O busses connected to the cell are known and
configured by the cell.
5. Boot-Is-Blocked (BIB) or Partition Rendezvous
Each cell either will remain at a boot-is-blocked state (spins at BIB)
or will rendezvous with any other available cells in the nPartition.
Cells that remain at BIB are inactive, and cells that rendezvous into
the nPartition are active.
• Boot-Is-Blocked (BIB)
A cell remains at boot-is-blocked (and thus is inactive) in any of
the following cases:
— The cell has a “n” use-on-next-boot setting.
— The cell boots too late to participate in nPartition
rendezvous.
— The cell’s nPartition has been reset to the ready for reconfig
state.
In this case, all of the nPartition’s cells remain at
boot-is-blocked.
— The cell fails self-tests that cause the cell to not be usable in
the nPartition.
• Partition Rendezvous
Partition rendezvous of all cells occurs in the following manner:
— Partition rendezvous begins when the first of the nPartition’s
cells has completed self-tests and I/O discovery.
— The nPartition is allowed up to ten minutes for all cells with
a “y” use-on-next-boot setting to participate in partition
rendezvous.
— Once all assigned cells with a “y” use-on-next-boot
setting have entered the rendezvous stage, partition
rendezvous can complete.
All cells participating in rendezvous are active cells
whose resources (processors, memory, I/O) are used by
the nPartition.