HP Neoware e140 Neoware Image Manager 4.6 User Manual - Page 30

Servers List, Using a Cluster of Servers, Technical Notes, SAN, NAS, RAID, SATA, etc.

Page 30 highlights

Overview of Neoware Image Manager Servers List Neoware Image Manager clients use an initialization file that the Image Manager boot loader loads and interprets to determine the server to contact from a list of servers. Neoware Image Manager clients can also use a specific DHCP option (DHCP Option 132) to determine the server to contact from a list of servers. Neoware Image Manager boot loader builds a list of the servers to contact from the initialization file and from DHCP Option 132. If the first server in this list does not answer, the client tries to contact the next server in the list, and so forth. If the client reaches the last server in its list and this server does not answer, it then tries the first server again. You can use Servers List and license files to achieve a form of loadbalancing. A server that has reached the maximum number of clients it can serve will refuse to serve a new client. Then a client that tries to boot off that server will fail and will try the next server. By tuning various different initialization files and/or DHCP options 132 and the license file for each server, you can balance the number of clients that connects to each server in your network. Using a Cluster of Servers Using a cluster of servers that are exposed to the outside world as a single IP address is a very good way to add fast recovery and high availability capabilities to the servers. Technical Notes • If a network cable is unplugged the session will not crash or 'blue-screen'. The desktop will wait for the network to return. • If the server fails, the client waits for the server to reboot. No data will be lost as long as the user does not shut down the client and the files on the server (especially CVol files) are free from error loss. • Neoware Image Manager provides support for various storage options. Hard disk images can be stored on IDE, SCSI, iSCSI, SAN, NAS, RAID, SATA, etc. 14 Technical Notes

  • 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
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406

Overview of Neoware Image Manager
14
Technical Notes
Servers List
Neoware Image Manager clients use an initialization file that the
Image Manager boot loader loads and interprets to determine the
server to contact from a list of servers. Neoware Image Manager cli-
ents can also use a specific DHCP option (DHCP Option 132) to
determine the server to contact from a list of servers.
Neoware Image Manager boot loader builds a list of the servers to
contact from the initialization file and from DHCP Option 132. If the
first server in this list does not answer, the client tries to contact the
next server in the list, and so forth. If the client reaches the last
server in its list and this server does not answer, it then tries the first
server again.
You can use Servers List and license files to achieve a form of load-
balancing. A server that has reached the maximum number of clients
it can serve will refuse to serve a new client. Then a client that tries
to boot off that server will fail and will try the next server.
By tun-
ing various different initialization files and/or DHCP options 132
and the license file for each server, you can balance the number of
clients that connects to each server in your network.
Using a Cluster of
Servers
Using a cluster of servers that are exposed to the outside world as a
single IP address is a very good way to add fast recovery and high
availability capabilities to the servers.
Technical Notes
If a network cable is unplugged the session will not crash or
’blue-screen’. The desktop will wait for the network to return.
If the server fails, the client waits for the server to reboot. No
data will be lost as long as the user does not shut down the client
and the files on the server (especially CVol files) are free from
error loss.
Neoware Image Manager provides support for various storage
options. Hard disk images can be stored on IDE, SCSI, iSCSI,
SAN, NAS, RAID, SATA, etc.