Guest

Preview Tool

Cisco Bug: CSCum07427 - 1X40GE MPA fails when inserted in MOD80 or after MPA type change

Last Modified

Jan 08, 2019

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases

4.2.3.BASE

Description (partial)

Symptom:
A9K-MPA-1X40GE fails when inserted in MOD80 or after MPA swap.

The symptoms vary between the codes:


1. 4.2.3 Symptoms: 

RP/0/RSP0/CPU0:Dec 14 14:37:47.572 UTC: shelfmgr[385]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-1X40GE state:INITIALIZED 
RP/0/RSP0/CPU0:Dec 14 14:37:48.581 UTC: shelfmgr[385]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-1X40GE state:IN-RESET 
RP/0/RSP0/CPU0:Dec 14 14:37:49.245 UTC: invmgr[254]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: FAILED
RP/0/RSP1/CPU0:Dec 14 14:39:58.028 UTC: pfm_node_rp[350]: %PLATFORM-DIAGS-3-PUNT_FABRIC_DATA_PATH_FAILED : Set|online_diag_rsp[233585]|System Punt/Fabric/data Path Test(0x2000004)|failure threshold is 3, (slot, NP) failed: (0/0/CPU0, 0)  
LC/0/0/CPU0:Dec 14 14:40:16.691 UTC: pfm_node_lc[290]: %PLATFORM-DIAGS-0-LC_NP_LOOPBACK_FAILED_TX_PATH : Set|online_diag_lc[172115]|Line card NPU loopback Test(0x2000006)|link failure mask is 0x1. 
RP/0/RSP0/CPU0:Dec 14 14:40:38.556 UTC: pfm_node_rp[350]: %PLATFORM-DIAGS-3-PUNT_FABRIC_DATA_PATH_FAILED : Set|online_diag_rsp[233591]|System Punt/Fabric/data Path Test(0x2000004)|failure threshold is 3, (slot, NP) failed: (0/0/CPU0, 0)

2. 5.1.2 Symptoms:

RP/0/RSP0/CPU0:May 14 11:58:02.576 : shelfmgr[382]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/3/1 UNKNOWN state:UNPOWERED 
RP/0/RSP0/CPU0:May 14 11:58:03.364 : shelfmgr[382]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/3/1 A9K-MPA-1X40GE state:POWER UP 
LC/0/3/CPU0:May 14 11:58:04.187 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 1 type A9K-MPA-1x40GE Initing   
RP/0/RSP0/CPU0:May 14 11:58:18.221 : shelfmgr[382]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/3/1 A9K-MPA-1X40GE state:INITIALIZED 
LC/0/3/CPU0:May 14 11:58:18.743 : prm_server_ty[300]: %PLATFORM-NP-3-IF_OIR_FAILURE : MPA failed OIR  
RP/0/RSP0/CPU0:May 14 11:58:19.225 : invmgr[257]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/3/1, state: FAILED 
RP/0/RSP0/CPU0:May 14 11:58:19.228 : shelfmgr[382]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/3/1 A9K-MPA-1X40GE state:IN-RESET 
LC/0/3/CPU0:May 14 11:58:19.286 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 1 type A9K-MPA-1x40GE Resetting   
RP/0/RSP0/CPU0:May 14 11:58:20.227 : invmgr[257]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/3/1, state: UNPOWERED 
LC/0/3/CPU0:May 14 11:58:24.871 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 1 type A9K-MPA-1x40GE Initing   
LC/0/3/CPU0:May 14 11:58:41.315 : prm_server_ty[300]: %PLATFORM-NP-3-IF_OIR_FAILURE : MPA failed OIR  
RP/0/RSP0/CPU0:May 14 11:58:41.315 : shelfmgr[382]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/3/1 A9K-MPA-1X40GE state:INITIALIZED 
RP/0/RSP0/CPU0:May 14 11:58:42.320 : invmgr[257]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/3/1, state: FAILED 
RP/0/RSP0/CPU0:May 14 11:58:42.323 : shelfmgr[382]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/3/1 A9K-MPA-1X40GE state:IN-RESET 
LC/0/3/CPU0:May 14 11:58:42.382 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 1 type A9K-MPA-1x40GE Resetting   
RP/0/RSP0/CPU0:May 14 11:58:43.322 : invmgr[257]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/3/1, state: UNPOWERED 
LC/0/3/CPU0:May 14 11:58:47.960 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 1 type A9K-MPA-1x40GE Initing   
LC/0/3/CPU0:May 14 11:59:01.791 : prm_server_ty[300]: %PLATFORM-NP-3-IF_OIR_FAILURE : MPA failed OIR  
RP/0/RSP0/CPU0:May 14 11:59:01.791 : shelfmgr[382]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/3/1 A9K-MPA-1X40GE state:INITIALIZED 
RP/0/RSP0/CPU0:May 14 11:59:02.797 : invmgr[257]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/3/1, state: FAILED 
RP/0/RSP0/CPU0:May 14 11:59:02.800 : shelfmgr[382]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/3/1 A9K-MPA-1X40GE state:IN-RESET 

Note: that the NP reset is not seen but the 1x40g EP still fails.

Conditions:
1) Power up the line card with a bay empty.

2) Insert a 1x40 GE ethernet plug in the bay.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.