"Unable To Determine Platform Id" error in ALOM on T5120/T5220 & T5140/T5240 systems

Asset ID:	1-72-1494101.1
Update Date:	2018-01-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1494101.1 : "Unable To Determine Platform Id" error in ALOM on T5120/T5220 & T5140/T5240 systems

Applies to:

Sun SPARC Enterprise T5120 Server - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise T5220 Server - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise T5240 Server - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise T5140 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

The ALOM command showfaults -v will show the error "unable to determine platform id":

sc> showfaults -v
Last POST Run: Thu Sep 20 10:00:20 2012

Post Status: Passed all devices
ID Time FRU Class Fault
1 Jan 22 13:45:42 /SYS/MB SP detected fault: unable to determine platform id

The message may also be seen in the showfru output in ALOM,

sc> showfru

/SYS/MB (container)
SEGMENT: FL
     /Configured_LevelR
     /Configured_LevelR/UNIX_Timestamp32: 2008-12-01T11:23:56-08:00
     /Configured_LevelR/Sun_Part_No: 5412530
     /Configured_LevelR/Configured_Serial_No: 0328MSL-08486P01A2
     /Configured_LevelR/HW_Dash_Level: 07

/Status_EventsR[0]/UNIX_Timestamp32: 2012-01-25T20:38:21-08:00
/Status_EventsR[0]/Old_Status: 0x40 (MAINTENANCE REQUIRED)
/Status_EventsR[0]/New_Status: 0x00 (OK)
/Status_EventsR[0]/Initiator: SCAPP
/Status_EventsR[0]/Component: 0
/Status_EventsR[0]/Event_Code: 02000000
/Status_EventsR[0]/Message: System Management reboot; prior status cleared.
/Status_EventsR[1]
/Status_EventsR[1]/UNIX_Timestamp32: 2012-01-25T20:36:16-08:00
/Status_EventsR[1]/Old_Status: 0x00 (OK)
/Status_EventsR[1]/New_Status: 0x40 (MAINTENANCE REQUIRED)
/Status_EventsR[1]/Initiator: SCAPP
/Status_EventsR[1]/Component: 0
/Status_EventsR[1]/Event_Code: 02000000
/Status_EventsR[1]/Message: unable to determine platform id       <<<<<<<<<<<<<<<<<<<
/Status_EventsR[2]
/Status_EventsR[2]/UNIX_Timestamp32: 2012-02-01T08:57:40-08:00
/Status_EventsR[2]/Old_Status: 0x40 (MAINTENANCE REQUIRED)
/Status_EventsR[2]/New_Status: 0x00 (OK)
/Status_EventsR[2]/Initiator: SCAPP
/Status_EventsR[2]/Component: 0
/Status_EventsR[2]/Event_Code: 02000000
/Status_EventsR[2]/Message: System Management reboot; prior status cleared.
/Status_EventsR[3]
/Status_EventsR[3]/UNIX_Timestamp32: 2012-02-09T21:04:37-08:00
/Status_EventsR[3]/Old_Status: 0x00 (OK)
/Status_EventsR[3]/New_Status: 0x40 (MAINTENANCE REQUIRED)
/Status_EventsR[3]/Initiator: SCAPP
/Status_EventsR[3]/Component: 0
/Status_EventsR[3]/Event_Code: 02000000
/Status_EventsR[3]/Message: unable to determine platform id       <<<<<<<<<<<<<<<<<<<

and the showplatform -v command in ALOM will not display the Chassis Serial Number:

sc> showplatform -v
SUNW,T5240
Chassis Serial Number: XXXXXXXXXXXXXXXXXXXX

Domain Status
------ ------
S0 Solaris running
sc>

Changes

This may happen if the Power Distribution Board (PDB) was replaced previously but the Serial Number (s/n) was not programmed into the new PDB by the Oracle Field Engineer.

Cause

Since the platform information is stored on the Power Distribution Board (PDB), the problem is likely a faulty or marginal PDB.

Solution

Replace the Power Distribution Board (PDB) and clear the fma errors.

NOTE: If the Power Distribution Board (PDB) was replaced previously but the Serial Number (s/n) was not programmed into the new PDB by the Oracle Field Engineer, then a new PDB is not required. An Oracle Field Engineer will need to be dispatched out to program the Serial Number information into the PDB.

Once the PDB is replaced, the Oracle Field Engineer will need to set the Serial Number of the system.

From Sun SPARC Enterprise T5140 and T5240 Servers Service Manual
http://docs.oracle.com/cd/E19910-01/820-3318-14/820-3318-14.pdf (pg 171)

Note – After replacing the power distribution board and powering on the system,
you must run the ALOM CMT setcsn and setcpn commands to set the
electronically readable chassis serial number and server part number.

11. At the ALOM CMT command line interface, use the setcsn command to set the
chassis serial number and the setcpn command to set the server part number
on the power distribution board.

The following is an example of the command-line dialog used to set the chassis
serial number and server part number for a Sun SPARC Enterprise T5140 server.

Caution – When performing the following steps, use special care to enter the correct
numbers. Once the power distribution board has been programmed with a chassis
serial number or server part number, the number cannot be changed.

sc> setsc sc_servicemode true
Warning: misuse of this mode may invalidate your warranty.

sc> setcsn -c chassis_serial_number
Are you sure you want to permanently set the Chassis Serial Number
to chassis_serial_number [y/n]? y
setcsn: Chassis serial number recorded.

sc> setcpn -p chassis_part_number
Are you sure you want to permanently set the Chassis Part Number
to chassis_part_number [y/n]? y
setcpn: Chassis part number recorded.

sc> showplatform
SPARC-Enterprise-T5140
Chassis Serial Number: chassis-serial-number
Domain Status
------ ------
SO Running

Once Chassis serial number and part number has been set, set sc_servicemode to false:

sc> setsc sc_servicemode false

Attachments

This solution has no attachment