Configuration file missing and/or ereport.fs.file.missing /package/ilom_rom.pkg (Doc ID 2208950.1)

Last updated on NOVEMBER 30, 2016

Applies to:

SPARC M6-32 - Version All Versions to All Versions [Release All Releases]
SPARC M5-32 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

When the SP0/SP1 and/or SPP0/SPP1/SPP2/SPP3 Firmware are mismatched in the platform, these errors and symptoms are observed in the below logs.  A missing /package/ilom_rom.pkg file will prevent an SP/SPP from automatically updating system firmware.  Firmware mismatch on an SPP may prevent DCU hardware from functioning (e.g., prevent CMU poweron).

********** @usr@local@bin@spshexec_show_-script_@X@logs@event@list.out **********

Event ID Date/Time Class Type Severity
----- ------------------------ -------- -------- --------
6472 Mon Nov 21 02:27:35 2016 Internal Product critical
Configuration file missing: User Management Attribute File.

********** DCUs controlled by a specific Golden SPPx may not start, due to a mismatch in FW for that particular SPPx **********

6468 Mon Nov 21 02:19:20 2016 Fault Fault critical
Fault detected at time = Mon Nov 21 02:19:20 2016. The suspect
component: /SYS/CMU11/MEM1 has fault.chassis.device.fail with
probability=100. Refer to http://support.oracle.com/msg/SPT-8000-1Q for details.

6467 Mon Nov 21 02:19:20 2016 Fault Fault critical
Fault detected at time = Mon Nov 21 02:19:19 2016. The suspect
component: /SYS/CMU11/CMP1 has fault.chassis.device.fail with
probability=100. Refer to http://support.oracle.com/msg/SPT-8000-1Q for
details.

6460 Mon Nov 21 02:18:51 2016 IPMI Log minor
ID = 47 : 11/21/2016 : 02:18:51 : System Boot Initiated : System
Management Software : Host2: System Restart : Asserted

********** fma@persist@faultdiags@ereports.log* **********

2016-11-05/16:12:36 ereport.fs.file.missing@/SYS/SP1
_file = /package/ilom_rom.pkg
system_component_firmware_manufacturer = Oracle Corporation
system_component_firmware_versions = (ILOM)3.2.7.1.b
system_component_firmware_releases = (ILOM)2016.09.09
**********
2016-11-05/16:11:03 ereport.fs.file.missing@/SYS/SP0
_file = /package/ilom_rom.pkg
system_component_firmware_manufacturer = Oracle Corporation
system_component_firmware_versions = (ILOM)3.2.7.1.b
system_component_firmware_releases = (ILOM)2016.09.09

 

 

How to Check the Firmware for each SPx/SPPx on a snapshot

<snapshot directory>/$ find . -name @etc@versions -print -exec egrep "SP firmware:" {} \;
./ilom/@etc@versions
SP firmware: 3.2.7.1.b <======================== SP1 is at 9.6.6.a (Active SP)
./sp_snapshot/SP0/ilom/@etc@versions
SP firmware: 3.2.1.3.a <======================== SP0 is at 9.0.1.a ** OLD FW **
./spp_snapshot/SPP2/ilom/@etc@versions
SP firmware: 3.2.4.1.f <======================== SPP2 is at 9.3.0.f ** OLD FW **
./spp_snapshot/SPP1/ilom/@etc@versions
SP firmware: 3.2.7.1.b <======================== SPP1 is at 9.6.6.a
./spp_snapshot/SPP3/ilom/@etc@versions
SP firmware: 3.2.7.1.b <======================== SPP1 is at 9.6.6.a
./spp_snapshot/SPP0/ilom/@etc@versions
SP firmware: 3.2.7.1.b <======================== SPP1 is at 9.6.6.a

 

 

Changes

 The above symptoms are usually observed in one of these conditions

1. An SPx or SPPx ws just replaced and the replacement board did not self update

2. A Platform System Firmware Update was performed and One or More SPx/SPPx was not updated

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms