When FPC Major alarm EEPROM is not accessible appeared, it denotes hardware error of the FPC.

When EEPROM is not accessible event occurs, FPC went offline with following log messages:

Jan 2 11:00:42 r1.tuni-her alarmd[18760]: Alarm set: CB id=-1660944241, color=RED, class=CHASSIS, reason=FPC 0 EEPROM is not accessible

Jan 2 11:10:34 r1.tuni-her chassisd[18344]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Restarting unresponsive board

Jan 2 11:10:34 r1.tuni-her chassisd[18344]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperDisabled (entPhysicalIndex 24, entStateAdmin 2, entStateAlarm 0)

Jan 2 11:10:34 r1.tuni-her chassisd[18344]: CHASSISD_SNMP_TRAP0: ENTITY trap generated: entConfigChanged

Jan 2 11:10:34 r1.tuni-her chassisd[18344]: CHASSISD_SNMP_TRAP10: SNMP trap generated: Fru Offline (jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC @ 0/*/*, jnxFruType 3, jnxFruSlot 0, jnxFruOfflineReason 15, jnxFruLastPowerOff -1504600973, jnxFruLastPowerOn -1504597775)

Jan 2 11:10:34 r1.tuni-her chassisd[18344]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperDisabled (entPhysicalIndex 24, entStateAdmin 2, entStateAlarm 0)

The cause is due to hardware error on the specified FPC device. 

Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.

Collect the show command output.

Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.

show log messages

show log chassisd

show system core-dumps

start shell network pfe <fpc#>

show nvram

show syslog messages

exit

Check for any associated core dumps at or just before the time of the Alarm event.

• If there is an associated core dump recorded, open a case with your technical support representative to investigate the issue further.

Analyze the show command output.

• In the 'show log messages', review the events that occurred at or just before the appearance of the "ALARM" message. Frequently these events help identify the cause.

During a maintenance window, as it will impact transit traffic, try the following:

• Reset the specific hardware reporting the error. 
• To ‘reset an FPC’ run the following CLI command
  • request chassis fpc slot # offline
  • request chassis fpc slot # online
• Reseat the FPC in its slot. Use a flashlight to check for bent pins at this time.
• Swap the FPC with a spare, or switch to a redundant FPC.

If the above steps not helped to resolve the issue, then RMA needed.