No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Damage of CXPAR board in RTN910 V1R1 after any type of reset if a FE ports reports HARD_BAD alarm

Publication Date:  2012-07-25 Views:  55 Downloads:  0
Issue Description
In OptiX RTN 910 V100R001C02SPC200(5.76.01.33) when the CXPAR board shows HARD_BAD (probably due to a lightning struck  in the system and injected in control board ) with the following parameter : 0x21 0x01 0x01

- 0x21: as FE port problem 
- 0x01, 0x02, 0x03 or 0x04: in last parameter as number of port damaged

, if any kind of reset is performed in the RTN, control board will be broken.




Alarm Information
HARD_BAD

Parameter: 0x21 0x01 0x01

Handling Process
The only way to solve the problem is changing the CXPAR board for a new one.


Root Cause
After a HARD_BAD alarm is reported in the FE ports RTN 910 due to hardware failure sometimes Ethernet service in the reported port pass and sometimes doesn´t. To verify the port following steps were done:

Check if FE port has link:

- After verifying with the UTP cable connected to port it was linking

Ping port to verify service:

- When HARD_BAD is detected in one port, all ports reports the alarm, even if there is no hardware damage in it so ping can pass.

Made a Warm or Hard reset to CXPAR board:

- After reboot, control board verify the BCM5241 Ethernet chip module. If the value is different from 0x143 at the time of making the consistency check, it will fail to start, due to the FE hardware failure and it will check the hardware status continuously and  always getting  a different ID chip value.  In consequence, CXPAR will never start
.


Suggestions
If a HARD_BAD alarm with Parameter: 0x21 0x01 (0x01,0x02,0x03 and 0x04) is reported in the RTN, never performed a reset until the CXPAR board is changed.


END