Troubleshooting transceiver modules

Transceiver module issues

Optical interface coming up failure

Symptom

An optical interface installed with a transceiver module cannot come up.

Common causes

·     The current version of the device does not support the transceiver module.

·     The optical interface has foreign objects, or the transceiver module's golden plating has been contaminated or damaged.

·     The transceiver module rate and the interface rate do not match.

·     The optical interface has failed.

·     The transceiver module or cable has failed.

·     The transceiver module and the optical fiber type do not match.

Troubleshooting flow

Figure 1 shows the troubleshooting flowchart.

Figure 1 Flowchart for troubleshooting optical interface coming up failure

 

Solution

1.     Identify whether the device's current version supports the transceiver module.

To identify whether the current software version supports the transceiver module, view the installation guide or release notes for the device. You can upgrade the software version if a new version supports the transceiver module.

2.     Identify whether the rate and duplex mode of the transceiver module match those of the interface.

Execute the display interface command to identify whether the rate and duplex mode of the interface match those of the transceiver module. If they do not match, configure the rate and duplex mode for the interface by using the speed and duplex commands, respectively.

3.     Identify whether the optical interface has failed.

Directly connect the optical interface with another optical interface of the same rate on the device by using a compatible cable (applicable to short-distance connection). Identify whether the interface can come up. If the interface can come up, the peer interface is abnormal. If the interface cannot come up, the local interface is abnormal. Identify whether the issue is resolved by changing the local and peer interfaces.

4.     Identify whether the transceiver module/cable is abnormal.

a.     Execute the display transceiver alarm interface command to view alarms present on the transceiver module in the interface. If the command output displays None, no fault exists. If the command output displays alarms, identify whether the issues lie with the transceiver module, the optical fibers, or the peer end. For example, if the output displays the RX signal loss and TX fault alarms, examine the optical interface and transceiver module for foreign objects or examine the golden plating of the transceiver module for severe oxidation.

b.     Execute the display transceiver interface command to identify whether the type, wavelength, and transmission distance of the transceiver modules on both ends are consistent.

c.     Execute the display transceiver diagnosis interface command to identify whether the current values of the digital diagnosis parameters on the transceiver module are within the normal range. Common issues and solutions for parameter exceptions are as follows:

-     If an optical fiber has poor contact with the transceiver module, firmly insert the optical fiber into the transceiver module.

-     Replace the optical fiber that has poor quality or is damaged.

-     If an intermediate optical attenuation device exists on the transmission path, adjust the optical attenuation device as required.

-     If there is a significant difference between the supported and actual transmission distances of the transceiver module, replace the transceiver module with one that supports the actual transmission distance.

5.     Identify whether the transceiver module type matches the optical fibers.

To identify whether the transceiver module type matches the optical fibers, see H3C Transceiver Modules User Guide. If they do not match, replace the optical fibers.

6.     If the issue persists, collect the following information and contact Technical Support:

¡     Results of each step.

¡     The configuration file, log messages, and alarm messages.

Related alarm and log messages

Alarm messages

N/A

Log messages

OPTMOD/3/CFG_ERR

OPTMOD/5/CHKSUM_ERR

OPTMOD/5/IO_ERR

OPTMOD/4/FIBER_SFPMODULE_INVALID

OPTMOD/4/FIBER_SFPMODULE_NOWINVALID

OPTMOD/5/MOD_ALM_ON

OPTMOD/5/RX_ALM_ON

OPTMOD/5/RX_POW_HIGH

OPTMOD/5/RX_POW_LOW

Transceiver module being not H3C-compliant

Symptom

After you execute the display logbuffer command to view system logs, a log shows that the transceiver module is not H3C-compliant. The log message is as follows:

This transceiver is NOT sold by H3C. H3C  therefore shall NOT guarantee the normal function of the device or  assume the maintenance responsibility thereof!

Common causes

The transceiver module is a third-party or fake transceiver module.

Troubleshooting flow

Figure 2 shows the troubleshooting flowchart.

Figure 2 Flowchart for troubleshooting the issue of transceiver module being not H3C-compliant

 

Solution

1.     Identify whether the transceiver module is from H3C.

a.     Examine the label on the transceiver module.

b.     Execute the display transceiver interface command to identify whether the Vendor Name field displays H3C.

-     If the Vendor Name field displays H3C, the transceiver module might be an H3C transceiver module without an electronic label or might not be an H3C transceiver module. Further confirmation is required.

-     If the Vendor Name field displays other information, the transceiver module is definitely not an H3C transceiver module. Replace it with one from H3C and identify whether the issue is resolved.

c.     Contact H3C Technical Support to identify whether the transceiver module is from H3C.

Execute the display hardware internal transceiver register interface and display transceiver information interface commands in probe view to collect transceiver module information. Then, send the barcode on the transceiver module to H3C Technical Support to confirm whether it is an H3C transceiver module. If the transceiver module is not from H3C, replace it with one from H3C and identify whether the issue is resolved.

2.     If the issue persists, collect the following information and contact Technical Support:

¡     Results of each step.

¡     The log messages and alarm messages.

Related alarm and log messages

Alarm messages

N/A

Log messages

OPTMOD/4/PHONY_MODULE

No support for digital diagnosis

Symptom

After you execute the display transceiver diagnosis interface command, the system prompts that the transceiver module does not support digital diagnosis. The prompt is as follows:

<Sysname> display transceiver diagnosis interface Ten-GigabitEthernet2/0/0

The transceiver does not support this function.

Common causes

·     The transceiver module is not from H3C.

·     The transceiver module does not support digital diagnosis.

·     The transceiver module has failed.

·     The device/optical interface has failed.

Troubleshooting flow

Figure 3 shows the troubleshooting flowchart.

Figure 3 Flowchart for troubleshooting the issue of no support for digital diagnosis

 

Solution

1.     Identify whether the transceiver module is from H3C. For more information, see "Transceiver module being not H3C-compliant."

2.     Execute the display transceiver interface command to identify whether the Digital Diagnostic Monitoring field displays YES.

¡     If it displays YES, the transceiver module supports digital diagnosis.

¡     If it does not display YES, the transceiver module does not support digital diagnosis.

3.     Insert another transceiver module of the same model into another normal interface on the device or into an interface on a device that is operating correctly and supports the transceiver module. Identify whether the system prompts that the transceiver module does not support digital diagnosis.

4.     If the issue persists, collect the following information and contact Technical Support:

¡     Results of each step.

¡     The alarm messages.

Related alarm and log messages

Alarm messages

N/A

Log messages

N/A

Transceiver module serial number loss

Symptom

The transceiver module serial number is found to be lost after you execute the display transceiver manuinfo interface command.

Common causes

·     The transceiver module is not securely inserted into an interface.

·     The transceiver module/device has failed.

Troubleshooting flow

Figure 4 shows the troubleshooting flowchart.

Figure 4 Flowchart for troubleshooting the issue of transceiver module serial number loss

 

Solution

1.     Identify whether the transceiver module is fully inserted into an optical interface.

Securely insert the transceiver module into the optical interface or change the optical interface.

2.     Identify whether the transceiver module has failed.

Insert another transceiver module of the same model into another interface on the device or into an interface on a device that is operating correctly and supports the transceiver module.

3.     If the issue persists, collect the following information and contact Technical Support:

¡     Results of each step.

¡     The alarm messages.

Related alarm and log messages

Alarm messages

N/A

Log messages

N/A