Home

Sun SPARC Enterprise T5120 and T5220 Servers Product Notes

1. It is now safe to unload the nxge driver 20 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Temporary PCIe Link Failure During Boot Causes a Fatal Error Later CR 6553515 If a temporary PCle link failure occurs during boot or any time later the system could fail If the link is up and working again before the firmware gets control the error is a problem in firmware handling the leftover status The following is an example of the error message 0 ok 4000 dload users bog rustn2obp_0502 Boot device pci 0 pci 0 pci 1 pci 0 pci 2 network 0 users bog rustn2obp_0502 File and args FATAL pci 0 pci 0 pci 1 pci 0 pci 2 network 0 Last Trap Non Resumable Error TL 1 STL 1 STT 7 STPC 0238978 TnPC 023897c TSTATE 820001600 CWP 0 SPSTATE 16 AG 0 IE 1 PRIV 1 AM 0 PEF 1 RED 0 MM 0 TLE 0 CLE 0 MG 0 IG 0 SAST 20 CCR 8 XCC nzvc ICC Nzvc STL 2 STT 3 STPC 024327c STnPC 0243280 TSTATE 14414000400 CWP 0 SPSTATE 4 AG 0 IE 0 PRIV 1 AM 0 PEF 0 RED 0 MM 0 TLE 0 CLE 0 MG 0 IG 0 SAST 14 CCR 44 XCC nZvc ICC nZvc Normal GL 1 0s 0 0 1 0200000 0 2 0200000 0 3s ff f78000 0 4 fec320fc 3ffe60000 5 02833e4 3ffe60000 6 fee826c8 3ffe60600 IE fee817d8 02432bc SP 0238978 nPC 023897c STBA 0200000 CCR 8200016 XCC nzvC ICC nZVc 0 ok Workaround If the system fails to boot because of this problem retry booting Chapter 2 Late Break
2. Cool Tools on page 5 Manages Logical Domains See Logical Domains on page 6 Data collection utility See Sun Explorer Utility on page 6 Sun Studio Developer Tools See Sun Studio C C amp Fortran Compilers and Tools on page 7 4 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 TABLE 1 3 Preloaded Software Software Location Function Sun Java Enterprise var spool stage JES5 Solaris_sparc Software that provides middleware System 5 U1 services that optimize network applications Solaris 10 OS and Solaris Live Upgrade The Solaris 10 OS is completely installed on your system including everything installed by the Entire Distribution plus OEM support option This software includes all the locales supported by this Solaris release In addition some patches are preinstalled on your server See Mandatory Patch Information on page 8 Note Some software that is provided in the Solaris 10 8 07 media kit has not been installed on your system If you want to use the additional software obtain the full media kit for this Solaris release and install software from the included discs Order the appropriate media kit for the version preinstalled on your system Your server is configured with a liveupgrade partition on Slice 3 that contains a duplicate of the Solaris OS core only The liveupgrade partition is known as an alternate boot environment ABE This t
3. 6585292 Some extraneous and misleading warning Ignore the extraneous warning messages messages are displayed in the output of the ILOM reset SP command and of the ALOM CMT compatibility resetsc command For an except of the misleading messages see Resetting the SP Produces Extraneous Warning Messages CR 6585292 on page 38 6585340 The uadmin 2 0 and reboot commands read See The uadmin 2 0 and reboot Commands old bootmode settings Read old Bootmode Settings CR 6585340 on page 36 6587869 Using the consolehistory e command with To see the entire consolehistory log use the a value greater than 1000 might result in the SP becoming unusable v option If you need to recover from problems related to running the consolehistory command with more than 1000 lines reboot the SP Chapter 2 Late Breaking Issues 29 TABLE 2 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6587919 The first time that show SYS is executed after Use the show SYS command again and the a power on none is displayed for the product product name is displayed name 6588999 When you connect to the ILOM CLI with SSH This error can be ignored The command and the SP is reset you might see an error actually succeeds and the SP is reset When the message similar to the following SP resets you lose the SSH connection to the SP Performing hard reset on SP failed reset Transport error check errno for transport erro
4. ERROR POST timed out Not all system components tested The system continues to boot but in a degraded state During the boot process the following error messages are displayed WARNING Unable to connect to Domain Service providers WARNING Unable to get LDOM Variable Updates WARNING Unable to update LDOM Variable Any programs or services that depend on an LDC channel run in a degraded state or not at all Some programs that require LDC to function are 1dmd fmd and eeprom Changes to OpenBoot PROM variables with nondefault LDoms configuration do not persist If an LDoms variable is set to a nondefault value when an LDoms configuration is saved to the service processor and then later changed back to its default value the change to its default value will not persist after a power cycle The ldm set variable command allows you to set an LDoms variable to any arbitrary string If an LDoms variable is set to a value that is not valid the OpenBoot firmware issues a warning message during boot with a list of correct values but without giving the name of the variable in question XAUI and CPU resources added after initial LDoms Setup are not available to LDoms Manager If the following error is observed on the console during boot power cycle the system and ensure that POST runs to completion You can also boot without running POST Save the SP configuration after changing an LDoms variable Example ldm remo
5. Message Queue Web Server m Availability services Sun Cluster Sun Cluster Agents For an overview and documentation visit the following web sites http www sun com service javaes index xml http docs sun com app docs prod entsys 5 If it becomes necessary to reload the software go to the following web site for download and installation instructions http www sun com software preinstall Chapter 1 Important Information About the Sun SPARC Enterprise T5120 and T5220 Servers 7 Note If you download a fresh copy of software that software might not include patches that are mandatory for your server After installing the software see Mandatory Patch Information on page 8 for a procedure to check for the presence of patches on the system Mandatory Patch Information Before contacting support ensure that all mandatory patches are installed on your server In addition to installing these patches check the SunSolves web site on a regular basis for the availability of new patches Patches are available at http sunsolve sun com TABLE 1 4 lists the mandatory patches for your server These patches are already installed in the preinstalled Solaris OS If you reinstall the OS you must reinstall these patches TABLE 1 4 Mandatory Patches for Both Servers For All Supported OS Versions Patch IDs Description Fixes Provided 127753 01 or later System panics with These patches fix Change Request CR 6590132 n
6. dans les pr sentes correspondent aux garanties express ment stipul es dans le contrat de licence r gissant le produit ou la technologie fourni e SAUF MENTION CONTRAIRE EXPRESSEMENT STIPULEE DANS CE CONTRAT FUJITSU LIMITED SUN MICROSYSTEMS INC ET LES SOCIETES AFFILIEES REJETTENT TOUTE REPRESENTATION OU TOUTE GARANTIE QUELLE QU EN SOIT LA NATURE EXPRESSE OU IMPLICITE CONCERNANT CE PRODUIT CETTE TECHNOLOGIE OU CE DOCUMENT LESQUELS SONT FOURNIS EN L TAT EN OUTRE TOUTES LES CONDITIONS REPRESENTATIONS ET GARANTIES EXPRESSES OU TACITES Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALIT MARCHANDE L APTITUDE UNE UTILISATION PARTICULI RE OU L ABSENCE DE CONTREFA ON SONT EXCLUES DANS LA MESURE AUTORIS E PAR LA LOI APPLICABLE Sauf mention contraire express ment stipul e dans ce contrat dans la mesure autoris e par la loi applicable en aucun cas Fujitsu Limited Sun Microsystems Inc ou l une de leurs filiales ne sauraient tre tenues responsables envers une quelconque partie tierce sous quelque th orie juridique que ce soit de tout manque gagner ou de perte de profit de probl mes d utilisation ou de perte de donn es ou d interruptions d activit s ou de tout dommage indirect sp cial secondaire ou cons cutif m me si ces entit s ont t pr alablement inform es d une telle ventualit LA DOCUMENTATION EST FOURNIE EN L ETAT ET TOUTES AUTRES CONDITIONS DECLARATIONS ET GARAN
7. pH oO D D H At this point the problem might have been encountered This problem will prevent future PSH events for example new hardware errors correctable or uncorrectable from being transported into the domain and properly diagnosed Workaround After the domain recovers and the diagnosis message is printed to the Solaris console reset the service processor as follows sc gt resetsc y ALOM CMT compatibility CLI OR gt reset SP ILOM CLI Once the SP is restarted and you are able to log in as the admin which means all daemons are ready type the following in the Solaris control domain fmadm unload etm fmadm load usr platform sun4v 1lib fm fmd plugins etm so Chapter 2 Late Breaking Issues 49 TABLE 2 6 LDoms Related Issues TABLE 2 6 lists the late breaking LDoms related issues Additional information for some of the change request CR issues is provided following the table LDom Related Issues CR Description Workaround 6540368 6543749 6567748 In Logical Domains 1 0 1 software there are a few cases where variable updates do not persist A guest domain wanboot miniroot download could take more than 30 minutes During boot or installation over wide area networks the time it takes to download the miniroot could significantly increase when using a virtual network device This performance degradation is relevant only when trying to boot or install over
8. Dropping CR 6554478 22 v To Set the MTU Size to 8172 22 Ierrs Generated When 100Mb Full With Forced Speed Duplex Is Set in e1000g conf CR 6555486 24 Setting Properties for nxge Devices Might Fail CR 6561389 25 Server Might Panic in nxge_start When dupb Fails CR 6567838 25 v To Disable Jumbo Frames 25 v To Set the MTU toa Smaller Size 26 Firmware ILOM POST and SP Issues 27 Problem When the PCIe Link Fails to Train as x8 CR 6556505 33 v To Identify the Problem 34 v To Correct the Problem 34 The showfaults Command Shows the Motherboard as Faulty Instead of the DIMM CR 6582853 35 The uadmin 2 0 and reboot Commands Read old Bootmode Settings CR 6585340 36 Communication Channel Between the Primary Domain and the Service Processor SP Might Hang CR 6583567 37 v To Recover From a Domain Crash 37 vi Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Resetting the SP Produces Extraneous Warning Messages CR 6585292 38 Spurious PIU Errors CR 6598381 39 Diagnostic Routine That Runs at Startup IBIST May Accidentally Disconnect the MCU CR 6618773 39 Solaris OS Issues 41 Servers Might Experience Panics Generated From the PCle Root Complex CR 6555956 45 Information Missing From prtpicl and prtdiag Commands CR 6586624 46 Booting the Solaris OS From an External USB DVD ROM Drive Could Cause a Panic CR 6588452 46 The prtdiag v Command Has Formatting Issues CR 6587389 47 PSH E
9. Errata This section describes known errors and corrections to the Sun SPARC Enterprise T5120 and T5220 server documentation Sun SPARC Enterprise T5120 and T5220 Servers Administration Guide Table 2 5 Lists Incorrect Device Identifiers The device identifier SYS MB NETport_number should be replaced with the device identifier SYS MB GBEcontroller_number The device description for SYS MB GBEcontroller_number should be as follows GBE controllers Number 0 1 GBEO controls NETO and NET1 m GBE1 controls NET2 and NET3 In other words replace this row of Table 2 5 Device Identifiers Devices SYS MB NETport_number Ethernet ports Number 0 3 with this row Device Identifiers Devices SYS MB GBEcontroller_number GBE controllers Number 0 1 e GBEO controls NETO and NET1 GBE1 controls NET2 and NET3 Under Table 2 4 in the Bullet List of Default Settings The default value of HOST diag level min The correct default value of diag level should be max Chapter 2 Late Breaking Issues 53 Sun Integrated Lights Out Manager 2 0 Supplement for the Sun SPARC Enterprise T5120 and T5220 Servers Incorrect Default Value Is Specified in the Procedure To Specify the Level of Diagnostics Using the CLI The default value of HOST diag level min The correct default value of diag level should be max Two ILOM Properties that Are not Described in This Manual The following list
10. Firmware updates are available from Sunsolves http sunsolve sun com as patch releases When you update the System Firmware all of the individual firmware components are updated You cannot Chapter 1 Important Information About the Sun SPARC Enterprise T5120 and T5220 Servers 3 update firmware components individually Refer to the Sun SPARC Enterprise T5120 and T5220 Servers Installation Guide for more information about updating the server firmware TABLE 1 2 Preinstalled and Preloaded Software This section describes the following m Preinstalled software TABLE 1 2 that is ready to use m Preloaded software TABLE 1 3 that must first be installed from the preloaded location before you can use it Preinstalled Software Software Location Function Solaris 10 8 07 OS Cool Tools GCC v 4 0 4 LDoms Manager 1 0 1 Sun Explorer Sun Studio 12 Developer Tools The root partition is installed on Slice 0 The core OS is on Slice 3 serving as a Live Upgrade alternate boot environment ABE opt gcc and opt SUNWOscgfss LDoms Manager e opt LDoms_Manager 1_0_1 RR Product e opt SUNW1dm LDoms MIB e opt ldoms_mib e opt SUNW1dmib opt SUNWexplo opt SUNWspro extra bin opt SUNWspro Operating system and alternate boot environment See Solaris 10 OS and Solaris Live Upgrade on page 5 GCC compiler for SPARC systems See Additional Software Available for Your Server
11. Panics Generated From the PCIe Root Complex CR 6555956 on page 45 Chapter 2 Late Breaking Issues 41 TABLE 2 4 Solaris OS Issues Continued CR Description Workaround 6564180 The Solaris OS locator command does not Instead use either the ILOM or ALOM CMT work on this server compatibility locator command as follows e From the ILOM CLI gt show SYS LOCATE gt show SYS LOCATE value off gt show SYS LOCATE value on From the ALOM CMT compatibility CLI sc gt showlocator sc gt setlocator on sc gt setlocator off 6572985 During long SunVTS test runs the SunVTS Install the SunVTS Patch number 127294 01 or cryptotest could fail intermittently with an later error similar to the following cryptotest FATAL n2rng0 SUNW_RANDOM generate failed values generated fall outside statistical tolerance 6578410 The server might hang when trying to boot with Add the following setting to the etc system an Infiniband HBA card installed file set tavor tavor_iommu_bypass 0 6586624 The Solaris prtdiag and prtpicl commands Use alternative methods to obtain the might not display complete information as information you need as described in follows Information Missing From prtpicl and e If the prtdiag v option is specified the prtdiag Commands CR 6586624 on page 46 firmware version and the chassis serial number might not be displayed e The prtpicl command will not always display the physical platform section 6586
12. are none and all In Several Sun SPARC T5120 and T5220 Server Manuals Hard Drive Logical Device Names Differ In the documentation the logical device names for the hard drives are described using cOtxxxx However that might not match the server s logical device names because device names can differ If the system has a DVD drive the logical names of the hard disks will be c1txxxx the DVD is cOtxxxx If the system has no DVD the logical names for the disks are cOtxxxx Chapter 2 Late Breaking Issues 55 56 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008
13. channel is used by a primary domain service or application other than the fault management daemon fmd for example the LDoms Manager 1dmd you might see warning or error messages concerning communication failures In this case the channel can be brought back up by restarting the affected service or application m If the channel is the one used by fma there are no warning or error messages fmd will not receive ereports and diagnosis of the errors does not occur m If the channel is the one used by the Solaris OS to communicate with the SP you could see warning or error messages regarding failure to obtain the PRI failure to access ASR data or failure to set LDoms variables or failure in SNMP communication In this case the channel can be brought back up by resetting the SP If the SP is reset restart the fmd on the primary domain If resetting the SP fails to bring the channel back up then it might also be necessary to reboot the primary domain m If a domain crashes or a service spontaneously restarts without any associated fault messages you must recover as follows to minimize potential loss of error telemetry V To Recover From a Domain Crash 1 Restart fmd on the primary domain 2 Wait 30 seconds 3 Reset the SP with either of the following commands gt reset SP ILOM CLI OR sc gt resetsc y ALOM CMT compatibility CLI Chapter 2 Late Breaking Issues 37 38 4 Restart fmd on the primary domain Enter
14. record of customized variables to values manually modify the firmware variables on the The service manual indicates that moving the new motherboard SCC module to the new motherboard will preserve customized variables but this is not true because not all variables are stored in the SCC module The following variables are stored in the SCC module and will be preserved when the SCC module is moved to a replacement motherboard Host ID e Mac addresses All other variable values will become default values 6610861 The prompt and character sequence for Type the boot command to resume the service and dropping to the u boot state is inconsistent with processor boot sequence 6613564 previous platforms When the service processor is booting pressing a key during the 5 second interval while the prompt Hit any key to stop autoboot is displayed causes the service processor boot sequence to stop and a u boot prompt is displayed Problem When the PCIe Link Fails to Train as x8 CR 6556505 The system could encounter a problem during a power on or reset sequence where the I O bridge PCIe root complex of the UltraSPARC T2 CPU does not train at all or trains at a lane width less than 8 and no error or fault is generated to indicate to the user this problem has been encountered Chapter 2 Late Breaking Issues 33 V To Identify the Problem Though no error or fault is reported it is easy to identify because no PCIe I O devices will be ava
15. show or set the serial port properties of the host port might cause the ILOM CLI to hang and become unresponsive The help message is incorrect in the ILOM BI The informational text displayed on the Configuration Serial Port tab in the ILOM BI refers to a DB 9 connector but the message should refer to the RJ 45 connector A diagnostic routine that runs at startup IBIST might disconnect the memory controller unit MCU resulting in errors For an example of the errors see Diagnostic Routine That Runs at Startup IBIST May Accidentally Disconnect the MCU CR 6618773 on page 39 Power off the host reset the SP and power on the host Do not configure the host serial port properties from the service processor Instead set the properties from the Solaris OS If the ILOM CLI hangs you must reset the system by power cycling the AC power Be aware of this discrepancy Install Patch 127580 04 or later and update the System Firmware to version 7 0 9 or later 32 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 TABLE 2 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6662997 If you change any firmware variables such as Keep a record of any firmware variables that are auto boot keep a record of your changes modified In the event of a motherboard replacement most In the event that the motherboard is replaced of the SP variables will become the default use your
16. showfaults command displays the faulty FRU as the motherboard SYS MB instead of the DIMM or PCle adapter This problem will occur for the following PSH Message IDs MSGID m SUN4V 8000 E2 m SUN4V 8000 D m SUN4 8000 4P m SUN4 8000 A2 m SUN4 8000 75 m SUN4 8000 9J m SUN4 8000 D4 m PCIEX 8000 0A m PCIEX 8000 DJ m PCIEX 8000 HS The following example from the ALOM CMT compatibility CLI illustrates the problem In this example the faulty FRU displayed is the motherboard SYS MB when the actual faulty component is a memory DIMM sc gt showfaults v Last POST Run Jul 13 18 32 11 2007 Post Status Passed all devices ID Time FRU Class Fault 0 Jul 13 19 31 34 SYS MB Host detected fault MSGID SUN4V 8000 DX UUID 7b471945 ceef eea0 c3ad 85ca140be5b2 In addition there is a problem with the output displayed by the show SYS faultmgmt command ILOM CLI The fault_state property of components and the faulted components listed under the Fault Management tab in the ILOM BI are incorrect for the PSH Message IDs listed above Also the FB DIMM fault indicator will not operate and the FRUID for the motherboard will have a fault recorded Workaround Use the Fault Management utilities on the host to find the location of the faulty DIMM s or PCIe adapters Instructions for using these utilities for these faults can be found in the Predictive Self Healing Knowledge Articles located at http www sun com msg MSGI
17. wide area networks using a virtual network device A similar boot or installation using a physical network device works as expected as does a traditional local area net boot or installing from a virtual network device Domain status might not be reported accurately For example the status reported for a domain might be Running when the OS is not running This problem is encountered when the domain status is reported by ILOM BI and CLI and from the ALOM CMT compatibility showplat form command The ambiguity also exists in the ILOM control MIB but not in the Sun platform entity MIB Thus the ambiguous domain status might be visible to third party systems monitoring tools if they monitor this entry For more information refer to the Logical Domains LDoms 1 0 1 Release Notes Be aware of the time needed to boot or perform installations over a wide area network with a virtual network device Ignore the domain status information from all CLIs and BI output as well as from the domain status entry in the ILOM control MIB Retrieve the true status of the domain by accessing the domain console 50 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 TABLE 2 6 CR LDom Related Issues Continued Description Workaround 6592934 6593132 6594395 6597815 In the unlikely event that POST times out before completing its test cycle the firmware issues the following message to the console
18. will be disabled and the proper information will be displayed in the banner 6581309 Console behavior is inconsistent when a If the graphics console appears hung connect to graphics device and keyboard are specified for console use This behavior occurs when the OpenBoot variables input device and output device are set to anything other than the default value of virtual console If the control domain is set this way some console messages are sent to the graphics console and others are sent to the virtual console This situation results in incomplete information on both consoles In addition when the system is halted or a break is sent to the console control is passed to the virtual console which requires keyboard input over the virtual console As a result the graphics console appears to hang the virtual console from the system processor to provide the required input Press Return on the virtual console keyboard once to see the output on the virtual console If this workaround does not work contact Sun Services To prevent the problem perform one of the following workarounds e Install patch ID 137111 01 or higher e Use only the virtual console Ensure that the default value of virtual console is set for both the input device and output device variables 28 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 TABLE 2 3 Firmware ILOM POST and SP Issues Continued CR Description
19. 06950 There is an important etc system setting for If you reinstall the Solaris OS you must add the 10 Gb Ethernet performance Note The preinstalled Solaris OS has the correct entry in the etc systen file following line to the etc systen file set ip ip_soft_rings_cnt 16 This etc system setting ensures optimum performance for 10 Gb Ethernet interfaces Using modunload While the nxge Port Is Running Could Cause a System Panic CR 6551509 If you run the modunload command on the nxge driver while it is running the system could panic Due to an issue in the nxge driver it is possible though very unlikely that the nxge driver could cause a panic during a system reboot This panic occurs if the system is still transferring substantial amounts of network data over an nxge interface while the system is shutting down It is very unlikely that this condition will occur in normal circumstances The panic message is mutex_enter bad mutex The panic stack will include the two nxge driver functions nxge_freeb and nxge_post_page If such a panic occurs the system will recover and continue to reboot normally The system including the nxge interfaces will come back up with no further panics Workaround Unplumb the interfaces prior to unloading the driver Chapter 2 Late Breaking Issues 19 V To Unplumb the Interfaces Prior to Unloading the Driver It is usually not necessary to unload a driver from a running kernel bu
20. 0G for more information AUTO RESPONSE Solaris will attempt to save and diagnose the error telemetry MPACT The system will sync files save a crash dump if needed and reboot REC ACTION Save the error summary below in case telemetry cannot be saved Gl P S D i I Or an unrecoverable error causes the firmware to abort and messages similar to the following are reported to the SP console when logged into the ALOM CMT compatibility CLI console Aug 17 22 09 09 ERROR HV Abort lt Unknown gt 228d74 PowerDown 48 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 After the control domain recovers a diagnosis is performed Messages to the console indicate the cause of the unrecoverable error For example UNW MSG ID SUN4V 8000 UQ TYPE Fault VER 1 SEVERITY Critical VENT TIME Fri Aug 17 18 00 57 EDT 2007 LATFORM SUNW SPARC Enterprise T5220 CSN HOSTNAME wgs48 100 OURCE cpumem diagnosis REV 1 6 VENT ID a8b0eb18 6449 c0a7 cc0f e230a1d27243 ESC The number of level 2 cache uncorrectable data errors has exceeded cceptable levels Refer to http sun com msg SUN4V 8000 UQ for more nformation UTO RESPONSE No automated response MPACT System performance is likely to be affected EC ACTION Schedule a repair procedure to replace the affected resource the identity of which can be determined using fmdump v u lt EVENT_ID gt HN Hun v ta
21. 1 Technical Support and Documentation This section includes where to obtain technical support software and documentation Technical Support If you have any technical questions or issues that are not addressed in the Sun SPARC Enterprise T5120 or T5220 servers documentation contact your local support services representative For customers in the U S or Canada call 1 800 USA 4SUN 1 800 872 4786 For customers in the rest of the world find the World Wide Solution Center nearest you by visiting the web site http www sun com service contacting solution html Documentation Instructions for installing administering and using your servers are provided in the Sun SPARC Enterprise T5120 and T5220 servers documentation sets from the following web sites m http docs sun com app docs prod sparc t5120 m http docs sun com app docs prod sparc t5220 For additional documentation such as documentation for the Solaris OS go to Sun s documentation web site m http www sun com documentation Note Information in these product notes supersedes the information in the Sun SPARC Enterprise T5120 and T5220 documentation sets Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Supported Versions of the OS and Firmware TABLE 1 1 lists supported minimum and preinstalled versions of the Solaris Operating System and System Firmware for the Sun SPARC Enterprise T5120 and T5220 servers Your
22. 2 22 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 3 If you want the system to set the netmask to a special value automatically add the following line in the etc netmasks file using netmask FFFFFFOO as an example 99 99 9 T 255 255 255 0 4 Reboot the system In this example the nxge1 interface is automatically plumbed with IP address 99 99 9 1 MTU value 8172 and netmask F FF F00 5 Run ifconfig a to confirm the configuration ifconfig a nxgel flags 1201000802 lt BROADCAST MULTICAST IPv4 CoS FIXEDMTU gt mtu 8172 index 3 inet 99 99 9 1 netmask ffffff00 broadcast 99 255 255 255 ether 0 14 4f 6c 88 5 If you want to set parameters permanently for other interfaces create etc hostname nxge0 etc hostname nxge2 and etc hostname nxge3 similarly and add the name IP address pairs to the same etc hosts file Also add their netmasks to the same etc netmasks file Chapter 2 Late Breaking Issues 23 Terrs Generated When 100Mb Full With Forced Speed Duplex Is Set in e1000g conf CR 6555486 Ierrs can be caused by the ForcedSpeedDuplex parameter The following code output shows an example of implementing the workaround in the e1000g conf file In this example the e1000g0 device is configured for 100Mb full duplex using autonegotiation ForceSpe dDupl xe7 1 ie e Vie lg dy Ty ed ply hi This will force Speed and Duplex for following settings for a typical instanc
23. 2cp alignment System panics n2cp alignment error in IPsec error testing 127741 01 or later Data integrity in the Fixes issues reported by Sun Alert ID 103076 nxge driver 127745 01 or later IPsec performance Fixes CR 6568352 IPsec performance does not scale using hardware crypto providers To determine if a patch is present see To Download Patches on page 8 V To Download Patches 1 Determine whether the patches have been installed on your system For example use the showrev command for each patch number showrev p grep Patch 127753 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 m If you see patch information listed for the queried patch and the dash extension the last two digits matches or exceeds the required version your system has the proper patches already installed and no further action is required For example if patch 127753 01 or later is installed your system has the required version of this patch m If you do not see patch information listed for the queried patch or if the dash extension precedes the required version go to Step 2 For example if no version of the 127753 patch is displayed you must download and install the patch The last two digits of the patch ID represent the revision of the patch 2 Go to http sunsolve sun com to download the patches Using the SunSolve PatchFinder tool specify the base Patch ID number the first six digits t
24. 847 The Solaris prtdiag command without the v Use the v option when running the prtdiag option does not show failures in the output command 6587380 The Solaris prtdiag v command displays non Be aware that the voltage and nonvoltage voltage information in the voltage indicator section information such as PSO TEMP_FAULT is accurate and represents the current condition of the components 42 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 TABLE 2 4 Solaris OS Issues Continued CR Description Workaround 6587389 The Solaris prtdiag v command might Instead use the showenvironment command display information with missing spaces from the ALOM CMT compatibility CLI as making the output difficult to read follows sc gt showenvironment For more details see The prtdiag v Command Has Formatting Issues CR 6587389 on page 47 6588452 Booting the Solaris OS from an external USB Use the built in DVD drive or use a drive whose DVD ROM drive could cause a panic and fail to subclass is not 2 3 or 4 boot For more information see Booting the Solaris OS From an External USB DVD ROM Drive Could Cause a Panic CR 6588452 on page 46 6588499 A Solaris OS shutdown might hang and result in Reboot the system by dropping to the service fewer system services processor SP Then power cycle the host Rarely a shutdown performed immediately after System using one of the following methods the Solaris OS boo
25. AND THEIR AFFILIATES MAKE NO REPRESENTATIONS OR WARRANTIES OF ANY KIND EXPRESS OR IMPLIED REGARDING SUCH PRODUCT OR TECHNOLOGY OR THIS DOCUMENT WHICH ARE ALL PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID Unless otherwise expressly set forth in such agreement to the extent allowed by applicable law in no event shall Fujitsu Limited Sun Microsystems Inc or any of their affiliates have any liability to any third party under any legal theory for any loss of revenues or profits loss of use or data or business interruptions or for any indirect special incidental or consequential damages even if advised of the possibility of such damages DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID Sd mon Ca Adobe PostScript Copyright 2008 Sun Microsystems Inc 4150 Network Circle Santa Clara California 95054 Etats Unis Tous droits r serv s Revue technique fournie par FUJITSU LIMITED sur des parties de ce mat riel Sun Microsystems Inc et Fuj
26. B PCIE I0 USB component_state Enabled Chapter 2 Late Breaking Issues 45 Using the ALOM CMT compatibility CLI sc gt enablecomponent SYS MB PCIE IO USB Information Missing From prtpicl and prtdiag Commands CR 6586624 The prtdiag command might not display environmental and FRU status If the v option verbose is specified the firmware version and the chassis serial number might not be displayed In addition the prtpicl command might not display the physical platform section Use one of the following alternative methods to obtain missing information a Alternative for the prtdiag command Use the following ALOM CMT compatibility CLI commands sc gt showenvironment displays the system s environmental status sc gt showfru component NAC displays a component s FRU status sc gt showplatform displays the Chassis Serial Number sc gt showhost displays the firmware version m Alternative for the prtpicl command Walk through the targets of the show SYS command with the ILOM CLI and the ILOM graphical user interface Refer to the Sun Integrated Lights Out Manager ILOM 2 0 User s Guide for details Booting the Solaris OS From an External USB DVD ROM Drive Could Cause a Panic CR 6588452 Booting the Solaris 10 OS from an external USB DVD ROM drive could panic the server and fail to boot the OS This situation happens because the Solaris OS names the device storage 1 and the System Firmware na
27. D Chapter 2 Late Breaking Issues 35 where MSGID is one of the PSH Message IDs listed in the bulleted list in this section and displayed by the ALOM showfaults command For faulty DIMMs refer to the DIMM label on the air duct or system cover to verify the DIMM location Once the faulty DIMM is replaced and the PSH fault has been cleared the entry in showfaults will be deleted and the fault recorded in the motherboard FRUID will be cleared The uadmin 2 0 and reboot Commands Read old Bootmode Settings CR 6585340 You can change LDoms variables in the control domain in one of three ways with the OpenBoot setenv command in the control domain with the Solaris eeprom command in the control domain or using ILOM bootmode bootscript option Changes made with the setenv and eeprom commands take effect immediately Changes made with the bootmode command are supposed to take effect on the next reset no matter what kind of reset it is Changes made in any of these three ways are supposed to stay in effect until the next change That is it doesn t matter how the value of an LDoms variable is changed Once changed the value is supposed to stay in effect until it is changed again However due to this issue changes made with the bootmode command will become effective only after a power on reset and will on every reset other than a power on reset that follows override any intervening change made with the setenv or eeprom commands That
28. M modules and CPU cores and the following messages are reported to the console Chapter 2 Late Breaking Issues 39 40 For example Chassis disabled Fault 2007 Chassis Chassis major major Chassis major Chassis Chassis 008192 MB major major Host has been powered on Dec 19 08 4 Dec 19 08 4 Dec 19 08 4 system operating at reduced Chassis major Dec 19 08 45 11 15 13 5 13 513 Dec 19 08 4 5243 ERROR MB CMPO MCU2 Failed IBIST critical SP detected fault at time Wed Dec 19 08 45 12 SYS MB CMP0 MCU2 Forced fail major Dec 19 08 45 13 ERROR MB CMP0 MCU3 unused because MB CMP0 MCU2 is not configured IBIST ERROR MB CMP0 L2_BANK4 MB CMP0 L2_BANK5 unused because MB CMP0 MCU2 is not configured ERROR MB CMP0 L2_BANK6 MB CMP0 L2_BANK7 unused because MB CMP0 MCU3 is not configured ERROR Degraded configuration capacity ERROR System DRAM Available Chassis major Dec 19 08 45 13 ERROR Only 4 cores up to 32 cpus are configured because some L2_BANKS are unusable Workaround Install Patch 127580 04 or later and update the System Firmware to version 7 0 9 or later Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Solaris OS Issues TABLE 2 4 lists the late breaking issues related to the running the Solaris OS on the Sun SPARC Enterprise T5120 and T5220 se
29. S KYUN microsystems Sun SPARC Enterprise T5120 and T5220 Servers Product Notes Sun Microsystems Inc www sun com Part No 820 2176 14 June 2008 Revision A Submit comments about this document at http www sun com hwdocs feedback Copyright 2008 Sun Microsystems Inc 4150 Network Circle Santa Clara California 95054 U S A All rights reserved FUJITSU LIMITED provided technical input and review on portions of this material Sun Microsystems Inc and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in this document and such products technology and this document are protected by copyright laws patents and other intellectual property laws and international treaties The intellectual property rights of Sun Microsystems Inc and Fujitsu Limited in such products technology and this document include without limitation one or more of the United States patents listed at http www sun com patents and one or more additional patents or patent applications in the United States or other countries This document and the product and technology to which it pertains are distributed under licenses restricting their use copying distribution and decompilation No part of such product or technology or of this document may be reproduced in any form by any means without prior written authorization of Fujitsu Limited and Sun Microsystems Inc and their applicable licensors
30. ST might encounter intermittent POST PIUO Power cycle the system as follows example uses link train errors during a power cycle test the ALOM CMT compatibility CLI sc gt poweroff fy sc gt clearasrdb sc gt poweron c 6573354 The method for clearing POST results displayed To clear POST results use the ALOM CMT with the showfaults command has changed compatibility setdefaults command After POST runs showfaults displays the status The only way to clear the status is to enter the setdefaults command For users familiar with ALOM CMT the previous way to clear the status was to enter the resetsc command 6577528 A terminal server break command does not Use the break commands from the SP either the work on the SP serial port ILOM or ALOM CMT compatibility commands If you use Telnet to connect to the SP serial line to send a break to the Solaris host with a terminal server such as the Cisco ASM Refer to the Integrated Lights Out Management series and try to send a break to the Solaris ILOM Supplement for SPARC Enterprise T5120 host the break command does not work and is and T5220 Servers for details ignored by the SP 6579390 After disabling a DIMM the OpenBoot PROM If you manually disable any CPU or memory banner does not show a decrease in the amount resource with the ASR commands while the host of memory is powered on you must power cycle the host to complete the disabling of the resource After the power cycle the resource
31. TIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE A L APTITUDE A UNE UTILISATION PARTICULIERE OU A L ABSENCE DE CONTREFACON Contents Important Information About the Sun SPARC Enterprise T5120 and T5220 Servers 1 Technical Support and Documentation 2 Technical Support 2 Documentation 2 Supported Versions of the OS and Firmware 3 System Firmware 3 Preinstalled and Preloaded Software 4 Solaris 10 OS and Solaris Live Upgrade 5 Additional Software Available for Your Server Cool Tools 5 Logical Domains 6 Sun Explorer Utility 6 Sun Studio C C amp Fortran Compilers and Tools 7 Sun Java Enterprise System 7 Mandatory Patch Information 8 v To Download Patches 8 Patches for Option Cards 9 Processor Identification 10 Cryptographic Support 11 v To Enable IPsec Cryptographic Hardware Acceleration 11 Late Breaking Issues 13 Hardware and Mechanical Issues 14 L2 Cache Errors Might Generate an Erroneous Memory Fault CR 6592272 16 Erroneous Power Supply Faults CR 6614432 17 Ethernet Interface Related Issues 18 Using modunload While the nxge Port Is Running Could Cause a System Panic CR 6551509 19 v To Unplumb the Interfaces Prior to Unloading the Driver 20 Temporary PCle Link Failure During Boot Causes a Fatal Error Later CR 6553515 21 Jumbo Frames Throughput of nxge Drops to 30 Mbps Due to Packet
32. Workaround 6582340 When you are connected to the virtual console If you are refused write access when you initiate and you enter the escape character sequence a connection to the host with the console to enter the SP CLI the following two error command enter console f the force option messages might display before reaching the CLI to get read and write access prompt read Connection reset by peer Write to vbsc Illegal seek This situation occurs when there is a lot of output through the console and implies that the console is in use when it is not 6582853 The showfaults ALOM CMT compatibility Use the fault management utilities that are command reports the motherboard as faulty described in the Predictive Self Healing PSH instead of the actual faulty DIMM or PCIe card Knowledge Articles located at http www sun com msg MSGID MSGID is the PSH Message ID For more information see The showfaults Command Shows the Motherboard as Faulty Instead of the DIMM CR 6582853 on page 35 6583567 A communication channel between the primary See Communication Channel Between the domain and the service processor SP could Primary Domain and the Service Processor SP hang and disable communication over the Might Hang CR 6583567 on page 37 channel 6585114 During automated testing the SP could AC power cycle the system encounter problems with useradd and usershow commands followed by the failure of all login attempts
33. a power supply fan and the fan returns to normal operation the fault indication is not automatically cleared 6674290 In the Sun SPARC Enterprise T5220 server ifa If possible do not install any PCIe cards in the XAUI card and a PCIe card are installed on the same riser assembly the XAUI card might fail POST and be disabled when the server boots same riser assembly as a XAUI card Chapter 2 Late Breaking Issues 15 L2 Cache Errors Might Generate an Erroneous Memory Fault CR 6592272 After an uncorrectable L2 writeback error a bogus memory fault message SUN4V 8000 E2 might be reported to the console Example SUNW MSG ID SUN4V 8000 E2 TYPE Fault VER 1 SEVERITY Critical EVENT TIME Wed Sep 5 18 49 35 EDT 2007 PLATFORM SUNW SPARC Enterprise T5220 CSN HOSTNAME wgs48 100 SOURCE cpumem diagnosis REV 1 6 EVENT ID 59bf6418 5dcb cl1b0 b06a f 26fal8e4ee7 DESC The number of errors associated with this memory module has xceeded acceptable levels Refer to http sun com msg SUN4V 8000 E2 for more information AUTO RESPONSE Pages of memory associated with this memory module are being removed from service as errors are reported IMPACT Total system memory capacity will be reduced as pages are retired Workaround Use fmdump eV u uuid with the UUID from the console message to determine if the memory error is bogus For example fmdump eV u 59bf 6418 5dc
34. ain can be created destroyed reconfigured and rebooted independently without requiring a power cycle of the server You can run a variety of applications software in different logical domains and keep them independent for performance and security purposes Using Logical Domains LDoms increases your server usage efficiency and return on investment and also reduces your server footprint The LDoms Manager software creates and manages logical domains and maps logical domains to physical resources Note The LDoms MIB must be configured before it is ready to use A README file with configuration instructions is located in the LDoms MIB installation directory opt 1doms_mib For more information on LDoms go to http www sun com servers coolthreads ldoms Sun Explorer Utility Sun Explorer is a diagnostic data collection tool The tool comprises shell scripts and a few binary executables Sun Explorer runs on the Solaris OS The Sun SPARC Enterprise T5120 and T5220 servers are supported by the Sun Explorer 5 10 or later data collection utility but not supported by earlier releases of the utility Installing Sun Cluster or Sun Net Connect software from the preinstalled Java ES package might automatically install an earlier version of the utility on your system After installing any of the Java ES software determine whether an earlier version of the Sun Explorer product has been installed on your system by typing the foll
35. b cib0 b06a f26fal8ed4ee7 grep dram esr dram esr 0x1000000000008221 If the dram esr is 0x1000000000008221 this CR 6592272 has been encountered and the memory error can be ignored No memory component replacement is necessary Use fmadm repair uuid to repair the bogus memory error If the dram esr is different schedule a repair procedure to replace the affected memory module Use fmdump v u event_id to identify the module 16 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Erroneous Power Supply Faults CR 6614432 The following example shows the kind of erroneous power supply faults that are described in TABLE 2 1 for this CR sc gt showlogs Oct 09 14 13 17 Chassis major Host is running Oct 09 14 36 10 IPMI minor ID 264 10 09 2007 14 36 10 Power Supply PS1 DC_POK State Deasserted Oct 09 14 36 11 IPMI minor ID 265 10 09 2007 14 36 11 Power Supply PS1 AC_POK State Deasserted Oct 09 14 36 14 IPMI minor ID 266 10 09 2007 14 36 14 Power Supply PS1 FAIL State Asserted Chapter 2 Late Breaking Issues 17 Ethernet Interface Related Issues TABLE 2 2 lists the late breaking Ethernet related issues Additional information for some of the change request CR issues is provided after the table TABLE 2 2 Ethernet Related Issues CR Description Workaround 6551509 If you run modunload while the nxge port is Unplumb
36. describes the missing properties m SP network dhcp_server_ip The IP address of the DHCP server that provided the dynamic IP address requested by the service processor m SP policy HOST_AUTO_POWER_ON Automatically powers on the host when the service processor has been booted If this policy is set to enabled the service processor sets HOST_LAST_POWER_STATE to disabled ALOM Compatibility CLI Example in the Section Adding a Commit Step on Page 38 Is Incomplete The description of the ALOM compatibility shell command line argument netsc_commit is incomplete on page 38 The first sentence at the top of the page should include the argument true as follows Instead change the network configuration property then commit it using setsc netsc_commit true in the ALOM compatibility CLI or set SP network commitpending using the ILOM CLI Where the first example shows sc gt setsc netsc_ipaddr XXX XXX XXX XXX sc gt setsc netsc_commit 54 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 The example should include the value of true on the second line sc gt setsc netsc_ipaddr Xxx XxXx XXX XXX sc gt setsc netsc_commit true Argument List for Resetting the Service Processor to Factory Defaults Is Incorrect The section titled Changing Service Processor Settings to Factory Defaults lists three options none configuration and all The configuration option is not available The only options
37. displayed raidctl 1 Device record is invalid 6594506 After certain hardware error events it is possible See PSH Events Are no Longer Transported that Solaris PSH events are no longer CR 6594506 on page 48 transported between the SP and the domain For examples see PSH Events Are no Longer Transported CR 6594506 on page 48 6596503 The output of the Solaris prtpicl command Instead use the output from the prtdiag or used with the v option might show CPU cores prtpicl c cpu commands or strands with an operational status of enabled when in fact the cores or strands do not exist 6607315 The login prompt resets five seconds after the Use the virtual console as the input device Solaris OS boots This only occurs when using a local keyboard as the input device input device keyboard This issue does not occur with the virtual console The output of the raidct1 h command and The Sun SPARC Enterprise T5120 and T5220 the raidct1 man page display some servers currently only support RAID 0 and unsupported features RAID 1 for the o board SAS disk controller The raidctl utility can be used to create and delete RAID 0 amp RAID 1 volumes Refer to the Sun SPARC Enterprise T5120 and T5220 Servers Administration Guide for supported RAID information 44 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Servers Might Experience Panics Generated From the PCIe Root Complex CR 6555956 A panic could occur
38. during reboot with the following message Fatal error has occurred in PCIe root complex The panic only occurs during a reboot and has never been observed during a reboot that follows the panic The panic can occur even if no external USB devices are connected to the server Workarounds If your server experiences this panic perform one or more of the following workarounds m To ensure that the system reboots and continues to function after a panic configure the server to automatically reboot using one of the following methods a Using the ILOM CLI gt set HOST bootmode script setenv auto boot true gt set HOST bootmode script setenv auto boot on error true Using the ALOM CMT compatibility CLI sc gt bootmode bootscript setenv auto boot true sc gt bootmode bootscript setenv auto boot on error true m To eliminate the possibility of the panic disable the USB only perform this workaround if you do not use USB devices including the built in DVD drive a Using the ILOM CLI gt set SYS MB PCIE IO USB component_state Disabled Using the ALOM CMT compatibility CLI sc gt disablecomponent SYS MB PCIE IO USB All devices on the USB will be disabled including the DVD drive Be aware that the service processor will generate a fault and turn on the fault LED If you need to enable the USB use the following commands a Using the ILOM CLI gt set SYS M
39. dvertently Apply counter pressure to the DVD assembly removed from the chassis when removing a USB device In addition do Note This issue only applies to servers that not remove a USB device while media is inserted have a finger detent in the floor of the and operating DVD USB module Servers with a DVD pull tab do not experience this problem n a Hot swapping fan modules requires careful fan When removing a fan module hold the adjacent removal fan module in place to avoid unintentionally dislodging the adjacent fan module n a All disk LEDs blink simultaneously about every Be aware that the blinking LEDs are a normal 16 seconds when a RAID volume is created condition 6550166 Components on the motherboard are hot to the When replacing components in the system touch chassis wait for components to cool down approximately one minute prior to performing service actions 6574127 If a hard drive fails in RAID 0 or RAID 1 If you encounter failed disks in RAID 0 or configurations it is possible that error messages RAID 1 configurations and you see the will not be displayed on the console or in the log following scenario the disk drive should be files replaced e The Fault LED is lit on a disk drive that is part of a RAIDO or RAID1 volume e The error condition can be displayed remotely by running the showenvironment command on the service processor e The hard drive that has the Fault LED illuminated displays a status of Failed and the se
40. e 1 will set the 10 Mbps speed and Half Duplex mode 2 will set the 10 Mbps speed and Full Duplex mode 3 will set the 100 Mbps speed and half Duplex mode 4 will set the 100 Mbps speed and Full Duplex mode 7 will let adapter autonegotiate AutoNegAdvertised 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 This parameter determines the speed duplex options that will be advertised during auto negotiation This is a bitmap with the following settings PBI PF 6 5 Bo 2 2 0 Setting N A N A 1000F N A 100F 100H 10F 10H For example To advertise 10 Half only AutoNegAdvertised To advertise 10 Full only AutoNegAdvertised 2 To advertise 10 Half Full AutoNegAdvertised 43 To advertise 100 Half only AutoNegAdvertised 4 To advertise 100 Full only AutoNegAdvertised 8 To advertise 100 Half Full AutoNegAdvertised 12 To advertise 1000 Full only AutoNegAdvertised 32 To advertise all speeds AutoNegAdvertised SAT 24 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Setting Properties for nxge Devices Might Fail CR 6561389 Setting a property for an nxge device node might not work correctly The following is an example name SUNW niusl parent niu 80 unit address 0 accept_jumbo 1 name SUNW niusl parent niu 80 unit address 1 accept_jumbo 1 Entries from etc path_to_inst niu 80 0 niumx niu 80 network 0 0 nxge n
41. echnology enables the Solaris OS to run normally during an upgrade or normal maintenance on an inactive boot environment For more information about Solaris Live Upgrade go to http www sun com software solaris liveupgrade You might need to install a different version of Solaris Live Upgrade depending on which Solaris OS version you are installing or upgrading For more information on installing the correct versions of Solaris Live Upgrade go to http www sun com software preinstall Additional Software Available for Your Server Cool Tools Cool Tools provide a collection of freely available tools that enable fast and efficient development and deployment of optimally configured software solutions on CoolThreads servers These tools significantly improve performance and time to market development for applications running on these servers Chapter 1 Important Information About the Sun SPARC Enterprise T5120 and T5220 Servers 5 An overview of the Cool Tools and full documentation is available at http www sun com servers coolthreads overview cooltools jsp Not all of the Cool Tools listed on the Cool Tools web page are preloaded on your server Refer to information at the Cool Tools web site for additional tools you can download and install on these servers Logical Domains A logical domain is a discrete logical grouping with its own operating system resources and identity within a single computer system Each logical dom
42. engagement de quelque type que ce soit de la part de Fujitsu Limited ou de Sun Microsystems Inc ou des soci t s affili es Ce document et le produit et les technologies qu il d crit peuvent inclure des droits de propri t intellectuelle de parties tierces prot g s par copyright et ou c d s sous licence par des fournisseurs Fujitsu Limited et ou Sun Microsystems Inc y compris des logiciels et des technologies relatives aux polices de caract res Par limites du GPL ou du LGPL une copie du code source r gi par le GPL ou LGPL comme applicable est sur demande vers la fin utilsateur disponible veuillez contacter Fujitsu Limted ou Sun Microsystems Inc Cette distribution peut comprendre des composants d velopp s par des tierces parties Des parties de ce produit pourront tre d riv es des syst mes Berkeley BSD licenci s par l Universit de Californie UNIX est une marque d pos e aux Etats Unis et dans d autres pays et licenci e exclusivement par X Open Company Ltd Sun Sun Microsystems le logo Sun Java Netra Solaris Sun StorEdge docs sun com OpenBoot SunVTS Sun Fire SunSolve CoolThreads J2EE SunService et Sun sont des marques de fabrique ou des marques d pos es de Sun Microsystems Inc et ses filiales aux Etats Unis et dans d autres pays Fujitsu et le logo Fujitsu sont des marques d pos es de Fujitsu Limited Toutes les marques SPARC sont utilis es sous licence et sont des marques de
43. ent v0 3 1 lt gt http snowman net projects ipt_recent arp_tables C 2002 802 1Q VLAN Support v1 8 lt gt All bugs added by Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Spurious PIU Errors CR 6598381 In rare circumstances the PIU PCle interface unit might issue a spurious error interrupt The following is an example of the event reported after diagnostics SUNW MSG ID FMD 8000 OW TYPE Defect VER 1 SEVERITY Minor EVENT TIME Mon Aug 27 10 07 33 EDT 2007 PLATFORM SUNW SPARC Enterprise T5220 CSN HOSTNAME xxxxxxx SOURCE fmd self diagnosis REV 1 0 EVENT ID dd9a4415 9be4 cb55 d061 8804b8009d3c The following is an example of the event reported by the fmdump command fmdump eV u dd9a4415 9be4 cb55 d061 8804b8009d3c TIME CLASS Aug 27 2007 10 06 15 496599680 ereport fm ferg invalid nvlist version 0 class ereport fm ferg invalid ena 0xd4e233fe480002 info DMU Core and Block Error Status 0 No bits set raw data 0x2 0x1a62441a01d844 0x30000000000005 0x4b63c07df9ff 0x3e002421030607 Ox 3e 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 tel 0X0 __tod 0x46d2da57 0x1d998280 These events are harmless and can be ignored Diagnostic Routine That Runs at Startup IBIST May Accidentally Disconnect the MCU CR 6618773 In some cases the MCU is disconnected from corresponding DIM
44. fabrique ou des marques d pos es de SPARC International Inc aux Etats Unis et dans d autres pays Les produits portant les marques SPARC sont bas s sur une architecture d velopp e par Sun Microsystems Inc SPARC64 est une marques d pos e de SPARC International Inc utilis e sous le permis par Fujitsu Microelectronics Inc et Fujitsu Limited L interface d utilisation graphique OPEN LOOK et Sun a t d velopp e par Sun Microsystems Inc pour ses utilisateurs et licenci s Sun reconna t les efforts de pionniers de Xerox pour la recherche et le d veloppement du concept des interfaces d utilisation visuelle ou graphique pour l industrie de l informatique Sun d tient une license non exclusive de Xerox sur l interface d utilisation graphique Xerox cette licence couvrant galement les licenci s de Sun qui mettent en place l interface d utilisation graphique OPEN LOOK et qui en outre se conforment aux licences crites de Sun Droits du gouvernement am ricain logiciel commercial Les utilisateurs du gouvernement am ricain sont soumis aux contrats de licence standard de Sun Microsystems Inc et de Fujitsu Limited ainsi qu aux clauses applicables stipul es dans le FAR et ses suppl ments Avis de non responsabilit les seules garanties octroy es par Fujitsu Limited Sun Microsystems Inc ou toute soci t affili e de l une ou l autre entit en rapport avec ce document ou tout produit ou toute technologie d crit e
45. if any The furnishing of this document to you does not give you any rights or licenses express or implied with respect to the product or technology to which it pertains and this document does not contain or represent any commitment of any kind on the part of Fujitsu Limited or Sun Microsystems Inc or any affiliate of either of them This document and the product and technology described in this document may incorporate third party intellectual property copyrighted by and or licensed from suppliers to Fujitsu Limited and or Sun Microsystems Inc including software and font technology Per the terms of the GPL or LGPL a copy of the source code governed by the GPL or LGPL as applicable is available upon request by the End User Please contact Fujitsu Limited or Sun Microsystems Inc This distribution may include materials developed by third parties Parts of the product may be derived from Berkeley BSD systems licensed from the University of California UNIX is a registered trademark in the U S and in other countries exclusively licensed through X Open Company Ltd Sun Sun Microsystems the Sun logo Java Netra Solaris Sun StorEdge docs sun com OpenBoot SunVTS Sun Fire SunSolve CoolThreads J2EE SunService and Sun are trademarks or registered trademarks of Sun Microsystems Inc or its subsidiaries in the U S and other countries Fujitsu and the Fujitsu logo are registered trademarks of Fujitsu Limited All SPARC tradema
46. ilable to the system If you power on the system or reset the domain and try and boot from a disk or network device and you get an error similar to the following 0 ok boot disk Boot device pci 0 pci 0 pci 2 scsi 0 disk 0 File and args ERROR boot read fail Can t locate boot device 0 ok 1 At the ok prompt issue the show devs command 2 Check the output to for PCIe devices If no PCIe devices are displayed the server has encountered this problem Note All PCIe devices begin with the path pci 0 pci o V To Correct the Problem 1 Take down all domains and power off the system 2 Run power on self test POST to identify whether this is a persistent failure or not To enable POST use the setsc an ALOM CMT compatibility CLI command and configure POST to run at max level For example sc gt setsc diag mode normal sc gt setsc diag_level max 3 Power on the system POST tests the CPU memory and I O subsystems If the problem is persistent POST will fail the PCIe root complex test and disable the SYS MB PCIE component 4 If POST detects the problem replace the motherboard 34 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 The showfaults Command Shows the Motherboard as Faulty Instead of the DIMM CR 6582853 In a system with DIMMs or PCle adapters that have been faulted by PSH Predictive Self Healing diagnosis on the host the ALOM
47. ing Issues 21 Jumbo Frames Throughput of nxge Drops to 30 Mbps Due to Packet Dropping CR 6554478 Receive side performance of the nxge driver drops significantly if the following two conditions are true m Jumbo frames are enabled because the following line is present and not commented out in the nxge conf file accept_jumbo 1 The nxge conf file is in the platform sun4v kernel drv directory on sun4v systems and it is in the platform sun4u kernel drv directory on sun4u systems a Maximum Transmission Unit MTU is set to a value larger than 8172 When jumbo frames are enabled the MTU size defaults to 9194 Note Refer to the Sun Quad GbE UTP x8 PCIe ExpressModule User s Guide the Sun Dual 10GbE XFP PCle ExpressModule User s Guide the Sun x8 Express Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter User s Guide or the Sun x8 Express Quad Gigabit Ethernet UTP Low Profile Adapter User s Guide for details V To Set the MTU Size to 8172 If jumbo frames are enabled use this procedure to set the MTU to a value of 8172 This procedure uses port1 as an example 1 Edit or create an etc hosts file and add the following line in it 99 99 9 1 nxge portl Where nxge port1 is the name you give to the interface and 99 99 9 1 is the IP address you want to assign to the interface 2 Edit or create a etc hostname nxge1 file and place the following two lines in it nxge porti nxge portl mtu 817
48. ion package visit http www sun com ipsec 2 Use the pkgadd command to install the activation package as shown in the following example pkgadd sol 10 u4 ga sparc cryptoactivation pkg 3 Reboot the system after installing the activation package to complete the activation Installing this package enables IPsec to automatically and transparently use the UltraSPARC T2 cryptographic hardware For more information about IPsec refer to the IPsec and IKE Administration Guide at http docs sun com Chapter 1 Important Information About the Sun SPARC Enterprise T5120 and T5220 Servers 11 12 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 CHAPTER 2 Late Breaking Issues These product notes contain late breaking information about the Sun SPARC Enterprise T5120 and T5220 servers The following sections are included Hardware and Mechanical Issues on page 14 Ethernet Interface Related Issues on page 18 Firmware ILOM POST and SP Issues on page 27 Solaris OS Issues on page 41 LDoms Related Issues on page 50 Documentation Errata on page 53 Hardware and Mechanical Issues TABLE 2 1 lists the late breaking hardware and mechanical issues Additional information for some of the change request CR issues is provided after the table TABLE 2 1 Hardware and Mechanical Issues CR Description Workaround 6579358 The DVD USB assembly might be ina
49. is the changes made by the bootmode command require a power on reset to be effective Changes made with the setenv or eeprom commands will only persist until the next reset at which point the variable will revert to the value set by the last bootmode command This persistence of the bootmode setting will persist until the machine is power cycled Upon power cycling the prior bootmode setting will not take effect Any subsequent change made by the setenv or eeprom command will now persist over resets at least until the next bootmode command followed by a power cycle Workaround Restart the control domain with a power on reset right after the bootmode command is executed and restart again after the control domain boots to either OpenBoot or Solaris The first power on reset will make the bootmode command effective and the second power on reset will workaround the persistence issue 36 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 The control domain can be reset using power on reset with the ALOM CMT compatibility CLI powercycle command If the control domain is booted to the Solaris OS remember to properly shut down the OS before executing the powercycle command Communication Channel Between the Primary Domain and the Service Processor SP Might Hang CR 6583567 Rarely a communication channel between the primary domain and the SP might hang and disable communication over the channel Workarounds m If the
50. itsu Limited d tiennent et contrdlent toutes deux des droits de propri t intellectuelle relatifs aux produits et technologies d crits dans ce document De m me ces produits technologies et ce document sont prot g s par des lois sur le copyright des brevets d autres lois sur la propri t intellectuelle et des trait s internationaux Les droits de propri t intellectuelle de Sun Microsystems Inc et Fujitsu Limited concernant ces produits ces technologies et ce document comprennent sans que cette liste soit exhaustive un ou plusieurs des brevets d pos s aux Etats Unis et indiqu s l adresse http www sun com patents de m me qu un ou plusieurs brevets ou applications brevet es suppl mentaires aux Etats Unis et dans d autres pays Ce document le produit et les technologies aff rents sont exclusivement distribu s avec des licences qui en restreignent l utilisation la copie la distribution et la d compilation Aucune partie de ce produit de ces technologies ou de ce document ne peut tre reproduite sous quelque forme que ce soit par quelque moyen que ce soit sans l autorisation crite pr alable de Fujitsu Limited et de Sun Microsystems Inc et de leurs ventuels bailleurs de licence Ce document bien qu il vous ait t fourni ne vous conf re aucun droit et aucune licence expresses ou tacites concernant le produit ou la technologie auxquels il se rapporte Par ailleurs il ne contient ni ne repr sente aucun
51. iu 80 network 1 1 nxge Entries from etc driver_aliases niumx SUNW niumx nxge SUNW niusl Workaround Use the global declaration without the device path in the nxge conf file For example add the following line to the nxge conf file accept_jumbo 1 Server Might Panic in nxge_start When dupb Fails CR 6567838 If jumbo frames are enabled it is possible for the system to panic as a result of a NULL pointer reference This scenario is only possible when frame sizes are larger than 4076 Jumbo frames with MTU 9194 do not experience this problem Workaround Disable jumbo frames or use a smaller MTU size as described in the following procedures V To Disable Jumbo Frames Disabling jumbo frames or using jumbo frames with a smaller MTU impacts system performance Only perform the following steps if the system panics due to jumbo frames 1 Edit the platform sun4v kernel drv nxge conf file and ensure that any line with accept_jumbo 1 is commented out 2 Ensure that there is no set nxge nxge_jumbo_enable 1 in the etc system file Chapter 2 Late Breaking Issues 25 V To Set the MTU to a Smaller Size If you want to use jumbo frames you can use this workaround instead of disabling jumbo frames This procedure sets the MTU to a value equal to or smaller than 4076 using port1 as an example Note By following these steps the MTU values are permanent As an alternative you can run the command ifc
52. mes the device cdrom 1 46 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Both the OpenBoot firmware and Solaris OS follow the 1275 USB bindings rules to name nodes For example TABLE 2 5 1275 USB Bindings Rules for Naming Nodes binterface Class binterface Subclass binterface Protocol Name 0x08 1 Any storage 0x08 2 Any cdrom 0x08 3 Any tape 0x08 4 Any floppy 0x08 5 Any storage 0x08 6 Any storage 0x08 Any Any storage The Solaris 10 OS always names the node as storage n Therefore the storage device with a subclass of 2 3 or 4 SPARC Enterprise T5120 and T5220 must be 2 cannot boot with Solaris 10 OS DVD Workaround Use the drive whose subclass is not 2 3 or 4 as the replacement The prtdiag v Command Has Formatting Issues CR 6587389 Some of the information displayed by the prtdiag 1M command is difficult to read when the v option is used White space is missing between the first and second fields in the report The following formatting issues are displayed in the prtdiag v command output m Fans sensors Missing spaces tab between Location and Sensor columns m Temperature sensors DIMMs missing spaces tab between Location and Sensor columns a LEDs Location missing for SERVICE LOCATE ACT PS_FAULT TEMP_FAULT and FAN_FAULT DIMMs Missing spaces tab between Location and LED Locations of sensors have the first portion of their location truncated resulting in no locati
53. o access the current release of a patch 3 Follow the installation instructions provided in a specific patch s README file Patches for Option Cards If you add option cards to your server refer to the documentation and README files for each card to determine if additional patches are needed Chapter 1 Important Information About the Sun SPARC Enterprise T5120 and T5220 Servers 9 10 Processor Identification Processor IDs Might Not Start at 0 and Might Not Be Contiguous Different platforms and platforms of the same model might have different processor IDs for identical configurations For example on UltraSPARC T1 CPU based platforms the processor IDs start with processor ID 0 but other platforms including those based on the UltraSPARC T2 CPU may not have a processor ID 0 The Solaris psrinfo command might display output similar to the following for platforms based on the UltraSPARC T2 processor 8 on line since 09 18 2007 21 26 25 9 on line since 09 18 2007 21 26 30 16 on line since 09 18 2007 21 26 30 17 on line since 09 18 2007 21 26 30 The processor IDs might have significance if you are running LDoms The processor IDs exported to a guest domain on a platform running multiple guest domains with a virtual machine manager might represent a virtual abstraction Within each guest domain each processor ID visible to the software will be a unique integer value Software running in different guest domains on
54. on being reported for some items such as system status LEDs To see this formatting information use the showenvironment command in the ALOM CMT compatibility CLI sc gt showenvironment displays the system environmental status Chapter 2 Late Breaking Issues 47 PSH Events Are no Longer Transported CR 6594506 After certain hardware error events it is possible that PSH events are no longer transported between the service processor SP and the domain The following scenarios are subject to this problem m Inanon LDoms environment an unrecoverable error occurs in the Solaris domain m In an LDoms environment an unrecoverable error occurs in the control domain a In either an LDoms or non LDoms environment a fatal error occurs in the system a fatal error resets the system at the hardware level Note In an LDoms environment unrecoverable errors in a noncontrolled LDoms guest domain are not subject to this problem For example an unrecoverable error in the control domain causes Solaris to panic Messages similar to the following are reported to the control domain console SUNW MSG ID SUNOS 8000 0G TYPE Error VER 1 SEVERITY Major EVENT TIME 0x46c61864 0x318184c6 0xidfeda2137e LATFORM SUNW SPARC Enterprise T5220 CSN HOSTNAME wgs48 100 OURCE SunOS REV 5 10 Generic_Patch SC Errors have been detected that require a reboot to ensure system ntegrity See http www sun com msg SUNOS 8000
55. onfig nxgeX mtu 4076 where X is the instance number but the MTU value will change back to the default one after a reboot 1 Edit or create an etc hosts file and add the following line in it 99 99 9 1 nxge porti Where nxge port1 is the name you assign to the interface 99 99 9 1 is the IP address you want to assign to the interface 2 Create an etc hostname nxgel file and place the following two lines in it nxge porti nxge porti mtu 4076 26 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 TABLE 2 3 CR Firmware ILOM POST and SP Issues TABLE 2 3 lists the late breaking issues for the firmware ILOM including ALOM compatibility CLI POST and service processor SP Additional information for some of the change request CR issues is provided following the table Firmware ILOM POST and SP Issues Description Workaround 6541482 6549028 6556505 6568750 POST always starts on the lowest available strand even when that strand is disabled If processor strand 0 of the first available physical core has been marked disabled as seen in the list of disabled devices in the output of the showcomponent command a new master strand is selected by the initialization process and the disabled strand is taken offline But the system initialization and execution of power on self test POST occurs using the disabled processor strand because power on and
56. ork interface unit Use the global declaration without the device NIU nxge devices could fail For an example of the failure see Setting Properties for nxge Devices Might Fail CR 6561389 on page 25 path in the nxge conf file For example add the following line to the nxge conf file accept_jumbo 1 18 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 TABLE 2 2 Ethernet Related Issues Continued CR Description Workaround 6567838 The server might panic in nxge_start when Disable the use of jumbo frames but be aware the dupb fails that doing so impacts system performance You If jumbo frames are enabled it is possible for the should only apply the workarounds if your system to panic as a result of a NULL pointer server is experiencing this problem For details reference This scenario is only possible when on this workaround see Server Might Panic in frame sizes are larger than 4076 Jumbo frames nxge_start When dupb Fails CR 6567838 on with MTU 9194 do not experience this problem Page 25 Note This scenario is rare and only occurs with frame sizes larger than 4076 6599334 XAUI interfaces might not be disabled when Be aware of this issue they should be disabled Normally when a CPU network interface unit NIU is disabled either through POST detected faults or manually the corresponding XAUI interface if one is installed should also be disabled but that does not happen 66
57. owing pkginfo 1 SUNWexplo Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 If an earlier version exists uninstall it and install version 5 10 or later To download version 5 10 go to http www sun com sunsolve Sun Studio C C amp Fortran Compilers and Tools Sun Studio delivers high performance by optimizing C C and Fortran compilers for the Solaris OS on multicore systems For an overview and documentation go to http developers sun com sunstudio index jsp Sun Java Enterprise System The Sun Java Enterprise System software provides a complete set of middleware services to support enterprise applications that are distributed across a network or Internet environment The Java Enterprise System components that provide the services are installed using a common installer synchronized on a common set of shared libraries and share an integrated user identity and security management system Sun Java Enterprise System software provides the following services m Portal services Portal Server Portal Server Secure Remote Access Access Manager Directory Server Application Server or Web Server Communication and collaboration services Messaging Server Calendar Server Instant Messaging Access Manager Directory Server Application Server or Web Server m Network identity services Access Manager Directory Server Web Server m Web and application services Application Server
58. r 6589043 If there are fewer than 21 entries in the event Use the showlogs v option to display the logs log the showlogs command displays none of After 21 or more events are logged in the log file the events you can revert back to using showlogs with no This situation is known to occur in the following Options scenarios e After a fresh installation of the system out of box the service processor SP event log is very likely to have fewer than 21 entries e After you clear the SP event log with the browser interface BI or ILOM CLI the ALOM CMT compatibility CLI showlogs command displays no new events until at least 21 new events are logged 6591367 You cannot obtain the system DIMM FRU Obtain the DIMM FRU information using the SP information with the ipmitool utility ALOM CMT compatibility CLI with the showfru command or the SP ILOM CLI with the show fru name command Refer to the Integrated Lights Out Management ILOM Supplement for Sun SPARC Enterprise T5120 and T5220 Servers for details 6593547 An erroneous watchdog reset error might occur The error is erroneous and can be ignored If this error occurs the system will not complete the boot sequence You might see the following error in either the I O or the Control domain when attempting to boot and the boot sequence will be aborted ERROR Last Trap Watchdog Reset Type boot at the OK prompt to proceed 30 Sun SPARC Enterprise T5120 and T5220 Servers Produc
59. rds French German and so on might behave as U S keyboards IMPI power off or power cycle operations might fail Manually copy the user settings before replacing the motherboard in a motherboard swap scenario After the swap is complete manually set the user parameters After changing variables reset the control domain using the reset all command These events are harmless and can be ignored Do not use USB keyboards Instead use a virtual console by setting the input device variable to virtual console Repeat the IPMI power off or power cycle operation or use one of the other available interfaces to perform this operation Chapter 2 Late Breaking Issues 31 TABLE 2 3 CR Firmware ILOM POST and SP Issues Continued Description Workaround 6604305 6612687 6614576 6618773 During system initialization memory might not be detected and the following error is reported ERROR MB CMP0O BR3 CH0 D0 must be populated Rarely the probing of DIMMs fails due to ILOM simultaneously updating DIMM information When the DIMM probing fails the host either boots with a reduced memory configuration or fails to boot This situation is not likely to happen when the service processor SP is reset because the DIMMs are probed before ILOM starts dynamic fruid updates This issue is most likely to occur when the host is being repeatedly powered on and off without resetting the SP Repeated attempts to
60. reset execution always starts on strand 0 of the first available physical core When this situation happens the system might fail to run the diagnostics and the system might fail in an unpredictable manner The system might not start the required firmware and software components as a result The netsc_commit command might cause the system to hang Through a serial connection the network might not be visible The PCIe link might fail to train as x8 This problem might occur during a power on or reset sequence where the I O bridge PCle root complex of the UltraSPARC T2 CPU does not properly train the PCIe interface Scripts that log into the SP might timeout after 60 seconds If this error occurs the following error message is displayed Logging out after 60 seconds Note This error is not seen during normal login only when logging in with a script If strand 0 of the first physical core is known to be bad there is no workaround The motherboard must be replaced Reboot the system If rebooting fails to reset the SP AC power cycle the system to recover the SP Be aware that you will lose active domains For workaround procedures see Problem When the PCIe Link Fails to Train as x8 CR 6556505 on page 33 If you use scripts to log into the SP be aware of this issue Chapter 2 Late Breaking Issues 27 TABLE 2 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6571886 PO
61. rks are used under license and are registered trademarks of SPARC International Inc in the U S and other countries Products bearing SPARC trademarks are based upon architecture developed by Sun Microsystems Inc SPARC64 is a trademark of SPARC International Inc used under license by Fujitsu Microelectronics Inc and Fujitsu Limited The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems Inc for its users and licensees Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry Sun holds a non exclusive license from Xerox to the Xerox Graphical User Interface which license also covers Sun s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun s written license agreements United States Government Rights Commercial use U S Government users are subject to the standard government user license agreements of Sun Microsystems Inc and Fujitsu Limited and the applicable provisions of the FAR and its supplements Disclaimer The only warranties granted by Fujitsu Limited Sun Microsystems Inc or any affiliate of either of them in connection with this document or any product or technology described herein are those expressly set forth in the license agreement pursuant to which the product or technology is provided EXCEPT AS EXPRESSLY SET FORTH IN SUCH AGREEMENT FUJITSU LIMITED SUN MICROSYSTEMS INC
62. rvers Additional information for some of the change request CR issues is provided following the table Note Additionally more general Solaris OS late breaking issues are described in the Solaris 10 Release Notes TABLE 2 4 Solaris OS Issues CR Description Workaround 6479347 The Solaris prtdiag command displays device Force load all instances of the e1000g driver paths incorrectly for e1000g driver devices and then restart the picld daemon as follows devfsadm i e1000g svcadm restart svc system picl Another workaround is to use the r option when booting or rebooting the system 6552999 Performing a Control C while the prtdiag v If the environmental data is missing from the command is running causes blank prtdiag output restart the picld SMF service environmental data fields when run again in the control domain with the following The missing output is persistent until the picld command SMF service is restarted svcadm restart picl 6555956 Servers might experience panics generated from If your server experiences this panic perform the PCle root complex A panic could occur during reboot with the following message Fatal error has occurred in PCIe root complex The panic only occurs during a reboot and has never been observed during a reboot that follows the panic The panic can occur even if no external USB devices are connected to the server the workarounds described in Servers Might Experience
63. rvice indicator is set to ON Replace the disk drive with the lit Fault LED 6592272 An uncorrectable L2 writeback error might See L2 Cache Errors Might Generate an generate a memory fault message SUN4V 8000 E2 to the console Erroneous Memory Fault CR 6592272 on page 16 14 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 TABLE 2 1 Hardware and Mechanical Issues Continued CR Description Workaround 6614432 Erroneous power supply faults might be Ensure that both server power supplies are displayed operating When both power supplies are For an example see Erroneous Power Supply Operating the server will remain powered on Faults CR 6614432 on page 17 during and after erroneous faults Some servers report a low AC line input voltage fault when the input voltage is in the range of 90V to 94V AC This threshold is incorrect and should not indicate an AC input fault until the voltage drops below 90V AC 6616209 A power supply fan failure might not generate a To ensure continuous operation during a fault possible power supply fan fault ensure that Note This issue only applies to fan failures in both power supplies ae connected to two power supply 0 A fan failure in power supply 1 separate power circuits will generate a fault 6616232 Power supply fan faults are not automatically Power cycle the power supply that has the fan cleared fault to clear the fault If a fault is detected for
64. server is preinstalled with the OS patches and firmware but you can install the same or another supported version Be aware that some versions of the OS require installation of mandatory patches See Mandatory Patch Information on page 8 If you install the OS you will not have access to the additional software that was preinstalled at the factory See Preinstalled and Preloaded Software on page 4 TABLE 1 1 Supported Minimum and Preinstalled Versions of the OS and Firmware Supported Versions Minimum Supported Version Preinstalled Version os e Solaris 10 8 07 OS plus patches Solaris 10 8 07 OS Solaris 10 8 07 OS e Solaris 10 5 08 OS plus patches Firmware e System Firmware 7 0 3 System Firmware 7 0 3 System Firmware 7 1 0 g e System Firmware 7 1 0 g available from patch ID 136932 01 The OS and firmware versions listed in the Preinstalled Version column are current relative to the publication date of this docu ment Preinstalled versions change over time It is possible that your server was preinstalled with different versions than what is shown in this table depending on the time of purchase System Firmware The System Firmware controls various aspects of the host and the service processor The System Firmware comprises the following individual firmware components m Integrated Lights Out Manager ILOM 2 0 firmware m OpenBoot firmware POST firmware a Hypervisor firmware m VBSC firmware System
65. t Notes June 2008 TABLE 2 3 CR Firmware ILOM POST and SP Issues Continued Description Workaround 6596430 6596594 6598381 6601900 6602913 If the socketed EEPROM SCC is replaced the SP does not always read some SP properties from the new EEPROM If the SP configuration variable sc_backupuserdata is set to false the following user configuration values are not backed up to the socketed EEPROM if_emailalerts mgt_mailhost mgt_mailalert sc_customerinfo sc_powerondelay sc_powerstatememory sc_backupuserdata Changed OpenBoot NVRAM parameters do not take affect after a resetsc If the service processor is reset while the control domain is at the ok prompt OpenBoot PROM will permanently lose its ability to store nonvolatile LDoms variables or security keys until the host has been reset Guest domains are not affected by this problem Attempts to update LDoms variables or security keys results in the following warning messages WARNING Unable to update LDOM Variable WARNING Unable to store Security key In rare circumstances the PCIe interface unit PIU might issue a spurious error interrupt For examples see Spurious PIU Errors CR 6598381 on page 39 When the OpenBoot PROM is set to input device keyboard you might see the following warning message when the system host is powered on or reset No keyboard support found A US keyboard will work properly International keyboa
66. t in those rare cases where it might be called for you must unplumb all driver instances prior to unloading it 1 Find out which nxge instances are plumbed active using the ifconfig command ifconfig a 100 flags 2001000849 lt UP LOOPBACK RUNNING MULTICAST IPv4 VIRTUAL gt mtu 8232 index 1 inet 127 0 0 1 netmask ff000000 bge0 flags 201000843 lt UP BROADCAST RUNNING MULTICAST IPv4 CoS gt mtu 1500 index 2 inet 129 153 54 82 netmask ffffff00 broadcast 129 153 54 255 ether 0 14 4f 2a 9f 6a nxge2 flags 201000843 lt UP BROADCAST RUNNING MULTICAST IPv4 CoS gt mtu 1500 index 19 inet 129 153 54 175 netmask ffffff00 broadcast 129 153 54 255 ether 0 14 4f 6c 85 aa nxge3 flags 201000803 lt UP BROADCAST MULTICAST IPv4 CoS gt mtu 1500 index 20 inet 129 153 54 171 netmask ffffff00 broadcast 129 153 54 255 ether 0 14 4f 6c 85 ab 2 Unplumb each active port each port named nxge plus an instance number for example nxge2 nxge3 Example ifconfig nxge2 unplumb ifconfig nxge3 unplumb 3 Run ifconfig a again to verify that there are no active nxge interfaces Example ifconfig a 100 flags 2001000849 lt UP LOOPBACK RUNNING MULTICAST IPv4 VIRTUAL gt mtu 8232 index 1 inet 127 0 0 1 netmask 000000 bge0 flags 201000843 lt UP BROADCAST RUNNING MULTICAST IPv4 CoS gt mtu 1500 index 2 inet 129 153 54 82 netmask ffffff00 broadcast 129 153 54 255 ether 0 14 4f 2a 9f 6a
67. the following command from the Solaris OS svcadm restart svc system fmd default Resetting the SP Produces Extraneous Warning Messages CR 6585292 The following excerpt shows the extraneous messages that should be ignored sc gt resetsc similar messages are also displayed for the reset SP command Linux version 2 4 22 kbellew sanpen rh4 0 gcc version 3 3 4 2 Wed Jul 18 19 25 18 PDT 2007 r21410 Loading modules fpga Warning loading lib modules 2 4 22 misc fpga fpga o will taint the kernel non GPL license Proprietary See http www tux org 1kml export tainted for information about tainted modules Module fpga loaded with warnings fpga_flash Warning loading lib modules 2 4 22 misc fpga_flash fpga_flash o will taint the kernel no license See http www tux org lkml1 export tainted for information about tainted modules Module fpga_flash loaded with warnings immap Warning loading lib modules 2 4 22 misc immap immap o will taint the kernel no license Refer to http www tux org lkml export tainted for information about tainted modules Module immap loaded with warnings EXT3 fs warning maximal mount count reached running e2fsck is recommended EXT3 FS 2 4 0 9 19 19 August 2002 on tffs 100 1 internal journal EXT3 fs mounted filesystem with ordered data mode kjournald starting Commit interval 5 seconds EXT3 fs warning maximal mount count reached running e2fsck is recommended ipt_rec
68. the interfaces prior to unloading the running a system panic might occur driver See Using modunload While the nxge Port Is Running Could Cause a System Panic CR 6551509 on page 19 6553515 If a temporary PCIe network link failure occurs If system fails to boot because of this problem during boot or any time later the system could try booting again fail If the link is up and working again before the firmware gets control the error is a problem in firmware handling the leftover status For an example of the error see Temporary PCle Link Failure During Boot Causes a Fatal Error Later CR 6553515 on page 21 6554478 Receiving jumbo frames might drop the Ethernet Set the MTU size to 8172 as described in Jumbo interface to 30 Mbps due to packet dropping Frames Throughput of nxge Drops to 30 Mbps Due to Packet Dropping CR 6554478 on page 22 6555486 Ierrs are generated when 100Mb Full with Use auto negotiation to set the Link Forced Speed Duplex is set in the Speed Duplex parameter in the e1000g conf e1000g conf file file To set 100Mb full duplex for a e1000g0 These Ierrs are caused by the Forced device change the settings in the e1000g conf Speed Duplex parameter When the port is file configured to 100Mb full duplex with auto negotiation Ierrs are not generated See Terrs Generated When 100Mb Full With Forced Speed Duplex Is Set in e1000g conf CR 6555486 on page 24 6561389 Setting properties for the netw
69. the same physical machine might see the same or different sets of virtual processor IDs If the server is running LDoms the virtual processor IDs and physical processor IDs are never the same For information about the mapping between virtual and physical CPU numbers refer to the Logical Domains LDoms 1 0 2 Administration Guide Processor IDs are unique integer values in the domain where the software is running The integer value fits in the type processorid_t Also refer to the p_online 2 man page Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Cryptographic Support The UltraSPARC T2 multicore processor provides hardware assisted acceleration of symmetric AES 3DES and RC4 asymmetric RSA DSA Diffie Hellman and Elliptic Curve hashing SHA1 SHA256 and MDS and random number generation cryptographic operations The Solaris 10 8 07 OS or later provides the multithreaded device drivers that support the hardware assisted cryptography Additional cryptographic support is available when you obtain the IPsec activation package and enable the IPsec cryptographic hardware as described in the following section To Enable IPsec Cryptographic Hardware Acceleration To enable IPsec crypto operations to use the cryptographic hardware on the UltraSPARC T2 processor you must obtain and install the IPsec activation package 1 Obtain the IPsec activation package For information about obtaining the IPsec activat
70. ts might cause the system to From the ILOM CLI hang because some system services are gt stop SYS attempting to stop while others are still in the gt start SYS process of starting The hang occurs with a Has message similar to the following From the ALOM CMT compatibility CLI svc startd The system is coming down sc gt poweroff Please wait sc gt poweron svc startd 74 system services are now sc gt powercycle being stopped 6588550 The Solaris prtdiag v command is slow to Be aware of the delay and wait for the output respond on the Sun SPARC Enterprise T5120 Do not perform a Control C servers The command might take as long as 5 minutes to display output and therefore appears to hang 6589612 The raidct1 1 command continuously Use the Control C keyboard sequence to stop the outputs the following output raidctl 1 Controller 1 Volume c1t0d0 Volume c1t2d0 0 0 0 0 0 0 Disk Disk output Chapter 2 Late Breaking Issues 43 TABLE 2 4 Solaris OS Issues Continued CR Description Workaround 6592238 You might not be able to remove a RAID 1 Apply patch ID 126434 05 or later volume after RAID 1 and RAID 0 volumes are created When two volumes are created through the onboard SAS controller or any controller that uses the mpt driver the raidct1 utility is unable to delete one of the RAID volumes and cannot list the correct disk information When this occurs the following is the error message is
71. ve spconfig my new config ldm add spconfig my new config For more information refer to the Logical Domains LDoms 1 0 1 Release Notes When you add CPU or XAUI resources to a server configured to use logical domains you must revert to the factory default configuration to allow the LDoms Manager software to allocate those resources to guest domains Chapter 2 Late Breaking Issues 51 TABLE 2 6 LDom Related Issues Continued CR Description Workaround 6597761 rm io followed by multiple set vcpu Either cancel the existing delayed operations might cause the firmware to abort or 1dmd core dump During a single delayed reconfiguration operation do not attempt to add CPUs to a domain if any CPUs were previously removed during the same delayed reconfiguration reconfiguration first if possible or commit it by rebooting the target domain and then apply the CPU addition Failure to heed this restriction can under certain circumstances lead to the firmware returning a parse error to the LDoms Manager resulting in the LDoms Manager aborting Additionally if any VIO devices had been removed during the same delayed reconfiguration operation when the LDoms manager restarts after the abort it incorrectly detects the need to perform a recovery operation This situation results in a corrupt configuration followed by a power down 52 Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 Documentation
72. vents Are no Longer Transported CR 6594506 48 LDoms Related Issues 50 Documentation Errata 53 Sun SPARC Enterprise T5120 and T5220 Servers Administration Guide 53 Table 2 5 Lists Incorrect Device Identifiers 53 Under Table 2 4 in the Bullet List of Default Settings 53 Sun Integrated Lights Out Manager 2 0 Supplement for the Sun SPARC Enterprise 15120 and T5220 Servers 54 Incorrect Default Value Is Specified in the Procedure To Specify the Level of Diagnostics Using the CLI 54 Two ILOM Properties that Are not Described in This Manual 54 ALOM Compatibility CLI Example in the Section Adding a Commit Step on Page 38 Is Incomplete 54 Argument List for Resetting the Service Processor to Factory Defaults Is Incorrect 55 In Several Sun SPARC T5120 and T5220 Server Manuals 55 Hard Drive Logical Device Names Differ 55 Contents vii viii Sun SPARC Enterprise T5120 and T5220 Servers Product Notes June 2008 CHAPTER 1 Important Information About the Sun SPARC Enterprise T5120 and T5220 Servers This chapter describes important information about the Sun SPARC Enterprise T5120 and T5220 servers The following sections are included Technical Support and Documentation on page 2 Supported Versions of the OS and Firmware on page 3 Preinstalled and Preloaded Software on page 4 Mandatory Patch Information on page 8 Processor Identification on page 10 Cryptographic Support on page 1

Sun SPARC Enterprise T5120 and T5220 Servers Product Notes

Contents

Download Pdf Manuals

Related Search

Related Contents