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

Hardware Problem Causes Channel Faulty Alarms

Publication Date:  2012-07-27 Views:  52 Downloads:  0
Issue Description
It’s found that there are some alarm records in NE40E like the following:
#May  5 21:40:15 2007 NE40E SRM/1/hwEntityInvalid: OID: 1.3.6.1.4.1.2011.5.25.129.2.1.9  EntityPhysicalIndex: 1  BaseTrapSeverity: 6  BaseTrapProbableCause: 21  BaseTrapEventType: 5  EntPhysicalContainedIn: 1  EntPhysicalName: TSR_HALF frame  RelativeResource: channel  ReasonDescription: SFU 13 is failed, perhaps No.1 channel faulty, entity is detected to be failed!
#May  5 21:40:16 2007 NE40E SRM/4/hwEntityResume: OID: 1.3.6.1.4.1.2011.5.25.129.2.1.10  EntityPhysicalIndex: 1  BaseTrapSeverity: 6  BaseTrapProbableCause: 21  BaseTrapEventType: 5  EntPhysicalContainedIn: 1  EntPhysicalName: TSR_HALF frame  RelativeResource: channel  ReasonDescription: SFU 13 is failed, perhaps No.1 channel faulty, The failed entity is detected to be recovered!
Alarm Information
#May  5 21:40:15 2007 NE40E SRM/1/hwEntityInvalid: OID: 1.3.6.1.4.1.2011.5.25.129.2.1.9  EntityPhysicalIndex: 1  BaseTrapSeverity: 6  BaseTrapProbableCause: 21  BaseTrapEventType: 5  EntPhysicalContainedIn: 1  EntPhysicalName: TSR_HALF frame  RelativeResource: channel  ReasonDescription: SFU 13 is failed, perhaps No.1 channel faulty, entity is detected to be failed!
#May  5 21:40:16 2007 NE40E SRM/4/hwEntityResume: OID: 1.3.6.1.4.1.2011.5.25.129.2.1.10  EntityPhysicalIndex: 1  BaseTrapSeverity: 6  BaseTrapProbableCause: 21  BaseTrapEventType: 5  EntPhysicalContainedIn: 1  EntPhysicalName: TSR_HALF frame  RelativeResource: channel  ReasonDescription: SFU 13 is failed, perhaps No.1 channel faulty, The failed entity is detected to be recovered!
      
Handling Process

First of all, check the service status. The services are not affected by the alarms.
Secondly, connected with Huawei HeadQuarter, collect detailed information, such as topology, device, log, and so on.
At last, it is confirmed from HeadQuarter that this type of Channel Faulty Alarm only comes from the communication channel between master SFU and backup SFU. 

Since every Router has 4 SFUs, the alarm won’t influence any service.
      

Root Cause

The Router uses Transformer Chip in Ethernet interface. The chip performance in NE40E SFU board declines, that influences the signal quality in Ethernet Channel. 

As a result, the receiver will receive some wrong packets. That causes the Channel Faulty Alarms. Since the following packets are right, the alarm will be cleared very soon, in 1 second.
      

Suggestions
Considering the long-time stable running, our suggestion is to replace that SFU board. Due to this SFU is included in the SRU board, we should replace that SRU board. 

END