Dell Brocade G620 Brocade 8.0.1 Fabric OS Troubleshooting and Diagnostics Guid - Page 24

Switch message logs, two sets of logs.

Get Dell Brocade G620 PDF manuals and user guides View all Dell Brocade G620 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 24 highlights

General Troubleshooting Symptom Probable cause and recommended action Frames are being dropped. Frames are timing out. Viewing frames ∙ Connect to the switch and log in using an account with admin permissions. ∙ Enter the framelog --show command. Switch message logs Switch message logs (RAS logs) contain information on events that happen on the switch or in the fabric. This is an effective tool in understanding what is going on in your fabric or on your switch. RAS logs are independent on director class switches. Weekly review of the RAS logs is necessary to prevent minor problems from becoming larger issues, or in catching problems at an early stage. There are two sets of logs. The ipAddrShow command provides the IP addresses of the CP0 and CP1 control processor blades and associated RAS logs. The following common problems can occur with or in your system message log. Symptom Probable cause and recommended action Inaccurate information in the system message log. In rare instances, events gathered by the Track Change feature can report inaccurate information to the system message log. For example, a user enters a correct user name and password, but the login was rejected because the maximum number of users had been reached. However, when looking at the system message log, the login was reported as successful. If the maximum number of switch users has been reached, the switch still performs correctly, in that it rejects the login of additional users, even if they enter the correct user name and password information. However, in this limited example, the Track Change feature reports this event inaccurately to the system message log; it appears that the login was successful. This scenario only occurs when the maximum number of users has been reached; otherwise, the login information displayed in the system message log reflects reality. Refer to the Fabric OS Administrator's Guide for information regarding enabling and disabling Track Changes (TC). Symptom Probable cause and recommended action MQ errors are appearing in the switch log. An MQ error is a message queue error. Identify an MQ error message by looking for the two letters MQ followed by a number in the error message: 2004/08/24-10:04:42, [MQ-1004], 218,, ERROR, ras007, mqRead, queue = raslog-test- string0123456raslog, queue I D = 1, type = 2 MQ errors can result in devices dropping from the switch's Name Server or can prevent a switch from joining the fabric. MQ errors are rare and difficult to troubleshoot; resolve them by working with the switch supplier. When encountering an MQ error, issue the supportSave command to capture debug information about the switch; then, forward the supportSave data to the switch supplier for further investigation. Brocade Fabric OS Troubleshooting and Diagnostics Guide 24 53-1004126-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
Symptom
Frames are being dropped.
Probable cause and recommended action
Frames are timing out.
Viewing frames
∙
Connect to the switch and log in using an account with admin
permissions.
∙
Enter the
framelog --show
command.
Switch message logs
Switch message logs (RAS logs) contain information on events that happen on the switch or in the fabric. This is an effective tool in
understanding what is going on in your fabric or on your switch. RAS logs are independent on director class switches. Weekly review of
the RAS logs is necessary to prevent minor problems from becoming larger issues, or in catching problems at an early stage. There are
two sets of logs. The
ipAddrShow
command provides the IP addresses of the CP0 and CP1 control processor blades and associated
RAS logs.
The following common problems can occur with or in your system message log.
Symptom
Inaccurate information in the system message log.
Probable cause and recommended action
In rare instances, events gathered by the Track Change feature can report
inaccurate information to the system message log.
For example, a user enters a correct user name and password, but the
login was rejected because the maximum number of users had been
reached. However, when looking at the system message log, the login was
reported as successful.
If the maximum number of switch users has been reached, the switch still
performs correctly, in that it rejects the login of additional users, even if
they enter the correct user name and password information.
However, in this limited example, the Track Change feature reports this
event inaccurately to the system message log; it appears that the login
was successful. This scenario only occurs when the maximum number of
users has been reached; otherwise, the login information displayed in the
system message log reflects reality.
Refer to the
Fabric OS Administrator’s Guide
for information regarding
enabling and disabling Track Changes (TC).
Symptom
MQ errors are appearing in the switch log.
Probable cause and recommended action
An MQ error is a message queue error. Identify an MQ error message by
looking for the two letters MQ followed by a number in the error message:
2004/08/24-10:04:42, [MQ-1004], 218,, ERROR,
ras007, mqRead, queue = raslog-test- string0123456-
raslog, queue I
D = 1, type = 2
MQ errors can result in devices dropping from the switch’s Name Server
or can prevent a switch from joining the fabric. MQ errors are rare and
difficult to troubleshoot; resolve them by working with the switch supplier.
When encountering an MQ error, issue the
supportSave
command to
capture debug information about the switch; then, forward the
supportSave
data to the switch supplier for further investigation.
General Troubleshooting
Brocade Fabric OS Troubleshooting and Diagnostics Guide
24
53-1004126-01