Excessive Port Errors
The switch can monitor a set of port errors and generates alarms based on
•CRC errors
•Decode errors
•ISL connection count
•Login errors
•Logout errors
•
Port threshold alarm monitoring is disabled by default. Refer to the McDATA Switch Module Management 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 Fibre Channel 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 do the following:
1.Examine the alarm configuration for the associated error using the Show Config Threshold command or the McDATA Embedded Web Server application. Refer to the McDATA 4416 Command Line Interface Guide for information about this command. 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. Refer to the McDATA Switch Module Management 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.
