HP Integrity rx5670 Windows Integrity nPartition Guide - Page 14

copy of complex profile data to contact other active cells in the nPartition.

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

Page 14 highlights

Introduction Getting to know nPartitions 2. The management processor releases BIB for all 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 a "n" use-on-next-boot value, or for any cell that did not complete the cell boot phase within ten minutes of the first cell to do so. Once BIB is release for a cell, the cell is considered to be active. 3. 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. 14 Chapter 1

  • 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
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
Introduction
Getting to know nPartitions
Chapter 1
14
2.The management processor releases BIB for all 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 a “n” use-on-next-boot
value, or for any cell that did not complete the cell boot phase within ten minutes of
the first cell to do so. Once BIB is release for a cell, the cell is considered to be active.
3.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.