t5140t5240 product notes en 06

8/6/2019 T5140T5240 Product Notes en 06

1/118

SPARC EnterprisT5140 and T5240 Serv

Product No

Manual Code C120-E493-06ENPart No. 875-4318-15March 2010, Revision A


2/118

PleaseRecycle

Copyright 2010 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. and FUJITSU LIMITED, 1-1, Kamikod4-chome, Nakahara-ku, Kawasaki-shi, Kanagawa-ken 211-8588, Japan. All rights reserved.

Sun Microsystems, Inc. and Fujitsu Limited each own or control intellectual property rights relating to products and technology describedthis document, and such products, technology and this document are protected by copyright laws, patents and other intellectual propertyand international treaties. The intellectual property rights of Sun Microsystems, Inc. and Fujitsu Limited in such products, technology anddocument include, without limitation, one or more of the United States patents listed at http://www.sun.com/patents and one or moreadditional patents or patent applications in the United States or other countries.

This document and the product and technology to which it pertains are distributed under licenses restricting their use, copying, distributand decompilation. No part of such product or technology, or of this document, may be reproduced in any form by any means without pr

written authorization of Fujitsu Limited and Sun Microsystems, Inc., and their applicable licensors, if any. The furnishing of this documenyou does not give you any rights or licenses, express or implied, with respect to the product or technology to which it pertains, and thisdocument does not contain or represent any commitment of any kind on the part of Fujitsu Limited or Sun Microsystems, Inc., or any affieither of them.

This document and the product and technology described in this document may incorporate third-party intellectual property copyrighteand/or licensed from suppliers to Fujitsu Limited and/or Sun Microsystems, Inc., including software and font technology.

Per the terms of the GPL or LGPL, a copy of the source code governed by the GPL or LGPL, as applicable, is available upon request by theUser. Please contact Fujitsu Limited or Sun Microsystems, Inc.

This distribution may include materials developed by third parties.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered tradin the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.

Sun, Sun Microsystems, the Sun logo, Java, Netra, Solaris, Sun Ray, Answerbook2, docs.sun.com, OpenBoot, and Sun Fire are trademaregistered trademarks of Sun Microsystems, Inc., or its subsidiaries, in the U.S. and other countries.

Fujitsu and the Fujitsu logo are registered trademarks of Fujitsu Limited.

All SPARC trademarks are used under license and are registered trademarks of SPARC International, Inc. in the U.S. and other countProducts bearing SPARC trademarks are based upon architecture developed by Sun Microsystems, Inc.

SPARC64 is a trademark of SPARC International, Inc., used under license by Fujitsu Microelectronics, Inc. and Fujitsu Limited.

The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowthe pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industholds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Suns licensees who implementLOOK GUIs and otherwise comply with Suns written license agreements.

United States Government Rights - Commercial use. U.S. Government users are subject to the standard government user license agreemeSun Microsystems, Inc. and Fujitsu Limited and the applicable provisions of the FAR and its supplements.

Disclaimer: The only warranties granted by Fujitsu Limited, Sun Microsystems, Inc. or any affiliate of either of them in connection widocument or any product or technology described herein are those expressly set forth in the license agreement pursuant to which the por technology is provided. EXCEPT AS EXPRESSLY SET FORTH IN SUCH AGREEMENT, FUJITSU LIMITED, SUN MICROSYSTEMSAND THEIR AFFILIATES MAKE NO REPRESENTATIONS OR WARRANTIES OF ANY KIND (EXPRESS OR IMPLIED) REGARDINGPRODUCT OR TECHNOLOGY OR THIS DOCUMENT, WHICH ARE ALL PROVIDED AS IS, AND ALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THEEXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Unless otherwise expressly set forth in such agreementextent allowed by applicable law, in no event shall Fujitsu Limited, Sun Microsystems, Inc. or any of their affiliates have any liability 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, sincidental or consequential damages, even if advised of the possibility of such damages.

DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANINCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.


3/118

Copyright 2010 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. et FUJITSU LIMITED, 1-1, Kamikod4-chome, Nakahara-ku, Kawasaki-shi, Kanagawa-ken 211-8588, Japon. Tous droits rservs.

Entre et revue tecnical fournies par Fujitsu Limited sur des parties de ce matriel.

Sun Microsystems, Inc. et Fujitsu Limited dtiennent et contrlent toutes deux des droits de proprit intellectuelle relatifs aux produtechnologies dcrits dans ce document. De mme, ces produits, technologies et ce document sont protgs par des lois sur le copyrigh

brevets, dautres lois sur la proprit intellectuelle et des traits internationaux. Les droits de proprit intellectuelle de Sun Microsystemet Fujitsu Limited concernant ces produits, ces technologies et ce document comprennent, sans que cette liste soit exhaustive, un ou pludes brevets dposs aux tats-Unis et indiqus ladresse http://www.sun.com/patents de mme quun ou plusieurs brevets ou applic

brevetes supplmentaires aux tats-Unis et dans dautres pays.

Ce document, le produit et les technologies affrents sont exclusivement distribus avec des licences qui en restreignent lutilisation, lala distribution et la dcompilation. Aucune partie de ce produit, de ces technologies ou de ce document ne peut tre reproduite sous qforme que ce soit, par quelque moyen que ce soit, sans lautorisation crite pralable de Fujitsu Limited et de Sun Microsystems, Inc., et dventuels bailleurs de licence. Ce document, bien quil vous ait t fourni, ne vous confre aucun droit et aucune licence, expresses ou tconcernant le produit ou la technologie auxquels i l se rapporte. Par ailleurs, il ne contient ni ne reprsente aucun engagement, de quelquque ce soit, de la part de Fujitsu Limited ou de Sun Microsystems, Inc., ou des socits affilies.

Ce document, et le produit et les technologies quil dcrit, peuvent inclure des droits de proprit intellectuelle de parties tierces protgcopyright et/ou cds sous licence par des fournisseurs Fujitsu Limited et/ou Sun Microsystems, Inc., y compris des logiciels et detechnologies relatives aux polices de caractres.

Par limites du GPL ou du LGPL, une copie du code source rgi par le GPL ou LGPL, comme applicable, est sur demande vers la fin utidisponible; veuillez contacter Fujitsu Limted ou Sun Microsystems, Inc.

Cette distribution peut comprendre des composants dvelopps par des tierces parties.

Des parties de ce produit pourront tre drives des systmes Berkeley BSD licencis par lUniversit de Californie. UNIX est une madpose aux Etats-Unis et dans dautres pays et licencie exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, Java, Netra, Solaris, Sun Ray, Answerbook2, docs.sun.com, OpenBoot, et Sun Fire sont des marqfabrique ou des marques dposes de Sun Microsystems, Inc., ou ses filiales, aux Etats-Unis et dans dautres pays.

Fujitsu et le logo Fujitsu sont des marques dposes de Fujitsu Limited.

Toutes les marques SPARC sont utilises sous licence et sont des marques de fabrique ou des marques dposes de SPARC Internationaux Etats-Unis et dans dautres pays. Les produits portant les marques SPARC sont bass sur une architecture dveloppe par SunMicrosystems, Inc.

SPARC64 est une marques dpose de SPARC International, Inc., utilise sous le permis par Fujitsu Microelectronics, Inc. et Fujitsu L

Linterface dutilisation graphique OPEN LOOK et Sun a t dveloppe par Sun Microsystems, Inc. pour ses utilisateurs et licencireconnat les efforts de pionniers de Xerox pour la recherche et le dveloppement du concept des interfaces dutilisation visuelle ou grappour lindustrie de linformatique. Sun dtient une license non exclusive de Xerox sur linterface dutilisation graphique Xerox, cette lcouvrant galement les licencis de Sun qui mettent en place linterface dutilisation graphique OPEN LOOK et qui, en outre, se confoaux licences crites de Sun.

Droits du gouvernement amricain - logiciel commercial. Les utilisateurs du gouvernement amricain sont soumis aux contrats de licstandard de Sun Microsystems, Inc. et de Fujitsu Limited ainsi quaux clauses applicables stipules dans le FAR et ses supplments.

Avis de non-responsabilit: les seules garanties octroyes par Fujitsu Limited, Sun Microsystems, Inc. ou toute socit affilie de lune ouentit en rapport avec ce document ou tout produit ou toute technologie dcrit(e) dans les prsentes correspondent aux garanties expressstipules dans le contrat de licence rgissant le produit ou la technologie fourni(e). SAUF MENTION CONTRAIRE EXPRESSMENTSTIPULE DANS CE CONTRAT, FUJITSU LIMITED, SUN MICROSYSTEMS, INC. ET LES SOCITS AFFILIES REJETTENT TOUTREPRSENTATION OU TOUTE GARANTIE, QUELLE QUEN SOIT LA NATURE (EXPRESSE OU IMPLICITE) CONCERNANT CEPRODUIT, CETTE TECHNOLOGIE OU CE DOCUMENT, LESQUELS SONT FOURNIS EN LTAT. EN OUTRE, TOUTES LES CONDITREPRSENTATIONS ET GARANTIES EXPRESSES OU TACITES, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATLA QUALIT MARCHANDE, LAPTITUDE UNE UTILISATION PARTICULIRE OU LABSENCE DE CONTREFAON, SOEXCLUES, DANS LA MESURE AUTORISE PAR LA LOI APPLICABLE. Sauf mention contraire expressment stipule dans ce contrala mesure autorise par la loi applicable, en aucun cas Fujitsu Limited, Sun Microsystems, Inc. ou lune de leurs filiales ne sauraient tre responsables envers une quelconque partie tierce, sous quelque thorie juridique que ce soit, de tout manque gagner ou de perte de de problmes dutilisation ou de perte de donnes, ou dinterruptions dactivits, ou de tout dommage indirect, spcial, secondaire oconscutif, mme si ces entits ont t pralablement informes dune telle ventualit.

