Download Print this page

Fujitsu SPARC Enterprise T5120 Product Notes

Sparc enterprise servers
Hide thumbs

Advertisement

SPARC Enterprise
T5120 and T5220 Servers
Product Notes
Manual Code C120-E458-09EN
Part No. 875-4189-19
April 2010, Revision A

Advertisement

loading

  Summary of Contents for Fujitsu SPARC Enterprise T5120

  • Page 1 SPARC Enterprise ™ T5120 and T5220 Servers Product Notes Manual Code C120-E458-09EN Part No. 875-4189-19 April 2010, Revision A...
  • Page 2 Fujitsu Limited or Sun Microsystems, Inc., or any affiliate of either of them.
  • Page 3: Table Of Contents

    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...
  • Page 4 SAS RAID Internal HBA Card 19 Processor Identification 19 Notes on the Use of 200V Power Supply 20 Known Issues 21 Hardware and Mechanical Issues 22 Ethernet Interface Related Issues 25 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 5 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 ▼...
  • Page 6 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 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 7 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...
  • Page 8 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...
  • Page 9 Boot Drive May Report “drive type unknown” for Solaris format Command (CR 6886514) 125 LDoms Related Issues 134 Contents...
  • Page 10 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 11: Technical Support

    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. “Support for the SPARC Enterprise T5120 and T5220 Servers” on page xi ■ “Fujitsu Welcomes Your Comments” on page xii ■...
  • Page 12 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 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 13: New Information About The Sparc Enterprise T5120 And T5220 Servers

    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.
  • Page 14: Support For Ssd Storage

    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/T5220 servers varies depending on the maximum number of HDDs installed in the servers.
  • Page 15: About The Estimated Usable Period Of Ssds

    = 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 /Partner_Part_NumberR/Partner_Part_Number: CF005413513REVxx Chapter 1 New Information About the SPARC Enterprise T5120 and T5220 Servers...
  • Page 16: Updating Lsi 1068E Controller Firmware To Support Ssds

    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.
  • Page 17: Support For Windows 7 And Internet Explorer 8

    7 and Internet Explorer 8 operating system clients. New 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...
  • Page 18: Hardware And Mechanical Issues

    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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 19: Firmware, Ilom, Post, And Sp Issues

    Mon Jun 29 23:54:28 2009 IPMI minor ID = e20 : 06/29/2009 : 23:54:28 : Power Unit : /SYS/VPS : Upper Critical going low : reading 0 < threshold 1215.40 Watts Chapter 1 New Information About the SPARC Enterprise T5120 and T5220 Servers...
  • Page 20 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 21: Notes On Dvd Drive And Discs

    C H A P T E R 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 ■...
  • Page 22: Supported Versions Of The Os And Firmware

    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 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 23: Solaris Os And Firmware Requirements For Certain Features

    The System Firmware controls various aspects of the host and the service processor. The System Firmware comprises the following individual firmware components: Integrated Lights Out Manager (ILOM) firmwares ■ Chapter 2 Important Information About the SPARC Enterprise T5120 and T5220 Servers...
  • Page 24: Preinstalled Software

    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. Preinstalled Software...
  • Page 25: Solaris 10 Os And Solaris Live Upgrade

    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...
  • Page 26: Logical Domains

    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.
  • Page 27: Sun Studio C, C++ & Fortran Compilers And Tools

    Sun Studio C, C++ & 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 Important Information About the SPARC Enterprise T5120 and T5220 Servers...
  • Page 28: Mandatory Patch Information

    To determine if a patch is present, see “To Download Patches” on page Mandatory Patches for the Solaris 10 5/08 OS There are no mandatory patches for the Solaris 10 5/08 OS at this time. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 29: Mandatory Patches For The Solaris 10 10/08 Os

    Patches for Option Cards If you add option cards to your server, refer to the documentation and README files for each card to determine if additional patches are needed. Chapter 2 Important Information About the SPARC Enterprise T5120 and T5220 Servers...
  • Page 30: Installing The Fujitsu 4Gbps Fibre Channel Card

    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...
  • Page 31: Express Rail Rackmounting Kit

    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...
  • Page 32: Notes On The Use Of 200V Power Supply

    The B-type plug refers to plugs other than grounding-type ones with two parallel blades, such as the NEMA L6-30, L6-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...
  • Page 33: Known Issues

    C H A P T E R 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 ■...
  • Page 34: Hardware And Mechanical Issues

    PCIe card are installed on the same same riser assembly as a XAUI card. riser assembly, the XAUI card might fail POST and be disabled when the server boots. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 35 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.
  • Page 36 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 37: Ethernet Interface Related Issues

    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 TABLE 3-2 Description Workaround 6553515 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.
  • Page 38: Ierrs Are Generated When 100Mb/Full With Forced Speed/Duplex Is Set In E1000G.conf (Cr 6555486)

    ■ 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 39: Firmware, Ilom, Post, And Sp Issues

    Firmware, ILOM, POST, and SP Issues TABLE 3-3 lists the late-breaking issues for the firmware, ILOM (including ALOM compatibility CLI), POST, and service processor (SP). Additional information for some of the issues is provided following the table. Firmware, ILOM, POST, and SP Issues TABLE 3-3 Description Workaround...
  • Page 40 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 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 41 At this time, the following message appears on For the details, see the section “OpenBoot ok the OS console; but none of the options can Prompt“ in the SPARC Enterprise T5120 and obtain the ok prompt. T5220 Servers Administration Guide.
  • Page 42 If this problem occurs, terminate the login processor, executing a command, and logging session on the client from which you have out, logout may fail. accessed the service processor. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 43 Firmware, ILOM, POST, and SP Issues (Continued) TABLE 3-3 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.
  • Page 44 0:0:0>Begin: Block Mem Test 0:0:0>Block Mem Test 00000000. 02000000- >00000008. 00000000 0:0:0> FBR Error Tally Branch 3 = 2 = Indefinite value SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 45 Firmware, ILOM, POST, and SP Issues (Continued) TABLE 3-3 Description Workaround 6815369 For DC input power models, /PS0/AC_POK None. 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, /PS0/AC_POK Is Displayed (CR 6815369)”...
  • Page 46 None. during the creation of snmpv3 users. This will result in a core dump. None. 6856315 Using show /SP/user/adminusr password returns show: Invalid command syntax. It should return “*****”. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 47 Firmware, ILOM, POST, and SP Issues (Continued) TABLE 3-3 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-...
  • Page 48 When you set /HOST bootfailrecovery to None. powercycle, powercycle (host power-off/on) Set to poweroff, wait for the host power turns fails to be executed. off and then manually turn on the host power. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 49 Firmware, ILOM, POST, and SP Issues (Continued) TABLE 3-3 Description Workaround 6883269 After downgrading the system firmware from None. 7.2.x to 7.1.x, "Condition" of the I_USB0 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.
  • Page 50: Problem When The Pcie Link Fails To Train As X8 (Cr 6556505)

    If no PCIe devices are displayed, the server has encountered this problem. Note – All PCIe devices begin with the path /pci@0/pci@0. ▼ To Correct the Problem 1. Take down all domains and power off the system. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 51: Communication Channel Between The Primary Domain And The Service Processor (Sp) Might Hang (Cr 6583567)

    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> setsc diag_mode normal sc>...
  • Page 52: To Recover From A Domain Crash

    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 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 53: Error Messages From The Ultra320 Scsi Card

    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.
  • Page 54: A Built-In Fan May Be Erroneously Detected As A Failure (Cr 6636098)

    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...
  • Page 55: 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)

    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> showplatform SUNW,SPARC-Enterprise-T5120 Domain Status ------ ------ Powered off * Domain Status : "Powered on", "Powered off", "OpenBoot initializing", "Unknown"...
  • Page 56: For Dc Input Power Models, /Ps0/Ac_Pok Is Displayed (Cr 6815369)

    : "ID = 1cf0 : 02/06/2009 : 04:00:59 : Power Supply : /PS0/DC_POK : State Asserted" IPMI |minor : "ID = 1cf1 : 02/06/2009 : 04:00:59 : Power Supply : /PS0/FAIL : State Deasserted" Workaround: None SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 57: 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 (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.
  • Page 58: In The Logical Domains Environment, After The Host Reset Operation, Host May Be Reset Again (Cr 6836426)

    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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 59: The Ilom Network Configuration Cannot Be Set (Cr 6835854, 6779753)

    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: ->...
  • Page 60: An Error Is Registered With The Showfaults Command When Running Post, But Post Ends Normally (Cr 11210193)

    SP detected fault: Fault Sensor VCORE_POK at /SYS/MB deasserted sc> Workaround: None. If this problem occurs, use the resetsc ALOM CMT compatibility command to clear the log and reset the LED display. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 61: The Ok Prompt Is Not Displayed After Post Ends (Cr 11215994)

    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: Chassis | major: Host has been powered on 0:0:0> 0:0:0>SPARC-Enterprise[TM] T5120/T5220 POST 4.30.6 2009/12/01 13:08 Chapter 3 Known Issues...
  • Page 62 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 63 1. Turn off the power to the system. - Power-off operation example - [In case of ALOM CMT compatible shell] sc> poweroff -y [In case of ILOM mode] -> stop -script /SYS 2. Wait for 180 or more seconds. 3. Remove the power cord. 4.
  • Page 64: 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 general Solaris OS late-breaking issues are described in the Solaris 10 Release Notes.
  • Page 65 This issue does not occur with the virtual- console. The output of the raidctl -h command and The SPARC Enterprise T5120 and T5220 servers the raidctl man page display some currently only support RAID 0 and RAID 1 for unsupported features.
  • Page 66 = 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 /Partner_Part_NumberR/Partner_Part_Nu mber: CF005413513REVxx SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 67: Sun Explorer May Fail To Collect The Ilom Data (Tx000) (Cr 6718841)

    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.
  • Page 68: Notes On Installing 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 69 The procedure is shown below. 1. Create an install image on the install server. Example: This example assumes the DVD medium has been mounted to '/cdmnt'. # 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"...
  • Page 70: Ldoms Related Issues

    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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 71: Documentation Errata

    C H A P T E R 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 ■...
  • Page 72 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.
  • Page 73 2. If the server is installed at a level between 21U and 40U (*1): (*1 Judged based on the level of the equipment top) Rear-side clearance for service access 800mm Equipment rack 1050mm Front-side clearance for service access 1300mm 1400mm 800mm 700mm 1400mm...
  • Page 74: Incorrect Values For The 1.6 Ghz Specjbb Test

    8 core, 1.6 GHz processor, with sixteen 4 GB FBDIMMs, 16 HDDs, 6 PCIe 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 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 75: Incorrect Idle Input Power Values

    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 PCIe I/O cards...
  • Page 76: Sparc Enterprise T5120 And T5220 Servers Installation Guide

    XAUI cards, open it and verify that 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 PCIe/XAUI cards and their risers as well as information about internal cable routing.
  • Page 77 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 the hard drive data cable. d. Route the hard drive data cable over the fan module and along the air duct.
  • Page 78: Erroneous Description In "Fan Module Configurations For Sparc Enterprise T5220 Servers (8- And 16-Disk Capable)

    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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 79: Incorrect Fru Name Is Specified In The Table: Motherboard Components (Sparc Enterprise T5220 Servers)

    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.
  • Page 80: 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.
  • Page 81: Integrated Lights Out Manager (Ilom) 3.0 Cli Procedures Guide

    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...
  • Page 82: Erroneous Description About Collecting Sp 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 83: And T5220 Servers

    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.
  • Page 84 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 85: Fixed Issues

    A P P E N D I X 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.
  • Page 86: L2 Cache Errors Might Generate An Erroneous Memory Fault (Cr 6592272)

    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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 87: Ethernet Interface Related Issues

    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. Ethernet Interface Related Issues TABLE A-2 lists the Ethernet related issues that have been fixed. Fixed Ethernet Related Issues TABLE A-2 Description Workaround...
  • Page 88: Using Modunload While The Nxge Port Is Running, Could Cause A System Panic (Cr 6551509)

    It is very unlikely that this condition will occur in normal circumstances. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 89: To Unplumb The Interfaces Prior To Unloading The Driver

    The panic message is mutex_enter: bad mutex, ... The panic stack will include the two nxge driver functions nxge_freeb() and nxge_post_page(). If such a panic occurs, the system will recover, and continue to reboot normally. The system, including the nxge interfaces, will come back up with no further panics. Workaround: Unplumb the interfaces prior to unloading the driver.
  • Page 90 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 91: To Set The Mtu Size To

    ▼ 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-port1 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.
  • Page 92: Setting Properties For Nxge Devices Might Fail (Cr 6561389)

    To Disable Jumbo Frames Disabling Jumbo Frames or using Jumbo Frames with a smaller MTU impacts system performance. Only perform the following steps if the system panics due to Jumbo Frames. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 93: To Set The Mtu To A Smaller Size

    1. Edit the /platform/sun4v/kernel/drv/nxge.conf file, and ensure that any line with accept_jumbo=1; is commented out. 2. Ensure that there is no set nxge:nxge_jumbo_enable=1 in the /etc/system file. ▼ 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.
  • Page 94: Firmware, Ilom, Post, And Sp Issues

    ALOM CMT compatibility CLI): sc> poweroff -fy sc> clearasrdb sc> poweron -c You can also update the System Firmware to the latest version to avoid encountering this issue. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 95 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 Servers for details.
  • Page 96 SSH connection to the SP. reset: Transport error - check errno for You can also update the System Firmware to the transport error latest version to avoid encountering this issue. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 97 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.
  • Page 98 ILOM CLI to hang and become unresponsive. 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 99 Fixed Firmware, ILOM, POST, and SP Issues (Continued) TABLE A-3 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.
  • Page 100 Identify and replace the faulty DIMM module. output to the console. For an example of the message, see “MCU Might Be Disconnected in DIMM Module Failure (CR 6656116)” on page 106. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 101 Fixed Firmware, ILOM, POST, and SP Issues (Continued) TABLE A-3 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 object is Clear the error by using the FRU name provided set to true, but no processing is executed: by the show /SP/faultmgmt command.
  • Page 102 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 103 Fixed Firmware, ILOM, POST, and SP Issues (Continued) TABLE A-3 Description Workaround 6802433 For DC input power models, the INPUT limit Note - Fixed in System Firmware 7.2.2.e or later. value included in the output from the None. Ignore this issue because it is only a display showpower -v command may differ between error.
  • Page 104 FRUs, and cannot be faulted and clear_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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 105 Fixed Firmware, ILOM, POST, and SP Issues (Continued) TABLE A-3 Description Workaround 6694475 It is 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 information will be displayed regardless of the option specified.
  • Page 106 "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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 107 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 64 8-Gbyte FB-DIMMS Chassis | major: Jul 27 16:40:17 ERROR: dt_allocprop: prop == NULL:...
  • Page 108 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 None. to the default value (none). SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 109 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. prtdiag command of Solaris OS, the From ILOM, check the component information "Environmental Status" and some part of and the status of fan, temperature, power sensor the "FRU Status"...
  • Page 110: Sp Serial Line Terminal Server Break Command Does Not Work (Cr 6577528)

    1. Log into the host with the ILOM console command. -> start /SP/console Are you sure you want to start /SP/console (y/n)? y Serial console started. To stop, type #. Solaris-host-prompt> SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 111: The Showfaults Command Shows The Motherboard As Faulty Instead Of The Dimm (Cr 6582853)

    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.
  • Page 112: The Uadmin 2 0 And Reboot Commands Read Old Bootmode Settings (Cr 6585340)

    You can change LDoms variables in the control domain in one of three ways, with the OpenBoot setenv command in the control domain, with the Solaris eeprom command in the control domain, or using ILOM bootmode bootscript option. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 113: Domain Etm And Ldc Deadlock When Transmit Queue Full (Cr 6594506)

    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.
  • Page 114 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 115 Workaround: After the domain recovers and the diagnosis message is printed to the Solaris console, reset the service processor: sc> resetsc -y [ALOM CMT compatibility CLI] -> 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...
  • Page 116: Spurious Piu Errors (Cr 6598381)

    3e 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 __ttl = 0x0 __tod = 0x46d2da57 0x1d998280 These events are harmless and can be ignored. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 117: Diagnostic Routine That Runs At Startup (Ibist) Might Accidentally Disconnect The Mcu (Cr 6618773)

    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,...
  • Page 118: Mcu Might Be Disconnected In Dimm Module Failure (Cr 6656116)

    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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 119: 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)

    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"...
  • Page 120 For example: {0} ok probe-scsi-all /pci@0/pci@0/pci@2/scsi@0 (Omitted.) Target 8 Unit 0 Disk SEAGATE ST914602SSUN146G0603 286739329 Blocks, 146 GB SASAddress 5000c5000b36a225 PhyNum 8 (Omitted.) SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 121: For Dc Input Power Models, The Output From The Showpower -V Command May Differ Between /Sys/Ps0 And /Sys/Ps1 (Cr 6802433)

    For DC Input Power Models, the Output From the showpower -v Command May Differ Between /SYS/PS0 And /SYS/PS1 (CR 6802433) This issue is resolved by updating the system firmware 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/PS0 and /SYS/PS1.
  • Page 122: In The Output From The Prtdiag Command, Warnings May Be Displayed (Cr 6821325)

    V_VMEML SYS/MB V_VMEMR SYS/MB V_VBAT SYS/PS0 V_IN_MAIN warning (-48volts) SYS/PS0 V_OUT_MAIN SYS/PS1 V_IN_MAIN warning (-48volts) SYS/PS1 V_OUT_MAIN Workaround: None. Ignore this issue because it is only a display error. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 123: During The Power-On Self-Test, The Diagnostic Process May Terminate Halfway (Cr 6835860)

    "ERROR:POST timed out" message may appear and the diagnostic process may terminate halfway. Example: sc> poweron -c Enter #. to return to ALOM. Chassis | major: Host has been powered on 0:0:0> 0:0:0>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>Copyright 2009 Sun Microsystems, Inc. All rights reserved 0:0:0>POST enabling CMP 0 threads: ffffffff.ffffffff...
  • Page 124: 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"...
  • Page 125: When The Service Processor Is Initialized, Ilom May Fails To Start With An Error Message Displayed (Cr 6856163)

    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 a failure to start an ILOM internal process.
  • Page 126 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 127: After The Scc Module Replacement, A Connection To The Ilom Network May Fail (Cr 6857271)

    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 replacement, part (*1) of the data kept on the motherboard is inadvertently overwritten with new SCC module data (*2).
  • Page 128: Solaris Os Issues

    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 encountering this issue. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 129 Fixed Solaris OS Issues (Continued) TABLE A-4 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.
  • Page 130 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 131 Fixed Solaris OS Issues (Continued) TABLE A-4 Description Workaround 6589612 The raidctl -l 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 ID 127127-11 or later installed. # raidctl -l Controller: 1 Use the Control-C keyboard sequence to stop the...
  • Page 132: Servers Might Experience Panics Generated From The Pcie Root Complex (Cr 6555956)

    The panic only occurs during a reboot and has never been observed during a reboot that follows the panic. The panic can occur even if no external USB devices are connected to the server. Workarounds: SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 133: Information Missing From Prtpicl And Prtdiag Commands (Cr 6586624)

    If your server experiences this panic, perform one or more of the following workarounds: 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: Using the ILOM CLI: ■...
  • Page 134: Booting The Solaris Os From An External Usb Dvd-Rom Drive Could Cause A Panic (Cr 6588452)

    Both the OpenBoot firmware and Solaris OS follow the 1275 USB bindings rules to name nodes. For example: 1275 USB Bindings Rules for Naming Nodes TABLE : bInterface Class bInterface Subclass bInterface Protocol Name 0x08 storage 0x08 cdrom 0x08 tape 0x08 floppy SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 135: The Prtdiag -V Command Has Formatting Issues (Cr 6587389)

    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.
  • Page 136: Psh Events Are No Longer Transported (Cr 6594506)

    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: <Unknown?> (228d74) - PowerDown SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 137 This issue is resolved with Solaris patch ID 124630-32 or later. During a period extending from 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”...
  • Page 138 6. Set and export the NOINUSE_CHECK variable to allow the format command full access to the boot drive. 7. Run the format utility to restore the drive’s “type”. 8. Use the fmthard command and stored information to complete the recovery. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 139 9. Verify the success of the recovery. Procedure for Recovering a Boot Drive”s “drive type” CODE EXAMPLE A-1 1. 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/c0t0d0s0 - / ufs - no rw,intr,largefiles,logging,xattr,onerror= panic root@host-1 # format c0t0d0s0 <========== boot device determined previously...
  • Page 140 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". SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 141 Procedure for Recovering a Boot Drive”s “drive type” CODE EXAMPLE A-1 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): <====== login single user mode single-user privilege assigned to /dev/console. Entering System Maintenance Mode Oct 20 18:06:11 su: ’...
  • Page 142 - set 8-character volume name The jumpstart install process !<cmd> - execute <cmd>, then return quit format> label Ready to label disk, continue? y format> quit root@ # SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 143 Procedure for Recovering a Boot Drive”s “drive type” CODE EXAMPLE A-1 8. Use the fmthard command and stored information to complete the recovery. root@ # /tmp/fmthard -s /tmp/vtoc /dev/rdsk/c0t0d0s0 <=== raw boot device used to capture vtoc. fmthard: New volume table of contents now in place. root@ # 9.
  • Page 144 - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name The jumpstart install process !<cmd> - execute <cmd>, then return quit format> disk SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 145 Procedure for Recovering a Boot Drive”s “drive type” CODE EXAMPLE A-1 AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0/pci@0/pci@2/scsi@0/sd@0,0 Specify disk (enter its number)[0]: selecting c0t0d0 [disk formatted] format> quit The drive type recovery is complete, reboot the server: root@ # reboot syncing file systems...
  • Page 146 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 the future. third-party systems monitoring tools if they monitor this entry. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...
  • Page 147 Fixed LDoms Related Issues (Continued) TABLE A-5 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.
  • Page 148 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. SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010...

This manual is also suitable for:

Sparc enterprise t5220