Users may find that on MX2000 Series routers with a non-native Modular Port Concentrator Card (MPC) with Adapter Card (ADC), the fru-poweron-sequence configuration knob is not honored. Both ADC and MPC are powered on in ascending order even though fru-poweron-sequence is configured.

This article clarifies that this is a product limitation due to ADC.

 

Example

1. Test-1: fru-poweron-sequence is configured in ascending order. The FPC bring up order (1 -> 3 -> 5 -> 7) is expected.

User@MX2020-re0> show chassis hardware |match fpc
FPC 1            REV 35   750-063414   CAFF1122          MPC9E 3D <-------------native MPC
FPC 3            REV 72   750-044130   ABDB6878          MPC6E 3D <-------------native MPC
FPC 5            REV 39   750-037355   CACR7840          MPC4E 3D 2CGE+8XGE
FPC 7            REV 40   750-031089   CACV3126          MPC Type 2 3D

User@MX2020-re0> show configuration chassis fru-poweron-sequence
fru-poweron-sequence "0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19";

User@MX2020-re0> show chassis power sequence 
Chassis FRU Power On Sequence: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

User@MX2020-re0> request system reboot
Reboot the system ? [yes,no] (no) yes

*** FINAL System shutdown message from User@MX2020-re0 ***

System going down IMMEDIATELY