LA DOCUMENTATION EST FOURNIE EN LETAT ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPROU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMTOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A LAPTITUDE A UNE UTILISATION PARTICULIERELABSENCE DE CONTREFACON.


4/118


5/118

Contents

Preface xi

1. New Information About the SPARC Enterprise T5140 and T5240 Servers

New Information About Known Issues 1

Hardware and Mechanical Issues 2

False Intermittent SATA Errors Seen on Sun SPARC Enterprise T5140T5240 Servers (CR 6880299) 2

Not Enough Memory to Expand MD On Some Memory Configurati(CR 6879970) 2

Firmware and General Software Issues 3

After the Power Cord Removal/Insert, an Error Message May Appe

during the POST 3

Solaris OS Issues 5

Boot Drive May Report drive type unknown for Solaris formatCommand (CR 6886514) 5

New Information About Documentation Errata 13

SPARC Enterprise T5140 and T5240 Servers Service Manual 13

Incorrect Data Cable Routing Diagram for T5140 Servers With 4-DisBackplanes 13

Incorrect Data Cable Routing Diagram for T5240 Servers With 8-DisBackplanes 14

Fan Module Missing in Data Cable Routing Diagram 14


6/118

vi SPARC Enterprise T5140 and T5240 Servers Product Notes March 2010

Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide 15

Erroneous Description about Collecting SP Data 15

Integrated Lights Out Manager 3.0 Web Interface Procedures Guide 16

Erroneous Description about Collecting SP Data 16

2. Important Information About the SPARC Enterprise T5140 and T5240 Servers17

Notes on DVD Drive and Discs 17

Supported Versions of Solaris and System Firmware 18

Solaris OS and Firmware Requirements for Certain Features 19

System Firmware 20

Preinstalled Software 20

Cool Tools for Servers With CoolThreads Technology 21Logical Domains 22

Sun Java Enterprise System and Solaris OS 22

To Enable the WebConsole SMF Service 22

Solaris Live Upgrade 23

Sun Studio - C, C++, and Fortran Compilers and Tools 23

Supported Sun Explorer Utility Version 24

Patch Information 25Patch CD 25

Mandatory Patch Information For the Solaris 10 8/07 OS 26




To Download Patches 27

Patches for Option Cards 28Installing the 4Gbps Fibre Channel card 28

General Functionality Issues and Limitations 29


7/118

Contents

Cryptographic Function 29

RAID Function 29

Cable Management Arm 29

SSD (Solid State Drive) 30

Express Rail Rackmounting Kit 30SAS RAID Internal HBA Card 30

Changed Behavior When Operating the Solaris OS With Logical Domains

Results from Halting or Rebooting the Control Domain 31

Messages Identifying the Availability of CPUs as Hot-Insertion Events

Processor Identification 33

Processor IDs Might Not Start at 0, and Might Not be Contiguous

Notes on the Use of 200V Power Supply 34

3. Known Issues 35


Hot-Swapping Fan Modules 35

Unexpected LED Behavior 36

Onboard Ethernet Port 36

XAUI Card Disables an Onboard Network Port 38

A Fault in the XAUI Card Causes the Built-in Ethernet Port to Be Unu(CR 6713773, 6724347) 39

Solaris OS Issues 42

Sun Explorer May Fail to Collect the ILOM Data (Tx000) (CR 6718841)

Notes on Installing Solaris 10 8/07 OS and Solaris 10 5/08 OS 46

Integrated Lights Out Manager (ILOM) Issues 49

After a Host Power-On Instruction is Executed from ILOM, the POST MaStart, and Processing May Not Go to OS Boot Processing or the ok Pr(CR 6752910) 55

For DC Input Power Models, /PS0/AC_POK Is Displayed (CR 6815369


8/118

viii SPARC Enterprise T5140 and T5240 Servers Product Notes March 2010

According to the IPMI PET Warning and SNMP Trap Warning Settings in theWarning Rule Settings, Warning Message Creation may not be PossibleDepending on the Event Type (CR 6746677) 58

In the Logical Domains Environment, After the Host Reset Operation, HostMay Be Reset Again (CR 6836426) 59

The ILOM Network Configuration Cannot Be Set (CR 6835854, 6779753) 60The prtdiag Command Doesn't Show the Correct Memory Configuration in

the Output, in the Configuration with Different Memory Capacities (CR6842745) 61

On the Server With a Specific Configuration, Lower Threshold Value of thePower Input Sensor May Not Be Correctly Displayed (CR 6847031) 64

4. Documentation Errata 67

Errors in the SPARC Enterprise T5140 and T5240 Servers Installation Guide 67

Verify Proper Seating of Preinstalled PCIe/XAUI Cards 68

Errors in the SPARC Enterprise T5140 and T5240 Servers Site Planning Guide 68

Error on page 2 in "Minimum Clearance for Service Access" 68

Incorrect Values for Idle Input Power Requirements in Minimum ServerConfigurations 70

Incorrect Operating Input Voltage Values for the 1.4 GHz, 8-DiskConfiguration 71

Incorrect Operating Input Power and Heat Dissipation for the 1.4 GHz, 16-

Disk Configuration 71Incorrect Operating Input Voltage Values for the 1.6 GHz, 8-Disk

Configuration 72

Errors in the SPARC Enterprise T5140 and T5240 Servers Administration Guide 72

Notes on the "SPARC Enterprise T5x40 Device Tree" 72

Errors in the Integrated Lights Out Manager 2.0 User's Guide 73

Incorrect ILOM Command Related to IP Address Assignment 73

The Command in the Section "Edit an SNMP User Account Using the CLI" onPage 195 is Incorrect 73

Errors in the Integrated Lights Out Manager 2.0 Supplement 73

Points of Concern about the Connection of ILOM (CR 6806789) 73


9/118

Contents

Errors in the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide

Erroneous Description in "Collect SP Data to Diagnose System Problems6806800) 74

Erroneous Default Value for /SP/clients/dns 74

Errors in the Integrated Lights Out Manager 3.0 Supplement for SPARC EnterprT5140 and T5240 Servers 75

Notes on "ILOM Information Stored on the SCC" 75

A. Fixed Issues 77


Incorrect Fan Diagrams on Service Label for Eight-Disk Capable T5140Servers 77

Solaris OS Issues 78

If prtdiag Is Canceled, Subsequent prtdiag Executions May Fail to DiStatus Information (CR 6552999, 6731560) 80

Integrated Lights Out Manager (ILOM) Issues 81

For DC Input Power Models, the Output From the showpower -vCommMay Differ Between /SYS/PS0 And /SYS/PS1 (CR 6802433) 93

In the Output From the prtdiagCommand, Warnings May Be Displayed6821325) 94

MCU Might Be Disconnected in DIMM Module Failure (CR 6656116) 9

On the DC Input Power Model, the "Environmental Status" and Some Pthe "FRU Status" Information Is Not Displayed (CR 6853843) 96

When the Service Processor Is Initialized, ILOM May Fails to Start WithError Message Displayed (CR 6856163) 97

After the SCC Module Replacement, a Connection to the ILOM NetworkFail (CR 6857271) 99

Firmware and General Software Issues 100


10/118

x SPARC Enterprise T5140 and T5240 Servers Product Notes March 2010


11/118

Preface

These product notes contain late-breaking information about the SPARCEnterprise T5140 and T5240 servers hardware, software, or documentation ethat became known after the documentation set was published.

Support for the SPARC Enterprise T5140 and T5240 Servers on page xi

Fujitsu Welcomes Your Comments on page xii

Support for the SPARC Enterprise T51and T5240 Servers

Technical SupportIf you have technical questions or issues that are not addressed in the SPARCEnterprise T5140 or T5240 servers documentation, contact a sales representativcertified service engineer.

Downloading DocumentationInstructions for installing, administering, and using your servers are provided i

SPARC Enterprise T5140 and T5240 servers documentation sets. The entiredocumentation set is available for download from the following web site:

Global Site

http://www.fujitsu.com/sparcenterprise/manual/


12/118

xii SPARC Enterprise T5140 and T5240 Servers Product Notes March 2010

North American Site

https://download.computers.us.fujitsu.com/

Japanese Site

http://primeserver.fujitsu.com/sparcenterprise/manual/

Note Information in these product notes supersedes the information in the SPARCEnterprise T5140 and T5240 documentation sets.

Fujitsu Welcomes Your CommentsIf you have any comments or requests regarding this document, or if you find anyunclear statements in the document, please state your points specifically on the format the following URL.

For Users in U.S.A., Canada, and Mexico:

http://www.computers.us.fujitsu.com/www/support_servers.shtml?support/servers

For Users in Other Countries:

SPARC Enterprise contact

http://www.fujitsu.com/global/contact/computing/sparce_index.html


13/118


14/118

2 SPARC Enterprise T5140 and T5240 Servers Product Notes March 2010

Hardware and Mechanical Issues

False Intermittent SATA Errors Seen on Sun SPARCEnterprise T5140 and T5240 Servers (CR 6880299)

When booting the Solaris 10 5/08 OS (S10 U5), some systems with SATA DVDdevices intermittently log port failur errors in /var/adm/messages. The followingshows an example of typical error messages for the T5x40 server:

Workaround: You can ignore these messages.

Not Enough Memory to Expand MD On Some MemoryConfigurations (CR 6879970)

This issue is resolved by updating the system firmware to 7.2.7.b or later.

If the memory size for one CPU in a system is 128 gigabytes, memory resources forthe other CPU must be greater than 16 gigabytes. Otherwise, a memory overflowcondition will result. TABLE 1-1 illustrates the three memory configurations thatexhibit this behavior.

Workaround: Assign memory resources in configurations that avoid thecombinations shown in TABLE 1-1.

/pci@400/pci@0/pci@1/pci@0/usb@0,1 (ohci1): Connecting device on port 1 failed/pci@400/pci@0/pci@1/pci@0/usb@0,2 (ehci0): Connecting device on port 2 failed

TABLE 1-1 Examples of Dual CPU Memory Configurations That Can Produce MemoryOverflow

CPU 0 Memory Size CPU 1 Memory Size CPU 0 FB-DIMM Use CPU 1 FB-DIMM Use

16 GB 128 GB 8x 2-GB DIMMs 16x 8-GB DIMMs




15/118

Chapter 1 New Information About the SPARC Enterprise T5140 and T5240 Servers

Firmware and General Software Issues

After the Power Cord Removal/Insert, an Error MessMay Appear during the POST

After you remove/insert the power cord and while POST is running, the/SYS/XXXXX prom is unreadable or corrupted message may appeastop at ok prompt.

TABLE 1-2 Firmware and General Software Issues

CR Description Workaround

67226026663105

When connected to OS console via ILOM, inputor display to console may not be enabled. And atthis time, output from OS to console may fail.

Note - Fixed in System Firmware 7.2.2.e orlater.

After the system stop, disconnect the power and then reconnect the power cord.

6913388 The ILOM event log may not be in the SolarisOS system log output (/var/adm/messages).ILOM login event example:Nov 7 14:13:03 xxxxxx SC Alert: [ID178418 daemon.notice] Audit | minor:admin : Open Session :

object = /session/type : value =shell : success

Nov 7 14:13:04 xxxxxx SC Alert: [ID434268 daemon.notice] Audit | minor:admin : Close Session :

object = /session/type : value =shell : success

None.Perform the ILOM reset operation. If notrecovered, shut down the system and thenremove and insert the power cord.ILOM reset operation example:Log in to ILOM and execute the followingcommand.

[In case of ILOM command mode]-> reset /SPAre you sure you want to reset /(y/n)? y

[In case of ALOM CMT compatible shell]sc> resetsc

Are you sure you want to reset tSC [y/n]? y

n/a After you remove/insert the power cord andwhile POST is running, the /SYS/XXXXX promis unreadable or corrupted messagemay appear and stop at ok prompt. For details,see After the Power Cord Removal/Insert, anError Message May Appear during the POSTon page 3.

Take 180 or more seconds for each of theintervals between the system power-off andpower cord removal, and between the remoand insertion of the power cord.


16/118


Message example:

This event occurs in case you power off the system and remove the power cord in ashort period of time, or in case you remove and insert the power cord in a shortperiod of time. When the above time period is too short, the ILOM internal processdoes not complete normally.

Chassis | major: Host has been powered on0:0:0>0:0:0>SPARC-Enterprise[TM] T5120/T5220 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 reserved0:0:0>POST enabling CMP 0 threads: ffffffff.ffffffff0:0:0>VBSC mode is: 00000000.000000010:0:0>VBSC level is: 00000000.000000010:0:0>VBSC selecting Normal mode, MAX Testing.0:0:0>VBSC setting verbosity level 20:0:0>Basic Memory Tests....Done0:0:0>Test Memory....Done0:0:0>Setup POST Mailbox ....Done0:0:0>Master CPU Tests Basic....Done0:0:0>Init MMU.....

Fault | critical: SP detected fault at time Mon Jan 18 08:45:10 2010. /SYS/PADCRDprom is unreadable or corrupted0:0:0>NCU Setup and PIU link train....Done0:0:0>L2 Tests....Done0:0:0>Extended CPU Tests....Done0:0:0>Scrub Memory....Done0:0:0>SPU CWQ Tests...Done0:0:0>MAU Tests...Done0:0:0>Network Interface Unit Tests....Done0:0:0>Functional CPU Tests....Done0:0:0>Extended Memory Tests....Done2010-01-18 08:46:50.299 0:0:0>INFO:

2010-01-18 08:46:50.302 0:0:0> POST Passed all devices.2010-01-18 08:46:50.307 0:0:0>POST: Return to VBSC.2010-01-18 08:46:50.310 0:0:0>Master set ACK for vbsc runpost command and spin...Chassis | major: Host is running

SPARC Enterprise T5220, No KeyboardCopyright 2009 Sun Microsystems, Inc. All rights reserved.OpenBoot 4.30.6, 8064 MB memory available, Serial #85367270.Ethernet address 0:21:28:16:99:e6, Host ID: 851699e6.

{0} ok


17/118


When this event occurred, perform the following procedure. After you restoreusing this procedure, you do not need to replace the component.

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. Wait for 180 or more seconds.

5. Insert the power cord.

Workaround: Take 180 or more seconds for each of the intervals between the sypower-off and the power cord removal, and between the removal and insertionthe power cord.

Solaris OS Issues

Boot Drive May Report drive type unknown for Solformat Command (CR 6886514)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 Tand T5240 servers, which introduced a latent bug into those systems. The bug described as latent because it is activated only when the Solaris format commis used. Otherwise, the bug has no effect on system behavior or performance.

When a system administrator or other user with root (/) privileges enters the focommand on a system containing this bug, the boot drive will report drive tyunknown. This fault condition presents two problems for the administrator:

The administrator will be unable to access unused portions of the boot drivbecause of the unknown drive type error.

The presence of mounted partitions blocks use of the format utilitys autoconfigure feature. Attempts to bypass this restriction by booting from the netor removable media could put the system in an unbootable state.


18/118


The Workaround section below describes a procedure you can use to recover fromthis drive type unknown fault mode without the risks associated with the networkand media boot methods.

Workaround: The sequence of steps shown in CODE EXAMPLE 1 must be followedexactly as shown. To simplify tracking of the procedure, the steps are organized intonine sections:

1. Determine whether or not the systems boot device is affected.

2. Shut server down and restart in single user mode with the root filesystemmounted read only.

3. Mount the tmpfs /tmp filesystem to provide a working area.

4. Capture the boot drives existing vtoc in a file stored in /tmp.

5. Make a copy of the fmthard utility for use in the /tmp work area.

6. Set and export the NOINUSE_CHECK variable to allow the format command fullaccess to the boot drive.

7. Run the format utility to restore the drives type.

8. Use the fmthard command and stored information to complete the recovery.

9. Verify the success of the recovery.

CODE EXAMPLE 1-1 Procedure for Recovering a Boot Drives drive type

1. Determine if the boot drive is affected:

root@host-1 #uname -aSunOS host-1 5.10 Generic_141414-10 sun4v sparc SUNW,SPARC-Enterprise-T5240

root@host-1 #mount -p | head -1/dev/dsk/c0t0d0s0 - / ufs - no rw,intr,largefiles,logging,xattr,onerror=

panicroot@host-1 # format c0t0d0s0


19/118



format - format and analyze the diskrepair - repair a defective sectorlabel - write label to the diskanalyze - surface analysis

defect - defect list managementbackup - search for backup labelsverify - read and display labelssave - save new disk/partition definitionsinquiry - show vendor, product and revisionvolname - set 8-character volume name The jumpstart install process! - execute , then returnquit

format> disk

The jumpstart install processAVAILABLE DISK SELECTIONS:

0. c0t0d0


20/118



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): /tmp/vtoc


21/118



Format will now present the following menu, choose 0. Auto configure

AVAILABLE DRIVE TYPES:0. Auto configure

1. Quantum ProDrive 80S2. Quantum ProDrive 105S

[...]17. Zip 25018. Peerless 10GB19. otherSpecify disk type (enter its number): 0c0t0d0: configured with capacity of 68.35GB quitroot@ #


22/118



8. Use the fmthard command and stored information to complete the recovery.

root@ # /tmp/fmthard -s /tmp/vtoc /dev/rdsk/c0t0d0s0 partition

PARTITION MENU:

0 - change 0 partition

