When our TNV3E224 installed in OSN9800 U32E raised MOD_COM_FAIL alarm, and how we found the alarm reason.
The Problem description
-As we expanded our OSN9800-U32E with new V3E224, and then installed the SFP and SFP+ in the board ports, According to the Documents the board supports 25G in ports 9 to 24 and 10G in all ports 1 to 24 but 1G optical or electrical in the ports from 13 to 24.
– After inserting for transceivers, a critical alarm raised (MOD_COM_FAIL), the alarm location was the board, not a specific port and the alarm parameter was (20 Alarm Parameter II(hex) 0x14 0x14 0x02).
The process
– Initially I get to the alarm details and handling process then to the NCE information center, the alarm raises when the communication between the CPU and other internal modules of the board is abnormal.
According to the table below of the alarm parameters the value (0x14 0x14 0x02), indicates that the alarm is related to SFP not XFP.
Also the Possible Causes
Cause 1: The board is in poor contact with the connector of the optical module.
Cause 2: The software processing of the optical module on the board is faulty.
Cause 3: The board or optical module is faulty.
-According to the causes, I asked the onsite personnel to check the Transceivers are inserted correctly and fixed, Next I asked him to re-plug the board, after that I checked the installed SFP and XFP in the board in the NCE, the inserted transceivers are all optical, but one of them appeared in the (Ethernet Interface) as Electrical in the port no. 24 and no information in the Board (Manufacturer Information).
After checking the SFP, we found it faulty, and it wasn’t related to the project, actually it was bought from other vendor.
The Solution
-After replacing the SFP with other new one, the alarm cleared.
-After that, I made a recommendation not to use other vendors SFP,XFP,CFP other than the Genuine which are related to the project.
Comments are closed