HP Integrity rx2800 Installation Guide, Windows Server 2008 R2 v7.0 - Page 85

nPartition Boot Phase, Choosing a Management Tool, EFI Boot Manager and EFI Shell

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 85 highlights

I/O discovery, and discovery of interconnecting fabric (connections between the cell and other cells, I/O, and system crossbars). 3. The firmware completes self-tests and discovery, reports the hardware configuration of the cell to the management processor (MP), informs the MP that the cell is "waiting at BIB," and then waits for the cell BIB flag to be cleared. nPartition Boot Phase After its cells have completed their self-tests, the nPartition is booted. The nPartition rendezvous occurs during this phase. Not all cells assigned to the nPartition need to participate in the rendezvous. Only one core-capable cell that has completed its cell boot phase is needed for the nPartition boot phase to begin. By default, all cells assigned to the nPartition that have a "y" use-on-next-boot value are expected to participate in rendezvous. The MP waits for up to 10 minutes for such cells to reach the waiting at BIB state. Cells that have a "n" use-on-next-boot value do not participate in rendezvous and remain waiting at BIB. The main steps that occur during the nPartition boot phase are as follows: 1. The MP provides a copy of the relevant Complex Profile data to the cells assigned to the nPartition. This data includes a copy of the Stable Complex Configuration Data and a copy of the Partition Configuration Data for the nPartition. The Complex Profile represents the configurable aspects of a server complex. The Stable Complex Configuration Data contains complex-wide configuration details and the Partition Configuration Data contains details specific to the nPartition. For more information, see the HP System Partitions Guide. 2. The management processor releases BIB for cells assigned to the nPartition that have a "y" use-on-next-boot value and complete the cell boot phase in time. The management processor does not release BIB for any cell with an "n" use-on-next-boot value or for any cell that did not complete the cell boot phase within 10 minutes of the first cell to do so. When BIB is released for a cell, the cell is considered to be active. 3. The nPartition rendezvous begins, with the system firmware on each active cell using its copy of complex profile data to contact other active cells in the nPartition. 4. The active cells in the nPartition negotiate to select a core cell. 5. The chosen core cell manages the rest of the nPartition boot process. A processor on the core cell runs the nPartition system boot environment (EFI). The core cell hands off control to an operating system loader when the OS boot process is initiated. Choosing a Management Tool You can manage nPartitions using the following tools: Partition Manager Partition Manager provides a graphical interface for managing nPartitions. You can run Partition Manager on the complex, or on management stations used to remotely manage the complex. nPartition commands You can manage nPartitions using commands such as parcreate, parmodify, parremove, parstatus, parunlock, fruled, frupower, and cplxmodify. As with Partition Manager, you can run nPar commands on the complex nPartitions or from a management station used to remotely manage the complex. Also, you must set the admin IP address for nPartitions using the nPar commands. This cannot be done with any other tool. EFI Boot Manager and EFI Shell commands EFI provides support for nPartition management. The EFI interfaces are accessible from an nPartition console when the nPartition is in an active state but has not booted an OS. Choosing a Management Tool 85

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
I/O discovery, and discovery of interconnecting fabric (connections between the cell and
other cells, I/O, and system crossbars).
3.
The firmware completes self-tests and discovery, reports the hardware configuration of the
cell to the management processor (MP), informs the MP that the cell is “waiting at BIB,” and
then waits for the cell BIB flag to be cleared.
nPartition Boot Phase
After its cells have completed their self-tests, the nPartition is booted. The nPartition rendezvous
occurs during this phase. Not all cells assigned to the nPartition need to participate in the
rendezvous. Only one core-capable cell that has completed its cell boot phase is needed for the
nPartition boot phase to begin.
By default, all cells assigned to the nPartition that have a “y” use-on-next-boot value are expected
to participate in rendezvous. The MP waits for up to 10 minutes for such cells to reach the waiting
at BIB state. Cells that have a “n” use-on-next-boot value do not participate in rendezvous and
remain waiting at BIB.
The main steps that occur during the nPartition boot phase are as follows:
1.
The MP provides a copy of the relevant Complex Profile data to the cells assigned to the
nPartition. This data includes a copy of the Stable Complex Configuration Data and a copy
of the Partition Configuration Data for the nPartition.
The Complex Profile represents the configurable aspects of a server complex. The Stable
Complex Configuration Data contains complex-wide configuration details and the Partition
Configuration Data contains details specific to the nPartition. For more information, see the
HP System Partitions Guide
.
2.
The management processor releases BIB for cells assigned to the nPartition that have a “y”
use-on-next-boot value and complete the cell boot phase in time. The management processor
does not release BIB for any cell with an “n” use-on-next-boot value or for any cell that did
not complete the cell boot phase within 10 minutes of the first cell to do so. When BIB is
released for a cell, the cell is considered to be active.
3.
The nPartition rendezvous begins, with the system firmware on each active cell using its
copy of complex profile data to contact other active cells in the nPartition.
4.
The active cells in the nPartition negotiate to select a core cell.
5.
The chosen core cell manages the rest of the nPartition boot process. A processor on the core
cell runs the nPartition system boot environment (EFI). The core cell hands off control to an
operating system loader when the OS boot process is initiated.
Choosing a Management Tool
You can manage nPartitions using the following tools:
Partition Manager
Partition Manager provides a graphical interface for
managing nPartitions. You can run Partition Manager on
the complex, or on management stations used to remotely
manage the complex.
nPartition commands
You can manage nPartitions using commands such as
parcreate
,
parmodify
,
parremove
,
parstatus
,
parunlock
,
fruled
,
frupower
, and
cplxmodify
. As
with Partition Manager, you can run nPar commands on
the complex nPartitions or from a management station
used to remotely manage the complex. Also, you must set
the admin IP address for nPartitions using the nPar
commands. This cannot be done with any other tool.
EFI Boot Manager and EFI Shell
commands
EFI provides support for nPartition management. The EFI
interfaces are accessible from an nPartition console when
the nPartition is in an active state but has not booted an
OS.
Choosing a Management Tool
85