Fujitsu SPARC Enterprise T5140 Product Notes
  1. Manuals
  2. Brands
  3. Fujitsu Manuals
  4. Server
  5. SPARC Enterprise T5140
  6. Product notes
Fujitsu SPARC Enterprise T5140 Product Notes

Fujitsu SPARC Enterprise T5140 Product Notes

Sparc enterprise
Hide thumbs Also See for SPARC Enterprise T5140:
Table of Contents

Quick Links

See also: Administration Manual, Service Manual
SPARC Enterprise
T5140 and T5240 Servers
Product Notes
Manual Code C120-E493-17EN
Part No.: 875-4318-26
November 2012, Revision A
Table of Contents
loading

Related Manuals for Fujitsu SPARC Enterprise T5140

Summary of Contents for Fujitsu SPARC Enterprise T5140

  • Page 1 SPARC Enterprise T5140 and T5240 Servers Product Notes Manual Code C120-E493-17EN Part No.: 875-4318-26 November 2012, Revision A...
  • Page 2 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 Oracle or Fujitsu Limited, and/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.
  • Page 3 Aucune partie de ce produit, de ces technologies ou de ce document ne peut être reproduite sous quelque forme que ce soit, par quelque moyen que ce soit, sans l’autorisation écrite préalable d’Oracle et/ou ses sociétés affiliées et de Fujitsu Limited, et de leurs éventuels bailleurs de licence. Ce document, bien qu’il vous ait été...

  • Page 5: Table Of Contents

    Contents Preface ix New Information About the SPARC Enterprise T5140 and T5240 Servers 1 Important New Information About the SPARC Enterprise T5140 and T5240 Servers 1 New Information About Known Issues 2 Hardware and Mechanical Issues 2 Solaris OS Issues 2...
  • Page 6 Updating LSI 1068e Controller Firmware to Support SSDs 19 RFID Tag 20 Changed Behavior When Operating the Solaris OS With Logical Domains 21 Results from Halting or Rebooting the Control Domain 21 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 7 SPARC Enterprise T5140 and T5240 Servers Administration Guide 55 Integrated Lights Out Manager 2.0 User's Guide 56 Integrated Lights Out Manager 2.0 Supplement for SPARC Enterprise T5140 and T5240 Servers 57 Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide 58 Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide 60...
  • Page 8 Fixed in System Firmware 7.1.6.d or Later 113 Fixed in System Firmware 7.1.3.d or Later 114 Fixed in Other Software 118 Minor Cases 119 Firmware and General Software Events 119 viii SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 9: Preface

    SPARC Enterprise T5140 and T5240 servers. http://www.fujitsu.com/sparcenterprise/manual/ Downloading Documentation The documentation set of SPARC Enterprise T5140 and T5240 servers is available on the following web site. Global Site ■...

  • Page 10: Documentation Feedback

    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 web site. http://www.fujitsu.com/global/contact/computing/sparce_index.html SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 11: New Information About The Sparc Enterprise T5140 And T5240 Servers

    Enterprise T5140 and T5240 Servers This chapter describes new information about the SPARC Enterprise T5140 and T5240 servers that was not documented in the previous edition of the SPARC Enterprise T5140 and T5240 Servers Product Notes. “Important New Information About the SPARC Enterprise T5140 and T5240 Servers” on ■...

  • Page 12: New Information About Known Issues

    There is no technical issue that were identified after the previous edition of this document was published. New Information About Documentation Errata There is no documentation errata that were identified after the previous edition of this document was published. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 13: Important Information About The Sparc Enterprise T5140 And T5240 Servers

    C H A PT E R Important Information About the SPARC Enterprise T5140 and T5240 Servers This chapter contains important information about the SPARC Enterprise T5140 and T5240 servers. The following sections are included: “Notes on DVD Drive and Discs” on page 3 ■...

  • Page 14: Supported Versions Of Solaris Os And System 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 T5140 and T5240 Servers Product Notes • November 2012...

  • Page 15: Solaris Os And Firmware Requirements For Certain Features

    † Oracle VM Server for SPARC * Follow all of the system memory configuration rules and restrictions defined in the SPARC Enterprise T5140 and T5240 Servers Service Manual. † Formerly, Oracle VM Server for SPARC was called Logical Domains or LDoms. For minimum firmware version, minimum OS version, and mandatory patches when using Oracle VM Server for SPARC software, see the SPARC Enterprise Oracle VM Server for SPARC Important Information.

  • Page 16: System Firmware Update

    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 T5140 and T5240 Servers Installation Guide for more information about updating the system firmware. Support for Windows 7 and Internet Explorer 8 As of System Firmware 7.2.7, the Remote Console feature in ILOM supports Microsoft...

  • Page 17: Addition Of Protocols For Firmware Update

    ILOM is reset. Are you sure you want to load the specified file (y/n)? y Do you want to preserve the configuration (y/n)? y ........................Chapter 2 Important Information About the SPARC Enterprise T5140 and T5240 Servers...

  • Page 18: Preinstalled Software

    The ABE enables you to upgrade the Solaris OS or perform system maintenance tasks without reducing performance. An identical (bootable) copy of the root partition (including the Solaris OS, EIS, and applications) is installed as an ABE in Slice 3. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 19: Logical Domains

    Supported Sun Explorer Utility Version The SPARC Enterprise T5140 and T5240 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...

  • Page 20: Patch Information

    Note – The patches on the CD include an updated network driver that is required to enable use of the network interfaces on the SPARC Enterprise T5140 and T5240 servers. After installing the Solaris 10 8/07 OS and the patches, network interfaces will remain unconfigured.

  • Page 21: Mandatory Patch Information For The Solaris 10 8/07 Os

    138048-01 or later nxge patch Mandatory Patch Information For the Solaris 10 10/08 There are no mandatory patches for the Solaris 10 10/08 OS at this time. Chapter 2 Important Information About the SPARC Enterprise T5140 and T5240 Servers...

  • Page 22: Mandatory Patch Information For The Solaris 10 5/09 Os

    Installing the Fujitsu 4Gbps Fibre Channel Card Once you install the Fujitsu 4Gbps Fibre Channel card (SE0X7F11X, SE0X7F12X), the patch indicated below is required. For the information on how to get the patch releases, contact your sales representative. For the installation instructions, see the README file included in the patch.
  • Page 23 Optional cards Single-channel 4Gbps Fibre Channel card (SE0X7F11X) ■ Dual-channel 4Gbps Fibre Channel card (SE0X7F12X) ■ Required patch FUJITSU PCI Fibre Channel 4.0: 914583-04 or later ■ Chapter 2 Important Information About the SPARC Enterprise T5140 and T5240 Servers...

  • Page 24: Notes And Limitations

    17 or later. Hardware RAID Function The SPARC Enterprise T5140 and T5240 servers are equipped with a hardware RAID function by default, and this section shows the support conditions and the points of concern. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 25 If there is a system restart during the RAID build or synchronization, the ■ build/synchronization must be started again from the beginning. When the RAID applied, the volume size is smaller than the size of original disk. ■ Chapter 2 Important Information About the SPARC Enterprise T5140 and T5240 Servers...

  • Page 26: Cable Management Arm

    -C -z Cable Management Arm The SPARC Enterprise T5140 server doesn't support the cable management arm (CMA). The following restrictions apply when using a CMA on SPARC Enterprise T5240 server: The maximum capacity of the CMA is as follows: ■...

  • Page 27: Express Rail Rackmounting Kit

    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 T5140 and T5240 servers varies depending on the maximum number of HDDs installed in the servers. For...

  • Page 28: Using A Ssd As A Boot Device

    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. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 29: Updating Lsi 1068E Controller Firmware To Support Ssds

    Depending on the firmware version of your server, you may need to update the controller firmware. Controller Firmware updates are provided as patch releases. For the information on how to get the patch releases, contact your sales representative. Chapter 2 Important Information About the SPARC Enterprise T5140 and T5240 Servers...

  • Page 30: Rfid Tag

    FIGURE 2-2 RFID Tag FIGURE 2-3 shows the appearance of RFID tag. RFID Tag Appearance FIGURE 2-3 Serial Number of the server Asset ID written in the RFID tag SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 31: Changed Behavior When Operating The Solaris Os With Logical Domains

    Reboots the host, no power off. reboot Reboots the host, no power off. Host powered off, stays off until powered on at the SP. shutdown –i 5 Resets and reboots. Chapter 2 Important Information About the SPARC Enterprise T5140 and T5240 Servers...

  • Page 32: Notes On Processor Identification

    The plug with lock function 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 T5140 and T5240 Servers Product Notes • November 2012...

  • Page 33: Notes On Using Oracle Solaris 11 Os

    : Close Session : object = "/SP/session/type" : value = "shell" : success 3191 Mon Nov 7 15:36:42 2011 Audit minor root : Open Session : object = "/SP/session/type" : value = "shell" : success Chapter 2 Important Information About the SPARC Enterprise T5140 and T5240 Servers...
  • Page 34 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 35: Known Issues

    C H A PT E R Known Issues This chapter describes known issues about the SPARC Enterprise T5140 and T5240 servers. The following sections are included in this chapter: “Hardware and Mechanical Issues” on page 25 ■ “Solaris OS Issues” on page 33 ■...
  • Page 36 This behavior is normal and can be ignored. Onboard Ethernet Port The onboard Ethernet port of the SPARC Enterprise T5140/T5240 does not support half duplex transfer at any of the speeds of 10M/100M/1000M. Therefore, connect it to a switch/hub that supports full duplex transfer.
  • Page 37 Hardware and Mechanical Issues TABLE 3-1 CR ID Description Workaround 6901327 In Solaris 10 10/09, after the RAID 1 build, label 1. Start the Solaris OS with single user mode, or from information may fail to be written correctly. the SunInstaller. When booting from the SunInstaller, terminate the SunInstaller once.
  • Page 38 RJ45 cable connector tab depressed, such as with a mounted in the SPARC Enterprise T5140 server. plastic card. XAUI card disables an On-board network port. For details, see “XAUI Card Disables an Onboard Network Port” on page SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 39 Note -- This error appears on all SPARC Enterprise an error. It says to press and hold the On/Standby T5140 and T5240 server configurations. button for "5 seconds". It should say "4 seconds". Two illustrations in the service label show the top Note -- This error appears on all SPARC Enterprise cover button in the wrong location.
  • Page 40 | Jun 10 13:09:25 /SP/faultmgmt/1/ | timestamp | Jun 10 13:09:25 faults/0 /SP/faultmgmt/1/ | sp_detected_fault | /SYS/MB/GBE Forced fail (POST) faults/0 |* The built-in Ethernet port is faulty. Workaround: None. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 41 Recovery procedure: Replace the XAUI card by using the following procedure: [Using ILOM command mode] 1. Execute stop /SYS. 2. Delete the XAUI and GBE components from the asr-db blacklist. Execution example: -> set /SYS/MB/RISER1/XAUI1 component_state=enabled -> set /SYS/MB/GBE component_state=enabled 3.
  • Page 42 NET0 NET1 NET2 NET3 =2U device only Network Ports and Device Names TABLE 3-2 On-board network XAUI Slot Device name NET 0 XAUI 1 nxge0 NET 1 XAUI 0 nxge1 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 43: Solaris Os Issues

    Encode devid failed for path target:##, lun:#, SAS address:################ In SPARC Enterprise T5140 and T5240 servers, This message shows that interrupt without the reason when rebooting is repeatedly executed, the following was detected when su (serial port) driver processes WARNING messages might be stored in interrupt.
  • Page 44 Recovery CD attached to the server and apply the patches to the install image. # LANG=C;export LANG # cd /export/home/dvd # patchadd -C ./Solaris_10/Tools/Boot /cdmnt/Solaris_10/Patches/125369* # patchadd -C ./Solaris_10/Tools/Boot /cdmnt/Solaris_10/Patches/125476* # patchadd -C ./Solaris_10/Tools/Boot /cdmnt/Solaris_10/Patches/127111* SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 45 # cp -R /cdmnt/Solaris_10/Patches/* Solaris_10/Patches # ls Solaris_10/Patches 124235-02 125369-13 125416-06 125476-02 126434-05 127111-08 3. Install the Solaris OS from the install server. 4. Apply the latest periodic PTF and the latest recommended security patches. The mandatory patches which are described in the “Patch Information”...

  • Page 46: Firmware And General Software Issues

    To recover from this event, reset ILOM. change it from enabled to disabled, you may fail in restarting the ILOM Web service. When this event occurred, it becomes unable to connect to BUI of ILOM. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 47 | Value -----------+--------------+------------- -> 7020694 In SPARC Enterprise T5140 server equipped with Use the ILOM show /SYS/PDB command to view System Firmware 7.3.0.c or earlier and power the part number of the power distribution board on distribution boards with part number CF00511-1604, your server.
  • Page 48 When the host is powered off, the value of ambient None. temperature sensor (MB/T_AMB) is not correctly This issue can be ignored. displayed in the output of showenvironment command. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 49 Firmware and General Software Issues (Continued) TABLE 3-4 CR ID Description Workaround 6849287 When powering on the system, there may be an None. output message to show that the memory sensor This is not a problem as far as the value has been (VMEMR/VMEML) or the CPU core sensor restored to normal after detected the message of an (VCORER/VCOREL) detected an excess of the...
  • Page 50 "https" to the protocol for Use other protocols (tftp, ftp, sftp, scp, http). data transfer (transfer_method property). Example: -> set dump_uri= https://ipaddres/directory/filename set: Unable to transfer image, please check URI SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 51 Firmware and General Software Issues (Continued) TABLE 3-4 CR ID Description Workaround 6591634 During OpenBoot PROM at the system start, when To recover this event, power off and then power on you execute a forced dump order from ILOM, a the system.
  • Page 52 ILOM firmware updates, the update may fail with the ILOM firmware update again. the following output message. Example of update failure # ./sysfwdownload Sun_System_Firmware- 7_1_3_d-SPARC_Enterprise_T5120+T5220.pkg sysfwdownload: send/receive failed(2) - "ret = -7" SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 53 SSH (Secure Shell) fails. It is already confirmed that this event can be avoided using the switching hub manufactured by Fujitsu. Perform the ILOM reset operation. The prtdiag Command Doesn't Show the Correct Memory Configuration in the Output, in the...
  • Page 54 MB/CMP0/BR1/CH0/D0 MB/CMP0/BR1/CH1/D0 256 MB MB/CMP0/BR0/CH0/D1 MB/CMP0/BR0/CH1/D1 256 MB MB/CMP0/BR1/CH0/D1 MB/CMP0/BR1/CH1/D1 0x940000000 1 GB 256 MB MB/CMP0/BR0/CH0/D0 MB/CMP0/BR0/CH1/D0 256 MB MB/CMP0/BR1/CH0/D0 MB/CMP0/BR1/CH1/D0 256 MB MB/CMP0/BR0/CH0/D1 MB/CMP0/BR0/CH1/D1 256 MB MB/CMP0/BR1/CH0/D1 MB/CMP0/BR1/CH1/D1 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 55: Oracle Vm Server For Sparc Issues

    Workaround: None. Please check that the memory size is equal to the mounted memory size. Oracle VM Server for SPARC Issues For the issues about Oracle VM Server for SPARC (Formerly, called Logical Domains of LDoms), see the SPARC Enterprise Oracle VM Server for SPARC Important Information. Chapter 3 Known Issues...
  • Page 56 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 57: Documentation Errata

    C H A PT E R Documentation Errata This chapter describes known errors and corrections to the SPARC Enterprise T5140 and T5240 server documentation. “SPARC Enterprise T5140 and T5240 Servers Site Planning Guide” on page 47 ■ “SPARC Enterprise T5140 and T5240 Servers Installation Guide” on page 52 ■...
  • Page 58 The SPARC Enterprise T5140 and T5240 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 59 Incorrect Operating Input Voltage Range for DC Input Models The Power Source Requirements section of the SPARC Enterprise T5140 and T5240 Site Planning Guide contains tables that identify power specifications for various server configurations. The operating input voltage range for DC input models indicated in each table is incorrect.
  • Page 60 Incorrect Values for Idle Input Power Requirements in Minimum Server Configurations The Power Source Requirements section of the SPARC Enterprise T5140 and T5240 Site Planning Guide contains tables that identify power specifications for various server configurations. These specifications include values for idle power use in minimum server configurations.
  • Page 61 Incorrect Operating Input Voltage Values for the 1.4 GHz, 8-Disk Configuration The table that describes input power requirements for the SPARC Enterprise T5240 server configuration with 1.4 GHz CPUs and an 8-disk capable backplane states the wrong operating input voltage value in two places. The following table describes the necessary correction.

  • Page 62: Sparc Enterprise T5140 And T5240 Servers Installation Guide

    PCIe 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. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 63: Sparc Enterprise T5140 And T5240 Servers Service Manual

    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 T5140 and T5240 Servers Service Manual for information about the PCIe/XAUI cards and their risers as well as information about internal cable routing.
  • Page 64 Enterprise T5240 Servers) Fan Module Missing in Data Cable Routing Diagram The cable routing diagram for 8-disk capable backplanes in T5140 systems is missing a fan module in the upper right corner. This is the correct diagram: SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 65: Sparc Enterprise T5140 And T5240 Servers Administration Guide

    Internal Cables for the Onboard SAS Controller Card (Eight-Disk Capable SPARC FIGURE 4-3 Enterprise T5140 Servers) SPARC Enterprise T5140 and T5240 Servers Administration Guide Incorrect Description in "Devices and Device Identifiers" (CR 6712561) DB9 serial port, /SYS/TTYA, is indicated in "Devices and Device Identifiers" on page 38, but the /SYS/TTYA can not be unconfigured.

  • Page 66: Integrated Lights Out Manager 2.0 User's Guide

    The ILOM commands indicated on page 23 and page 28 include erroneous information. setpendingipdiscovery= should be set pendingipdiscovery=. Incorrect Command in the Section "Edit an SNMP User Account Using the CLI" The following command described on page 195 is incorrect. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 67: Servers

    T5240 Servers Notes on the Connection of ILOM (CR 6806789) On the SPARC Enterprise T5140 and T5240 servers, ILOM supports a maximum of 5 active sessions, including serial, Secure Shell (SSH), and web interface sessions. Complement to the Description Regarding Diagnostics Trigger In "Specify Diagnostic Trigger Conditions Using the CLI,"...

  • Page 68: Integrated Lights Out Manager (Ilom) 3.0 Cli Procedures Guide

    The directory data is relative 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. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 69: Erroneous Description About Collecting Sp Data

    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 Specifies that all data is to be collected ("full" collection). full Note - Using this option may reset the running host.

  • Page 70: Integrated Lights Out Manager (Ilom) 3.0 Web Interface Procedures Guide

    While the host is executing, you can specify the full option. Notes on Downloading System Firmware For the information on how to get the patch releases, contact your sales representative. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 71: T5240 Servers

    Integrated Lights Out Manager (ILOM) 3.0 Supplement for SPARC Enterprise T5140 and T5240 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 72 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 73: Fixed Issues

    A P P E N D I X Fixed Issues This appendix describes the fixed issues concerning the SPARC Enterprise T5140 and T5240 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 74 8x 1-GB DIMMs 16x 8-GB DIMMs 16 GB 128 GB 16x 1-GB DIMMs 16x 8-GB DIMMs Workaround: Assign memory resources in configurations that avoid the combinations shown in TABLE A-1. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 75: Solaris Os Issues

    Solaris OS Issues TABLE A-2 lists the Solaris OS issues that have been fixed. Fixed Solaris OS Issues TABLE A-2 CR ID Description Workaround 6886514 Boot drive may report "drive type unknown" Note - Fixed in Solaris patch ID 124630-32 or for Solaris format command.
  • Page 76 The change will take effect after the domain reboots. 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. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 77 During a period extending from mid-September to early October 2009 (approximately 3 weeks) a patch was preinstalled on some SPARC Enterprise T5140 and T5240 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.
  • Page 78 Copyright 2009 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.30.4, 3968 MB memory available, Serial #xxxxxxxx. Ethernet address xx: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 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 79 Procedure for Recovering a Boot Drive's "drive type" (Continued) CODE EXAMPLE A-1 milestone=none Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Booting to milestone "none". 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...
  • Page 80 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@ # SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 81 Procedure for Recovering a Boot Drive's "drive type" (Continued) CODE EXAMPLE A-1 9. Verify the success of the recovery. root@ # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@0/pci@0/pci@2/scsi@0/sd@0,0 Specify disk (enter its number): 0 selecting c0t0d0 [disk formatted]...
  • Page 82 0. c0t0d0 /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 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 83 Procedure for Recovering a Boot Drive's "drive type" (Continued) CODE EXAMPLE A-1 syncing file systems... done rebooting... Resetting... SPARC Enterprise T5240, No Keyboard Copyright 2009 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.30.4, 3968 MB memory available, Serial #xxxxxxxx. Ethernet address xx:xx:xx:xx:xx:xx, Host ID: xxxxxxxx. Boot 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.

  • Page 84: Firmware And General Software Issues

    “Fixed in System Firmware 7.1.6.d or Later” on page 113 ■ “Fixed in System Firmware 7.1.3.d or Later” on page 114 ■ “Fixed in Other Software” on page 118 ■ SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 85: Fixed In System Firmware 7.4.2 Or Later

    Fixed in System Firmware 7.4.2 or Later Issues Fixed in System Firmware 7.4.2 or Later TABLE A-3 CR ID Description Workaround 7020953 In System Firmware 7.3.0.c or later, when Solaris OS Note - Fixed in System Firmware 7.4.2 or later. is started, the FMA message of SUN4V-8002-SP None.
  • Page 86 ILOM set time before you remove and insert the power cord and start and the Solaris OS startup time may become the Solaris OS. inaccurate. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 87 Service Required LED May Turn On Due To False Recognition of Fan Speed (CR 6989852) This issue is resolved by updating the system firmware to 7.3.0.c or later. ILOM firmware falsely recognizes the fan speed as "0" and the Service Required LED may turn on.
  • Page 88 Jul 23 15:19:02 xxxxxxx SC Alert: [ID 935808 daemon.error] SC unretrieved msg: [Chassis | major: V_IN_MAIN at /SYS/PS0 has reached low warning threshold.] In the prtdiag -v command execution result, warning will be displayed as follows. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 89 Message example: Chassis | major: Host has been powered on 0:0:0> 0:0:0>SPARC-Enterprise[TM] T5140/T5240 POST 4.30.6 2009/12/01 13:08 /export/delivery/delivery/4.30/4.30.6/post4.30.6-micro/Niagara/huron/integrated (root) 0:0:0>Copyright 2009 Sun Microsystems, Inc. All rights reserved...
  • Page 90 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 T5140 and T5240 Servers Product Notes • November 2012...

  • Page 91: Fixed In System Firmware 7.2.10.A Or Later

    1. Turn off the power to the system. Power-off operation example: [Using ALOM CMT compatible shell] sc> poweroff -y [Using ILOM command mode] -> stop -script /SYS 2. Wait for 180 or more seconds. 3. Remove the power cord. 4. Wait for 180 or more seconds. 5.

  • Page 92: Fixed In System Firmware 7.2.10 Or Later

    Falsely Recognized as F20 Card (CR 6947945)” on For details, see “Fujitsu 4Gbps Fibre Channel Card Is page Falsely Recognized as F20 Card (CR 6947945)” on page SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 93 Issues Fixed in System Firmware 7.2.10 or Later (Continued) TABLE A-6 CR ID Description Workaround 6946636 In the Oracle VM Server for SPARC (the former Note - Fixed in System Firmware 7.2.10 or later. Logical Domains Manager) environment, in such 6908024 After the system stop, disconnect the power cord and occasions as you changed the domain configuration,...
  • Page 94 This issue is resolved by updating the system firmware to 7.2.10 or later. After a PSU failure occurred on the T5140 server, even though you replaced the faulty PSU, the fault indication may not be cleared or the Service Required LED and the [REARPS] LED may remain on.
  • Page 95 [Using ALOM CMT compatible shell] sc> resetsc Are you sure you want to reset the SC [y/n]? y Fujitsu 4Gbps Fibre Channel Card Is Falsely Recognized as F20 Card (CR 6947945) This issue is resolved by updating the system firmware to 7.2.10 or later.
  • Page 96 When you mount a Fujitsu 4Gbps Fibre Channel card and start the system, the 4Gbps Fibre Channel card is falsely recognized as a F20 card in the ILOM CLI interface. Also, the slot number is falsely displayed. In addition, the false recognition and the false display may occur also in the FRU Status of the prtdiag -v command output.
  • Page 97 FIBRE fibre-channel /pci@500/pci@0/pci@9/fibre-channel Slot Number of Link Card Connected to PCI Box Is Falsely Displayed (CR 6942238) This issue is resolved by updating the system firmware to 7.2.10 or later. When you mount a link card connected to PCI box and start the system, the slot number is falsely displayed in the LEDs and FRU Status of the prtdiag -v command output.
  • Page 98 /pci@500/pci@0/pci@c/pci@0/pci@1/pci@0/pci@9/pci@0/FJSV,e2ta@4,1 PCIE5 PCIE FJSV,e4tb-fjgi Broadcom,BCM5715C /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@0/pci@0/pci@2/pci@0 /FJSV,e4tb@4 PCIE5 PCIE FJSV,e4tb-fjgi Broadcom,BCM5715C /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@0/pci@0/pci@2/pci@0 /FJSV,e4tb@4,1 PCIE5 PCIE FJSV,e4tb-fjgi Broadcom,BCM5715C /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@0/pci@0/pci@4/pci@0 /FJSV,e4tb@4 PCIE5 PCIE FJSV,e4tb-fjgi Broadcom,BCM5715C /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@0/pci@0/pci@4/pci@0 /FJSV,e4tb@4,1 PCIE5 PCIE FJSV,e4ta-fjgi Broadcom,BCM5704C SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 99 /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@1/pci@0/FJSV,e4ta@4 PCIE5 PCIE FJSV,e4ta-fjgi Broadcom,BCM5704C /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@1/pci@0/FJSV,e4ta@4,1 PCIE5 PCIE FJSV,e4ta-fjgi Broadcom,BCM5704C /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@1/pci@0,1/FJSV,e4ta@6 PCIE5 PCIE FJSV,e4ta-fjgi Broadcom,BCM5704C /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@1/pci@0,1/FJSV,e4ta@6,1 PCIE5 PCIE FJSV,e2ta-fjgi Broadcom,BCM5715C /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@9/pci@0/FJSV,e2ta@4 PCIE5 PCIE FJSV,e2ta-fjgi Broadcom,BCM5715C /pci@500/pci@0/pci@c/pci@0/pci@9/pci@0/pci@9/pci@0/FJSV,e2ta@4,1 After Updated to System Firmware 7.2.8, a Message Indicating the Presence or Absence of a Component May Be Displayed in the Event Log (CR 6939213) This issue is resolved by updating the system firmware to 7.2.10 or later.
  • Page 100 /SYS/PS0/V_IN_MAIN | upper_critical_thresho | N/A | ld /SYS/PS0/V_IN_MAIN | upper_noncritical_thre | N/A | shold /SYS/PS0/V_IN_MAIN | lower_noncritical_thre | 0.000 Volts | shold /SYS/PS0/V_IN_MAIN | lower_critical_thresho | N/A | ld SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 101 /SYS/PS0/V_IN_MAIN | lower_nonrecov_thresho | N/A | ld /SYS/PS0/V_IN_MAIN | alarm_status | cleared Example of normal display: -> show /SYS/PS0/V_IN_MAIN -o table Target | Property | Value --------------------+-------------------------+--------------- /SYS/PS0/V_IN_MAIN | type | Voltage /SYS/PS0/V_IN_MAIN | ipmi_name | /PS0/V_IN_MAIN /SYS/PS0/V_IN_MAIN | class | Threshold Sensor /SYS/PS0/V_IN_MAIN | value...

  • Page 102: Fixed In System Firmware 7.2.8 Or Later

    (CR 6919764) This issue is resolved by updating the system firmware to 7.2.8 or later. In System Firmware 7.2.7.b, after the power-on of a system mounted with the Fujitsu 4Gbps Fibre Channel card, the message "F20CARD prom is unreadable or corrupted"...

  • Page 103: Fixed In System Firmware 7.2.7.B Or Later

    The ILOM event log example: Tue Apr 6 09:41:17 2010 Fault Fault critical SP detected fault at time Tue Apr 6 09:41:17 2010. /SYS/MB/RISER0/PCIE3/ F20CARD prom is unreadable or corrupted When this event occurred, power off the system and then reset the ILOM. After the reset complete, wait for about 180 seconds and then power on the system.
  • Page 104 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. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 105 Issues Fixed in System Firmware 7.2.7.b or Later (Continued) TABLE A-8 CR ID Description Workaround 6822111 Pressing the FB-DIMM failure locator button on the Note - Fixed in System Firmware 7.2.7.b or later. motherboard in response to a failure of a memory None.
  • Page 106 (*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. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 107 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-BEL07482AU login: root Password: Waiting for daemons to initialize...
  • Page 108 1. Disconnect the power cord. 2. Connect the LAN cable to the ILOM network port. 3. Connect the power cord. 4. Verify that the ILOM network port is linked up. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 109 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 T5140 Server, when you execute the prtdiag command of Solaris OS, the "Environmental Status" and some part of the "FRU Status"...

  • Page 110: Fixed In System Firmware 7.2.2.E Or Later

    /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/PS0 and /SYS/PS1 (CR 6802433)” on page 104. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 111 Issues Fixed in System Firmware 7.2.2.e or Later (Continued) TABLE A-9 CR ID Description Workaround 6801248 For DC input power models, the following event log Note - Fixed in System Firmware 7.2.2.e or later. might be repeatedly collected when the power to the None.
  • Page 112 Note - Fixed in System Firmware 7.2.2.e or later. using "Active directory" on the ILOM Web interface, Log in to ILOM and verify the defaultrole setting the Role field is still blank. in /SP/clients/activedirectory. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 113 Issues Fixed in System Firmware 7.2.2.e or Later (Continued) TABLE A-9 CR ID Description Workaround 6718841 Sun Explorer may fail to collect the ILOM data Note - Fixed in System Firmware 7.2.2.e or later. (Tx000). If failed, it may take more than 30 minutes You can collect the ILOM data (Tx000) in another to return an error.
  • Page 114 Workaround: None. Ignore this issue because it is only a display error. Sun Explorer May Fail to Collect the ILOM Data (Tx000) (CR 6718841) This issue is resolved by updating the system firmware to 7.2.2.e or later. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 115 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.
  • Page 116 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" SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 117: Fixed In System Firmware 7.1.7.F Or Later

    showfaults command output example: 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. Fixed in System Firmware 7.1.7.f or Later Issues Fixed in System Firmware 7.1.7.f or Later TABLE A-10 CR ID...
  • Page 118 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. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 119 Issues Fixed in System Firmware 7.1.7.f or Later (Continued) TABLE A-10 CR ID Description Workaround 6582340 When you are connected to the virtual console and Note - Fixed in System Firmware 7.1.7.f or later. you enter the escape character sequence (#.) to enter If you are refused write access when you initiate a the SP CLI, the following two error messages might connection to the host with the console command,...
  • Page 120 ALOM CLI on the service processor (SP): 1. sc> bootmode config="name_of_config" 2. sc> poweron SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 121 CMP0+MEM0 added up to 128 Gbytes, but the memory on CMP1+MEM1 were only 16 Gbytes. This situation might happen in two different situations; each situation has its own recovery procedure. Case 1 - POST has determined that multiple FBDIMMS have failed on T5140 and T5240 ■ servers with 64 8-Gbyte FB-DIMMS If POST takes a FB-DIMM offline, you must replace it immediately.
  • Page 122 Then, disable the following additional devices: /SYS/MB/MEM1/CMP1/BR0/CH0/D1 /SYS/MB/MEM2/CMP2/BR0/CH0/D1 /SYS/MB/MEM3/CMP3/BR0/CH0/D1 Case 2 - You have added new FB-DIMM modules to T5140 and T5240 servers and have ■ configured one of the CMP/memory module pairs with significantly more memory than the other modules 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.

  • Page 123: Fixed In System Firmware 7.1.6.D Or Later

    None. Example of display from host side: Recovery procedure: Execute recovery by using the following procedure. T5140, No Keyboard If the phenomenon occurs even after executing the Copyright 2008 Sun Microsystems, recovery procedure, the CPU component may be Inc.

  • Page 124: Fixed In System Firmware 7.1.3.D Or Later

    Further, the location of the LSI controller might be reported as MB instead of MB/SASHBA. 6656072 POST failure messages can specify the wrong CPU. Note - Fixed in System Firmware 7.1.3.d or later. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 125 Note - Fixed in System Firmware 7.1.3.d or later. failures can be misleading. The POST error messages XAUI port and slot numbers should match for the can identify the correct port while reporting the SPARC Enterprise T5140 and T5240 servers . Use wrong slot number. the port number.
  • Page 126 FRUs, and cannot be faulted or have clear_fault_action property of /SYS/MB. their fault state cleared. However, if a /SYS/MB/CMPx component fails, that fault_state property of the /SYS/MB target will be updated correctly. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 127 Issues Fixed in System Firmware 7.1.3.d or Later (Continued) TABLE A-12 CR ID Description Workaround 6639002 On systems with PCI-E adapters that have been Note - Fixed in System Firmware 7.1.3.d or later. faulted by Predictive Self-Healing (PSH) diagnosis Use the Fault Management utilities on the host to find on the host, the show faulty command displays the location of the faulty PCI-E adapters.

  • Page 128: Fixed In Other Software

    SunVTS xnetlbtest fails intermittently when run Note - Fixed in SunVTS6.4ps4 or later. in internal loopback mode for longer test durations. Failures occur with this error message: Excessive packets dropped SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

  • Page 129: Minor Cases

    A P P E N D I X Minor Cases This appendix describes the minor cases concerning the SPARC Enterprise T5140 and T5240 servers. Those cases will not be fixed in the future. Firmware and General Software Events TABLE B-1 lists minor events related to the firmware and general software.
  • Page 130 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. SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 131 Firmware and General Software Events (Continued) TABLE B-1 CR ID Description Workaround 6739602 If the logdetail property in If Active Directory 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 Active Directory is set to disabled (state = disabled): sc>...
  • Page 132 In the environment where applied System Firmware 7.2.8 or later, when you restore the ILOM setting and downgrade the firmware version to earlier than 7.2.8, the log output may be limited to part of the past ILOM event log. Event log example: SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 133 There supposed to be logs older than ID 4461, which are not displayed. -> show /SP/logs/event/list /SP/logs/event/list Targets: Properties: Commands: show Date/Time Class Type Severity ----- ------------------------ -------- -------- -------- 4463 Mon Apr 5 06:51:54 2010 Audit minor root : Open Session : object = /session/type : value = shell : success 4462 Mon Apr 5 06:39:11 2010...
  • Page 134 : "ID = 1cef : 02/06/2009 : 04:00:59 : Power Supply : /PS0/AC_POK : State Asserted" <--(*) IPMI |minor : "ID = 1cf0 : 02/06/2009 : 04:00:59 : Power Supply SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 135 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-T5140 Domain Status ------ ------ Powered off * Domain Status : "Powered on", "Powered off", "OpenBoot initializing", "Unknown"...
  • Page 136 Txxxx, No Keyboard Copyright 2010 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.30.7, 7968 MB memory available, Serial #XXXXXXX. Ethernet address XX:XX:XX:XX:XX:XX, Host ID: XXXXXXX. Boot device: disk File and args: SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...
  • Page 137 SunOS Release 5.10 Version Generic_141444-09 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: xxxxxxxx /dev/rdsk/c1t0d0s7 is clean Reading ZFS config: done. xxxxxxxx console login: Workaround: None. This message has no impact on the system and the USB device, and can be safely ignored.
  • Page 138 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012...

This manual is also suitable for:

Sparc enterprise t5240

Table of Contents