| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||||||
Solution Type Technical Instruction Sure Solution 1527924.1 : How to verify your SPARC SuperCluster is at version 1.1
Prior to the date of initial authoring of this note all SPARC SuperCluster engineered systems were installed using version ssc-1.0.1.x of the SuperCluster install scripts. The later version of the install scripts is ssc-1.1.x It is possible to bring a ssc-1.0.1.x machine up to ssc-1.1.x level and this note will describe what to check to see if your machine is already there. This is critical because certain features are only supported at the ssc-1.1.x build and above such as Exadata databases in Solaris 11 zones and the EM plugin for exadata on SuperCluster. In this Document
Applies to:SPARC SuperCluster T4-4 Half Rack - Version All Versions to All Versions [Release All Releases]SPARC SuperCluster T4-4 - Version All Versions to All Versions [Release All Releases] SPARC SuperCluster T4-4 Full Rack - Version All Versions to All Versions [Release All Releases] Oracle Solaris on SPARC (64-bit) GoalThe SPARC SuperCluster has a versioning that is determined on the software stack of all of it's components at the time of install and the install scripts used to perform said install. ssc-1.0.1 is the version all systems have been installed at in the field at the time of authoring this note. Future installs will be done with the ssc-1.1.<x> version of the install tools and software bundle. This being stated ssc-1.0.1.x SPARC SuperCluster may be brought forward to ssc-1.1.<x> software bundle level. It is possible that your SPARC SuperCluster may already meet these requirements and this note details the minimum versions of the items required and how to check to them. SolutionCheck the identification service on all your compute nodes and see if it states ssc-1.1.<x> . If so you can stop at this step. If it states ssc-1.0.1.<x> continue.
# svcprop /system/ssc/identification:default |grep build
configuration/build astring ssc-1.1.0.build-03 NOTE: For the very early SuperCluster installs there is a possibility the identification service does not exist. There is no way to retrofit this. Also this service does not get updated at patch time. This entry is merely here for you to save some time because if it states 1.1.<x> then you are complaint.
Use pkg list commands to verify the following packages on all your compute nodes. The minimum SRU level is 11.0 SRU12.4 The packages in this list are the minimum required version. Your version may be higher depending on which Quarterly Full Stack Download Patch you are on.
pkg://solaris/entire@0.5.11,5.11-0.175.0.12.0.4.0:20121002T161728Z The Code block will provide a couple examples. You will have to check for all the above packages in a fashion similar to below.
# pkg list iscsi
NAME (PUBLISHER) VERSION IFO system/platform/supercluster/iscsi 0.5.11-1.1.0.5 i-- # pkg list entire
NAME (PUBLISHER) VERSION IFO entire (solaris) 0.5.11-0.175.0.13.0.4.0 i-- Verify the Exadata Storage cell version for all storage cells. Minimum required version for 1.1 is 11.2.3.2.0 # imageinfo
Kernel version: 2.6.32-400.1.1.el5uek #1 SMP Mon Jun 25 20:25:08 EDT 2012 x86_64 Cell version: OSS_11.2.3.2.0_LINUX.X64_120713 Cell rpm version: cell-11.2.3.2.0_LINUX.X64_120713-1 Active image version: 11.2.3.2.0.120713 Active image activated: 2012-11-08 12:56:55 -0500 Active image status: success Active system partition on device: /dev/md5 Active software partition on device: /dev/md7 In partition rollback: Impossible Cell boot usb partition: /dev/sdm1 Cell boot usb version: 11.2.3.2.0.120713 Inactive image version: undefined Rollback to the inactive partitions: Impossible Verify the database version is 11.2.0.3.11 minimum. set your environment for your grid infrastructure home
$ORACLE_HOME/OPatch/opatch lsinventory |grep "PATCH FOR EXADATA"
Patch description: "QUARTERLY DISKMON PATCH FOR EXADATA (OCT 2012 - 11.2.0.3.11) : (14307915)" Patch description: "QUARTERLY CRS PATCH FOR EXADATA (OCT 2012 - 11.2.0.3.11) : (14275572)" Patch description: "QUARTERLY DATABASE PATCH FOR EXADATA (OCT 2012 - 11.2.0.3.11) : (14474780)" Verify the T4-4 firmware version is 8.2.1.b minimum for each compute node. #/opt/ipmitool/sbin/ipmitool sunoem cli "show /HOST"| grep sysfw_version
sysfw_version = Sun System Firmware 8.2.1.b 2012/08/03 11:58 Verify the software version of the onboard ZFSSA 7320. It should be 2011.1.4.0 + ZFS Storage Appliance ILOM+BIOS Firmware (1.6.1) minimum. Run the following for each of the storage heads from one of your compute nodes, substituting your storage head hostname for the word zfshostname. ssh orlscsn1 "configuration version get ak_version sp_version bios_version"
ak_version = ak/SUNW,maguro_plus@2011.04.24.4.0,1-1.21 sp_version = 3.0.16.10 bios_version = American Megatrends Inc. 08120104 05/08/2012 As you can see in this example we meet the software requirements however we do not meet the bios revision level requirement. If your 7320 is in a similar state open an SR to get the appropriate firmware.
If you are missing any of the requirements, outside of solaris-large-server, the course of action would be to update your system to the October 2012 Quarterly Full Stack Download Patch (QFSDP) minimum however it is strongly advised to move forward to the January 2013 QFSDP. If you are missing the solaris-large-server attach to your package repository and install it.
# pkg install solaris-large-server
References<NOTE:1567979.1> - Oracle SuperCluster Supported Software Versions - All Hardware TypesAttachments This solution has no attachment |
||||||||||||||||
|
||||||||||||||||