Nov 25 19:01:06  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC9E 3D @ 1/*/*, jnxFruType 3, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 1589)
Nov 25 19:01:13  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 4, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC6E 3D @ 3/*/*, jnxFruType 3, jnxFruSlot 3, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 2228)
Nov 25 19:03:48  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 23, jnxFruL1Index 6, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName ADC 5, jnxFruType 20, jnxFruSlot 5, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 17754)
Nov 25 19:03:49  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 6, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC4E 3D 2CGE+8XGE @ 5/*/*, jnxFruType 3, jnxFruSlot 5, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 17859)
Nov 25 19:04:05  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 23, jnxFruL1Index 8, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName ADC 7, jnxFruType 20, jnxFruSlot 7, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 19487)
Nov 25 19:04:06  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 8, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC Type 2 3D @ 7/*/*, jnxFruType 3, jnxFruSlot 7, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 19513)
Nov 25 19:05:04  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 2, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName PIC:  @ 1/0/*, jnxFruType 11, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 25384)
Nov 25 19:05:14  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 2, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: MRATE-12xQSFPP-XGE-XLGE-CGE @ 1/0/*, jnxFruType 11, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)
Nov 25 19:06:17  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 8, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName PIC:  @ 7/0/*, jnxFruType 11, jnxFruSlot 7, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 32627)
Nov 25 19:06:17  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 8, jnxFruL2Index 2, jnxFruL3Index 0, jnxFruName PIC:  @ 7/1/*, jnxFruType 11, jnxFruSlot 7, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 32628)
Nov 25 19:06:22  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 8, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: 3D 2x 10GE XFP @ 7/0/*, jnxFruType 11, jnxFruSlot 7, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)
Nov 25 19:06:29  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 4, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName PIC:  @ 3/0/*, jnxFruType 11, jnxFruSlot 3, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 33894)
Nov 25 19:06:39  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 4, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: 24X10GE SFPP @ 3/0/*, jnxFruType 11, jnxFruSlot 3, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)
Nov 25 19:07:46  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 6, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName PIC:  @ 5/0/*, jnxFruType 11, jnxFruSlot 5, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 41513)
Nov 25 19:07:46  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 6, jnxFruL2Index 2, jnxFruL3Index 0, jnxFruName PIC:  @ 5/1/*, jnxFruType 11, jnxFruSlot 5, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 41514)
Nov 25 19:07:46  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 6, jnxFruL2Index 3, jnxFruL3Index 0, jnxFruName PIC:  @ 5/2/*, jnxFruType 11, jnxFruSlot 5, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 41514)
Nov 25 19:07:46  MX2020-re0 chassisd[4456]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 6, jnxFruL2Index 4, jnxFruL3Index 0, jnxFruName PIC:  @ 5/3/*, jnxFruType 11, jnxFruSlot 5, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 41514)

2. Test-2: fru-poweron-sequence is configured in descending order. The FPC bring up order (9->6->5->7->8) is expected.

User@MX2020-re0> show chassis hardware |match fpc
FPC 5            REV 09   750-038492   CAAB1419          MPCE Type 2 3D EQ
FPC 6            REV 81   750-044130   ABDN5588          MPC6E 3D <-----------------native MPC
FPC 7            REV 37   750-054564   CANN7276          MPC5E 3D 2CGE+4XGE
FPC 8            REV 44   750-056519   CAKL9446          MPC7E 3D MRATE-12xQSFPP-XGE-XLGE-CGE
FPC 9            REV 30   750-063414   CAGL2094          MPC9E 3D <-----------------native MPC

User@MX2020-re0> show configuration chassis fru-poweron-sequence
fru-poweron-sequence "19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0";

User@MX2020-re0> show chassis power sequence 
Chassis FRU Power On Sequence: 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

User@MX2020-re0> request system reboot
Reboot the system ? [yes,no] (no) yes

*** FINAL System shutdown message from User@MX2020-re0 ***

System going down IMMEDIATELY

Nov 26 11:50:40  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 10, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC9E 3D @ 9/*/*, jnxFruType 3, jnxFruSlot 9, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 3086)
Nov 26 11:50:48  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 7, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC6E 3D @ 6/*/*, jnxFruType 3, jnxFruSlot 6, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 3801)
Nov 26 11:54:03  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 23, jnxFruL1Index 6, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName ADC 5, jnxFruType 20, jnxFruSlot 5, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 23367)
Nov 26 11:54:05  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 6, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPCE Type 2 3D EQ @ 5/*/*, jnxFruType 3, jnxFruSlot 5, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 23580)
Nov 26 11:54:27  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 23, jnxFruL1Index 8, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName ADC 7, jnxFruType 20, jnxFruSlot 7, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 25796)
Nov 26 11:54:28  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 8, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC5E 3D 2CGE+4XGE @ 7/*/*, jnxFruType 3, jnxFruSlot 7, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 25862)
Nov 26 11:54:53  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 23, jnxFruL1Index 9, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName ADC 8, jnxFruType 20, jnxFruSlot 8, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 28309)
Nov 26 11:54:54  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 9, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC7E 3D MRATE-12xQSFPP-XGE-XLGE-CGE @ 8/*/*, jnxFruType 3, jnxFruSlot 8, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 28427)
Nov 26 11:56:33  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 10, jnxFruL2Index 2, jnxFruL3Index 0, jnxFruName PIC:  @ 9/1/*, jnxFruType 11, jnxFruSlot 9, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 38366)
Nov 26 11:58:07  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 10, jnxFruL2Index 2, jnxFruL3Index 0, jnxFruName MIC: MRATE-12xQSFPP-XGE-XLGE-CGE @ 9/1/*, jnxFruType 11, jnxFruSlot 9, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)
Nov 26 11:58:41  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 7, jnxFruL2Index 2, jnxFruL3Index 0, jnxFruName PIC:  @ 6/1/*, jnxFruType 11, jnxFruSlot 6, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 51136)
Nov 26 11:58:51  MX2020-re0 chassisd[15600]: %DAEMON-5-CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 7, jnxFruL2Index 2, jnxFruL3Index 0, jnxFruName MIC: 24X10GE SFPP @ 6/1/*, jnxFruType 11, jnxFruSlot 6, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0)

 

On MX2000 platforms, Junos OS controls the bring-up sequence for native MPCs (MPC6E/8E/9E and so on), but it does not do the same for non-native MPCs (MPC1E/2E/3E/4E/5E and so on) with ADC.

The MX2000 Series routers do not honor the fru-poweron-sequence configuration with non-native MPCs with ADC. Both ADC and MPC are powered on in ascending order as default even though fru-poweron-sequence is configured.

This is a product limitation of ADC.

 

If the slot-ids of native MPCs are not configured in fru-poweron-sequence, these non-configured slot-ids (for native MPCs) are powered on in ascending order as is the default. (Slot-ids that are not configured in fru-poweron-sequence, they will be powered on in ascending order as is the default).

Non-native MPCs with ADC are not affected by the fru-poweron-sequence configuration, so they (non-native MPCs) will be powered on in the default ascending order after the configured native MPCs are reset.

Users can only control the starting of the power-on sequence. The actual sequence in which the MPCs will finally come up online is in-deterministic. It depends on how long each MPC takes to come up online.