HP BL10e HP ProLiant BL e-Class Integrated Administrator User Guide - Page 177

Configuring Server Blade Boot Order, SET BAY BOOT ONCE [HDD | PXE | RBSU] [ALL | <bay number&gt

Page 177 highlights

Performing Advanced Functions Configuring Server Blade Boot Order Enclosure and group administrators may change the boot order, sometimes referred to as Initial Program Load (IPL), of their server blades by using the CLI of the Integrated Administrator. The change can be made permanently or only for the next reboot. Several commands are available in the CLI to control the blades in this manner. This feature requires version 1.20 or higher of the Integrated Administrator firmware and a blade ROM dated 06/15/02 or newer to be controlled in this manner. To set a server blade boot order, enter: SET BAY BOOT FIRST [HDD | PXE] [ALL | {[,|-] }] During the next reboot, this will set the specified server blade boot order to use the given boot device first. This has the same effect as changing the Standard Boot Order (IPL) setting in the RBSU on the server blade. To set a server blade boot order for the next boot only, enter: SET BAY BOOT ONCE [HDD | PXE | RBSU] [ALL | {[,|-] }] This will force the specified server blade to boot to the specified media on the next boot only. The RBSU setting will make the server(s) boot into the RBSU which can be viewed with the Remote Console functionality. The HDD setting forces the server blade to boot from the hard drive first, and the PXE setting forces it to boot from the integrated NIC first. To reset blade boot order settings which have not yet taken effect, enter: CLEAR BAY BOOT [FIRST | ONCE] [ALL | {[,|-] }] This will clear changes to the specified server boot order that were made with the SET BAY BOOT command. It only affects pending changes so if the server blade has been rebooted since the SET BAY BOOT command, this command will have no effect. HP ProLiant BL e-Class Integrated Administrator User Guide 7-7

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228

Performing Advanced Functions
Configuring Server Blade Boot Order
Enclosure and group administrators may change the boot order, sometimes referred
to as Initial Program Load (IPL), of their server blades by using the CLI of the
Integrated Administrator. The change can be made permanently or only for the next
reboot. Several commands are available in the CLI to control the blades in this
manner. This feature requires version 1.20 or higher of the Integrated Administrator
firmware and a blade ROM dated 06/15/02 or newer to be controlled in this manner.
To set a server blade boot order, enter:
SET BAY BOOT FIRST [HDD | PXE] [ALL | <bay number> {[,|-]
<bay number>}]
During the next reboot, this will set the specified server blade boot order to use the
given boot device first. This has the same effect as changing the Standard Boot Order
(IPL) setting in the RBSU on the server blade.
To set a server blade boot order for the next boot only, enter:
SET BAY BOOT ONCE [HDD | PXE | RBSU] [ALL | <bay number>
{[,|-] <bay number>}]
This will force the specified server blade to boot to the specified media on the next
boot only. The RBSU setting will make the server(s) boot into the RBSU which can
be viewed with the Remote Console functionality. The HDD setting forces the server
blade to boot from the hard drive first, and the PXE setting forces it to boot from the
integrated NIC first.
To reset blade boot order settings which have not yet taken effect, enter:
CLEAR BAY BOOT [FIRST | ONCE] [ALL | <bay number> {[,|-]
<bay number>}]
This will clear changes to the specified server boot order that were made with the
SET BAY BOOT
command. It only affects pending changes so if the server blade has
been rebooted since the
SET BAY BOOT
command, this command will have no
effect.
HP ProLiant BL e-Class Integrated Administrator User Guide
7-7