Device alarms "PHY chip abnormal"

Publication Date:  2013-08-30 Views:  1145 Downloads:  0
Issue Description
Customer reports the following alarms on device:

<S05_HW_BKR_PB_SUR>
Aug 13 2013 14:01:39-06:00 S05_HW_BKR_PB_SUR SRM/3/ENTITYINVALID:OID 1.3.6.1.4.1.2011.5.25.129.2.1.9 PHY chip abnormal.(EntityPhysicalIndex=67108873, BaseTrapSeverity=3, BaseTrapProbableCause=67861, BaseTrapEventType=5, EntPhysicalContainedIn=5, EntPhysicalName=MPU Board 0, RelativeResource=PHY chip, ReasonDescription=PHY chip is abnormal.)
Aug 13 2013 14:01:39-06:00 S05_HW_BKR_PB_SUR SRM/3/ENTITYINVALID:OID 1.3.6.1.4.1.2011.5.25.129.2.1.9 PHY chip abnormal.(EntityPhysicalIndex=67108873, BaseTrapSeverity=3, BaseTrapProbableCause=67861, BaseTrapEventType=5, EntPhysicalContainedIn=5, EntPhysicalName=MPU Board 0, RelativeResource=PHY chip, ReasonDescription=PHY chip is abnormal.)
Aug 13 2013 14:01:39-06:00 S05_HW_BKR_PB_SUR SRM/3/ENTITYINVALID:OID 1.3.6.1.4.1.2011.5.25.129.2.1.9 PHY chip abnormal.(EntityPhysicalIndex=67108873, BaseTrapSeverity=3, BaseTrapProbableCause=67861, BaseTrapEventType=5, EntPhysicalContainedIn=5, EntPhysicalName=MPU Board 0, RelativeResource=PHY chip, ReasonDescription=PHY chip is abnormal.)
Aug 13 2013 14:01:38-06:00 S05_HW_BKR_PB_SUR %%01HSC/3/PHYEXC(l)[5]:Detect abnormity on the PHY chip of the master SCU .
Aug 13 2013 14:01:39-06:00 S05_HW_BKR_PB_SUR %%01HSC/3/PHYEXC(l)[6]:Detect abnormity on the PHY chip of the master SCU .
Aug 13 2013 14:01:39-06:00 S05_HW_BKR_PB_SUR %%01HSC/3/PHYEXC(l)[7]:Detect abnormity on the PHY chip of the master SCU .
Aug 13 2013 14:01:39-06:00 S05_HW_BKR_PB_SUR %%01HSC/3/PHYEXC(l)[8]:Detect abnormity on the PHY chip of the master SCU .
Alarm Information
According to device documentation, the alarms refer to a physical issue with device, and there is a procedure to follow to confirm.

Alarm: PHYEXC
Detail: Detect abnormity on the PHY chip of the master SCU .



Handling Process
This is the process that we have advised to customer:

1. Please verify that the device and its interfaces send and receive packets normally.

(a) If NO, this means that the PHY chip has failed, In this case the device needs to be replaced.

(b) If the traffic is OK, there is no need to replace.

2.   Run the reboot command to restart the device, and check the board status with display device, and check if the alarms still appear.

If the alarm is still showed, the device needs to be replaced.
Root Cause
None
Suggestions
Customer has rebooted device and the alarms are deleted, also they do not appear again.

END