This document explains the meaning of the "FPC x Voltage Tolerance Exceeded " alarm and also suggests steps to overcome the issue.
Active Alarm:
user@host> show chassis alarms 1 alarm currently active Alarm time Class Description 2020-04-17 09:01:08 UTC Major FPC 2 Voltage Tolerance Exceeded
Log Messages:
Apr 17 09:01:08 2020 craftd[15077]: Major alarm set, FPC 2 Voltage Tolerance Exceeded Apr 17 09:01:08 2020 alarmd[16732]: Alarm set: CB color=RED, class=CHASSIS, reason=FPC 2 Voltage Tolerance Exceeded
Detailed Logs:
Apr 17 09:01:08 2020 craftd[15077]: Major alarm set, FPC 2 Voltage Tolerance Exceeded Apr 17 09:01:08 2020 alarmd[16732]: Alarm set: CB color=RED, class=CHASSIS, reason=FPC 2 Voltage Tolerance Exceeded Apr 17 09:01:22 2020 edge3-la1-re0 craftd[15077]: Major alarm cleared, FPC 2 Voltage Tolerance Exceeded Apr 17 09:18:22 2020 alarmd[16732]: Alarm set: CB color=RED, class=CHASSIS, reason=FPC 2 Voltage Tolerance Exceeded Apr 17 09:18:22 2020 craftd[15077]: Receive FX craftd set alarm message: color: 1 class: 100 object: 143 slot: 2 silent: 0 short_reason=FPC 2 Voltage Failu long_reason=FPC 2 Voltage Tolerance Exceeded id=1946157711 reason=1946157056 Apr 17 09:18:22 2020 craftd[15077]: Major alarm set, FPC 2 Voltage Tolerance Exceeded Apr 17 09:18:38 2020 alarmd[16732]: Alarm cleared: CB color=RED, class=CHASSIS, reason=FPC 2 Voltage Tolerance Exceeded Apr 17 09:18:38 2020 craftd[15077]: Major alarm cleared, FPC 2 Voltage Tolerance Exceeded
The log messages above indicate an exceeded voltage detection on FPC 2. This major alarm gets triggered when FPC 2 gets an out-of-range reading from the voltage sensor. Also, it indicates voltage failure logs for the specific FRU.
C heck FPC Type:
user@host >show chassis hardware
Hardware inventory: Item Version Part number Serial number Description Chassis XXXXX JNP10008 [MX10008] Midplane REV 12 750-071974 XXXXXXXX Midplane 8 Routing Engine 0 BUILTIN BUILTIN RE X10 Routing Engine 1 BUILTIN BUILTIN RE X10 CB 0 REV 15 750-079562 XXXXXXXX Control Board CB 1 REV 15 750-079562 XXXXXXXX Control Board FPC 0 REV 15 750-084779 XXXXXXXX JNP10K-LC2101
For FPC type " JNP10K-LC2101 " if this alarm is triggered, it does not necessarily indicate an issue with the hardware. The out-of-range sensor value causes by reading the voltage sensor while the sensor is not ready. The alarm is cleared when the software is able to get a correct reading from the sensor later on. In this case, the alarm usually sets and clears on its own and does not require reboot of the FPC. If there is a match to this FPC type, it is most likely the issue is not with the actual hardware. The alarm will self clear on its own. In corner cases when it does not, then you might need to consider the possibility of a hardware fault.
Check FPC state:
user@host> show chassis fpc Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%) Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer 0 Empty 1 Online 52 19 0 16 16 16 3136 18 26 2 Offline ---Bad Voltage---
Restart the FPC:
user@host> request chassis fpc (offline | online | restart) slot slot-number
Here,
user@host> request chassis fpc offline slot 2 user@host> request chassis fpc online slot 2
OR
user@host> request chassis fpc restart slot 2
If this solves the issue, you can ignore the next steps. If the issue still exists, continue on with the following steps.
Collect Host Logs:
Collect LCMD logs:
Apr 17 09:01:06 lcmd[31935]: ALARM [ SET -> Time: Apr 17 09:01:06, Name: FRU FPC 2, Short Reason: FPC 2 Voltage Failure , Long Reason: FPC 2 Voltage Tolerance Exceeded ] Apr 17 09:01:11 lcmd[31935]: Health Debounce 1 [Fru: FPC 2 ID: 1202350500 Desc: VDDQ, voltage] Apr 17 09:01:17 lcmd[31935]: Health Debounce 2 [Fru: FPC 2 ID: 1202350500 Desc: VDDQ, voltage] Apr 17 09:01:22 lcmd[31935]: ALARM [ CLEAR -> Time: Apr 17 09:01:06, Name: FRU FPC 2, Short Reason: FPC 2 Voltage Failure , Long Reason: FPC 2 Voltage Tolerance Exceeded ] Apr 17 09:18:21 lcmd[31935]: ALARM [ SET -> Time: Apr 17 09:18:21, Name: FRU FPC 2, Short Reason: FPC 2 Volta Failure , Long Reason: FPC 2 Voltage Tolerance Exceeded ] Apr 17 09:18:27 lcmd[31935]: Health Debounce 1 [Fru: FPC 2 ID: 1202350500 Desc: VDDQ, voltage] Apr 17 09:18:31 lcmd[31935]: Health Debounce 2 [Fru: FPC 2 ID: 1202350500 Desc: VDDQ, voltage] Apr 17 09:18:36 lcmd[31935]: ALARM [ CLEAR -> Time: Apr 17 09:18:21, Name: FRU FPC 2, Short Reason: FPC 2 Voltage Failure , Long Reason: FPC 2 Voltage Tolerance Exceeded ]
These logs confirm voltage failure on FPC 2.
If the issue still persists post restart of FPC, this could be a possible issue with FPC or the slot. Please contact JTAC for detailed analysis and replacement if needed. Collect the logs below for JTAC:
show log messages
show logs chassisd
VM Host Logs ( procedure above )
LCMD logs ( procedure above)
show chassis fpc detail