Asset ID: |
1-72-2208950.1 |
Update Date: | 2017-10-11 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2208950.1
:
Configuration file missing and/or ereport.fs.file.missing /package/ilom_rom.pkg
Related Categories |
- PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Mx-32
|
In this Document
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
You can also see from the version output of each individual SP/SPP what Firmware is exactly loaded
SP0
====
!! the FW 9.0.1.a is not even in the released version
!! first released version after Beta is 9.0.1.f
!! the SP0 came from Logistics during replacement and failed to update itself
Trace logs....
FLASH 2016-11-20 19:59:31.749933 1370 S20A_0proxy_sp_self_update Firmware mismatch detected: local=3.2.4.1.f-96162, active SP=3.2.7.1.b-112192
FLASH 2016-11-20 19:59:31.749933 1370 S20A_0proxy_sp_self_update Firmware mismatch detected: local=3.2.4.1.f-96162, active SP=3.2.7.1.b-112192
FLASH 2016-11-20 19:59:31.978911 1374 S20A_0proxy_sp_self_update get_active_sp_pkg_ver: Could not obtain package version from Active-SP
-bash-4.1$ pwd
/sr/3-13593887261/M5SNSH/Dhqux_M6-32_SP2_AK00259892_2016-11-20T23-42-44/sp_snapshot/SP0/ilom
-bash-4.1$ cat @etc@versions
SP firmware: 3.2.1.3.a
SP firmware date: Thu Feb 28 21:50:02 PST 2013
SP firmware build number: 79412
SP firmware repository: http://ilomsvn.us.oracle.com/svnht/platform/hotamale/branches/3.2.1.3
SP platform class: river/main.pilot3
SP filesystem: 0.2.7
SP builder: cboland@sanpen-rh5-0
SP workspace: /scratch/re/9.0/9.0.1.a/ilom <================= FW Does not match with the rest
htws config file: river.main.config.pilot3
SPP2
====
-bash-4.1$ pwd
/sr/3-13593887261/M5SNSH/Dhqux_M6-32_SP2_AK00259892_2016-11-20T23-42-44/spp_snapshot/SPP2/ilom
-bash-4.1$ cat @etc@versions
SP firmware: 3.2.4.1.f
SP firmware date: Tue Jan 13 20:09:43 PST 2015
SP firmware build number: 96162
SP firmware repository: http://ilomsvn.us.oracle.com/svnht/platform/hotamale/branches/3.2.4.1
SP platform class: river/bm.pilot3
SP filesystem: 0.2.10
SP builder: cboland@sanpen-oel5-1
SP workspace: /scratch/re/9.3/9.3.0.f/ilom <==================== FW Does not match with the rest
SP Build: /scratch/re/9.3/9.3.0.f/ilom/Buld/river/bm.pilot3
SP Output: /scratch/re/9.3/9.3.0.f/ilom/Output/river/bm.pilot3
htws config file: river.bm.config.pilot3
<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 (this SP0 was replaced and came from Logistics)
./spp_snapshot/SPP2/ilom/@etc@versions
SP firmware: 3.2.4.1.f <======================== *SPP2 is at 9.3.0.f (DCU2 was having trouble powering on, Golden was SPP2)
./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
Could be caused by faulty hardware or Firmware Update Bug
Solution
To fix the condition of missing package files and correct firmware mismatch, Update System Firmware by re-applying the same SysFW version by following the instructions in the document(s) listed below:
Mx-32 - How to update System Firmware (ILOM / HC / POST / HV / OBP / GM ) (Doc ID 1981675.1)
SPARC Mx-32 and M7 Servers: Firmware FAQ (Doc ID 1542610.1)
http://docs.oracle.com/cd/E24355_01/index.html
SPARC M5-32 and SPARC M6-32 Servers Administration Guide
References
<BUG:18346701> - GENERATE EREPORT WHEN REQUIRED FILES ARE MISSING
<NOTE:2045782.1> - How to verify SPP are at correct firmware level following SysFW upgrade
<NOTE:1981675.1> - Mx-32 - How to update System Firmware (ILOM / HC / POST / HV / OBP / GM )
<NOTE:1542610.1> - SPARC Mx-32 and M7 Servers: Firmware FAQ
Attachments
This solution has no attachment