Dell Brocade G620 Brocade 8.0.1 Fabric OS Administratiors Guide - Page 34

Duplicate Port World Wide Name, Device recovery, High availability of daemon processes

Page 34 highlights

Understanding Fibre Channel Services ∙ Nodes leaving or joining the fabric, such as zoning, powering on or shutting down a device, or zoning changes. NOTE Fabric reconfigurations with no domain change do not cause an RSCN. Duplicate Port World Wide Name According to Fibre Channel standards, the Port World Wide Name (PWWN) of a device cannot overlap with that of another device, thus having duplicate PWWNs within the same fabric is an illegal configuration. If a PWWN conflict occurs with two devices attached to the same domain, Fabric OS handles device login in such a way that only one device may be logged in to the fabric at a time. For more information, refer to Duplicate PWWN handling during device login on page 101. If a PWWN conflict occurs and two duplicate devices are attached to the fabric through different domains, the devices are removed from the Name Server database and a RASlog is generated. Device recovery To recover devices that have been removed from the Name Server database due to duplicate PWWNs, the devices must re-login to the fabric. This is true for any device--for example, a device on an F_Port, NPIV devices, or devices attached to a switch in Access Gateway mode. High availability of daemon processes Starting non-critical daemons is automatic; you cannot configure the startup process. The following sequence of events occurs when a non-critical daemon fails: 1. A RASlog and AUDIT event message are logged. 2. The daemon is automatically started again. 3. If the restart is successful, then another message is sent to RASlog and AUDIT reporting the successful restart status. 4. If the restart fails, another message is sent to RASlog and no further attempts are made to restart the daemon. You can then schedule downtime and reboot the switch at your convenience. The following table lists the daemons that are considered non-critical and are automatically restarted on failure. TABLE 1 Daemons that are automatically restarted Daemon arrd cald raslogd rpcd snmpd npd Description Asynchronous Response Router, which is used to send management data to hosts when the switch is accessed through the APIs (FA API or SMI-S). Common Access Layer daemon, which is used by manageability applications. Reliability, Availability, and Supportability daemon logs error detection, reporting, handling, and presentation of data into a format readable by you and management tools. Remote Procedure Call daemon, which is used by the API (Fabric Access API and SMI-S). Simple Network Management Protocol daemon. Flow Vision daemon. Brocade Fabric OS Administration Guide, 8.0.1 34 53-1004111-02

  • 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
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465
  • 466
  • 467
  • 468
  • 469
  • 470
  • 471
  • 472
  • 473
  • 474
  • 475
  • 476
  • 477
  • 478
  • 479
  • 480
  • 481
  • 482
  • 483
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 493
  • 494
  • 495
  • 496
  • 497
  • 498
  • 499
  • 500
  • 501
  • 502
  • 503
  • 504
  • 505
  • 506
  • 507
  • 508
  • 509
  • 510
  • 511
  • 512
  • 513
  • 514
  • 515
  • 516
  • 517
  • 518
  • 519
  • 520
  • 521
  • 522
  • 523
  • 524
  • 525
  • 526
  • 527
  • 528
  • 529
  • 530
  • 531
  • 532
  • 533
  • 534
  • 535
  • 536
  • 537
  • 538
  • 539
  • 540
  • 541
  • 542
  • 543
  • 544
  • 545
  • 546
  • 547
  • 548
  • 549
  • 550
  • 551

Nodes leaving or joining the fabric, such as zoning, powering on or shutting down a device, or zoning changes.
NOTE
Fabric reconfigurations with no domain change do not cause an RSCN.
Duplicate Port World Wide Name
According to Fibre Channel standards, the Port World Wide Name (PWWN) of a device cannot overlap with that of another device, thus
having duplicate PWWNs within the same fabric is an illegal configuration.
If a PWWN conflict occurs with two devices attached to the same domain, Fabric OS handles device login in such a way that only one
device may be logged in to the fabric at a time. For more information, refer to
Duplicate PWWN handling during device login
on page
101.
If a PWWN conflict occurs and two duplicate devices are attached to the fabric through different domains, the devices are removed from
the Name Server database and a RASlog is generated.
Device recovery
To recover devices that have been removed from the Name Server database due to duplicate PWWNs, the devices must re-login to the
fabric. This is true for any device--for example, a device on an F_Port, NPIV devices, or devices attached to a switch in Access Gateway
mode.
High availability of daemon processes
Starting non-critical daemons is automatic; you cannot configure the startup process. The following sequence of events occurs when a
non-critical daemon fails:
1.
A RASlog and AUDIT event message are logged.
2.
The daemon is automatically started again.
3.
If the restart is successful, then another message is sent to RASlog and AUDIT reporting the successful restart status.
4.
If the restart fails, another message is sent to RASlog and no further attempts are made to restart the daemon. You can then
schedule downtime and reboot the switch at your convenience.
The following table lists the daemons that are considered non-critical and are automatically restarted on failure.
TABLE 1
Daemons that are automatically restarted
Daemon
Description
arrd
Asynchronous Response Router, which is used to send management
data to hosts when the switch is accessed through the APIs (FA API
or SMI-S).
cald
Common Access Layer daemon, which is used by manageability
applications.
raslogd
Reliability, Availability, and Supportability daemon logs error
detection, reporting, handling, and presentation of data into a format
readable by you and management tools.
rpcd
Remote Procedure Call daemon, which is used by the API (Fabric
Access API and SMI-S).
snmpd
Simple Network Management Protocol daemon.
npd
Flow Vision daemon.
Understanding Fibre Channel Services
Brocade Fabric OS Administration Guide, 8.0.1
34
53-1004111-02