Cisco DS-C9124-K9 Troubleshooting Guide - Page 121

Analyzing The Logs, Troubleshooting Module Issues, show module internal event-history module

Page 121 highlights

Chapter 4 Troubleshooting Hardware Troubleshooting Switching and Services Modules Send documentation comments to [email protected] • Online health management (OHMS)-Sent from the supervisor to all the ports in the module to verify that traffic is flowing properly. In addition, the module monitors itself and generates an exception if it detects an anomalous condition. If the exception is a FATAL error, the module is power cycled. Use the following CLI commands to view the conditions leading up to the problem: • show logging • show module diag • show module internal exception-log module • show module internal event-history module • show hardware internal errors Analyzing The Logs In some instances, you may need to check other internal logs to verify the cause of a problem. You can use the state transition log and the error log in these instances. These logs may hold information not present in the system messages or in the exception log because of interactions between the module and the supervisor. The state transition log is sorted in ascending manner (that is, the latest state is at the end of the log). The error log is sorted in descending manner (that is, the latest error is at the beginning of the log). Use the show module internal event-history module CLI command to view the state transition log for a module. Use the show module internal event-history errors CLI command to view the error log. The state transition log indicates the current state of a given module. (See Example 4-16.) Each element of the transition log contains the following information: • Timestamp • Node that triggered the state transition • Module state prior to transition • Event that occurred • Current state of module Example 4-16 State Transition Log 7) FSM: Transition at 14258 usecs after Mon Sep 26 17:50:56 2005 Previous state: [LCM_ST_LC_POWERED_UP] Triggered event: [LCM_EV_PFM_LC_STATUS_POWERED_DOWN] Next state: [LCM_ST_LC_NOT_PRESENT] Based on the above state transition you can infer that when the module was in the powered-up state, PFM triggered an event to power down the module. This trigger caused the state machine to go to the not present state. Troubleshooting Module Issues To isolate a module problem, follow these steps: Step 1 Verify that all Status LEDs are green. If any status LED is red or off, the module might have shifted out of its slot. OL-9285-05 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x 4-25

  • 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
  • 552
  • 553
  • 554
  • 555
  • 556
  • 557
  • 558
  • 559
  • 560

Send documentation comments to [email protected]
4-25
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 4
Troubleshooting Hardware
Troubleshooting Switching and Services Modules
Online health management (OHMS)—Sent from the supervisor to all the ports in the module to
verify that traffic is flowing properly.
In addition, the module monitors itself and generates an exception if it detects an anomalous condition.
If the exception is a FATAL error, the module is power cycled. Use the following CLI commands to view
the conditions leading up to the problem:
show logging
show module diag
show module internal exception-log module
show module internal event-history module
show hardware internal errors
Analyzing The Logs
In some instances, you may need to check other internal logs to verify the cause of a problem. You can
use the state transition log and the error log in these instances. These logs may hold information not
present in the system messages or in the exception log because of interactions between the module and
the supervisor. The state transition log is sorted in ascending manner (that is, the latest state is at the end
of the log). The error log is sorted in descending manner (that is, the latest error is at the beginning of
the log).
Use the
show module internal event-history module
CLI command to view the state transition log for
a module. Use the
show module internal event-history errors
CLI command to view the error log.
The state transition log indicates the current state of a given module. (See
Example 4-16
.) Each element
of the transition log contains the following information:
Timestamp
Node that triggered the state transition
Module state prior to transition
Event that occurred
Current state of module
Example 4-16
State Transition Log
7) FSM:<ID(2): Slot 8, node 0x0800> Transition at 14258 usecs after Mon Sep 26 17:50:56
2005
Previous state: [LCM_ST_LC_POWERED_UP]
Triggered event: [LCM_EV_PFM_LC_STATUS_POWERED_DOWN]
Next state: [LCM_ST_LC_NOT_PRESENT]
Based on the above state transition you can infer that when the module was in the
powered-up
state, PFM
triggered an event to power down the module. This trigger caused the state machine to go to the
not
present
state.
Troubleshooting Module Issues
To isolate a module problem, follow these steps:
Step 1
Verify that all Status LEDs are green. If any status LED is red or off, the module might have shifted out
of its slot.