Description

The article describers a scenario of improper event-options configuration triggers unexpected FPC offline.

Symptoms

user@router# show event-options
policy poweroff-fpc-1 {
    events chassisd_snmp_trap10;
    attributes-match {
        chassisd_snmp_trap10.trap matches "Fru Offline";
        chassisd_snmp_trap10.argument6 matches jnxFruType;
        chassisd_snmp_trap10.argument7 matches jnxFruSlot;
        chassisd_snmp_trap10.value7 matches 1;
    }
    then {
        change-configuration {
            commands {
                "set chassis fpc 1 power off";
                " deactivate chassis error";
            }
            commit-options {
                log "Power off FPC slot 1 by offline FPC trap raised";
            }
        }
    }
}
policy poweroff-fpc-10 {
    events chassisd_snmp_trap10;
    attributes-match {
        chassisd_snmp_trap10.trap matches "Fru Offline";
        chassisd_snmp_trap10.argument6 matches jnxFruType;
        chassisd_snmp_trap10.argument7 matches jnxFruSlot;
        chassisd_snmp_trap10.value7 matches 10;
    }
    then {
        change-configuration {
            commands {
                "set chassis fpc 10 power off";
                " deactivate chassis error";
            }
            commit-options {
                log "Power off FPC slot 10 by offline FPC trap raised";
            }
        }
    }
}

user@router# show chassis

[edit]
user@router# run show chassis fpc |match online
                     Temp  CPU Utilization (%)   CPU Utilization (%)  Memory    Utilization (%)
Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
  1  Online           Testing  55         0       54     57     56    511        42          0
 10  Online           Testing  61         0       62     59     55    511        42          0

user@router> monitor start messages |match SNMP_TRAP10

user@router> request chassis fpc restart slot 10
Restart initiated, use "show chassis fpc" to verify

Aug 26 23:52:13  router chassisd[19658]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 7, jnxFruL1Index 11, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: VMX EAGLE MPC @ 10/*/*, jnxFruType 3, jnxFruSlot 10, jnxFruOfflineReason 9, jnxFruLastPowerOff 68155531, jnxFruLastPowerOn 68108724)
Aug 26 23:52:13  router chassisd[19658]: CHASSISD_SNMP_TRAP10: SNMP trap generated: Fru Offline (jnxFruContentsIndex 7, jnxFruL1Index 11, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: VMX EAGLE MPC @ 10/*/*, jnxFruType 3, jnxFruSlot 10, jnxFruOfflineReason 9, jnxFruLastPowerOff 68155531, jnxFruLastPowerOn 68108724)
Aug 26 23:52:15  router chassisd[19658]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: VMX EAGLE MPC @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 5, jnxFruLastPowerOff 68155735, jnxFruLastPowerOn 1738)
Aug 26 23:52:15  router chassisd[19658]: CHASSISD_SNMP_TRAP10: SNMP trap generated: Fru Offline (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: VMX EAGLE MPC @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 5, jnxFruLastPowerOff 68155735, jnxFruLastPowerOn 1738)

user@router# show chassis
fpc 0 {
    power off;
}
fpc 10 {
    power off;
}

As the configuration and CLI operations above, request chassis fpc restart slot 10 to simulate a FPC10 failure, the operation generates CHASSISD_SNMP_TRAP10 for FPC10, expected policy poweroff-fpc-10 of event-option is called and auto config fpc 10 power off under [chassis] hierarchy, but FPC 0 is set power off as well, that is unexpected.

Solution

This is due to incorrect  attributes-match chassisd_snmp_trap10.value7, in case of FPC 10 reloads, both policy poweroff-fpc-1 and policy poweroff-fpc-10 are matched.
The correct configuration of [attributes-match chassisd_snmp_trap10.value7] as below to instead. 
set event-options policy poweroff-fpc-1 attributes-match chassisd_snmp_trap10.value7 matches "^1$"
set event-options policy poweroff-fpc-10 attributes-match chassisd_snmp_trap10.value7 matches "^10$
Refer to Use Regular Expressions to Refine the Set of Events That Trigger a Policy .

Modification History

2024-08-27 : Article Created