Cisco Bug: CSCvu30991 - Np reset with (PA2REG.ppe_int1) for LSP in debug mode.
Jun 02, 2020
- Cisco ASR 9000 Series Aggregation Services Routers
Known Affected Releases
Symptom: Np reset with (PA2REG.ppe_int1) for LSP and sometime Np reset with FLBFFEREG.FlbFfeWdTimerTimeoutErr is observed while using monitor counter command in debug mode. LC/0/0/CPU0:May 1 14:31:31.426 UTC: npu_server_lsp: %PLATFORM-NP-4-HARD_RESET_START : NP1: Performing recovery action for an internal network processor error. (PA2REG.ppe_int1) LC/0/0/CPU0:May 1 14:31:31.441 UTC: npu_server_lsp: %PLATFORM-NP-3-DIAG : NP-DIAG failure on NP1 LC/0/0/CPU0:May 1 14:33:02.175 UTC: npu_server_lsp: %PLATFORM-NP-4-HARD_RESET_COMPLETE : NP1: Recovery action is successful. Network processor is operational. LC/0/0/CPU0:May 1 14:33:02.395 UTC: npu_server_lsp: %PLATFORM-NP-3-ERROR_MSG : NP1 Datalog created. Dump file saved: /misc/scratch/np/NPdatalog_0_0_CPU0_np1_diagP1_20200501-143131.txt.gz RP/0/RSP0/CPU0:f3a-r1-pod16# Conditions: Switch from prod mode to debug mode on lc .Once the lc is up again then try to use monitor counter command for any np on lc . While doing so np failure will be observed on lc.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases