Symptom
ASR9K LC NP lockup -
prm_server_to[141]: %PLATFORM-NP-3-DIAG : NP-DIAG failure on NP0, ICFD
pfm_node_lc[217]: %PLATFORM-NP-2-NP_DIAG : Set|prm_server_to[5334]|0x1008000| NP diagnostics warning on NP0.
prm_server_to[141]: %PLATFORM-NP-0-LC_RELOAD : Failed fast reset recovery on NP, initiate LC reboot
,or -
prm_server_to[174]: %PLATFORM-NP-3-COLLISION : NP error, memory collision detected on NP0, ColMemId: 2, Client: 38, bValid: 1, uiBaseAddress: 0x19c7600, uiRange: 0x22f400, uiLogicalAddress: 0x76fcff2b, uiPhysicalAddress: 0x1e700a1, uiClientSubType: 2, uiSize: 1, eCmdType: 1, bCollision: 1, bSotEotMismatch: 0, bIncorrectSize: 0, uiClientDa ta: 0x0, uiRequestType: 0
prm_server_to[174]: %PLATFORM-NP-3-DIAG : NP-DIAG failure on NP0, ICFD
pfm_node_lc[279]: %PLATFORM-NP-0-MEMORY_COLLISION_ERROR : Set|prm_server_to[4593]|0x1008000| An NP memory collision error has been detected on NP0. The linecard will be rebooted.
In some cases the fast reset recovers the NP and the LC reload is avoided.
Conditions
Entropy label is enabled in the router configuration.
MPLS netflow is enabled ingress on an interface. The interface receives MPLS frames with invalid EL/ELI labels.
Further Problem Description
Npdatalog will show 115 packets in OCFDQ indicating a TM lockup.
It may provide PARSE_DROP_ING_MPLS_LABEL_INVALID as a unique counter increased before the lockup.
