Dell Brocade Adapters Brocade Adapters Installation and Reference Manual - Page 155

Boot over SAN

Page 155 highlights

Boot over SAN 4 NOTE For details on using BCU commands, refer to instructions for ethboot in the Brocade Command Utility appendix of the Brocade Adapters Administrator's Guide. Boot over SAN The "Boot Over SAN" feature allows a host to boot its operating system from a boot device directly attached to the host system or located somewhere on the SAN instead of the host's local disk. Specifically, this "boot device" is a logical unit number (LUN) located on a storage device. LUNs can be specifically targeted to boot hosts running Windows, Linux, or VMware, or Solaris. For more information on how the Brocade Boot BIOS functions to implement this feature, refer to "Brocade BIOS support for boot over SAN" on page 128. Booting from a remote SAN location provides the obvious advantage of recovering quickly from a host or adapter malfunction. With the adapter boot BIOS enabled for booting over SAN and configured with boot device locations and boot sequences, replacing an old host with a new one involves installing the adapter from the old host into the new one with the same configuration, then booting the new host. The host's operating system automatically boots from the remote SAN boot device. Although fast recovery from a malfunction is a big advantage, following are considerations for the host and adapter, depending on the replacement situation: • Even though you install a similar host, the new host may require unique System BIOS options and other settings, or internal IDE drives may need to be disconnected or disabled to boot over SAN. • If replacing the Brocade adapter in a host with a similar Brocade adapter, you will need to reconfigure the adapter and storage to boot from the appropriate remote boot device. You must also update access on storage device ports to reflect the adapter PWWN. Finally, you must update the single-initiator target zone created for the adapter port and storage device port with the new adapter PWWN. • If replacing a host with a different model, you may be prompted to install the adapter driver for the existing adapter. Booting servers from SAN-attached storage can significantly streamline server administration and facilitate server deployment. Instead of manually configuring each individual server, boot images on SAN-attached storage can be cloned and assigned to groups of servers at the same time. This not only simplifies initial configuration, but makes ongoing software updates and maintenance much easier to administer. When boot images are centrally managed on the SAN, server security, integrity, and ability to recover data are also enhanced. Following are additional benefits of boot over SAN: • Eliminating the requirement for local hard drives. • Centralized storage management and administration of client workstations. • Disaster recovery. • More control and efficiency for software distribution. • Increased host reliability since operating system boots from highly available storage devices. • Improved security. Brocade Adapters Installation and Reference Manual 127 53-1002144-01

  • 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
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272

Brocade Adapters Installation and Reference Manual
127
53-1002144-01
Boot over SAN
4
NOTE
For details on using BCU commands, refer to instructions for ethboot in the Brocade Command Utility
appendix of the
Brocade Adapters Administrator’s Guide
.
Boot over SAN
The “Boot Over SAN” feature allows a host to boot its operating system from a boot device directly
attached to the host system or located somewhere on the SAN instead of the host’s local disk.
Specifically, this “boot device” is a logical unit number (LUN) located on a storage device. LUNs can
be specifically targeted to boot hosts running Windows, Linux, or VMware, or Solaris. For more
information on how the Brocade Boot BIOS functions to implement this feature, refer to
“Brocade
BIOS support for boot over SAN”
on page 128.
Booting from a remote SAN location provides the obvious advantage of recovering quickly from a
host or adapter malfunction. With the adapter boot BIOS enabled for booting over SAN and
configured with boot device locations and boot sequences, replacing an old host with a new one
involves installing the adapter from the old host into the new one with the same configuration, then
booting the new host. The host’s operating system automatically boots from the remote SAN boot
device.
Although fast recovery from a malfunction is a big advantage, following are considerations for the
host and adapter, depending on the replacement situation:
Even though you install a similar host, the new host may require unique System BIOS options
and other settings, or internal IDE drives may need to be disconnected or disabled to boot over
SAN.
If replacing the Brocade adapter in a host with a similar Brocade adapter, you will need to
reconfigure the adapter and storage to boot from the appropriate remote boot device. You
must also update access on storage device ports to reflect the adapter PWWN. Finally, you
must update the single-initiator target zone created for the adapter port and storage device
port with the new adapter PWWN.
If replacing a host with a different model, you may be prompted to install the adapter driver for
the existing adapter.
Booting servers from SAN-attached storage can significantly streamline server administration and
facilitate server deployment. Instead of manually configuring each individual server, boot images
on SAN-attached storage can be cloned and assigned to groups of servers at the same time. This
not only simplifies initial configuration, but makes ongoing software updates and maintenance
much easier to administer. When boot images are centrally managed on the SAN, server security,
integrity, and ability to recover data are also enhanced.
Following are additional benefits of boot over SAN:
Eliminating the requirement for local hard drives.
Centralized storage management and administration of client workstations.
Disaster recovery.
More control and efficiency for software distribution.
Increased host reliability since operating system boots from highly available storage devices.
Improved security.