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-1009212.1
Update Date:2011-06-10
Keywords:

Solution Type  Technical Instruction Sure

Solution  1009212.1 :   Sun Fire[TM] 12K/15K/E20K/E25K: Solaris[TM] and SMS requirements and recommendations  


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
212749


Applies to:

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

Goal

The minimum Solaris[TM] OS and SMS (System Management Services) software requirements on the Sun Fire[TM] 12K/15K/E20K/E25K platforms vary depending on the System Controller (SC) and/or the System Board (SB) type which make up the platform configuration. The configuration requirements are not determined by the platform name itself.

Solution

In order to know the specific software minimum requirements, you must first know the individual SB and SC  requirements. This document details the individual component software configuration requirements and provides information on configuration rules and recommendations for the Sun Fire 12K/15K/E20K/E25K software environment.

Sustaining support for SMS Releases :
SMS 1.1. 1.2, 1.4 : Discontinued effective June 9,2004.
SMS 1.3 : Discontinued effective October 5,2005.
SMS 1.4.1 : Discontinued effective July 15,2006.
SMS 1.5 : Discontinued effective July 30, 2008.
SMS 1.6 is the only supported releases for the Sun Fire 12K/15K/E20K/E25K platform family.

SMS 1.6. System Controllers must have as the minimum Solaris[TM] 9 4/04 or Solaris 10 1/06 with required patches.

Note: Solaris 10 should not be run on a cp1500, see Sun Alert <Document 1017340.1>.

When speaking about Solaris releases (for example, Solaris[TM] 9 09/05), it's supposed to be installed from corresponding distribution either from scratch or using upgrade installation type against previously installed OS image (for example, Solaris[TM] 9 04/04). There is no other supported way to get existing OS image updated to required release level patching and applying maintenance updates is insufficient.  Refer to /etc/release file to discover existing OS release level.

----------------------------------------------------------------------------------------------------------
Individual Component Configuration Requirements
----------------------------------------------------------------------------------------------------------

NOTE: A CP1500 (Nordica) SC and a MaxCPU Board are only used on a Sun Fire 12K/15K platform.  All other components can be interchanged between a Sun Fire 12K/15K/E20K/E25K platform.

CP1500 (Nordica) SC minimum requirements:
- SMS 1.1 (See NOTE-1 below)
- SC OS as early as Solaris[TM] 8 10/01
- See the Sun System Handbook for details

CP2140 (Othello+) SC minimum requirements:
- SMS 1.4.1 plus patches (See NOTE-1 below)
- Solaris[TM] 8 2/02 as the SC OS plus patches
- See the Sun System Handbook for details.

USIII (UltraSPARC(R) III) System Board minimum requirements:
- SMS 1.1 for 900 mhz USIII; SMS 1.2 for 1050 and 1200 mhz USIII SBs (See NOTE-1 below)
- Domain OS as early as Solaris[TM] 8 10/01 (depending on cpu speed) plus patches
- See the Sun System Handbook for details.

USIV (UltraSPARC(R) IV) System Board minimum requirements:
- SMS 1.4.1 plus patches (See NOTE-1 below)
- domains that contain USIV boards must be at Solaris[TM] 8 2/04 or Solaris[TM] 9 4/04 plus patches (See NOTE-2 below)
- See the Sun System Handbook for details.

USIV+ (UltraSPARC(R) IV+) System Board minimum requirements:
- SMS 1.6 for USIV+.
- SMS 1.6 plus patches 123300-06 and 124319-02 are required for USIV+ 1950MHz.
- Domains that contain USIV+ boards must be at Solaris[TM] 9 9/05 or Solaris[TM] 10 3/05 HW1 plus patches
- See the Sun System Handbook for details.


A211 Power supply
- SMS 1.6 plus patches 123300-05 and 124319-02 are required for A211 power supply support.


NOTE-1 : As of July 30, 2008 SMS 1.6 is the only supported SMS release, so this SMS release is the only realistic minimum that should be considered at this time.
NOTE-2 : As of September 8,2006 Solaris[TM] 8 will be EOLed. So SMS 1.6 will require Solaris 9 4/04 or Solaris 10 1/06 with required patches.

NOTE-3 : SMS 1.6 is not supported with Solaris 10 and cp1500s see Alert <Document 1017340.1>

Patches for Solaris[TM] and SMS should be maintained to include all the recent code fixes and enhancements made to the software configuration. Patches can be downloaded from My Oracle Support and should be applied by following the special installation instructions which are included in the downloaded patch.

----------------------------------------------------------------------------------------------------------
Firmware Requirements

----------------------------------------------------------------------------------------------------------

<Document 1003372.1> - Sun Fire[TM] 12K/15K/E20K/E25K: Firmware Revisions" provides the firmware compatibility  support matrix for the Sun Fire 12K/15K/E20K/E25K platform.

NOTE: Firmware compatibility requirements are based on the SMS release, not SB type.

----------------------------------------------------------------------------------------------------------
Minimum Requirement Guidelines
----------------------------------------------------------------------------------------------------------

Ultimately, the minimum software requirement for a platform is based on the minimum requirement for the "newest" component installed on that platform (SB or SC). Since software updates are backwards compatible, a new release of SMS or Solaris[TM] will contain all past fixes and configuration requirements for "older" component compatibility as well as "newer" component compatibility and improvements.

This translates to a configuration that supports the "new" and "old" simultaneously. An "older" software configuration knows nothing of hardware released after it was coded, so an "old" software configuration can only support "old" components.  It is the recommendation of engineering to keep the software configuration as current as possible at all times. By installing the most recent release of Solaris[TM] and SMS you are not only allowing the newest component types to be used in the platform configuration, but you are also taking advantage of the latest code fixes and enhancements available to the OS and SMS environment.  At the time of this writing, the recommendation would be to upgrade the CP1500 to a CP2140 and run Solaris[TM] 10 on the SC with SMS 1.6. Domains should utilize either Solaris 9 or Solaris 10 to fully realize the performance of the Sun Fire[TM] 12K/15K/E20K/E25K platform. Applying the Solaris[TM] OS and SMS patches further enhances the software configuration.


This OS and SMS recommendation is based on the improvements made in Solaris[TM] 9 and SMS 1.5 in areas such as availability, performance, security and PCI support, just to name a few. In addition, these software releases meet all of the minimum configuration requirements necessary to run any hardware configuration currently supported on the Sun Fire[TM] 12K/15K/E20K/E25K platform.

----------------------------------------------------------------------------------------------------------
Software Minimum requirements matrix for CPU types and speed.

----------------------------------------------------------------------------------------------------------

The following matrix is a summary of the minimum software requirements for Solaris and SMS in conjunction with what type of CPU board used in your platform. These requirements are listed as the minimum, any releases that are higher then the ones listed below should also meet the requirement.

Type
Speed
SC Reqs.
Domain Reqs.
USIII
900
SMS 1.2
Solaris 8 10/01

1050
SMS 1.2 w/
112481-06, 112488-07
Solaris 8 02/02

1200
SMS 1.2 w/
112481-06, 112488-07
Solaris[TM] 10 3/05 HW1
or Solaris 1/06
USIV
1050
SMS 1.4.1 w/
117385-01

Solaris 8 02/02
117002-01, 108528-29
115831-01, 115829-01

Solaris 9 4/04
113027-03
Solaris 8 2/04
117002-01, 110826-09
111335-18

Solaris 9 4/04
113027-03, 112233-09

Solaris[TM] 10 3/05 HW1
or Solaris 10 1/06

1200
SMS 1.4.1 w/
117866-04, 117385-01

Solaris 8 02/02
117002-01, 108528-29
115831-01, 115829-01

Solaris 9 04/04
113027-03


1350
SMS 1.4.1 w/
117866-04, 117385-01
117772-04

Solaris 8 02/02
117002-01, 108528-29
115831-01, 115829-01

Solaris 9 04/04
113027-03


USIV+
1500
SMS 1.6
123300-06

Solaris 9 04/04
113027-03

Solaris 10 1/06
121946-01

Solaris[TM] 9 9/05
Solaris 10 3/05 HW1 w/ 118822-18

1800
SMS 1.6
123300-06

Solaris 9 04/04
113027-03, 111712-12

Solaris 10 1/06
121946-01



1950
SMS 1.6
123300-06, 124319-02

Solaris 9 04/04
113027-03, 111712-12
Solaris 10 1/06
121946-01


The rules are:
- USIV+ requires a domain minimum Solaris[TM] OS of Solaris[TM] 9 9/05 or Solaris[TM] 10 3/05 HW1 w/ 118822-18.
- USIV requires a domain minimum Solaris[TM] OS of Solaris[TM] 8 2/04 or Solaris[TM] 9 4/04.
- USIII boards have a domain Solaris[TM] OS minimum requirement of Solaris[TM] 8 10/01.


Technically speaking an ALL USIII domain could operate at Solaris[TM] 8 10/01, while an ALL USIV domain on the same platform could operate at it's minimum OS releaseSolaris[TM] 8 2/04 or Solaris[TM] 9 4/04. Likewise, an ALL USIV+ domain could operate at their minimum requirement of Solaris 9 9/05 or Solaris[TM] 10 3/05 HW1 w/ 118822-18.  In order to have different minimum OS configurations, USIII, USIV and USIV+ domains must be completely separated from each other.

NOTE: A USIII board could move (Dynamic Reconfiguration) into the USIV domain due to the backwards compatibility of the newer OS release, but you could not move a USIV SB into the USIII domain because the OS does not support the newer board type. To reduce the headaches and heartache that may be associated with managing this mixed configuration platform, the recommendation, platform wide, would be to run the minimum required SMS and Solaris[TM] release for the newest board type (USIV) installed on platform. This resolves the issue with DR and moving different board types between domains, as well as allowing the maintenance tasks platform wide to be the same.


----------------------------------------------------------------------------------------------------------
References
----------------------------------------------------------------------------------------------------------

CP1500 Sun System Handbook reference.
CP2140 Sun System Handbook reference.
USIII Sun System Handbook reference.
USIV / USIV+ Sun System Handbook reference.
<Document 1003372.1> Sun Fire[TM] 12K/15K/E20K/E25K: Firmware Revisions

Internal References
@
TSC Patch Tools scpatch.pl and dmpatch.pl
http://panacea.uk.oracle.com/twiki/bin/view/Products/ProdPatchesFirmwareStarcat (this link is sometimes not working properly)
Onestop Sun Fire[TM] 12K/15K page
Onestop Sun Fire[TM] E20K/E25K page
Technical Instruction <Document 1003372.1> Sun Fire[TM] 12K/15K/E20K/E25K: Firmware Revisions
Enterprise Installation Standards (EIS) - Homepage

dead link as of 2011-06-10: Solaris 8 2/02 Installation Instructions: Dynamic Reconfiguration for hsPCI Assemblies and Max CPU Boards on Sun Fire[TM] 15K/12K Servers

Keywords Soloris, SMS, System Management Services, Component Configuration, Configuration Requirements, SunFire 12k, 15k,E20k, E25k

Previously Published As 79802


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