1 - change

1

partition2 - change 2 partition3 - change 3 partition4 - change 4 partition


23/118



5 - change 5 partition6 - change 6 partition7 - change 7 partitionselect - select a predefined table

modify - modify a predefined partition tablename - name the current tableprint - display the current tablelabel - write partition map and label to the disk! - execute , then returnquit

partition> printCurrent partition table (original):Total disk cylinders available: 14087 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks0 root wm 825 - 3298 12.00GB (2474/0/0) 25175424

1 swap wu 0 - 824 4.00GB (825/0/0) 83952002 backup wm 0 - 14086 68.35GB (14087/0/0) 1433493123 unassigned wm 3299 - 5772 12.00GB (2474/0/0) 251754244 unassigned wu 0 0 (0/0/0) 05 unassigned wu 0 0 (0/0/0) 06 unassigned wu 0 0 (0/0/0) 07 nassigned wu 0 0 (0/0/0) 0

partition> quit

FORMAT MENU:disk - select a disk

type - select (define) a disk typepartition - select (define) a partition tablecurrent - describe the current diskformat - format and analyze the diskrepair - repair a defective sectorlabel - write label to the diskanalyze - surface analysisdefect - defect list managementbackup - search for backup labelsverify - read and display labelssave - save new disk/partition definitionsinquiry - show vendor, product and revision

volname - set 8-character volume name The jumpstart install process! - execute , then returnquit

format> disk


24/118



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]format> quit

The drive type recovery is complete, reboot the server:

root@ # rebootsyncing file systems... donerebooting...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-bitCopyright 1983-2009 Sun Microsystems, Inc. All rights reserved.Use is subject to license terms.Hostname: host-1The / file system (/dev/rdsk/c0t0d0s0) is being checked.Reading ZFS config: done.host-1 console login:


25/118


New Information About DocumentatiErrata

This section describes documentation errors that were discovered since the preedition of the Product Notes was published.

SPARC Enterprise T5140 and T5240 Servers ServiManual

Incorrect Data Cable Routing Diagram for T5140 Serv

With 4-Disk BackplanesThe data cable routing diagram for 4-disk capable backplanes is wrong. It showcable connected to SAS1. It should be connected to SAS0. This is the correct dia

FIGURE 1-1 Internal Cables for the Onboard SAS Controller Card (Four-Disk CapbaSPARC Enterprise T5140 Servers)


26/118


Incorrect Data Cable Routing Diagram for T5240 ServersWith 8-Disk Backplanes

The data cable routing diagram for 8-disk capable backplanes in T5240 servers iswrong. It shows a single data cable. There should be two. This is the correctdiagram:

FIGURE 1-2 Internal Cables for Onboard SAS Controller Cards (Eight-Disk CapableSPARC Enterprise T5240 Servers)

Fan Module Missing in Data Cable Routing Diagram

The cable routing diagram for 8-disk capable backplanes in T5140 systems is missinga fan module in the upper right corner. This is the correct diagram:


27/118


FIGURE 1-3 Internal Cables for the Onboard SAS Controller Card (Eight-Disk CapabSPARC Enterprise T5140 Servers)

Integrated Lights Out Manager (ILOM) 3.0 CLIProcedures Guide

Erroneous Description about Collecting SP Data

The following description in the section "Collect SP Data to Diagnose SystemProblems" on page 88 includes incorrect information.

On the SPARC Enterprise T-series servers, when you specified the full optionhost in execution will not be reset. While the host is executing, you can specifyfull option.

Variable Option Description

data full Specifies that all data is to be collected ("full" collectNote - Using this option may reset the running host


28/118


Integrated Lights Out Manager 3.0 Web InterfaceProcedures Guide

Erroneous Description about Collecting SP Data

The following description in the section "Collect SP Data to Diagnose SystemProblems" on page 79 includes incorrect information.

3. Select the desired Data Set: Normal, Full, or Custom.

Normal Specifies that ILOM, operating system, and hardware information iscollected.

Full Specifies that all data is to be collected. Selecting Full might reset thesystem.

Custom Allows you to choose one or more of the following data sets:

ILOM Data

Hardware Data

Basic OS Data

Diagnostic Data

On the SPARC Enterprise T-series servers, when you specified the full option, thehost in execution will not be reset. While the host is executing, you can specify thefull option.


29/118

CHAPTER 2

Important Information About theSPARC Enterprise T5140 and T5240Servers

This chapter contains important information about the SPARC Enterprise T514

T5240 servers.The following sections are included:

Notes on DVD Drive and Discs on page 17

Supported Versions of Solaris and System Firmware on page 18

Solaris OS and Firmware Requirements for Certain Features on page 19

System Firmware on page 20

Preinstalled Software on page 20

Patch Information on page 25

General Functionality Issues and Limitations on page 29

Changed Behavior When Operating the Solaris OS With Logical Domainspage 31

Processor Identification on page 33

Notes on the Use of 200V Power Supply on page 34

Notes on DVD Drive and DiscsSee the "Notes on DVD Drive and Discs in SPARC Enterprise" on the website b

before using the CD/DVD discs in the standard DVD drive mounted in this se

http://www.fujitsu.com/sparcenterprise/manual/


30/118


Supported Versions of Solaris andSystem FirmwareTABLE 2-1 lists the versions of Solaris OS and system firmware supported forSPARC Enterprise T5140 and T5240 servers.

Your server is preinstalled with the latest supported OS, patches and firmware. Ifyou decide to install some other supported version, be certain to also install thepatches required by that version. For information on OS patch requirements, seePatch Information on page 25.

Note If you install an OS over the preinstalled OS (even if it is the same version)you will overwrite the supplementary software that was preinstalled at the factory.See Preinstalled Software on page 20 for more information on this additionalpreinstalled software.

Note Some optional features require certain versions of the OS and SystemFirmware. See Solaris OS and Firmware Requirements for Certain Features onpage 19.

Note When installing the Solaris 10 8/07 OS or Solaris 10 5/08 OS on a serverequipped with a USB SATA DVD drive, see Notes on Installing Solaris 10 8/07 OSand Solaris 10 5/08 OS on page 46.

TABLE 2-1 Supported Versions of the OS and Firmware

Supported Versions

OS Solaris 10 8/07 OS plus mandatory patches Minimum supported OS

Solaris 10 5/08 OS plus patches

Solaris 10 10/08 OS

Solaris 10 5/09 OS

Solaris 10 10/09 OS Latest supported OS

Firmware System Firmware 7.1.3.d Minimum supported System Firmware

System Firmware 7.2.7.b Latest supported version (as of March 2010)


31/118

Chapter 2 Important Information About the SPARC Enterprise T5140 and T5240 Servers

Solaris OS and Firmware Requirementfor Certain FeaturesThe following table identifies the minimum OS and firmware versions requiresupport certain features.

Note To benefit from the accumulated features, enhancements, and fixes, upgyour system firmware to the most recent version available.

TABLE 2-2 Minimum OS and Firmware Version Requirements for Certain Features

Feature Minimum Firmware Version Minimum OS Version

12 or 24 FB-DIMM systemconfiguration

7.1.3.d N/A

Systems using the External I/OExpansion Unit

7.1.6.d Solaris 10 10/08 OS

Systems using low voltage (LV)1.5V FB-DIMMs*

*Follow all of the system memory configuration rules and restrictions defined in the SPEnterprise T5140 and T5240 Servers Service Manual.

7.1.6.d N/A

Different FB-DIMM capacities ondifferent CPUs*

7.1.7.f N/A

Systems operating with DC powersupplies

7.1.7.f Solaris 10 10/08 OS

1.6 GHz processors 7.2.2.e N/A

ILOM 3.0 firmware 7.2.2.e N/A

Different FB-DIMM capacitiesusing the memory mezzanineassembly

7.2.7.b N/A

LDoms 1.2

For minimum firmware version, minimum OS version, and mandatory patches when using LDoms softwarsee the Logical Domains Guide.

- -

LDoms 1.3 - -


32/118


System FirmwareThe 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) firmware OpenBoot firmware

POST firmware

Hypervisor firmware

VBSC firmware

System Firmware updates are available from following web site as patch releases.

http://www.fujitsu.com/global/services/computing/server/sparcenterprise/downloads/

When you update the System Firmware, all of the individual firmware components

are updated. You cannot update firmware components individually. Refer to theSPARC Enterprise T5140 and T5240 Servers Installation Guide for more informationabout updating the system firmware.

Preinstalled SoftwareThis section lists and describes the preinstalled software on your server. Thepreinstalled software is ready to use.

Note The Solaris OS is preinstalled both in root disk Slice 0 for normal operations,and in Slice 3 along with Live Upgrade software to provide an Alternate BootEnvironment (ABE). The ABE enables you to upgrade the OS or performing systemmaintenance tasks without reducing performance. An identical (bootable) copy ofthe root partition (including the OS, EIS, and applications) is installed as an ABE inSlice 3.


33/118


The following table lists the software preinstalled on your server.

Cool Tools for Servers With CoolThreadsTechnologyCool Tools provide a collection of freely available tools designed to enable fastefficient development and deployment of optimally configured software solution CoolThreads servers. These tools significantly improve performance and to-market for applications running on these servers.

