SPARC T4-1B Server Module Product Notes
Contents
1. For 10GbE network connectivity FEM 4871A Z For storage connectivity REM SG SAS6 REM Z This NEM s documentation is at http www oracle com pls topic lookup ctx E19285 01 Requires e For 1GbE connectivity no FEM required For 10GbE connectivity FEM 7100283 or 7100633 For SAS2 storage connectivity REM SG SGX SAS6 REM Z This NEM s documentation is at http www oracle com pls topic lookup ctx E19530 01 Provides GbE connectivity no FEM required Prior to installation update firmware on SAS 1 components See Important Firmware Upgrade Required Prior to Mixing SAS 1 and SAS 2 Components on page 8 This REM s documentation is at http www oracle com pls topic lookup ctx E19946 01 Supported Supported This FEM s documentation is at http www oracle com pls topic lookup ctx E19539 01 Chapter 1 Late Breaking Information 3 Preinstalled Software Software Location Function One of the following On ZFS with the root partition OS Oracle Solaris 11 OS on drive 0 slice 0 e Oracle Solaris 10 8 11 OS Note Mandatory package updates and patches are not preinstalled You must obtain and install them before you put the server module into production See Required Patches and Package Updates on page 6 Oracle VM Server for SPARC 2 1 opt SUNW1dm Manages logical domains Electronic Prognostics EP 1 2 opt ep Provides early warni2. on page 9 1 At the ok prompt type 0 ok probe scsi all pci 400 pci l pci 0 pci c LSI sas 0 lt SAS Controller FCode Version 1 00 54 MPT Version 2 00 Firmware Version 5 00 17 00 Target 9 Unit 0 Disk SEAGATE ST930003SSUN300G 0B70 585937500 Blocks 300 GB SASDeviceName 5000c50033438dbb SASAddress 5000c50033438db9 PhyNum 0 lt HD slot 0 Target b 10 SPARC T4 1B Server Module Product Notes December 2011 Unit 0 Disk SEAGATE ST930003SSUN300G 0468 585937500 Blocks 300 GB SASDeviceName 5000c50005c15803 SASAddress 5000c50005c15801 PhyNum 1 lt HD slot 1 Target c Unit 0 Encl Serv device SUN NEM Hydra II SOL 0308 SASAddress 5080020000bb193d PhyNum 24 pci 400 pci l1 pci 0 pci 0 pci 0 usb 0 2 hub 3 storage 2 Unit 0 Removable Read Only device AMI Virtual CDROM 1 00 2 In output look for the following disk identifiers LSI sas 0 Controller REM on the server module SASDeviceName WWN that the Oracle Solaris OS recognizes m SASAddress WWN that the OBP references PhyNum Physical slot that the drive occupies 3 Use the values in the output to construct the resulting Oracle Solaris logical device name as expressed by cntndn This example is based on the previous output cn c0 n is the SAS controller number 0 in this example tn t5000c50033438dbb n is the SASDeviceName value dn d0 n is 0 for all embedded SCSI devices The resulting log
3. on page 9 m Here are some examples of situations when you must correlate a logical device name with a drive s physical location When downloading the OS over a network you must specify the logical device name of the drive in slot 0 the default boot device In addition if you use Oracle Solaris Jumpstart you must use a specific WWN syntax See Oracle Solaris Jumpstart WWN Syntax on page 11 If you run the format command you must select one of the logical device names presented To ensure you select the correct drive you must correlate a logical device name with the physical drive If you view a system message that lists a drive s logical device name you might need to identify the slot in which the drive is installed To correlate drive logical device names with physical locations or the other way around From the Oracle Solaris 10 8 10 OS use the diskinfo command See Correlate WWN Device Names With Physical Locations diskinfo Command on page 9 At the OBP ok prompt use the probe scsi all command See Correlate WWN Device Names With Physical Locations probe scsi all Command on page 10 Correlate WWN Device Names With Physical Locations diskinfo Command The diskinfo command a new disk and slot identification utility was introduced in Oracle Solaris 10 8 11 OS and in the kernel patch 144500 19 or later If you do not have access to the OS for example if the server module is not
4. Documentation vii Late Breaking Information 1 Supported Chassis 1 v Identify Your Chassis Version 2 Supported Hardware Components 3 Preinstalled Software 4 Supported Versions of the OS Firmware and Software 5 Required Patches and Package Updates 6 Oracle Solaris 11 OS Package Updates 6 Oracle Solaris 10 OS Patches 6 v Obtain Patches 7 Important Firmware Upgrade Required Prior to Mixing SAS 1 and SAS 2 Components 8 Identifying Drive Logical Device Names and Physical Locations 8 v Correlate WWN Device Names With Physical Locations diskinfo Command 9 v Correlate WWN Device Names With Physical Locations probe scsi all Command 10 Oracle Solaris Jumpstart WWN Syntax 11 Interactive Installation Example 2 2 Known Product Issues 15 Hardware Issues 15 Sun Type 6 Keyboards are Not Supported by SPARC T4 Series Servers 15 PSH Might Not Clear a Retired Cache Line on a Replaced Motherboard CR 7031216 15 2 Meter USB Cable Length Limit 7048419 16 Uncorrectable L2 Cache Errors are Sometimes Reported as Core Faults Without Any Cache Line Retirement CR 7071237 and CR 7071974 16 During a Reboot After an Unrecoverable Hardware Error CPUs Might Not Start CR 7075336 16 Blue LED on Drive Does Not Light When the Drive is Ready to Remove CR 7082700 17 Firmware OS and Other Software Issues 7 fault memory memlink uc Fault Did Not Cause Panic as Stated by System Message CR 6940599 7 Timestamp for an Oracle
5. ILOM Fault Critical Event Might Be off by One Hour CR 6943957 18 e1000g Driver Generates Spurious ereports When Installing Oracle Solaris OS Over a Sun PCIe Dual Gigabit Ethernet Adapter CR 6958011 18 When diag switch Is Set to true Oracle Solaris OS Fails to Update the EEPROM for Automatic Rebooting CR 6982060 19 sas2ircu Message That RAID Volume Sizes Other Than MAX Are Not Supported CR 6983210 20 Fault Management Sometimes Sends Resolved Cases to the SP CR 6983432 20 Units Used to Define the MIB Power Management Time Limit are Reported in Seconds CR 6993008 2 Spurious Interrupt Message in System Console When Using Oracle VTS CR 7038266 22 Intermittent Link Training Timeout Displayed During Power Cycles CR 7043201 22 iv SPARC T4 1B Server Module Product Notes December 2011 The cfgadm Command Might Fail on SG SAS6 REM Z or SGX SAS6 REM Z HBAs CR 7044759 23 Message From cpustat Refers to Processor Documentation Incorrectly CR 7046898 23 reboot disk Command Occasionally Fails When disk Argument Picks Up Extra Characters CR 7050975 4 PCIe Correctable Errors Might Be Reported CR 7051331 24 Watchdog Timeouts Seen With Heavy Workloads and Maximum Memory Configurations CR 7083001 25 ereport fm fmd module Generated During a Reboot of an SDIO Domain CR 7085231 26 Oracle VTS dtlbtest Hangs When CPU Threading Mode is Set to max ipc CR 7094158 27 Contents v vi SPARC T4 1B Server Modu
6. autres mesures n cessaires son utilisation dans des conditions optimales de s curit Oracle Corporation et ses affili s d clinent toute responsabilit quant aux dommages caus s par l utilisation de ce logiciel ou mat riel pour ce type d applications Oracle et Java sont des marques d pos es d Oracle Corporation et ou de ses affili s Tout autre nom mentionn peut correspondre des marques appartenant d autres propri taires qu Oracle Intel et Intel Xeon sont des marques ou des marques d pos es d Intel Corporation Toutes les marques SPARC sont utilis es sous licence et sont des marques ou des marques d pos es de SPARC International Inc AMD Opteron le logo AMD et le logo AMD Opteron sont des marques ou des marques d pos es d Advanced Micro Devices UNIX est une marque d pos e d The Open Group Ce logiciel ou mat riel et la documentation qui l accompagne peuvent fournir des informations ou des liens donnant acc s des contenus des produits et des services manant de tiers Oracle Corporation et ses affili s d clinent toute responsabilit ou garantie expresse quant aux contenus produits ou services manant de tiers En aucun cas Oracle Corporation et ses affili s ne sauraient tre tenus pour responsables des pertes subies des co ts occasionn s ou des dommages caus s par l acc s des contenus produits ou services tiers ou leur utilisation 9 n 41 Adobe PostScript Contents Using This
7. remains disabled Workaround Manually clear the disabled cache line by typing these commands fmadm repaired fmri label fmadm replaced fmri label 2 Meter USB Cable Length Limit 7048419 The server module has three USB ports m Port 1 and 2 accessible through a dongle that is attached to the front UCP connector m Port 5 located on the rear of the motherboard intended for a USB flash drive Workaround If you connect USB devices to ports 1 or 2 ensure that the cable does not exceed 2 meters approximately 6 5 feet Uncorrectable L2 Cache Errors are Sometimes Reported as Core Faults Without Any Cache Line Retirement CR 7071237 and CR 7071974 When a processor cache line encounters an uncorrectable error the fault manager should retire the cache line that is involved in the error However the fault manager might not succeed in retiring the faulty cache line and instead report the entire core or processor as faulted Workaround Schedule a replacement of the enclosure motherboard For additional information about this issue search for message ID SUN4V 8002 Wy at the Oracle support site http support oracle com During a Reboot After an Unrecoverable Hardware Error CPUs Might Not Start CR 7075336 In rare cases a server or sever module might experience a serious problem that results in a panic When the server or server module is rebooted a number of CPUs might not start even though the CPU
8. with the Oracle VM for SPARC threading mode set to max ipc mode Chapter 2 Known Product Issues 27 28 SPARC T4 1B Server Module Product Notes December 1
9. 050975 When running the reboot disk command extraneous characters are occasionally added to the disk argument before it reaches the OBP This situation results in a failure to boot Recovery Action Repeat the boot request PCIe Correctable Errors Might Be Reported CR 7051331 In rare cases PCle Gen2 devices in the server module might report I O errors that are identified and reported by predictive self healing PSH For example Aug 10 13 03 23 a7d43aeb 61ca 626a f47b c05635f2cf5a PCIEX 8000 KP Major Host Platform Product_sn Fault class Affects FRU dt214 154 ORCL SPARC T3 1B Chassis_id fault io pciex device interr corr 67 fault io pciex bus linkerr corr 33 dev pci 400 pci 1 pci 0 pci c dev pci 400 pci 1 pci 0 pci c pci 0 faulted but still in service SYS MB hc product id ORCL SPARC T3 1B product sn 1052NND107 server id dt214 154 chassis id 0000000 0000000000 serial 1005LCB 1052D9008K part 541 424304 revision 50 chassis 0 motherboard 0 67 FEMO he product id ORCL SPARC T3 1B product sn 1052NND107 server id dt214 154 chassis id 0000000 0000000000 chassis 0 motherboard 0 hostbridge 0 pciexrc 0 pciexbus 1 pciexdev 0 pciexfin 0 pciexbus 2 pciexdev 12 pciexfn 0 pciexbus 62 pciexdev 0 33 Description faulty Too many recovered bus errors have been detected which indicates a problem with the specified bus or with the specified transmitting device This ma
10. 6000 storage modules must be upgraded to firmware revision 5 04 03 or later This firmware revision enables SAS 1 SAS 2 devices to coexist in the Sun Blade 6000 modular system chassis Using older firmware revisions might result in SAS 2 devices hanging Refer to the SAS 1 SAS 2 Compatibility Upgrade Guide for details This guide is available at http www oracle com pls topic lookup ctx E22513 1 Identifying Drive Logical Device Names and Physical Locations The Oracle Solaris OS now uses the worldwide number WWN in place of the target ID field tn in drive logical device names for SAS 2 storage controllers This change affects how you correlate a drive s logical name with the drive s physical location These points are key to understanding the impact of this change Before the change to using WWNs drives were known to the OS by a logical name such as 606080 This logical name mapped to the drive s physical location With the change the device identifier for drives now has this form cnt WWNdn where WWN is a unique hexadecimal value An example of a logical device name is c0t5000C50033438DBBd0 This WWN value does not map in a predictable way to the physical location of the drive SPARC T4 1B Server Module Product Notes December 2011 The OBP and the OS use different WWN numbers to identify a drive This is explained further in Correlate WWN Device Names With Physical Locations diskinfo Command
11. 7 433e 6bf 7 cb53 c3d665e8cd09 SUN4V 8002 6E Sep 16 08 40 47 8191 af875d87 433e 6bf 7 cb53 c3d665e8cd09 FMD 8000 4M Repaired Sep 16 08 40 47 8446 af875d87 433e 6bf 7 cb53 c3d665e8cd09 FMD 8000 6U Resolved 4 Flush the previously faulty component from the host resource cache fmadm flush SYS MB fmadm flushed resource history for SYS MB Chapter 2 Known Product Issues 21 5 Repair the fault in Oracle ILOM faultmgmtsp gt fmadm repair SYS MB faultmgmtsp gt fmadm faulty No faults found faultmgmtsp gt Units Used to Define the MIB Power Management Time Limit are Reported in Seconds CR 6993008 The MIB should report the sunHwCtrlPowerMgmtBudgetTimelimit in milliseconds but the value displayed is in seconds Workaround Understand that the value reported for sunHwCtrlPowerMgmtBudgetTimelimit is in seconds Spurious Interrupt Message in System Console When Using Oracle VTS CR 7038266 During normal operation and when running the Oracle VTS system exerciser you might see this message in the system console date time hostname px ID 781074 kern warning WARNING px0 spurious interrupt from ino 0x3 0x02 or 0x04 Workaround You can safely ignore this message Intermittent Link Training Timeout Displayed During Power Cycles CR 7043201 On occasion during a power cycle the server module might display the following warning message CPU 0 0 0 NOTICE MCUO Link init fai
12. RU faults 7 0 PS11 minimum e 7 0 PS12 7 0 PS13 Note For the most reliable test coverage of the various modular components in the chassis use Oracle VTS 7 0 PS12 or higher Chapter 1 Late Breaking Information 5 Required Patches and Package Updates If you use the preinstalled OS or if you reinstall the OS on the server module you might need to install certain patches or package updates before you put the server module into production Note Oracle Solaris 11 OS uses package updates rather than patches Oracle Solaris 11 OS Package Updates No package updates are required at this time to use Oracle Solaris 11 OS with this server You should install an Oracle Solaris 11 Support Repository Update SRU if one is available Use the pkg command or the package manager GUI to download any available SRU from https pkg oracle com solaris support Oracle Solaris 10 OS Patches TABLE 1 1 Oracle Solaris 10 8 11 OS Required Patches Installation Order OS or Patch 1 Oracle Solaris 10 8 11 OS 2 These mandatory patches e 147440 04 or higher e 147149 01 or higher e 147153 01 or higher e 147707 01 or higher e 147159 03 or higher 3 Recommended OS Patchset Solaris 10 SPARC SPARC T4 1B Server Module Product Notes December 2011 TABLE 1 2 Oracle Solaris 10 9 10 OS and Oracle Solaris 10 10 09 OS Required Patches Installation Order OS or Patch 1 2 3 Oracle Solaris 10 9 10 OS
13. SPARC T4 1B Server Module Product Notes S R SUN Part No E22737 03 ORACLE December 2011 Copyright 2011 Oracle and or its affiliates All rights reserved This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing If this is software or related software documentation that is delivered to the U S Government or anyone licensing it on behalf of the U S Government the following notice is applicable U S GOVERNMENT RIGHTS Programs software databases and related documentation and technical data delivered to U S Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency specific ja ieee oleae regulations As such the use duplication disclosure modification and adaptation shall be subjec
14. SPARC T4 1B Server Module Product Notes December 2011 source valid 1 ttl 0x1 __tod 0x4c058b2e 0x1e8813a0 Workaround You can safely ignore these ereports When diag switch Is Set to true Oracle Solaris OS Fails to Update the EEPROM for Automatic Rebooting CR 6982060 When installing the Oracle Solaris OS while the OBP diag switch parameter is set to true the OS installer fails to update the bootdevice parameter with the new device path where the OS was installed Therefore this new device path will not be used during the subsequent automatic system reboots Under these conditions the server displays these error message and you are unable to reboot from the device Installing boot information Installing boot blocks cxtxdxsx Installing boot blocks dev rdsk cxtxdxsx Updating system firmware for automatic rebooting WARNING Could not update system for automatic rebooting On previous servers and server modules the OBP diag device parameter used to set the new device path to the boot device when the diag switch parameter was set to true On SPARC T4 servers and server modules the diag device parameter is no longer supported and the Oracle Solaris OS installer warns that setting the OBP boot device parameter is not possible Workaround From the Oracle ILOM prompt set the OBP diag switch parameter to false gt set HOST bootmode script setenv diag switch false Alter
15. booted see Correlate WWN Device Names With Physical Locations probe scsi all Command on page 10 If your OS does not provide the diskinfo command refer to the SPARC and Netra SPARC T4 Series Servers Administration Guide for alternative methods 1 Log into the OS 2 Type diskinfo a Enclosure path 1114BD0ACC physical hba 0 Chapter 1 Late Breaking Information 9 Chassis Serial Number 1114BDOACC physical hba 0 Chassis Model ORCL SPARC T4 1B Label Disk name Vendor Product Vers SYS HDDO c0t5000C50033438DBBd0 SEAGATI ST930003SSUN300G 0B70 SYS HDD1 c0t5000C50005C15803d0 SEAGATI ST930003SSUN300G 0468 3 Use the output under the Label and Disk Name columns to correlate a drive s physical location with its corresponding logical device name For this server module m SYS HDDO represents a drive in slot 0 m SYS HDD1 represents a drive in slot 1 In this example the drive installed in slot 0 has a logical device name of c0t5000C50033438DBBd0 Note The diskinfo command provides a variety of disk information depending on the command options you specify For more information type diskinfo hand refer to the diskinfo 1M man page V Correlate WWN Device Names With Physical Locations probe scsi all Command If you have access to the OS you might be able to use the diskinfo command instead See Correlate WWN Device Names With Physical Locations diskinfo Command
16. dule Sun Blade X6275 M2 server module Sun Blade Storage Module M2 To determine your chassis version see Identify Your Chassis Version on page 2 V Identify Your Chassis Version View the CMM on the rear of the modular system chassis 17 111 CCCCCCCCCCCOCCODCCEOCC i CCCCCCCCCC kB i Di i a CCCOCCCCCCCC Left CMM on the previous model A90 B chassis Right CMM on the latest model A90 D chassis For more details about the chassis refer to the Sun Blade 6000 modular system documentation 2 SPARC T4 1B Server Module Product Notes December 2011 Supported Hardware Components Hardware Component NEMs NEM 7100091 or 7011713 Sun Blade 6000 Virtualized 40 GbE NEM NEM 2073A Sun Blade 6000 Ethernet Switched Network Express Module 24p 10GbE NEM NEM 4338A Sun Blade 6000 Virtualized Multi Fabric 10GbE M2 NEM NEM 4250A Sun Blade 6000 Network Express Module 10 port 1 GbE Pass Through NEM REMs REM SG X SAS6 REM Z Sun StorageTek 6 Gb SAS REM HBA FEMs FEM 7100283 or 7100633 PCI E Pass Through FEM FEM X4871A Z Sun Dual 10GbE PCIe 2 0 FEM Description Requires For 1GbE connectivity no FEM required e For 10GbE connectivity FEM 7100283 or 7100633 For SAS2 storage connectivity REM SG or SGX SAS6 REM Z This NEM s documentation is at http www oracle com pls topic lookup ctx E21077 01 Requires
17. e access to or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services Oracle Corporation and its affiliates will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services Copyright 2011 Oracle et ou ses affili s Tous droits r serv s Ce logiciel et la documentation qui Pon pa sont pies par les lois sur la propri t intellectuelle Ils sont conc d s sous licence et soumis des restrictions d utilisation et de divulgation Sauf disposition de votre contrat de licence ou de la loi vous ne pouvez pas copier reproduire traduire diffuser modifier breveter transmettre distribuer exposer ex cuter publier ou afficher le logiciel m me partiellement sous quelque forme et par uelque proc d que ce soit Par ailleurs il est interdit de proc der a toute ing nierie inverse du logiciel de le d sassembler ou de le d compiler except a es fins d interoperabilit avec des logiciels tiers ou tel que prescrit par la loi Les informations fournies dans ce document sont susceptibles de modification sans pr avis Par ailleurs Oracle Corporation ne garantit pas qu elles soient exemptes d erreurs et vous invite le cas ch ant a lui en faire part par crit Si ce
18. eled Host watchdog expired you are experiencing this issue Workaround Contact your authorized service provider to see if a fix is available There are two ways you can work around this issue m You can extend the watchdog period by adding this entry to the Oracle Solaris etc systen file set watchdog_timeout 60000 This extends the watchdog timeout period to 1 minute 60000 milliseconds Chapter 2 Known Product Issues 25 In extreme cases you can disable the watchdog timeout altogether by adding this entry to the etc systen file set watchdog_enabled 0 Whenever you modify the etc system file you must reboot the system for the changes to take effect If you do not want to reboot the system immediately after editing etc system you can apply an additional temporary workaround that takes effect immediately To apply this temporary workaround as root type psrset c F 0 This command creates a temporary processor set containing only CPU 0 preventing application workloads from using this processor and preventing this issue from occurring Note If any threads were bound to CPU 0 they will be unbound This temporary processor set is removed on the next operating system reboot at which point the etc system file workaround takes effect ereport fm fmd module Generated During a Reboot of an SDIO Domain CR 7085231 The server module might generate an ereport fm fmd module message duri
19. ical device name is c0t5000c50033438dbbd0 Oracle Solaris Jumpstart WWN Syntax The Oracle Solaris syntax requires all WWN alpha characters to be capitalized Note Only the WWN portion of the logical device name requires capitalized alpha characters The 60 and d0 portion are not capitalized Chapter 1 Late Breaking Information 11 This Jumpstart profile example shows how to use the WWN syntax when installing the OS on a specific drive install type flash_ install boot_device c0t5000C50033438DBBd0 preserve archive_location nfs 129 148 94 249 export install media solaris builds s10u9 flar la test flar Disk layouts partitioning explicit filesys rootdisk s0 free filesys rootdisk s1 8192 swap Interactive Installation Example In an interactive installation you are asked to specify one or more drives as the targets for the OS installation This step ensures that sufficient storage capacity is provided for the installation Specify the drive with the WWN value that corresponds to the drive on which you want to install the software These WWN values are illustrated in the following interactive example The drive selected as the installation target is located in drive slot 0 the default boot location Note If you prefer to use some other disk specify it instead of the one in HDD slot 0 _ Select Disks On this screen you must select the disks for installing Solaris software Start by loo
20. king at the Suggested Minimum field this value is the approximate space needed to install the software you ve selected Keep selecting disks until the Total Selected value exceeds the Suggested Minimum value NOTE denotes current boot disk Disk Device Available Space c0t5000C50005C15803d0 286090 MB X c0t5000C50033438DBBd0 286090 MB F4 to edit Total Selected 286090 MB 12 SPARC T4 1B Server Module Product Notes December 1 Suggested Minimum 5032 MB Esc 2_Continue F3_Go Back F4 Edit F5 Exit F6_Help Note You might need to label new and replacement drives using the format utility before you can install the OS on the drives Chapter 1 Late Breaking Information 13 14 SPARC T4 1B Server Module Product Notes December 1 CHAPTER 2 Known Product Issues These sections describe known issues for the server module Hardware Issues on page 15 Firmware OS and Other Software Issues on page 17 Hardware Issues These are the known hardware issues and workarounds Sun Type 6 Keyboards are Not Supported by SPARC T4 Series Servers Sun Type 6 keyboards cannot be used with SPARC T4 series servers PSH Might Not Clear a Retired Cache Line on a Replaced Motherboard CR 7031216 When the enclosure is replaced to repair faulty cache on the motherboard PSH might not clear the cache on the replacement The cache line
21. le Product Notes December 2011 Using This Documentation This document provides important and late breaking information for Oracle s SPARC T4 1B server module Related Documentation on page vii m Feedback on page viii Support and Accessibility on page viii Related Documentation Documentation Links All Oracle products h SPARC T4 1B server h module Sun Blade 6000 h modular system Oracle Integrated h Lights Out Manager networking 190072 Oracle ILOM 3 0 Oracle Solaris OS h and other system software Oracle VTS software h SAS 1 SAS 2 h compatibility ttp www oracle ttp www oracle ttp www oracle ttp www oracle html ttp www oracle ttp www oracle ttp www oracle com documentation com pls topic lookup ctx SPARCT4 1B com pls topic lookup ctx sb6000 com technetwork documentation sys mgmt com technetwork indexes documentation sys_sw com pls topic lookup ctx com pls topic lookup ctx 1 22513 1 vii Feedback Provide feedback on this documentation at http www oracle com goto docfeedback Support and Accessibility Description Links Access electronic support through My Oracle Support Learn about Oracle s commitment to accessibility http support oracle com For hearing impaired http www oracle com accessibility support html http www oracle com us corporate acces
22. led TSO Timeout The server module automatically retries the training sequence operation without error Workaround You can safely ignore this message 22 SPARC T4 1B Server Module Product Notes December 2011 The cfgadm Command Might Fail on SG SAS6 REM Z or SGX SAS6 REM Z HBAs CR 7044759 The cfgadm command might fail on SG SAS6 REM Z or SGX SAS6 REM Z HBA devices cfgadm c unconfigure Slot1 cfgadm Component system is busy try again unconfigure failed WARNING pcieb2 failed to detach driver for the device mpt_sas9 in the Connection Slotl WARNING pcieb2 failed to detach driver for the device mpt_sas9 in the Connection Slotl Workaround Disable the fault management daemon before running the cfgadm unconfigure command svcadm disable fmd ps ef grep fmd cfgadm c unconfigure PCI EMO After completing the cfadm task re enable the fault management daemon svcadm enable fmd Message From cpustat Refers to Processor Documentation Incorrectly CR 7046898 A message displayed by the cpustat command says See the SPARC T4 User s Manual for descriptions of these events Documentation for Sun processors can be found at http www sun com processors manuals The document and website listed in this message are not available Chapter 2 Known Product Issues 23 reboot disk Command Occasionally Fails When disk Argument Picks Up Extra Characters CR 7
23. logiciel ou la documentation qui l accompagne est conc d sous licence au Gouvernement des Etats Unis ou toute entit qui d livre la licence de ce logiciel ou l utilise pour le compte du Gouvernement des Etats Unis la notice suivante s applique U S GOVERNMENT RIGHTS Programs software databases and related documentation and technical data delivered to U S Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency specific Pell os regulations As such the use duplication disclosure modification and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract and to the extent applicable by the terms of the Government contract the additional rights set forth in FAR 52 227 19 Commercial Computer Software License December 2007 Oracle America Inc 500 Oracle Parkway Redwood City CA 94065 Ce logiciel ou mat riel a t d velopp pour un usage g n ral dans le cadre d applications de gestion des informations Ce logiciel ou mat riel n est pas con u ni n est destin tre utilis dans des applications risque notamment dans des applications pouvant causer des dommages corporels Si vous utilisez ce logiciel ou mat riel dans le cadre d applications dangereuses il est de votre responsabilit de prendre toutes les mesures de secours de sauvegarde de redondance et
24. natively you can set this parameter at the OBP ok prompt ok setenv diag switch false Chapter 2 Known Product Issues 19 sas2ircu Message That RAID Volume Sizes Other Than MAX Are Not Supported CR 6983210 If you attempt to create a RAID volume smaller than MAX the following series of messages is returned You are about to create an IR volume WARNING Proceeding with this operation may cause data loss or data corruption Are you sure you want to proceed YES NO yes WARNING Volume created with size other than MAX is not supported Do you want to continue with volume creation YES NO n SAS2IRCU you must answer YES or yes to proceed operation aborted SAS2IRCU Error executing command CREATE RAID volumes smaller than MAX are not supported However if you want to create a volume below MAX size for nonproduction use the software allows you to do so This situation is not clear from the message Workaround Ignore the messages and answer yes for the question Do you want to continue with volume creation YES NO Fault Management Sometimes Sends Resolved Cases to the SP CR 6983432 Previously diagnosed and repaired PSH faults from the host reappear in Oracle ILOM when the host reboots An incorrect report of a PSH diagnosed fault appears in the Oracle ILOM CLI and web interface and the fault LED illuminates You can identify this issue by checking to see if the same PSH fa
25. ng a reboot of an SDIO domain This ereport indicates that an error occurred on one of the fmd modules but the fmdump command does not display a valid message msg For example fmdump eV c ereport fm fmd module TIME CLASS Sep 27 2011 06 27 19 954801492 ereport fm fmd module nvlist version 0 version 0x0 class ereport fm fmd module detector embedded nvlist nvlist version 0 version 0x0 scheme fmd 26 SPARC T4 1B Server Module Product Notes December 1 authority embedded nvlist nvlist version 0 version 0x0 product id ORCL SPARC T4 1B server id c193 133 end authority mod name etm mod version 1 2 end detector ena 0x425fc9b065404001 msg cannot open write only transport lt ttl 1 tod 0x4e81cf37 0x38e91d54 Workaround You can safety ignore ereport fm fmd module ereports Oracle VTS dtlbtest Hangs When CPU Threading Mode is Set to max ipc CR 7094158 This issue is fixed in Oracle VTS 7 0 PS13 The Oracle VTS processor test called dt lbtest hangs when Oracle VM for SPARC max ipc threading mode is set This issue is not specific to any processor type and happens when both the following cases are true Only one CPU or strand per core is enabled or online The total number of online CPU per strand is less than or equal to 128 Workaround Do one of the following Update to Oracle VTS 7 0 3 Do not run the Oracle VTS dtlbtest
26. ng of the potential for specific FRU faults Oracle VTS 7 0 PS11 usr sunvts Provides hardware validation tests The preinstalled OS is ready to be configured at the appropriate point when you first apply power to the server Review Required Patches and Package Updates on page 6 to find out if the preinstalled OS requires package updates You can reinstall the OS and install patches instead of using the preinstalled OS See Supported Versions of the OS Firmware and Software on page 5 Refer to the Oracle Solaris documentation for instructions on installing and configuring the Oracle Solaris OS 4 SPARC T4 1B Server Module Product Notes December 2011 Supported Versions of the OS Firmware and Software Software Supported Versions Host OS System firmware Oracle VM Server for SPARC LDoms Oracle Electronic Prognostics EP Oracle VTS e Oracle Solaris 11 OS e Oracle Solaris 10 8 11 OS requires mandatory patches e Oracle Solaris 10 9 10 OS requires patches e Oracle Solaris 10 10 09 OS requires patches For OS patch and package update information see Required Patches and Package Updates on page 6 For information about the preinstalled OS see Preinstalled Software on page 4 8 1 2 b or later includes Oracle ILOM 3 0 2 1 plus patches The patches are included and preinstalled on the preinstalled OS 1 2 This software provides early warning of the potential for specific F
27. or Oracle Solaris 10 10 09 OS Solaris 10 8 11 Patch Bundle 13058415 These mandatory patches 147440 04 or higher 147149 01 or higher 147153 01 or higher 147707 01 or higher 147159 03 or higher Recommended OS Patchset Solaris 10 SPARC Note For current information about required patches and updates for optional hardware and software refer to the documentation for each product Obtain Patches 1 Sign into My Oracle Support http support oracle com Select the Patches amp Updates tab Search for a patch using the Patch Search panel When searching for a patch using the Patch Name or Number field you must specify the complete name or number of the patch For example Solaris 10 8 11 Patch Bundle m 13058415 m 147159 03 To search using a patch number without the revision number two last digits use in place of the revision number For example 14159 Once you locate the patch access the README and download the patch from the site The patch README provides the patch installation instructions Chapter 1 Late Breaking Information 7 Important Firmware Upgrade Required Prior to Mixing SAS 1 and SAS 2 Components Before you insert a SAS 2 component into the chassis you must upgrade the firmware of your SAS 1 components SAS 1 NEMs and storage modules to a firmware version that supports SAS 1 SAS 2 coexistence At a minimum all SAS expanders for SAS 1 NEMs and Sun Blade
28. s are not faulty Here is an example of the type of error displayed rebooting Resetting ERROR 63 CPUs in MD did not start 16 SPARC T4 1B Server Module Product Notes December 2011 Workaround Log into Oracle ILOM on the SP and power cycle the host gt stop SYS Are you sure you want to stop SYS y n y Stopping SYS gt start SYS Are you sure you want to start SYS y n y Starting SYS Blue LED on Drive Does Not Light When the Drive is Ready to Remove CR 7082700 When you attempt to unconfigure a drive for removal the drive s blue LED which indicates the drive is ready for removal might not light This situation occurs after you replace a drive in a slot with a drive that has a different WWID Workaround If you inserted a drive after booting the server reboot the server for the blue LED to work properly Firmware OS and Other Software Issues The following notes describe know issues for the firmware OS and other software fault memory memlink uc Fault Did Not Cause Panic as Stated by System Message CR 6940599 When 8 fault memory memlink uc interconnect fault is detected the server should shut down to protect memory integrity On intermittent occasions this fault has been reported during boot operations without the server shutting down Although this irregular behavior might indicate that the system was able to recover from the memory link error and restore a healthy boo
29. sibility index html viii SPARC T4 1B Server Module Product Notes December 2011 CHAPTER 1 Late Breaking Information These sections provide important information and late breaking news about the server module Supported Chassis on page 1 Supported Hardware Components on page 3 Preinstalled Software on page 4 Supported Versions of the OS Firmware and Software on page 5 Required Patches and Package Updates on page 6 Important Firmware Upgrade Required Prior to Mixing SAS 1 and SAS 2 Components on page 8 Identifying Drive Logical Device Names and Physical Locations on page 8 Supported Chassis Several versions of the Sun Blade 6000 modular system have been available The latest two versions support SAS 1 and SAS 2 modular components Gen2 capable PCIe EMs and NEMs connected to this server module through the chassis run at Gen2 speeds Genl capable devices run at Gen1 speeds This server module is supported in the following chassis models Latest model A90 D Sun Blade 6000 modular system Requires CMM software release 4 0 or later m Previous model A90 B Sun Blade 6000 modular system Requires CMM software release 3 3 or later This server module is only supported in this modular system with these modular components SPARC T3 1B server module Sun Blade T6320 server module Sun Blade T6340 server module Sun Blade X6270 M2 server module Sun Blade X6270 server mo
30. t to the restrictions and license terms set forth in the applicable Government contract and to the extent applicable by the terms of the Government contract the additional rights set forth in FAR 52 227 19 Commercial Computer Software License December 2007 Oracle America Inc 500 Oracle Parkway Redwood City CA 94065 This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerous applications including applications which may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate fail safe backup redundancy and other measures to ensure its safe use Oracle orporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are trademarks or Fine trademarks of SPARC International Inc AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices UNIX is a registered trademark of The Open Group This software or hardware and documentation may provid
31. t up state the safest course is to power down then power up the server Chapter 2 Known Product Issues 17 Recovery Action Log into Oracle ILOM on the SP power cycle the host gt stop SYS Are you sure you want to stop SYS y n y Stopping SYS gt start SYS Are you sure you want to start SYS y n y Starting SYS Timestamp for an Oracle ILOM Fault Critical Event Might Be off by One Hour CR 6943957 The timestamp reported in an email generated in an Oracle ILOM fault critical event might be one hour later than the timestamp recorded in the event log Workaround Check the timestamp recorded in the event log If that timestamp does not match the timestamp reported in the email use the event log time e1000g Driver Generates Spurious ereports When Installing Oracle Solaris OS Over a Sun PCIe Dual Gigabit Ethernet Adapter CR 6958011 When installing the Oracle Solaris OS on domains controlled through Sun PCIe Dual Gigabit Ethernet UTP or MMF adapters the e1000g driver might generate false error reports on the static direct I O SDIO and primary domains For example date time ereport io pciex tl ca nvlist version 0 ena 0x298a9f62243802 ena 0x298a9f62243802 detector embedded nvlist nvlist version 0 scheme dev device path 1 end detector class ereport io pciex tl ca dev status 0x2 ue status 0x8000 ue severity 0x62030 adv ctl Oxf source id 0x600 18
32. ult was also reported from the host If the fault was reported only by Oracle ILOM and not from the host it is probably an example of this issue Recovery Action Use the Oracle ILOM diagnostic and repair tools to identify the error condition and correct it This example illustrates how to diagnose and repair a PSH fault diagnosed by the host This example is based on the Oracle ILOM fault management shell You could instead use the Oracle ILOM CLI or web interface to accomplish the same results 20 SPARC T4 1B Server Module Product Notes December 1 1 Display the fault information faultmgmtsp gt fmadm faulty 2011 09 16 15 38 19 af875d87 433e 6bf 7 cb53 c3d665e8cd09 SUN4V 8002 6E Major Fault class fault cpu generic sparc strand FRU SYS MB Part Number 7015272 Serial Number 465769T 1130Y6004M Description A fault has been diagnosed by the Host Operating System Response The service required LED on the chassis and on the affected FRU may be illuminated Impact No SP impact Check the Host OS for more information Action The administrator should review the fault on the Host OS Please refer to the Details section of the Knowledge Article for additional information 2 Check for faults on the host fmadm fault lt Host displays no faults 3 Verify that the fault shown by Oracle ILOM was repaired on the host fmdump TIME UUID SUNW MSG ID Sep 16 08 38 19 5582 af875d8
33. y degrade into an unrecoverable fault Refer to http sun com msg PCIEX 8000 KP for more information 24 SPARC T4 1B Server Module Product Notes December 2011 Response Impact Action One or more device instances may be disabled Loss of services provided by the device instances associated with this fault If a plug in card is involved check for badly seated cards or bent pins Otherwise schedule a repair procedure to replace the affected device Use fmadm faulty to identify the device or contact Sun for support These errors might be an indication of a faulty or incorrectly seated PCI EM Or these errors might be erroneous Workaround Ensure that the PCI EM is properly seated and functioning If the errors continue apply the Oracle Solaris 10 8 11 OS patch 147705 01 or higher Watchdog Timeouts Seen With Heavy Workloads and Maximum Memory Configurations CR 7083001 With certain unusual heavy workloads especially where a highly processor intensive workload is bound to cpu 0 the host might appear to suddenly reset back to OBP without any sign of there having been a crash or a panic The Oracle ILOM event log contains a host watchdog expired entry The problem is more likely to occur on systems with full memory configurations If you see this sort of sudden reset display the SP event log using this command from the Oracle ILOM CLI gt show SP logs event list If you see an entry lab
Download Pdf Manuals
Related Search