HP StorageWorks 2/16V Brocade Fabric Manager Administrator's Guide (53-1000019 - Page 352

Wizard Hangs, Performance Monitoring, Incorrect Performance Monitoring Port Statistics

Page 352 highlights

26 Pinpointing Additional Problem Areas You must have access to at least AD0 and the physical fabric on an Admin Domain-aware switch to monitor and manage that switch. Wizard Hangs Occasionally the FC Router Configuration wizard and the Device Connectivity Troubleshooting wizard (device diagnostic wizard) hang due to rendering issues with Java Swing. If this happens, close the wizard by clicking the X button in the upper right-hand corner of the window, and then relaunch the wizard. Relaunch the FC Router Configuration wizard by right-clicking on the edge fabric and selecting FC Router Configuration; relaunch the Device Connectivity Troubleshooting wizard by clicking Tasks>Device Sharing and Troubleshooting>Device Connectivity Troubleshooting (GDD). Performance Monitoring The following problems might happen if you are using performance monitoring. Incorrect Performance Monitoring Port Statistics If you are running a 4.x version of Fabric OS on a switch that is v4.2.0b or lower, the Advanced Performance Monitoring port statistics for the switch are returned incorrectly. You must upgrade the firmware on the 4.x switch to Fabric OS v4.2.0c or higher. Performance Monitoring Configuration Window Hangs If you have manually stopped the Fabric Manager PM Server process and you then try to refresh Endto-End monitors while the Fabric Manager PM Server process is dead, the Performance Monitor configuration window hangs. If this happens, you must manually restart the Fabric Manager PM Server process. Fabric Manager Database File Is Too Large Make sure that you periodically back up the Fabric Manager database so that the file does not get too large. You can back up the database using the Server Management Console. See Chapter 24, "Server Management Console" for instructions. Sequenced Reboot Does Not Show Correct Status If you perform a sequenced reboot on all of the switches in a large fabric at the same time, the Reboot window might not show the status of some of the switches correctly. The Reboot window might show the status of switches as still performing the reboot when the reboot is actually done and you can reach the switches via telnet. 26-14 Fabric Manager Administrator's Guide Publication Number: 53-1000196-01-HP

  • 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

26-14
Fabric Manager Administrator’s Guide
Publication Number: 53-1000196-01-HP
Pinpointing Additional Problem Areas
26
You must have access to at least AD0 and the physical fabric on an Admin Domain-aware switch to
monitor and manage that switch.
Wizard Hangs
Occasionally the FC Router Configuration wizard and the Device Connectivity Troubleshooting wizard
(device diagnostic wizard) hang due to rendering issues with Java Swing. If this happens, close the
wizard by clicking the
X
button in the upper right-hand corner of the window, and then relaunch the
wizard.
Relaunch the FC Router Configuration wizard by right-clicking on the edge fabric and selecting
FC
Router Configuration
; relaunch the Device Connectivity Troubleshooting wizard by clicking
Tasks
>
Device Sharing and Troubleshooting>Device Connectivity Troubleshooting (GDD)
.
Performance Monitoring
The following problems might happen if you are using performance monitoring.
Incorrect Performance Monitoring Port Statistics
If you are running a 4.x version of Fabric OS on a switch that is v4.2.0b or lower, the Advanced
Performance Monitoring port statistics for the switch are returned incorrectly. You must upgrade the
firmware on the 4.x switch to Fabric OS v4.2.0c or higher.
Performance Monitoring Configuration Window Hangs
If you have manually stopped the Fabric Manager PM Server process and you then try to refresh End-
to-End monitors while the Fabric Manager PM Server process is dead, the Performance Monitor
configuration window hangs. If this happens, you must manually restart the Fabric Manager PM Server
process.
Fabric Manager Database File Is Too Large
Make sure that you periodically back up the Fabric Manager database so that the file does not get too
large. You can back up the database using the Server Management Console. See
Chapter 24, “Server
Management Console”
for instructions.
Sequenced Reboot Does Not Show Correct
Status
If you perform a sequenced reboot on all of the switches in a large fabric at the same time, the Reboot
window might not show the status of some of the switches correctly. The Reboot window might show
the status of switches as still performing the reboot when the reboot is actually done and you can reach
the switches via telnet.