An overview of the Cool Tools and full documentation is available at the folloURL:

http://www.sun.com/servers/coolthreads/overview/cooltools.js

Not all of the Cool Tools listed on the Cool Tools web page are preinstalled on server. The following are not included:

Consolidation Tool

CoolTuner

Cool Stack

Corestat

Cooltst

Sun Application Porting Assistant

Note The Sun Code Generator GCC compiler is preinstalled. For lists ofpreinstalled software, see TABLE 2-3.

TABLE 2-3 Preinstalled Software

Software Location Function

Solaris 10 5/09 Root disk Slice 0 (and on Slice 3 in the ABE) with

patches (see Patch CD on page 25)

Operating system

Sun Studio /opt/SUNWspro C, C++, and Fortran compiler

LDoms Manager /opt/SUNWldm/ Manages Logical Domains

LDoms MIB /opt/SUNWldmib LDoms Management Information B

CMT Tools /opt/SUNWspro/extra/bin Sun Studio Developer Tools

Sun CodeGenerator forSPARC Systems

/opt/gcc and /opt/SUNW0scgfss GCC compiler for SPARC Systems


34/118


Logical DomainsUsing Logical Domains (LDoms) increases your server usage, efficiency, and returnon investment. LDoms also reduce your server footprint. The LDoms Managersoftware creates and manages logical domains, and maps logical domains tophysical resources.

Note The LDoms MIB must be configured before it is ready to use. A READMEfile with configuration instructions is located in the LDoms MIB installationdirectory, /opt/ldoms_mib.

For more information on LDoms, go to:

http://www.fujitsu.com/global/services/computing/server/sparcenterprise/products/software/ldoms/

Sun Java Enterprise System and Solaris OSThe Sun Java Enterprise System is a comprehensive set of software and lifecycleservices that make the most of your software investment.

For an overview and documentation, go to:

http://www.sun.com/service/javaes/index.xml

Formerly preinstalled, you must download Sun Java Enterprise System in order toinstall it. To acquire Sun Java Enterprise System software go to:

http://www.sun.com/download

Note Due to an issue that arises from the installation of the Java Enterprise System5 Update 1 on your system (CR 6644798), it might be necessary to enable theWebConsole SMF service.

To Enable the WebConsole SMF Service Log into a terminal as root then type the following command:

# svcadm enable svc:/system/webconsole:console
http://www.fujitsu.com/global/services/computing/server/sparcenterprise/products/software/ldoms/http://www.fujitsu.com/global/services/computing/server/sparcenterprise/products/software/ldoms/http://www.fujitsu.com/global/services/computing/server/sparcenterprise/products/software/ldoms/


35/118


If it becomes necessary to reload the software, go to the following web site fordownload and installation instructions:

http://www.sun.com/software/preinstall

Note If you download a fresh copy of software, that software might not incl

patches that are mandatory for your server. After installing the software, see Information on page 25 for a procedure to check for the presence of patches osystem.

Solaris Live UpgradeSolaris Live Upgrade technology significantly reduces the instances of service oduring an OS upgrade. This technology enables the Solaris OS to run normallyduring an upgrade or normal maintenance on an inactive boot environment.

Your server is configured with a liveupgrade partition on Slice 3 on the bootthat contains an exact duplicate of the root partition (including the OS, EIS, aapplications). This liveupgrade partition is an Alternate Boot Environment (A

For more information about Solaris Live Upgrade, go to:

http://www.sun.com/software/solaris/liveupgrade/

Sun Studio - C, C++, and Fortran Compilers an

ToolsSun Studio delivers high performance by optimizing C, C++, and Fortran compfor the Solaris OS on multicore systems.

For an overview and documentation, go to:

http://developers.sun.com/sunstudio/index.jsp


36/118


Supported Sun Explorer Utility VersionThe SPARC Enterprise T5140 and T5240 servers are supported by the Sun Explorer5.10 (or later) data collection utility, but are not supported by earlier releases of theutility. Determine whether an earlier version of the Sun Explorer product has beeninstalled on your system by typing the following:

If an earlier version exists, uninstall it and install version 5.10, or later. Forinformation on how to get the Sun Explorer Utility, please contact a certified serviceengineer.

#pkginfo -l SUNWexplo


37/118


Patch InformationPatches are available at:

Global Sitehttp://www.fujitsu.com/global/support/software/security/products-s/patch-

Japanese Site

http://software.fujitsu.com/jp/security/products-others/unix

North American Site

https://download.computers.us.fujitsu.com/

Before contacting support, ensure that all mandatory patches are installed on yserver. In addition to installing these patches, check the above web site on a re

basis for the availability of new patches.

To determine if a patch is present, see To Download Patches on page 27.

Note The mandatory patches might not be included in some versions of thepreinstalled or preloaded software on your server. If the patches are missing fryour server, download them from as described in To Download Patches onpage 27.

Patch CDA patch CD (Operating System Patch Recovery CD for UltraSPARC T2 Plus ProduOnly for use with the Solaris 10 8/07 OS) has been shipped with your server.

TABLE 2-4 Patch CD Components

Patch ID Description

124235-02 libpam.so.1 patch

125369-13 Fault Manager patch

125416-06 UFS utilities patch


38/118


The CD has been provided for recovery purposes in case you chose to install theSolaris 10 8/07 OS. Install the patches on the CD if you decide to replace theinstalled OS with Solaris 10 8/07.

Note The patches on the CD include an updated network driver that is required toenable use of the network interfaces on the SPARC Enterprise T5140 and T5240servers. After installing the Solaris 10 8/07 OS and the patches, network interfaceswill remain unconfigured. You can configure the network interfaces by running theSolaris sys-unconfig (1M) command or by configuring network options manually.See your Solaris 10 8/07 OS documentation.

Mandatory Patch Information For the Solaris 108/07 OSTABLE 2-5 identifies the mandatory patches for the Solaris 10 8/07 OS.

125476-02 libc_psr_hwcap.so.1 patch

126434-05 raidctl patch

127111-08 Kernel patch

TABLE 2-5 Mandatory Patches for the Solaris 10 8/07 OS


124235-02 or later libpam.so.1 patch

125369-13 or later Fault Manager patch

125416-06 or later UFS utilities patch

125476-02 or later libc_psr_hwcap.so.1 patch

126434-05 or later raidctl patch

127127-11 or later Kernel patch


TABLE 2-4 Patch CD Components



39/118


Mandatory Patch Information For the Solaris 15/08 OSTABLE 2-6 identifies the mandatory patches for the Solaris 10 5/08 OS.

Mandatory Patch Information For the Solaris 1

10/08 OSThere are no mandatory patches for the Solaris 10 10/08 OS at this time.

Mandatory Patch Information For the Solaris 15/09 OSThere are no mandatory patches for the Solaris 10 5/09 OS at this time.

To Download Patches1. Determine whether the patches you require have been installed on your

system.

For example, using the showrev command, type the following for each patnumber:

If you see patch information listed for the queried patch, and the dash exten(the last two digits) matches or exceeds the required version, your system haproper patches already installed. No further action is required.

For example, if patch 123456-16 or later is installed, your system has the reqversion of this patch.

TABLE 2-6 Mandatory Patches for the Solaris 10 5/08 OS



137291-01 or later n2cp driver patch

138048-01 or later nxge patch

# showrev -p | grep "Patch: 123456"


40/118


If you do not see patch information listed for the queried patch, or if the dashextension precedes the required version, go to Step 2.

For example, if no version of the 123456 patch, or a version with an extension of-15 or earlier is installed, you must download and install the new patch.

2. Access the above-mentioned web site to download the patches.

3. Follow the installation instructions provided in a specific patchs README file.

Patches for Option CardsIf you add option cards to your server, refer to the documentation and READMEfiles for each card to determine if additional patches are needed.

Installing the 4Gbps Fibre Channel card

Once you install the 4Gbps Fibre Channel card (SE0X7F11X, SE0X7F12X), the patchindicated below is required. Access the above-mentioned web site to download thepatch. Follow the installation instructions provided in the README file for thepatch.

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


41/118


General Functionality Issues andLimitationsThis section describes general issues known to exist at this release of the SPAREnterprise T5140 and T5240 servers.

Cryptographic FunctionIPsec encryption processing using the built-in encryption function of theUltraSPARC T2 Plus multi-core processor requires installation of the IPsec activpackage. Since Fujitsu currently does not support the IPsec activation package, encryption processing with the built-in encryption function of the UltraSPARCPlus multi-core processor is not available.

RAID FunctionA hardware RAID function is provided as standard in SPARC Enterprise T5140T5240 servers. However, with regard to data protection, reliability, and serviceabFujitsu does not support this function.

Fujitsu recommends use of software RAID functions for internal disks as specibelow:

PRIMECLUSTER GDS

Solaris Volume Manager (attached to Solaris OS)

Cable Management ArmThe SPARC Enterprise T5140 server doesn't support the cable management arm(CMA).

The following restrictions apply when using a CMA on SPARC Enterprise T52servers:

The maximum capacity of the CMA is as follows: AC input power model : 2 AC cables and 6 RJ45 cables

DC input power model : 6 DC cables and 6 RJ45 cables


42/118


Optical fiber cables cannot be accommodated in the CMA. Route the cablesthrough the free space on top of the CMA.

Cables with a cable core (such as SCSI cables) cannot be accommodated in theCMA. Route the cables through the free space on top of the CMA.

Moreover, if it hampers to install optional products that are subject to the followingstructural restriction, first uninstall and remove the CMA.

Cables with large connectors (such as for an XVR-300 or SAS card) must beconnected to the top PCIe slot.

SSD (Solid State Drive)SSD (Solid State Drive) is not currently supported.

Express Rail Rackmounting KitInstalling the servers with the express rail rackmounting kit is not supported.

SAS RAID Internal HBA CardSAS RAID Internal HBA Card is not currently supported.


43/118


Changed Behavior When Operating thSolaris OS With Logical Domains

This section describes the changes in behavior in using the Solaris OS that occuonce a configuration has been created by the Logical Domains Manager.

Note OpenBoot firmware is not available after the Solaris OS has started, beit is removed from memory. To reach the ok prompt from the Solaris OS, you mhalt the domain. You can use the Solaris OS halt command to halt the domain

Results from Halting or Rebooting the Control

DomainThe following table shows the expected behavior of halting or rebooting the co(primary) domain.

TABLE 2-7 Expected Behavior of Halting or Rebooting the Control (primary) Dom

Command Other Domain

Configured?

Behavior

halt No Host powered off and stays off until powered on at the

Yes Resets and boots up if the variable

auto-boot?=true. Resets and halts at ok prompt if thvariable auto-boot?=false.

reboot No Reboots the host, no power off.

Yes Reboots the host, no power off.

shutdowni5 No Host powered off, stays off until powered on at the SP.

Yes Resets and reboots.


44/118


Messages Identifying the Availability of CPUs asHot-Insertion EventsMessages referring to hot-insertion of CPUs can appear on the console and in thelogs. These messages are generated during initial system power on if the system hashad a firmware upgrade or system component change. These messages aregenerated only on systems with firmware version 7.1.3.d (or later). For example:

These messages display the available cores and threads on a system rather thanshowing the entire list of resources. If a CPU contains fewer than eight cores, themissing cores are not reported.

Components are automatically detected. The detections are described as hot-insertionevents. Once the components have been identified, no subsequent messages aredisplayed unless ILOM detects a change in the system configuration on a systemwith hot-pluggable CPU boards or if a CPU thread or core fails.

279 Mon Oct 27 11:26:31 2008 Chassis Action majorHot insertion of /SYS/MB/CMP0/CORE0278 Mon Oct 27 11:26:31 2008 Chassis Action majorHot insertion of /SYS/MB/CMP0/P7277 Mon Oct 27 11:26:31 2008 Chassis Action majorHot insertion of /SYS/MB/CMP0/P6276 Mon Oct 27 11:26:31 2008 Chassis Action majorHot insertion of /SYS/MB/CMP0/P5275 Mon Oct 27 11:26:31 2008 Chassis Action majorHot insertion of /SYS/MB/CMP0/P4

274 Mon Oct 27 11:26:31 2008 Chassis Action majorHot insertion of /SYS/MB/CMP0/P3273 Mon Oct 27 11:26:31 2008 Chassis Action majorHot insertion of /SYS/MB/CMP0/P2272 Mon Oct 27 11:26:31 2008 Chassis Action majorHot insertion of /SYS/MB/CMP0/P1271 Mon Oct 27 11:26:31 2008 Chassis Action majorHot insertion of /SYS/MB/CMP0/P0...


45/118


Processor Identification

Processor IDs Might Not Start at 0, and Might Not beContiguous

Different platforms and platforms of the same model might have different procIDs for identical configurations. For example, on UltraSPARC T1 CPU basedplatforms, the processor IDs start with processor ID 0. But other platforms, incluthose based on the UltraSPARC T2 Plus CPU, might not have a processor ID 0Solaris psrinfo command might display output similar to the following forplatforms based on the UltraSPARC T2 Plus processor:

The processor IDs exported to a guest domain on a platform running multiple domains with a virtual machine manager might represent a virtual abstractionWithin each guest domain, each processor ID visible to the software will be a uninteger value.

Software running in different guest domains on the same physical machine misee the same or different sets of virtual processor IDs. If domaining is enabled,virtual processor IDs and physical processor IDs are never the same. For inform

about the mapping between virtual and physical CPU numbers, see the latest LDomains (LDoms) Administration Guide.

Processor IDs are simply unique integer values in the domain where the softwrunning. The integer value will fit in the type processorid_t. Also refer to tp_online(2) man page.

8 on-line since 09/18/2007 21:26:259 on-line since 09/18/2007 21:26:30

16 on-line since 09/18/2007 21:26:3017 on-line since 09/18/2007 21:26:30


46/118


Notes on the Use of 200V Power SupplyFor the servers that have the B-type plug, confirm that a 15A overcurrent protectiondevice is available outside the server. If one is not available, prepare an external 15A

overcurrent protection that can be achieved by means of no-fuse breakers (NFBs) orfuses. The B-type plug refers to plugs other than grounding-type ones with twoparallel 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 serviceengineer.


47/118

CHAPTER 3

Known Issues

This chapter describes known issues about the SPARC Enterprise T5140 and T5servers.

The following sections are included in this chapter:

Hardware and Mechanical Issues on page 35

Solaris OS Issues on page 42

Integrated Lights Out Manager (ILOM) Issues on page 49

Note For the issues already fixed in the latest version of Solaris OS or SysteFirmware, see Appendix A. For the latest version to be supported, see SuppoVersions of Solaris and System Firmware on page 18.

Hardware and Mechanical IssuesThis section describes hardware issues known to exist at this release of the SPAEnterprise T5140 and T5240 servers.

Hot-Swapping Fan ModulesWhen removing a fan module, hold the adjacent fan module in place to avoidunintentionally dislodging the adjacent fan module.


48/118


Unexpected LED BehaviorAn unexpected LED behavior occurs when you create a RAID volume using internaldrives. All of the LEDs on the disks in the volume blink at the same time aboutevery 16 seconds. This behavior is normal and can be ignored.

Onboard Ethernet PortThe onboard Ethernet port of the SPARC Enterprise T5140/T5240 does not supporthalf duplex transfer at any of the speeds of 10M/100M/1000M.Therefore, connect it to a switch/hub that supports full duplex transfer.

TABLE 3-1 Hardware-Related Issues on the SPARC Enterprise T5140 and T5240 Servers

CR ID Description Workaround

6651885 A kernel panic can occur under any of four rare

hardware error conditions IngressHeaderBuffer (IHB) parity error EgressHeaderBuffer (EHB) parity error EgressDataBuffer (EDB) parity error Link-down transitionIf any of these errors occur, then a softwareinitiated reboot of the domain will fail.The failure symptom will be no that there is noPCI device in the OpenBoot PROM device tree.OpenBoot software will not be able to boot thedomain automatically.

Power the system off then power it on again

from the service processor. This action permitsthe automated reboot to proceed normally. Adiagnostic process will run, identifying anyfaulty hardware.

6654466 DRAM scrub errors can occur withoutproducing error reports.

6668745 The DC output value reported by the ILOMV_DC_MAIN and OUTPUT_POWER properties (orby the ALOM compatibility shellsshowpower v and showenvironmentcommands) for power supplies in SPARCEnterprise T5240 servers is incorrect. Thereported value is 87.5% of the actual value. Thisissue does not affect SPARC Enterprise T5140servers.

n/a An RJ45 cable may sometimes be difficult todisconnect from an RJ45 port of an Ethernet cardmounted in the SPARC Enterprise T5140.

In this event, disconnect the cable while keepingthe RJ45 cable connector tab depressed, such aswith a plastic card.


49/118

Chapter 3 Known Issues

6581309 To use the XVR-300 as a console of the SPARCEnterprise T5xx0, patch 137111-01 or later must

be applied.If the patch is applied after the OBP variable has

been changed to use the XVR-300 as the console,console output will revert to the default ILOMconsole during the Solaris boot sequence.

To use the XVR-300 as a console, apply patc137111-01 or later to the Solaris OS beforechanging the OBP variable.Alternatively, install the Solaris OS (or reinsit) with ILOM set as the console used, and tapply the patch.No GUI can be used during that time.After the patch has been applied, the XVR-3can be used as the console as soon as the OBvariable is changed.

n/a XAUI card disables an On-board network port.For details, see XAUI Card Disables anOnboard Network Port on page 38.

6677336 When removing or replacing the air duct, thecapacitor on the DC to DC converter can bedamaged.

Use care not to hit or shock components on motherboard while removing or replacing t

air duct.

66879156687916

Components inside the chassis get hot and somecomponents have sharp edges.

When servicing the server, be careful workiinside the chassis. For example, let the servecool down for a few minutes before performservice procedures, and avoid contact with heat sink on the motherboard.

67137736724347

A fault in the XAUI card causes the built-inEthernet port to be unusable.If, in an environment where an XAUI card isinstalled, the XAUI card becomes faulty, notonly the XAUI card, but also the built-in

Ethernet port (component name MB/GBE) isdisabled during a POST run. As a result, thebuilt-in Ethernet port becomes unusable.

None.For display samples and recovery procedureA Fault in the XAUI Card Causes the BuiltEthernet Port to Be Unusable (CR 6713773,6724347) on page 39.

6706976 At write to CD/DVD media, there may be caseswhere the writing speed may not reach themaximum speed supported by the CD/DVDdrive. Even if the maximum operation is notreached, there are no problems in the processingfor writing to the CD/DVD media.

Use the media as is.

n/a When the system is initialized, firmware isloaded and occupies approximately 128 MB to352 MB of the host memory.

The banner and other software utilities report anamount of memory minus the amount ofmemory that is occupied by firmware.

Be aware that the banner reports the amounmemory less the amount used by the firmw

TABLE 3-1 Hardware-Related Issues on the SPARC Enterprise T5140 and T5240 Servers (Continued)



50/118


XAUI Card Disables an Onboard Network PortInstalling a 10GbE XFP XAUI Adapter Card (XAUI card) in slot 0 disables on-boardnetwork port 1 (NET1)(*1). Installing the XAUI card in slot 1 disables on-boardnetwork port 0 (NET0)(*2).

n/a The On/Standby portion of the service labelcontains an error. It says to press and hold theOn/Standby button for 5 seconds. It shouldsay 4 seconds.

Note -- This error appears on all SPARCEnterprise T5140 and T5240 serverconfigurations.

n/a Two illustrations in the service label show thetop cover button in the wrong location. The

button is near the right edge of the server.

Note -- This error appears on all SPARCEnterprise T5140 and T5240 servers.

n/a The portion of the service label that cautionsabout the weight of the server gives the wrongweight. It should say 42 lb and 19 kg.

Note -- This error appears on SPARC EnterpriseT5140 server configurations.

n/a In the Interior Service Label CRU and FRUProcedures portion of the service label, theletters PBD should say PDB.

Note -- This error appears on all SPARCEnterprise T5140 and T5240 servers.

n/a The FM Status Indicator portion of the service

label has an erroneous statement. Where it says,In front of FM on FanBD it should say, on topof FM.

Note -- This error appears on SPARC Enterprise

T5240 server configurations.

n/a The drawing showing the cable managementarm being rotated represents the wrong servermodel. It should show the SPARC EnterpriseT5240 server.

Note -- This error appears on SPARC EnterpriseT5240 server configurations.

n/a The shapes of anti-tilt legs shown on servicelabels may be different, depending on racks.

Note - This error appears on all SPARCEnterprise T5140 and T5240 servers.

TABLE 3-1 Hardware-Related Issues on the SPARC Enterprise T5140 and T5240 Servers (Continued)



51/118


FIGURE 3-1 XAUI cards and on-board network ports

A Fault in the XAUI Card Causes the Built-in EthernePort to Be Unusable (CR 6713773, 6724347)A fault in the XAUI card causes the built-in Ethernet port to be unusable.

If, in an environment where an XAUI card is installed, the XAUI card becomesfaulty, not only the XAUI card, but also the built-in Ethernet port (component nMB/GBE) is disabled during a POST run. As a result, the built-in Ethernet por

becomes unusable.

TABLE 3-2 Network Ports and Device Names

On-board network XAUI Slot Device name

NET 0 XAUI 1 nxge0

NET 1 XAUI 0 nxge1

PCI 3 PCI 4 PCI 5

PCI 0/XAUI 0 PCI 1/XAUI 1 PCI 2

NET0 NET1 NET2 NET3

*2

*1

=2U devic


52/118


Workaround: None.

Recovery procedure: Replace the XAUI card by using the following procedure:

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

T5140, No KeyboardCopyright 2008 Sun Microsystems, Inc. All rights reserved.OpenBoot 4.28.6, 32544 MB memory available, Serial #XXXXXXXX.Ethernet address XX:XX:XX:XX:XX:XX, Host ID: XXXXXXXX.

ERROR: The following devices are disabled:MB/RISER1/XAUI1 *The number varies with the layout.MB/GBE *The built-in Ethernet port is disabled.

{0} ok{0} ok show-nets *No longer displayed because the built-in Ethernet port is faulty.{0} ok

-> show faultyTarget | Property | Value--------------------+------------------------+---------------------------------/SP/faultmgmt/0 | fru | /SYS/MB/RISER1/XAUI1/SP/faultmgmt/0 | timestamp | Jun 10 13:02:34/SP/faultmgmt/0/ | timestamp | Jun 10 13:02:34faults/0 | |/SP/faultmgmt/0/ | sp_detected_fault | /SYS/MB/RISER1/XAUI1 Disabledfaults/0 | | by CLI action./SP/faultmgmt/1 | fru | /SYS/MB/SP/faultmgmt/1 | timestamp | Jun 10 13:09:25

/SP/faultmgmt/1/ | timestamp | Jun 10 13:09:25faults/0 | |/SP/faultmgmt/1/ | sp_detected_fault | /SYS/MB/GBE Forced fail (POST)faults/0 | |* The built-in Ethernet port is faulty.


53/118


set /SYS/MB/GBE component_state=enabled

3. Disconnect the power cable from the AC outlet.

4. Replace the XAUI card.

5. Connect the power cable to the AC power source.

1. Execute the poweroff command.

2. Delete the XAUI and GBE components from the asr-db blacklist.

Execution example:

enablecomponent /SYS/MB/RISER1/XAUI1

enablecomponent /SYS/MB/GBE

Alternatively, execute the clearasrdb command.

3. Disconnect the power cable from the AC outlet.

4. Replace the XAUI card.

5. Connect the power cable to the AC power source.


54/118


Solaris OS IssuesThis section describes Solaris OS issues known to exist at this release of the SPARCEnterprise T5140 and T5240 servers.

TABLE 3-3 Solaris OS-Related Issues on the SPARC Enterprise T5140 and T5240 Servers


n/a While booting SPARC EnterpriseT5240 server (16 HDD type), mptdriver outputs the followingWARNING message:Encode devid failed for pathtarget:##, lun:#, SASaddress:################

This message shows the failure in the setting of the SESdevice installed in SPARC Enterprise T5240 server (16 HDDtype). Because this device is not used, you can ignore thismessage.

n/a In SPARC Enterprise T5140/T5240servers, when rebooting is repeatedlyexecuted, the following WARNINGmessages might be stored in/var/adm/messages.px: [ID 781074 kern.warning]

WARNING: px0: spuriousinterrupt from ino 0x13px: [ID 548919 kern.info] su-0#0px: [ID 100033 kern.info]

This message shows that interrupt without the reason wasdetected when su (serial port) driver processes interrupt.Because this message doesn't influence the system, you candisregard this message.

6718841 Sun Explorer may fail to collect theILOM data (Tx000). If failed, it maytake more than 30 minutes to returnan error.

You can collect the ILOM data (Tx000) in another way.

For details, see Sun Explorer May Fail to Collect the ILOMData (Tx000) (CR 6718841) on page 45.


55/118


6734788 A panic may occur while theCD/DVD test (cddvdtest) includedwith the SunVTS software is runninga hardware diagnosis on the DVD

drive.This symptom might happen even ifDVD drive is not used.

Only use the DVD drive to install the Solaris OS or softor to apply a patch or PTF (Program Temporary Fix). stop vold(1M) if the system is running. Stop of vold(1doesn't disrupt the system operation.

To stop vold(1M), disable the volfs service, which is a service.# svcadm disable volfs

To use removable devices such as DVD, execute thefollowing.# svcadm enable volfs

n/a System shutdown may fail. Do not attempt a shutdown before boot processing iscompleted.Start shutdown processing after ensuring that bootprocessing is completed or waiting for an adequate peof time (at least 10 minutes).

TABLE 3-3 Solaris OS-Related Issues on the SPARC Enterprise T5140 and T5240 Servers (Continued)



56/118


6836653 USB SATA DVD drive is notsupported for the following versionsof the Solaris OS: Solaris 10 8/07 OS Solaris 10 5/08 OSNote - USB SATA DVD drive issupported for the later versions of theSolaris 10 OS, beginning with Solaris10 10/08 OS.

To install Solaris 10 8/07 OS or Solaris 10 5/08 OS on aserver equipped with a USB SATA DVD drive, install theOS from the install server and apply the mandatorypatches, the latest periodic PTF, and the latest

recommended security patches.

When installing the Solaris 10 8/07 OS, follow the patchapplication procedure which is stored in the OperatingSystem Patch Recovery CD attached to the server and applythe patches to the install image before the installation.When installing the Solaris 10 5/08 OS, there are no patchesyou should apply to the install image.For the installation procedures, see Notes on InstallingSolaris 10 8/07 OS and Solaris 10 5/08 OS on page 46.

For servers shipped after September 2009, the USB SATA

DVD drive unit has been mounted. Confirm whether aUSB SATA DVD drive unit is mounted on your server byusing either of the following methods. Confirm that the "SATA DVD" mark appears on the front

side of the DVD drive. Confirm that specific part numbers are displayed in the

output for the following ILOM/ALOM commands.

[Confirm by using ILOM command]Confirm whether either of the following part numbers isdisplayed in the output from ls /SYS/PADCRD command.

fru_part_number = 5413512orfru_part_number = 5413513

[Confirm by using ALOM command]Confirm whether either of the following part numbers isdisplayed in the output from showfru /SYS/PADCRDcommand.

/Partner_Part_NumberR/Partner_Part_Number:CF005413512REVxx

or

/Partner_Part_NumberR/Partner_Part_Number:CF005413513REVxx

TABLE 3-3 Solaris OS-Related Issues on the SPARC Enterprise T5140 and T5240 Servers (Continued)



57/118


Sun Explorer May Fail to Collect the ILOM Da(Tx000) (CR 6718841)Sun Explorer may fail to collect the ILOM data (Tx000).If failed, it may take more than 30 minutes to return an error.

Workaround: You can collect the ILOM data (Tx000) in another way.1. Specify the option as follows.

2. Confirm the version of ILOM.

Depending on the version of ILOM, the data collection method varies.

How to check the version

- ILOM mode

- ALOM mode

3. Collect the ILOM data (Tx000).

In ILOM 3.0 or later

In the Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, refer to t"Collect SP Data to Diagnose System Problems" section to collect the SP datinformation.

In ILOM 2.x or earlierCollect the ILOM and ALOM data and supply it to service engineers along the Sun Explorer output.

a. Collect the following data on ILOM.

# /opt/SUNWexplo/bin/explorer -w !Tx000

->versionSP firmware 3.0.3.20.c

~

sc> showsc versionSP firmware version: 3.0.3.20.c

~


58/118


show /SP/usersshow /SP/users/adminshow /HOST

b. Create an ALOM compatible user and collect the following data on ALOM.

consolehistory -vshowcomponentshowdateshowenvironmentshowfaults -vshowfrushowhostshowkeyswitchshowlogs -v -g 0 -p p

shownetworkshowplatform -vshowscshowsc version -v

showusers

c. Reset ILOM.

Notes on Installing Solaris 10 8/07 OS and Solaris 105/08 OS

USB SATA DVD drive is not supported for the Solaris 10 8/07 OS and Solaris 105/08 OS.To install Solaris 10 8/07 OS or Solaris 10 5/08 OS on a server equipped with a USBSATA DVD drive, install the OS from the install server and apply the mandatorypatches, the latest periodic PTF, and the latest recommended security patches.

When installing the Solaris 10 8/07 OS, follow the patch application procedurewhich is stored in the Operating System Patch Recovery CD attached to the serverand apply the patches to the install image before the installation.

When installing the Solaris 10 5/08 OS, there are no patches you should apply to the

install image.

-> reset /SPAre you sure you want to reset /SP (y/n)?yPerforming hard reset on /SP


59/118


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'.

2. Apply the patches to the install image.When installing the Solaris 10 5/08 OS, proceed to Step 3. There are no patcyou should apply to the install image.

In case of Solaris 10 8/07 OS

Follow the patch application procedure which is stored in the OperatingSystem Patch Recovery CD attached to the server and apply the patches tinstall image.

3. Install the OS from the install server.

# mkdir -p /export/home/dvd# cd /cdmnt/Solaris_10/Tools# ./setup_install_server /export/home/dvd# share |grep /export/home/dvd# share -F nfs -o ro,anon=0 -d "install server directory" /export/home/dvd# svcs -l svc:/network/nfs/server:default# svcadm enable svc:/network/nfs/server# shareall# cd /# eject cdrom

# 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*# cp -R /cdmnt/Solaris_10/Patches/* Solaris_10/Patches# ls Solaris_10/Patches124235-02 125369-13 125416-06 125476-02 126434-05 127111-08


60/118


4. Apply the latest periodic PTF and the latest recommended security patches.

The mandatory patches which are described in the Patch Information onpage 25 are collected into the periodic PTF R08111 or later. From the viewpoint ofpreventive maintenance, apply the latest periodic PTF and the latestrecommended security patches.

To apply the minimum mandatory patches only, apply the patches in the

following order. In case of Solaris 10 8/07 OS

In case of Solaris 10 5/08 OS

5. Restart the OS.

# LANG=C;export LANG# patchadd 119254-51# patchadd 125891-01# patchadd 127755-01# patchadd 127127-11# patchadd 137111-01

# LANG=C;export LANG# patchadd 138048-01# patchadd 137111-01

# shutdown -i6 -g0 -y


61/118


62/118


6760139 ILOM firmware and OpenBoot PROM (OBP)setting information may not be inherited duringmotherboard replacement.

If an ILOM firmware initialization has beenperformed or any of the firmware settings have

been changed, follow the procedure below tosave the latest ILOM firmware setting

information. After replacing the motherboard,set the saved setting information again.(Procedure for saving ILOM firmware settinginformation)1) Log in to ILOM, execute the following

commands, and save the displayed results:-> show /SP -level all -o table-> show /SYS -o table-> show /HOST -level all -o table

2) Log in to the ALOM CMT compatibilityshell, execute the following command, andsave the displayed results:

sc> showsc

6752910 After a host power-on instruction is executedfrom ILOM, the POST (self-diagnostics test) maynot start, and processing may not go to OS bootprocessing or the ok prompt for OpenBootPROM (OBP).For details, see After a Host Power-OnInstruction is Executed from ILOM, the POSTMay Not Start, and Processing May Not Go toOS Boot Processing or the ok Prompt (CR6752910) on page 55.

After turning off the power to the host, wait atleast three minutes before turning it on again.

6794877 At the first power on after the power cable hasbeen connected, the ILOM event log may beoutput. For example:IPMI |minor: "ID =7d1: Voltage :/MB/V_VTTL : Lower Non-critical

going low : reading 0.83 threshold 0.73 Volts"

None.Because this message doesn't influence thesystem, you can disregard this message.

TABLE 3-4 ILOM-Related Issues on the SPARC Enterprise T5140 and T5240 Servers (Continued)



63/118


6815369 For DC input power models, /PS0/AC_POKand /PS0/DC_POK identify sensors in thepower supply units. /PS0/AC_POK does notrepresent an AC power supply unit. For

examples, see For DC Input Power Models,/PS0/AC_POK Is Displayed (CR 6815369) onpage 57.

None.

6723410 If you repeat in sequence a login to the serviceprocessor, executing a command, and loggingout, logout may fail.

If this problem occurs, terminate the loginsession on the client from which you haveaccessed the service processor.

6746677 According to the IPMI PET warning and SNMPtrap warning settings in the warning rulesettings, warning message creation may not bepossible depending on the event type,irrespective of the warning level. All generatedevents can be confirmed with show/SP/logs/event/list or showlogs.

None.See According to the IPMI PET Warning anSNMP Trap Warning Settings in the WarninRule Settings, Warning Message Creation mnot be Possible Depending on the Event Typ

(CR 6746677) on page 58.

6726663 In ILOM mode, or through access to the ILOMWeb, it may be possible to change the systemtime when the system is powered on.

In ILOM mode, be sure not to change theproperties displayed below at power on so not to change the system time directly or enNTP services.-> show /SP/clock/SP/clock

Targets:

Properties:datetime = Wed Dec 3 06:22:48 usentpserver = disabled

Commands:

cdsetshow

->

6624705 When a component set disable by using"Component Management" of BUI, on the screenof an ALOM mode log-in user, a messageappears which supposed to be shown when thecommand executed from CLI.Fault | critical: SP detected fault at

time Wed Jul 18 09:37:15 2007./SYS/MB/GBE1 Disabled by CLI action.

None.




64/118


6806268 The flashupdate (ALOM CMT command)with the -v option doesn't display the details ofthe execution result.The -v option exists to maintain compatibilitywith the earlier ALOM. The -v option specifieddoesn't affect the system firmware downloadand update. The result shows no details and will

be the same as the execution result without theoption.

None.

6823561 In the back up and restore functions of ILOMsettings, you cannot set "https" to the protocolfor data transfer (transfer_methodproperty).

Example:

-> set dump_uri=https://ipaddres/directory/filename

set: Unable to transfer image,please check URI

None.Use other protocols (tftp, ftp, sftp, scp, http).

6830397 In ILOM3.0, you cannot set "service" to the/HOST/diag mode property or the diag_modeproperty of the ALOM CMT compatible shell. Ifyou set, it is displayed as "unknown."

None.The following settings offer the POST diagnosisin a mode equivalent to the "service."/HOST/diag mode = normal

/HOST diag level = max

/HOST verbosity = max

6829248 The alert rule configuration using the SNMPtrap fails in the filtering of alert levels.When you select theminor or any upper levels,alerts of all levels will be notified to the SNMPtrap.

None.

6836426 In the Logical Domains environment, after thehost reset operation, host may be reset again.For the example, see In the Logical DomainsEnvironment, After the Host Reset Operation,Host May Be Reset Again (CR 6836426) onpage 59.

None.The second reset has no impact on the system.




65/118

8/6/2019 T5140T5240 Product Notes e

t5140t5240 product notes en 06

Documents