It seems like FPC is not initialising completely
Jul 14 11:45:17 CHASSISD_FRU_UNRESPONSIVE: Error for FPC 0: unresponsive to attempts to start it; left it offline
Jul 14 11:45:17 CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Error
Jul 14 11:45:17 fpc_down slot 0 reason Error cargs 0x0
Jul 14 11:45:17 fpc_offline_now - slot 0, reason: Error, error Unresponsive transition state 1
Jul 14 11:45:17 fpc_atlas_snmp_get_led_state FPC 0: LED idx2 0 color blinking green value 8
Jul 14 11:45:17 i2cs_virtual_power_off Powered OFF FPC 0, bitmap 0
Jul 14 11:45:17 FPC#0 - power off [addr 0x11] reason: Error
Jul 14 11:45:17 CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: Virtual FPC @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 3, jnxFruLastPowerOff 246325, jnxFruLastPowerOn 186317)
Jul 14 11:45:17 CHASSISD_SNMP_TRAP10: SNMP trap generated: Fru Offline (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: Virtual FPC @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 3, jnxFruLastPowerOff 246325, jnxFruLastPowerOn 186317)
Jul 14 11:45:17 fpc_atlas_snmp_get_led_state FPC 0: LED idx2 0 color off value 7
Jul 14 11:45:17 fpc_offline_now - slot 0, is_resync_ready cleared
Jul 14 11:45:17 fpc/pic 0/0: No handle for i2c_id 0x0
Jul 14 11:45:17 fpc/pic 0/1: No handle for i2c_id 0x0
Jul 14 11:45:17 fpc/pic 0/2: No handle for i2c_id 0x0
Jul 14 11:45:17 fpc/pic 0/3: No handle for i2c_id 0x0
Jul 14 11:45:17 hwdb: entry for fpc 2986 at slot 0 deleted
Jul 14 11:45:17 send: red alarm set, device FPC 0, reason FPC 0 Hard errors
.....
Jul 14 11:50:14 CHASSISD_UNSUPPORTED_FPC: FPC with I2C ID of 0xbaa is not supported
I suspect this could be related to vmx version ? Did you by any chance perfrom a cli upgrade ?
If not, just for troubleshooting sake config fpc in lite-mode and restart vmx entirety.
//QZ