Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1012287.1
Update Date:2011-05-23
Keywords:

Solution Type  Technical Instruction Sure

Solution  1012287.1 :   Sun Fire[TM] Servers: 12K/15K/E25K/E20K: Platform Identification on Highend Systems  


Related Items
  • Sun Fire E25K Server
  •  
  • Sun Fire E20K Server
  •  
  • Sun Fire 12K Server
  •  
  • Sun Fire 15K Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>High-End Servers
  •  

PreviouslyPublishedAs
216961


Applies to:

Sun Fire 12K Server
Sun Fire 15K Server
Sun Fire E20K Server
Sun Fire E25K Server
All Platforms

Goal

This article contains: Platform Identification on Highend Systems.

System Management Services (SMS) 1.4.1 incorporates a new feature for improved platform identification.

Solution

The first release of the 15000 architecture included only one system type, the 18 Expander 15K. The 9 Expander 12K was released in April 2002.
At its release both systems were identically identified by domain commands, such as "prtdiag" and the OpenBoot[TM] PROM banner.
The platform identification was "Sun Fire[TM] 15000."

For example:
System Configuration: Sun Microsystems sun4u Sun Fire 15000
System clock frequency: 150 MHz
Memory size: 28672 Megabyte

Neither was there a distinction between the 12K and 15K from the System Controller (SC) perspective. The only way to differentiate the two platforms was by determining the number of installed expanders.

SMS 1.4.1 has enhanced platform identification so that all four systems in the 15000 architecture may be differentiated. The four systems include the Sun Fire[TM] 12K, 15K, E20K and E25K.
The latter two systems represent the second release of the 15000 architecture and debuted with the UltraSPARC[R] IV processor family.
All Sun Fire E20K and E25K servers are encoded in manufacturing with the proper platform type.
The SMS "showplatform" command displays the platform type when run on the Main SC. Valid values are "Sun Fire E20K" or "Sun Fire E25K."

For example:
PLATFORM:
=========
Platform Type: Sun Fire E25K

Platform type identification is also displayed in the domain Open Boot PROM banner:
Sep 22 11:05:21 2009 Sun Fire E25K, using IOSRAM based Console
Sep 22 11:05:21 2009 Copyright 2006 Sun Microsystems, Inc. All rights reserved.
Sep 22 11:05:21 2009 OpenBoot 4.22.20, 126976 MB memory installed, Serial #44641544.
Sep 22 11:05:21 2009 Ethernet address 0:0:be:a9:2d:8, Host ID: 82a92d08.

or by running "prtdiag" on the domain:
System Configuration: Sun Microsystems sun4u Sun Fire E25K
System clock frequency: 150 MHz
Memory size: 262144 Megabytes

The Sun Fire 12K and 15K servers that were manufactured prior to May 2004 are not encoded with a platform type. When no platform type is encoded, machines identify themselves as "Sun Fire 15000."
You may contact your authorized Sun Service representative to have the platform type programmed to reflect the actual machine type (12K or 15K).
Customers who elect to have this programming performed should understand that command output from "prtdiag" will be modified. Instead of the default "Sun Fire 15000" the command will instead output "Sun Fire 12K" or "Sun Fire 15K," depending upon the system type.

It is important to understand that all four platforms are identified as "SUNW,Sun-Fire-15000" in the domain's "uname" output.
The "uname -i" command displays the hardware implementation (also known as root node name). All four Sun Fire servers (12K, 15K, E20K and E25K) in the 15000 family are part of the Sun-Fire-15000 hardware implementation.

Product
Sun Fire 15K Server
Sun Fire 12K Server
Sun Fire E25K Server
Sun Fire E20K Server

Internal Section

SMS 1.4.1, and later, accesses a FRU ID property stored on the CP to determine the platform type.

The record is the "PlatformR" record and can be displayed with the "prtfru" command run on the Main system controller.  The prtfru output is useful because you can also see when the "PlatformR" record was written.  An example follows:
% prtfru "/frutree/chassis/CP" | egrep PlatformR 
/PlatformR
/PlatformR/UNIX_Timestamp32: Fri Apr 23 11:02:18 PDT 2004
/PlatformR/Platform_Name: SunFire15K

In this example the platform type is "Sun Fire 15K," and the record was written on 23 April 2004 at 11:02 PDT.

SMS defaults platform identification to "Sun Fire 15000" when no seeprom value is encoded.  An error similar to the following example message appears after an SMS start and when the PlatformR record is not encoded.  The error is contained in the platform messages file ($SMSVAR/adm/platform/messages):

    Mar 25 15:39:40 2004 sc0 frad[9397]: [9942 2237309660682 ERR
FRUData.cc 856] Failed to read packet FD/PlatformR on CP at CP0

The procedure to program platform type is documented in Technical Instruction Document 1004941.1

It is necessary to re-write this PlatformR record in the seeprom following a centerplane support board (CSB) replacement.


Keywords: platformR, uname, platform, type


Previously Published As 76208



Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback