This article explains when the fxpc process is crash on EX4400 or EX4100 switches, 

SNMP traps indicating FRU insertion/removal and "not powered" alarms for power supplies (PSMs) have been observed. 

Following the crash and subsequent restart of the fxpc process on your EX4400 device, a series of system-level events were triggered.

Below relevant logs have been attached for the reference. 

Chassis Alarms for Power Supply Modules (PSM0 and PSM1):

The system reported FRU removal followed by FRU insertion traps for the FPC and both power supply modules (PSM0 and PSM1). 

During an FPC reinitialization, as the chassis management processes momentarily lose contact with hardware components.

Minor alarms were displayed for both PSM0 and PSM1 as “not powered” during the transition period.

These alarms were cleared automatically after approximately 15 seconds, once hardware reinitialization was complete and power supply status was re-synced.

SNMP Traps Generated for FRU Events:

SNMP traps were logged for both FRU removal and FRU insertion events related to the FPC and power supplies, indicating hardware-level transitions recognized by the system.

Following logs displaying as below:

■Restart fxpc

Jun 6 16:43:56 device mgd[23245]: UI_CMDLINE_READ_LINE: User command 'request system process terminate 23267 '

Jun 6 16:43:57 device chassisd[11245]: CHASSISD_IPC_CONNECTION_DROPPED: Dropped IPC connection for FPC 0

Jun 6 16:43:57 device chassisd[11245]: CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(0)

Jun 6 16:43:57 device ppmd[11273]: PPMD_PFE_SHUTDWN: PPMD: Connection Shutdown/Closed with PFE: fpc0

■FPC removal

Jun 6 16:43:57 device chassisd[11245]: CHASSISD_SNMP_TRAP7: SNMP trap generated: FRU removal (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: device @ 0/*/*, jnxFruType 3, jnxFruSlot 0)

■FRU insertion PSM 0 & PSM 1

Jun 6 16:43:58 device chassisd[11245]: CHASSISD_SNMP_TRAP7: SNMP trap generated: FRU insertion (jnxFruContentsIndex 2, jnxFruL1Index 1, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName Power Supply 0 @ 0/0/*, jnxFruType 7, jnxFruSlot 0)

Jun 6 16:43:58 device chassisd[11245]: CHASSISD_SNMP_TRAP7: SNMP trap generated: FRU insertion (jnxFruContentsIndex 2, jnxFruL1Index 1, jnxFruL2Index 2, jnxFruL3Index 0, jnxFruName Power Supply 1 @ 0/1/*, jnxFruType 7, jnxFruSlot 1)

■PSM 0 & PSM1 not powered

Jun 6 16:43:58 device craftd[11261]: Minor alarm set, FPC 0 PEM 0 is not powered

Jun 6 16:43:58 device craftd[11261]: Minor alarm set, FPC 0 PEM 1 is not powered

■PSM 0 & PSM1 alarm cleared

Jun 6 16:44:13 device craftd[11261]: Minor alarm cleared, FPC 0 PEM 0 is not powered

Jun 6 16:44:13 device craftd[11261]: Minor alarm cleared, FPC 0 PEM 1 is not powered

FXPC Restart Impact: 

FXPC is one of the major process in Junos that is responsible for managing the data plane forwarding on Juniper Switches. 

It plays a critical role in handling packet forwarding engine tasks, including the programming and monitoring of ASICs.

Restarting this process simulates an FPC reboot.

When fxpc is restarted, messages such as "FRU removal/insertion" and "not powered" have been displayed,

However, as a part of its standard behavior, chassisd might generates SNMP traps for FRU removal/insertion events and power state changes during such transitions.

Sometimes, the sensors on the switch take time to detect the hardware.

Especially if the power supplies are functioning normally and the device stabilizes and no persistent alarms remain, then no need to be worries.

No alarms have been seen:

——————

user@device> show chassis alarms no-forwarding

No alarms currently active   <<<<<<<<<<<<