Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, June 2008)

12 Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
Switch Message Logs
2
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 will still perform correctly in
that it will reject 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 will report this event inaccurately to the
system message log; it will appear 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 should reflect reality.
See 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 switches 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.
Symptom I2C bus errors are appearing in the switch log.
Probable cause and recommended action
I
2
C bus errors generally indicate defective hardware or poorly seated devices or blades; the
specific item is listed in the error message. See the Fabric OS Message Reference for information
specific to the error that was received. Some Chip-Port (CPT) and Environmental Monitor (EM)
messages contain I
2
C-related information.
If the I
2
C message does not indicate the specific hardware that may be failing, begin debugging the
hardware, as this is the most likely cause. The next sections provide procedures for debugging the
hardware.
Checking fan components
1. Log in to the switch as user.
2. Enter the fanShow command.