Home

- Fujitsu

1. 128 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 CODE EXAMPLE A 1 Procedure for Recovering a Boot Drive s drive type Requesting System Maintenance Mode See lib svc share README for more information Console login service s cannot run Root password for system maintenance control d to bypass lt login single user mode single user privilege assigned to dev console Entering System Maintenance Mode Oct 20 18 06 11 su su root succeeded for root on dev console Sun Microsystems Inc SunOS 5 10GenericJanuary 2005 Sourcing profile EIS 3 Mount the tmpfs tmp filesystem to provide a working area root mount F tmpfs tmp root cd tmp 4 Capture the boot drive s existing vtoc ina file stored in tmp Use the raw device of the boot device determined at the beginning i e use dev rdsk c t d s not dev dsk c t d s root prtvtoc dev rdsk c0t0d0s0 gt tmp vtoc lt boot disk vtoc saved in tmp vtoc 5 Make a copy of the fmthard utility for use in the tmp work area root cp usr sbin fmthard tmp 6 Set and export the NOINUSE_CHECK variable root setenv NOINUSE CHECK 1 root export NOINUSE CHECK 7 Run the format utility to restore the drive s type root format Searching for disks done AVAILABLE DISK SELECTIONS 0 cOtO0dO lt drive type unknown gt lt drive type unknown is the issue pci 0 pci
2. Feature Minimum Firmware Version Minimum OS Version Mixed memory configurations 7 1 6 4 N A Systems using the External I O 7 1 6 d Solaris 10 10 08 OS Expansion Unit Systems operating with DC power 7 1 6 Solaris 10 10 08 OS supplies 8 disk capable T5120 servers 7 1 6 N A 16 disk capable T5220 servers 7 1 6 N A 1 6 GHz processors 7 2 2 e N A ILOM 3 0 firmware 7 2 2 e N A Hardware RAID 7 2 2 e N A LDoms 1 2 LDoms 1 3 t x When installing the following optional FB DIMM s into servers running with system firmware older than 7 1 6 d you need to update the firmware to 7 1 6 d or later Optional FB DIMMs SESX2A2_ 1GBx2 or SESX2B2_ 2GBx2 Make sure that all FB DIMMs in the server have the same capacity For details contact your service engineer For minimum firmware version minimum OS version and mandatory patches when using LDoms software see the Logical Domains Guide Note To benefit from the accumulated features enhancements and fixes upgrade your system firmware to the most recent version available 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 firmwares Chapter 2 Important Information About the SPARC Enterprise T5120 and T5220 Servers 11 OpenBoot firmware POST firmware Hypervisor firmware VBSC firmware
3. on number might not be displayed page 121 e The prtpicl command will not always You can also update the System Firmware to the display the physical platform section latest version to avoid encountering this issue 6586847 The Solaris prtdiag command without the v Note Fixed in the Solaris 10 5 08 OS and option does not show failures in the output later and in the Solaris 10 8 07 OS with patch ID 127127 11 or later installed Use the v option when running the prtdiag command You can also upgrade the OS or install the patch to avoid encountering this issue 6587389 The Solaris prtdiag v command might Note Fixed in the Solaris 10 5 08 OS and display information with missing spaces later and in the Solaris 10 8 07 OS with patch making the output difficult to read ID 127127 11 or later installed Use the showenvironment command from the ALOM CMT compatibility CLI as follows sc gt showenvironment For more details see The prtdiag v Command Has Formatting Issues CR 6587389 on page 123 You can also upgrade the OS or install the patch to avoid encountering this issue 6588452 Booting the Solaris OS from an external USB Note Fixed in the Solaris 10 5 08 OS and DVD ROM drive could cause a panic and fail to later and in the Solaris 10 8 07 OS with patch boot ID 127127 11 or later installed For more information see Booting the Solaris Use the built in DVD drive or use a drive whose OS From an External USB D
4. During the Power On Self Test the Diagnostic Process May Terminate Halfway CR 6835860 on page 111 6823516 In the DNS client settings the number of retries Note Fixed in System Firmware 7 2 7 b or later retries property cannot be set to 5 None Set the integer between 0 and 4 to the number of retries 6823725 Once you set the searchpath property of the Note Fixed in System Firmware 7 2 7 b or later DNS client function you cannot change it back to the default value none None 96 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6853843 On the DC input power model of SPARC Note Fixed in System Firmware 7 2 7 b or later Enterprise T5120 Server when you execute the None peedieg command of Solaris ny the f From ILOM check the component information Pryl ronmenpal Status AROME part 9 and the status of fan temperature power sensor the FRU Status information is not displayed and soon For the incomplete data output example see On the DC Input Power Model the Environmental Status and Some Part of the FRU Status Information Is Not Displayed CR 6853843 on page 112 6856163 If the service processor is initialized with the Note Fixed in System Firmware 7 2 7 b or later LAN cable disconnected from the ILOM Initialize the service processor with the LAN network port the ILOM
5. Note Fixed in System Firmware 7 1 6 d or later Use the show SYS command again and the product name is displayed You can also update the System Firmware to the latest version to avoid encountering this issue Note Fixed in System Firmware 7 1 6 d or later This error can be ignored The command actually succeeds and the SP is reset When the SP resets you lose the SSH connection to the SP You can also update the System Firmware to the latest version to avoid encountering this issue 84 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6589043 If there are fewer than 21 entries in the event Note Fixed in System Firmware 7 1 6 d or later log the showlogs command displays none of Use the showlogs v option to display the logs the events After 21 or more events are logged in the log file This situation is known to occur in the following you can revert back to using showlogs with no scenarios options e After a fresh installation of the system out of You can also update the System Firmware to the box the service processor SP event log is latest version to avoid encountering this issue 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 e
6. Fixed in System Firmware 7 1 0 g or later test failures can be misleading The POST error XAUI port and slot numbers should match for the messages can identify the correct port while SPARC Enterprise T5120 and T5220 servers Use reporting the wrong slot number the port number 6656072 POST failure messages can specify the wrong Note Fixed in System Firmware 7 1 0 g or later CPU 6743343 Test Alert generation alert test transmission Note Fixed in System Firmware 7 2 2 e or later may not be possible depending on the Alert None Type and Event under the alert rule settings 6847308 In the backup of the ILOM settings when the Note Fixed in System Firmware 7 2 7 b or later value of the system identifier property SP None system_identifier is its default value Delete the entry of SP system identifier none the value of the system description in the backup file a property SP system_description will be stored in the backup file Example of erroneously stored data lt entry gt lt property gt SP system_ identifier lt property gt lt value gt SPARC Enterprise T5120 ILOM v3 0 3 20 e r46064 lt value gt lt entry gt 6835860 For SPARC Enterprise T5220 Server during the Note Fixed in System Firmware 7 2 7 b or later power on self test POST the ERROR POST None ee our eet ARECA and the Power on the host again and perform the power diagnostic process may terminate halfway on self test POST For the example see
7. Incorrect ILOM Command Related to IP Address Assignment 67 The Command in the Section Edit an SNMP User Account Using the CLI on Page 195 is Incorrect 68 Integrated Lights Out Manager 2 0 Supplement for the SPARC Enterprise T5120 and T5220 Servers 68 vi SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Points of Concern about the Connection of ILOM CR 6806789 68 About ALOM CMT Shell Command 68 Integrated Lights Out Manager ILOM 3 0 CLI Procedures Guide 69 Erroneous Description in Collect SP Data to Diagnose System Problems CR 6806800 69 Erroneous Default Value for SP clients dns 69 Erroneous Description about Collecting SP Data 70 Integrated Lights Out Manager ILOM 3 0 Web Interface Procedures Guide 70 Erroneous Description about Collecting SP Data 70 Integrated Lights Out Manager ILOM 3 0 Supplement for SPARC Enterprise T5120 and T5220 Servers 71 Notes on ILOM Information Stored on the SCC 71 Fixed Issues 73 Hardware and Mechanical Issues 73 L2 Cache Errors Might Generate an Erroneous Memory Fault CR 6592272 74 Ethernet Interface Related Issues 75 Using modunload While the nxge Port Is Running Could Cause a System Panic CR 6551509 76 v To Unplumb the Interfaces Prior to Unloading the Driver 77 Jumbo Frames Throughput of nxge Drops to 30 Mbps Due to Packet Dropping CR 6554478 78 v To Set the MTU Size to 8172 79 Setting Properties for nxge Devices Might Fail CR 6561389 80
8. System Firmware updates are available from the following web site as patch releases https updatesite jp fujitsu com unix en download firmware When you update the System Firmware all of the individual firmware components are updated You cannot update firmware components individually Refer to the SPARC Enterprise T5120 and T5220 Servers Installation Guide for more information about updating the server firmware TABLE 2 3 Preinstalled Software This section describes the following m Preinstalled software TABLE 2 3 that is ready to use Preinstalled Software Software Location Function Solaris 10 5 09 OS CMT Tools 1 0 Cool Tools GCC v 4 0 4 LDoms Manager LDoms MIB 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 SUNWspro extra bin opt gec and opt SUNWOscgfss opt SUNW1dm opt SUNW1dmib opt SUNWspro extra bin opt SUNWspro Operating system and alternate boot environment See Solaris 10 OS and Solaris Live Upgrade on page 13 Sun Studio Developer Tools GCC compiler for SPARC systems See Additional Software Available for Your Server Cool Tools on page 13 Manages Logical Domains LDoms Management Information Base Sun Studio Developer Tools See Sun Studio C C amp Fortran Compilers and Tools on page 15
9. information on both consoles In addition when Install patch ID 137111 01 or higher the system is halted or a break is sent to the e Use only the virtual console Ensure that the console control is passed to the virtual console f f default value of virtual console is set for which requires keyboard input over the virtual i 7 both the input device and output device console As a result the graphics console variables appears to hang 6582340 When you are connected to the virtual console Note Fixed in System Firmware 7 2 2 e or later and you enter the escape character sequence to enter the SP CLI the following two error messages might display before reaching the CLI 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 If you are refused write access when you initiate a connection to the host with the console command enter console f the force option to get read and write access Appendix A Fixed Issues 83 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6582853 The showfaults ALOM CMT compatibility command reports the motherboard as faulty instead of the actual faulty DIMM or PCle card 6585340 The uadmin 2 0 and reboot commands read old bootmode settings 6587869 Using the consolehistory e c
10. 78 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 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 nxgel file and place the following two lines in it nxge portl nxge portl mtu 8172 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 1 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 ffffff00 5 Type 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 4 6 c 88 5 If you want to set parameters permanently for other interfaces create etc hostname nxge0d 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
11. Appendix A Fixed Issues 79 Setting Properties for nxge Devices Might Fail CR 6561389 This issue is resolved for servers running the Solaris 10 5 08 OS and later If you are running Solaris 10 8 07 you can fix this issue with patch ID 127127 11 or later 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 niu 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 This issue is resolved for servers running the Solaris 10 5 08 OS and later If you are running Solaris 10 8 07 you can fix this issue with patch ID 127127 11 or later 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
12. CR 6594506 This issue is resolved with Solaris patch ID 125369 12 or later After certain hardware error events it is possible that PSH events are no longer transported between the Service Processor SP and the domain The scenarios subject to this CR m Inanon LDoms environment an unrecoverable error in the Solaris domain m In an LDoms environment an unrecoverable error in the control domain a Ineither an LDoms or non LDoms environment a fatal error in the system a fatal error resets the system at the HW level Appendix A Fixed Issues 101 Note In an LDoms environment unrecoverable errors in a non control LDoms guest domain are not subject to this CR 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 0x1ldfeda2137e PLATFORM SUNW SPARC Enterprise T5220 CSN HOSTNAME wgs48 100 SOURCE SunOS REV 5 10 Generic _Patch DESC Errors have been detected that require a reboot to ensure system integrity See http www sun com msg SUNOS 8000 0G for more information AUTO RESPONSE Solaris will attempt to save and diagnose the error telemetry IMPACT 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 Or an
13. Server Might Panic in nxge_start When dupb Fails CR 6567838 80 v To Disable Jumbo Frames 80 v To Set the MTU to a Smaller Size 81 Firmware ILOM POST and SP Issues 82 SP Serial Line Terminal Server break Command Does Not Work CR 6577528 98 Contents vii The showfaults Command Shows the Motherboard as Faulty Instead of the DIMM CR 6582853 99 The uadmin 2 0 and reboot Commands Read Old Bootmode Settings CR 6585340 100 Domain ETM and LDC Deadlock When Transmit Queue Full CR 6594506 101 Spurious PIU Errors CR 6598381 104 Diagnostic Routine That Runs at Startup IBIST Might Accidentally Disconnect the MCU CR 6618773 105 MCU Might Be Disconnected in DIMM Module Failure CR 6656116 106 When the showenvironment Command is Executed in a Sixteen Disk Capable Server Even Though the Hard Disk is Mounted in Slot 8 NOT PRESENT is Output CR 6772707 107 For DC Input Power Models the Output From the showpower v Command May Differ Between SYS PSO And SYS PS1 CR 6802433 109 In the Output From the prtdiag Command Warnings May Be Displayed CR 6821325 110 During the Power On Self Test the Diagnostic Process May Terminate Halfway CR 6835860 111 On the DC Input Power Model the Environmental Status and Some Part of the FRU Status Information Is Not Displayed CR 6853843 112 When the Service Processor Is Initialized I LOM May Fails to Start With an Error Message Displayed CR 6856163 113 After
14. information After replacing the motherboard set the saved setting information again Procedure for saving ILOM firmware setting information 1 Log in to ILOM execute the following commands and save the displayed results gt show SP level all o table gt show SYS o table gt show HOST level all o table 2 Log in to the ALOM CMT compatibility shell execute the following command and save the displayed results sc gt showsc 6762635 One of the following messages may be output Recovery procedure while a POST self diagnostics test is in Disconnect and then reconnect the power cable progress and POST processing may not be completed Also a transition to OpenBoot PROM OBP may occur Message examples Fault Sensor VMEML POK at SYS MB deasserted Fault Sensor VCORE POK at SYS MB deasserted Fault Sensor VMEMR POK at SYS MB deasserted 6761778 The following error message may be displayed Ignore this message Message example picld 154 ID 276222 daemon error PICL snmpplugin sunPlatSensorClass 0 unsupported row 388 Chapter 3 Known Issues 31 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6752910 After a host power on instruction is executed After turning off the power to the host wait at from ILOM the POST self diagnostics test may least three minutes before turning it on again not start and processing may not go to OS boot processing or the ok prom
15. under certain during the same delayed reconfiguration 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 You can also update the System Firmware to the latest version to avoid encountering this issue in the future 136 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 cO FUJITSU
16. 12 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Note Previously the Sun Java Enterprise System software package was placed in the var spool stage JES5 Solaris_ sparc directory at the factory This is no longer the case If you want to install the Sun Java Enterprise System software download it from http www sun com software javaenterprisesystem 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 16 Note Some software that is provided in the Solaris OS 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 1iveupgrade 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 technology 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
17. 1dm add io pci 400 guestB Save new configuration to SP 2 1dm add io pci 600 guestA 5 clean shutdown and power cycle 3 ldm add io pci 700 guestC Case2 7 If the you assign I O branches to guest If you encounter this hang you can recover by domains in any order except in numerical order booting the system with either a prior working one or more of the guest domains will be unable configuration or with the factory default to start configuration For example the following actions performed in The system can be booted to an earlier working the sequence shown might lead to one or more configuration or in the factory default guest domains hanging when they are started configuration by executing following sequence of 1 1dm add io pci 600 guestA commands in the ALOM CLI on the service 2 1dm add io pci 500 guestB processor SP 3 ldm add io pci 700 guestC 1 sc gt bootmode config name_of_config 2 sc gt poweron 3 sc gt poweroff The name_of_config is the working configuration saved on the service processor If no such configurations exists on the service processor use factory default as the name of the configuration Note If the factory default configuration is used in the above procedure then you must reconfigure all of the guest domains and the primary domain 94 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround
18. 20 L6 15 and L5 15 For details of the power cord type for your server contact your authorized service engineer SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 CHAPTER 3 Known Issues This chapter describes known issues about the SPARC Enterprise T5120 and T5220 servers The following sections are included Hardware and Mechanical Issues on page 22 Ethernet Interface Related Issues on page 25 Firmware ILOM POST and SP Issues on page 27 Solaris OS Issues on page 52 LDoms Related Issues on page 58 Note For the issues already fixed in the latest version of Solaris OS or System Firmware see Appendix A For the latest version to be supported see Supported Versions of the OS and Firmware on page 10 21 Hardware and Mechanical Issues TABLE 3 1 lists the late breaking hardware and mechanical issues Additional information for some of the issues is provided after the table TABLE 3 1 Hardware and Mechanical Issues CR Description Workaround 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 compone
19. 6730610 In certain circumstances you might encounter Note Fixed in System Firmware 7 2 2 e or later these error messages when powering on Case 1 POST has determined that multiple FB T5120 T5220 servers DIMMS have failed on T5120 T5220 servers with Chassis major Jul 27 16 40 17 64 8 Gbyte FB DIMMS ERROR dt_allocprop prop NULL Recovery 1 If POST takes a FB DIMM offline Not enough memory to expand MD for you must replace it immediately If replacing the new property fwd failed FB DIMM is not immediately possible or Chassis major Jul 27 16 40 17 desired you must disable the corresponding FB ERROR dt_allocnode Not enough DIMMs on the other CMP memory modules memory to expand MD for new node corresponding memory branches to guarantee a mblock contiguous memory configuration Chassis critical Jul 27 16 41 55 Type one of the following FATAL The Service Processor gt set SY S component software has taken a FATAL component _state disabled configuration error sc gt disablecomponent asr key Chassis critical the HOST Process Type one of the following commands to display a cannot pen started list of enabled and disabled devices Chassis critical Please examine gt show components the logs to determine the reason for failure And then sc gt showcomponent na For each FB DIMM device that is disabled Chassis critical reset the 5 f E E disable the corresponding FB DIMM associated i with the other CMP memory
20. 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 80 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 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 systen file 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 ifconfig 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 port1 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 portl nxge portl mtu 4076 Appendix A Fixed Issues 81 Firmware ILOM POST and SP Issues TABLE A 3 lists the firmware ILOM POST and SP issues that have been fixed TABLE A 3 Fixed Firmware
21. ILOM POST and SP Issues CR Description Workaround 6541482 POST always starts on the lowest available Note Fixed in System Firmware 7 1 6 d or later strand even when that strand is disabled If strand 0 of the first physical core is known to be If processor strand 0 of the first available good then it can be enabled by using the physical core has been marked disabled as seen enablecomponent ALOM CMT compatibility in the list of disabled devices in the output of the command followed by power on reset of the showcomponent command a new master system poweroff followed by poweron ALOM strand is selected by the initialization process CMT compatibility commands and the disabled strand is taken offline But the Jf strand 0 of the first physical core is known to be system initialization and execution of power on had there is no workaround The motherboard self test POST occurs using the disabled must be replaced processor strand beca se power n anid res t You can also update the System Firmware to the execution always starts on strand 0 of the first latest version to avoid encountering this issue 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 6549028 The netsc_commit command might cause the Note Fixed in System Firmware 7 1 6 d or later system to
22. ILOM POST and SP Issues Continued CR Description Workaround 6615884 The help message is incorrect in the ILOM BI Note Fixed in System Firmware 7 0 9 or later 6614576 The informational text displayed on the Be aware of this discrepancy Configuration Serial Port tab in the ILOM BI refers to a DB 9 connector but the message should refer to the RJ 45 connector 6616693 When the information obtained by using IPMI Note Fixed in System Firmware 7 0 9 or later the information such as the Product Part Log in to ILOM and refer to the information such Number of the server is not displayed correctly as SYS 6618773 A diagnostic routine that runs at startup IBIST Note Fixed in System Firmware 7 1 0 g or later might disconnect the memory controller unit Install Patch 127580 04 or later and update the MCU resulting in errors System Firmware to version 7 0 9 or later For an example of the errors see Diagnostic Routine That Runs at Startup IBIST Might Accidentally Disconnect the MCU CR 6618773 on page 105 6622444 In the mirroring configuration of the system Note Fixed in System Firmware 7 0 9 or later volume disk using the PRIMECLUSTER GDS When the process returned to the ok prompt when an error occurred while reading the boot reexecute the boot command to start the OS block of boot disk the boot path does not switch At this time the following message appears and the process returns to the ok prompt Boot lo
23. Log entries since Sep 29 12 45 39 Sep 29 12 45 39 Chassis major Host has been powered on Sep 29 12 49 28 Chassis major Host is running Sep 29 12 49 43 Chassis critical Host has been powered off Chapter 3 Known Issues 43 Sep 29 12 50 47 Chassis major Host has been powered on Sep 29 12 54 35 Chassis major Host is running Sep 29 12 54 51 Chassis critical Host has been powered off There is no Host has been powered on log entry after this sc gt For DC Input Power Models PSO AC_POK Is Displayed CR 6815369 For DC input power models PS0 AC_POK and PS0 DC_POK identify sensors in the power supply units PS0 AC_POK does not represent an AC power supply unit For example the following event log is collected when the DC power cable is disconnected or reconnected When the DC power cable is disconnected IPMI minor ID lcec 02 06 2009 04 00 26 Power Supply PSO AC_POK State Deasserted lt IPMI minor ID 1lced 02 06 2009 04 00 26 Power Supply PSO DC_POK State Deasserted IPMI minor ID lcee 02 06 2009 04 00 26 Power Supply PSO FAIL State Asserted When the DC power cable is reconnected IPMI minor ID lcef 02 06 2009 04 00 59 Power Supply PSO AC_POK State Asserted lt IPMI minor ID 1cf0 02 06 2009 04 00 59 Power Supply PSO DC_POK State Asserted IPMI minor ID 1cf
24. Servers for details Serial Line Terminal Server STERR Command You can also update the System Firmware to the Does Not Work R 6577528 on page 98 latest version to avoid encountering this issue 6579390 After disabling a DIMM the OpenBoot PROM Note Fixed in System Firmware 7 2 2 e or later banner does not show a decrease in the amount If you manually disable any CPU or memory of memory resource with the ASR commands while the host is powered on you must power cycle the host to complete the disabling of the resource After the power cycle the resource will be disabled and the proper information will be displayed in the banner 6581309 Console behavior is inconsistent when a Note Fixed in Solaris patch ID 137111 01 or graphics device and keyboard are specified for later console use If the graphics console appears hung connect to This behavior occurs when the OpenBoot the virtual console from the system processor to variables input device and output device provide the required input Press Return on the are set to anything other than the default value virtual console keyboard once to see the output of virtual console on the virtual console If this workaround does If the control domain is set this way some not work contact your service engineer console messages are sent to the graphics console and others are sent to the virtual To prevent the problem perform one of the console This situation results in incomplete following workarounds
25. 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 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 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 Domain ETM and LDC Deadlock When Transmit Queue Full
26. device Note Fixed in the Solaris 10 5 08 OS and 6479347 paths incorrectly for e1000g driver devices later and in the Solaris 10 8 07 OS with patch ID 127127 11 or later installed Force load all instances of the e1000g driver 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 You can also upgrade the OS or install the patch to avoid encountering this issue 6527622 After the OS panic the server may display the Note Fixed in Solaris patch ID 127111 05 or following message and stop at the ok prompt later WARNING promif_ldom_setprop ds Set auto boot true or use the boot response timeout command to start the server manually WARNING unable to store boot command for use on reboot 6536482 Currently coummem does not diagnose the Note Fixed in Solaris patch ID 127127 11 or fbr fbu errors later 6552999 Performing a Control C while the prtdiag v Note Fixed in the Solaris 10 10 08 OS or by command is running causes blank installing patch ID 13094 01 or later environmental data fields when run again If the environmental data is missing from the The missing output is persistent until the picld prtdiag output restart the picld SMF service SMF service is restarted in the control domain with the following command svcadm restart picl You can also upgrade the OS or install the patch to avoid encoun
27. file accept _jumbo 1 You can also upgrade the OS or install the patch to avoid encountering this issue Appendix A Fixed Issues 75 TABLE A 2 Fixed Ethernet Related Issues Continued CR Description Workaround 6567838 6599334 6599105 The server might panic in nxge_start when the dupb fails If Jumbo Frames are enabled the system might 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 Note This scenario is rare and only occurs with frame sizes larger than 4076 XAUI interfaces might not be disabled when 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 Jumbo does not work for packets larger than 8144 bytes when bcopy is forced Note Fixed in the Solaris 10 5 08 OS and later and in the Solaris 10 8 07 OS with patch ID 127127 11 or later installed Disable the use of Jumbo Frames but be aware that doing so impacts system performance You should only apply the workarounds if your server is experiencing this problem For details on this workaround see Server Might Panic in nxge_start When dupb Fails CR 6567838 on page 80 You can also upgrade the OS or instal
28. following command set SP services snmp users wusername authenticationpassword password Integrated Lights Out Manager 2 0 Supplement for the SPARC Enterprise T5120 and T5220 Servers Points of Concern about the Connection of ILOM CR 6806789 On the SPARC Enterprise T5120 and T5220 servers ILOM supports a maximum of 5 active sessions including serial Secure Shell SSH and web interface sessions About ALOM CMT Shell Command This manual focuses on the basic usage of the ALOM CMT compatibility shell command For details of the ALOM CMT shell command see Advanced Lights Out Management ALOM CMT v1 x Guide C120 E386 68 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Integrated Lights Out Manager ILOM 3 0 CLI Procedures Guide Erroneous Description in Collect SP Data to Diagnose System Problems CR 6806800 The following description in the section Collect SP Data to Diagnose System Problems on page 88 includes incorrect information Variable Option Description URI Any valid target directory location Specifies the URI of the target directory The URI format is as follows protocol username password host directory Where protocol can be one of these transfer methods SFTP TFTP or FTP For example to store the snapshot information in the directory named data on the host define the URI as follows ftp joe mypasswd host_ip_address data The directory data is r
29. for the firmware ILOM including ALOM compatibility CLI POST and service processor SP Additional information for some of the issues is provided following the table Firmware ILOM POST and SP Issues CR Description Workaround 6237994 6510082 6556505 6568750 6573354 6583567 Registration with DMI could fail with an err 831 message For users familiar with ALOM CMT and using the ALOM CMT compatibility CLI the help for the consolehistory command displays both a boot and a run option Both options result in the same output because ILOM makes no distinction between the run and boot buffers 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 PCIe root complex of the UltraSPARC T2 CPU does not properly train the PCle 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 The method for clearing POST results displayed with the showfaults command has changed 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 A communication channel between the primary d
30. hang Reboot the system Through a serial connection the network might Jf rebooting fails to reset the SP AC power cycle not be visible the system to recover the SP Be aware that you will lose active domains You can also update the System Firmware to the latest version to avoid encountering this issue 6583392 POST might encounter intermittent POST PIU0 Note Fixed in System Firmware 7 1 6 d or later 6571886 link train errors during a power cycle test Power cycle the system as follows example uses the ALOM CMT compatibility CLI sc gt poweroff fy sc gt clearasrdb sc gt poweron c You can also update the System Firmware to the latest version to avoid encountering this issue 82 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6577528 A terminal server break command does not Note Fixed in System Firmware 7 1 6 d or later work on the SP serial port Use the break commands from the SP either the If you use Telnet to connect to the SP serial line ILOM or ALOM CMT compatibility commands with a terminal server such as the Cisco ASM to send a break to the Solaris host series and try to send a break to the Solaris __ Refer to the Integrated Lights Out Management host the break command does not work and is ILOM Supplement for SPARC Enterprise T5120 and ignored by the SP For a sample output see SP T5220
31. ignored Chapter 1 New Information About the SPARC Enterprise T5120 and T5220 Servers 7 8 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 CHAPTER 2 Important Information About the SPARC Enterprise T5120 and T5220 Servers This chapter describes important information about the SPARC Enterprise T5120 and T5220 servers The following sections are included Notes on DVD Drive and Discs on page 9 Supported Versions of the OS and Firmware on page 10 Solaris OS and Firmware Requirements for Certain Features on page 11 Preinstalled Software on page 12 Mandatory Patch Information on page 16 General Functionality Issues and Limitations on page 18 Processor Identification on page 19 Notes on the Use of 200V Power Supply on page 20 Notes on DVD Drive and Discs See the Notes on DVD Drive and Discs in SPARC Enterprise on the website below before using the CD DVD discs in the standard DVD drive mounted in this server http www fujitsu com sparcenterprise manual Supported Versions of the OS and Firmware TABLE 2 1 lists the versions of Solaris OS and system firmware supported for SPARC Enterprise T5120 and T5220 servers Your server is preinstalled with the latest supported OS patches and firmware If you decide to install some other supported version be certain to also install the patches required by that version For information
32. in DIMM Module Failure CR 6656116 on page 106 Identify and replace the faulty DIMM module 88 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6654695 The following message is displayed when the Note Fixed in System Firmware 7 1 3 d or later clear_fault_action property of the SYS objectis Clear the error by using the FRU name provided set to true but no processing is executed by the show SP faultmgmt command Message example Set clear fault_action to true The SYS object clear_fault_action property has been corrected in System Firmware 7 1 3 d or later 6768806 An attempt to read the properties of the power Note Fixed in System Firmware 7 2 2 e or later supply unit PSU may be unsuccessful and None cause the ILOM session to terminate It is however possible to check the PSU properties with the showfru command of the gt show level all o table SYS PSO ALOM CMT compatibility shell Target Property Value O AE E E E E A see Connection to XXX XXX XXX XXX closed 6784525 In a sixteen disk capable server the Ready to Note Fixed in System Firmware 7 2 2 e or later Remove LED does not go on when hard disks Instead of using the Ready to Remove LED use mounted in slots 8 to 15 are hot replaced the execution result of the cEgadm 1 command If the status becomes unconfigured hot repla
33. in single user mode with the root filesystem mounted read only Mount the tmpfs tmp filesystem to provide a working area Capture the boot drive s existing vtoc in a file stored in tmp Make a copy of the fmthard utility for use in the tmp work area Set and export the NOINUSE_CHECK variable to allow the format command full access to the boot drive Run the format utility to restore the drive s type Use the fmthard command and stored information to complete the recovery SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 9 Verify the success of the recovery CODE EXAMPLE A 1 Procedure for Recovering a Boot Drive s drive type I Determine if the boot drive is affected root host 1 uname a SunOS host 1 5 10 Generic _141414 10 sun4v sparc SUNW SPARC Enterprise T5220 root host 1 mount p head 1 dev dsk cOt0d0so ufs no rw intr largefiles logging xattr onerror panic root host 1 format cOt0d0s0 lt boot device determined previously dev dsk cOt0d0s0O is currently mounted on Please see umount 1M dev dsk c0Ot0d0s1 is currently used by swap Please see swap 1M FORMAT MENU disk select a disk type select define a disk type partition select define a partition table Appendix A Fixed Issues 127 CODE EXAMPLE A 1 Procedure for Recovering a Boot Drive s drive type format format and analyze the disk repair repair
34. logical domains and maps logical domains to physical resources Note The LDoms MIB must be configured before you can use it A README file with configuration instructions is located in the LDoms MIB installation directory opt ldoms_mib For more information on LDoms go to http www fujitsu com global services computing server sparcent erprise products software ldoms Supported Sun Explorer Utility Version 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 SPARC Enterprise T5120 and T5220 servers are supported by the Sun Explorer 5 10 or later data collection utility but are not supported by earlier releases of the utility Determine whether an earlier version of the Sun Explorer product has been installed on your system by typing the following pkginfo 1 SUNWexplo If an earlier version exists uninstall it and install version 5 10 or later For information on how to get the Sun Explorer Utility please contact a certified service engineer 14 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 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 Chapter 2 Importa
35. mid September to early October 2009 approximately 3 weeks a patch was preinstalled on some SPARC Enterprise T5120 and T5220 servers which introduced a latent bug into those systems The bug is described as latent because it is activated only when the Solaris format command is used Otherwise the bug has no effect on system behavior or performance Appendix A Fixed Issues 125 126 When a system administrator or other user with root privileges enters the format command on a system containing this bug the boot drive will report drive type unknown This fault condition presents two problems for the administrator The administrator will be unable to access unused portions of the boot drive because of the unknown drive type error The presence of mounted partitions blocks use of the format utility s auto configure feature Attempts to bypass this restriction by booting from the network or removable media could put the system in an unbootable state The Workaround section below describes a procedure you can use to recover from this drive type unknown fault mode without the risks associated with the network and media boot methods Workaround The sequence of steps shown in CODE EXAMPLE 1 must be followed exactly as shown To simplify tracking of the procedure the steps are organized into nine sections 1 2 Determine whether or not the system s boot device is affected Shut server down and restart
36. minor and Type IPMI PET to Type SNMP Trap the level setting changes to disable The level must be set again While the external I O expansion unit is being None powered on when you power off on the server the SNMP information of the external I O expansion unit may fail to be obtained It can be recovered by removal insert of the power cord of the external I O expansion unit and power off on of the server When you set HOST bootfailrecovery to None powercycle powercycle host power off on Set to powerof wait for the host power turns fails to be executed off and then manually turn on the host power 36 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6883269 After downgrading the system firmware from None 7 2 x to 7 1 x Condition of the I USBO and I_USB1 may be displayed as fail in the output of prtdiag v command It can be recovered by removal insert of the power cords Output Example Voltage indicators Location Indicator Condition SYS MB VCORE_POK ok SYS MB VMEML POK ok SYS MB VMEMR_POK ok SYS MB I_USBO fail lt SYS MB I_USB1 fail lt 6913388 The ILOM event log may not be in the Solaris None OS system log output var adm messages Perform the ILOM reset operation If not ILOM login event example recovered shut down the system and then Nov 7 14 13 03 xxxxxx SC Alert ID Temov
37. ok Prompt is Not Displayed After displayed normally after POST execution ends POST Ends CR 11215994 on page 49 Chapter 3 Known Issues 35 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6739633 6738510 6739602 6837115 6765542 6881020 When the host is off any prepare_to_remove Make the following setting from the CLI operation for the component selected in the e set SYS selected component ILOM Web interface System Information tab gt return to service action true Components tab may cause the radio button of T the component to disappear In the Ready to Remove Status column NotReady changes to Ready No Power for the component but Return to Service cannot be performed for the component because the radio button is no longer displayed Specifying the t option in certain commands None create delete exit load reset set start stop version may cause a forced logout from the ILOM CLI If the logdetail property in If ActiveDirectory is set to disabled ignore the SP clients activedirectory is set to a message value other than none the following authentication error message may be displayed even if ActiveDirectory is set to disabled state disabled sc gt ActDir critical ActDir authentication status auth ERROR On the ILOM Web interface when you change None the Alert Management settings from Level
38. panic The panic can occur even if no external USB devices are connected to the server Workarounds 120 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 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 a 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 a Using the ALOM CMT compatibility CLI sc gt disablecomponent SYS MB PCIE I0 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 MB PCIE IO USB component state Enabled a Using the ALOM CMT compatibility CLI sc gt enablecomponen
39. saved to ldm remove spconfig my new config the service processor and then later changed ldm add spconfig my new config back to its default value the change to its You can also update the System Firmware to the default value will not persist after a power cycle Jatest version to avoid encountering this issue in the future 6594395 The ldm set variable command allows you Note Fixed in System Firmware 7 1 0 g or 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 later For more information refer to the Logical Domains LDoms 1 0 1 Release Notes You can also update the System Firmware to the latest version to avoid encountering this issue in the future Appendix A Fixed Issues 135 TABLE A 5 Fixed LDoms Related Issues Continued CR Description Workaround 6597761 rm io followed by multiple set vcpu Note Fixed in System Firmware 7 0 9 or later operations might cause the firmware to abort or Either cancel the existing delayed 1dmd core dump reconfiguration first if possible or commit it During a single delayed reconfiguration by rebooting the target domain and then apply operation do not attempt to add CPUs to a the CPU addition domain if any CPUs were previously removed Failure to heed this restriction can
40. tod 0x46d2da57 0x1d998280 These events are harmless and can be ignored 104 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Diagnostic Routine That Runs at Startup IBIST Might Accidentally Disconnect the MCU CR 6618773 This issue is resolved by updating the system firmware to 7 1 0 g or later In some cases the MCU is disconnected from corresponding DIMM modules and CPU cores and the following messages are reported to the console For example Chassis major Host has been powered on Chassis major Dec 19 08 45 11 ERROR MB CMP0 MCU2 Failed IBIST disabled Fault critical SP detected fault at time Wed Dec 19 08 45 12 2007 SYS MB CMP0 MCU2 Forced fail IBIST Chassis major Dec 19 08 45 13 ERROR MB CMP0 MCU3 unused because MB CMPO MCU2 is not configured Chassis major Dec 19 08 45 13 ERROR MB CMP0O L2_BANK4 MB CMP0 L2_BANK5 unused because MB CMP0 MCU2 is not configured Chassis major Dec 19 08 45 13 ERROR MB CMPO L2 BANK6 MB CMP0 L2_BANK7 unused because MB CMP0 MCU3 is not configured Chassis major Dec 19 08 45 13 ERROR Degraded configuration system operating at reduced capacity Chassis major Dec 19 08 45 13 ERROR System DRAM Available 008192 MB 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 versio
41. unrecoverable error causes the Hypervisor 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 After the control domain recovers there is a diagnosis performed Messages to the console indicate the cause of the unrecoverable error For example SUNW MSG ID SUN4V 8000 UQ TYPE Fault VER 1 SEVERITY Critical EVENT TIME Fri Aug 17 18 00 57 EDT 2007 PLATFORM SUNW SPARC Enterprise T5220 CSN HOSTNAME wgs48 100 SOURCE cpumem diagnosis REV 1 6 EVENT ID a8b0eb18 6449 c0a7 cc0Of e230a1d27243 DESC The number of level 2 cache uncorrectable data errors has exceeded acceptable levels Refer to http sun com msg SUN4V 8000 UQ for more information AUTO RESPONSE No automated response IMPACT System performance is likely to be affected REC 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 At this point CR 6594506 might have been encountered This will prevent future PSH events for example new HW errors correctable or uncorrectable from being transported into the domain and properly diagnosed 102 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Workaround After the domain recovers and the diagnosis message is printed to the Sola
42. 0 CODE EXAMPLE A 1 Procedure for Recovering a Boot Drive s drive type 8 Use the fmthard command and stored information to complete the recovery root tmp fmthard s tmp vtoc dev rdsk c0t0d0s0 lt raw boot device used to capture vtoc fmthard New volume table of contents now in place roote 9 Verify the success of the recovery root format Searching for disks done AVAILABLE DISK SELECTIONS 0 cOtOdO lt SUN72G cyl 14087 alt 2 hd 24 sec 424 gt pci 0 pci 0 pcie 2 scsi 0 sd o 0 Specify disk enter its number 0 selecting cOt0do disk formatted FORMAT MENU disk select a disk type select define a disk type partition select define a partition table current describe the current disk format format and analyze the disk repair repair a defective sector label write label to the disk analyze surface analysis defect defect list management backup search for backup labels verify read and display labels save save new disk partition definitions inquiry show vendor product and revision volname set 8 character volume name The jumpstart install process lt cmd gt execute lt cmd gt then return quit format gt partition PARTITION MENU 0 change 0 partition 1 change 1 partition 2 change 2 partition 3 change 3 partition 4 change 4 partition Appendix A Fixed Issues 131 CODE EXAMPLE A 1 Procedure for Rec
43. 0 10 09 installer and information may fail to be written correctly perform the labeling as described below 1 Terminate SunInstaller 2 Use the format e command to execute the following 2 1 to 2 3 2 1 Label the target disk with SMI label 2 2 Label the target disk with EFI label 2 3 Label the target disk with SMI label 6 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Firmware ILOM POST and SP Issues TABLE 1 2 Firmware ILOM POST and SP Issues CR Description Workaround 6835866 The value of power consumption shown by None 6857524 SYS VPS SYS VPS value may exceed the The value of power consumption shown by 6858176 threshold value At this time an event log as SYS VPS is given as an indication shown below will be collected Event log example 4368 Mon Jun 29 23 53 39 2009 IPMI Log major ID elf 06 29 2009 23 53 39 Power Unit SYS VPS Upper Critical going high reading 1480 90 gt threshold 1215 40 Watts And when the power consumption value SYS VPS value has come back to under the threshold it may display an abnormal value Abnormal value display example 4369 Mon Jun 29 23 54 28 2009 IPMI Log minor ID e20 06 29 2009 23 54 28 Power Unit SYS VPS Upper Critical going low reading 0 lt threshold 1215 40 Watts For the right value of power consumption see SP powermgmt actual_power Therefore the collected event log can be safely
44. 0 pci 2 scsi 0 sd 0 0 Specify disk enter its number 0 Appendix A Fixed Issues 129 CODE EXAMPLE A 1 Procedure for Recovering a Boot Drive s drive type Format will now present the following menu choose 0 Auto configure AVAILABLE DRIVE TYPES 0 Auto configure 1 Quantum ProDrive 80S 2 Quantum ProDrive 105S eee 17 Zip 250 18 Peerless 10GB 19 other Specify disk type enter its number 0 c0t0d0 configured with capacity of 68 35GB lt drive type corrected lt SUN72G cyl 14087 alt 2 hd 24 sec 424 gt lt drive type corrected selecting cOt0odo disk formatted Following Auto configure the correct drive value should be reported FORMAT MENU disk select a disk type select define a disk type partition select define a partition table current describe the current disk format format and analyze the disk repair repair a defective sector label write label to the disk analyze surface analysis defect defect list management backup search for backup labels verify read and display labels save save new disk partition definitions inquiry show vendor product and revision volname set 8 character volume name The jumpstart install process lt cmd gt execute lt cmd gt then return quit format gt label Ready to label disk continue y format gt quit root 130 SPARC Enterprise T5120 and T5220 Servers Product Notes April 201
45. 00849 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 It is now safe to unload the nxge driver Jumbo Frames Throughput of nxge Drops to 30 Mbps Due to Packet Dropping CR 6554478 This issue is resolved for servers running the Solaris 10 5 08 OS and later If you are running Solaris 10 8 07 you can fix this issue with patch ID 127127 11 or later 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 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 PCIe 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
46. 1 02 06 2009 04 00 59 Power Supply PSO FAIL State Deasserted Workaround None 44 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 According to the IPMI PET Warning and SNMP Trap Warning Settings in the Warning Rule Settings Warning Message Creation may not be Possible Depending on the Event Type CR 6746677 According to the IPMI PET warning and SNMP trap warning settings in the warning rule settings warning message creation may not be possible depending on the event type irrespective of the warning level Execution example a SYS MB component name Disabled by CLI action or SYS MB component name Disabled by user critical is reported with an IPMI PET warning when a component is disabled by the set SYS component name component_state disabled command or disablecomponent command respectively a Host has been powered on major is not reported with an IPMI PET warning or SNMP trap warning when the power to the host is turned on m SYS MB FT has exceeded low non recoverable threshold critical is not reported when the fan speed of a built in fan falls below the threshold value m ERROR POST errors detected major is not reported with an IPMI PET warning or SNMP trap warning when an error is detected in a POST self diagnostics test Chapter 3 Known Issues 45 In the Logical Domains Environment After the Host Reset Operation Host May Be Reset Again CR 6836426 In
47. 17 18 00 57 EDT 2007 PLATFORM SUNW SPARC Enterprise T5220 CSN HOSTNAME wgs48 100 SOURCE cpumem diagnosis REV 1 6 EVENT ID a8b0eb18 6449 c0a7 ccOf e230a1d27243 DESC The number of level 2 cache uncorrectable data errors has exceeded acceptable levels Refer to http sun com msg SUN4V 8000 UQ for more information AUTO RESPONSE No automated response IMPACT System performance is likely to be affected REC 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 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 Boot Drive May Report drive type unknown for Solaris format Command CR 6886514 This issue is resolved with Solaris patch ID 124630 32 or later During a period extending from
48. 20 servers varies depending on the maximum number of HDDs installed in the servers T5120 server a Up to 3 SSDs can be installed in the servers which have a maximum of 4 HDDs a Up to 4 SSDs can be installed in the servers which have a maximum of 8 HDDs T5220 server a Up to 7 SSDs can be installed in the servers which have a maximum of 8 HDDs m Up to 8 SSDs can be installed in the servers which have a maximum of 16 HDDs For additional information on the SSDs refer to the 32 GByte 2 5 inch SATA Enterprise Solid State Drive Guide For instructions on installation and removal of SSDs see the Hot Plugging a Hard Drive described in the SPARC Enterprise T5120 and T5220 Servers Service Manual The procedures apply to both the disk based hard drives and SSDs Using a SSD as a Boot Device You cannot use a SSD as a boot device About the Cache Setting of SSDs The SSDs have a setting of internal cache enabled in the initial status When used in the cache enabled condition data may be lost at the time of power failure You can disable the internal cache by using a sub command cache of format e command after booting the Solaris This setting is not saved when you reboot the Solaris To ensure data integrity it is recommended to use an uninterruptible power supply SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 About the Estimated Usable Period of SSDs The SSDs are designed with the estimate of usable peri
49. 2010 Temporary PCIe Link Failure During Boot Causes a Fatal Error Later CR 6553515 25 Ierrs Are Generated When 100Mb Full With Forced Speed Duplex Is Set in e1000g conf CR 6555486 26 Firmware ILOM POST and SP Issues 27 Problem When the PCIe Link Fails to Train as x8 CR 6556505 38 v To Identify the Problem 38 v To Correct the Problem 38 Communication Channel Between the Primary Domain and the Service Processor SP Might Hang CR 6583567 39 v To Recover From a Domain Crash 40 Resetting the SP Produces Extraneous Warning Messages CR 6585292 40 Error Messages from the Ultra320 SCSI Card 41 Erroneous Power Supply Faults CR 6614432 41 A Built In Fan May be Erroneously Detected as a Failure CR 6636098 42 After a Host Power On Instruction is Executed from ILOM the POST May Not Start and Processing May Not Go to OS Boot Processing or the ok Prompt CR 6752910 43 For DC Input Power Models PS0 AC_POK Is Displayed CR 6815369 44 According to the IPMI PET Warning and SNMP Trap Warning Settings in the Warning Rule Settings Warning Message Creation may not be Possible Depending on the Event Type CR 6746677 45 In the Logical Domains Environment After the Host Reset Operation Host May Be Reset Again CR 6836426 46 The ILOM Network Configuration Cannot Be Set CR 6835854 6779753 47 An Error is Registered with the showfaults Command When Running POST But POST Ends Normally CR 11210193 48 The ok Prompt is No
50. 3 20 c lt ILOM3 0 3 Collect the ILOM data Tx000 a In ILOM 3 0 or later In the Integrated Lights Out Manager ILOM 3 0 Concepts Guide refer to the Collect SP Data to Diagnose System Problems section to collect the SP data information m In ILOM 2 x or earlier Collect the ILOM and ALOM data and supply it to service engineers along with the Sun Explorer output a Collect the following data on ILOM Chapter 3 Known Issues 55 show SP users show SP users admin show HOST b Create an ALOM compatible user and collect the following data on ALOM consolehistory v showcomponent showdate showenvironment showfaults v showfru showhost showkeyswitch showlogs v g 0 p p shownetwork showplatform v showsc showsc version v showusers c Reset ILOM gt reset SP Are you sure you want to reset SP y n y Performing hard reset on SP Notes on Installing Solaris 10 8 07 OS and Solaris 10 5 08 OS USB SATA DVD drive is not supported for the Solaris 10 8 07 OS and Solaris 10 5 08 OS To install Solaris 10 8 07 OS or Solaris 10 5 08 OS on a server equipped with a USB SATA DVD drive install the OS from the install server and apply the mandatory patches the latest periodic PTF and the latest recommended security patches 56 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 The procedure is shown below 1 Create an install image on the install server
51. 305 Using the SP setdate command ALOM Note Fixed in System Firmware 7 2 2 e or later compatibility shell after having configured non default logical domains can cause the date on non default domains to change Use the setdate command to configure the date on the SP before configuring and saving logical domain configurations If you use setdate after non default logical domain configurations have been saved each non default domain must be booted to Solaris and the date corrected See date 1 or ntpdate 1M 6733632 When the ILOM show level all sys Note Fixed in System Firmware 7 2 2 e or later command is executed information under Use the show SYS MB SP command SYS MB SP is not displayed When show level all SYS MB is executed information under SYS MB SP is not displayed either 6757022 Resetting the service processor while the host is Note Fixed in System Firmware 7 2 2 e or later powered on can cause the host to crash Do not reset the service processor while the system is powered on If you encounter this issue power cycle the server 6654395 If the LDoms Manager is active on a host Note Fixed in System Firmware 7 1 0 g or later machine do not reset the service processor while the host machine is powered on If the service processor is reset while the system power is active the machine must be power cycled before the LDoms Manager can start properly 6613209 When moving the SCC chip from one syste
52. 7 4 W 814 4W 754 1 W 760 7W Table 8 SPARC Enterprise T5220 Server 16 Disk Capable Power Specifications Maximum Server Configuration Specifications 8 core 1 6 GHz processor with sixteen 4 GB FBDIMMs 16 HDDs 6 PCle I O cards Incorrect Value Correct Value Incorrect Value Correct Value AC Input AC Input DC Input DC Input Peak input power running SpecJBB 901 5 W 908 5W 842 0 W 848 6W 62 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Incorrect Idle Input Power Values Four tables in the SPARC Enterprise T5120 and T5220 Site Planning Guide contain incorrect values for the idle input power The following four tables show the correct information for those tables Table 5 SPARC Enterprise T5120 Server 4 Disk Capable Power Specifications Minimum Server Configuration Specifications 4 core 1 2 GHz processor with four 1 GB FBDIMMs no HDDs no PCle I O cards Incorrect Value Correct Value Incorrect Value Correct Value AC Input AC Input DC Input DC Input Idle input power 187 0 W 179 0 W 174 7 W 167 2 W Table 6 SPARC Enterprise T5120 Server 8 Disk Capable Power Specifications Minimum Server Configuration Specifications 4 core 1 2 GHz processor with four 1 GB FBDIMMs no HDDs no PCle I O cards Incorrect Value Correct Value Incorrect Value Correct Value AC Input AC Input DC Input DC Input Idle input power 187 0 W 179 0 W 174 7 W 167 2 W Table 7 SPARC En
53. 7c TnPC 0243280 STSTATE 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 SASIT 14 CCR 44 XCC nZvc ICC nZve Normal GL 1 QO 0 0 ce O200000 0 23 f0200000 0 3 F 78000 0 4 fec320fc 3ffe60000 Bs 02833e4 3 e60000 6 fFee826c8 3ffe60600 Ta fee817d8 f02432bc o PC 0238978 nPC f023897c TBA 0200000 CCR 8200016 XCC nzvC ICC nZVc 0 ok oe Workaround If the system fails to boot because of this problem retry booting Ierrs Are Generated When 100Mb Full With Forced Speed Duplex Is Set in e1000g conf CR 6555486 As a result of research it turned out that this problem had never happened on the condition which we informed before It is the case that this problem happens when e1000g sets Auto negotiation off and its link partner sets Auto negotiation on which is specified in IEEE802 3 Therefore the same problem can be seen on the other drivers than e1000g when it does the same setting The following setting is also available on e1000g driver m Auto negotiation off m speed 100Mbps a Duplex Full But we suggest Auto negotiation be set to on because this problem frequently occurs when users who set Auto negotiation off to e1000g forget to set Auto negotiation off to link partner 26 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 3 3 Firmware ILOM POST and SP Issues TABLE 3 3 lists the late breaking issues
54. 816507 After mounted the 10GbE XAUI card when you Note Fixed in System Firmware 7 2 7 b or later insert the power cable the component None information of the 10GbE XAUI card does not To confirm the component information of the ei on ILOM ILOM recognized the 10GbE 10GbE XAUI card from ILOM check it after you pica power on the host 6722602 When connected to OS console via ILOM input Note Fixed in System Firmware 7 2 8 or later 6663105 Or display to console may not be enabled And at After the system stop disconnect the power cord 6913105 this time output from OS to console may fail and then reconnect the power cord Appendix A Fixed Issues 97 98 SP Serial Line Terminal Server break Command Does Not Work CR 6577528 This issue is resolved by updating the system firmware to 7 1 6 d or later If you use Telnet to connect to the SP serial line with a terminal server such as the Cisco ASM series and try to send a break to the Solaris host the break command does not work and is ignored by the SP Use the break command from the SP CLI to send a break to the Solaris host The following is sample output of sending a break to the Solaris host from the ALOM CMT compatibility CLI 1 Log into the host with the console command sc gt console 2 Enter to return to the host prompt sc gt Solaris host prompt gt 3 Enter to escape to the SP ALOM CMT compatibility CLI The escape se
55. 8volts ok Workaround None Ignore this issue because it is only a display error SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 During the Power On Self Test the Diagnostic Process May Terminate Halfway CR 6835860 This issue is resolved by updating the system firmware to 7 2 7 b or later For SPARC Enterprise T5220 Server during the power on self test POST the ERROR POST timed out message may appear and the diagnostic process may terminate halfway Example Sc gt poweron cC Enter to return to ALOM Chassis major Host has been powered on 0 0 0 gt 0 0 0 gt SPARC Enterprise TM T5120 T5220 POST 4 30 2 build_06 PROTOTYPE BUILD 2009 03 19 08 25 export delivery delivery 4 30 4 30 2 build_06 post4 30 x Niagara huron integrated root 0 0 0 gt Copyright 2009 Sun Microsystems Inc All rights reserved 0 gt POST enabling CMP 0 threads ffffffff ffffffff 0 gt VBSC mode is 00000000 00000001 0 gt VBSC level is 00000000 00000001 0 gt VBSC selecting Normal mode MAX Testing 0 gt VBSC setting verbosity level 2 0 gt Basic Memory Tests Done 0 gt Test Memory Done 0 gt Setup POST Mailbox Done 0 gt Master CPU Tests Basic Done O gt Init MMU 0 gt NCU Setup and PIU link train Done 0 gt L2 Tests Done 0 0 gt Extended CPU Tests Chassis major Apr 21 10 51 09 ERROR POST timed out Not all system components tested Chassis major
56. A DVD mark appears on the front side of the DVD drive e Confirm that specific part numbers are displayed in the output for the following ILOM ALOM commands Confirm by using ILOM command Confirm whether either of the following part numbers is displayed in the output from 1s SYS PADCRD command fru_part_number 5413512 or fru_part_number 5413513 Confirm by using ALOM command Confirm whether either of the following part numbers is displayed in the output from showfru SYS PADCRD command Partner_Part_NumberR Partner_Part_Nu mber CF005413512REVxx or Partner Part NumberR Partner Part Nu mber CF005413513REVxx 54 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Sun Explorer May Fail to Collect the ILOM Data Tx000 CR 6718841 Sun Explorer may fail to collect the ILOM data Tx000 If failed it may take more than 30 minutes to return an error Workaround You can collect the ILOM data Tx000 in another way 1 Specify the option as follows opt SUNWexplo bin explorer w Tx000 2 Confirm the version of ILOM Depending on the version of ILOM the data collection method varies How to check the version ILOM mode gt version SP firmware 3 0 3 20 c lt ILOM3 0 SP firmware build number 45383 SP firmware date Tue Jun 2 15 38 58 PDT 2009 SP filesystem version 0 1 22 ALOM mode sc gt showsc version SP firmware version 3 0
57. D 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 SS com Ca Adobe PostScript Contents Preface xi New Information About the SPARC Enterprise T5120 and T5220 Servers 1 Important New Information About the T5120 and T5220 Servers 1 Support for SSD Storage 2 Using a SSD as a Boot Device 2 About the Cache Setting of SSDs 2 About the Estimated Usable Period of SSDs 3 About the SSD Use on the 16 Disk Backplane Model 3 Updating LSI 1068e Controller Firmware to Support SSDs 4 Support for RAID Function 4
58. Example This example assumes the DVD medium has been mounted to cdmnt HHH H HH HHH OH mkdir p export home dvd cd cdmnt Solaris 10 Tools setup_install_ server export home dvd share grep export home dvd share F nfs o ro anon 0 d install server directory export home dvd svcs l svc network nfs server default svcadm enable svc network nfs server shareall cd eject cdrom 2 Install the OS from the install server 3 Apply the latest periodic PTF and the latest recommended security patches The mandatory patches which are described in the Mandatory Patch Information on page 16 are collected into the periodic PTF R08111 or later From the viewpoint of preventive maintenance apply the latest periodic PTF and the latest recommended security patches To apply the minimum mandatory patches only apply the patches in the following order a Incase of Solaris 10 8 07 OS LANG C export LANG patchadd 119254 51 patchadd 125891 01 patchadd 127755 01 patchadd 127127 11 HH H a Incase of Solaris 10 5 08 OS There are no mandatory patches 4 Restart the OS shutdown i6 g0 y Chapter 3 Known Issues 57 LDoms Related Issues TABLE 3 5 lists the late breaking LDoms related issues Additional information for some of the issues is provided following the table TABLE 3 5 LDoms Related Issues CR Description Workaround 6540368 In Logical Domai
59. Host is running O OR On On On On On On On On On eee OOOO OOO O00 0 0 Workaround None Power on the host again and perform the power on self test POST Appendix A Fixed Issues 111 On the DC Input Power Model the Environmental Status and Some Part of the FRU Status Information Is Not Displayed CR 6853843 This issue is resolved by updating the system firmware to 7 2 7 b or later On the DC input power model of SPARC Enterprise T5120 Server when you execute the prtdiag command of Solaris OS the Environmental Status and some part of the FRU Status information is not displayed Incomplete Data Output Example lt Part of Environmental Status 9 output A t e FRU Status 5 5SS5SS555 5 Name Status MB enabled HDDO enabled HDD1 enabled data is not on display Workaround None From ILOM check the component information and the status of fan temperature power sensor and so on 112 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 When the Service Processor Is Initialized ILOM May Fails to Start With an Error Message Displayed CR 6856163 This issue is resolved by updating the system firmware to 7 2 7 b or later If the service processor is initialized 1 with the LAN cable disconnected from the ILOM network port the ILOM firmware serial console window displays an error message 2 indicating
60. Information About Known Issues This section describes issues that were discovered since the previous edition of these product notes was published Chapter 1 New Information About the SPARC Enterprise T5120 and T5220 Servers 5 Hardware and Mechanical Issues False Intermittent SATA Errors Seen on Sun SPARC Enterprise T5120 and T5220 Servers CR 6880299 While booting some systems with SATA DVD devices intermittently log extraneous port failure errors in var adm messages The following shows an example of typical error messages pci 400 pci 0 pci 1 pci d0 usbe 0 1 pci 400 pci 0 pci 1 pci 0 usbe 0 2 oheil ehci0 Connecting device on port 1 failed Connecting device on port 2 failed Workaround You can ignore these messages TABLE 1 1 Hardware and Mechanical Issues CR Description Workaround n a When a disk failure occurred in a RAID 0 Do not use RAID 0 configuration the failed disk cannot be identified n a After the build and the deletion of RAID 1 disk It becomes recognized correctly after the server device may not be recognized correctly reboot 6823163 In servers with 8 and 16 disk backplanes the 1 Loosen all the screws on the backplane 32GB SATA SSD drive may not install in some 2 Install SSDs in the corner drive bays drive bay slots 3 Tighten all backplane screws 4 Install remaining SSDs if any 6901327 In Solaris 10 10 09 after the RAID 1 build label Start from the Solaris 1
61. LDoms environment unrecoverable errors in a uncontrolled 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 0x1ldfeda2137e PLATFORM SUNW SPARC Enterprise T5220 CSN HOSTNAME wgs48 100 SOURCE SunOS REV 5 10 Generic _Patch DESC Errors have been detected that require a reboot to ensure system integrity See http www sun com msg SUNOS 8000 0G for more information AUTO RESPONSE Solaris will attempt to save and diagnose the error telemetry IMPACT 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 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 124 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 After the control domain recovers a diagnosis is performed Messages to the console indicate the cause of the unrecoverable error For example SUNW MSG ID SUN4V 8000 UQ TYPE Fault VER 1 SEVERITY Critical EVENT TIME Fri Aug
62. M CMT compatibility CLI 4 Restart fmd on the primary domain Enter 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 lkm1 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 40 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 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 mount
63. P might hang and disable communication over the channel Workarounds m If the 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 Chapter 3 Known Issues 39 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 ALO
64. Support for Windows 7 and Internet Explorer 8 5 New Information About Known Issues 5 Hardware and Mechanical Issues 6 False Intermittent SATA Errors Seen on Sun SPARC Enterprise T5120 and T5220 Servers CR 6880299 6 Firmware ILOM POST and SP Issues 7 Important Information About the SPARC Enterprise T5120 and T5220 Servers 9 Notes on DVD Drive and Discs 9 Supported Versions of the OS and Firmware 10 Solaris OS and Firmware Requirements for Certain Features 11 System Firmware 11 Preinstalled Software 12 Solaris 10 OS and Solaris Live Upgrade 13 Additional Software Available for Your Server Cool Tools 13 Logical Domains 14 Supported Sun Explorer Utility Version 14 Sun Studio C C amp Fortran Compilers and Tools 15 Mandatory Patch Information 16 Mandatory Patches for the Solaris 108 07 OS 16 Mandatory Patches for the Solaris 105 08 OS 16 Mandatory Patches for the Solaris 10 10 08 OS 17 Mandatory Patches for the Solaris 105 09 OS 17 v To Download Patches 17 Patches for Option Cards 17 Installing the Fujitsu 4Gbps Fibre Channel card 18 General Functionality Issues and Limitations 18 Cryptographic Function 18 Cable Management Arm 18 Express Rail Rackmounting Kit 19 SAS RAID Internal HBA Card 19 Processor Identification 19 Notes on the Use of 200V Power Supply 20 3 Known Issues 21 Hardware and Mechanical Issues 22 Ethernet Interface Related Issues 25 iv SPARC Enterprise T5120 and T5220 Servers Product Notes April
65. VD ROM Drive subclass is not 2 3 or 4 Could Cause a Panic CR 6588452 on page 122 You can also upgrade the OS or install the patch to avoid encountering this issue 6588550 The Solaris prtdiag v command is slow to Note Fixed in Solaris patch ID 139502 01 or respond on the SPARC Enterprise T5120 servers later The command might take as long as 5 minutes to Be aware of the delay and wait for the output display output and therefore appears to hang Do not perform a Control C 118 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 4 Fixed Solaris OS Issues Continued CR Description Workaround 6589612 The raidct1 1 command continuously Note Fixed in the Solaris 10 5 08 OS and outputs the following output later and in the Solaris 10 8 07 OS with patch raidetl 1 ID 127127 11 or later installed Controller 1 Use the Control C keyboard sequence to stop the Volume c1t0do output volume ett2do You can also upgrade the OS or install the patch DERK ae to avoid encountering this issue Disk 0 0 0 6592238 You might not be able to remove a RAID 1 Note Fixed in the Solaris 10 5 08 OS and volume after RAID 1 and RAID 0 volumes are later and in the Solaris 10 8 07 OS with patch created ID 127127 11 or later installed When two volumes are created through the Update the OS to the latest version or install the onboard SAS controller or any controller that mandatory patches to avoid encountering th
66. a ILOM Data a Hardware Data a Basic OS Data a Diagnostic Data On the SPARC Enterprise T series servers when you specified the full option the host in execution will not be reset While the host is executing you can specify the full option 70 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Integrated Lights Out Manager ILOM 3 0 Supplement for SPARC Enterprise T5120 and T5220 Servers Notes on ILOM Information Stored on the SCC When transferring the SCC to the replacement server keep the following note in mind Note If the ILOM versions are different between the failed server and the replacement server the settings on the SCC NVRAM will be ignored or overwritten If the ILOM versions are the same the settings will be retained Chapter 4 Documentation Errata 71 72 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 APPENDIX A Fixed Issues This appendix describes the fixed issues concerning the SPARC Enterprise T5120 and T5220 servers You can avoid the issues by using the latest version of Solaris OS System Firmware or other software For details on the fix see the workaround in each table a Hardware and Mechanical Issues on page 73 m Ethernet Interface Related Issues on page 75 a Firmware ILOM POST and SP Issues on page 82 m Solaris OS Issues on page 116 a LDoms Related Issues on page 134 Hardware and Mechanical Issu
67. a defective sector label write label to the disk analyze surface analysis defect defect list management backup search for backup labels verify read and display labels save save new disk partition definitions inquiry show vendor product and revision volname set 8 character volume name The jumpstart install process lt cmd gt execute lt cmd gt then return quit format gt disk The jumpstart install process AVAILABLE DISK SELECTIONS 0 cOtOdO lt drive type unknown gt lt problem indication pci 0 pci 0 pci 2 scsi 0 sd 0 0 Specify disk enter its number 0 C lt quit with lt ctrlsc format gt quit root host 1 2 Shut the server down then bring it up in single user mode with root filesystem mounted read only root host 1 init 0 Oct 20 16 26 56 host 1 syslogd going down on signal 15 svc startd The system is down syncing file systems done Program terminated SPARC Enterprise T5220 No Keyboard Copyright 2009 Sun Microsystems Inc All rights reserved OpenBoot 4 30 4 3968 MB memory available Serial xxxxxxxx Ethernet address XxXX XX XX XX XX XX Host ID xxxxxxxx 0 ok boot m milestone none Boot device pci 0 pci 0 pci 2 scsi 0 disk 0 0 a File and args m milestone none SunOS Release 5 10 Version Generic _141414 10 64 bit Copyright 1983 2009 Sun Microsystems Inc All rights reserved Use is subject to license terms Booting to milestone none
68. a failure to start an ILOM internal process As a result ILOM fails to start 1 Service processor initialization has the following meaning a For ILOM gt set SP reset_to defaults all or factory gt reset SP a For ALOM CMT compatible shell sc gt setdefaults sc gt resetsc Example of failure SUNSP BELO7482AU login root Password Waiting for daemons to initialize Timed out waiting for daemons to start lt 2 sccd daemon has shutdown lt 2 Integrated Lights Out Manager Version 3 0 3 20 e Copyright 2009 Sun Microsystems Inc All rights reserved Use is subject to license terms Warning password is set to factory default Workaround Initialize the service processor with the LAN cable connected to the ILOM network port Appendix A Fixed Issues 113 As long as the network port is linked up the service processor can be initialized even without ILOM network settings If this problem occurs restore normal system operation by using the following procedure 1 Disconnect the power cable 2 Connect the LAN cable to the ILOM network port Verify that the ILOM network port is linked up 3 Connect the power cable 114 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 After the SCC Module Replacement a Connection to the ILOM Network May Fail CR 6857271 This issue is resolved by updating the system firmware to 7 2 7 b or later During SCC module replaceme
69. ad failed The file just loaded does not appear to be executable 0 ok 6623454 Despite the change of SSH setting from Disable Note Fixed in System Firmware 7 2 2 e or later to Enable by using the SSH Server tab of BUI The SSH setting has been changed to Enable it is displayed as Disable Use the Refresh function of BUI 6624658 Unless the system is stopped from the service Note Fixed in System Firmware 7 1 3 d or later processor the system will be automatically To stop the system use the command on the powered on at the next AC power on even if the service processor HOST LAST POWER STATE in SP policy is Moreover when setting the set to enabled HOST_AUTO_POWER_ON property to enabled The same applies if the HOST_AUTO_POWER_ON also set the HOST_POWER_ON_DELAY property to property is set to enabled but the system has enabled not been stopped from the service processor 6624699 Despite the change of Role to Note Fixed in System Firmware 7 2 2 e or later Administrator Operator by using Active Directory of BUI Role is displayed as blank Log in to ILOM and check the defaultrole property of SP clients activedirectory Appendix A Fixed Issues 87 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6643177 If an attempt is made to power on the system Note Fixed in System Firmware 7 1 0 g or later with poweron ALOM CMT compatibility None commands power on
70. cO FUJITSU SPARC Enterprise T5120 and T5220 Servers Product Notes Copyright 2010 Sun Microsystems Inc 4150 Network Circle Santa Clara California 95054 U S A and FUJITSU LIMITED 1 1 Kamikodanaka 4 chome Nakahara ku Kawasaki shi Kanagawa ken 211 8588 Japan All rights reserved 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 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 whi
71. card to determine if additional patches are needed Chapter 2 Important Information About the SPARC Enterprise T5120 and T5220 Servers 17 Installing the Fujitsu 4Gbps Fibre Channel card Once you install the Fujitsu 4Gbps Fibre Channel card SEOX7F11X SEOX7F12X the patch indicated below is required Access the above mentioned web site to download the patch Follow the installation instructions provided in the README file for the patch Optional cards m Single channel 4Gbps Fibre Channel card SEOX7F11X a Dual channel 4Gbps Fibre Channel card SEOX7F12X Required patch m FUJITSU PCI Fibre Channel 4 0 914583 04 or later General Functionality Issues and Limitations This section describes general issues known to exist at this release of the SPARC Enterprise T5120 and T5220 servers Cryptographic Function The IPsec capability of the on chip cryptographic accelerator in the UltraSPARC T2 multicore processor is a mechanism that cannot be used unless the IPsec activation package has been installed As the IPsec activation package is presently not supported by Fujitsu the IPsec function cannot be used in Fujitsu brand servers Cable Management Arm The SPARC Enterprise T5120 server does not support the cable management arm CMA The following restrictions apply when using a CMA on SPARC Enterprise T5220 servers a The maximum capacity of the CMA is as follows a AC input power model 2 AC cables and 6 RJ45 cables a DC in
72. cement is enabled Confirmation example cfgadm 1 cl dsk clt1do Ap_Id Type Receptacle Occupant Condition cl dsk cltidoO disk connected unconfigured unknown 6772707 When the showenvironment command of the Note Fixed in System Firmware 7 2 2 e or later ALOM CMT compatibility shell is executed in a sixteen disk capable server even though the hard disk is mounted in slot 8 NOT PRESENT is output For examples see When the showenvironment Command is Executed in a Sixteen Disk Capable Server Even Though the Hard Disk is Mounted in Slot 8 NOT PRESENT is Output CR 6772707 on page 107 The status can be confirmed from the ok prompt by using the probe scsi all command For examples see When the showenvironment Command is Executed in a Sixteen Disk Capable Server Even Though the Hard Disk is Mounted in Slot 8 NOT PRESENT is Output CR 6772707 on page 107 Appendix A Fixed Issues 89 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6692478 Failures may occur in ILOM functions suchas Note Fixed in System Firmware 7 2 2 e or later 6781815 6782508 user account management if a prohibited character like or is used for the first character of an ILOM user account After the ILOM reset or the power cable removal and insertion when the server powered on Solaris OS startup at the ok prompt of OBP OpenBoot PROM using the boot
73. ch 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 Ray Answerbook2 docs sun com OpenBoot and Sun Fire 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 trademarks 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 Micr
74. command may fail Error output example 0 ok boot ERROR All device paths in boot device have failed 0 ok It cannot refer to the device paths that configured in the OBP environmental variable boot device and fails to start Solaris OS The SP powermgmt policy property has been disabled None When the user account can be deleted the ILOM can be recovered by deleting the user account When the user can not be deleted reset the ILOM configuration to factory defaults to recover the ILOM For the details about procedures and valid characters for ILOM user accounts see the Integrated Lights Out Manager 2 0 User s Guide Note Fixed in System Firmware 7 2 2 e or later After the ILOM reset or the power cable removal and insertion when you power on the server check the OBP environmental variable Especially in case the OBP environmental variable use nvramrc has been set to true it is necessary in advance of starting the OS to see the ok prompt and check that use nvramrc has been set to true and then execute the boot command Confirmation example 0 ok printenv use nvramrc use nvramrc true 0 ok Note Fixed in System Firmware 7 2 2 e or later To SP powermgmt policy the following properties have become available Performance The system is allowed to use all the power that is available Elastic The system power usage is adapted to the current utilization level For exam
75. 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 names the device cdrom 1 Both the OpenBoot firmware and Solaris OS follow the 1275 USB bindings rules to name nodes For example TABLE 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 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 1275 USB Bindings Rules for Naming Nodes Continued binterface Class binterface Subclass binterface Protocol Name 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 This issue is resolved for servers running the Solaris 10 5 08 OS and later If you are running Solaris 10 8 07 you can fix this issue with patch ID 127127 11 or later 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
76. d Ethernet Related Issues CR Description Workaround 6551509 6554478 6561389 If you run modunload while the nxge port is running a system panic might occur Receiving Jumbo Frames might drop the Ethernet interface to 30 Mbps due to packet dropping Setting properties for the network interface unit NIU nxge devices could fail For an example of the failure see Setting Properties for nxge Devices Might Fail CR 6561389 on page 80 Note Fixed in the Solaris 10 5 08 OS and later and in the Solaris 10 8 07 OS with patch ID 127127 11 or later installed Unplumb the interfaces prior to unloading the driver See Using modunload While the nxge Port Is Running Could Cause a System Panic CR 6551509 on page 76 You can also upgrade the OS or install the patch to avoid encountering this issue Note Fixed in the Solaris 10 5 08 OS and later and in the Solaris 10 8 07 OS with patch ID 127127 11 or later installed Set the MTU size to 8172 as described in Jumbo Frames Throughput of nxge Drops to 30 Mbps Due to Packet Dropping CR 6554478 on page 78 You can also upgrade the OS or install the patch to avoid encountering this issue Note Fixed in the Solaris 10 5 08 OS and later and in the Solaris 10 8 07 OS with patch ID 127127 11 or later installed Use the global declaration without the device path in the nxge conf file For example add the following line to the nxge conf
77. d 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 e Host ID e Mac addresses All other variable values will become default values 6636098 If a built in fan is erroneously detected as a Note Enhanced Support Facility patch 914604 failure and reported as such to the Enhanced 04 Support Facility software or Server System Since these messages do not have an effect on Manager software an error message is your system behavior ignore these messages displayed For an example of the errors see A Built In Fan May be Erroneously Detected as a Failure CR 6636098 on page 42 6723410 If you repeat in sequence a login to the service If this problem occurs terminate the login processor executing a command and logging out logout may fail session on the client from which you have accessed the service processor 30 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6760139 ILOM firmware and OpenBoot PROM OBP If an ILOM firmware initialization has been setting information may not be inherited during performed or any of the firmware settings have motherboard replacement been changed follow the procedure below to save the latest ILOM firmware setting
78. dentify because no PCIe I O devices will be available 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 YV To Correct the Problem 1 Take down all domains and power off the system 38 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 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 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 S
79. ding to the IPMI PET warning and SNMP trap warning settings in the warning rule settings warning message creation may not be possible depending on the event type irrespective of the warning level All generated events can be confirmed with show SP logs event list or showlogs The flashupdate ALOM CMT command with the v option doesn t display the details of the execution result The v option exists to maintain compatibility with the earlier ALOM The v option specified doesn t affect the system firmware download and update The result shows no details and will be the same as the execution result without the option In the back up and restore functions of LOM settings you cannot set https to the protocol for data transfer transfer_method property Example gt set dump_uri https ipaddres directory filename set Unable to transfer image please check URI In ILOM3 0 you cannot set service to the HOST diag mode property or the diag_mode property of the ALOM CMT compatible shell If you set it is displayed as unknown None None See According to the IPMI PET Warning and SNMP Trap Warning Settings in the Warning Rule Settings Warning Message Creation may not be Possible Depending on the Event Type CR 6746677 on page 45 None None Use other protocols tftp ftp sftp scp http None The following settings offer the POST diagnosis in a mode equivalent to the service HOST d
80. 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 location 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 Appendix A Fixed Issues 123 PSH Events Are no Longer Transported CR 6594506 This issue is resolved for servers running the Solaris 10 5 08 OS and later If you are running Solaris 10 8 07 you can fix this issue with patch ID 127127 11 or later 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 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
81. dress to 192 9 200 33 gt set SP network pendingipnetmask 255 255 255 0 Set pendingipnetmask to 255 255 255 0 gt set SP network commitpending true set Unable to get network management property gt gt show SP network d properties SP network Properties commitpending Cannot show property dhcp server_ip none ipaddress none ipdiscovery none ipgateway none ipnetmask none macaddress none pendingipaddress 192 9 200 33 pendingipdiscovery static pendingipgateway none pendingipnetmask 255 255 255 0 state disabled Workaround None Connect the LAN cable to the NET MGT port of ILOM and then set the network configuration Chapter 3 Known Issues 47 48 An Error is Registered with the showfaults Command When Running POST But POST Ends Normally CR 11210193 If an error occurs during POST execution Fault Sensor VCORE _POK at SYS MB deasserted may be registered when the showfaults ALOM CMT compatibility command is used for status confirmation However POST will still end normally in this case sc gt showfaults v Last POST Run Sun Apr 20 17 53 36 2008 Post Status Passed all devices ID Time FRU Class Fault 1 Apr 19 06 41 14 SYS MB SP detected fault Fault Sensor VCORE POK at SYS MB deasserted sc gt Workaround None If this problem occurs use the resetsc ALOM CMT compatibility command to clear the log and rese
82. e and insert the power cord 178418 daemon notice Audit minor ILOM reset operation example admin Open Session Log in to ILOM and execute the following object session type value command shell success In case of ILOM command mode Nov 7 14 13 04 xxxxxx SC Alert ID gt reset SP 434268 daemon miotice Audit minor Are you sure you want to reset SP admin Close Session y n y object session type yalus In case of ALOM CMT compatible shell shell success sc gt resetsc Are you sure you want to reset the sc y n y n a After you remove insert the power cord and Take 180 or more seconds for each of the while POST is running the SYS XXXXX prom is unreadable or corrupted message may appear and stop at ok prompt For details see After the Power Cord Removal Insert an Error Message May Appear during the POST on page 49 intervals between the system power off and the power cord removal and between the removal and insertion of the power cord Chapter 3 Known Issues 37 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 V To Identify the Problem Though no error or fault is reported it is easy to i
83. e 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 c1b0 b06a f26fal8e4ee7 DESC The number of errors associated with this memory module has exceeded 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 5dcb clb0 b06a 26fal8e4ee7 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 74 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 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 TABLE A 2 Ethernet Interface Related Issues TABLE A 2 lists the Ethernet related issues that have been fixed Fixe
84. e future third party systems monitoring tools if they monitor this entry 134 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 5 Fixed LDoms Related Issues Continued CR Description Workaround 6592934 In the unlikely event that POST times out before Note Fixed in System Firmware 7 1 0 g or completing its test cycle the firmware issues the later following message to the console If the error is observed on the console during ERROR POST timed out Not all boot power cycle the system and ensure that system components tested POST runs to completion The system continues to boot but in a degraded You can also boot without running POST state During the boot process the following You can also update the System Firmware to the error messages are displayed latest version to avoid encountering this issue in WARNING Unable to connect to Domain the future 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 6593132 Changes to OpenBoot PROM variables with Note Fixed in System Firmware 7 0 9 or later non default LDoms configuration do not persist Save the SP configuration after changing an If an LDoms variable is set to a non default LDoms variable Example value when an LDoms configuration is
85. ed filesystem with ordered data mode kjournald starting Commit interval 5 seconds EXT3 fs warning maximal mount count reached running e2fsck is recommended ipt_recent 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 Error Messages from the Ultra320 SCSI Card At the time of boot from a device connected with the dual channel Ultra320 SCSI Card SEOX7SC2F SEOX7SC2X the following messages may be displayed Since these messages do not have an effect on your system behavior ignore these messages SCSI command timeout occurred SCSI interrupts not occur Erroneous Power Supply Faults CR 6614432 Some SPARC Enterprise T5120 servers report a low AC line input voltage fault when the input voltage is in the range of 90V to 94V AC This is not the correct threshold and should not indicate an AC input fault until the voltage drops below 90V AC Example of erroneous fault messages sc gt showlogs Oct 09 Oct 09 Supply Oct 09 Supply Oct 09 Supply 14 13 17 Chassis major Host is running 14 36 10 IPMI minor ID 264 10 09 2007 14 36 10 Power PS1 DC_POK State Deasserted 14 36 11 IPMI minor ID 265 10 09 2007 14 36 11 Power PS1 AC_POK State Deasserted 14 36 14 IPMI minor ID 266 10 09 2007 14 36 14 Power PS1 FAIL State Asserted Chapter 3 Known Iss
86. elative to the user s login so the directory would probably be home joe data Service Snapshot utility does not support the SP data collection using TFTP Erroneous Default Value for SP clients dns The default value for SP clients dns indicated on page 29 and page 144 is incorrect The correct value is enabled Chapter 4 Documentation Errata 69 Erroneous Description about Collecting SP Data The following description in the section Collect SP Data to Diagnose System Problems on page 88 includes incorrect information Variable Option Description data full Specifies that all data is to be collected full collection Note Using this option may reset the running host On the SPARC Enterprise T series servers when you specified the full option the host in execution will not be reset While the host is executing you can specify the full option Integrated Lights Out Manager ILOM 3 0 Web Interface Procedures Guide Erroneous Description about Collecting SP Data The following description in the section Collect SP Data to Diagnose System Problems on page 79 includes incorrect information 3 Select the desired Data Set Normal Full or Custom m Normal Specifies that ILOM operating system and hardware information is collected m Full Specifies that all data is to be collected Selecting Full might reset the system m Custom Allows you to choose one or more of the following data sets
87. em using one of the following methods the Solaris OS boots 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 Bee l 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 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 n a The output of the raidct1 h command and The SPARC Enterprise T5120 and T5220 servers the raidct1 man page display some currently only support RAID 0 and RAID 1 for unsupported features the o board SAS disk controller The raidct1 utility can be used to create and delete RAID 0 amp RAID 1 volumes Refer to the SPARC Enterprise T5120 and T5220 Servers Administration Guide for supported RAID information 6617544 The prtdiag command doesn t display the fjgi None information of Fujitsu manufactured card 6617549 In times such as PSU failure OS outputs the None message however the last one character is not displayed 6722640 Messages similar to the following might be This problem ha
88. er During boot or installation over wide area Be aware of the time needed to boot or perform networks the time it takes to download the installations over a wide area network with a miniroot could significantly increase when using virtual network device a virtual network device You can also update the System Firmware to the This performance degradation is relevant only latest version to avoid encountering this issue in when trying to boot or install over wide area the future 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 6567748 Domain status might not be reported accurately Note Fixed in System Firmware 7 1 0 g or For example the status reported fora domain later might be Running when the OS is not running Ignore the domain status information from all This problem is encountered when the domain CLIs and BI output as well as from the domain status is reported by ILOM BI and CLI and status entry in the ILOM control MIB Retrieve from the ALOM CMT compatibility the true status of the domain by accessing the showplat form command domain console The ambiguity also exists in the ILOM control You can also update the System Firmware to the MIB but not in the platform entity MIB Thus latest version to avoid encountering this issue in the ambiguous domain status might be visible to th
89. es TABLE A 1 lists the hardware and mechanical issues that have been fixed TABLE A 1 Fixed Hardware and Mechanical Issues CR Description Workaround 6592272 An uncorrectable L2 writeback error might Note Fixed in the Solaris 10 5 08 OS and generate a memory fault message SUN4V later and in the Solaris 10 8 07 OS with patch 8000 E2 to the console ID 127127 11 or later installed See L2 Cache Errors Might Generate an Erroneous Memory Fault CR 6592272 on page 74 You can also upgrade the OS or install the patch to avoid encountering this issue 73 TABLE A 1 Fixed Hardware and Mechanical Issues Continued CR Description Workaround 6616209 A power supply fan failure might not generate a Note Fixed in System Firmware 7 0 9 or later 6617012 fault To ensure continuous operation during a Note This issue only applies to fan failures in possible power supply fan fault ensure that power supply 0 A fan failure in power supply 1 both power supplies are connected to two will generate a fault separate power circuits L2 Cache Errors Might Generate an Erroneous Memory Fault CR 6592272 This issue is resolved for servers running the Solaris 10 5 08 OS and later If you are running Solaris 10 8 07 you can fix this issue with patch ID 127127 11 or later In earlier versions the issue shows up after an uncorrectable L2 writeback error A bogus memory fault message SUN4V 8000 E2 might be reported to th
90. es see Domain ETM and LDC Deadlock When Transmit Queue Full CR 6594506 on page 101 later See Domain ETM and LDC Deadlock When Transmit Queue Full CR 6594506 on page 101 Appendix A Fixed Issues 85 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6598381 In rare circumstances the PCle interface unit Note Fixed in System Firmware 7 1 6 d or later PIU might issue a spurious error interrupt These events are harmless and can be ignored For examples see Spurious PIU Errors CR You can also update the System Firmware to the 6598381 on page 104 latest version to avoid encountering this issue 6611700 When the OpenBoot PROM is set to input Note Fixed in System Firmware 7 1 6 d or later 6601900 device keyboard you might see the Do not use USB keyboards Instead use a virtual following warning message when the system console by setting the input device variable to host is powered on or reset virt al console No REyROdEG SUPPO r Found You can also update the System Firmware to the A U S keyboard will work properly latest version to avoid encountering this issue International keyboards French German and so on might behave as U S keyboards 6602913 IPMI power off or power cycle operations might Note Fixed in System Firmware 7 1 6 d or later fail Repeat the IPMI power off or power cycle operation or use one of the other available interfaces to
91. firmware serial console cable connected to the ILOM network port window displays an error message indicating a As lon g as the network port is linked up the DEE to aen T ILO Ianto process 32 service processor can be initialized even without result IONI ails to start i ILOM network settings o see When the Service Processor Is For procedures to restore normal system Talizeo War ay ep to Stant With a operation see When the Service Processor Is a Displayed CR Geet p Initialized I LOM May Fails to Start With an Error page H3 Message Displayed CR 6856163 on page 113 6857271 During SCC module replacement part of the Note Fixed in System Firmware 7 2 7 b or later data kept on the motherboard is inadvertently Jf only the SCC module fails replace the SCC overwritten with new SCC module data This module together with the motherboard oe a c nnectioni failure to the ILOM After replacing these components restore the cases backed up contents For details see After the SCC Module Replacement a Connection to the ILOM Network May Fail CR 6857271 on page 115 6854379 After the replacement of motherboard the Note Fixed in System Firmware 7 2 7 b or later values for properties stored in the HOST diag None directory may norbe camied Oven even though Before replacing the motherboard back up the system hatin uae module as ILOM settings After the replacement restore the moved to the new motherboard backed up settings 6
92. 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 AC power cycle the system Ignore the extraneous warning messages 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 28 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6599333 The ASR database does not support disabling XAUI devices When a XAUI device is disabled with ILOM CLI set NACname component_state disabled or with the ALOM CMT compatib
93. he hard drive data cable d Route the hard drive data cable over the fan module and along the air duct e Plug the data cable into J6401 on the motherboard The correct information is as follows 3 SPARC Enterprise T5120 server 8 HDD model Disconnect and stow the hard drive data cable a Unplug the hard drive data cable from J6401 on the motherboard b Remove the hard drive data cable from its seat on the CPU air duct c Place the hard drive cable end out of the way of the air duct Chapter 4 Documentation Errata 65 Erroneous Description in Fan Module Configurations for SPARC Enterprise T5220 Servers 8 and 16 Disk Capable The description in the section Fan Module Configurations for SPARC Enterprise T5220 Servers 8 and 16 Disk Capable is incorrect The fan module configurations are different between 8 disk capable and 16 disk capable servers The correct configurations are as follows TABLE SPARC Enterprise T5220 8 Hard Drive Capable Fan Module Locations and FRU Names Empty Empty Empty SYS FANBDO FMO SYS FANBDO FM1 SYS FANBDO FM2 Front of system TABLE SPARC Enterprise T5220 16 Hard Drive Capable Fan Module Locations and FRU Names Empty SYS FANBD1 FM1 Empty SYS FANBDO FMO SYS FANBDO FM1 SYS FANBDO FM2 Front of system Unnecessary Procedure in Install the Hard Drive Cage The following procedure in Install the Hard Drive Cage is u
94. iag mode normal HOST diag level max HOST verbosity max Chapter 3 Known Issues 33 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6829248 6836426 6835863 6835854 6779753 6853383 6858772 6856315 The alert rule configuration using the SNMP trap fails in the filtering of alert levels When you select the minor or any upper levels alerts of all levels will be notified to the SNMP trap In the Logical Domains environment after the host reset operation host may be reset again For the example see In the Logical Domains Environment After the Host Reset Operation Host May Be Reset Again CR 6836426 on page 46 During the execution of SunVTS there may be the following warning message on the OS console and the system log output Message example WARNING ldc_close failed 11 Oxc unregister In case that the NET MGT port of ILOM has not been connected with the LAN cable and the network gateway is not set the ILOM network configuration cannot be set For the output example see The ILOM Network Configuration Cannot Be Set CR 6835854 6779753 on page 47 On SPARC Enterprise T5220 Server after the Solaris OS panic occurred and while collecting the OS panic core dump the ILOM watchdog timer occasionally detects it as an error and may reset the system In this case the OS panic core dump is not collected snmpd can sometime
95. ility disablecomponent command or due to failures detected by POST the corresponding network device is still available in the OpenBoot firmware 6613212 Though you set user reset or all reset to Add all resets or power on reset to Host diag trigger and execute reset by HOST diag trigger using the reset SYS command POST fails to be executed 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 41 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 6614568 In ILOM mode though you send the break None When the auto boot parameter is set request to OS you cannot obtain the ok prompt to false ok prompt can be displayed by gt set HOST send break _action break selecting s or r Selecting c returns you to the Set send_break_action to break Solaris OS However when the auto boot parameter is set to true none of the options can At this time the following message appears on optat the ok prompt the OS console but none of the options can For the details see the section OpenBoot ok obtain the ok prompt Prompt in the SPARC E
96. inued CR Description Workaround n a When the system is initialized firmware is When viewing the amount of memory in the loaded and occupies approximately 128 MB to banner be aware that the banner reports the 352 MB of the host memory The banner and amount less what is used by the firmware other software utilities report an amount of memory minus the amount of memory that is occupied by firmware n a An RJ45 cable may sometimes be difficult to In this event disconnect the cable while keeping disconnect from an RJ45 port of an Ethernet card the RJ45 cable connector tab depressed such as mounted in the SPARC Enterprise T5120 with a plastic card Bug ID To use the XVR 300 as a console of the SPARC To use the XVR 300 as a console apply patch 6581309 Enterprise T5xx0 patch 137111 01 or later must 137111 01 or later to the Solaris OS before be applied changing the OBP variable If the patch is applied after the OBP variable has Alternatively install the Solaris OS or reinstall been changed to use the XVR 300 as the console it with ILOM set as the console used and then console output will revert to the default LOM apply the patch console during the Solaris boot sequence No GUI can be used during that time After the patch has been applied the XVR 300 can be used as the console as soon as the OBP variable is changed 6706976 At write to CD DVD media there may be cases Use the media as is where the writing speed may not reach the ma
97. is uses the mpt driver the raidct1 utility is issue in the future 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 displayed raidctl 1 Device record is invalid 6594506 After certain hardware error events it is possible Note Fixed in the Solaris 10 5 08 OS and that Solaris PSH events are no longer later and in the Solaris 10 8 07 OS with patch transported between the SP and the domain ID 127127 11 or later installed For examples see PSH Events Are no Longer See PSH Events Are no Longer Transported Transported CR 6594506 on page 124 CR 6594506 on page 124 You can also upgrade the OS or install the patch to avoid encountering this issue 6596503 The output of the Solaris prtpicl v Note Fixed in System Firmware 7 1 6 d or command might show CPU cores or strands with an operational status of enabled when the cores or strands do not exist later Instead use the output from the prtdiag or prtpicl c cpu commands You can also update the System Firmware to the latest version to avoid encountering this issue Appendix A Fixed Issues 119 TABLE A 4 Fixed Solaris OS Issues Continued CR Description Workaround 6581309 The selection message r ebook 0 k Note Fixed in Solaris patch ID 137111 01 or prompt h alt appears on the OS console later but if you select o you might see the The
98. l the patch to avoid encountering this issue Note Fixed in System Firmware 7 1 6 d or later You can also update the System Firmware to the latest version to avoid encountering this issue Note Fixed in the Solaris 10 5 08 OS and later and in the Solaris 10 8 07 OS with patch ID 127127 11 or later installed You can also upgrade the OS or install the patch to avoid encountering this issue 76 Using modunload While the nxge Port Is Running Could Cause a System Panic CR 6551509 This issue is resolved for servers running the Solaris 10 5 08 OS and later If you are running Solaris 10 8 07 you can fix this issue with patch ID 127127 11 or later 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 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 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 in
99. ler or the data path redundancy use the dedicated RAID system 4 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 m When building or deleting a RAID 1 array a When you build or delete a RAID array do not fail to make backup copies of the data When rebuilding a RAID you need to restore data from the backup media a The RAID build or the synchronization associated with maintenance takes about an hour for a 146GB HDD a If there is a system restart during the RAID build or synchronization the build synchronization must be started again from the beginning a When the RAID applied the volume size is smaller than the size of original disk a During the RAID 1 operation a Preventive maintenance while the system is running is not available In some cases RAID controller cannot conclude the disk is completely in failure and system slowdown may occur To do maintenance in this status it becomes necessary to rebuild the RAID 1 and to restore the data from the backup media m Notes on the raidctl command a Do not use the following options of the raidct1 command which are not supported raidctl C r 1E raidctl c r 1E raidctl a raidctl p a The following option of the raidct1 command cannot be used raidctl C z Support for Windows 7 and Internet Explorer 8 As of ILOM 3 0 9 the Remote Console feature in ILOM supports Microsoft Windows 7 and Internet Explorer 8 operating system clients New
100. m 800mm SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 2 If the server is installed at a level between 21U and 40U 1 1 Judged based on the level of the equipment top en eral F Rear side clearance for service access 800mm Equipment rack 1050mm Front side clearance for service access 1300mm 1400mm 800mm 700mm 1400mm Chapter 4 Documentation Errata 61 Incorrect Values for the 1 6 GHz SpecJBB Test Tables 5 7 and 8 of the Site Planning Guide contain incorrect values for the peak input power when running SpecJBB in a system with 1 6 GHz CPUs and a maximum memory HDD and PCle card configuration The following tables provide the correct values Table 5 SPARC Enterprise T5120 Server 4 Disk Capable Power Specifications Maximum Server Configuration Specifications 8 core 1 6 GHz processor with sixteen 4 GB FBDIMMs 4 HDDs 3 PCle I O cards Incorrect Value Correct Value Incorrect Value Correct Value AC Input AC Input DC Input DC Input Peak input power running SpecJBB 615 3 W 624 3W 574 7 W 583 1W Table 7 SPARC Enterprise T5220 Server 8 Disk Capable Power Specifications Maximum Server Configuration Specifications 8 core 1 6 GHz processor with sixteen 4 GB FBDIMMs 8HDDs 6 PCle I O cards Incorrect Value Correct Value Incorrect Value Correct Value AC Input AC Input DC Input DC Input Peak input power running SpecJBB 80
101. m to Note Fixed in System Firmware 7 1 3 d or later another if the value of HOST diag trigger When moving an SCC chip from one system to or diag_trigger has two values such as another verify that the values of power on reset error reset the values HOST diag trigger are correct If the values are restored incorrectly from the SCC chip to the are not correct set them to the desired value new system The values will be restored without a space separating them for example power on reseterror reset This situation will result in POST not being run when the host is reset 6639312 The SYS MB CMPx components have a Note Fixed in System Firmware 7 1 0 g or later fault_state property and a Ignore the fault state and clear_fault_action property These clear_fault_action properties of the components should not have these properties SYS MB CMPx targets Use the fault_state since they are not FRUs and cannot be faulted and cle ar_fault_action property of or have their fault state cleared SYS MB However if a SYS MB CMPx component fails that fault_state property of the SYS MB target will be updated correctly 92 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6694475 Itis impossible to use options of the showfru Note Fixed in System Firmware 7 1 6 d or later command on the ALOM CMT compatibility None shell All infor
102. mation will be displayed regardless of the option specified showfru g lines s d FRU g Only the specified line s Only static information d Only dynamic information 6694693 ILOM allows only two privileges Administrator Note Fixed in System Firmware 7 2 2 e or later and Operator Therefore the following text None about the ALOM CMT userperm command in the manual is inappropriate If one of c u a and r is set Administrator authority will be in effect If nothing is specified Operator authority will be in effect lt Integrated Lights Out Manager 2 0 Supplement gt userperm username c u a r 6738989 The SNMP tab of the ILOM Web interface does Note Fixed in System Firmware 7 2 2 e or later not have an item for setting engineid Use the set SP services snmp engineid value command from the CLI to set engineid 6729474 The powercycle command of the ILOM Note Fixed in System Firmware 7 2 2 e or later browser interface does not secure sufficient time for normal power off of the system and may fail to complete powercycle None Appendix A Fixed Issues 93 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6731227 Two circumstances can cause a logical domain to Note Fixed in System Firmware 7 2 2 e or later hang when reassigning I O branches from the Both situations can be avoided by following these primary domain control domain to a gue
103. may fail with the following message displayed sc gt poweron Host poweron failed poweron error Internal error sc gt poweron Error reading keyswitch value 6676309 When using NTP services under Solaris OS time Note Fixed in System Firmware 7 1 3 d or later 6667409 correction with NTP may fail and a time delay Alternatively if the firmware is not updated add may occur the appropriate one of the commands below to the settings in the etc system file and restart Solaris OS If the NTP correction mode is set to slew mode e and the processor speed is 1 2 GHz set sys tick _freq 1165379275 e and the processor speed is 1 4 GHz set sys tick freq 1415103392 6610861 The prompt and character sequence for Note Fixed in System Firmware 7 1 6 d or later 6613564 dropping to the u boot state is inconsistent with Type the boot command to resume the service previous platforms processor boot sequence When the service processor is booting pressing You can also update the System Firmware to the a key during the 5 second interval while the latest version to avoid encountering this issue prompt Hit any key to stop autoboot is displayed causes the service processor boot sequence to stop and a u boot prompt is displayed 6656116 If the DIMM module fails the MCU will be Note Fixed in System Firmware 7 2 2 e or later disconnected and an error message might be output to the console For an example of the message see MCU Might Be Disconnected
104. ministering and using your servers are provided in the SPARC Enterprise T5120 and T5220 servers documentation sets The entire documentation set is available for download from the following web site Global Site http www fujitsu com sparcenterprise manual xi North American Site https download computers us fujitsu com Japanese Site http primeserver fujitsu com sparcenterprise manual Note Information in these product notes supersedes the information in the SPARC Enterprise T5120 and T5220 documentation sets Fujitsu Welcomes Your Comments If you have any comments or requests regarding this document or if you find any unclear statements in the document please state your points specifically on the form at the following URL For Users in U S A Canada and Mexico http www computers us fujitsu com www support_servers shtml su pport servers For Users in Other Countries SPARC Enterprise contact http www fujitsu com global contact computing sparce_ index htm 1 xii SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 CHAPTER 1 New Information About the SPARC Enterprise T5120 and T5220 Servers This chapter describes new information about the SPARC Enterprise T5120 and T5220 servers that was not documented in the previous edition of the SPARC Enterprise T5120 and T5220 Servers Product Notes The following sections are included in this chapter m Important New I
105. module units For This error is encountered when there is a large example if the following device was disabled difference between the amount of memory on the different CMP and memory modules For SYS MB MEM0 CMPO BRO CHO DI example this could happen if the memory on then disable the following additional devices CMP0 MEM0 added up to 128 Gbytes but the SYS MB MEM1 CMP1 BRO CHO D1 memory on CMP1 MEM1 were only 16 Gbytes sys MB MEM2 CMP2 BRO CHO D1 This situation might happen in two different SYS MB MEM3 CMP3 BRO CHO D1 Da Sach situatior has ita own recovery Case 2 You have added new FB DIMM modules to T5120 T5220 servers and have configured one of the CMP memory module pairs with significantly more memory than the other modules Recovery 2 Reallocate the FB DIMMs across the CMP memory modules to keep the total number and types of FB DIMMs the same on each CMP memory module pair 6731027 Under certain conditions the system might not Note Fixed in System Firmware 7 2 2 e or later power off when the Solaris OS is halted The system might appear unresponsive in this case with no messages in at the system console or on the SC console Power off the system using one of the following methods e The ILOM stop SYS command e The ALOM poweroff command Appendix A Fixed Issues 95 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6652046 POST error messages for some types of XAUI Note
106. n 7 0 9 or later Appendix A Fixed Issues 105 MCU Might Be Disconnected in DIMM Module Failure CR 6656116 This issue is resolved by updating the system firmware to 7 2 2 e or later If the DIMM module fails the MCU will be disconnected and the following message might be output to the console For example Message Jun 04 06 11 22 Chassis major Jun 4 06 11 22 ERROR MCU2 initialization failed DRAM init disabled Jun 04 06 11 23 Fault critical SP detected fault at time Wed un 4 06 11 23 2008 SYS MB CMPO MCU2 Forced fail DRAM init un 04 06 11 24 Chassis major Jun 4 06 11 24 ERROR MB CMPO MCU3 unused because MB CMPO MCU2 is not configured Jun 04 06 11 24 Chassis major Jun 4 06 11 24 ERROR MB CMP0 L2_BANK4 MB CMP0 L2_BANK5 unused because MB CMP0 MCU2 is not configured Jun 04 06 11 24 Chassis major Jun 4 06 11 24 ERROR MB CMP0 L2_BANK6 MB CMP0 L2_ BANK7 unused because MB CMP0 MCU3 is not configured Er Ep E Jun 04 06 11 24 Chassis major Jun 4 06 11 24 ERROR Degraded configuration system operating at reduced capacity Jun 04 06 11 24 Chassis major Jun 4 06 11 24 ERROR System DRAM Available 002048 MB showfaults command Last POST Run Wed Jun 4 06 14 17 2008 Post Status Passed all devices ID FRU Fault 1 SYS MB SP detected fault SYS MB CMP0 MCU2 Forced fail DRAM init Workaround Identify and replace the faulty DIMM module 106 SPARC E
107. name The jumpstart install process execute lt cmd gt then return 132 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 CODE EXAMPLE A 1 Procedure for Recovering a Boot Drive s drive type AVAILABLE DISK SELECTIONS 0 cOtOdO lt SUN72G cyl 14087 alt 2 hd 24 sec 424 gt pci 0 pci 0 pci 2 scsi 0 sd o 0 Specify disk enter its number 0 selecting cOt0odo disk formatted format gt quit The drive type recovery is complete reboot the server root reboot syncing file systems done rebooting Resetting SPARC Enterprise T5220 No Keyboard Copyright 2009 Sun Microsystems Inc All rights reserved OpenBoot 4 30 4 3968 MB memory available Serial xxxxxxxx Ethernet address XxXX XX XX XX XX XX Host ID xxxxxxxx B oot device pci 0 pci 0 pci 2 scsi 0 disk 0 0 a File and args SunOS Release 5 10 Version Generic _141414 10 64 bit Copyright 1983 2009 Sun Microsystems Inc All rights reserved Use is subject to license terms Hostname host 1 The file system dev rdsk cOt0d0s0 is being checked Reading ZFS config done host 1 console login Appendix A Fixed Issues 133 LDoms Related Issues TABLE A 5 lists the LDoms related issues that have been fixed TABLE A 5 Fixed LDoms Related Issues CR Description Workaround 6543749 A guest domain wanboot miniroot download Note Fixed in System Firmware 7 1 0 g or could take more than 30 minutes lat
108. nce 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 Chapter 2 Important Information About the SPARC Enterprise T5120 and T5220 Servers 19 Software running in different guest domains on 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 latest Logical Domains LDoms 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 20 Notes on the Use of 200V Power Supply For the servers that have the B type plug confirm that a 15A overcurrent protection device is available outside the server If one is not available prepare an external 15A overcurrent protection that can be achieved by means of no fuse breakers NFBs or fuses The B type plug refers to plugs other than grounding type ones with two parallel blades such as the NEMA L6 30 L6
109. neral Solaris OS late breaking issues are described in the Solaris 10 Release Notes TABLE 3 4 Solaris OS Issues CR Description Workaround 6519290 Large amounts of I O on swap devices might The amount of I O required may be generated cause the system to appear hangup by through a number of ways memory shortage overwelling the I O system heavy use of tmp etc Set the following to etc system and then reboot the Solaris OS set maxfastscan 0x2000 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 e From the ALOM CMT compatibility CLI sc gt showlocator sc gt setlocator on sc gt setlocator off 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 PS0 TEMP_ FAULT is accurate and represents the current condition of the components 52 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 3 4 Solaris OS Issues Continued CR Description Workaround 6373437 A Solaris OS shutdown might hang and result in Reboot the system by dropping to the service 6588499 fewer system services processor SP Then power cycle the host Rarely a shutdown performed immediately after Syst
110. nformation About the T5120 and T5220 Servers on page 1 This section describes important new information about the T5120 and T5220 servers a New Information About Known Issues on page 5 This section describes technical issues that were identified after the previous edition was published Information that was documented in the previous edition of this document is provided in the following locations m Chapter 2 contains important information about the T5120 and T5220 servers m Chapter 3 describes technical issues m Chapter 4 describes documentation issues Important New Information About the T5120 and T5220 Servers The section describes new capabilities that are supported on the SPARC Enterprise T5120 and T5220 servers Support for SSD Storage on page 2 a Support for RAID Function on page 4 a Support for Windows 7 and Internet Explorer 8 on page 5 Support for SSD Storage This section describes support for 32GB SATA SSD Solid State Drives It also describes the procedure for updating the SATA Controller with the firmware version required to use SSDs SPARC Enterprise T5120 and T5220 servers can now use 32GB SATA SSDs for internal storage The SSDs are hot pluggable You can replace the existing 2 5 inch SAS hard drives with the SSDs You can also have both 2 5 inch SAS hard drives and SSDs installed at the same time Note The number of 32GB SATA SSDs which can be installed in T5120 T52
111. nnecessary and can be ignored 3 SPARC Enterprise T5120 server 8 disk capable Remove fan FM1 Incorrect FRU Name is Specified in the TABLE Motherboard Components SPARC Enterprise T5120 Servers The FRU Name of SYS MB SC SCC_NVRAM should be SYS MB SCC_NVRAM 66 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Incorrect FRU Name is Specified in the TABLE Motherboard Components SPARC Enterprise T5220 Servers The FRU Name of SYS MB SC SCC_NVRAM should be SYS MB SCC_NVRAM SPARC Enterprise T5120 and T5220 Servers Administration Guide Notes on the SPARC Enterprise T5x20 Device Tree The device tree of the DVD drive indicated on page 39 is not supported for the servers shipped after September 2009 The correct tree is as follows m For the servers shipped after September 2009 pci 0 pci 0 pci 1 pci 0 pci 1 pci 0 usb 0 2 hub 4 device 4 storage 0 disk Integrated Lights Out Manager 2 0 User s Guide Incorrect ILOM Command Related to IP Address Assignment The ILOM commands indicated on page 23 and page 28 include erroneous information setpendingipdiscovery should be set pendingipdiscovery Chapter 4 Documentation Errata 67 The Command in the Section Edit an SNMP User Account Using the CLI on Page 195 is Incorrect The following command described is incorrect edit SP services snmp users username authenticationpassword password To edit an SNMP v3 user account type the
112. ns 1 0 1 software there are a For more information refer to the Logical few cases where variable updates do not persist Domains LDoms 1 0 1 Release Notes 6597815 XAUI and CPU resources added after initial When you add CPU or XAUI resources to a LDoms Setup are not available to LDoms server configured to use logical domains you Manager must revert to the factory default configuration to allow the LDoms Manager software to allocate those resources to guest domains 58 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 CHAPTER 4 Documentation Errata This chapter describes known errors and corrections to the SPARC Enterprise T5120 and T5220 server documentation SPARC Enterprise T5120 and T5220 Servers Site Planning Guide on page 59 SPARC Enterprise T5120 and T5220 Servers Installation Guide on page 64 SPARC Enterprise T5120 and T5220 Servers Service Manual on page 64 SPARC Enterprise T5120 and T5220 Servers Administration Guide on page 67 Integrated Lights Out Manager 2 0 User s Guide on page 67 Integrated Lights Out Manager 2 0 Supplement for the SPARC Enterprise T5120 and T5220 Servers on page 68 Integrated Lights Out Manager ILOM 3 0 CLI Procedures Guide on page 69 Integrated Lights Out Manager ILOM 3 0 Web Interface Procedures Guide on page 70 Integrated Lights Out Manager ILOM 3 0 Supplement for SPARC Enterprise T5120 and T5220 Servers on
113. nt part 1 of the data kept on the motherboard is inadvertently overwritten with new SCC module data 2 This results in a connection failure to the ILOM network 1 SCC module data including ILOM user data network setting data and diagnostics data For details see the ILOM Supplement for each server 2 The data is initialized at this point in time so the data has no set values Also the following type of log is output to the ILOM serial console window at the occurrence of the failure sccd fails to start at ILOM startup Example of output to ILOM serial console at failure occurrence SUNSP BELO7482AU login root Password Waiting for daemons to initialize Timed out waiting for daemons to start lt sccd daemon has shutdown lt Integrated Lights Out Manager Version 3 0 3 20 e Copyright 2009 Sun Microsystems Inc All rights reserved Use is subject to license terms Warning password is set to factory default Be sure to back up the service processor settings before replacing the SCC module Workaround If only the SCC module fails replace the SCC module together with the motherboard After replacing these components restore the backed up contents Appendix A Fixed Issues 115 Solaris OS Issues TABLE A 4 lists the Solaris OS issues that have been fixed TABLE A 4 Fixed Solaris OS Issues CR Description Workaround 6243759 The Solaris prtdiag command displays
114. nt Information About the SPARC Enterprise T5120 and T5220 Servers 15 Mandatory Patch Information Patches are available at Global Site http www fujitsu com global support software security products s patch info Japanese Site http software fujitsu com jp security products others unix North American Site https download computers us fujitsu com Before contacting support ensure that all mandatory patches are installed on your server In addition to applying the periodic PTF check the above web site on a regular basis for the availability of new patches Mandatory Patches for the Solaris 10 8 07 OS TABLE 2 4 lists the mandatory patch that is needed for servers running the Solaris 10 8 07 OS This patch was installed along with the OS at the factory If you reinstall the server with the Solaris 10 8 07 OS you must reinstall this patch TABLE 2 4 Mandatory Patch for Servers Installed with the Solaris 10 8 07 OS Patch IDs Description Fixes Provided 127127 11 or later SunOS 5 10 kernel Includes the following fixes patch e CR 6590132 System panics n2cp alignment error in IPsec testing e Issues regarding data integrity in the nxge driver as reported by Sun Alert ID 103076 e CR 6568352 IPsec performance does not scale using hardware crypto providers To determine if a patch is present see To Download Patches on page 17 Mandatory Patches for the Solaris 10 5 08 OS There are no mandatory patches for
115. nterprise T5120 and Debugging requested hardware watchdog 15220 Servers Administration Guide suspended c ontinue s ync r eset 6624705 When a component set disable by using None Component Management of BUI on the screen of an ALOM mode log in user a message appears which supposed to be shown when the command executed from CLI Fault critical SP detected fault at time Wed Jul 18 09 37 15 2007 SYS MB GBE1 Disabled by CLI action Chapter 3 Known Issues 29 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6627396 If you keep on continuously executing the If ILOM has been used at least once log out command in the service processor that you from ILOM logged in the return of command slows down When problems arise AC power cycle the Or errors might occur system 6628377 Though you disable the TTYA by using the None ILOM command it doesn t turn disable and you can log in to OS 6662997 If you change any firmware variables suchas 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 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 customize
116. nterprise T5120 and T5220 Servers Product Notes April 2010 When the showenvironment Command is Executed in a Sixteen Disk Capable Server Even Though the Hard Disk is Mounted in Slot 8 NOT PRESENT is Output CR 6772707 This issue is resolved by updating the system firmware to 7 2 2 e or later When the showenvironment command of ALOM CMT compatible shell is executed in a sixteen disk capable server even though the hard disk is mounted in slot 8 NOT PRESENT is output For examp le SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD SYS HD Omitted sc gt Omitted D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 sc gt showenvironment OK NOT PRESENT OK OK OK OK OK OK OK Workaround The status can be confirmed from the ok prompt by using the probe scsi all command Appendix A Fixed Issues 107 For example 0 ok probe scsi all pci 0 pci 0 pci 2 scsi od Omitted Target 8 Unit 0 Disk SEAGATE ST914602SSUN146G0603 286739329 Blocks 146 GB SASAddress 5000c5000b36a225 PhyNum 8 Omitted 0 108 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 For DC Input Power Models the Output From the showpower v Command May Differ Between SYS PSO And SYS PS1 CR 6802433 This issue is resolved by updating the system firmwa
117. nts in the system 6667545 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 6480945 configurations error messages might not be RAID 1 configurations and you see the displayed on the console or in the log files following scenario the disk drive should be 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 service indicator is set to ON Replace the disk drive with the lit Fault LED 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 a power supply fan and the fan returns to normal operation the fault indication is not automatically cleared 6674290 In the SPARC Enterprise T5220 server if a XAUI If possible do not install any PCIe cards in the card and a PCle 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 22 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 3 1 Hardware and Mechanical Issues Cont
118. od for five years Depending on the user environment such as the frequency of use replacement may be required before the five year maintenance support period expires About the SSD Use on the 16 Disk Backplane Model To use the SSDs on the 16 disk backplane model only the server equipped with the USB SATA DVD drive can be used For servers shipped after September 2009 the USB SATA DVD drive unit has been mounted Confirm whether a USB SATA DVD drive unit is mounted on your server by using either of the following methods m Confirm that the SATA DVD mark appears on the front side of the DVD drive Confirm that specific part numbers are displayed in the output for the following ILOM ALOM commands Confirm by using ILOM command Confirm whether either of the following part numbers is displayed in the output from 1s SYS PADCRD command fru_part_number 5413512 or fru_part_number 5413513 Confirm by using ALOM command Confirm whether either of the following part numbers is displayed in the output from showfru SYS PADCRD command Partner Part _NumberR Partner Part Number CF005413512REVxx or Partner Part _NumberR Partner Part Number CF005413513REVxx Chapter 1 New Information About the SPARC Enterprise T5120 and T5220 Servers 3 Updating LSI 1068e Controller Firmware to Support SSDs To use SSDs the version of LSI 1068e controller firmware should be 1 27 00 00 or later Depending on the firmware version of you
119. omain and the service processor SP could hang and disable communication over the channel Disable DMI service at the startup For example mv etc rc3 d S77dmi etc re3 d _S77dmi For workaround procedures see Problem When the PCIe Link Fails to Train as x8 CR 6556505 on page 38 If you use scripts to log into the SP be aware of this issue To clear POST results use the ALOM CMT compatibility setdefaults command See Communication Channel Between the Primary Domain and the Service Processor SP Might Hang CR 6583567 on page 39 Chapter 3 Known Issues 27 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6585114 6585292 6595955 6596430 6596594 During automated testing the SP could encounter problems with useradd and usershow commands followed by the failure of all login attempts Some extraneous and misleading warning 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 40 If a component is not physically present on a system such as the fan module the status field in the prtdiag v Environmental Status Section output shows no value and is blank If the socketed EEPROM SCC is replaced the SP does not always read some SP properties
120. ommand with a value greater than 1000 might result in the SP becoming unusable 6587919 The first time that show SYS is executed after a power on none is displayed for the product name 6588999 When you connect to the ILOM CLI with SSH and the SP is reset you might see an error message similar to the following Performing hard reset on SP failed reset Transport error check errno for transport error Note Fixed in System Firmware 7 1 6 d or later Use the fault management utilities that are described in the Predictive Self Healing PSH 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 99 You can also update the System Firmware to the latest version to avoid encountering this issue Note Fixed in System Firmware 7 1 6 d or later See The uadmin 2 0 and reboot Commands Read Old Bootmode Settings CR 6585340 on page 100 You can also update the System Firmware to the latest version to avoid encountering this issue Note Fixed in System Firmware 7 1 6 d or later To see the entire consolehistory log use the v option If you need to recover from problems related to running the consolehistory command with more than 1000 lines reboot the SP You can also update the System Firmware to the latest version to avoid encountering this issue
121. on OS patch requirements see Mandatory Patch Information on page 16 Note If you install an OS over the preinstalled OS even if it is the same version you will overwrite the supplementary software that was preinstalled at the factory See Preinstalled Software on page 12 for more information on this additional preinstalled software Note Some optional features require certain versions of the OS and System Firmware See Solaris OS and Firmware Requirements for Certain Features on page 11 TABLE 2 1 Supported Versions of the OS and Firmware Supported Versions os Solaris 10 8 07 OS plus mandatory patches Minimum supported OS Solaris 10 5 08 OS plus patches Solaris 10 10 08 OS Solaris 10 5 09 OS Solaris 10 10 09 OS Latest supported OS Firmware System Firmware 7 0 9 Minimum supported System Firmware System Firmware 7 2 8 Latest supported version as of April 2010 Note When installing the Solaris 10 8 07 OS or Solaris 10 5 08 OS on a server equipped with a USB SATA DVD drive see Notes on Installing Solaris 10 8 07 OS and Solaris 10 5 08 OS on page 56 10 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Solaris OS and Firmware Requirements for Certain Features The following table identifies the minimum OS and firmware versions required to support certain features TABLE 2 2 Minimum OS and Firmware Version Requirements for Certain Features
122. on error SC unretrieved msg Chassis major Hot removal of HDD3 6902381 When you powered on the server all LEDs or all None LEDs on the right side on the front panel may When this event occurred perform the ILOM light up When using System Firmware 7 2 2 e or reset operation If not recovered shut down the later the ILOM status check command the system and then remove and insert the power showenvironment command also displays the cord status of relevant LED being ON however this ILOM reset operation example event itself is an issue absolutely limited to the Loe i ILOM and te the followi LED display and does not have an effect on the og im to eee ee ee system command In case of ILOM command mode gt reset SP Are you sure you want to reset SP y n y In case of ALOM CMT compatible shell sc gt resetsc Are you sure you want to reset the sc y n y 11210193 If an error occurs during POST execution None If this problem occurs use the resetsc Fault Sensor VCORE_POK at SYS MB ALOM CMT compatibility command to clear the deasserted may be registered when the log and reset the LED display showfaults ALOM CMT compatibility command is used for status confirmation However POST will still end normally in this case For an example see An Error is Registered with the showfaults Command When Running POST But POST Ends Normally CR 11210193 on page 48 11215994 In rare circumstances the ok prompt may notbe See The
123. on your system behavior ignore these messages For the Enhanced Support Facility this problem is also resolved by applying the Enhanced Support Facility Patch 914604 04 For Server System Manager no workaround is available SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 After a Host Power On Instruction is Executed from ILOM the POST May Not Start and Processing May Not Go to OS Boot Processing or the ok Prompt CR 6752910 After a host power on instruction is executed from ILOM the POST self diagnostics test may not start and processing may not go to OS boot processing or the ok Prompt for OpenBoot PROM OBP ILOM command interface operation example gt start SYS gt start SP console Are you sure you want to start SP console y n y Serial console started To stop type ALOM CMT compatibility shell operation example sc gt poweron sc gt console Enter to return to ALOM Nothing is displayed on the OS console Entering the escape character restores the ILOM prompt The result of the Domain Status may vary No power on log item has been recorded in the event log showplatform command and showlogs command domain status reference example sc gt showplatform SUNW SPARC Enterprise T5120 Domain Status So Powered off Domain Status Powered on Powered off OpenBoot initializing Unknown etc sc gt sc gt showlogs p p
124. or later In a system with DIMMs or PCle adapters that have been faulted by PSH Predictive Self Healing diagnosis on the host the ALOM showfaults command displays the faulty FRU as the motherboard SYS MB instead of the DIMM or PCIe 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 Appendix A Fixed Issues 99 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 85cal40be5b2 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 adap
125. osystems 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 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 IMPLIE
126. overing a Boot Drive s drive type 5 change 6 change 7 change r 5 partition 6 partition 7 partition select select a predefined tabl modify modify a predefined partition table name name the current table print display the current table label write partition map and label to the disk lt cmd gt execute lt cmd gt then return quit partition gt print Current partition table original Total disk cylinders available 14087 2 reserved cylinders Part Tag root swap backup unassigned unassigned unassigned unassigned unassigned NNW U BP WNEH O partition gt quit FORMAT MENU disk type partition current format repair label analyze defect backup verify save inquiry volname lt cmd gt quit format gt disk Fl wm wu wm wu wu wu wu ag Cylinders Size Blocks 825 3298 12 00GB 2474 0 0 25175424 0 824 4 00GB 825 0 0 8395200 O 14086 68 35GB 14087 0 0 143349312 3299 5772 12 00GB 2474 0 0 25175424 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 select a disk select define a disk type select define a partition table describe the current disk format and analyze the disk repair a defective sector write label to the disk surface analysis defect list management search for backup labels read and display labels save new disk partition definitions show vendor product and revision set 8 character volume
127. p 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 25 There is an important etc system setting for If you reinstall the Solaris OS you must add the 10 Gb Ethernet performance following line to the etc systen file Note The preinstalled Solaris OS has the correct set ip ip_soft_rings_cnt 16 entry in the etc systen file This etc system setting ensures optimum performance for 10 Gb Ethernet interfaces Temporary PCle Link Failure During Boot Causes a Fatal Error Later CR 6553515 If a temporary PCIe 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 1l 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 al TL 1 STT 7 STPC 0238978 S TnPC 023897c STSTATE 820001600 CWP 0 Chapter 3 Known Issues 25 SPSTATE 16 AG 0 IE 1 PRIV 1 AM 0 PEF 1 RED 0 MM 0 TLE 0 CLE 0 MG 0 IG 0 SASI 20 CCR 8 XCC nzvc ICC Nzvc S TL 2 STT 3 STPC 02432
128. page 71 SPARC Enterprise T5120 and T5220 Servers Site Planning Guide Error on page 2 in Minimum Clearance for Service Access The text in Minimum Clearance for Service Access on page 2 contains an error The correct text is as follows 59 60 The SPARC Enterprise T5120 T5220 servers require physical access from the top for maintenance Therefore a stepladder may be required depending on which rack the server is installed in And it may be necessary to remove the server from the rack depending on the component to be replaced The minimum clearance for service access varies depending on whether a stepladder is used Secure an appropriate clearance for service access before starting maintenance This section shows the minimum clearance for service access premised on the standard maintenance work of our company If this minimum clearance cannot be secured contact our field engineer No stepladder is required if this server is installed at the 20U level or lower A stepladder is required if it is installed at the 21U level or higher FIGURE 1 shows the minimum clearance for service access required for either server FIGURE 1 Minimum Clearance for Service Access 1 If the server is installed at the 20U level or lower 1 1 Judged based on the level of the equipment top Nossa Rear side clearance for service access 800mm Equipment rack 1050mm Front side clearance for service access 1700mm 800mm 700m
129. perform this operation You can also update the System Firmware to the latest version to avoid encountering this issue 6604305 During system initialization memory might not Note Fixed in System Firmware 7 1 6 d or later be detected and the following error is reported Power off the host reset the SP and power on the ERROR MB CMP0 BR3 CHO DO must be host populated You can also update the System Firmware to the Rarely the probing of DIMMs fails due to ILOM Jatest version to avoid encountering this issue 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 6612687 Repeated attempts to show or set the serial port Note Fixed in System Firmware 7 0 9 or later properties of the host port might cause the ILOM CLI to hang and become unresponsive 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 86 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 3 Fixed Firmware
130. ple power up or down just enough system components to keep relative utilization at 70 at all times even if workload fluctuates This property is enabled only in the logical domain LDoms environment In case you are not in the logical domain LDoms environment or in case that the logical domain LDoms configuration is the factory default the property setting is available but cannot utilize its power consumption control function 90 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6802433 6801248 6819987 6821325 For DC input power models the INPUT limit value included in the output from the showpower v command may differ between SYS PSO and SYS PS1 The SYS PS1 value is correct For examples see For DC Input Power Models the Output From the showpower v Command May Differ Between SYS PSO And SYS PS1 CR 6802433 on page 109 For DC input power models the following event log might be repeatedly collected when the power to the system is turned on Sample output from the showlogs command Chassis minor Error getting status DC volt for PSO Chassis minor Error getting status DC volt for PS1 Chassis minor Error getting status DC volt for PSO Chassis minor Error getting status DC volt for PSO For DC input power models the following event log might be
131. pt for OpenBoot PROM OBP For details see After a Host Power On Instruction is Executed from ILOM the POST May Not Start and Processing May Not Go to OS Boot Processing or the ok Prompt CR 6752910 on page 43 6726663 In ILOM mode or through access to the ILOM In ILOM mode be sure not to change the Web it may be possible to change the system properties displayed below at power on so as time when the system is powered on not to change the system time directly or enable NTP services gt show SP clock SP clock Targets Properties datetime Wed Dec 3 06 22 48 2008 usentpserver disabled Commands cd set show aw n a The following error message may be output None during POST Since the error has no impact on system operation you can ignore the message 0 0 0 gt Begin Block Mem Test 0 0 0 gt Block Mem Test 00000000 02000000 gt 00000008 00000000 0 0 0 gt FBR Error Tally Branch 3 2 _ Indefinite value 32 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6815369 6746677 6806268 6823561 6830397 For DC input power models PSO AC_POK and PS0 DC_POK identify sensors in the power supply units PS0 AC_POK does not represent an AC power supply unit For examples see For DC Input Power Models PSO0 AC_POK Is Displayed CR 6815369 on page 44 Accor
132. put power model 6 DC cables and 6 RJ45 cables 18 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Optical fiber cables cannot be accommodated in the CMA Route the cables through the free space on top of the CMA m Cables with a cable core such as SCSI cables cannot be accommodated in the CMA Route the cables through the free space on top of the CMA Moreover if it hampers to install optional products that are subject to the following structural restriction first uninstall and remove the CMA m Cables with large connectors such as for an XVR 300 or SAS card must be connected to the top PCle slot Express Rail Rackmounting Kit Installing the servers with the express rail rackmounting kit is not supported SAS RAID Internal HBA Card SAS RAID Internal HBA Card is not currently supported 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 might 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 si
133. quence is not echoed Solaris host prompt gt sc gt 4 Enter the break command sc gt break c y 5 Enter to return to the SP ALOM CMT compatibility CLI sc gt c ontinue s ync r eboot h alt The following is sample output of sending a break to the Solaris host from the SP ILOM CLI 1 Log into the host with the ILOM console command gt start SP console Are you sure you want to start SP console y n y Serial console started To stop type Solaris host prompt gt SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 2 Enter to escape to the SP ILOM CLI The escape sequence is not echoed Solaris host prompt gt gt 3 Enter the break command as follows gt set HOST send break action break gt Log back into the Solaris host with the console command gt start SP console Are you sure you want to start SP console y n y Serial console started To stop type c ontinue s ync r eboot h alt Refer to the Integrated Lights Out Manager 2 0 User s Guide and the Integrated Lights Out Management ILOM Supplement for SPARC Enterprise T5120 and T5220 Servers for details on how to use the break command from the SP CLIs The showfaults Command Shows the Motherboard as Faulty Instead of the DIMM CR 6582853 This issue is resolved by updating the system firmware to 7 1 6 d
134. r server you may need to update the controller firmware The updated version is available on the following web site as a patch release The patch to be applied varies depending on the server models See the documentation on the web site for details and update the firmware https updatesite jp fujitsu com unix en download firmware Support for RAID Function The SPARC Enterprise T5120 and T5220 servers are equipped with a hardware RAID function by default and this section shows the support conditions and the points of concern 1 Support conditions Item Description Mandatory OS patch Patch ID 141444 09 or later or PTF RPTF R10021 or later Mandatory ESF Enhanced 914604 07 or later Support Facility patch System Firmware 7 2 2 e or later RAID level RAID 1 IM Integrated Mirror only In RAID 1 two member disks per volume RAID 0 IS Integrated Stripe is not supported HDD A single volume shall be made up of disks of the same capacity and the same rotational speed SSD is not supported Number of volumes Up to 2 volumes supported per system 2 Points of concern m When using the RAID function a Make backup copies of important data and programs periodically In some failures rebuild of RAID and the data restore from the backup media may become necessary To ensure data integrity in time of unexpected power failure we recommend the use of UPS a If you require higher availability such as the control
135. r slots n a The FM Status Indicator portion of the service Note This error appears on the service labels label has an erroneous statement Where it says for SPARC Enterprise T5220 servers In front of FM on FanBD it should say on top of FM n a The drawing showing the cable management Note This error appears on the service labels arm being rotated represents the wrong server for SPARC Enterprise T5220 servers model It should show the SPARC Enterprise T5220 server n a The Fan Module Configuration portion of the Note This error appears on the service labels service label is wrong It should show fan for SPARC Enterprise T5220 servers with 16 disk modules in location FANBD1 FM1 capable backplanes n a The shapes of anti tilt legs shown on service Note This error appears on the service labels labels may be different depending on racks on all SPARC Enterprise T5120 and T5220 servers 24 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 3 2 Ethernet Interface Related Issues TABLE 3 2 lists the late breaking Ethernet related issues Additional information for some of the issues is provided after the table Ethernet Related Issues CR Description Workaround 6553515 6606950 If a temporary PCIe network link failure occurs If the system fails to boot because of this during boot or any time later the system could problem try booting again fail If the link is u
136. rd Copyright 2009 Sun Microsystems Inc All rights reserved OpenBoot 4 30 6 8064 MB memory available Serial 85367270 Ethernet address 0 21 28 16 99 e6 Host ID 85169966 0 ok This event occurs in case you power off the system and remove the power cord in a short period of time or in case you remove and insert the power cord in a short period of time When the above time period is too short the ILOM internal process does not complete normally When this event occurred perform the following procedure After you restored using this procedure you do not need to replace the component 50 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 4 5 Turn off the power to the system Power off operation example In case of ALOM CMT compatible shell sc gt poweroff y In case of ILOM mode gt stop script SYS Wait for 180 or more seconds Remove the power cord Wait for 180 or more seconds Insert the power cord Workaround Take 180 or more seconds for each of the intervals between the system power off and the power cord removal and between the removal and insertion of the power cord Chapter 3 Known Issues 51 Solaris OS Issues TABLE 3 4 lists the late breaking issues related to the running the Solaris OS on the SPARC Enterprise T5120 and T5220 servers Additional information for some of the issues is provided following the table Note Additionally more ge
137. re to 7 2 2 e or later For DC input power models the INPUT limit value included in the output from the showpower v command may differ between SYS PSO and SYS PS1 The SYS PS1 value is correct Example of showpower v command execution sc gt showpower v INPUT OUTPUT Power Power Supply Status W W SYS PSO OK 172 8 123 8 SYS PS1 OK 153 6 133 3 Total Power 326 4 INPUT INPUT INPUT OUTPUT OUTPUT OUTPUT Volt Current limit Volt Current limit Supply V A A V A A SYS PSO 48 0 3 60 37 20 11 9 10 40 99 20 SYS PS1 48 0 3 20 8 00 11 9 11 20 99 20 sc gt This is incorrect The SYS PSO value is correct Workaround None Ignore this issue because it is only a display error Appendix A Fixed Issues 109 110 In the Output From the prtdiag Command Warnings May Be Displayed CR 6821325 This issue is resolved by updating the system firmware to 7 2 7 b or later In the output from the prtdiag command warnings may be displayed for input voltage sensors V_IN_MAIN on power supply units Voltage sensors SYS MB CMPO MRO SYS MB CMPO MRO SYS MB CMP1 MR1 SYS MB CMP1 MR1 vn K wn z wW wW w w wW w w w w SYS PSO SYS PSO SYS PS1 SYS PS1 V_VMEM V_ 1V5_VDD V_VMEM V_ 1V5_VDD V_ 3V3_STBY V_ 3V3_MAIN V_ 12V0_MAIN V_VDDIO V_VCOREL V_VCORER V_ 1V5_I0 V_VMEML V_VMEMR V_VBAT V_IN_MAIN V_OUT_MAIN V_IN_MAIN V_OUT_MAIN ok warning 48volts ok warning 4
138. repeatedly collected Sample output from the showlogs command IPMI ID 20a 03 11 2009 02 31 48 Current PSO CUR_FAULT State Asserted PMI minor ID 20b 03 11 2009 02 31 51 Temperature PS0 TEMP_FAULT State Asserted PMI minor ID 20c 03 11 2009 02 31 54 Current PSO CUR_FAULT State Deasserted PMI minor ID 20d 03 11 2009 02 31 57 Temperature PSO TEMP FAULT State Deasserted minor H HN ae ey In the output from the prtdiag command warnings may be displayed for input voltage sensors V_IN_MAIN on power supply units For examples see In the Output From the prtdiag Command Warnings May Be Displayed CR 6821325 on page 110 Note Fixed in System Firmware 7 2 2 e or later None Ignore this issue because it is only a display error Note Fixed in System Firmware 7 2 2 e or later None Ignore this event log Note Fixed in System Firmware 7 2 2 e or later None If the Service Required Overtemp and Power Supply Service Required LEDs on the server are off ignore the event log items If one of these LEDs is on indicating that a power supply problem or temperature related problem has occurred correct the problem Note Fixed in System Firmware 7 2 7 b or later None Ignore this issue because it is only a display error Appendix A Fixed Issues 91 TABLE A 3 Fixed Firmware ILOM POST and SP Issues Continued CR Description Workaround 6586
139. ris console reset the service processor sc gt resetsc y ALOM CMT compatibility CLI OR gt reset SP ILOM CLI Once the SP is restarted and you are able to login as the admin which means all daemons are ready execute the following in the Solaris control domain to unload and load the etm fmadm unload etm fmadm load usr platform sun4v 1lib fm fmd plugins etm so Appendix A Fixed Issues 103 Spurious PIU Errors CR 6598381 This issue is resolved by updating the system firmware to 7 1 6 d or later 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 0x4b63c07qdf9ff 0x3e 002421030607 Ox 3e 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 tt 0x0 _
140. s become unresponsive during the creation of snmpv3 users This will result in a core dump Using show SP user adminusr password returns Show Invalid command syntax It should return None None The second reset has no impact on the system None This message has no impact on the system and can be safely ignored None Connect the LAN cable to the NET MGT port of ILOM and then set the network configuration None None None 34 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE 3 3 Firmware ILOM POST and SP Issues Continued CR Description Workaround 6932448 With the System firmware 7 1 6 d or later the Be aware that these messages are not necessarily following type of message might be displayed error messages on the console and in the logs Messages referring to hot insertions of CPUs Chassis major Hot insertion of and hard disks or messages referring to hot SYS MB CMP0 PO insertions removals of a nonexistent device are or displayed at power on if the system has had a SC Alert ID 639621 daemon error SC firmware upgrade or system component change unretrieved msg Chassis major Hot Once the components have been identified no insertion of SYS MB CMP0 P3 subsequent messages are displayed unless ILOM detects a change in the system configuration or Chassis major Hot removal of HDD3 if hardware failure occurs or SC Alert ID 677427 daem
141. s no effect on your server when displayed during boot You might not be able to not using SNMP get some sensor information when using SNMP picld xxx PICL snmpplugin sunPlatSensorClass 0 unsupported 6718841 Sun Explorer may fail to collect the ILOM data You can collect the ILOM data Tx000 in Tx000 If failed it may take more than 30 minutes to return an error another way For details see Sun Explorer May Fail to Collect the ILOM Data Tx000 CR 6718841 on page 55 Chapter 3 Known Issues 53 TABLE 3 4 Solaris OS Issues Continued CR Description Workaround 6836653 USB SATA DVD drive is not supported for the following versions of the Solaris OS e Solaris 10 8 07 OS e Solaris 10 5 08 OS Note USB SATA DVD drive is supported for the later versions of the Solaris 10 OS beginning with Solaris 10 10 08 OS To install Solaris 10 8 07 OS or Solaris 10 5 08 OS on a server equipped with a USB SATA DVD drive install the OS from the install server and apply the mandatory patches the latest periodic PTF and the latest recommended security patches For the installation procedures see Notes on Installing Solaris 10 8 07 OS and Solaris 10 5 08 OS on page 56 For servers shipped after September 2009 the USB SATA DVD drive unit has been mounted Confirm whether a USB SATA DVD drive unit is mounted on your server by using either of the following methods e Confirm that the SAT
142. se messages have no effect on your server following messages Apply patch ID 137111 01 or later Example 1 r eboot o k prompt h alt o WARNING promif_ldom_setprop ds response timeout Example 2 r eboot o k prompt h alt o WARNING promif_ldom_setprop ds response timeout WARNING LDOMs Variable Update request failed NOTICE Unable to complete Domain Service protocol version handshake WARNING Unable to connect to Domain Service providers WARNING Unable to update LDOM Variable 6601028 The LEDs of TX data transmitting and RX data Note Fixed in Solaris patch ID 137137 09 or receiving on XAUI Card do not show correct later status of data transmission Please ignore these LED s status 6886514 Boot drive may report drive type unknown Note Fixed in Solaris patch ID 124630 32 or for Solaris format command For details see later Boot Drive May Report drive type unknown For recovery procedures see Boot Drive May for Solaris format Command CR 6886514 on Report drive type unknown for Solaris page 125 format Command CR 6886514 on page 125 Servers Might Experience Panics Generated From the PCIe Root Complex CR 6555956 This issue is resolved for servers running the Solaris 10 5 08 OS or later 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
143. sis major Host has been powered on 0 0 0 gt 0 0 0 gt SPARC Enterprise TM T5120 T5220 POST 4 30 6 2009 12 01 13 08 Chapter 3 Known Issues 49 export delivery delivery 4 30 4 30 6 post4 30 6 micro Niagara huron integrated root 0 0 gt Copyright 2009 Sun Microsystems Inc All rights reserved 0 0 0 0 gt POST enabling CMP 0 threads ffffffff ffffffff 0 0 0 gt VBSC mode is 00000000 00000001 0 0 0 gt VBSC level is 00000000 00000001 0 0 0 gt VBSC selecting Normal mode MAX Testing 0 0 0 gt VBSC setting verbosity level 2 0 0 0 gt Basic Memory Tests Done 0 0 0 gt Test Memory Done 0 0 0 gt Setup POST Mailbox Done 0 0 0 gt Master CPU Tests Basic Done 0 0 0 gt Init MMU Fault critical SP detected fault at time Mon Jan 18 08 45 10 2010 SYS PADCRD prom is unreadable or corrupted 0 0 0 gt NCU Setup and PIU link train Done 0 0 0 gt L2 Tests Done 0 0 0 gt Extended CPU Tests Done 0 0 0 gt Scrub Memory Done 0 0 0 gt SPU CWQ Tests Done 0 0 0 gt MAU Tests Done 0 0 0 gt Network Interface Unit Tests Done 0 0 0 gt Functional CPU Tests Done 0 0 0 gt Extended Memory Tests Done 2010 01 18 08 46 50 299 0 0 0 gt INFO 2010 01 18 08 46 50 302 0 0 0 gt POST Passed all devices 2010 01 18 08 46 50 307 0 0 0 gt POST Return to VBSC 2010 01 18 08 46 50 310 0 0 0 gt Master set ACK for vbsc runpost command and spin Chassis major Host is running SPARC Enterprise T5220 No Keyboa
144. st guidelines domain I O domain Case 1 Do not remove an I O branch from the Case 1 If you remove an I O branch from the primary domain and then immediately add it logical domain configuration of the primary back to the primary domain domain and then add the same I O branch back Case 2 Be certain to add the I O branches to the to the primary domain upon reboot the system guest domains in numerical order might come back up without any I O the 4 Su p system might hang in OpenBoot or the entire Example 1 The primary domain is using pci 400 onboard disks USB DVD and slots I O branch and the associated I O devices PCIe0 and PCIe1 and you want to assign might be absent from the primary domain y pcei 500 pci 600 and pci 700 to three guests For example the following actions performed in Do the following the sequence shown might lead to the primary l domain hanging in OpenBoot 1 1am add io pci 500 guestB 1 1dm rm io pci 500 primary 2 1dm add io pci 600 guestA Remove pci 500 from the configuration 3 Idm add io pci 700 guestC 2 1dm rm io pci 600 primary Example 2 The primary domain is using Remove pci 600 from the configuration pei 300 onboard 1Gb see and10Gb sec f network slots PCIE4 PCIE5 XAUIO XAUI1 and elm DER Ree eene Primary you want to assign pci 400 pci 600 and Add pci 500 back to the configuration pci 700 to three guests Do the following 4 1am add config config_name 1
145. t SYS MB PCIE IO USB Information Missing From prtpicl and prtdiag Commands CR 6586624 This issue is resolved by updating the system firmware to 7 0 9 or later Appendix A Fixed Issues 121 122 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 m 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 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 This issue is resolved for servers running the Solaris 10 5 08 OS and later If you are running Solaris 10 8 07 you can fix this issue with patch ID 127127 11 or later Booting the Solaris 10 OS from an external USB DVD ROM drive
146. t Displayed After POST Ends CR 11215994 49 After the Power Cord Removal Insert an Error Message May Appear during the POST 49 Solaris OS Issues 52 Contents v Sun Explorer May Fail to Collect the ILOM Data Tx000 CR 6718841 55 Notes on Installing Solaris 10 8 07 OS and Solaris 105 08 OS 56 LDoms Related Issues 58 4 Documentation Errata 59 SPARC Enterprise T5120 and T5220 Servers Site Planning Guide 59 Error on page 2 in Minimum Clearance for Service Access 59 Incorrect Values for the 1 6 GHz SpecJBB Test 62 Incorrect Idle Input Power Values 63 SPARC Enterprise T5120 and T5220 Servers Installation Guide 64 Verify Proper Seating of Preinstalled PCle XAUI Cards 64 SPARC Enterprise T5120 and T5220 Servers Service Manual 64 Erroneous Description in the Section Disconnect Power Cords From the Server 64 Erroneous Description in the Section Removing the Air Duct on page 101 65 Erroneous Description in Fan Module Configurations for SPARC Enterprise T5220 Servers 8 and 16 Disk Capable 66 Unnecessary Procedure in Install the Hard Drive Cage 66 Incorrect FRU Name is Specified in the TABLE Motherboard Components SPARC Enterprise T5120 Servers 66 Incorrect FRU Name is Specified in the TABLE Motherboard Components SPARC Enterprise T5220 Servers 67 SPARC Enterprise T5120 and T5220 Servers Administration Guide 67 Notes on the SPARC Enterprise T5x20 Device Tree 67 Integrated Lights Out Manager 2 0 User s Guide 67
147. t later aligned None e Though the CPU threads have been disabled the FRU Status shows All FRUs are enabled e Information of a FAN replaced by hot swapping is not displayed e Some of the memory configuration information is not displayed 6572985 During long SunVTS test runs the SunVTS Note Fixed in Solaris patch ID 139667 01 or cryptotest could fail intermittently with an later error similar to the following Install the SunVTS Patch number 127294 01 or cryptotest FATAL n2rng0 later SUNW_RANDOM generate failed values generated fall outside statistical tolerance 6578410 The server might hang when trying to boot with Note Fixed in the Solaris 10 5 08 OS and an Infiniband HBA card installed later and in the Solaris 10 8 07 OS with patch ID 127127 11 or later installed Add the following setting to the etc system file set tavor tavor_iommu_bypass 0 You can also upgrade the OS or install the patch to avoid encountering this issue Appendix A Fixed Issues 117 TABLE A 4 Fixed Solaris OS Issues Continued CR Description Workaround 6586624 The Solaris prtdiag and prtpicl commands Note Fixed in System Firmware 7 0 9 or later might not display complete information as Use alternative methods to obtain the follows information you need as described in e If the prtdiag v option is specified the Information Missing From prtpicl and firmware version and the chassis serial prtdiag Commands CR 6586624
148. t the LED display SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 The ok Prompt is Not Displayed After POST Ends CR 11215994 In rare circumstances the ok prompt may not be displayed normally after POST execution ends Workaround If this problem occurs use the showfaults v ALOM CMT compatibility command to confirm the status of POST When the Last POST Run displays the date and time of the POST currently executed and POST Status shows Passed all devices this indicates that the POST completed normally Execute the resetsc ALOM CMT compatibility command and then execute the poweroff and poweron ALOM CMT compatibility commands in this order 2008 04 29 1 721035 407 Oie 0 OS 30 ies 2008 04 29 17 10 57 749 0 0 0 gt End Block Mem Test 2008 04 29 17 10 57 757 0 0 0 gt INFO 2008 04 29 17 10 57 766 0 0 0 gt POST Passed all devices 2008 04 29 17 10 57 783 0 0 0 gt POST Return to VBSC 2008 04 29 17 10 57 795 0 0 0 gt Master set ACK for vbsc runpost command and spin sc gt sc gt showfaults v Last POST Run Tue Apr 29 17 10 58 2008 Post Status Passed all devices No failures found in System sc gt After the Power Cord Removal Insert an Error Message May Appear during the POST After you remove insert the power cord and while POST is running the SYS XXXXX prom is unreadable or corrupted message may appear and stop at ok prompt Message example Chas
149. terfaces will come back up with no further panics Workaround Unplumb the interfaces prior to unloading the driver To Unplumb the Interfaces Prior to Unloading the Driver It is usually not necessary to unload a driver from a running kernel In those rare cases where it might be called for you must unplumb all driver instances prior to unloading the driver 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 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 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 4 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 Appendix A Fixed Issues 77 3 Run ifconfig a again to verify that there are no active nxge interfaces Example ifconfig a 100 flags 20010
150. tering this issue 116 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 TABLE A 4 Fixed Solaris OS Issues Continued CR Description Workaround 6554813 During the transmission using the GLDv3 Note Fixed in Solaris patch ID 127127 11 or Generic LAN Driver version 3 compliant later Ethernet driver if you execute the ifconfig Add the following entry to the etc system command with the modlist file and reboot the system modinsert modremove option the software set ip ip soft rings cnt 0 ring procedure of GLDv3 module could cause a deadlock 6555956 Servers might experience panics generated from Note This issue is resolved for servers the PCle root complex running the Solaris 10 5 08 OS or later A panic could occur during reboot with the If your server experiences this panic perform following message the workarounds described in Servers Might Fatal error has occurred in PCIe root Experience Panics Generated From the PCIe complex Root Complex CR 6555956 on page 120 The panic only occurs during a reboot and has If you are not running the Solaris 10 10 08 OS never been observed during a reboot that this issue is also resolved by installing patch ID follows the panic The panic can occur even if no 128304 03 or later external USB devices are connected to the server 6566442 The prtdiag command output may be incorrect Note Fixed in Solaris patch ID 127127 11 or e Information of memory is displayed as lef
151. terprise T5220 Server 8 Disk Capable Power Specifications Minimum Server Configuration Specifications 4 core 1 2 GHz processor with four 1 GB FBDIMMs no HDDs no PCle I O cards Incorrect Value Correct Value Incorrect Value Correct Value AC Input AC Input DC Input DC Input Idle input power 194 0 W 186 0 W 181 2 W 173 7 W Table 8 SPARC Enterprise T5220 Server 16 Disk Capable Power Specifications Minimum Server Configuration Specifications 4 core 1 2 GHz processor with four 1 GB FBDIMMs no HDDs no PCle I O cards Incorrect Value Correct Value Incorrect Value Correct Value AC Input AC Input DC Input DC Input Idle input power 194 0 W 186 0 W 181 2 W 173 7 W Chapter 4 Documentation Errata 63 SPARC Enterprise T5120 and T5220 Servers Installation Guide This manual includes descriptions using the cable management arm CMA however the SPARC Enterprise T5120 server doesn t support the cable management arm Verify Proper Seating of Preinstalled PCle XAUI Cards The server installation procedure should include instructions for verifying that any preinstalled PCle and or XAUI cards and their risers have not worked loose during shipping This procedure should also include instructions for verifying that internal cables are properly routed and that their connections are secure Workaround When installing a newly arrived server that has preinstalled PCle and or XAUI cards open it and verify that
152. ters 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 MSGID 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 This issue is resolved by updating the system firmware to 7 1 6 d or later 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 100 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 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
153. the Logical Domains environment after the host reset operation host may be reset again Example sc gt reset c y Reset major Reset of SYS initiated by alom Reset major Reset of SYS by alom succeeded Performing reset on the system ct ct Enter to return to ALOM SPARC Enterprise T5220 No Keyboard Copyright 2009 Sun Microsystems Inc All rights reserved OpenBoot 4 30 2 build_06 PROTOTYPE BUILD 2048 MB memory available Serial XXXXXXxX Ethernet address XX XX XX XX XX XX Host ID XXXXXXX host1 console login Chassis critical Host has been reset SPARC Enterprise T5220 No Keyboard Copyright 2009 Sun Microsystems Inc All rights reserved OpenBoot 4 30 2 build_06 PROTOTYPE BUILD 2048 MB memory available Serial XXXXXXXXX Ethernet address XX XX XX XX XX XX Host ID XXXXXXX host1 console login Workaround None The second reset has no impact on the system 46 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 The ILOM Network Configuration Cannot Be Set CR 6835854 6779753 In case that the NET MGT port of ILOM has not been connected with the LAN cable and the network gateway is not set the ILOM network configuration cannot be set Output example when the settings cannot be applied gt set SP network pendingipdiscovery static Set pendingipdiscovery to static gt set SP network pendingipaddress 192 9 200 33 Set pendingipad
154. the SCC Module Replacement a Connection to the ILOM Network May Fail CR 6857271 115 Solaris OS Issues 116 Servers Might Experience Panics Generated From the PCle Root Complex CR 6555956 120 Information Missing From prtpicl and prtdiag Commands CR 6586624 121 Booting the Solaris OS From an External USB DVD ROM Drive Could Cause a Panic CR 6588452 122 The prtdiag v Command Has Formatting Issues CR 6587389 123 PSH Events Are no Longer Transported CR 6594506 124 viii SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Boot Drive May Report drive type unknown for Solaris format Command CR 6886514 125 LDoms Related Issues 134 Contents ix x SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Preface These product notes contain late breaking information about the SPARC Enterprise T5120 and T5220 servers hardware software or documentation errata that became known after the documentation set was published m Support for the SPARC Enterprise T5120 and T5220 Servers on page xi a Fujitsu Welcomes Your Comments on page xii Support for the SPARC Enterprise T5120 and T5220 Servers Technical Support If you have any technical questions or issues that are not addressed in the SPARC Enterprise T5120 or T5220 servers documentation contact a sales representative or a certified service engineer Downloading Documentation Instructions for installing ad
155. the Solaris 10 5 08 OS at this time 16 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 Mandatory Patches for the Solaris 10 10 08 OS There are no mandatory patches for the Solaris 10 10 08 OS at this time Mandatory Patches for the Solaris 10 5 09 OS There are no mandatory patches for the Solaris 10 5 09 OS at this time 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 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 127127 11 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 127127 09 is displayed you must download and install the patch The last two digits of the patch ID represent the revision of the patch 2 Access the above mentioned web site to download the patches 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
156. the cards and their risers are securely seated Also verify that the internal cables are correctly routed and securely connected Refer to the SPARC Enterprise T5120 and T5220 Servers Service Manual for information about the PCle XAUI cards and their risers as well as information about internal cable routing AN SPARC Enterprise T5120 and T5220 Servers Service Manual Erroneous Description in the Section Disconnect Power Cords From the Server The following description in the section Disconnect Power Cords From the Server is incorrect m Unplug all power cords from the server Caution Because 3 3v standby power is always present in the system you must unplug the power cords before accessing any cold serviceable components 64 SPARC Enterprise T5120 and T5220 Servers Product Notes April 2010 The correct information is as follows m For AC models Unplug all power cords from the server m For DC models Turn off the power at the power source circuit breaker Caution When power is applied to the server even when the host is powered off the 3 3v standby power is present in the system so you must remove power before accessing any cold serviceable components Erroneous Description in the Section Removing the Air Duct on page 101 The following description in the section Removing the Air Duct on page 101 is incorrect 3 SPARC Enterprise T5120 server 8 drive capable Disconnect and stow t
157. to http www sun com software solaris liveupgrade 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 An overview of the Cool Tools and full documentation is available at http www sun com servers coolthreads overview cooltools jsp Chapter 2 Important Information About the SPARC Enterprise T5120 and T5220 Servers 13 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 domain 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
158. ues 41 Workaround Make sure that both server power supplies are operating When both power supplies are operating the server will remain powered on during and after erroneous faults A Built In Fan May be Erroneously Detected as a Failure CR 6636098 If a built in fan is erroneously detected as a failure and reported as such to the Enhanced Support Facility software or Server System Manager software the following message is displayed Message Example of Enhanced Support Facility FJSVmadm A FANBDO FM0 FO TACH FJSVmadm Detected failure on the fan location of a built in fan Results may vary Message Example of Server System Manager SSMAPL A FJSVapplg status was changed component FANBDO FMO from normal to fatal location of a built in fan Results may vary However entering one of the ILOM status confirmation commands such as the showenvironment command will display the status of the system correctly When the actual faulty in a built in fan is detected the following sample message is displayed Otherwise a built in fan is erroneously detected as a failure and the message below is not displayed sc gt showfaults Last POST Run Fri May 16 14 27 39 2008 Post Status Passed all devices ID FRU Fault 1 SYS FANBDO FMO SP detected fault TACH at SYS FANBDO FMO FO has exceeded low non recoverable threshold 42 Workaround Since these messages do not have an effect
159. vents are logged 6591367 You cannot obtain the system DIMM FRU Note Fixed in System Firmware 7 1 6 d or later information with the ipmitool utility Obtain the DIMM FRU information using the SP 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 SPARC Enterprise T5120 and T5220 Servers for details You can also update the System Firmware to the latest version to avoid encountering this issue 6593547 An erroneous watchdog reset error might occur Note Fixed in System Firmware 7 1 6 d or later If this error occurs the system will not complete The error is erroneous and can be ignored the boot sequence You might see the following Type boot at the ok prompt to proceed CELOR Ut either the I O or the Control domain You can also update the System Firmware to the when attempting to boot and the boot sequence latest version to avoid encountering this issue will be aborted ERROR Last Trap Watchdog Reset 6593801 When all platform identity checks fail system Note Fixed in System Firmware 7 1 3 d or later power on should be disabled If enough of the FRUs are corrupted the system cannot determine its identity which makes certain components nonoperational and could crash the server 6594506 Domain ETM and LDC Deadlock When Note Fixed in Solaris patch ID 125369 12 or Transmit Queue Full For exampl
160. ximum speed supported by the CD DVD drive Even if the maximum operation is not reached there are no problems in the processing for writing to the CD DVD media 6840287 When a server is power cycled with DVD media Ignore the message installed the message Device is gone will be displayed approximately 30 minutes after the OS is booted up 6857080 Systems with firmware version 7 2 2 x have low Ensure that the air flowing into the server is fan speed 5000 rpms The low fan speed within the ambient temperature specification condition can result in SC Alerts that warn of the low fan speed n a The On Standby portion of the service label Note This error appears on the service labels contains an error It says to press and hold the on all SPARC Enterprise T5120 and T5220 server On Standby button for 5 seconds It should configurations say 4 seconds n a Some service labels show an extra fan module in Note This error appears on the service label for step 2 of the four step fan board diagram The extra fan is on the right half of FanBDO SPARC Enterprise T5120 servers with 4 disk capable backplanes Chapter 3 Known Issues 23 TABLE 3 1 Hardware and Mechanical Issues Continued CR Description Workaround n a On service labels that show the locations of Note This error appears on the service labels PCIe and XAUI slots the XAUI callouts are for SPARC Enterprise T5220 servers wrong They should point to the lowe

- Fujitsu

Contents

Download Pdf Manuals

Related Search

Related Contents