In some cases, the Flexible PIC Concentrators (FPCs) that are taken offline by using the request chassis fpc slot fpc-slot offline operational-mode CLI command can come online after a configuration commit.
request chassis fpc slot fpc-slot offline
This article explains the kinds of configuration changes that can lead to this event and how they can bring up an offline FPC.
This behavior is demonstrated as follows:
Take an FPC offline with the command request chassis fpc slot fpc-slot offline :
Jul 30 00:59:33.127 router-re0 chassisd[7159]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Offlined by cli command Jul 30 00:59:35.242 router-re0 chassisd[7159]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC 3D 16x 10GE @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 7, jnxFruLastPowerOff 54240, jnxFruLastPowerOn 1445) Jul 30 00:59:35.346 router-re0 chassisd[7159]: CHASSISD_SNMP_TRAP10: SNMP trap generated: Fru Offline (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC 3D 16x 10GE @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 7, jnxFruLastPowerOff 54240, jnxFruLastPowerOn 1445)
When you check after a few days, the FPC remains in offline state as shown below:
{MASTER} labroot@router-re0> show chassis fpc Jul 31 21:07:34 Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%) Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer 0 Offline ---Offlined by cli command--- 1 Online 43 20 0 19 19 19 2048 14 19 2 Online 39 15 0 13 13 14 2048 11 20 3 Empty 4 Online 49 2 0 2 2 2 1024 15 51 5 Online 55 12 0 12 12 12 3136 9 19
Make some configuration changes that does not involve chassisd, such as adding a router-id or changing the CoS configuration of the interface.
{MASTER} labroot@router-re0> show system rollback compare 1 0 Jul 31 21:14:11 [edit class-of-service] + interfaces { + xe-1/1/0 { + unit 0 { + classifiers { + exp CLASSIFY_7Q_EXP; + } + } + } + } {MASTER} labroot@router-re0> show system rollback compare 3 2 Jul 31 21:14:37 [edit routing-options] - router-id 1.1.1.1; + router-id 2.2.2.2; {MASTER} labroot@router-re0> show chassis fpc Jul 31 21:14:50 Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%) Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer 0 Offline ---Offlined by cli command--- 1 Online 42 20 0 19 19 19 2048 14 19 2 Online 39 13 0 13 13 14 2048 11 20 3 Empty 4 Online 49 6 0 3 3 2 1024 15 51 5 Online 55 13 0 12 12 12 3136 9 19
Add the family "iso" to an interface, and then FPC 0 will be brought online as shown below.
{MASTER}[edit] labroot@router-re0# show |compare Jul 31 21:16:01 [edit] + interfaces { + xe-1/1/0 { + unit 0 { + family iso; + } + } + } labroot@router-re0> show chassis fpc Jul 31 21:26:04 Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%) Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer 0 Online 42 20 0 19 18 11 2048 14 20 <<< FPC 1 came online post commit of interface configuration 1 Online 43 20 0 19 19 19 2048 14 19 2 Online 39 14 0 14 14 14 2048 11 20 3 Empty 4 Online 49 4 0 3 3 3 1024 15 51 5 Online 55 13 0 12 12 12 3136 9 19
This is as per design. If the configuration involves chassisd, SIGHUP will be triggered followed by the FRU power sequencer, and then FRU power on, which would make the FPC come online. If the configuration does not involve chassisd, the FPC will remain offline.
When you look at the log messages by using show log messages , you can see that "FRU power on" was triggered immediately after configuration commit:
show log messages
Jul 31 21:16:08.994 router-re0 mgd[75054]: UI_COMMIT_COMPLETED: commit complete Jul 31 21:16:09.006 router-re0 mgd[75054]: UI_DBASE_LOGOUT_EVENT: User 'labroot' exiting configuration mode Jul 31 21:16:09.236 router-re0 chassisd[7159]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC 3D 16x 10GE @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 7, jnxFruLastPowerOff 54240, jnxFruLastPowerOn 15993639)
From the chassisd log, you can see that “Receive SIGHUP" and "power sequencer started" were initiated as well.
Jul 31 21:16:08 Receive SIGHUP Jul 31 21:16:08 .. power sequencer started .. Jul 31 21:16:09 CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC 3D 16x 10GE @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 7, jnxFruLastPowerOff 54240, jnxFruLastPowerOn 15993639) Jul 31 21:16:11 ... power sequencer finished …
If the configuration involves chassisd, SIGHUP will be triggered followed by the FRU power sequencer, and then FRU power on, which makes the FPC come online.
If you want to make sure that the FPCs are in offline state, perform the following sequentially:
Take the FPC offline by using the request chassis fpc slot fpc-slot offline command to gracefully offline the FPC.
Use the command set fpc fpc-slot power off to make sure that the FPCs remain in offline state no matter what configuration changes are made.
set fpc fpc-slot power off