SRX1500 in cluster deployment or standalone, showing Major FPC 0 Hard errors due to EEPROM corruption
Chassis Alarms will prompt Major FPC 0 hard Errors
> show chassis alarms no-forwarding 1 alarms currently active Alarm time Class Description 2023-07-12 09:44:37 CEST Major FPC 0 Hard errors
Hardware details will be missing the SN:
> show chassis hardware detail no-forwarding Hardware inventory: Item Version Part number Serial number Description Chassis Midplane CB 0 REV 12 711-053838 BCAK1234 CPU Board
Hardware inventory will point out random values instead of the SN
> show chassis hardware extensive Item Version Part number Serial number Description Chassis Jedec Code: 0x7fb0 EEPROM Version: 0x02 S/N: \x10‡fl\x06 <<<<<<<<<<< Assembly ID: 0xe0ff Assembly Version: 00.00 Date: 00-00-0000 Assembly Flags: 0x1e Board Information Record: Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I2C Hex Data: Address 0x00: 7f b0 02 ff e0 ff 00 00 00 00 00 00 00 00 00 00 Address 0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Address 0x20: 10 e0 df 06 00 00 00 00 00 00 00 00 1e 00 00 00 Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Address 0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Midplane Jedec Code: 0x51ab EEPROM Version: 0x0d S/N: …Ÿ\x06\x01@\x1z\x07\x01 <<<<<<<<<<< Assembly ID: 0xe0ff Assembly Version: 127.63 Date: 04-44-0000 Assembly Flags: 0x1e
Logs will indicate Corruption on midplane ID EEPROM:
LCC: send: lcc 1 sending swversion CHASSISD release 21.4R3.15 built by builder on 2022-09-03 07:34:06 UTC LCC: ch_srxtvp_sno_macaddr_init: Failed sysctl for hw.product.pvi.config.mac_address.from_interface. LCC: chassis serial number: 10 d0 df 6 0 0 CHASSISD_I2C_MIDPLANE_CORRUPT: Corruption on midplane ID EEPROM (ID: 0xE0FF, MAC address: 0x0, 0x0) LCC: send: lcc 16777216 sending mac addresses
Reinstalling the current Junos or upgrading to a different Junos version (any version) might recover the EEPROM from the issue state. If it does not help we must proceed with the RMA of the chassis.
25 Aug 2023: Initial Verison