DFE f/w 5.41.25+ with Extra "GBIC indicated TX Fault." Error Messages

[FAQ_User]

Article ID: 10385

Products
Matrix N-Series DFE, firmware 5.41.25 through 6.02.05.0001
7G4280-19, 7GR4280-19
7G-6MGBIC, 7G-6MGBIC-A, 7G-6MGBIC-B
7K-2XFP-6MGBIC
7S-DSNSA7-01, 7S-DSNSA7-01NPS

Symptoms
CLI, Syslog, '

code:

show logging buffer

', or Fault Logs (5101) display error messages similiar to:

<

code:

165

>

code:

May 1 12:58:00 10.26.156.22 System[3]GBIC 12 indicated TX Fault.

<

code:

165

>

code:

May 1 12:57:48 10.26.156.22 System[3]GBIC 25 indicated TX Fault.

<

code:

165

>

code:

May 1 12:57:49 10.26.156.22 System[3]GBIC 26 indicated TX Fault.

Cause
In any circumstance, as described in 7352 there is a defective MGBIC component (here, for port #12 in slot 3) associated with the designated host blade or installed uplink.

However, in such a scenario a firmware bug displays additional invalid messages for MGBICs which may or may not exist.

That is, a fault on one MGBIC yields error messages for three ports: one valid and two invalid. The invalid port numbers will vary based on the installed uplink. Here are the invalid port numbers and the order in which they would be displayed:

• 7G-6MGBIC-B, 7K-2XFP-6MGBIC, or no uplink: #25, #26
• 7G-6MGBIC, 7G-6MGBIC-A: #18, #17
• 7S-DSNSA7-01, 7S-DSNSA7-01NPS: #14, #13

Solution/Workaround
Replace the defective MGBIC.

The invalid error messages are corrected with firmware 6.11.01.0040 and higher.
Release notes state, in the '

code:

Firmware Changes and Enhancements

' section:

code:

7GR4280-19 and 7G4280-19 cards may report GBIC TX faults for invalid GBIC numbers. This occurs when a valid GBIC TX Fault syslog message is logged. The invalid GBIC numbers displayed depend on the NEM type installed; With Security modules invalid GBIC #14 and #13 are displayed, 7G-6MGBIC and 7G-6MGBIC-A: #18, #17 7G-6MGBIC-B and 7K-2XFP-6MGBIC or no uplink: #25, #26

Pre-upgrade workaround:
After replacing the defective MGBIC, the true error message and two invalid error messages should stop. If the invalid MGBIC ports do exist, assume that they are operating properly unless the error messages persist in the absence of messages for other ports.