40
Diagnostics and troubleshooting
NOTE:
This can be caused by merging two fabrics whose active zone sets have two zones with the
same name, but different membership.
Excessive port errors
The switch can monitor a set of port errors and generate alarms based on user-defined sample windows
and thresholds. These port errors include the following:
•
CRC errors
•
Decode errors
•
ISL connection count
•
Excessive device logins
•
Excessive device logouts
•
Loss-of-signal errors
Port threshold alarm monitoring is disabled by default. See the
McDATA 4Gb SAN Switch for HP p-Class
BladeSystem user guide
for information about managing port threshold alarms.
If the count for any of these errors exceeds the rising trigger for three consecutive sample windows, the
switch generates an alarm and disables the affected port, changing its operational state to “down”. Port
errors can be caused by the following:
•
Triggers are too low or the sample window is too small
•
Faulty FC port cable
•
Faulty SFP
•
Faulty port
•
Fault device or HBA
Review the event browser to determine if excessive port errors are responsible for disabling the port. Look
for a message that mentions one of the monitored error types indicating that the port has been disabled,
then perform the following procedure:
1.
Examine the alarm configuration for the associated error using the CLI and
Show Config Threshold
command or the McDATA Web Server application. Are the thresholds
and sample window correct?
• Yes — continue
• No — correct the alarm configuration. If the condition remains, continue.
2.
Reset the port, then perform an external port loopback test to validate the port and the SFP. See the
McDATA 4Gb SAN Switch for HP p-Class BladeSystem user guide
for information about testing ports.
Does the port pass the test?
• Yes — continue
• No — replace the SFP and repeat the test. If the port does not pass the test, contact your authorized
maintenance provider. Otherwise continue.
3.
Replace the FC port cable. Is the problem corrected?
• Yes — complete.
• No — continue.
4.
Inspect the device to which the affected port is connected and confirm that the device is working
properly. Make repairs and corrections as needed. If the condition remains, contact your authorized
maintenance provider.
Summary of Contents for McDATA 4Gb SAN Switch
Page 10: ...10 ...
Page 18: ...18 General description ...
Page 44: ...44 Diagnostics and troubleshooting ...
Page 70: ...70 ...
