SPARC Enterprise T5120 and T5220 Servers Product Notes

SPARC Enterprise T5120 and T5220 Servers Product Notes
SPARC Enterprise™
T5120 and T5220 Servers
Product Notes
Manual Code C120-E458-10EN
Part No. 875-4189-20
November 2010, Revision C
Copyright © 2007, 2010, Oracle and/or its affiliates and FUJITSU LIMITED. All rights reserved.
Oracle and/or its affiliates and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in this
document, and such products, technology and this document are protected by copyright laws, patents, and other intellectual property laws and
international treaties.
This document and the product and technology to which it pertains are distributed under licenses restricting their use, copying, distribution, and
decompilation. No part of such product or technology, or of this document, may be reproduced in any form by any means without prior written
authorization of Oracle and/or its affiliates and Fujitsu Limited, and their applicable licensors, if any. The furnishings of this document to you does not
give you any rights or licenses, express or implied, with respect to the product or technology to which it pertains, and this document does not contain or
represent any commitment of any kind on the part of Oracle or Fujitsu Limited, or any affiliate of either of them.
This document and the product and technology described in this document may incorporate third-party intellectual property copyrighted by and/or
licensed from the suppliers to Oracle and/or its affiliates and Fujitsu Limited, including software and font technology.
Per the terms of the GPL or LGPL, a copy of the source code governed by the GPL or LGPL, as applicable, is available upon request by the End User. Please
contact Oracle and/or its affiliates or Fujitsu Limited.
This distribution may include materials developed by third parties.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and
in other countries, exclusively licensed through X/Open Company, Ltd.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Fujitsu and the Fujitsu logo are registered trademarks of Fujitsu Limited.
All SPARC trademarks are used under license and are registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing
SPARC trademarks are based upon architectures developed by Oracle and/or its affiliates. SPARC64 is a trademark of SPARC International, Inc., used
under license by Fujitsu Microelectronics, Inc. and Fujitsu Limited. Other names may be trademarks of their respective owners.
United States Government Rights - Commercial use. U.S. Government users are subject to the standard government user license agreements of Oracle
and/or its affiliates and Fujitsu Limited and the applicable provisions of the FAR and its supplements.
Disclaimer: The only warranties granted by Oracle and Fujitsu Limited, and/or any affiliate of either of them in connection with this document or any
product or technology described herein are those expressly set forth in the license agreement pursuant to which the product or technology is provided.
EXCEPT AS EXPRESSLY SET FORTH IN SUCH AGREEMENT, ORACLE OR FUJITSU LIMITED, AND/OR THEIR AFFILIATES MAKE NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND (EXPRESS OR IMPLIED) REGARDING SUCH PRODUCT OR TECHNOLOGY OR THIS
DOCUMENT, WHICH ARE ALL PROVIDED AS IS, AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Unless
otherwise expressly set forth in such agreement, to the extent allowed by applicable law, in no event shall 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.
DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Please
Recycle
Copyright © 2007, 2010, Oracle et/ou ses sociétés affiliées et FUJITSU LIMITED. Tous droits réservés.
Oracle et/ou ses sociétés affiliées et Fujitsu Limited détiennent et contrôlent chacune des droits de propriété intellectuelle relatifs aux produits et
technologies décrits dans ce document. De même, ces produits, technologies et ce document sont protégés par des lois sur le copyright, des brevets,
d’autres lois sur la propriété intellectuelle et des traités internationaux.
Ce document, le produit et les technologies afférents sont exclusivement distribués avec des licences qui en restreignent l’utilisation, la copie, la
distribution et la décompilation. Aucune partie de ce produit, de ces technologies ou de ce document ne peut être reproduite sous quelque forme que ce
soit, par quelque moyen que ce soit, sans l’autorisation écrite préalable 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é fourni, ne vous confère aucun droit et aucune licence, expresses ou tacites, concernant le produit
ou la technologie auxquels il se rapporte. Par ailleurs, il ne contient ni ne représente aucun engagement, de quelque type que ce soit, de la part d’Oracle ou
de Fujitsu Limited, ou des sociétés affiliées de l’une ou l’autre entité.
Ce document, ainsi que les produits et technologies qu’il décrit, peuvent inclure des droits de propriété intellectuelle de parties tierces protégés par
copyright et/ou cédés sous licence par des fournisseurs à Oracle et/ou ses sociétés affiliées et Fujitsu Limited, y compris des logiciels et des technologies
relatives aux polices de caractères.
Conformément aux conditions de la licence GPL ou LGPL, une copie du code source régi par la licence GPL ou LGPL, selon le cas, est disponible sur
demande par l’Utilisateur final. Veuillez contacter Oracle et/ou ses sociétés affiliées ou Fujitsu Limited.
Cette distribution peut comprendre des composants développés par des parties tierces.
Des parties de ce produit peuvent être dérivées des systèmes Berkeley BSD, distribués sous licence par l’Université de Californie. UNIX est une marque
déposée aux États-Unis et dans d’autres pays, distribuée exclusivement sous licence par X/Open Company, Ltd.
Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses sociétés affiliées. Fujitsu et le logo Fujitsu sont des marques déposées de
Fujitsu Limited.
Toutes les marques SPARC sont utilisées sous licence et sont des marques déposées de SPARC International, Inc., aux États-Unis et dans d’autres pays. Les
produits portant la marque SPARC reposent sur des architectures développées par Oracle et/ou ses sociétés affiliées. SPARC64 est une marque de SPARC
International, Inc., utilisée sous licence par Fujitsu Microelectronics, Inc. et Fujitsu Limited. Tout autre nom mentionné peut correspondre à des marques
appartenant à d’autres propriétaires.
United States Government Rights - Commercial use. U.S. Government users are subject to the standard government user license agreements of Oracle
and/or its affiliates and Fujitsu Limited and the applicable provisions of the FAR and its supplements.
Avis de non-responsabilité : les seules garanties octroyées par Oracle et Fujitsu Limited et/ou toute société affiliée de l’une ou l’autre entité en rapport avec
ce document ou tout produit ou toute technologie décrits dans les présentes correspondent aux garanties expressément stipulées dans le contrat de licence
régissant le produit ou la technologie fournis. SAUF MENTION CONTRAIRE EXPRESSÉMENT STIPULÉE DANS CE CONTRAT, ORACLE OU FUJITSU
LIMITED ET LES SOCIÉTÉS AFFILIÉES À L’UNE OU L’AUTRE ENTITÉ REJETTENT TOUTE REPRÉSENTATION OU TOUTE GARANTIE, QUELLE
QU’EN SOIT LA NATURE (EXPRESSE OU IMPLICITE) CONCERNANT CE PRODUIT, CETTE TECHNOLOGIE OU CE DOCUMENT, LESQUELS
SONT FOURNIS EN L’ÉTAT. EN OUTRE, TOUTES LES CONDITIONS, REPRÉSENTATIONS ET GARANTIES EXPRESSES OU TACITES, Y COMPRIS
NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE À LA QUALITÉ MARCHANDE, À L’APTITUDE À UNE UTILISATION PARTICULIÈRE
OU À L’ABSENCE DE CONTREFAÇON, SONT EXCLUES, DANS LA MESURE AUTORISÉE PAR LA LOI APPLICABLE. Sauf mention contraire
expressément stipulée dans ce contrat, dans la mesure autorisée par la loi applicable, en aucun cas Oracle ou Fujitsu Limited et/ou l’une ou l’autre de leurs
sociétés affiliées ne sauraient être tenues responsables envers une quelconque partie tierce, sous quelque théorie juridique que ce soit, de tout manque à
gagner ou de perte de profit, de problèmes d’utilisation ou de perte de données, ou d’interruptions d’activités, ou de tout dommage indirect, spécial,
secondaire ou consécutif, même si ces entités ont été préalablement informées d’une telle éventualité.
LA DOCUMENTATION EST FOURNIE « EN L’ÉTAT » ET TOUTE AUTRE CONDITION, DÉCLARATION ET GARANTIE, EXPRESSE OU TACITE, EST
FORMELLEMENT EXCLUE, DANS LA MESURE AUTORISÉE PAR LA LOI EN VIGUEUR, Y COMPRIS NOTAMMENT TOUTE GARANTIE
IMPLICITE RELATIVE À LA QUALITÉ MARCHANDE, À L’APTITUDE À UNE UTILISATION PARTICULIÈRE OU À L’ABSENCE DE
CONTREFAÇON.
Contents
Preface
1.
ix
New Information About the SPARC Enterprise T5120 and T5220 Servers
Important New Information About the T5120 and T5220 Servers
RFID Tag
1
2
2
New Information About Known Issues
3
Firmware, ILOM, POST, and SP Issues
3
Service Required LED May Turn On Due To False Recognition of Fan
Speed (CR 6989852) 3
2.
Important Information About the SPARC Enterprise T5120 and T5220 Servers
7
Notes on DVD Drive and Discs
7
Supported Versions of the OS and Firmware
8
Solaris OS and Firmware Requirements for Certain Features
System Firmware Update
9
10
Support for Windows 7 and Internet Explorer 8
10
Change and Functional Enhancement in System Firmware 7.2.8
About the Change of Host Console Target
10
About the Addition of Protocols for Firmware Update
Preinstalled Software
10
11
12
v
Solaris 10 OS and Solaris Live Upgrade
13
Additional Software Available for Your Server – Cool Tools
Logical Domains
14
Supported Sun Explorer Utility Version
14
Sun Studio C, C++ & Fortran Compilers and Tools
Mandatory Patch Information
16
Mandatory Patches for the Solaris 10 5/08 OS
16
Mandatory Patches for the Solaris 10 10/08 OS
Mandatory Patches for the Solaris 10 5/09 OS
To Download Patches
16
Patches for Option Cards
17
16
16
Installing the Fujitsu 4Gbps Fibre Channel Card
General Functionality Issues and Limitations
Cryptographic Function
18
18
20
Express Rail Rackmounting Kit
SAS RAID Internal HBA Card
Support for SSD Storage
17
18
Support for RAID Function
Cable Management Arm
15
15
Mandatory Patches for the Solaris 10 8/07 OS
▼
13
20
20
20
Using a SSD as a Boot Device
21
About the Cache Setting of SSDs
21
About the Estimated Usable Period of SSDs
22
About the Preventive Replacement Monitoring Function of SSD
About the SSD Use on the 16-Disk Backplane Model
22
Updating LSI 1068e Controller Firmware to Support SSDs
Processor Identification
23
Notes on the Use of 200V Power Supply
vi
24
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
23
22
3.
Known Issues
25
Hardware and Mechanical Issues
26
Ethernet Interface Related Issues
30
Firmware, ILOM, POST, and SP Issues
Solaris OS Issues
58
LDoms Related Issues
4.
32
Documentation Errata
62
63
SPARC Enterprise T5120 and T5220 Servers Site Planning Guide
63
Error on page 2 in "Minimum Clearance for Service Access"
Incorrect Values for the 1.6 GHz SpecJBB Test
Incorrect Idle Input Power Values
63
66
67
SPARC Enterprise T5120 and T5220 Servers Installation Guide
68
Verify Proper Seating of Preinstalled PCIe/XAUI Cards
SPARC Enterprise T5120 and T5220 Servers Service Manual
68
68
Erroneous Description in the Section "Disconnect Power Cords From the
Server" 68
Erroneous Description in the Section "Removing the Air Duct" on page 101
69
Erroneous Description in "Fan Module Configurations for SPARC Enterprise
T5220 Servers (8- and 16-Disk Capable)" 70
Unnecessary Procedure in "Install the Hard Drive Cage"
70
Incorrect FRU Name is Specified in the TABLE: Motherboard Components
(SPARC Enterprise T5120 Servers) 70
Incorrect FRU Name is Specified in the TABLE: Motherboard Components
(SPARC Enterprise T5220 Servers) 71
SPARC Enterprise T5120 and T5220 Servers Administration Guide
Notes on the "SPARC Enterprise T5x20 Device Tree"
Integrated Lights Out Manager 2.0 User's Guide
71
71
71
Incorrect ILOM Command Related to IP Address Assignment
71
Contents
vii
The Command in the Section "Edit an SNMP User Account Using the CLI" on
Page 195 is Incorrect 72
Integrated Lights Out Manager 2.0 Supplement for the SPARC Enterprise T5120 and
T5220 Servers 72
Points of Concern about the Connection of ILOM (CR 6806789)
About ALOM CMT Shell Command
72
72
Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide
73
Erroneous Description in "Collect SP Data to Diagnose System Problems" (CR
6806800) 73
Erroneous Default Value for /SP/clients/dns
73
Erroneous Description about Collecting SP Data
New URL for Downloading System Firmware
74
74
Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide
Erroneous Description about Collecting SP Data
New URL for Downloading System Firmware
74
74
75
Integrated Lights Out Manager (ILOM) 3.0 Supplement for SPARC Enterprise T5120
and T5220 Servers 75
Notes on "ILOM Information Stored on the SCC"
A.
Fixed Issues
77
Hardware and Mechanical Issues
77
Ethernet Interface Related Issues
79
Firmware, ILOM, POST, and SP Issues
Solaris OS Issues
127
LDoms Related Issues
viii
86
146
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
75
Preface
These product notes contain late-breaking information about the SPARC Enterprise
T5120 and T5220 servers hardware, software, or documentation errata that became
known after the documentation set was published.
■
“Support for the SPARC Enterprise T5120 and T5220 Servers” on page ix
■
“Fujitsu Welcomes Your Comments” on page x
Support for the SPARC Enterprise T5120
and T5220 Servers
Technical Support
If you have any technical questions or issues that are not addressed in the SPARC
Enterprise T5120 or T5220 servers documentation, contact a sales representative or a
certified service engineer.
Downloading Documentation
Instructions for installing, administering, and using your servers are provided in the
SPARC Enterprise T5120 and T5220 servers documentation sets. The entire
documentation set is available for download from the following web site:
Global Site
http://www.fujitsu.com/sparcenterprise/manual/
ix
North American Site
https://download.computers.us.fujitsu.com/
Japanese Site
http://primeserver.fujitsu.com/sparcenterprise/manual/
Note – Information in these product notes supersedes the information in the SPARC
Enterprise T5120 and T5220 documentation sets.
Fujitsu Welcomes Your Comments
If you have any comments or requests regarding this document, or if you find any
unclear statements in the document, please state your points specifically on the form
at the following URL.
For Users in U.S.A., Canada, and Mexico:
http://www.computers.us.fujitsu.com/www/support_servers.shtml?support/servers
For Users in Other Countries:
SPARC Enterprise contact
http://www.fujitsu.com/global/contact/computing/sparce_index.html
x
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
CHAPTER
1
New Information About the SPARC
Enterprise T5120 and T5220 Servers
This chapter describes new information about the SPARC Enterprise T5120 and
T5220 servers that was not documented in the previous edition of the SPARC
Enterprise T5120 and T5220 Servers Product Notes.
The following sections are included in this chapter:
■
“Important New Information About the T5120 and T5220 Servers” on page 2-This section describes important new information about the T5120 and T5220
servers.
■
“New Information About Known Issues” on page 3-- This section describes
technical issues that were identified after the previous edition was published.
Information that was documented in the previous edition of this document is
provided in the following locations:
■
Chapter 2 contains important information about the T5120 and T5220 servers.
■
Chapter 3 describes technical issues.
■
Chapter 4 describes documentation issues.
■
Appendix A describes fixed technical issues.
1
Important New Information About the
T5120 and T5220 Servers
This section describes new capabilities that are supported on the SPARC Enterprise
T5440 server.
■
“RFID Tag” on page 2
For information about the capabilities that have been supported at the release of the
previous edition, see the following sections.
■
“Support for RAID Function” on page 18
■
“Support for SSD Storage” on page 20
RFID Tag
RFID tags are attached to the servers shipped after September 2010 in stages. Note
that the servers with and without the RFID tag may temporarily exist.
FIGURE 1-1 and FIGURE 1-2 show the locations of the RFID tags.
FIGURE 1-1
SPARC Enterprise T5120 Server Appearance (Front View)
RFID Tag
FIGURE 1-2
SPARC Enterprise T5220 Server Appearance (Front View)
RFID Tag
FIGURE 1-3 shows the appearance of RFID tag.
2
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
FIGURE 1-3
RFID Tag Appearance
Serial Number of the server
Asset ID written in the RFID tag
New Information About Known Issues
This section describes issues that were discovered since the previous edition of these
product notes was published.
Firmware, ILOM, POST, and SP Issues
TABLE 1-1
Firmware, ILOM, POST, and SP Issues
CR
Description
Workaround
6989852
ILOM firmware falsely recognizes the fan speed
as “0” and the Service Required LED may turn
on. In that case, ILOM event log is output. For
details, see “Service Required LED May Turn On
Due To False Recognition of Fan Speed (CR
6989852)” on page 3.
None.
Reset ILOM to recover. If the error is cleared,
then it corresponds to this event and the fan
replacement is unnecessary. ILOM reset has no
impact on the system.
Service Required LED May Turn On Due To False
Recognition of Fan Speed (CR 6989852)
ILOM firmware falsely recognizes the fan speed as "0" and the Service Required LED
may turn on. In that case, the following event log is output.
Chapter 1
New Information About the SPARC Enterprise T5120 and T5220 Servers
3
The ILOM event log example:
IPMI
| critical: "ID
: Lower
Non-recoverable going
IPMI
| critical: "ID
: Lower
Non-recoverable going
IPMI
| critical: "ID
: Lower
Non-recoverable going
IPMI
| critical: "ID
: Lower
Non-recoverable going
=
9a : 08/17/2010 : 00:39:17 : Fan : /FB0/FM0/F0/TACH
low : reading 0 <= threshold 2400 RPM"
=
9a : 08/17/2010 : 00:39:22 : Fan : /FB0/FM0/F1/TACH
low : reading 0 <= threshold 2400 RPM"
=
9a : 08/17/2010 : 00:39:26 : Fan : /FB0/FM1/F0/TACH
low : reading 0 <= threshold 2400 RPM"
=
9a : 08/17/2010 : 00:39:30 : Fan : /FB0/FM2/F1/TACH
low
: reading 0 <= threshold 2400 RPM"
The showenvironment command output example:
-------------------------------------------------------------------Fan Status:
-------------------------------------------------------------------Fans (Speeds Revolution Per Minute):
Sensor
Status
Speed
Warn
Low
-------------------------------------------------------------------/SYS/FANBD0/FM0/F0/TACH
FAILED
0
4000
2400
/SYS/FANBD0/FM0/F1/TACH
FAILED
0
4000
2400
/SYS/FANBD0/FM1/F0/TACH
FAILED
0
4000
2400
/SYS/FANBD0/FM1/F1/TACH
OK
6400
4000
2400
/SYS/FANBD0/FM2/F0/TACH
OK
7000
4000
2400
/SYS/FANBD0/FM2/F1/TACH
FAILED
0
4000
2400
The showenvironment command output example:
sc> showfaults
Last POST Run: Mon Jul 12 00:08:46 2010
Post Status: Passed all devices
ID FRU Fault
1 /SYS/FANBD0/FM0 SP detected fault:
TACH at /SYS/FANBD0/FM0/F0 has reached
2 /SYS/FANBD0/FM0 SP detected fault:
TACH at /SYS/FANBD0/FM0/F1 has reached
3 /SYS/FANBD0/FM1 SP detected fault:
TACH at /SYS/FANBD0/FM1/F0 has reached
4 /SYS/FANBD0/FM2 SP detected fault:
TACH at /SYS/FANBD0/FM2/F1 has reached
low non-recoverable threshold.
low non-recoverable threshold.
low non-recoverable threshold.
low non-recoverable threshold.
Workaround:
4
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
None. Reset ILOM to recover. If the error is cleared, then it corresponds to this event
and the fan replacement is unnecessary. ILOM reset has no impact on the system.
Chapter 1
New Information About the SPARC Enterprise T5120 and T5220 Servers
5
6
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
CHAPTER
2
Important Information About the
SPARC Enterprise T5120 and T5220
Servers
This chapter describes important information about the SPARC Enterprise T5120 and
T5220 servers.
The following sections are included:
■
“Notes on DVD Drive and Discs” on page 7
■
“Supported Versions of the OS and Firmware” on page 8
■
“Solaris OS and Firmware Requirements for Certain Features” on page 9
■
“System Firmware Update” on page 10
■
“Preinstalled Software” on page 12
■
“Mandatory Patch Information” on page 15
■
“General Functionality Issues and Limitations” on page 18
■
“Support for SSD Storage” on page 20
■
“Processor Identification” on page 23
■
“Notes on the Use of 200V Power Supply” on page 24
Notes on DVD Drive and Discs
See the "Notes on DVD Drive and Discs in SPARC Enterprise" on the website below
before using the CD/DVD discs in the standard DVD drive mounted in this server.
http://www.fujitsu.com/sparcenterprise/manual/
7
Supported Versions of the OS and
Firmware
TABLE 2-1 lists the versions of Solaris OS and system firmware supported for
SPARC Enterprise T5120 and T5220 servers.
Your server is preinstalled with the latest supported OS, patches and firmware. If
you decide to install some other supported version, be certain to also install the
patches required by that version. For information on OS patch requirements, see
“Mandatory Patch Information” on page 15.
Note – If you install an OS over the preinstalled OS (even if it is the same version)
you will overwrite the supplementary software that was preinstalled at the factory.
See “Preinstalled Software” on page 12 for more information on this additional
preinstalled software.
Note – Some optional features require certain versions of the OS and System
Firmware. See “Solaris OS and Firmware Requirements for Certain Features” on
page 9.
TABLE 2-1
Supported Versions of the OS and Firmware
Supported Versions
OS
Solaris
Solaris
Solaris
Solaris
Solaris
10
10
10
10
10
8/07 OS plus mandatory patches - Minimum supported OS
5/08 OS plus patches
10/08 OS
5/09 OS
10/09 OS - Latest supported OS
Firmware
System Firmware 7.0.9 - Minimum supported System Firmware
System Firmware 7.2.10.a - Latest supported version (as of November 2010)
Note – When installing the Solaris 10 8/07 OS or Solaris 10 5/08 OS on a server
equipped with a USB SATA DVD drive, see “Notes on Installing Solaris 10 8/07 OS
and Solaris 10 5/08 OS” on page 61.
8
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Solaris OS and Firmware Requirements
for Certain Features
The following table identifies the minimum OS and firmware versions required to
support certain features.
TABLE 2-2
Minimum OS and Firmware Version Requirements for Certain Features
Feature
Minimum Firmware Version
Minimum OS Version
Mixed memory configurations*
7.1.6.d
N/A
Systems using the External I/O
Expansion Unit
7.1.6.d
Solaris 10 10/08 OS
Systems operating with DC power 7.1.6.j
supplies
Solaris 10 10/08 OS
8 disk-capable T5120 servers
7.1.6.j
N/A
16 disk-capable T5220 servers
7.1.6.j
N/A
1.6 GHz processors
7.2.2.e
N/A
ILOM 3.0 firmware
7.2.2.e
N/A
Hardware RAID
7.2.2.e
N/A
LDoms 1.2 †
-
-
LDoms 1.3 †
-
-
* When installing the following optional FB-DIMMs into servers running with system firmware older than 7.1.6.d,
you need to update the firmware to 7.1.6.d or later.
- Optional FB-DIMMs: 'SESX2A2_(1GBx2)' or 'SESX2B2_(2GBx2)'
Make sure that all FB-DIMMs in the server have the same capacity. For details, contact your service engineer.
† For minimum firmware version, minimum OS version, and mandatory patches when using LDoms software,
see the Logical Domains Guide.
Note – To benefit from the accumulated features, enhancements, and fixes, upgrade
your system firmware to the most recent version available.
Chapter 2
Important Information About the SPARC Enterprise T5120 and T5220 Servers
9
System Firmware Update
The System Firmware controls various aspects of the host and the service processor.
The System Firmware comprises the following individual firmware components:
■
Integrated Lights Out Manager (ILOM) firmwares
■
OpenBoot firmware
■
POST firmware
■
Hypervisor firmware
■
VBSC firmware
System Firmware updates are available from the following web site as patch
releases.
https://updatesite.jp.fujitsu.com/unix/en/download/firmware/
When you update the System Firmware, all of the individual firmware components
are updated. You cannot update firmware components individually. Refer to the
SPARC Enterprise T5120 and T5220 Servers Installation Guide for more information
about updating the server firmware.
Support for Windows 7 and Internet Explorer 8
As of System Firmware 7.2.7, the Remote Console feature in ILOM supports
Microsoft Windows 7 and Internet Explorer 8 operating system clients.
Change and Functional Enhancement in System
Firmware 7.2.8
About the Change of Host Console Target
In System Firmware 7.2.8 or later, the host console target in ILOM has been changed
to /HOST/console. However, by directly specifying the conventional target
/SP/console, you can obtain the host console as before. Also, the properties under
the host console target can be used in the same way as /SP/console.
10
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
How to obtain the host console in System Firmware 7.2.8 or later is as follows.
-> show /HOST/console
/HOST/console
Targets:
history
Properties:
escapechars = #.
line_count = 0
pause_count = 0
start_from = end
Commands:
cd
show
start
stop
-> start /HOST/console
Are you sure you want to start /HOST/console (y/n)? y
Serial console started.
To stop, type #.
XXXXXX console login:
About the Addition of Protocols for Firmware Update
In System Firmware 7.2.8 or later, three protocols which can be used in the firmware
update via the ILOM CLI interface have been added. In addition to the conventional
tftp, you can use ftp, sftp, and scp.
The scp protocol execution example:
-> load -source
scp://xxxxx:xxxxxx@XXX.XXX.XXX.XXX//mnt1/Firmware_Update/Huron/7.2.8/
/Sun_System_Firmware-7_2_8-SPARC_Enterprise_T5120+T5220.pkg
NOTE: An upgrade takes several minutes to complete. ILOM will enter a special
mode to load new firmware. No other tasks can be performed in ILOM until the
firmware upgrade is complete and 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 T5120 and T5220 Servers
11
Firmware update is complete.
ILOM will now be restarted with the new firmware.
Preinstalled Software
This section describes the following:
■
TABLE 2-3
Preinstalled software (TABLE 2-3) that is ready to use.
Preinstalled Software
Software
Location
Function
Solaris 10 5/09 OS
The root (/) partition is installed on Slice 0. The
core OS is on Slice 3, serving as a Live Upgrade
alternate boot environment (ABE).
Operating system and alternate
boot environment.
See “Solaris 10 OS and Solaris Live
Upgrade” on page 13.
CMT Tools 1.0
/opt/SUNWspro/extra/bin
Sun Studio Developer Tools
Cool Tools GCC
v. 4.0.4
/opt/gcc and /opt/SUNW0scgfss
GCC compiler for SPARC systems.
See “Additional Software Available
for Your Server – Cool Tools” on
page 13.
LDoms Manager
/opt/SUNWldm
Manages Logical Domains.
LDoms MIB
/opt/SUNWldmib
LDoms Management Information
Base.
Sun Studio 12
Developer Tools
/opt/SUNWspro/extra/bin
/opt/SUNWspro
Sun Studio Developer Tools.
See “Sun Studio C, C++ & Fortran
Compilers and Tools” on page 15.
Note – Previously, the Sun Java Enterprise System software package was placed in
the /var/spool/stage/JES5/Solaris_sparc directory at the factory. This is no
longer the case. If you want to install the Sun Java Enterprise System software,
download it from: http://www.sun.com/software/javaenterprisesystem.
12
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Solaris 10 OS and Solaris Live Upgrade
The Solaris 10 OS is completely installed on your system, including everything
installed by the "Entire Distribution plus OEM support" option. This software
includes all the locales supported by this Solaris release. In addition, some patches
are preinstalled on your server. See “Mandatory Patch Information” on page 15.
Note – Some software that is provided in the Solaris OS media kit has not been
installed on your system. If you want to use the additional software, obtain the full
media kit for this Solaris release and install software from the included discs. Order
the appropriate media kit for the version preinstalled on your system.
Your server is configured with a liveupgrade partition on Slice 3 that contains a
duplicate of the Solaris OS (core only). The liveupgrade partition is known as an
alternate boot environment (ABE). This technology enables the Solaris OS to run
normally during an upgrade or normal maintenance on an inactive boot
environment.
For more information about Solaris Live Upgrade, go to:
http://www.sun.com/software/solaris/liveupgrade
Additional Software Available for Your Server –
Cool Tools
Cool Tools provide a collection of freely available tools that enable fast and efficient
development and deployment of optimally configured software solutions on
CoolThreads servers. These tools significantly improve performance and time-tomarket development for applications running on these servers.
An overview of the Cool Tools and full documentation is available at:
http://www.sun.com/servers/coolthreads/overview/cooltools.jsp
Not all of the Cool Tools listed on the Cool Tools web page are preloaded on your
server. Refer to information at the Cool Tools web site for additional tools you can
download and install on these servers.
Chapter 2
Important Information About the SPARC Enterprise T5120 and T5220 Servers
13
Logical Domains
A logical domain is a discrete logical grouping with its own operating system,
resources, and identity within a single computer system. Each logical domain can be
created, destroyed, reconfigured, and rebooted independently, without requiring a
power cycle of the server. You can run a variety of applications software in different
logical domains and keep them independent for performance and security purposes.
Using Logical Domains (LDoms) increases your server usage, efficiency, and return
on investment, and also reduces your server footprint. The LDoms Manager
software creates and manages logical domains, and maps logical domains to
physical resources.
Note – The LDoms MIB must be configured before you can use it. A README file
with configuration instructions is located in the LDoms MIB installation directory,
/opt/ldoms_mib.
For more information on LDoms, go to:
http://www.fujitsu.com/global/services/computing/server/sparcent
erprise/products/software/ldoms/
Supported Sun Explorer Utility Version
Sun Explorer is a diagnostic data collection tool. The tool comprises shell scripts and
a few binary executables. Sun Explorer runs on the Solaris OS.
The SPARC Enterprise T5120 and T5220 servers are supported by the Sun Explorer
5.10 (or later) data collection utility, but are not supported by earlier releases of the
utility. Determine whether an earlier version of the Sun Explorer product has been
installed on your system by typing the following:
# pkginfo -l SUNWexplo
If an earlier version exists, uninstall it and install version 5.10, or later. For
information on how to get the Sun Explorer Utility, please contact a certified service
engineer.
14
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Sun Studio C, C++ & Fortran Compilers and Tools
Sun Studio delivers high performance by optimizing C, C++, and Fortran compilers
for the Solaris OS on multicore systems.
For an overview and documentation, go to:
http://developers.sun.com/sunstudio/index.jsp
Mandatory Patch Information
Patches are available at:
Global Site
http://www.fujitsu.com/global/support/software/security/products-s/patch-info/
Japanese Site
http://software.fujitsu.com/jp/security/products-others/unix/
North American Site
https://download.computers.us.fujitsu.com/
Before contacting support, ensure that all mandatory patches are installed on your
server. In addition to applying the periodic PTF, check the above web site on a
regular basis for the availability of new patches.
Chapter 2
Important Information About the SPARC Enterprise T5120 and T5220 Servers
15
Mandatory Patches for the Solaris 10 8/07 OS
TABLE 2-4 lists the mandatory patch that is needed for servers running the Solaris
10 8/07 OS. This patch was installed along with the OS at the factory. If you reinstall
the server with the Solaris 10 8/07 OS, you must reinstall this patch.
TABLE 2-4
Mandatory Patch for Servers Installed with the Solaris 10 8/07 OS
Patch IDs
Description
Fixes Provided
127127-11 or later
SunOS 5.10: kernel
patch
Includes the following fixes:
• CR 6590132: System panics (n2cp alignment
error) in IPsec testing
• Issues regarding data integrity in the nxge
driver as reported by Sun Alert ID 103076
• CR 6568352: IPsec performance does not scale
using hardware crypto providers
To determine if a patch is present, see “To Download Patches” on page 16.
Mandatory Patches for the Solaris 10 5/08 OS
There are no mandatory patches for the Solaris 10 5/08 OS at this time.
Mandatory Patches for the Solaris 10 10/08 OS
There are no mandatory patches for the Solaris 10 10/08 OS at this time.
Mandatory Patches for the Solaris 10 5/09 OS
There are no mandatory patches for the Solaris 10 5/09 OS at this time.
▼ To Download Patches
1. Determine whether the patches have been installed on your system.
For example, use the showrev command for each patch number:
# showrev -p | grep "Patch: 127753"
16
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
■
If you see patch information listed for the queried patch, and the dash extension
(the last two digits) matches or exceeds the required version, your system has the
proper patches already installed and no further action is required.
For example, if patch 127127-11 or later is installed, your system has the required
version of this patch.
■
If you do not see patch information listed for the queried patch, or if the dash
extension precedes the required version, go to Step 2.
For example, if 127127-09 is displayed you must download and install the patch.
The last two digits of the patch ID represent the revision of the patch.
2. Access the above-mentioned web site to download the patches.
3. Follow the installation instructions provided in a specific patch's README file.
Patches for Option Cards
If you add option cards to your server, refer to the documentation and README files
for each card to determine if additional patches are needed.
Installing the Fujitsu 4Gbps Fibre Channel Card
Once you install the Fujitsu 4Gbps Fibre Channel card (SE0X7F11X, SE0X7F12X), the
patch indicated below is required. Access the above-mentioned web site to
download the patch. Follow the installation instructions provided in the README file
for the patch.
Optional cards
■
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 T5120 and T5220 Servers
17
General Functionality Issues and
Limitations
This section describes general issues known to exist at this release of the SPARC
Enterprise T5120 and T5220 servers.
Cryptographic Function
The IPsec capability of the on-chip cryptographic accelerator in the UltraSPARC T2
multicore processor is a mechanism that cannot be used unless the IPsec activation
package has been installed. As the IPsec activation package is presently not
supported by Fujitsu, the IPsec function cannot be used in Fujitsu-brand servers.
Support for RAID Function
The SPARC Enterprise T5120 and T5220 servers are equipped with a hardware RAID
function by default, and this section shows the support conditions and the points of
concern.
1. Support conditions
Item
Description
Mandatory OS patch
Patch ID: 141444-09 or later, or PTF RPTF R10021 or later
Mandatory ESF (Enhanced
Support Facility) patch
914604-07 or later
System Firmware
7.2.2.e or later
RAID level
RAID 1 (IM: Integrated Mirror) only. In RAID 1, two member
disks per volume.
* RAID 0 (IS: Integrated Stripe) is not supported.
HDD
A single volume shall be made up of disks of the same
capacity and the same rotational speed.
* SSD is not supported.
Number of volumes
Up to 2 volumes supported per system.
2. Points of concern
■
18
When using the RAID function
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
■
Make backup copies of important data and programs periodically. In some
failures, rebuild of RAID and the data restore from the backup media may
become necessary.
To ensure data integrity in time of power failure, it is recommended to use an
UPS.
■
■
■
If you require higher availability such as the controller or the data path
redundancy, use the dedicated RAID system.
When building or deleting a RAID 1 array
■
The data in the disk is not secured during the build or the deletion of a RAID
array. When you newly build a RAID array while the system is running, or
delete the built RAID array once, do not fail to make backup copies of the data.
After building a RAID, you need to install data newly or restore data from the
backup media.
■
The RAID build or the synchronization associated with maintenance takes
about an hour for a 146GB HDD.
■
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.
During the RAID 1 operation
■
In some cases, RAID controller cannot conclude the disk is completely in
failure, and system slowdown may occur. To do maintenance in this status,
follow the procedures below.
1. Delete the RAID.
2. Replace all disks related to the RAID.
3. Rebuild the RAID 1.
4. Restore the data from the backup media.
■
Notes on the raidctl command
■
The following options of the raidctl command can not be used because the
hardware specifications do not support them.
raidctl -C -r 1E
(To create a RAID1E)
raidctl -c -r 1E
(To create a RAID1E)
raidctl -a
(To assign hot-spare disks)
raidctl -p
(To set the cache)
raidctl -C -z
(To specify the volume capacity)
Chapter 2
Important Information About the SPARC Enterprise T5120 and T5220 Servers
19
Cable Management Arm
The SPARC Enterprise T5120 server does not support the cable management arm
(CMA).
The following restrictions apply when using a CMA on SPARC Enterprise T5220
servers:
■
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
■
Optical fiber cables cannot be accommodated in the CMA. Route the cables
through the free space on top of the CMA.
■
Cables with a cable core (such as SCSI cables) cannot be accommodated in the
CMA. Route the cables through the free space on top of the CMA.
Moreover, if it hampers to install optional products that are subject to the following
structural restriction, first uninstall and remove the CMA.
■
Cables with large connectors (such as for an XVR-300 or SAS card) must be
connected to the top PCIe slot.
Express Rail Rackmounting Kit
Installing the servers with the express rail rackmounting kit is not supported.
SAS RAID Internal HBA Card
SAS RAID Internal HBA Card is not currently supported.
Support for SSD Storage
This section describes support for 32GB SATA SSD (Solid State Drives). It also
describes the procedure for updating the SATA Controller with the firmware version
required to use SSDs.
Sun SPARC Enterprise T5120 and T5220 Servers can now use 32GB SATA SSDs for
internal storage. The SSDs are hot-pluggable. You can replace the existing 2.5-inch
SAS hard drives with the SSDs. You can also have both 2.5-inch SAS hard drives and
SSDs installed at the same time.
20
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Note – The number of 32GB SATA SSDs which can be installed in T5120/T5220
servers varies depending on the maximum number of HDDs installed in the servers.
For details, see TABLE 2-5.
TABLE 2-5
The Number of Installable 32GB SATA SSDs
T5120 server
T5220 server
Maximum Number
of HDDs
Installable Number
of SSDs
4
3
8
4
8
7
16
8
Note
When using the external storage unit for the system
disk, up to 4 SSDs can be installed.
When using the external storage unit for the system
disk, up to 8 SSDs can be installed.
For instructions on installation and removal of SSDs, see the "Hot-Plugging a Hard
Drive" described in the SPARC Enterprise T5120 and T5220 Servers Service Manual. The
procedures apply to both the disk-based hard drives and SSDs.
Using a SSD as a Boot Device
You cannot use a SSD as a boot device.
About the Cache Setting of SSDs
The SSDs have a setting of internal cache enabled in the initial status. When used in
the cache enabled condition, data may be lost at the time of power failure.
You can disable the internal cache by using a sub command cache of format -e
command after booting the Solaris. This setting is not saved when you reboot the
Solaris.
To ensure data integrity, it is recommended to use an uninterruptible power supply
(UPS).
Chapter 2
Important Information About the SPARC Enterprise T5120 and T5220 Servers
21
About the Estimated Usable Period of SSDs
The SSDs are designed with the estimate of usable period for five years. Depending
on the user environment such as the frequency of use, replacement may be required
before the five-year maintenance support period expires.
About the Preventive Replacement Monitoring
Function of SSD
On the ESF (Enhanced Support Facility) of a certain version or later, the preventive
replacement monitoring function of SSD is supported. Supported versions of
software are as follows.
■
Supported versions of software
ESF (Enhanced Support Facility) 3.0 to 3.1, and patch 914604-08 or later
About the SSD Use on the 16-Disk Backplane
Model
To use the SSDs on the 16-disk backplane model, only the server equipped with the
USB SATA DVD drive can be used.
For servers shipped after September 2009, the USB SATA DVD drive unit has been
mounted. Confirm whether a USB SATA DVD drive unit is mounted on your server
by using either of the following methods.
■
Confirm that the "SATA DVD" mark appears on the front side of the DVD drive.
■
Confirm that specific part numbers are displayed in the output for the following
ILOM/ALOM commands.
[Confirm by using ILOM command]
Confirm whether either of the following part numbers is displayed in the output
from ls /SYS/PADCRD command.
fru_part_number = 5413512
or
fru_part_number = 5413513
22
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
[Confirm by using ALOM command]
Confirm whether either of the following part numbers is displayed in the output
from showfru /SYS/PADCRD command.
/Partner_Part_NumberR/Partner_Part_Number: CF005413512REVxx
or
/Partner_Part_NumberR/Partner_Part_Number: CF005413513REVxx
Updating LSI 1068e Controller Firmware to
Support SSDs
To use SSDs, the version of LSI 1068e controller firmware should be 1.27.00.00 or
later. Depending on the firmware version of your server, you may need to update
the controller firmware. The updated version is available on the following web site
as a patch release. The patch to be applied varies depending on the server models.
See the documentation on the web site for details, and update the firmware.
https://updatesite.jp.fujitsu.com/unix/en/download/firmware/
Processor Identification
Processor IDs might not start at 0, and might not be contiguous.
Different platforms and platforms of the same model might have different processor
IDs for identical configurations. For example, on UltraSPARC® T1 CPU based
platforms, the processor IDs start with processor ID 0 but other platforms, including
those based on the UltraSPARC T2 CPU, might not have a processor ID 0. The
Solaris psrinfo command might display output similar to the following for
platforms based on the UltraSPARC T2 processor:
8
9
16
17
on-line
on-line
on-line
on-line
since
since
since
since
09/18/2007
09/18/2007
09/18/2007
09/18/2007
21:26:25
21:26:30
21:26:30
21:26:30
The processor IDs might have significance if you are running LDoms. The processor
IDs exported to a guest domain on a platform running multiple guest domains with
a virtual machine manager might represent a virtual abstraction. Within each guest
domain, each processor ID visible to the software will be a unique integer value.
Chapter 2
Important Information About the SPARC Enterprise T5120 and T5220 Servers
23
Software running in different guest domains on the same physical machine might
see the same or different sets of virtual processor IDs. If the server is running
LDoms, the virtual processor IDs and physical processor IDs are never the same. For
information about the mapping between virtual and physical CPU numbers, refer to
the latest Logical Domains (LDoms) Administration Guide.
Processor IDs are unique integer values in the domain where the software is
running. The integer value fits in the type processorid_t. Also refer to the
p_online(2) man page.
Notes on the Use of 200V Power Supply
For the servers that have the B-type plug, confirm that a 15A overcurrent protection
device is available outside the server. If one is not available, prepare an external 15A
overcurrent protection that can be achieved by means of no-fuse breakers (NFBs) or
fuses. The B-type plug refers to plugs other than grounding-type ones with two
parallel blades, such as the NEMA L6-30, L6-20, L6-15, and L5-15.
For details of the power cord type for your server, contact your authorized service
engineer.
24
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
CHAPTER
3
Known Issues
This chapter describes known issues about the SPARC Enterprise T5120 and T5220
servers.
The following sections are included:
■
“Hardware and Mechanical Issues” on page 26
■
“Ethernet Interface Related Issues” on page 30
■
“Firmware, ILOM, POST, and SP Issues” on page 32
■
“Solaris OS Issues” on page 58
■
“LDoms Related Issues” on page 62
Note – For the issues already fixed in the latest version of Solaris OS or System
Firmware, see Appendix A. For the latest version to be supported, see “Supported
Versions of the OS and Firmware” on page 8.
25
Hardware and Mechanical Issues
This section describes the late-breaking hardware and mechanical issues.
False Intermittent SATA Errors Seen on Sun
SPARC Enterprise T5120 and T5220 Servers (CR
6880299)
While booting, some systems with SATA DVD devices intermittently log extraneous
port failure errors in /var/adm/messages. The following shows an example of
typical error messages:
/pci@400/pci@0/pci@1/pci@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
Workaround: You can ignore these messages.
TABLE 3-1
Hardware and Mechanical Issues
CR
Description
Workaround
n/a
Hot-swapping fan modules requires careful fan
removal.
When removing a fan module, hold the adjacent
fan module in place to avoid unintentionally
dislodging the adjacent fan module.
n/a
All disk LEDs blink simultaneously about every
16 seconds when a RAID volume is created.
Be aware that the blinking LEDs are a normal
condition.
6550166
6667545
Components on the motherboard are hot to the
touch.
When replacing components in the system
chassis, wait for components to cool down,
approximately one minute, prior to performing
service actions.
26
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE 3-1
Hardware and Mechanical Issues (Continued)
CR
Description
Workaround
6574127
6480945
If a hard drive fails in RAID 0 or RAID 1
configurations, error messages might not be
displayed on the console or in the log files.
If you encounter failed disks in RAID 0 or
RAID 1 configurations, and you see the
following scenario, the disk drive should be
replaced:
• The Fault LED is lit on a disk drive that is part
of a RAID0 or RAID1 volume.
• The error condition can be displayed
remotely by running the showenvironment
command on the service processor.
• The hard drive that has the Fault LED
illuminated displays a status of Failed and
the service indicator is set to ON.
Replace the disk drive with the lit Fault LED.
6616232
Power cycle the power supply that has the fan
Power supply fan faults are not automatically
fault to clear the fault.
cleared.
If a fault is detected for a power supply fan, and
the fan returns to normal operation, the fault
indication is not automatically cleared.
6674290
In the SPARC Enterprise T5220 server, if a XAUI
card and a PCIe card are installed on the same
riser assembly, the XAUI card might fail POST
and be disabled when the server boots.
If possible, do not install any PCIe cards in the
same riser assembly as a XAUI card.
n/a
When the system is initialized, firmware is
loaded and occupies approximately 128 MB to
352 MB of the host memory. The banner and
other software utilities report an amount of
memory minus the amount of memory that is
occupied by firmware.
When viewing the amount of memory in the
banner, be aware that the banner reports the
amount less what is used by the firmware.
n/a
In this event, disconnect the cable while keeping
An RJ45 cable may sometimes be difficult to
disconnect from an RJ45 port of an Ethernet card the RJ45 cable connector tab depressed, such as
with a plastic card.
mounted in the SPARC Enterprise T5120.
6581309
To use the XVR-300 as a console of the SPARC
Enterprise 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 ILOM
console during the Solaris boot sequence.
To use the XVR-300 as a console, apply patch
137111-01 or later to the Solaris OS before
changing the OBP variable.
Alternatively, install the Solaris OS (or reinstall
it) with ILOM set as the console used, and then
apply the patch.
No GUI can be used during that time.
After the patch has been applied, the XVR-300
can be used as the console as soon as the OBP
variable is changed.
Chapter 3
Known Issues
27
TABLE 3-1
Hardware and Mechanical Issues (Continued)
CR
Description
Workaround
6706976
At write to CD/DVD media, there may be cases
where the writing speed may not reach the
maximum speed supported by the CD/DVD
drive. Even if the maximum operation is not
reached, there are no problems in the processing
for writing to the CD/DVD media.
Use the media as is.
6840287
When a server is power cycled with DVD media
installed, the message "Device is gone" will
be displayed approximately 30 minutes after the
OS is booted up.
Ignore the message.
6857080
Systems with firmware version 7.2.2.x have low Ensure that the air flowing into the server is
within the ambient temperature specification.
fan speed (5000 rpms). The low fan speed
condition can result in SC Alerts that warn of the
low fan speed.
n/a
The On/Standby portion of the service label
contains an error. It says to press and hold the
On/Standby button for "5 seconds". It should
say "4 seconds".
n/a
Some service labels show an extra fan module in Note - This error appears on the service label for
SPARC Enterprise T5120 servers with 4-disk
step 2 of the four-step fan board diagram. The
capable backplanes.
extra fan is on the right half of FanBD0.
n/a
On service labels that show the locations of PCIe Note - This error appears on the service labels
for SPARC Enterprise T5220 servers.
and XAUI slots, the XAUI callouts are wrong.
They should point to the lower slots.
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 top
of FM".
Note - This error appears on the service labels
for SPARC Enterprise T5220 servers.
n/a
The drawing showing the cable management
arm being rotated represents the wrong server
model. It should show the SPARC Enterprise
T5220 server.
Note - This error appears on the service labels
for SPARC Enterprise T5220 servers.
n/a
The Fan Module Configuration portion of the
service label is wrong. It should show fan
modules in location FANBD1, FM1.
Note - This error appears on the service labels
for SPARC Enterprise T5220 servers with 16-disk
capable backplanes.
n/a
The shapes of anti-tilt legs shown on service
labels may be different, depending on racks.
Note - This error appears on the service labels
on all SPARC Enterprise T5120 and T5220
servers.
n/a
When a disk failure occurred in a RAID 0
configuration, the failed disk cannot be
identified.
Do not use RAID 0.
28
Note - This error appears on the service labels
on all SPARC Enterprise T5120 and T5220 server
configurations.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE 3-1
Hardware and Mechanical Issues (Continued)
CR
Description
Workaround
n/a
After the build and the deletion of RAID 1, disk
device may not be recognized correctly.
It becomes recognized correctly after the server
reboot.
6823163
In servers with 8- and 16-disk backplanes, the
32GB SATA SSD drive may not install in some
drive bay slots.
1. Loosen all the screws on the backplane.
2. Install SSDs in the corner drive bays.
3. Tighten all backplane screws.
4. Install remaining SSDs (if any).
6901327
In Solaris 10 10/09, after the RAID 1 build, label
information may fail to be written correctly.
1. Start the OS with single user mode, or from
the SunInstaller.
When booting from the SunInstaller, terminate
the SunInstaller once.
2. Use the format -e command to execute the
following 2-1 to 2-3.
2-1) Label the target disk with SMI label.
2-2) Label the target disk with EFI label.
2-3) Label the target disk with SMI label.
Chapter 3
Known Issues
29
Ethernet Interface Related Issues
TABLE 3-2 lists the late-breaking Ethernet related issues. Additional information for
some of the issues is provided after the table.
TABLE 3-2
Ethernet Related Issues
CR
Description
Workaround
6553515
If a temporary PCIe network link failure occurs
during boot or any time later, the system could
fail.
If the link is up and working again before the
firmware gets control, the error is a problem in
firmware handling the leftover status. For an
example of the error, see “Temporary PCIe Link
Failure During Boot Causes a Fatal Error Later
(CR 6553515)” on page 30.
If the system fails to boot because of this
problem, try booting again.
6606950
There is an important /etc/system setting for
10 Gb Ethernet performance.
Note - The preinstalled Solaris OS has the correct
entry in the /etc/system file.
If you reinstall the Solaris OS, you must add the
following line to the /etc/system file:
set ip:ip_soft_rings_cnt=16
This /etc/system setting ensures optimum
performance for 10 Gb Ethernet interfaces.
Temporary PCIe Link Failure During Boot Causes
a Fatal Error Later (CR 6553515)
If a temporary PCIe link failure occurs during boot or any time later, the system
could fail. If the link is up and working again before the firmware gets control, the
error is a problem in firmware handling the leftover status. The following is an
example of the error message:
{0} ok 4000 dload users/bog/rustn2obp_0502
Boot device:
/pci@0/pci@0/pci@1/pci@0/pci@2/network@0:,users|bog|rustn2obp_0502 File
and args:
FATAL: /pci@0/pci@0/pci@1/pci@0/pci@2/network@0: Last Trap: NonResumable Error
TL:
1
%TL:1 %TT:7f %TPC:f0238978 %TnPC:f023897c
%TSTATE:820001600 %CWP:0
30
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
%PSTATE:16 AG:0 IE:1 PRIV:1 AM:0 PEF:1 RED:0 MM:0 TLE:0 CLE:0 MG:0 IG:0
%ASI:20 %CCR:8 XCC:nzvc
ICC:Nzvc
%TL:2 %TT:3f %TPC:f024327c %TnPC:f0243280
%TSTATE:14414000400 %CWP:0
%PSTATE:4 AG:0 IE:0 PRIV:1 AM:0 PEF:0 RED:0 MM:0 TLE:0 CLE:0 MG:0 IG:0
%ASI:14 %CCR:44 XCC:nZvc
ICC:nZvc
Normal
GL=1
0:
0
0
1:
f0200000
0
2:
f0200000
0
3:
fff78000
0
4:
fec320fc
3ffe60000
5:
f02833e4
3ffe60000
6:
fee826c8
3ffe60600
7:
fee817d8
f02432bc
%PC f0238978 %nPC f023897c
%TBA f0200000 %CCR 8200016 XCC:nzvC
ICC:nZVc
{0} ok
Workaround: If the system fails to boot because of this problem, retry booting.
Ierrs Are Generated When 100Mb/Full With
Forced Speed/Duplex Is Set in e1000g.conf (CR
6555486)
As a result of research, it turned out that this problem had never happened on the
condition which we informed before.
It is the case that this problem happens when e1000g sets Auto-negotiation:off and
its link partner sets Auto-negotiation:on, which is specified in IEEE802.3.
Therefore the same problem can be seen on the other drivers than e1000g when it
does the same setting.
The following setting is also available on e1000g driver.
■
Auto-negotiation : off
■
speed
■
Duplex
: 100Mbps
: Full
But we suggest Auto-negotiation be set to "on" because this problem frequently
occurs when users who set Auto-negotiation:off to e1000g forget to set Autonegotiation:off to link partner.
Chapter 3
Known Issues
31
Firmware, ILOM, POST, and SP Issues
TABLE 3-3 lists the late-breaking issues for the firmware, ILOM (including ALOM
compatibility CLI), POST, and service processor (SP). Additional information for
some of the issues is provided following the table.
TABLE 3-3
Firmware, ILOM, POST, and SP Issues
CR
Description
Workaround
6237994
Registration with DMI could fail with an err=
831 message.
Disable DMI service at the startup. For example:
% mv /etc/rc3.d/S77dmi
/etc/rc3.d/_S77dmi
6510082
For users familiar with ALOM CMT and using
the ALOM CMT compatibility CLI, the help for
the consolehistory command displays both a
boot and a run option. Both options result in the
same output because ILOM makes no distinction
between the run and boot buffers.
6556505
The PCIe link might fail to train as x8.
This problem might occur during a power on or
reset sequence where the I/O bridge (PCIe root
complex) of the UltraSPARC T2 CPU does not
properly train the PCIe interface.
For workaround procedures, see “Problem
When the PCIe Link Fails to Train as x8 (CR
6556505)” on page 43.
6568750
Scripts that log into the SP might timeout after
60 seconds.
If this error occurs, the following error message
is displayed:
Logging out after 60 seconds.
Note - This error is not seen during normal
login, only when logging in with a script.
If you use scripts to log into the SP, be aware of
this issue.
6573354
The method for clearing POST results (displayed To clear POST results, use the ALOM CMT
with the showfaults command) has changed. compatibility setdefaults command.
After POST runs, showfaults displays the
status. The only way to clear the status is to
enter the setdefaults command. For users
familiar with ALOM CMT, the previous way to
clear the status was to enter the resetsc
command.
6583567
A communication channel between the primary
domain and the service processor (SP) could
hang and disable communication over the
channel.
32
See “Communication Channel Between the
Primary Domain and the Service Processor (SP)
Might Hang (CR 6583567)” on page 44.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
6585114
AC power cycle the system.
During automated testing, the SP could
encounter problems with useradd and
usershow commands, followed by the failure of
all login attempts.
6585292
Some extraneous and misleading warning
messages are displayed in the output of the
ILOM reset /SP command and of the ALOM
CMT compatibility resetsc command.
For an except of the misleading messages, see
“Resetting the SP Produces Extraneous Warning
Messages (CR 6585292)” on page 45.
6595955
If a component is not physically present on a
system (such as the fan module), the status field
in the prtdiag -v (Environmental Status
Section) output shows no value and is blank.
6596430
If the socketed EEPROM (SCC) is replaced, the
SP does not always read some SP properties
from the new EEPROM.
If the SP configuration variable
sc_backupuserdata is set to false, the
following user configuration values are not
backed up to the socketed EEPROM:
if_emailalerts, mgt_mailhost,
mgt_mailalert, sc_customerinfo,
sc_powerondelay, sc_powerstatememory,
sc_backupuserdata
6596594
Changed OpenBoot NVRAM parameters do not After changing variables, reset the control
domain using the reset-all command.
take affect after a resetsc.
If the service processor is reset while the control
domain is at the ok prompt, OpenBoot PROM
will permanently lose its ability to store
nonvolatile LDoms variables or security keys
until the host has been reset. Guest domains are
not affected by this problem. Attempts to update
LDoms variables or security keys results in the
following warning messages:
WARNING: Unable to update LDOM Variable
WARNING: Unable to store Security key
Workaround
Ignore the extraneous warning messages.
Manually copy the user settings before replacing
the motherboard in a motherboard swap
scenario. After the swap is complete, manually
set the user parameters.
Chapter 3
Known Issues
33
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
6599333
The ASR database does not support disabling
XAUI devices. When a XAUI device is disabled
(with ILOM CLI set NACname
component_state=disabled, or with the
ALOM CMT compatibility disablecomponent
command) or due to failures detected by POST,
the corresponding network device is still
available in the OpenBoot firmware.
6613212
Add "all-resets" or "power-on-reset" to
Though you set user-reset or all-reset to
/HOST/diag/trigger.
/Host/diag/trigger and execute reset by
using the reset /SYS command, POST fails to
be executed.
6614432
Erroneous power supply faults might be
displayed.
For an example, see “Erroneous Power Supply
Faults (CR 6614432)” on page 46.
Some servers report a low AC line input voltage
fault when the input voltage is in the range of
90V to 94V AC. This threshold is incorrect and
should not indicate an AC input fault until the
voltage drops below 90V AC.
Ensure that both server power supplies are
operating. When both power supplies are
operating, the server will remain powered on
during and after erroneous faults.
6614568
In ILOM mode, though you send the break
request to OS, you cannot obtain the ok prompt.
-> set /HOST send_break_action=break
Set 'send_break_action' to 'break'
None. When the auto-boot? parameter is set
to false, ok prompt can be displayed by
selecting s or r. Selecting c returns you to the
Solaris OS. However, when the auto-boot?
parameter is set to true, none of the options can
obtain the ok prompt.
For the details, see the section "OpenBoot ok
Prompt" in the SPARC Enterprise T5120 and
T5220 Servers Administration Guide.
At this time, the following message appears on
the OS console; but none of the options can
obtain the ok prompt.
# Debugging requested; hardware watchdog
suspended.
c)ontinue, s)ync, r)eset?
Workaround
6624705
None.
When a component set disable by using
"Component Management" of BUI, on the screen
of an ALOM mode log-in user, a message
appears which supposed to be shown when the
command executed from CLI.
Fault | critical: SP detected fault at
time Wed Jul 18 09:37:15 2007.
/SYS/MB/GBE1 Disabled by CLI action.
6628377
None.
Though you disable the TTYA by using the
ILOM command, it doesn't turn disable and you
can log in to OS.
34
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6636098
If a built-in fan is erroneously detected as a
failure and reported as such to the Enhanced
Support Facility software or Server System
Manager software, an error message is
displayed:
For an example of the errors, see “A Built-In Fan
May be Erroneously Detected as a Failure (CR
6636098)” on page 47.
Note - Fixed in Enhanced Support Facility
patch 914604-04.
Since these messages do not have an effect on
your system behavior, ignore these messages.
6662997
If you change any firmware variables (such as
auto-boot?), keep a record of your changes.
In the event of a motherboard replacement, most
of the SP variables will become the default
values.
The service manual indicates that moving the
SCC module to the new motherboard will
preserve customized variables, but this is not
true because not all variables are stored in the
SCC module.
The following variables are stored in the SCC
module, and will be preserved when the SCC
module is moved to a replacement motherboard:
• Host ID
• Mac addresses
All other variable values will become default
values.
Keep a record of any firmware variables that are
modified.
In the event that the motherboard is replaced,
use your record of customized variables to
manually modify the firmware variables on the
new motherboard.
6723410
If you repeat in sequence a login to the service
processor, executing a command, and logging
out, logout may fail.
If this problem occurs, terminate the login
session on the client from which you have
accessed the service processor.
Chapter 3
Known Issues
35
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6760139
ILOM firmware and OpenBoot PROM (OBP)
setting information may not be inherited during
motherboard replacement.
If an ILOM firmware initialization has been
performed or any of the firmware settings have
been changed, follow the procedure below to
save the latest ILOM firmware setting
information. After replacing the motherboard,
set the saved setting information again.
(Procedure for saving ILOM firmware setting
information)
1) Log in to ILOM, execute the following
commands, and save the displayed results:
-> show /SP -level all -o table
-> show /SYS -o table
-> show /HOST -level all -o table
2) Log in to the ALOM CMT compatibility
shell, execute the following command, and
save the displayed results:
sc> showsc
6762635
One of the following messages may be output
while a POST (self-diagnostics test) is in
progress, and POST processing may not be
completed.
Also, a transition to OpenBoot PROM (OBP)
may occur.
Message examples:
Fault Sensor VMEML_POK at /SYS/MB
deasserted
Fault Sensor VCORE_POK at /SYS/MB
deasserted
Fault Sensor VMEMR_POK at /SYS/MB
deasserted
(Recovery procedure)
Disconnect and then reconnect the power cable.
6761778
The following error message may be displayed:
Message example:
picld[154]: [ID 276222 daemon.error]
PICL snmpplugin: sunPlatSensorClass 0
unsupported (row=388)
Ignore this message.
36
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
6752910
After turning off the power to the host, wait at
After a host power-on instruction is executed
from ILOM, the POST (self-diagnostics test) may least three minutes before turning it on again.
not start, and processing may not go to OS boot
processing or the ok prompt for OpenBoot
PROM (OBP).
For details, see “After a Host Power-On
Instruction is Executed from ILOM, the POST
May Not Start, and Processing May Not Go to
OS Boot Processing or the ok Prompt (CR
6752910)” on page 48.
6726663
In ILOM mode, or through access to the ILOM
Web, it may be possible to change the system
time when the system is powered on.
Workaround
In ILOM mode, be sure not to change the
properties displayed below at power on so as
not to change the system time directly or enable
NTP services.
-> show /SP/clock
/SP/clock
Targets:
Properties:
datetime = Wed Dec 3 06:22:48 2008
usentpserver = disabled
Commands:
cd
set
show
->
n/a
The following error message may be output
None.
during POST. Since the error has no impact on
system operation, you can ignore the message.
0:0:0>Begin: Block Mem Test
0:0:0>Block Mem Test 00000000. 02000000>00000008. 00000000
0:0:0>
FBR Error Tally Branch
3 = 2
= Indefinite value
6815369
For DC input power models, /PS0/AC_POK
and /PS0/DC_POK identify sensors in the
power supply units. /PS0/AC_POK does not
represent an AC power supply unit. For
examples, see “For DC Input Power Models,
/PS0/AC_POK Is Displayed (CR 6815369)” on
page 49.
None.
Chapter 3
Known Issues
37
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6746677
According to the IPMI PET warning and SNMP
trap warning settings in the warning rule
settings, warning message creation may not be
possible depending on the event type,
irrespective of the warning level. All generated
events can be confirmed with show
/SP/logs/event/list or showlogs.
None.
See “According to the IPMI PET Warning and
SNMP Trap Warning Settings in the Warning
Rule Settings, Warning Message Creation may
not be Possible Depending on the Event Type
(CR 6746677)” on page 50.
6806268
None.
The flashupdate (ALOM CMT command)
with the -v option doesn't display the details of
the execution result.
The -v option exists to maintain compatibility
with the earlier ALOM. The -v option specified
doesn't affect the system firmware download
and update. The result shows no details and will
be the same as the execution result without the
option.
6823561
In the back up and restore functions of ILOM
settings, you cannot set "https" to the protocol
for data transfer (transfer_method
property).
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_mode
property of the ALOM CMT compatible shell. If
you set, it is displayed as "unknown."
None.
The following settings offer the POST diagnosis
in a mode equivalent to the "service."
/HOST/diag mode = normal
/HOST diag level = max
/HOST verbosity = max
6829248
The alert rule configuration using the SNMP
trap fails in the filtering of alert levels.
When you select the minor or any upper levels,
alerts of all levels will be notified to the SNMP
trap.
None.
6836426
In the Logical Domains environment, after the
host reset operation, host may be reset again.
For the example, see “In the Logical Domains
Environment, After the Host Reset Operation,
Host May Be Reset Again (CR 6836426)” on
page 50.
None.
The second reset has no impact on the system.
38
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6835863
During the execution of SunVTS, there may be
the following warning message on the OS
console and the system log output.
Message example:
WARNING: ldc_close: (0xc) unregister
failed, 11
None.
This message has no impact on the system and
can be safely ignored.
6835854
6779753
In case that the NET-MGT port of ILOM has not
been connected with the LAN cable and the
network gateway is not set, the ILOM network
configuration cannot be set.
For the output example, see “The ILOM
Network Configuration Cannot Be Set (CR
6835854, 6779753)” on page 51.
None.
Connect the LAN cable to the NET-MGT port of
ILOM and then set the network configuration.
6853383
None.
On SPARC Enterprise T5220 Server, after the
Solaris OS panic occurred and while collecting
the OS panic core dump, the ILOM watchdog
timer occasionally detects it as an error and may
reset the system. In this case, the OS panic core
dump is not collected.
6858772
snmpd can sometimes become unresponsive
during the creation of snmpv3 users. This will
result in a core dump.
None.
6856315
Using show /SP/user/adminusr password
returns show: Invalid command syntax. It
should return "*****".
None.
6932448
Messages referring to hot insertions/removals of
devices including a nonexistent device are
displayed at power on if the system has had a
system initialization, firmware upgrade, or
system component change.
Message example:
Chassis | major: Hot insertion of
/SYS/MB/CMP0/P0
or
SC Alert: [ID 639621 daemon.error] SC
unretrieved msg: [Chassis | major: Hot
insertion of /SYS/MB/CMP0/P3]
None.
Those messages are displayed when the ILOM
firmware recognizes the system configuration at
system initialization, firmware upgrade, or
system component change. You can ignore the
messages.
Chassis | major: Hot removal of HDD3
or
SC Alert: [ID 677427 daemon.error] SC
unretrieved msg: [Chassis | major: Hot
removal of HDD3]
Chapter 3
Known Issues
39
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
11210193
None. If this problem occurs, use the resetsc
If an error occurs during POST execution,
ALOM CMT compatibility command to clear the
"Fault Sensor VCORE_POK at /SYS/MB
log and reset the LED display.
deasserted" may be registered when the
showfaults ALOM CMT compatibility
command is used for status confirmation.
However, POST will still end normally in this
case.
For an example, see “An Error is Registered with
the showfaults Command When Running
POST, But POST Ends Normally (CR 11210193)”
on page 52.
11215994
In rare circumstances, the ok prompt may not be See “The ok Prompt is Not Displayed After
displayed normally after POST execution ends. POST Ends (CR 11215994)” on page 53.
6739633
When the host is off, any prepare_to_remove
operation for the component selected in the
ILOM Web interface (System Information tab ->
Components tab) may cause the radio button of
the component to disappear.
In the "Ready to Remove Status" column,
"NotReady" changes to "Ready (No Power)" for
the component, but "Return to Service"
cannot be performed for the component because
the radio button is no longer displayed.
Make the following setting from the CLI:
• set /SYS/(selected-component)
return_to_service_action=true
6738510
Specifying the -t option in certain commands
(create, delete, exit, load, reset, set,
start, stop, version) may cause a forced
logout from the ILOM CLI.
None.
6739602
If ActiveDirectory is set to disabled, ignore the
If the logdetail property in
message.
/SP/clients/activedirectory is set to a
value other than "none," the following
authentication error message may be displayed
even if ActiveDirectory is set to disabled (state =
disabled):
sc> ActDir | critical: (ActDir)
authentication status: auth-ERROR
6837115
On the ILOM Web interface, when you change
the "Alert Management" settings from "Level:
minor" and "Type: IPMI PET" to "Type: SNMP
Trap" the level setting changes to "disable." The
level must be set again.
None.
6881020
When you set /HOST bootfailrecovery to
powercycle, powercycle (host power-off/on)
fails to be executed.
None.
Set to poweroff, wait for the host power turns
off and then manually turn on the host power.
40
Workaround
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
6883269
After downgrading the system firmware from
None.
7.2.x to 7.1.x, "Condition" of the I_USB0 and
I_USB1 may be displayed as "fail" in the output
of prtdiag -v command. It can be recovered
by removal/insert of the power cords.
Output Example:
Voltage indicators:
------------------------------------Location
Indicator
Condition
------------------------------------SYS/MB
VCORE_POK
ok
SYS/MB
VMEML_POK
ok
SYS/MB
VMEMR_POK
ok
SYS/MB
I_USB0
fail <SYS/MB
I_USB1
fail <-
6913388
The ILOM event log may not be in the Solaris
OS system log output (/var/adm/messages).
ILOM login event example:
Nov 7 14:13:03 xxxxxx SC Alert: [ID
178418 daemon.notice] Audit | minor:
admin : Open Session :
object = /session/type : value =
shell : success
Nov 7 14:13:04 xxxxxx SC Alert: [ID
434268 daemon.notice] Audit | minor:
admin : Close Session :
object = /session/type : value =
shell : success
None.
Perform the ILOM reset operation. If not
recovered, shut down the system and then
remove and insert the power cord.
ILOM reset operation example:
Log in to ILOM and execute the following
command.
[In case of ILOM command mode]
-> reset /SP
Are you sure you want to reset /SP
(y/n)? y
[In case of ALOM CMT compatible shell]
sc> resetsc
Are you sure you want to reset the
SC [y/n]? y
n/a
After you remove/insert the power cord, or
while POST is running right after the ILOM rest
operation is performed, the "/SYS/XXXXX prom
is unreadable or corrupted" message
may appear and Service Required LED may turn
on. For details, see “After the Power Cord
Removal/Insert, an Error Message May Appear
during the POST” on page 53.
In the following operations, execute the second
operation after an interval of 180 or more
seconds.
• When you power off the system and remove
the power cord
• When you remove the power cord and insert
the power cord
• When you insert the power cord and power
on
Workaround
Chapter 3
Known Issues
41
TABLE 3-3
Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6835866
6857524
6858176
The value of power consumption shown by
/SYS/VPS (/SYS/VPS value) may exceed the
threshold value. At this time, an event log as
shown below will be collected.
Event log example:
4368 Mon Jun 29 23:53:39 2009 IPMI
Log
major
ID = e1f : 06/29/2009 :
23:53:39 : Power Unit : /SYS/VPS : Upper
Critical going high : reading 1480.90 >
threshold 1215.40 Watts
None.
The value of power consumption shown by
/SYS/VPS is given as an indication.
For the right value of power consumption, see
/SP/powermgmt/actual_power.
Therefore, the collected event log can be safely
ignored.
And when the power consumption value
(/SYS/VPS value) has come back to under the
threshold, it may display an abnormal value.
Abnormal value display example:
4369 Mon Jun 29 23:54:28 2009 IPMI
Log
minor
ID = e20 : 06/29/2009 :
23:54:28 : Power Unit : /SYS/VPS : Upper
Critical going low : reading 0 <
threshold 1215.40 Watts
None.
The newly generated ILOM event log is
normally collected.
6952927
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.
For details, see “After Downgraded the System
Firmware, the Log Output May Be Limited to
Part of the Past ILOM Event Log (CR 6952927)”
on page 55.
6659980
None.
When you restarted Solaris OS, OpenBoot
PROM may output the error message "ERROR:
This message has no impact on the system and
Unable to disown USB port 3."
the USB device, and can be safely ignored.
For details, see “When You Restarted Solaris OS,
OpenBoot PROM May Output the Error
Message (CR 6659980)” on page 56.
42
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Problem When the PCIe Link Fails to Train as x8
(CR 6556505)
The system could encounter a problem during a power-on or reset sequence where
the I/O bridge (PCIe root complex) of the UltraSPARC T2 CPU does not train at all
or trains at a lane width less than 8, and no error or fault is generated to indicate to
the user this problem has been encountered.
▼ To Identify the Problem
Though no error or fault is reported, it is easy to identify because no PCIe I/O
devices will be available to the system. If you power on the system, or reset the
domain and try and boot from a disk or network device, and you get an error similar
to the following:
{0} ok boot disk
Boot device: /pci@0/pci@0/pci@2/scsi@0/disk@0
ERROR: boot-read fail
File and args:
Can't locate boot device
{0} ok
1. At the ok prompt, issue the show-devs command.
2. Check the output to for PCIe devices.
If no PCIe devices are displayed, the server has encountered this problem.
Note – All PCIe devices begin with the path /pci@0/pci@0.
▼ To Correct the Problem
1. Take down all domains and power off the system.
Chapter 3
Known Issues
43
2. Run power-on-self-test (POST) to identify whether this is a persistent failure
or not.
To enable POST, use the setsc (an ALOM CMT compatibility CLI command)
and configure POST to run at max level.
For example:
sc> setsc diag_mode normal
sc> setsc diag_level max
3. Power on the system.
POST tests the CPU, memory, and I/O subsystems. If the problem is persistent,
POST will fail the PCIe root complex test and disable the /SYS/MB/PCIE
component.
4. If POST detects the problem, replace the motherboard.
Communication Channel Between the Primary
Domain and the Service Processor (SP) Might
Hang (CR 6583567)
Rarely, a communication channel between the primary domain and the SP might
hang and disable communication over the channel.
Workarounds:
44
■
If the channel is used by a primary domain service or application other than the
fault management daemon (fmd), for example the LDoms Manager ldmd, you
might see warning or error messages concerning communication failures. In this
case, the channel can be brought back up by restarting the affected service or
application.
■
If the channel is the one used by fmd, there are no warning or error messages. fmd
will not receive ereports, and diagnosis of the errors does not occur.
■
If the channel is the one used by the Solaris OS to communicate with the SP, you
could see warning or error messages regarding failure to obtain the PRI, failure to
access ASR data, or failure to set LDoms variables or failure in SNMP
communication. In this case, the channel can be brought back up by resetting the
SP. If the SP is reset, restart the fmd on the primary domain. If resetting the SP
fails to bring the channel back up, then it might also be necessary to reboot the
primary domain.
■
If a domain crashes or a service spontaneously restarts without any associated
fault messages, you must recover as follows to minimize potential loss of error
telemetry.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
▼ To Recover From a Domain Crash
1. Restart fmd on the primary domain.
2. Wait 30 seconds.
3. Reset the SP with either of the following commands:
[In case of ILOM command mode]
-> reset /SP
Are you sure you want to reset /SP (y/n)? y
[In case of ALOM CMT compatible shell]
sc> resetsc
Are you sure you want to reset the SC [y/n]? y
4. Restart fmd on the primary domain.
Enter the following command from the Solaris OS:
# svcadm restart svc:/system/fmd:default
Resetting the SP Produces Extraneous Warning
Messages (CR 6585292)
The following excerpt shows the extraneous messages that should be ignored.
sc> resetsc [similar messages are also displayed for the reset /SP command]
...
Linux version 2.4.22 (kbellew@sanpen-rh4-0) (gcc version 3.3.4) #2
Wed Jul 18 19:25:18 PDT 2007 r21410
Loading modules: fpga Warning: loading
/lib/modules/2.4.22/misc/fpga/fpga.o will taint the kernel: nonGPL license - Proprietary
See http://www.tux.org/lkml/#export-tainted for information
about tainted modules
...
Module fpga loaded, with warnings
fpga_flash Warning: loading
/lib/modules/2.4.22/misc/fpga_flash/fpga_flash.o will taint the
kernel: no license
See http://www.tux.org/lkml/#export-tainted for information
about tainted modules
Module fpga_flash loaded, with warnings
Chapter 3
Known Issues
45
immap Warning: loading /lib/modules/2.4.22/misc/immap/immap.o will
taint the kernel: no license
Refer to: http://www.tux.org/lkml/#export-tainted for information
about tainted modules
Module immap loaded, with warnings
...
EXT3-fs warning: maximal mount count reached, running e2fsck is
recommended
EXT3 FS 2.4-0.9.19, 19 August 2002 on tffs(100,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is
recommended
...
ipt_recent v0.3.1: ... < ... >.
http://snowman.net/projects/ipt_recent/
arp_tables: (C) 2002
802.1Q VLAN Support v1.8 ... < ... >
All bugs added by ...
Error Messages from the Ultra320 SCSI Card
At the time of boot from a device connected with the dual-channel Ultra320 SCSI
Card (SE0X7SC2F, SE0X7SC2X), the following messages may be displayed. Since
these messages do not have an effect on your system behavior, ignore these
messages.
SCSI command timeout occurred
SCSI interrupts not occur
Erroneous Power Supply Faults (CR 6614432)
Some SPARC Enterprise T5120 servers report a low AC line input voltage fault when
the input voltage is in the range of 90V to 94V AC. This is not the correct threshold
and should not indicate an AC input fault until the voltage drops below 90V AC.
Example of erroneous fault messages:
sc> showlogs
Oct 09 14:13:17: Chassis |major
46
: "Host is running"
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Oct 09 14:36:10:
14:36:10 : Power
Oct 09 14:36:11:
14:36:11 : Power
Oct 09 14:36:14:
14:36:14 : Power
IPMI
|minor
: "ID = 264 : 10/09/2007 :
Supply : /PS1/DC_POK : State Deasserted"
IPMI
|minor
: "ID = 265 : 10/09/2007 :
Supply : /PS1/AC_POK : State Deasserted"
IPMI
|minor
: "ID = 266 : 10/09/2007 :
Supply : /PS1/FAIL : State Asserted"
Workaround: Make sure that both server power supplies are operating. When both
power supplies are operating, the server will remain powered on during and after
erroneous faults.
A Built-In Fan May be Erroneously Detected as a
Failure (CR 6636098)
If a built-in fan is erroneously detected as a failure and reported as such to the
Enhanced Support Facility software or Server System Manager software, the
following message is displayed:
Message Example of Enhanced Support Facility:
FJSVmadm:A:FANBD0/FM0/F0/TACH:FJSVmadm:Detected failure on the fan
-----------------(location of a built-in fan. Results may vary.)
Message Example of Server System Manager:
SSMAPL:A::FJSVapplg::status was changed. (component:"FANBD0/FM0" from "normal"
to "fatal")
---------(location of a built-in fan. Results may vary.)
However, entering one of the ILOM status confirmation commands (such as the
showenvironment command) will display the status of the system correctly.
When the actual faulty in a built-in fan is detected, the following sample message is
displayed.
Otherwise a built-in fan is erroneously detected as a failure and the message below
is not displayed.
sc> showfaults
Last POST Run: Fri May 16 14:27:39 2008
Post Status: Passed all devices
Chapter 3
Known Issues
47
ID FRU Fault
1 /SYS/FANBD0/FM0 SP detected fault: TACH at /SYS/FANBD0/FM0/F0 has
exceeded low non-recoverable threshold.
Workaround: Since these messages do not have an effect on your system behavior,
ignore these messages. For the Enhanced Support Facility, this problem is also
resolved by applying the Enhanced Support Facility Patch 914604-04. For Server
System Manager, no workaround is available.
After a Host Power-On Instruction is Executed
from ILOM, the POST May Not Start, and
Processing May Not Go to OS Boot Processing or
the ok Prompt (CR 6752910)
After a host power-on instruction is executed from ILOM, the POST (self-diagnostics
test) may not start, and processing may not go to OS boot processing or the ok
Prompt for OpenBoot PROM (OBP).
[ILOM command interface operation example]
-> start /SYS
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type #.
[ALOM CMT compatibility shell operation example]
sc> poweron
sc> console
Enter #. to return to ALOM.
Nothing is displayed on the OS console. Entering the escape character "#." restores
the ILOM prompt. The result of the Domain Status may vary. No power-on log item
has been recorded in the event log.
showplatform command and showlogs command domain status reference
example:
sc> showplatform
SUNW,SPARC-Enterprise-T5120
Domain Status
------ ------
48
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
S0
Powered off * Domain Status : "Powered on", "Powered off", "OpenBoot
initializing", "Unknown" etc.
sc>
sc> showlogs -p p
Log entries since Sep 29 12:45:39
---------------------------------Sep 29 12:45:39: Chassis |major
: "Host has been powered
Sep 29 12:49:28: Chassis |major
: "Host is running"
Sep 29 12:49:43: Chassis |critical: "Host has been powered
Sep 29 12:50:47: Chassis |major
: "Host has been powered
Sep 29 12:54:35: Chassis |major
: "Host is running"
Sep 29 12:54:51: Chassis |critical: "Host has been powered
"Host has been powered on." log entry after this.
sc>
on"
off"
on"
off" * There is no
For DC Input Power Models, /PS0/AC_POK Is
Displayed (CR 6815369)
For DC input power models, /PS0/AC_POK and /PS0/DC_POK identify sensors in
the power supply units. /PS0/AC_POK does not represent an AC power supply
unit.
For example, the following event log is collected when the DC power cable is
disconnected or reconnected:
[When the DC power cable is disconnected]
IPMI
|minor : "ID = 1cec : 02/06/2009 : 04:00:26 : Power Supply
: /PS0/AC_POK : State Deasserted" <--(*)
IPMI
|minor : "ID = 1ced : 02/06/2009 : 04:00:26 : Power Supply
: /PS0/DC_POK : State Deasserted"
IPMI
|minor : "ID = 1cee : 02/06/2009 : 04:00:26 : Power Supply
: /PS0/FAIL : State Asserted"
[When the DC power cable is reconnected]
IPMI
|minor : "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
: /PS0/DC_POK : State Asserted"
IPMI
|minor : "ID = 1cf1 : 02/06/2009 : 04:00:59 : Power Supply
: /PS0/FAIL : State Deasserted"
Chapter 3
Known Issues
49
Workaround: None.
According to the IPMI PET Warning and SNMP
Trap Warning Settings in the Warning Rule
Settings, Warning Message Creation may not be
Possible Depending on the Event Type (CR
6746677)
According to the IPMI PET warning and SNMP trap warning settings in the warning
rule settings, warning message creation may not be possible depending on the event
type, irrespective of the warning level.
Execution example:
■
"/SYS/MB/component name Disabled by CLI action." or "/SYS/MB/component
name Disabled by user" (critical) is reported with an IPMI PET warning when a
component is disabled by the set /SYS/component-name component_state=
disabled command or disablecomponent command, respectively.
■
"Host has been powered on" (major) is not reported with an IPMI PET warning or
SNMP trap warning when the power to the host is turned on.
■
"/SYS/MB/FT* has exceeded low non-recoverable threshold." (critical) is not
reported when the fan speed of a built-in fan falls below the threshold value.
■
"ERROR: POST errors detected" (major) is not reported with an IPMI PET
warning or SNMP trap warning when an error is detected in a POST (selfdiagnostics test).
In the Logical Domains Environment, After the
Host Reset Operation, Host May Be Reset Again
(CR 6836426)
In the Logical Domains environment, after the host reset operation, host may be
reset again.
Example:
sc> reset -c -y
Reset | major: Reset of /SYS initiated by alom.
Reset | major: Reset of /SYS by alom succeeded.
Performing reset on the system
50
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Enter #. to return to ALOM.
SPARC Enterprise T5220, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.30.2.build_06***PROTOTYPE BUILD***, 2048 MB memory
available, Serial #XXXXXXX.
Ethernet address XX:XX:XX:XX:XX:XX, Host ID: XXXXXXX.
:
:
host1 console login: Chassis | critical: Host has been reset
:
SPARC Enterprise T5220, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.30.2.build_06***PROTOTYPE BUILD***, 2048 MB memory
available, Serial #XXXXXXXXX.
Ethernet address XX:XX:XX:XX:XX:XX, Host ID: XXXXXXX.
:
:
host1 console login:
Workaround: None. The second reset has no impact on the system.
The ILOM Network Configuration Cannot Be Set
(CR 6835854, 6779753)
In case that the NET-MGT port of ILOM has not been connected with the LAN cable
and the network gateway is not set, the ILOM network configuration cannot be set.
Output example when the settings cannot be applied:
-> set /SP/network/ pendingipdiscovery=static
Set 'pendingipdiscovery' to 'static'
-> set /SP/network/ pendingipaddress=192.9.200.33
Set 'pendingipaddress' to '192.9.200.33'
-> set /SP/network/ pendingipnetmask=255.255.255.0
Set 'pendingipnetmask' to '255.255.255.0'
-> set /SP/network/ commitpending=true
set: Unable to get network management property
->
-> show /SP/network/ -d properties
Chapter 3
Known Issues
51
/SP/network
Properties:
commitpending = (Cannot show property)
dhcp_server_ip = none
ipaddress = (none)
ipdiscovery = (none)
ipgateway = (none)
ipnetmask = (none)
macaddress = (none)
pendingipaddress = 192.9.200.33
pendingipdiscovery = static
pendingipgateway = (none)
pendingipnetmask = 255.255.255.0
state = disabled
Workaround: None. Connect the LAN cable to the NET-MGT port of ILOM and then
set the network configuration.
An Error is Registered with the showfaults
Command When Running POST, But POST Ends
Normally (CR 11210193)
If an error occurs during POST execution, "Fault Sensor VCORE_POK at
/SYS/MB deasserted" may be registered when the showfaults ALOM CMT
compatibility command is used for status confirmation. However, POST will still
end normally in this case.
sc> showfaults -v
Last POST Run: Sun Apr 20 17:53:36 2008
Post Status: Passed all devices
ID Time
FRU
Class
1 Apr 19 06:41:14 /SYS/MB
VCORE_POK at /SYS/MB
deasserted
sc>
Fault
SP detected fault: Fault Sensor
Workaround: None. If this problem occurs, use the resetsc ALOM CMT
compatibility command to clear the log and reset the LED display.
52
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
The ok Prompt is Not Displayed After POST Ends
(CR 11215994)
In rare circumstances, the ok prompt may not be displayed normally after POST
execution ends.
Workaround: If this problem occurs, use the showfaults -v ALOM CMT
compatibility command to confirm the status of POST. When the "Last POST
Run" displays the date and time of the POST currently executed and "POST
Status" shows "Passed all devices," this indicates that the POST completed
normally. Execute the resetsc ALOM CMT compatibility command, and then
execute the poweroff and poweron ALOM CMT compatibility commands, in this
order.
2008-04-29 17:10:35.407 0:0:0>........
2008-04-29 17:10:57.749 0:0:0>End : Block Mem Test
2008-04-29 17:10:57.757 0:0:0>INFO:
2008-04-29 17:10:57.766 0:0:0> POST Passed all devices.
2008-04-29 17:10:57.783 0:0:0>POST:
Return to VBSC.
2008-04-29 17:10:57.795 0:0:0>Master set ACK for vbsc runpost
command and spin...
/
sc>
sc> showfaults -v
Last POST Run: Tue Apr 29 17:10:58 2008
Post Status: Passed all devices
No failures found in System
sc>
After the Power Cord Removal/Insert, an Error
Message May Appear during the POST
After you remove/insert the power cord, or while POST is running right after the
ILOM rest operation is performed, the "/SYS/XXXXX prom is unreadable or
corrupted" message may appear and Service Required LED may turn on.
Message example:
Chassis | major: Host has been powered on
0:0:0>
0:0:0>SPARC-Enterprise[TM] T5120/T5220 POST 4.30.6 2009/12/01 13:08
Chapter 3
Known Issues
53
/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
0:0:0>POST enabling CMP 0 threads: ffffffff.ffffffff
0:0:0>VBSC mode is: 00000000.00000001
0:0:0>VBSC level is: 00000000.00000001
0:0:0>VBSC selecting Normal mode, MAX Testing.
0:0:0>VBSC setting verbosity level 2
0:0:0>Basic Memory Tests....Done
0:0:0>Test Memory....Done
0:0:0>Setup POST Mailbox ....Done
0:0:0>Master CPU Tests Basic....Done
0:0:0>Init MMU.....
Fault | critical: SP detected fault at time Mon Jan 18 08:45:10 2010. /SYS/PADCRD
prom is unreadable or corrupted
0:0:0>NCU Setup and PIU link train....Done
0:0:0>L2 Tests....Done
0:0:0>Extended CPU Tests....Done
0:0:0>Scrub Memory....Done
0:0:0>SPU CWQ Tests...Done
0:0:0>MAU Tests...Done
0:0:0>Network Interface Unit Tests....Done
0:0:0>Functional CPU Tests....Done
0:0:0>Extended Memory Tests....Done
2010-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 Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.30.6, 8064 MB memory available, Serial #85367270.
Ethernet address 0:21:28:16:99:e6, Host ID: 851699e6.
{0} ok
This event occurs in any of the following cases:
■
When you power off the system and remove the power cord in a short period of
time
■
When you remove the power cord and insert the power cord in a short period of
time
■
When you insert the power cord and power on in a short period of time
When this event occurred, perform the ILOM reset operation. If recovered, you do
not need to replace the component.
ILOM reset operation example:
54
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Log in to ILOM and execute the following command.
[In case of ILOM command mode]
-> reset /SP
Are you sure you want to reset /SP (y/n)? y
[In case of ALOM CMT compatible shell]
sc> resetsc
Are you sure you want to reset the SC [y/n]? y
Workaround:
In the following operations, execute the second operation after an interval of 180 or
more seconds.
■
When you power off the system and remove the power cord
■
When you remove the power cord and insert the power cord
■
When you insert the power cord and power on
After Downgraded the System Firmware, the Log
Output May Be Limited to Part of the Past ILOM
Event Log (CR 6952927)
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:
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:
cd
show
Chapter 3
Known Issues
55
ID
----4463
4462
4461
Date/Time
Class
Type
Severity
------------------------------- -------- -------Mon Apr 5 06:51:54 2010
Audit
Log
minor
root : Open Session : object = /session/type : value = shell : success
Mon Apr 5 06:39:11 2010
Audit
Log
major
Upgrade Succeeded
Mon Apr 5 06:32:18 2010
Audit
Log
minor
root : Set : object = /config/load_uri : value =
ftp://root:*****@192.9.2
00.254/export/LOG/ilom_backup/LE4-3_728.config : success
Workaround:
None. The newly generated ILOM event log is normally collected.
When You Restarted Solaris OS, OpenBoot PROM
May Output the Error Message (CR 6659980)
When you restarted Solaris OS, OpenBoot PROM may output the error message
"ERROR: Unable to disown USB port 3."
Event example:
# shutdown -i6 -g0 -y
Shutdown started.
Tue Apr 13 16:10:09 JST 2010
Changing to init state 6 - please wait
Broadcast Message from root (console) on xxxxxxx Tue Apr 13 16:10:09...
THE SYSTEM maramba1 IS BEING SHUT DOWN NOW ! ! !
Log off now or risk your files being damaged
# svc.startd: The system is coming down. Please wait.
svc.startd: 101 system services are now being stopped.
Apr 13 16:10:23 xxxxxxx syslogd: going down on signal 15
svc.startd: The system is down.
syncing file systems... done
rebooting...
Resetting...
ERROR: Unable to disown USB port 3
<--
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.
56
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Boot device: disk File and args:
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.
Chapter 3
Known Issues
57
Solaris OS Issues
TABLE 3-4 lists the late-breaking issues related to the running the Solaris OS on the
SPARC Enterprise T5120 and T5220 servers. Additional information for some of the
issues is provided following the table.
Note – Additionally, more general Solaris OS late-breaking issues are described in
the Solaris 10 Release Notes.
TABLE 3-4
Solaris OS Issues
CR
Description
Workaround
6519290
Large amounts of I/O on swap devices might
cause the system to appear hangup by
overwelling the I/O system.
The amount of I/O required may be generated
through a number of ways: memory shortage,
heavy use of /tmp etc.
Set the following to /etc/system and then
reboot the Solaris OS.
set maxfastscan=0x2000
6564180
The Solaris OS locator command does not
work on this server.
Instead, use either the ILOM or ALOM CMT
compatibility locator command as follows:
• From the ILOM CLI:
-> show /SYS/LOCATE/
-> show /SYS/LOCATE/ value=off
-> show /SYS/LOCATE/ value=on
• From the ALOM CMT compatibility CLI:
sc> showlocator
sc> setlocator on
sc> setlocator off
6587380
The Solaris prtdiag -v command displays non- Be aware that the voltage and nonvoltage
information (such as PS0/TEMP_FAULT) is
voltage information in the voltage indicator
accurate and represents the current condition of
section.
the components.
58
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE 3-4
Solaris OS Issues (Continued)
CR
Description
Workaround
6373437
6588499
A Solaris OS shutdown might hang and result in
fewer system services.
Rarely, a shutdown performed immediately after
the Solaris OS boots might cause the system to
hang because some system services are
attempting to stop while others are still in the
process of starting. The hang occurs with a
message similar to the following:
svc.startd: The system is coming down.
Please wait
svc.startd: 74 system services are now
being stopped
Reboot the system by dropping to the service
processor (SP). Then power cycle the host
system using one of the following methods:
• From the ILOM CLI:
-> stop /SYS
-> start /SYS
• From the ALOM CMT compatibility CLI:
sc> poweroff
sc> poweron
sc> powercycle
6607315
Use the virtual console as the input device.
The login prompt resets five seconds after the
Solaris OS boots.
This only occurs when using a local keyboard as
the input device (input-device=keyboard).
This issue does not occur with the virtualconsole.
n/a
The output of the raidctl -h command and
the raidctl man page display some
unsupported features.
The SPARC Enterprise T5120 and T5220 servers
currently only support RAID 0 and RAID 1 for
the o- board SAS disk controller. The raidctl
utility can be used to create and delete RAID 0 &
RAID 1 volumes. Refer to the SPARC Enterprise
T5120 and T5220 Servers Administration Guide for
supported RAID information.
6617544
The prtdiag command doesn't display the fjgi
information of Fujitsu-manufactured card
None.
6617549
In times such as PSU failure, OS outputs the
message; however, the last one character is not
displayed.
None.
6722640
This problem has no effect on your server when
Messages similar to the following might be
displayed during boot.You might not be able to not using SNMP.
get some sensor information when using SNMP.
picld[xxx]: PICL snmpplugin:
sunPlatSensorClass 0 unsupported
Chapter 3
Known Issues
59
TABLE 3-4
Solaris OS Issues (Continued)
CR
Description
Workaround
6836653
USB SATA DVD drive is not supported for the
following versions of the Solaris OS:
• Solaris 10 8/07 OS
• Solaris 10 5/08 OS
Note - USB SATA DVD drive is supported for
the later versions of the Solaris 10 OS, beginning
with Solaris 10 10/08 OS.
To install Solaris 10 8/07 OS or Solaris 10 5/08
OS on a server equipped with a USB SATA DVD
drive, install the OS from the install server and
apply the mandatory patches, the latest periodic
PTF, and the latest recommended security
patches.
For the installation procedures, see “Notes on
Installing Solaris 10 8/07 OS and Solaris 10 5/08
OS” on page 61.
For servers shipped after September 2009, the
USB SATA DVD drive unit has been mounted.
Confirm whether a USB SATA DVD drive unit is
mounted on your server by using either of the
following methods.
• Confirm that the "SATA DVD" mark appears
on the front side of the DVD drive.
• Confirm that specific part numbers are
displayed in the output for the following
ILOM/ALOM commands.
[Confirm by using ILOM command]
Confirm whether either of the following part
numbers is displayed in the output from ls
/SYS/PADCRD command.
fru_part_number = 5413512
or
fru_part_number = 5413513
[Confirm by using ALOM command]
Confirm whether either of the following part
numbers is displayed in the output from
showfru /SYS/PADCRD command.
/Partner_Part_NumberR/Partner_Part_Nu
mber: CF005413512REVxx
or
/Partner_Part_NumberR/Partner_Part_Nu
mber: CF005413513REVxx
60
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Notes on Installing Solaris 10 8/07 OS and Solaris
10 5/08 OS
USB SATA DVD drive is not supported for the Solaris 10 8/07 OS and Solaris 10
5/08 OS.
To install Solaris 10 8/07 OS or Solaris 10 5/08 OS on a server equipped with a USB
SATA DVD drive, install the OS from the install server and apply the mandatory
patches, the latest periodic PTF, and the latest recommended security patches.
The procedure is shown below.
1. Create an install image on the install server.
Example:
This example assumes the DVD medium has been mounted to '/cdmnt'.
#
#
#
#
#
#
#
#
#
#
mkdir -p /export/home/dvd
cd /cdmnt/Solaris_10/Tools
./setup_install_server /export/home/dvd
share |grep /export/home/dvd
share -F nfs -o ro,anon=0 -d "install server directory" /export/home/dvd
svcs -l svc:/network/nfs/server:default
svcadm enable svc:/network/nfs/server
shareall
cd /
eject cdrom
2. Install the OS from the install server.
3. Apply the latest periodic PTF and the latest recommended security patches.
The mandatory patches which are described in the “Mandatory Patch
Information” on page 15 are collected into the periodic PTF R08111 or later. From
the viewpoint of preventive maintenance, apply the latest periodic PTF and the
latest recommended security patches.
To apply the minimum mandatory patches only, apply the patches in the
following order.
■
#
#
#
#
#
■
In case of Solaris 10 8/07 OS
LANG=C;export LANG
patchadd 119254-51
patchadd 125891-01
patchadd 127755-01
patchadd 127127-11
In case of Solaris 10 5/08 OS
Chapter 3
Known Issues
61
There are no mandatory patches.
4. Restart the OS.
# shutdown -i6 -g0 -y
LDoms Related Issues
TABLE 3-5 lists the late-breaking LDoms related issues. Additional information for
some of the issues is provided following the table.
TABLE 3-5
LDoms Related Issues
CR
Description
6540368
In Logical Domains 1.0.1 software, there are a
For more information, refer to the Logical
few cases where variable updates do not persist. Domains (LDoms) 1.0.1 Release Notes.
6597815
XAUI and CPU resources added after initial
LDoms Setup are not available to LDoms
Manager.
62
Workaround
When you add CPU or XAUI resources to a
server configured to use logical domains, you
must revert to the factory default configuration
to allow the LDoms Manager software to
allocate those resources to guest domains.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
CHAPTER
4
Documentation Errata
This chapter describes known errors and corrections to the SPARC Enterprise T5120
and T5220 server documentation.
■
“SPARC Enterprise T5120 and T5220 Servers Site Planning Guide” on page 63
■
“SPARC Enterprise T5120 and T5220 Servers Installation Guide” on page 68
■
“SPARC Enterprise T5120 and T5220 Servers Service Manual” on page 68
■
“SPARC Enterprise T5120 and T5220 Servers Administration Guide” on page 71
■
“Integrated Lights Out Manager 2.0 User's Guide” on page 71
■
“Integrated Lights Out Manager 2.0 Supplement for the SPARC Enterprise T5120
and T5220 Servers” on page 72
■
“Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide” on page 73
■
“Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide” on
page 74
■
“Integrated Lights Out Manager (ILOM) 3.0 Supplement for SPARC Enterprise
T5120 and T5220 Servers” on page 75
SPARC Enterprise T5120 and T5220
Servers Site Planning Guide
Error on page 2 in "Minimum Clearance for
Service Access"
The text in "Minimum Clearance for Service Access" on page 2 contains an error.
63
The correct text is as follows:
The SPARC Enterprise T5120/T5220 servers require physical access from the top for
maintenance. Therefore, a stepladder may be required depending on which rack the
server is installed in. And it may be necessary to remove the server from the rack
depending on the component to be replaced.
The minimum clearance for service access varies depending on whether a stepladder
is used. Secure an appropriate clearance for service access before starting
maintenance.
This section shows the minimum clearance for service access premised on the
standard maintenance work of our company. If this minimum clearance cannot be
secured, contact our field engineer.
No stepladder is required if this server is installed at the 20U level or lower. A
stepladder is required if it is installed at the 21U level or higher. FIGURE 1 shows the
minimum clearance for service access required for either server.
FIGURE 1
Minimum Clearance for Service Access
1. If the server is installed at the 20U level or lower (*1): (*1 Judged based on the
level of the equipment top)
Rear-side clearance for service access
800mm
Equipment rack
1050mm
Front-side clearance for service access
1700mm
800mm
64
700mm
800mm
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
2. If the server is installed at a level between 21U and 40U (*1): (*1 Judged based on
the level of the equipment top)
Rear-side clearance for service access
800mm
Equipment rack
1050mm
Front-side clearance for service access
1300mm
800mm
1400mm
700mm
1400mm
Chapter 4
Documentation Errata
65
Incorrect Values for the 1.6 GHz SpecJBB Test
Tables 5, 7, and 8 of the Site Planning Guide contain incorrect values for the peak
input power when running SpecJBB in a system with 1.6 GHz CPUs and a maximum
memory, HDD, and PCIe card configuration. The following tables provide the
correct values.
Table 5: SPARC Enterprise T5120 Server (4-Disk Capable) Power Specifications
Maximum Server Configuration Specifications
8 core, 1.6 GHz processor, with sixteen 4 GB FBDIMMs, 4 HDDs, 3 PCIe I/O cards
Peak input power running SpecJBB
Incorrect Value
(AC Input)
Correct Value
(AC Input)
Incorrect Value
(DC Input)
Correct Value
(DC Input)
615.3 W
624.3W
574.7 W
583.1W
Table 7: SPARC Enterprise T5220 Server (8-Disk Capable) Power Specifications
Maximum Server Configuration Specifications
8 core, 1.6 GHz processor, with sixteen 4 GB FBDIMMs, 8HDDs, 6 PCIe I/O cards
Peak input power running SpecJBB
Incorrect Value
(AC Input)
Correct Value
(AC Input)
Incorrect Value
(DC Input)
Correct Value
(DC Input)
807.4 W
814.4W
754.1 W
760.7W
Table 8: SPARC Enterprise T5220 Server (16-Disk Capable) Power Specifications
Maximum Server Configuration Specifications
8 core, 1.6 GHz processor, with sixteen 4 GB FBDIMMs, 16 HDDs, 6 PCIe I/O cards
Peak input power running SpecJBB
66
Incorrect Value
(AC Input)
Correct Value
(AC Input)
Incorrect Value
(DC Input)
Correct Value
(DC Input)
901.5 W
908.5W
842.0 W
848.6W
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Incorrect Idle Input Power Values
Four tables in the SPARC Enterprise T5120 and T5220 Site Planning Guide contain
incorrect values for the idle input power. The following four tables show the correct
information for those tables:
Table 5: SPARC Enterprise T5120 Server (4-Disk Capable) Power Specifications
Minimum Server Configuration Specifications
4 core, 1.2 GHz processor, with four 1 GB FBDIMMs, no HDDs, no PCIe I/O cards
Idle input power
Incorrect Value
(AC Input)
Correct Value
(AC Input)
Incorrect Value
(DC Input)
Correct Value
(DC Input)
187.0 W
179.0 W
174.7 W
167.2 W
Table 6: SPARC Enterprise T5120 Server (8-Disk Capable) Power Specifications
Minimum Server Configuration Specifications
4 core, 1.2 GHz processor, with four 1 GB FBDIMMs, no HDDs, no PCIe I/O cards
Idle input power
Incorrect Value
(AC Input)
Correct Value
(AC Input)
Incorrect Value
(DC Input)
Correct Value
(DC Input)
187.0 W
179.0 W
174.7 W
167.2 W
Table 7: SPARC Enterprise T5220 Server (8-Disk Capable) Power Specifications
Minimum Server Configuration Specifications
4 core, 1.2 GHz processor, with four 1 GB FBDIMMs, no HDDs, no PCIe I/O cards
Idle input power
Incorrect Value
(AC Input)
Correct Value
(AC Input)
Incorrect Value
(DC Input)
Correct Value
(DC Input)
194.0 W
186.0 W
181.2 W
173.7 W
Table 8: SPARC Enterprise T5220 Server (16-Disk Capable) Power Specifications
Minimum Server Configuration Specifications
4 core, 1.2 GHz processor, with four 1 GB FBDIMMs, no HDDs, no PCIe I/O cards
Idle input power
Incorrect Value
(AC Input)
Correct Value
(AC Input)
Incorrect Value
(DC Input)
Correct Value
(DC Input)
194.0 W
186.0 W
181.2 W
173.7 W
Chapter 4
Documentation Errata
67
SPARC Enterprise T5120 and T5220
Servers Installation Guide
This manual includes descriptions using the cable management arm (CMA);
however, the SPARC Enterprise T5120 server doesn't support the cable management
arm.
Verify Proper Seating of Preinstalled PCIe/XAUI
Cards
The server installation procedure should include instructions for verifying that any
preinstalled 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.
Workaround: When installing a newly arrived server that has preinstalled PCIe
and/or XAUI cards, open it and verify that the cards and their risers are securely
seated. Also verify that the internal cables are correctly routed and securely
connected. Refer to the SPARC Enterprise T5120 and T5220 Servers Service Manual for
information about the PCIe/XAUI cards and their risers as well as information about
internal cable routing.
SPARC Enterprise T5120 and T5220
Servers Service Manual
Erroneous Description in the Section "Disconnect
Power Cords From the Server"
The following description in the section "Disconnect Power Cords From the Server"
is incorrect.
■
68
Unplug all power cords from the server.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Caution – Because 3.3v standby power is always present in the system, you must
unplug the power cords before accessing any cold-serviceable components.
The correct information is as follows:
■
For AC models – Unplug all power cords from the server.
■
For DC models – Turn off the power at the power source circuit breaker.
Caution – When power is applied to the server (even when the host is powered off)
the 3.3v standby power is present in the system, so you must remove power before
accessing any cold-serviceable components.
Erroneous Description in the Section "Removing
the Air Duct" on page 101
The following description in the section "Removing the Air Duct" on page 101 is
incorrect.
3. (SPARC Enterprise T5120 server; 8 drive-capable) Disconnect and stow the hard
drive data cable.
a. Route the hard drive data cable over the fan module and along the air duct.
b. Plug the data cable into J6401 on the motherboard.
The correct information is as follows:
3. (SPARC Enterprise T5120 server, 8-HDD model) Disconnect and stow the hard
drive data cable.
a. Unplug the hard drive data cable from J6401 on the motherboard.
b. Remove the hard drive data cable from its seat on the CPU air duct.
c. Place the hard drive cable end out of the way of the air duct.
Chapter 4
Documentation Errata
69
Erroneous Description in "Fan Module
Configurations for SPARC Enterprise T5220
Servers (8- and 16-Disk Capable)"
The description in the section "Fan Module Configurations for SPARC Enterprise
T5220 Servers (8- and 16-Disk Capable)" is incorrect. The fan module configurations
are different between 8-disk capable and 16-disk capable servers. The correct
configurations are as follows:
TABLE:
SPARC Enterprise T5220 (8 Hard Drive Capable) Fan Module Locations and
FRU Names
(Empty)
(Empty)
(Empty)
/SYS/FANBD0/FM0
/SYS/FANBD0/FM1
/SYS/FANBD0/FM2
Front of system
TABLE:
SPARC Enterprise T5220 (16 Hard Drive Capable) Fan Module Locations and
FRU Names
(Empty)
/SYS/FANBD1/FM1
(Empty)
/SYS/FANBD0/FM0
/SYS/FANBD0/FM1
/SYS/FANBD0/FM2
Front of system
Unnecessary Procedure in "Install the Hard Drive
Cage"
The following procedure in "Install the Hard Drive Cage" is unnecessary and can be
ignored.
3. (SPARC Enterprise T5120 server, 8 disk-capable) Remove fan FM1.
Incorrect FRU Name is Specified in the TABLE:
Motherboard Components (SPARC Enterprise
T5120 Servers)
The FRU Name of /SYS/MB/SC/SCC_NVRAM should be
/SYS/MB/SCC_NVRAM.
70
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Incorrect FRU Name is Specified in the TABLE:
Motherboard Components (SPARC Enterprise
T5220 Servers)
The FRU Name of /SYS/MB/SC/SCC_NVRAM should be
/SYS/MB/SCC_NVRAM.
SPARC Enterprise T5120 and T5220
Servers Administration Guide
Notes on the "SPARC Enterprise T5x20 Device
Tree"
The device tree of the DVD drive indicated on page 39 is not supported for the
servers shipped after September 2009. The correct tree is as follows:
■
For the servers shipped after September 2009
/pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/hub@4/device@4/storage@
0/disk
Integrated Lights Out Manager 2.0 User's
Guide
Incorrect ILOM Command Related to IP Address
Assignment
The ILOM commands indicated on page 23 and page 28 include erroneous
information.
setpendingipdiscovery= should be set pendingipdiscovery=.
Chapter 4
Documentation Errata
71
The Command in the Section "Edit an SNMP User
Account Using the CLI" on Page 195 is Incorrect
The following command described is incorrect.
edit /SP/services/snmp/users/username authenticationpassword=
password
To edit an SNMP v3 user account, type the following command:
set /SP/services/snmp/users/username authenticationpassword=
password
Integrated Lights Out Manager 2.0
Supplement for the SPARC Enterprise
T5120 and T5220 Servers
Points of Concern about the Connection of ILOM
(CR 6806789)
On the SPARC Enterprise T5120 and T5220 servers, ILOM supports a maximum of 5
active sessions, including serial, Secure Shell (SSH), and web interface sessions.
About ALOM CMT Shell Command
This manual focuses on the basic usage of the ALOM CMT compatibility shell
command. For details of the ALOM CMT shell command, see Advanced Lights Out
Management (ALOM) CMT v1.x Guide (C120-E386).
72
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Integrated Lights Out Manager (ILOM) 3.0
CLI Procedures Guide
Erroneous Description in "Collect SP Data to
Diagnose System Problems" (CR 6806800)
The following description in the section "Collect SP Data to Diagnose System
Problems" on page 88 includes incorrect information.
Variable
Option
Description
URI
Any valid target
directory location
Specifies the URI of the target directory. The URI format
is as follows:
protocol://username:password@host/directory
Where protocol can be one of these transfer methods:
SFTP, TFTP, or FTP.
For example, to store the snapshot information in the
directory named data on the host, define the URI as
follows:
ftp://joe:mypasswd@host_ip_address/data
The directory data is 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.
Erroneous Default Value for /SP/clients/dns
The default value for /SP/clients/dns indicated on page 29 and page 144 is
incorrect. The correct value is "enabled."
Chapter 4
Documentation Errata
73
Erroneous Description about Collecting SP Data
The following description in the section "Collect SP Data to Diagnose System
Problems" on page 88 includes incorrect information.
Variable
Option
Description
data
full
Specifies that all data is to be collected ("full" collection).
Note - Using this option may reset the running host.
On the SPARC Enterprise T-series servers, when you specified the full option, the
host in execution will not be reset. While the host is executing, you can specify the
full option.
New URL for Downloading System Firmware
The URL for downloading system firmware, which is indicated on page 113 in the
Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide and on page 105 in the
Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, has been
changed as follows:
■
New URL
https://updatesite.jp.fujitsu.com/unix/en/download/firmware/
Integrated Lights Out Manager (ILOM) 3.0
Web Interface Procedures Guide
Erroneous Description about Collecting SP Data
The following description in the section "Collect SP Data to Diagnose System
Problems" on page 79 includes incorrect information.
3. Select the desired Data Set: Normal, Full, or Custom.
74
■
Normal – Specifies that ILOM, operating system, and hardware information is
collected.
■
Full – Specifies that all data is to be collected. Selecting Full might reset the
system.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
■
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, the
host in execution will not be reset. While the host is executing, you can specify the
full option.
New URL for Downloading System Firmware
The URL for downloading system firmware, which is indicated on page 113 in the
Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide and on page 105 in the
Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, has been
changed as follows:
■
New URL
https://updatesite.jp.fujitsu.com/unix/en/download/firmware/
Integrated Lights Out Manager (ILOM) 3.0
Supplement for SPARC Enterprise T5120
and T5220 Servers
Notes on "ILOM Information Stored on the SCC"
When transferring the SCC to the replacement server, keep the following note in
mind.
Note – If the ILOM versions are different between the failed server and the
replacement server, the settings on the SCC(NVRAM) will be ignored or overwritten.
If the ILOM versions are the same, the settings will be retained.
Chapter 4
Documentation Errata
75
76
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
APPENDIX
A
Fixed Issues
This appendix describes the fixed issues concerning the SPARC Enterprise T5120 and
T5220 servers. You can avoid the issues by using the latest version of Solaris OS,
System Firmware, or other software. For details on the fix, see the "workaround" in
each table.
■
“Hardware and Mechanical Issues” on page 77
■
“Ethernet Interface Related Issues” on page 79
■
“Firmware, ILOM, POST, and SP Issues” on page 86
■
“Solaris OS Issues” on page 127
■
“LDoms Related Issues” on page 146
Hardware and Mechanical Issues
TABLE A-1 lists the hardware and mechanical issues that have been fixed.
TABLE A-1
Fixed Hardware and Mechanical Issues
CR
Description
Workaround
6592272
An uncorrectable L2 writeback error might
generate a memory fault message (SUN4V8000-E2) to the console.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
See “L2 Cache Errors Might Generate an
Erroneous Memory Fault (CR 6592272)” on
page 78.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
77
TABLE A-1
Fixed Hardware and Mechanical Issues (Continued)
CR
Description
Workaround
6616209
6617012
A power supply fan failure might not generate a
fault.
Note - This issue only applies to fan failures in
power supply 0. A fan failure in power supply 1
will generate a fault.
Note - Fixed in System Firmware 7.0.9 or later.
To ensure continuous operation during a
possible power supply fan fault, ensure that
both power supplies are connected to two
separate power circuits.
L2 Cache Errors Might Generate an Erroneous
Memory Fault (CR 6592272)
This issue is resolved for servers running the Solaris 10 5/08 OS and later. If you are
running Solaris 10 8/07, you can fix this issue with patch ID 127127-11 or later.
In earlier versions, the issue shows up after an uncorrectable L2 writeback error. A
bogus memory fault message (SUN4V-8000-E2) might be reported to the console.
Example:
SUNW-MSG-ID: SUN4V-8000-E2, TYPE: Fault, VER: 1, SEVERITY: Critical
EVENT-TIME: Wed Sep 5 18:49:35 EDT 2007
PLATFORM: SUNW,SPARC-Enterprise-T5220, CSN: -, HOSTNAME: wgs48-100
SOURCE: cpumem-diagnosis, REV: 1.6
EVENT-ID: 59bf6418-5dcb-c1b0-b06a-f26fa18e4ee7
DESC: The number of errors associated with this memory module has
exceeded acceptable levels. Refer to http://sun.com/msg/SUN4V8000-E2
for more information.
AUTO-RESPONSE: Pages of memory associated with this memory module
are
being removed from service as errors are reported.
IMPACT: Total system memory capacity will be reduced as pages are
retired.
Workaround: Use fmdump -eV -u uuid with the UUID from the console message to
determine if the memory error is bogus. For example:
# fmdump -eV -u 59bf6418-5dcb-c1b0-b06a-f26fa18e4ee7 | grep dram-esr
dram-esr = 0x1000000000008221
If the dram-esr is 0x1000000000008221, this CR 6592272 has been encountered,
and the memory error can be ignored. No memory component replacement is
necessary. Use fmadm repair uuid to repair the bogus memory error.
78
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
If the dram-esr is different, schedule a repair procedure to replace the affected
memory module. Use fmdump -v -u event_id to identify the module.
Ethernet Interface Related Issues
TABLE A-2 lists the Ethernet related issues that have been fixed.
TABLE A-2
Fixed Ethernet Related Issues
CR
Description
Workaround
6551509
If you run modunload while the nxge port is
running, a system panic might occur.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Unplumb the interfaces prior to unloading the
driver. See “Using modunload While the nxge
Port Is Running, Could Cause a System Panic
(CR 6551509)” on page 80.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
6554478
Receiving Jumbo Frames might drop the
Ethernet interface to 30 Mbps due to packet
dropping.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Set the MTU size to 8172 as described in “Jumbo
Frames Throughput of nxge Drops to 30 Mbps
Due to Packet Dropping (CR 6554478)” on
page 82.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
6561389
Setting properties for the network interface unit
(NIU) nxge devices could fail.
For an example of the failure, see “Setting
Properties for nxge Devices Might Fail (CR
6561389)” on page 84.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Use the global declaration without the device
path in the nxge.conf file. For example, add
the following line to the nxge.conf file:
accept_jumbo = 1;
You can also upgrade the OS or install the patch
to avoid encountering this issue.
Appendix A
Fixed Issues
79
TABLE A-2
Fixed Ethernet Related Issues (Continued)
CR
Description
Workaround
6567838
The server might panic in nxge_start when
the dupb fails.
If Jumbo Frames are enabled, the system might
panic as a result of a NULL pointer reference.
This scenario is only possible when frame sizes
are larger than 4076. Jumbo Frames with MTU=
9194 do not experience this problem.
Note - This scenario is rare, and only occurs with
frame sizes larger than 4076.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Disable the use of Jumbo Frames, but be aware
that doing so impacts system performance. You
should only apply the workarounds if your
server is experiencing this problem. For details
on this workaround, see “Server Might Panic in
nxge_start When dupb Fails (CR 6567838)” on
page 84.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
6599334
XAUI interfaces might not be disabled when
they should be disabled.
Normally, when a CPU network interface unit
(NIU) is disabled (either through POST detected
faults or manually), the corresponding XAUI
interface (if one is installed) should also be
disabled, but that does not happen.
Note - Fixed in System Firmware 7.1.6.d or
later.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6599105
Jumbo does not work for packets larger than
8144 bytes when bcopy is forced.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
Using modunload While the nxge Port Is
Running, Could Cause a System Panic (CR
6551509)
This issue is resolved for servers running the Solaris 10 5/08 OS and later. If you are
running Solaris 10 8/07, you can fix this issue with patch ID 127127-11 or later.
If you run the modunload command on the nxge driver while it is running, the
system could panic. Due to an issue in the nxge driver, it is possible, though very
unlikely, that the nxge driver could cause a panic during a system reboot. This panic
occurs if the system is still transferring substantial amounts of network data over an
nxge interface while the system is shutting down. It is very unlikely that this
condition will occur in normal circumstances.
80
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
The panic message is mutex_enter: bad mutex, ...
The panic stack will include the two nxge driver functions nxge_freeb() and
nxge_post_page().
If such a panic occurs, the system will recover, and continue to reboot normally. The
system, including the nxge interfaces, will come back up with no further panics.
Workaround: Unplumb the interfaces prior to unloading the driver.
▼ To Unplumb the Interfaces Prior to Unloading the Driver
It is usually not necessary to unload a driver from a running kernel. In those rare
cases where it might be called for, you must unplumb all driver instances prior to
unloading the driver.
1. Find out which nxge instances are plumbed (active) using the ifconfig
command:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS>
mtu 1500 index 2
inet 129.153.54.82 netmask ffffff00 broadcast 129.153.54.255
ether 0:14:4f:2a:9f:6a
nxge2: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS>
mtu 1500 index 19
inet 129.153.54.175 netmask ffffff00 broadcast 129.153.54.255
ether 0:14:4f:6c:85:aa
nxge3: flags=201000803<UP,BROADCAST,MULTICAST,IPv4,CoS> mtu 1500
index 20
inet 129.153.54.171 netmask ffffff00 broadcast 129.153.54.255
ether 0:14:4f:6c:85:ab
2. Unplumb each active port (each port named nxge plus an instance number, for
example, nxge2, nxge3, . . .). Example:
# ifconfig nxge2 unplumb
# ifconfig nxge3 unplumb
Appendix A
Fixed Issues
81
3. Run ifconfig -a again to verify that there are no active nxge interfaces.
Example:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS>
mtu 1500 index 2
inet 129.153.54.82 netmask ffffff00 broadcast 129.153.54.255
ether 0:14:4f:2a:9f:6a
It is now safe to unload the nxge driver.
Jumbo Frames Throughput of nxge Drops to 30
Mbps Due to Packet Dropping (CR 6554478)
This issue is resolved for servers running the Solaris 10 5/08 OS and later. If you are
running Solaris 10 8/07, you can fix this issue with patch ID 127127-11 or later.
Receive-side performance of the nxge driver drops significantly if the following two
conditions are true:
■
Jumbo Frames are enabled because the following line is present and not
commented out in the nxge.conf file:
accept_jumbo=1
The nxge.conf file is in the /platform/sun4v/kernel/drv directory on
sun4v systems, and it is in the /platform/sun4u/kernel/drv directory on
sun4u systems.
■
Maximum Transmission Unit (MTU) is set to a value larger than 8172. When
Jumbo Frames are enabled, the MTU size defaults to 9194.
Note – Refer to the Sun Quad GbE UTP x8 PCIe ExpressModule User’s Guide, the Sun
Dual 10GbE XFP PCIe ExpressModule User’s Guide, the Sun x8 Express Dual 10 Gigabit
Ethernet Fiber XFP Low Profile Adapter User’s Guide, or the Sun x8 Express Quad Gigabit
Ethernet UTP Low Profile Adapter User’s Guide for details.
82
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
▼ To Set the MTU Size to 8172
If Jumbo Frames are enabled, use this procedure to set the MTU to a value of 8172.
This procedure uses port1 as an example.
1. Edit or create an /etc/hosts file and add the following line in it:
99.99.9.1 nxge-port1
Where nxge-port1 is the name you give to the interface, and 99.99.9.1 is the IP
address you want to assign to the interface.
2. Edit or create a /etc/hostname.nxge1 file and place the following two lines
in it:
nxge-port1
nxge-port1 mtu 8172
3. If you want the system to set the netmask to a special value automatically, add
the following line in the /etc/netmasks file (using netmask FFFFFF00 as an
example):
99.99.9.1 255.255.255.0
4. Reboot the system.
In this example, the nxge1 interface is automatically plumbed with IP address
99.99.9.1, MTU value 8172 and netmask ffffff00.
5. Type ifconfig -a to confirm the configuration:
# ifconfig -a
nxge1: flags=1201000802<BROADCAST,MULTICAST,IPv4,CoS,FIXEDMTU>
mtu 8172 index 3
inet 99.99.9.1 netmask ffffff00 broadcast 99.255.255.255
ether 0:14:4f:6c:88:5
If you want to set parameters permanently for other interfaces, create
/etc/hostname.nxge0, /etc/hostname.nxge2 and /etc/hostname.nxge3
similarly, and add the name IP-address pairs to the same /etc/hosts file. Also add
their netmasks to the same /etc/netmasks file.
Appendix A
Fixed Issues
83
Setting Properties for nxge Devices Might Fail
(CR 6561389)
This issue is resolved for servers running the Solaris 10 5/08 OS and later. If you are
running Solaris 10 8/07, you can fix this issue with patch ID 127127-11 or later.
Setting a property for an nxge device node might not work correctly. The following
is an example:
name="SUNW,niusl" parent="/niu@80" unit-address="0" accept_jumbo=1;
name="SUNW,niusl" parent="/niu@80" unit-address="1" accept_jumbo=1;
Entries from /etc/path_to_inst:
/niu@80" 0 niumx
/niu@80/network@0" 0 nxge
/niu@80/network@1 1 nxge
Entries from /etc/driver_aliases:
niumx "SUNW,niumx
nxge "SUNW,niusl
Workaround: Use the global declaration without the device path in the nxge.conf
file. For example, add the following line to the nxge.conf file.
accept_jumbo = 1;
Server Might Panic in nxge_start When dupb
Fails (CR 6567838)
This issue is resolved for servers running the Solaris 10 5/08 OS and later. If you are
running Solaris 10 8/07, you can fix this issue with patch ID 127127-11 or later.
If Jumbo Frames are enabled, it is possible for the system to panic as a result of a
NULL pointer reference. This scenario is only possible when frame sizes are larger
than 4076. Jumbo Frames with MTU=9194 do not experience this problem.
Workaround: Disable Jumbo Frames or use a smaller MTU size as described in the
following procedures.
▼ To Disable Jumbo Frames
Disabling Jumbo Frames or using Jumbo Frames with a smaller MTU impacts
system performance. Only perform the following steps if the system panics due to
Jumbo Frames.
84
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
1. Edit the /platform/sun4v/kernel/drv/nxge.conf file, and ensure that
any line with accept_jumbo=1; is commented out.
2. Ensure that there is no set nxge:nxge_jumbo_enable=1 in the
/etc/system file.
▼ To Set the MTU to a Smaller Size
If you want to use Jumbo Frames, you can use this workaround instead of disabling
Jumbo Frames. This procedure sets the MTU to a value equal to or smaller than 4076,
using port1 as an example.
Note – By following these steps, the MTU values are permanent. As an alternative,
you can run the command ifconfig nxgeX mtu 4076 (where X is the instance
number), but the MTU value will change back to the default one after a reboot.
1. Edit or create an /etc/hosts file and add the following line in it:
99.99.9.1
nxge-port1
Where nxge-port1 is the name you assign to the interface. 99.99.9.1 is the IP
address you want to assign to the interface.
2. Create an /etc/hostname.nxge1 file and place the following two lines in it:
nxge-port1
nxge-port1 mtu 4076
Appendix A
Fixed Issues
85
Firmware, ILOM, POST, and SP Issues
TABLE A-3 lists the firmware, ILOM, POST, and SP issues that have been fixed.
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues
CR
Description
Workaround
6541482
POST always starts on the lowest available
strand even when that strand is disabled.
If processor strand 0 of the first available
physical core has been marked disabled (as seen
in the list of disabled devices in the output of the
showcomponent command), a new master
strand is selected by the initialization process,
and the disabled strand is taken offline. But the
system initialization and execution of power-onself-test (POST) occurs using the disabled
processor strand, because power on and reset
execution always starts on strand 0 of the first
available physical core.
When this situation happens, the system might
fail to run the diagnostics and the system might
fail in an unpredictable manner. The system
might not start the required firmware and
software components as a result.
Note - Fixed in System Firmware 7.1.6.d or later.
If strand 0 of the first physical core is known to be
good, then it can be enabled by using the
enablecomponent ALOM CMT compatibility
command followed by power-on reset of the
system (poweroff followed by poweron ALOM
CMT compatibility commands).
If strand 0 of the first physical core is known to be
bad, there is no workaround. The motherboard
must be replaced.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6549028
The netsc_commit command might cause the
system to hang.
Through a serial connection, the network might
not be visible.
Note - Fixed in System Firmware 7.1.6.d or later.
Reboot the system.
If rebooting fails to reset the SP, AC power cycle
the system to recover the SP. Be aware that you
will lose active domains.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6583392
6571886
POST might encounter intermittent POST PIU0
link train errors during a power cycle test.
Note - Fixed in System Firmware 7.1.6.d or later.
Power cycle the system as follows (example uses
the ALOM CMT compatibility CLI):
sc> poweroff -fy
sc> clearasrdb
sc> poweron -c
You can also update the System Firmware to the
latest version to avoid encountering this issue.
86
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6577528
A terminal server break command does not
work on the SP serial port.
If you use Telnet to connect to the SP serial line
with a terminal server (such as the Cisco ASM
series) and try to send a break to the Solaris
host, the break command does not work and is
ignored by the SP. For a sample output, see “SP
Serial Line Terminal Server break Command
Does Not Work (CR 6577528)” on page 105.
Note - Fixed in System Firmware 7.1.6.d or later.
Use the break commands from the SP (either the
ILOM or ALOM CMT compatibility commands)
to send a break to the Solaris host.
Refer to the Integrated Lights Out Management
(ILOM) Supplement for SPARC Enterprise T5120 and
T5220 Servers for details.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6579390
After disabling a DIMM, the OpenBoot PROM
banner does not show a decrease in the amount
of memory.
Note - Fixed in System Firmware 7.2.2.e or later.
If you manually disable any CPU or memory
resource with the ASR commands while the host
is powered on, you must power cycle the host to
complete the disabling of the resource.
After the power cycle, the resource will be
disabled, and the proper information will be
displayed in the banner.
6581309
Console behavior is inconsistent when a
graphics device and keyboard are specified for
console use.
This behavior occurs when the OpenBoot
variables input-device and output-device
are set to anything other than the default value
of virtual-console.
If the control domain is set this way, some
console messages are sent to the graphics
console and others are sent to the virtual
console. This situation results in incomplete
information on both consoles. In addition, when
the system is halted, or a break is sent to the
console, control is passed to the virtual console,
which requires keyboard input over the virtual
console. As a result, the graphics console
appears to hang.
Note - Fixed in Solaris patch ID 137111-01 or
later.
If the graphics console appears hung, connect to
the virtual console from the system processor to
provide the required input. Press Return on the
virtual console keyboard once to see the output
on the virtual console. If this workaround does
not work, contact your service engineer.
When you are connected to the virtual console
and you enter the escape character sequence
(#.) to enter the SP CLI, the following two error
messages might display before reaching the CLI
prompt:
read: Connection reset by peer
Write to vbsc: Illegal seek
This situation occurs when there is a lot of
output through the console, and implies that the
console is in use when it is not.
Note - Fixed in System Firmware 7.2.2.e or later.
If you are refused write access when you initiate a
connection to the host with the console
command, enter console -f (the force option)
to get read and write access.
6582340
To prevent the problem, perform one of the
following workarounds:
• Install patch ID 137111-01 (or higher).
• Use only the virtual console. Ensure that the
default value of virtual-console is set for
both the input-device and output-device
variables.
Appendix A
Fixed Issues
87
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6582853
The showfaults ALOM CMT compatibility
command reports the motherboard as faulty
instead of the actual faulty DIMM or PCIe card.
Note - Fixed in System Firmware 7.1.6.d or later.
Use the fault management utilities that are
described in the Predictive Self-Healing (PSH)
Knowledge Articles located at:
http://www.sun.com/msg/MSGID
(MSGID is the PSH Message ID.)
For more information see “The showfaults
Command Shows the Motherboard as Faulty
Instead of the DIMM (CR 6582853)” on page 106.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6585340
The uadmin 2 0 and reboot commands read
old bootmode settings.
Note - Fixed in System Firmware 7.1.6.d or later.
See “The uadmin 2 0 and reboot Commands
Read Old Bootmode Settings (CR 6585340)” on
page 107.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6587869
Using the consolehistory -e command with
a value greater than 1000 might result in the SP
becoming unusable.
Note - Fixed in System Firmware 7.1.6.d or later.
To see the entire consolehistory log, use the v option.
If you need to recover from problems related to
running the consolehistory command with
more than 1000 lines, reboot the SP.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6587919
The first time that show /SYS is executed after Note - Fixed in System Firmware 7.1.6.d or later.
a power on, (none) is displayed for the product Use the show /SYS command again and the
name.
product name is displayed.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6588999
When you connect to the ILOM CLI with SSH
and the SP is reset, you might see an error
message similar to the following:
Performing hard reset on /SP failed
reset: Transport error - check errno for
transport error
88
Note - Fixed in System Firmware 7.1.6.d or later.
This error can be ignored. The command actually
succeeds and the SP is reset. When the SP resets,
you lose the SSH connection to the SP.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6589043
If there are fewer than 21 entries in the event
log, the showlogs command displays none of
the events.
This situation is known to occur in the following
scenarios:
• After a fresh installation of the system (out-ofbox), the service processor (SP) event log is
very likely to have fewer than 21 entries.
• After you clear the SP event log with the
browser interface (BI), or ILOM CLI, the
ALOM CMT compatibility CLI showlogs
command displays no new events until at
least 21 new events are logged.
Note - Fixed in System Firmware 7.1.6.d or later.
Use the showlogs -v option to display the logs.
After 21 or more events are logged in the log file,
you can revert back to using showlogs with no
options.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6591367
You cannot obtain the system DIMM FRU
information with the ipmitool utility.
Note - Fixed in System Firmware 7.1.6.d or later.
Obtain the DIMM FRU information using the SP
ALOM CMT compatibility CLI (with the
showfru command) or the SP ILOM CLI (with
the show fru-name command). Refer to the
Integrated Lights Out Management (ILOM)
Supplement for SPARC Enterprise T5120 and T5220
Servers for details.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6593547
An erroneous watchdog reset error might occur.
If this error occurs, the system will not complete
the boot sequence. You might see the following
error in either the I/O or the Control domain
when attempting to boot and the boot sequence
will be aborted:
Note - Fixed in System Firmware 7.1.6.d or later.
The error is erroneous and can be ignored.
Type boot at the ok prompt to proceed.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
"ERROR: Last Trap: Watchdog
Reset".
6593801
When all platform identity checks fail, system
power on should be disabled. If enough of the
FRUs are corrupted, the system cannot
determine its identity, which makes certain
components nonoperational and could crash the
server.
Note - Fixed in System Firmware 7.1.3.d or later.
6594506
Domain ETM and LDC Deadlock When
Transmit Queue Full
For examples, see “Domain ETM and LDC
Deadlock When Transmit Queue Full (CR
6594506)” on page 108.
Note - Fixed in Solaris patch ID 125369-12 or
later.
See “Domain ETM and LDC Deadlock When
Transmit Queue Full (CR 6594506)” on page 108.
Appendix A
Fixed Issues
89
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6598381
In rare circumstances, the PCIe interface unit
(PIU) might issue a spurious error interrupt.
For examples, see “Spurious PIU Errors (CR
6598381)” on page 110.
Note - Fixed in System Firmware 7.1.6.d or later.
These events are harmless and can be ignored.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6611700
6601900
When the OpenBoot PROM is set to inputdevice=keyboard, you might see the
following warning message when the system
host is powered on or reset:
Note - Fixed in System Firmware 7.1.6.d or later.
Do not use USB keyboards. Instead, use a virtual
console by setting the input-device variable to
virtual-console.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
No keyboard support found
A U.S. keyboard will work properly.
International keyboards (French, German, and
so on) might behave as U.S. keyboards.
6602913
IPMI power off or power cycle operations might
fail.
Note - Fixed in System Firmware 7.1.6.d or later.
Repeat the IPMI power off, or power-cycle
operation, or use one of the other available
interfaces to perform this operation.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6604305
During system initialization, memory might not
be detected, and the following error is reported:
ERROR: MB/CMP0/BR3/CH0/D0 must be
populated.
Rarely, the probing of DIMMs fails due to ILOM
simultaneously updating DIMM information.
When the DIMM probing fails, the host either
boots with a reduced memory configuration, or
fails to boot. This situation is not likely to
happen when the service processor (SP) is reset,
because the DIMMs are probed before ILOM
starts dynamic fruid updates. This issue is
most likely to occur when the host is being
repeatedly powered on and off without resetting
the SP.
Note - Fixed in System Firmware 7.1.6.d or later.
Power off the host, reset the SP, and power on the
host.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6612687
Repeated attempts to show or set the serial port
properties of the host port might cause the
ILOM CLI to hang and become unresponsive.
Note - Fixed in System Firmware 7.0.9 or later.
Do not configure the host serial port properties
from the service processor. Instead, set the
properties from the Solaris OS.
If the ILOM CLI hangs, you must reset the system
by power cycling the AC power.
90
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6615884
6614576
The help message is incorrect in the ILOM BI.
The informational text displayed on the
Configuration Serial Port tab in the ILOM BI
refers to a DB-9 connector, but the message
should refer to the RJ-45 connector.
Note - Fixed in System Firmware 7.0.9 or later.
Be aware of this discrepancy.
6616693
When the information obtained by using IPMI, Note - Fixed in System Firmware 7.0.9 or later.
the information such as the "Product Part
Log in to ILOM and refer to the information such
Number" of the server is not displayed correctly. as /SYS.
6618773
A diagnostic routine that runs at startup (IBIST) Note - Fixed in System Firmware 7.1.0.g or later.
might disconnect the memory controller unit
Install Patch 127580-04 or later, and update the
(MCU), resulting in errors.
System Firmware to version 7.0.9 or later.
For an example of the errors, see “Diagnostic
Routine That Runs at Startup (IBIST) Might
Accidentally Disconnect the MCU (CR 6618773)”
on page 111.
6622444
In the mirroring configuration of the system
volume disk using the PRIMECLUSTER GDS,
when an error occurred while reading the boot
block of boot disk, the boot path does not
switch. At this time, the following message
appears and the process returns to the ok
prompt.
Boot load failed.
The file just loaded does not appear to
be executable.
{0} ok
6623454
Despite the change of SSH setting from "Disable" Note - Fixed in System Firmware 7.2.2.e or later.
to "Enable" by using the "SSH Server" tab of BUI, The SSH setting has been changed to "Enable."
it is displayed as "Disable."
Use the Refresh function of BUI.
6624658
Unless the system is stopped from the service
processor, the system will be automatically
powered on at the next AC power-on even if the
HOST_LAST_POWER_STATE in /SP/policy is
set to "enabled".
The same applies if the HOST_AUTO_POWER_ON
property is set to enabled but the system has
not been stopped from the service processor.
Note - Fixed in System Firmware 7.1.3.d or later.
To stop the system, use the command on the
service processor.
Moreover, when setting the
HOST_AUTO_POWER_ON property to "enabled",
also set the HOST_POWER_ON_DELAY property to
"enabled".
6624699
Despite the change of Role to
Administrator/Operator by using "Active
Directory" of BUI, Role is displayed as blank.
Note - Fixed in System Firmware 7.2.2.e or later.
Log in to ILOM and check the defaultrole
property of /SP/clients/activedirectory.
Note - Fixed in System Firmware 7.0.9 or later.
When the process returned to the ok prompt,
reexecute the boot command to start the OS.
Appendix A
Fixed Issues
91
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6643177
If an attempt is made to power on the system
with poweron ALOM CMT compatibility
commands, power-on may fail with the
following message displayed:
sc> poweron
Host poweron failed.
poweron error: Internal error
Note - Fixed in System Firmware 7.1.0.g or later.
None.
sc> poweron
Error reading keyswitch value
6676309
6667409
When using NTP services under Solaris OS, time Note - Fixed in System Firmware 7.1.3.d or later.
correction with NTP may fail, and a time delay Alternatively, if the firmware is not updated, add
may occur.
the appropriate one of the commands below to
the settings in the /etc/system file and restart
Solaris OS.
If the NTP correction mode is set to slew mode
• and the processor speed is 1.2 GHz:
set sys_tick_freq=1165379275
• and the processor speed is 1.4 GHz:
set sys_tick_freq=1415103392
6610861
6613564
The prompt and character sequence for
dropping to the u-boot state is inconsistent with
previous platforms.
When the service processor is booting, pressing
a key during the 5-second interval while the
prompt Hit any key to stop autoboot is
displayed causes the service processor boot
sequence to stop and a u-boot prompt is
displayed.
6656116
Note - Fixed in System Firmware 7.2.2.e or later.
If the DIMM module fails, the MCU will be
disconnected, and an error message might be
Identify and replace the faulty DIMM module.
output to the console.
For an example of the message, see “MCU Might
Be Disconnected in DIMM Module Failure (CR
6656116)” on page 111.
92
Note - Fixed in System Firmware 7.1.6.d or later.
Type the boot command to resume the service
processor boot sequence.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6654695
The following message is displayed when the
clear_fault_action property of the /SYS object is
set to true, but no processing is executed:
Message example:
Set clear_fault_action to true
Note - Fixed in System Firmware 7.1.3.d or later.
Clear the error by using the FRU name provided
by the show /SP/faultmgmt command.
The /SYS object clear_fault_action property has
been corrected in System Firmware 7.1.3.d or
later.
6768806
An attempt to read the properties of the power
supply unit (PSU) may be unsuccessful and
cause the ILOM session to terminate.
6784525
In a sixteen-disk capable server, the "Ready-toRemove LED" does not go on when hard disks
mounted in slots #8 to #15 are hot replaced.
Note - Fixed in System Firmware 7.2.2.e or later.
None.
It is, however, possible to check the PSU
properties with the showfru command of the
-> show -level all -o table /SYS/PS0 ALOM CMT compatibility shell.
Target
| Property
| Value
------------+---------------+----------Connection to XXX.XXX.XXX.XXX closed.
%
Note - Fixed in System Firmware 7.2.2.e or later.
Instead of using the "Ready-to-Remove LED," use
the execution result of the cfgadm -l command.
If the status becomes unconfigured, hot
replacement is enabled.
Confirmation example:
# cfgadm -l c1::dsk/c1t1d0
Ap_Id
Type Receptacle
Occupant
Condition
c1::dsk/c1t1d0 disk connected
unconfigured unknown
#
6772707
When the showenvironment command of the
ALOM CMT compatibility shell is executed in a
sixteen-disk capable server, even though the
hard disk is mounted in slot #8, "NOT
PRESENT" is output.
For examples, see “When the
showenvironment Command is Executed in a
Sixteen-Disk Capable Server, Even Though the
Hard Disk is Mounted in Slot #8, "NOT
PRESENT" is Output (CR 6772707)” on page 112.
Note - Fixed in System Firmware 7.2.2.e or later.
The status can be confirmed from the ok prompt
by using the probe-scsi-all command.
For examples, see “When the showenvironment
Command is Executed in a Sixteen-Disk Capable
Server, Even Though the Hard Disk is Mounted
in Slot #8, "NOT PRESENT" is Output (CR
6772707)” on page 112.
Appendix A
Fixed Issues
93
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6692478
Failures may occur in ILOM functions such as
user account management if a prohibited
character like "#", "+", or ":" is used for the first
character of an ILOM user account.
Note - Fixed in System Firmware 7.2.2.e or later.
None.
When the user account can be deleted, the ILOM
can be recovered by deleting the user account.
When the user can not be deleted, reset the ILOM
configuration to factory defaults to recover the
ILOM.
For the details about procedures and valid
characters for ILOM user accounts, see the
Integrated Lights Out Manager 2.0 User's Guide.
6781815
After the ILOM reset or the power cable removal
and insertion, when the server powered on,
Solaris OS startup at the ok prompt of OBP
(OpenBoot PROM) using the boot command
may fail.
Error output example:
{0} ok boot
ERROR: All device paths in bootdevice have failed. (*)
{0} ok
It cannot refer to the device paths that
configured in the OBP environmental variable
boot-device and fails to start Solaris OS.
Note - Fixed in System Firmware 7.2.2.e or later.
After the ILOM reset or the power cable removal
and insertion, when you power on the server,
check the OBP environmental variable. Especially,
in case the OBP environmental variable usenvramrc? has been set to true, it is necessary in
advance of starting the OS to see the ok prompt
and check that use-nvramrc? has been set to
true and then execute the boot command.
Confirmation example:
{0} ok printenv use-nvramrc?
use-nvramrc? = true
{0} ok
6782508
The /SP/powermgmt/policy property has
been disabled.
Note - Fixed in System Firmware 7.2.2.e or later.
To /SP/powermgmt/policy, the following
properties have become available.
- Performance
The system is allowed to use all the power that is
available.
- Elastic
The system power usage is adapted to the current
utilization level. For example, power up or down
just enough system components to keep relative
utilization at 70% at all times, even if workload
fluctuates.
This property is enabled only in the logical
domain (LDoms) environment.
In case you are not in the logical domain (LDoms)
environment, or in case that the logical domain
(LDoms) configuration is the factory-default, the
property setting is available but cannot utilize its
power consumption control function.
94
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6802433
For DC input power models, the INPUT limit
value included in the output from the
showpower -v command may differ between
/SYS/PS0 and /SYS/PS1. 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 114.
Note - Fixed in System Firmware 7.2.2.e or later.
None. Ignore this issue because it is only a display
error.
6801248
For DC input power models, the following event Note - Fixed in System Firmware 7.2.2.e or later.
log might be repeatedly collected when the
None. Ignore this event log.
power to the system is turned on:
Sample output from the showlogs command:
Chassis|minor:"Error getting status
DC volt for PS0"
Chassis|minor:"Error getting status
DC volt for PS1"
Chassis|minor:"Error getting status
DC volt for PS0"
Chassis|minor:"Error getting status
DC volt for PS0"
6819987
For DC input power models, the following event
log might be repeatedly collected:
Sample output from the showlogs command:
IPMI |minor : "ID = 20a : 03/11/2009
: 02:31:48 : Current :
/PS0/CUR_FAULT : State Asserted"
IPMI |minor : "ID = 20b : 03/11/2009
: 02:31:51 : Temperature :
/PS0/TEMP_FAULT : State Asserted"
IPMI |minor : "ID = 20c : 03/11/2009
: 02:31:54 : Current :
/PS0/CUR_FAULT : State Deasserted"
IPMI |minor : "ID = 20d : 03/11/2009
: 02:31:57 : Temperature :
/PS0/TEMP_FAULT : State Deasserted"
Note - Fixed in System Firmware 7.2.2.e or later.
None. If the Service Required, Overtemp, and
Power Supply Service Required LEDs on the
server are off, ignore the event log items. If one of
these LEDs is on, indicating that a power supply
problem or temperature-related problem has
occurred, correct the problem.
6821325
In the output from the prtdiag command,
warnings may be displayed for input voltage
sensors (V_IN_MAIN) on power supply units.
For examples, see “In the Output From the
prtdiag Command, Warnings May Be
Displayed (CR 6821325)” on page 115.
Note - Fixed in System Firmware 7.2.7.b or later.
None. Ignore this issue because it is only a display
error.
Appendix A
Fixed Issues
95
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6586305
Using the SP setdate command (ALOM
compatibility shell) after having configured nondefault logical domains can cause the date on
non-default domains to change.
Note - Fixed in System Firmware 7.2.2.e or later.
Use the setdate command to configure the date
on the SP before configuring and saving logical
domain configurations.
If you use setdate after non-default logical
domain configurations have been saved, each
non-default domain must be booted to Solaris
and the date corrected. (See date(1) or
ntpdate(1M).)
6733632
Note - Fixed in System Firmware 7.2.2.e or later.
When the ILOM "show -level all /SYS"
command is executed, information under
Use the show /SYS/MB/SP command.
/SYS/MB/SP is not displayed.
When "show -level all /SYS/MB" is
executed, information under /SYS/MB/SP is not
displayed either.
6757022
Resetting the service processor while the host is
powered on can cause the host to crash.
6654395
Note - Fixed in System Firmware 7.1.0.g or later.
If the LDoms Manager is active on a host
machine, do not reset the service processor while
the host machine is powered on. If the service
processor is reset while the system power is
active, the machine must be power-cycled before
the LDoms Manager can start properly.
6613209
When moving the SCC chip from one system to
another, if the value of /HOST/diag trigger
(or diag_trigger) has two values (such as
power-on-reset error-reset), the values
are restored incorrectly from the SCC chip to the
new system. The values will be restored without
a space separating them (for example,
power-on-reseterror-reset). This situation
will result in POST not being run when the host
is reset.
Note - Fixed in System Firmware 7.1.3.d or later.
When moving an SCC chip from one system to
another, verify that the values of
/HOST/diag trigger are correct. If the values
are not correct, set them to the desired value.
6639312
The /SYS/MB/CMPx components have a
fault_state property and a
clear_fault_action property. These
components should not have these properties
since they are not FRUs, and cannot be faulted
or have 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.
Note - Fixed in System Firmware 7.1.0.g or later.
Ignore the fault_state and
clear_fault_action properties of the
/SYS/MB/CMPx targets. Use the fault_state
and clear_fault_action property of
/SYS/MB.
96
Note - Fixed in System Firmware 7.2.2.e or later.
Do not reset the service processor while the
system is powered on. If you encounter this issue,
power cycle the server.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6694475
It is impossible to use options of the showfru
command on the ALOM CMT compatibility
shell. All information will be displayed
regardless of the option specified.
showfru [-g lines] [-s|-d] [FRU]
-g: Only the specified line
-s: Only static information
-d: Only dynamic information
Note - Fixed in System Firmware 7.1.6.d or later.
None.
6694693
ILOM allows only two privileges: Administrator Note - Fixed in System Firmware 7.2.2.e or later.
and Operator. Therefore, the following text
None.
about the ALOM CMT userperm command in
the manual is inappropriate.
If one of [c], [u], [a], and [r] is set, Administrator
authority will be in effect. If nothing is specified,
Operator authority will be in effect.
<Integrated Lights Out Manager 2.0 Supplement>
userperm [username] [c][u][a][r]
6738989
The SNMP tab of the ILOM Web interface does
not have an item for setting engineid.
Note - Fixed in System Firmware 7.2.2.e or later.
Use the "set /SP/services/snmp engineid=
(value)" command from the CLI to set
engineid.
6729474
The powercycle command of the ILOM
browser interface does not secure sufficient time
for normal power-off of the system and may fail
to complete powercycle.
Note - Fixed in System Firmware 7.2.2.e or later.
None.
Appendix A
Fixed Issues
97
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6731227
Two circumstances can cause a logical domain to
hang when reassigning I/O branches from the
primary domain (control domain) to a guest
domain (I/O domain):
Case 1 - If you remove an I/O branch from the
logical domain configuration of the primary
domain and then add the same I/O branch back
to the primary domain, upon reboot the system
might come back up without any I/O, the
system might hang in OpenBoot, or the entire
I/O branch and the associated I/O devices
might be absent from the primary domain.
For example, the following actions performed in
the sequence shown might lead to the primary
domain hanging in OpenBoot:
1. ldm rm-io pci@500 primary
(Remove pci@500 from the configuration)
2. ldm rm-io pci@600 primary
(Remove pci@600 from the configuration)
3. ldm add-io pci@500 primary
(Add pci@500 back to the configuration)
4. ldm add-config config_name
(Save new configuration to SP)
5. clean shutdown and power cycle
Case 2 - If the you assign I/O branches to guest
domains in any order except in numerical order,
one or more of the guest domains will be unable
to start.
For example, the following actions performed in
the sequence shown might lead to one or more
guest domains hanging when they are started:
1. ldm add-io pci@600 guestA
2. ldm add-io pci@500 guestB
3. ldm add-io pci@700 guestC
Note - Fixed in System Firmware 7.2.2.e or later.
Both situations can be avoided by following these
guidelines:
Case 1 - Do not remove an I/O branch from the
primary domain and then immediately add it
back to the primary domain.
Case 2 - Be certain to add the I/O branches to the
guest domains in numerical order.
Example #1: The primary domain is using
pci@400 (onboard disks/USB/DVD and slots
PCIe0 and PCIe1), and you want to assign
pci@500, pci@600, and pci@700 to three guests.
Do the following:
1. ldm add-io pci@500 guestB
2. ldm add-io pci@600 guestA
3. ldm add-io pci@700 guestC
Example #2: The primary domain is using
pci@500 (onboard 1Gb/sec and10Gb/sec
network, slots PCIE4, PCIE5, XAUI0, XAUI1), and
you want to assign pci@400, pci@600, and
pci@700 to three guests. Do the following:
1. ldm add-io pci@400 guestB
2. ldm add-io pci@600 guestA
3. ldm add-io pci@700 guestC
If you encounter this hang, you can recover by
booting the system with either a prior working
configuration or with the factory default
configuration.
The system can be booted to an earlier working
configuration or in the factory default
configuration by executing following sequence of
commands in the ALOM CLI on the service
processor (SP):
1. sc> bootmode config="name_of_config"
2. sc> poweron
3. sc> poweroff
The name_of_config is the working configuration
saved on the service processor. If no such
configurations exists on the service processor, use
"factory-default" as the name of the configuration.
Note - If the "factory-default" configuration is
used in the above procedure then you must
reconfigure all of the guest domains and the
primary domain.
98
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6730610
In certain circumstances you might encounter
these error messages when powering on
T5120/T5220 servers:
Chassis | major: Jul 27 16:40:17
ERROR: dt_allocprop: prop == NULL:
Not enough memory to expand MD for
new property fwd
Chassis | major: Jul 27 16:40:17
ERROR: dt_allocnode: Not enough
memory to expand MD for new node
mblock
Chassis | critical: Jul 27 16:41:55
FATAL: The Service Processor
software has taken a FATAL
configuration error,
Chassis | critical: the HOST Process
cannot be started.
Chassis | critical: Please examine
the logs to determine the reason for
failure and then
Chassis | critical: reset the
Service Processor
This error is encountered when there is a large
difference between the amount of memory on
the different CMP and memory modules. For
example, this could happen if the memory on
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.
Note - Fixed in System Firmware 7.2.2.e or later.
Case 1 - POST has determined that multiple FBDIMMS have failed on T5120/T5220 servers with
64 8-Gbyte FB-DIMMS
Recovery 1 - If POST takes a FB-DIMM offline,
you must replace it immediately. If replacing the
failed FB-DIMM is not immediately possible or
desired, you must disable the corresponding FBDIMMs on the other CMP/memory modules'
corresponding memory branches to guarantee a
contiguous memory configuration.
Type one of the following:
-> set /SYS/component
component_state=disabled
sc> disablecomponent asr-key
Type one of the following commands to display a
list of enabled and disabled devices:
-> show components
sc> showcomponent
For each FB-DIMM device that is disabled,
disable the corresponding FB-DIMM associated
with the other CMP/memory module units. For
example, if the following device was disabled:
/SYS/MB/MEM0/CMP0/BR0/CH0/D1
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 T5120/T5220 servers and have configured one
of the CMP/memory module pairs with
significantly more memory than the other
modules
Recovery 2 - Reallocate the FB-DIMMs across the
CMP/memory modules to keep the total number
and types of FB-DIMMs the same on each
CMP/memory module pair.
6731027
Under certain conditions, the system might not
power off when the Solaris OS is halted. The
system might appear unresponsive in this case
with no messages in at the system console or on
the SC console.
Note - Fixed in System Firmware 7.2.2.e or later.
Power off the system using one of the following
methods:
• The ILOM stop/SYS command
• The ALOM poweroff command
Appendix A
Fixed Issues
99
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6652046
POST error messages for some types of XAUI
test failures can be misleading. The POST error
messages can identify the correct port while
reporting the wrong slot number.
Note - Fixed in System Firmware 7.1.0.g or later.
XAUI port and slot numbers should match for the
SPARC Enterprise T5120 and T5220 servers. Use
the port number.
6656072
POST failure messages can specify the wrong
CPU.
Note - Fixed in System Firmware 7.1.0.g or later.
6743343
Test Alert generation (alert test transmission)
may not be possible, depending on the "Alert
Type" and "Event" under the alert rule settings.
Note - Fixed in System Firmware 7.2.2.e or later.
None.
6847308
In the backup of the ILOM settings, when the
value of the system identifier property (/SP
system_identifier) is its default value
(none), the value of the system description
property (/SP system_description) will be
stored in the backup file.
Example of erroneously stored data:
<entry>
<property>/SP/system_identifier
</property>
<value>SPARC-Enterprise-T5120,
ILOM v3.0.3.20.e, r46064</value>
</entry>
Note - Fixed in System Firmware 7.2.7.b or later.
None.
Delete the entry of "/SP system_identifier"
in the backup file.
6835860
For SPARC Enterprise T5220 Server, during the
power-on self-test (POST), the "ERROR:POST
timed out" message may appear and the
diagnostic process may terminate halfway.
For the example, see “During the Power-On SelfTest, the Diagnostic Process May Terminate
Halfway (CR 6835860)” on page 115.
Note - Fixed in System Firmware 7.2.7.b or later.
None.
Power on the host again and perform the poweron self-test (POST).
6823516
In the DNS client settings, the number of retries
(retries property) cannot be set to "5."
Note - Fixed in System Firmware 7.2.7.b or later.
None.
Set the integer between "0" and "4" to the number
of retries.
6823725
Once you set the searchpath property of the
DNS client function, you cannot change it back
to the default value (none).
Note - Fixed in System Firmware 7.2.7.b or later.
None.
100
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6853843
On the DC input power model of SPARC
Enterprise T5120 Server, when you execute the
prtdiag command of Solaris OS, the
"Environmental Status" and some part of
the "FRU Status" information is not displayed.
For the incomplete data output example, see
“On the DC Input Power Model, the
"Environmental Status" and Some Part of the
"FRU Status" Information Is Not Displayed (CR
6853843)” on page 116.
Note - Fixed in System Firmware 7.2.7.b or later.
None.
From ILOM, check the component information
and the status of fan, temperature, power sensor
and so on.
6856163
If the service processor is initialized with the
LAN cable disconnected from the ILOM
network port, the ILOM firmware serial console
window displays an error message indicating a
failure to start an ILOM internal process. As a
result, ILOM fails to start.
For details, see “When the Service Processor Is
Initialized, ILOM May Fails to Start With an
Error Message Displayed (CR 6856163)” on
page 117.
Note - Fixed in System Firmware 7.2.7.b or later.
Initialize the service processor with the LAN
cable connected to the ILOM network port.
As long as the network port is linked up, the
service processor can be initialized, even without
ILOM network settings.
For procedures to restore normal system
operation, see “When the Service Processor Is
Initialized, ILOM May Fails to Start With an Error
Message Displayed (CR 6856163)” on page 117.
6857271
During SCC module replacement, part of the
data kept on the motherboard is inadvertently
overwritten with new SCC module data. This
results in a connection failure to the ILOM
network.
For details, see “After the SCC Module
Replacement, a Connection to the ILOM
Network May Fail (CR 6857271)” on page 118
Note - Fixed in System Firmware 7.2.7.b or later.
If only the SCC module fails, replace the SCC
module together with the motherboard.
After replacing these components, restore the
backed up contents.
6854379
After the replacement of motherboard, the
values for properties stored in the /HOST/diag
directory may not be carried over, even though
system configuration card (SCC module) is
moved to the new motherboard.
Note - Fixed in System Firmware 7.2.7.b or later.
None.
Before replacing the motherboard, back up the
ILOM settings. After the replacement, restore the
backed up settings.
6816507
After mounted the 10GbE XAUI card, when you
insert the power cable, the component
information of the 10GbE XAUI card does not
appear on ILOM. ILOM recognized the 10GbE
XAUI card.
Note - Fixed in System Firmware 7.2.7.b or later.
None.
To confirm the component information of the
10GbE XAUI card from ILOM, check it after you
power on the host.
6722602
6663105
6913105
6908024
When connected to OS console via ILOM, input Note - Fixed in System Firmware 7.2.8 or later.
or display to console may not be enabled. And at After the system stop, disconnect the power cord
this time, output from OS to console may fail.
and then reconnect the power cord.
Appendix A
Fixed Issues
101
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6919764
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" may
appear in the ILOM event log and the Service
Required LED may turn on.
Solaris OS completes the startup normally, and
the fibre channel card is normally recognized on
Solaris OS.
For details, see “On a System Mounted With the
Fujitsu 4Gbps Fibre Channel Card, the Service
Required LED May Turn On After the System
Power-on (CR 6919764)” on page 119.
Note - Fixed in System Firmware 7.2.8 or later.
After you insert the power cord, or after the
ILOM reset complete, wait for about 180 seconds
and then power on the system.
6942238
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.
For details, see “Slot Number of Link Card
Connected to PCI Box Is Falsely Displayed (CR
6942238)” on page 120.
Note - Fixed in System Firmware 7.2.10 or later.
None.
This can be safely ignored. To check the fibre
channel card mount, use IO Devices of the
prtdiag command of Solaris OS.
For details, see “Slot Number of Link Card
Connected to PCI Box Is Falsely Displayed (CR
6942238)” on page 120.
6939213
After updated to System Firmware 7.2.8, when
you remove/insert the power cord or reset
ILOM, a message that indicates the presence or
absence of a component such as DIMM, PSU, or
FAN (Device Present / Device Absent)
may be displayed in the event log.
For details, see “After Updated to System
Firmware 7.2.8, a Message That Indicates the
Presence or Absence of a Component May Be
Displayed in the Event Log (CR 6939213)” on
page 123.
Note - Fixed in System Firmware 7.2.10 or later.
None.
These messages are not the error messages. The
message is displayed at the point when ILOM
restarted, in order to reload the component
information, and can be safely ignored.
102
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6902381
When you powered on the server, all LEDs or all
LEDs on the right side on the front panel may
light up. When using System Firmware 7.2.2.e or
later, the ILOM status check command (the
showenvironment command) also displays the
status of relevant LED being ON; however, this
event itself is an issue absolutely limited to the
LED display and does not have an effect on the
system.
Note - Fixed in System Firmware 7.2.10 or later.
None.
When this event occurred, perform the ILOM
reset operation. If not recovered, shut down the
system and then remove and insert the power
cord.
ILOM reset operation example:
Log in to ILOM and execute the following
command.
[In case of ILOM command mode]
-> reset /SP
Are you sure you want to reset /SP
(y/n)? y
[In case of ALOM CMT compatible shell]
sc> resetsc
Are you sure you want to reset the
SC [y/n]? y
6931546
The following event log might be collected when
the power to the system is turned on.
Event log example:
624
Fri Feb 26 03:33:12 2010 Chassis
Log
major
Feb 26 03:33:12 ERROR: TPM
protocol error occurred
Note - Fixed in System Firmware 7.2.10 or later.
When this event occurs on servers with the
system firmware 7.2.10 or later, it is recovered by
the automatic system power-off and -on executed
during POST that runs before Solaris OS starts
during the system startup.
At this time, an ILOM event log shown below
will be collected.
Chassis | major: TPM operation
initiating a power-cycle
Chassis | critical: Host has been
powered off
Chassis | major: Host has been
powered on
6948680
When you change the system diagnostics
settings (/HOST/diag) from "Remote Control"->
"Diagnostics" tab in the ILOM Web interface, the
value of "Trigger" fails to be set with a pop-up
message "Error:Invalid property value," if the
following value is singly selected for the
"Trigger".
• Power On
• User Reset
Note - Fixed in System Firmware 7.2.10 or later.
None.
Use the set /HOST/diag trigger= (value)
command from the ILOM CLI interface.
Appendix A
Fixed Issues
103
TABLE A-3
Fixed Firmware, ILOM, POST, and SP Issues (Continued)
CR
Description
Workaround
6627396
If you keep on continuously executing the
command in the service processor that you
logged in, the return of command slows down.
Or errors might occur.
Note - Fixed in System Firmware 7.2.7.b or later.
If ILOM has been used at least once, log out from
ILOM.
When problems arise, AC power-cycle the
system.
6947945
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.
For details, see “Fujitsu 4Gbps Fibre Channel
Card Is Falsely Recognized as F20 Card (CR
6947945)” on page 124.
Note - Fixed in System Firmware 7.2.10 or later.
None.
This can be safely ignored. To check the fibre
channel card mount, use IO Devices of the
prtdiag command of Solaris OS.
For details, see “Fujitsu 4Gbps Fibre Channel
Card Is Falsely Recognized as F20 Card (CR
6947945)” on page 124.
6942129
When you mounted one or two units of PSU of a
certain version or later on the T5220 server, the
showpower command execution result shows
the OUTPUT Power (W) and OUTPUT Current
(A) values which are larger than the respective
INPUT values. For details, see “OUTPUT Power
and OUTPUT Current May Be Incorrectly
Displayed on the T5220 Server (CR 6942129)” on
page 125.
Note - Fixed in System Firmware 7.2.10 or later.
None. System Firmware's way of referring to the
data of PSU of a certain version or later was
wrong. PSU itself has no problem, and the
displayed data can be safely ignored.
6948710
With System Firmware 7.2.7.b or later, messages
referring to hot insertions/removals of devices
(including a nonexistent device) may be
displayed intermittently during the system
startup and the system running.
Message example of a nonexistent device:
Chassis | major: Hot insertion of
/SYS/MB/RISER1/XAUI1
Chassis | major: Hot removal of
/SYS/MB/RISER1/XAUI1
Message example of an existent device:
Chassis | major: Hot removal of
/SYS/MB/CMP0/BR1/CH0/D0
Chassis | major: Hot insertion of
/SYS/MB/CMP0/BR1/CH0/D0
Note - Fixed in System Firmware 7.2.10.a or
later.
None.
ILOM firmware's way of referring to the sensor is
wrong. This has no impact on the system. If no
faults are detected by the show faulty
command, ignore the output messages.
104
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
SP Serial Line Terminal Server break Command
Does Not Work (CR 6577528)
This issue is resolved by updating the system firmware to 7.1.6.d or later.
If you use Telnet to connect to the SP serial line with a terminal server (such as the
Cisco ASM series) and try to send a break to the Solaris host, the break command
does not work and is ignored by the SP. Use the break command from the SP CLI to
send a break to the Solaris host.
The following is sample output of sending a break to the Solaris host from the
ALOM CMT compatibility CLI:
1. Log into the host with the console command.
sc> console
2. Enter #. to return to the host prompt.
sc> #.
Solaris-host-prompt>
3. Enter #. to escape to the SP ALOM CMT compatibility CLI. The escape
sequence is not echoed.
Solaris-host-prompt> #.
sc>
4. Enter the break command.
sc> break -c -y
5. Enter #. to return to the SP ALOM CMT compatibility CLI.
sc> #.
c)ontinue, s)ync, r)eboot, h)alt?
The following is sample output of sending a break to the Solaris host from the SP
ILOM CLI:
1. Log into the host with the ILOM console command.
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type #.
Solaris-host-prompt>
Appendix A
Fixed Issues
105
2. Enter #. to escape to the SP ILOM CLI. The escape sequence is not echoed.
Solaris-host-prompt> #.
->
3. Enter the break command as follows.
-> set /HOST send_break_action=break
->
Log back into the Solaris host with the console command.
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type #.
c)ontinue, s)ync, r)eboot, h)alt?
Refer to the Integrated Lights Out Manager 2.0 User’s Guide and the Integrated Lights
Out Management (ILOM) Supplement for SPARC Enterprise T5120 and T5220 Servers for
details on how to use the break command from the SP CLIs.
The showfaults Command Shows the
Motherboard as Faulty Instead of the DIMM (CR
6582853)
This issue is resolved by updating the system firmware to 7.1.6.d or later.
In a system with DIMMs or PCIe adapters that have been faulted by PSH (Predictive
Self-Healing) diagnosis on the host, the ALOM showfaults command displays the
faulty FRU as the motherboard (/SYS/MB) instead of the DIMM or PCIe adapter.
This problem will occur for the following PSH Message-IDs (MSGID):
106
■
SUN4V-8000-E2
■
SUN4V-8000-D
■
SUN4-8000-4P
■
SUN4-8000-A2
■
SUN4-8000-75
■
SUN4-8000-9J
■
SUN4-8000-D4
■
PCIEX-8000-0A
■
PCIEX-8000-DJ
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
■
PCIEX-8000-HS
The following example from the ALOM CMT compatibility CLI illustrates the
problem. In this example, the faulty FRU displayed is the motherboard (/SYS/MB)
when the actual faulty component is a memory DIMM.
sc> showfaults -v
Last POST Run: Jul. 13 18:32:11 2007
Post Status: Passed all devices
ID Time
FRU
Class
Fault
0 Jul 13 19:31:34
/SYS/MB
Host detected fault, MSGID:
SUN4V-8000-DX UUID: 7b471945-ceef-eea0-c3ad-85ca140be5b2
In addition, there is a problem with the output displayed by the show
/SYS/faultmgmt command (ILOM CLI). The fault_state property of
components, and the faulted components listed under the Fault Management tab in
the ILOM BI are incorrect for the PSH Message-IDs listed above. Also, the FB-DIMM
fault indicator will not operate, and the FRUID for the motherboard will have a fault
recorded.
Workaround: Use the Fault Management utilities on the host to find the location of
the faulty DIMM(s) or PCIe adapters. Instructions for using these utilities for these
faults can be found in the Predictive Self-Healing Knowledge Articles located at:
http://www.sun.com/msg/MSGID
where MSGID is one of the PSH Message IDs listed in the bulleted list in this section
and displayed by the ALOM showfaults command.
For faulty DIMMs, refer to the DIMM label on the air duct or system cover to verify
the DIMM location.
Once the faulty DIMM is replaced and the PSH fault has been cleared, the entry in
showfaults will be deleted, and the fault recorded in the motherboard FRUID will
be cleared.
The uadmin 2 0 and reboot Commands Read
Old Bootmode Settings (CR 6585340)
This issue is resolved by updating the system firmware to 7.1.6.d or later.
You can change LDoms variables in the control domain in one of three ways, with
the OpenBoot setenv command in the control domain, with the Solaris eeprom
command in the control domain, or using ILOM bootmode bootscript option.
Appendix A
Fixed Issues
107
Changes made with the setenv and eeprom commands take effect immediately.
Changes made with the bootmode command are supposed to take effect on the next
reset, no matter what kind of reset it is.
Changes made in any of these three ways are supposed to stay in effect until the next
change. That is, it doesn't matter how the value of an LDoms variable is changed.
Once changed, the value is supposed to stay in effect until it is changed again.
However, due to this issue, changes made with the bootmode command will
become effective only after a power-on reset and will, on every reset (other than a
power-on reset) that follows, override any intervening change made with the
setenv or eeprom commands. That is, the changes made by the bootmode
command require a power-on reset to be effective. Changes made with the setenv
or eeprom commands will only persist until the next reset, at which point the
variable will revert to the value set by the last bootmode command. This persistence
of the bootmode setting will persist until the machine is power-cycled. Upon power
cycling, the prior bootmode setting will not take effect. Any subsequent change
made by the setenv or eeprom command will now persist over resets, at least until
the next bootmode command followed by a power cycle.
Workaround: Restart the control domain with a power-on reset right after the
bootmode command is executed, and restart again after the control domain boots to
either OpenBoot or Solaris. The first power-on reset will make the bootmode
command effective and the second power-on reset will workaround the persistence
issue.
The control domain can be reset using power-on reset with the ALOM CMT
compatibility CLI powercycle command. If the control domain is booted to the
Solaris OS, remember to properly shut down the OS before executing the
powercycle command.
Domain ETM and LDC Deadlock When Transmit
Queue Full (CR 6594506)
This issue is resolved with Solaris patch ID 125369-12 or later.
After certain hardware error events, it is possible that PSH events are no longer
transported between the Service Processor (SP) and the domain. The scenarios
subject to this CR:
108
■
In a non-LDoms environment, an unrecoverable error in the Solaris domain
■
In an LDoms environment, an unrecoverable error in the control domain
■
In either an LDoms or non-LDoms environment, a fatal error in the system (a fatal
error resets the system at the HW level)
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Note – In an LDoms environment, unrecoverable errors in a non-control LDoms
guest domain are not subject to this CR.
For example, an unrecoverable error in the control domain causes Solaris to panic.
Messages similar to the following are reported to the control domain console:
SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, VER: 1, SEVERITY: Major
EVENT-TIME: 0x46c61864.0x318184c6 (0x1dfeda2137e)
PLATFORM: SUNW,SPARC-Enterprise-T5220, CSN: -, HOSTNAME: wgs48-100
SOURCE: SunOS, REV: 5.10 Generic_Patch
DESC: Errors have been detected that require a reboot to ensure system
integrity. See http://www.sun.com/msg/SUNOS-8000-0G for more information.
AUTO-RESPONSE: Solaris will attempt to save and diagnose the error telemetry
IMPACT: The system will sync files, save a crash dump if needed, and reboot
REC-ACTION: Save the error summary below in case telemetry cannot be saved
Or, an unrecoverable error causes the Hypervisor to abort and messages similar to
the following are reported to the SP console when logged into the ALOM CMT
compatibility CLI console:
Aug 17 22:09:09 ERROR: HV Abort: <Unknown?> (228d74) - PowerDown
After the control domain recovers, there is a diagnosis performed. Messages to the
console indicate the cause of the unrecoverable error. For example:
SUNW-MSG-ID:SUN4V-8000-UQ, TYPE:Fault, VER:1, SEVERITY:Critical
EVENT-TIME: Fri Aug 17 18:00:57 EDT 2007
PLATFORM: SUNW,SPARC-Enterprise-T5220, CSN: -, HOSTNAME: wgs48-100
SOURCE: cpumem-diagnosis, REV: 1.6
EVENT-ID: a8b0eb18-6449-c0a7-cc0f-e230a1d27243
DESC: The number of level 2 cache uncorrectable data errors has exceeded
acceptable levels. Refer to http://sun.com/msg/SUN4V-8000-UQ for more
information.
AUTO-RESPONSE: No automated response.
IMPACT: System performance is likely to be affected.
REC-ACTION: Schedule a repair procedure to replace the affected resource,
the identity of which can be determined using fmdump -v -u <EVENT_ID>.
At this point, CR 6594506 might have been encountered. This will prevent future
PSH events (for example, new HW errors, correctable or uncorrectable) from being
transported into the domain and properly diagnosed.
Workaround: After the domain recovers and the diagnosis message is printed to the
Solaris console, reset the service processor:
Appendix A
Fixed Issues
109
[In case of ILOM command mode]
-> reset /SP
Are you sure you want to reset /SP (y/n)? y
[In case of ALOM CMT compatible shell]
sc> resetsc
Are you sure you want to reset the SC [y/n]? y
Once the SP is restarted and you are able to login as the admin (which means all
daemons are ready), execute the following in the Solaris control domain to unload
and load the etm.:
# fmadm unload etm
# fmadm load /usr/platform/sun4v/lib/fm/fmd/plugins/etm.so
Spurious PIU Errors (CR 6598381)
This issue is resolved by updating the system firmware to 7.1.6.d or later.
In rare circumstances, the PIU (PCIe interface unit) might issue a spurious error
interrupt.
The following is an example of the event reported after diagnostics:
SUNW-MSG-ID: FMD-8000-0W, TYPE: Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Mon Aug 27 10:07:33 EDT 2007
PLATFORM: SUNW,SPARC-Enterprise-T5220, CSN: -, HOSTNAME: xxxxxxx
SOURCE: fmd-self-diagnosis, REV: 1.0
EVENT-ID: dd9a4415-9be4-cb55-d061-8804b8009d3c
The following is an example of the event reported by the fmdump command:
# fmdump -eV -u dd9a4415-9be4-cb55-d061-8804b8009d3c
TIME
CLASS
Aug 27 2007 10:06:15.496599680 ereport.fm.ferg.invalid
nvlist version: 0
class = ereport.fm.ferg.invalid
ena = 0xd4e233fe480002
info = DMU Core and Block Error Status(0): No bits set
raw-data = 0x2 0x1a62441a01d844 0x30000000000005 0x4b63c07df9ff
0x3e002421030607 0x
110
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
3e 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
__ttl = 0x0
__tod = 0x46d2da57 0x1d998280
These events are harmless and can be ignored.
Diagnostic Routine That Runs at Startup (IBIST)
Might Accidentally Disconnect the MCU (CR
6618773)
This issue is resolved by updating the system firmware to 7.1.0.g or later.
In some cases, the MCU is disconnected from corresponding DIMM modules and
CPU cores, and the following messages are reported to the console.
For example:
Chassis | major: Host has been powered on
Chassis | major: Dec 19 08:45:11 ERROR: MB/CMP0/MCU2 Failed IBIST,
disabled
Fault | critical: SP detected fault at time Wed Dec 19 08:45:12
2007. /SYS/MB/CMP0/MCU2 Forced fail (IBIST)
Chassis | major: Dec 19 08:45:13 ERROR: MB/CMP0/MCU3 unused because
MB/CMP0/MCU2 is not configured
Chassis | major: Dec 19 08:45:13 ERROR: MB/CMP0/L2_BANK4,
MB/CMP0/L2_BANK5 unused because MB/CMP0/MCU2 is not configured
Chassis | major: Dec 19 08:45:13 ERROR: MB/CMP0/L2_BANK6,
MB/CMP0/L2_BANK7 unused because MB/CMP0/MCU3 is not configured
Chassis | major: Dec 19 08:45:13 ERROR: Degraded configuration:
system operating at reduced capacity
Chassis | major: Dec 19 08:45:13 ERROR: System DRAM Available:
008192 MB
Chassis | major: Dec 19 08:45:13 ERROR: Only 4 cores, up to 32 cpus
are configured because some L2_BANKS are unusable
Workaround: Install Patch 127580-04 or later, and update the System Firmware to
version 7.0.9 or later.
MCU Might Be Disconnected in DIMM Module
Failure (CR 6656116)
This issue is resolved by updating the system firmware to 7.2.2.e or later.
Appendix A
Fixed Issues
111
If the DIMM module fails, the MCU will be disconnected, and the following message
might be output to the console.
Message Example:
Jun 04 06:11:22: Chassis |major
: "Jun 4 06:11:22 ERROR: MCU2
initialization failed: DRAM init, disabled"
Jun 04 06:11:23: Fault
|critical: "SP detected fault at time Wed
Jun 4 06:11:23 2008. /SYS/MB/CMP0/MCU2 Forced fail (DRAM init)"
Jun 04 06:11:24: Chassis |major
: "Jun 4 06:11:24 ERROR:
MB/CMP0/MCU3 unused because MB/CMP0/MCU2 is not configured"
Jun 04 06:11:24: Chassis |major
: "Jun 4 06:11:24 ERROR:
MB/CMP0/L2_BANK4, MB/CMP0/L2_BANK5 unused because MB/CMP0/MCU2 is
not configured"
Jun 04 06:11:24: Chassis |major
: "Jun 4 06:11:24 ERROR:
MB/CMP0/L2_BANK6, MB/CMP0/L2_BANK7 unused because MB/CMP0/MCU3 is
not configured"
Jun 04 06:11:24: Chassis |major : "Jun 4 06:11:24 ERROR: Degraded
configuration: system operating at reduced capacity"
Jun 04 06:11:24: Chassis |major
: "Jun 4 06:11:24 ERROR: System
DRAM Available: 002048 MB"
showfaults command 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.
When the showenvironment Command is
Executed in a Sixteen-Disk Capable Server, Even
Though the Hard Disk is Mounted in Slot #8,
"NOT PRESENT" is Output (CR 6772707)
This issue is resolved by updating the system firmware to 7.2.2.e or later.
When the showenvironment command of ALOM CMT compatible shell is
executed in a sixteen-disk capable server, even though the hard disk is mounted in
slot #8, "NOT PRESENT" is output.
112
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
For example:
sc> showenvironment
:
(Omitted)
:
----------------------------------------------------------------System Disks:
----------------------------------------------------------------Disk
Status
Service
OK2RM
----------------------------------------------------------------/SYS/HDD0
OK
OFF
OFF
/SYS/HDD1
OK
OFF
OFF
/SYS/HDD2
OK
OFF
OFF
/SYS/HDD3
OK
OFF
OFF
/SYS/HDD4
OK
OFF
OFF
/SYS/HDD5
OK
OFF
OFF
/SYS/HDD6
OK
OFF
OFF
/SYS/HDD7
OK
OFF
OFF
/SYS/HDD8
NOT PRESENT
OFF
OFF
/SYS/HDD9
OK
OFF
OFF
/SYS/HDD10 OK
OFF
OFF
/SYS/HDD11 OK
OFF
OFF
/SYS/HDD12 OK
OFF
OFF
/SYS/HDD13 OK
OFF
OFF
/SYS/HDD14 OK
OFF
OFF
/SYS/HDD15 OK
OFF
OFF
:
(Omitted)
:
sc>
Workaround: The status can be confirmed from the ok prompt by using the probescsi-all command.
For example:
{0} ok probe-scsi-all
/pci@0/pci@0/pci@2/scsi@0
:
(Omitted)
:
Target 8
Unit 0 Disk
SEAGATE ST914602SSUN146G0603
146 GB
SASAddress 5000c5000b36a225 PhyNum 8
:
286739329 Blocks,
Appendix A
Fixed Issues
113
(Omitted)
:
{0}
For DC Input Power Models, the Output From the
showpower -v Command May Differ Between
/SYS/PS0 And /SYS/PS1 (CR 6802433)
This issue is resolved by updating the system firmware to 7.2.2.e or later.
For DC input power models, the INPUT limit value included in the output from the
showpower -v command may differ between /SYS/PS0 and /SYS/PS1. The
/SYS/PS1 value is correct.
Example of showpower -v command execution:
sc> showpower -v
----------------------------------------------------------------Power Supplies:
----------------------------------------------------------------INPUT
OUTPUT
Power
Power
Supply
Status
(W)
(W)
----------------------------------------------------------------/SYS/PS0
OK
172.8
123.8
/SYS/PS1
OK
153.6
133.3
----------------------------------------------------------------Total Power
326.4
----------------------------------------------------------------INPUT
INPUT
INPUT
OUTPUT
OUTPUT
OUTPUT
Volt
Current limit
Volt
Current
limit
Supply
(V)
(A)
(A)
(V)
(A)
(A)
----------------------------------------------------------------/SYS/PS0
-48.0
3.60
37.20
11.9
10.40
99.20
/SYS/PS1
-48.0
3.20
8.00(*) 11.9
11.20
99.20
sc>
(*) This is incorrect. The /SYS/PS0 value is correct.
Workaround: None. Ignore this issue because it is only a display error.
114
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
In the Output From the prtdiag Command,
Warnings May Be Displayed (CR 6821325)
This issue is resolved by updating the system firmware to 7.2.7.b or later.
In the output from the prtdiag command, warnings may be displayed for input
voltage sensors(V_IN_MAIN) on power supply units.
Voltage sensors:
-----------------------------------------------------------Location
Sensor
Status
-----------------------------------------------------------SYS/MB/CMP0/MR0
V_VMEM
ok
SYS/MB/CMP0/MR0
V_+1V5_VDD
ok
SYS/MB/CMP1/MR1
V_VMEM
ok
SYS/MB/CMP1/MR1
V_+1V5_VDD
ok
SYS/MB
V_+3V3_STBY
ok
SYS/MB
V_+3V3_MAIN
ok
SYS/MB
V_+12V0_MAIN
ok
SYS/MB
V_VDDIO
ok
SYS/MB
V_VCOREL
ok
SYS/MB
V_VCORER
ok
SYS/MB
V_+1V5_IO
ok
SYS/MB
V_VMEML
ok
SYS/MB
V_VMEMR
ok
SYS/MB
V_VBAT
ok
SYS/PS0
V_IN_MAIN
warning (-48volts)
SYS/PS0
V_OUT_MAIN
ok
SYS/PS1
V_IN_MAIN
warning (-48volts)
SYS/PS1
V_OUT_MAIN
ok
Workaround: None. Ignore this issue because it is only a display error.
During the Power-On Self-Test, the Diagnostic
Process May Terminate Halfway (CR 6835860)
This issue is resolved by updating the system firmware to 7.2.7.b or later.
For SPARC Enterprise T5220 Server, during the power-on self-test (POST), the
"ERROR:POST timed out" message may appear and the diagnostic process may
terminate halfway.
Appendix A
Fixed Issues
115
Example:
sc> poweron -c
Enter #. to return to ALOM.
Chassis | major: Host has been powered on
0:0:0>
0:0:0>SPARC-Enterprise[TM] T5120/T5220 POST
4.30.2.build_06***PROTOTYPE BUILD***
2009/03/19 08:25
/export/delivery/delivery/4.30/4.30.2.build_06/post4.30.x/Niagar
a/huron/integrated (root)
0:0:0>Copyright 2009 Sun Microsystems, Inc. All rights reserved
0:0:0>POST enabling CMP 0 threads: ffffffff.ffffffff
0:0:0>VBSC mode is: 00000000.00000001
0:0:0>VBSC level is: 00000000.00000001
0:0:0>VBSC selecting Normal mode, MAX Testing.
0:0:0>VBSC setting verbosity level 2
0:0:0>Basic Memory Tests....Done
0:0:0>Test Memory....Done
0:0:0>Setup POST Mailbox ....Done
0:0:0>Master CPU Tests Basic....Done
0:0:0>Init MMU.....
0:0:0>NCU Setup and PIU link train....Done
0:0:0>L2 Tests....Done
0:0:0>Extended CPU Tests....-Chassis | major: Apr 21 10:51:09
ERROR: POST timed out. Not all system components tested.
Chassis | major: Host is running
Workaround: None. Power on the host again and perform the power-on self-test
(POST).
On the DC Input Power Model, the
"Environmental Status" and Some Part of the
"FRU Status" Information Is Not Displayed (CR
6853843)
This issue is resolved by updating the system firmware to 7.2.7.b or later.
On the DC input power model of SPARC Enterprise T5120 Server, when you execute
the prtdiag command of Solaris OS, the "Environmental Status" and some part of
the "FRU Status" information is not displayed.
116
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Incomplete Data Output Example:
============================ Environmental Status ============================
<-- No data output.
============================ FRU Status ============================
Location
Name
Status
-----------------------------------------------------SYS
MB
enabled
SYS
HDD0
enabled
SYS
HDD1
enabled
<-- Part of data is not on display.
Workaround: None. From ILOM, check the component information and the status of
fan, temperature, power sensor and so on.
When the Service Processor Is Initialized, ILOM
May Fails to Start With an Error Message
Displayed (CR 6856163)
This issue is resolved by updating the system firmware to 7.2.7.b or later.
If the service processor is initialized (*1) with the LAN cable disconnected from the
ILOM network port, the ILOM firmware serial console window displays an error
message (*2) indicating a failure to start an ILOM internal process. As a result, ILOM
fails to start.
(*1) Service processor initialization has the following meaning:
■
For ILOM
-> set /SP reset_to_defaults=all or factory
-> reset /SP
■
For ALOM CMT compatible shell
sc> setdefaults
sc> resetsc
Appendix A
Fixed Issues
117
Example of failure:
SUNSP-BEL07482AU login: root
Password:
Waiting for daemons to initialize...
Timed out waiting for daemons to start
sccd daemon has shutdown
<-- (*2)
<-- (*2)
Integrated Lights Out Manager
Version 3.0.3.20.e
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Warning: password is set to factory default.
->
Workaround: Initialize the service processor with the LAN cable connected to the
ILOM network port.
As long as the network port is linked up, the service processor can be initialized,
even without ILOM network settings.
If this problem occurs, restore normal system operation by using the following
procedure:
1. Disconnect the power cable.
2. Connect the LAN cable to the ILOM network port.
Verify that the ILOM network port is linked up.
3. Connect the power cable.
After the SCC Module Replacement, a Connection
to the ILOM Network May Fail (CR 6857271)
This issue is resolved by updating the system firmware to 7.2.7.b or later.
During SCC module replacement, part (*1) of the data kept on the motherboard is
inadvertently overwritten with new SCC module data (*2). This results in a
connection failure to the ILOM network.
118
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
(*1) SCC module data including ILOM user data, network setting data, and
diagnostics data. For details, see the ILOM Supplement for each server.
(*2) The data is initialized at this point in time, so the data has no set values.
Also, the following type of log is output (*) to the ILOM serial console window at
the occurrence of the failure. sccd fails to start at ILOM startup:
Example of output to ILOM serial console at failure occurrence:
SUNSP-BEL07482AU login: root
Password:
Waiting for daemons to initialize...
Timed out waiting for daemons to start
sccd daemon has shutdown
<-- (*)
<-- (*)
Integrated Lights Out Manager
Version 3.0.3.20.e
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Warning: password is set to factory default.
->
Be sure to back up the service processor settings before replacing the SCC module.
Workaround: If only the SCC module fails, replace the SCC module together with
the motherboard.
After replacing these components, restore the backed up contents.
On a System Mounted With the Fujitsu 4Gbps
Fibre Channel Card, the Service Required LED
May Turn On After the System Power-on (CR
6919764)
This issue is resolved by updating the system firmware to 7.2.8 or later.
Appendix A
Fixed Issues
119
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" may appear in the ILOM event log and the Service Required LED may
turn on.
Solaris OS completes the startup normally, and the fibre channel card is normally
recognized on Solaris OS.
The show faulty command output example:
-> show faulty
Target
| Property
| Value
--------------------+------------------------+-------------------------------/SP/faultmgmt/0
| fru
| /SYS
/SP/faultmgmt/0/
| timestamp
| Apr 06 09:41:17
faults/0
|
|
/SP/faultmgmt/0/
| sp_detected_fault
| /SYS/MB/RISER0/PCIE3/F20CARD
faults/0
|
| prom is unreadable or corrupted
->
The ILOM event log example:
15
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.
Workaround:
After you insert the power cord, or after the ILOM reset complete, wait for about 180
seconds and then power on the system.
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.
Shown below is an event example in time of failure.
120
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Configuration:
PCIE#0: void
PCIE#1: void
PCIE#2: void
PCIE#3: void
PCIE#4: void
PCIE#5: Link Card
The ILOM CLI interface output example:
/SYS/MB/RISER0/PCIE3/LINK
Properties:
type = Link Card
fru_description = Copper Link Card
fru_manufacturer = Celestica
fru_version = 02_51
fru_part_number = 5017041
fru_serial_number = XP00DD
fault_state = OK
connection = none
clear_fault_action = (none)
LEDs and FRU Status in the prtdiag -v command output:
# prtdiag -v
...
LEDs:
-----------------------------------------------------Location
LED
State
-----------------------------------------------------...
SYS/MB/RISER0/PCIE3/LINK
DATA
off
SYS/MB/RISER0/PCIE3/LINK
MGMT
off
...
=========================== FRU Status ===========================
Location
Name
Status
-----------------------------------------------------...
SYS/MB/RISER0/PCIE3
LINK
enabled
...
Workaround:
None. This can be safely ignored. To check the link card mount, use IO Devices of
the prtdiag command of Solaris OS.
Appendix A
Fixed Issues
121
The prtdiag command execution result:
# prtdiag
...
=========================== IO Devices ===========================
Slot +
Bus
Name +
Model
Status
Type Path
----------------------------------------------------------------...
PCIE5
PCIE FJSV,e4ta-fjgi
Broadcom,BCM5704C
/pci@500/pci@0/pci@c/pci@0/pci@1/pci@0/pci@0/pci@0/FJSV,e4ta@4
PCIE5
PCIE FJSV,e4ta-fjgi
Broadcom,BCM5704C
/pci@500/pci@0/pci@c/pci@0/pci@1/pci@0/pci@0/pci@0/FJSV,e4ta@4,1
PCIE5
PCIE FJSV,e4ta-fjgi
Broadcom,BCM5704C
/pci@500/pci@0/pci@c/pci@0/pci@1/pci@0/pci@0/pci@0,1/FJSV,e4ta@6
PCIE5
PCIE FJSV,e4ta-fjgi
Broadcom,BCM5704C
/pci@500/pci@0/pci@c/pci@0/pci@1/pci@0/pci@0/pci@0,1/FJSV,e4ta@6,1
PCIE5
PCIE FJSV,e2ta-fjgi
Broadcom,BCM5715C
/pci@500/pci@0/pci@c/pci@0/pci@1/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@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
/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
...
122
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
After Updated to System Firmware 7.2.8, a
Message That Indicates 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.
After updated to System Firmware 7.2.8, when you remove/insert the power cord or
reset ILOM, a message that indicates the presence or absence of a component such as
DIMM, PSU, or FAN (Device Present / Device Absent) may be displayed in
the event log.
Event log example:
314
Tue Apr 13 14:31:07 2010 IPMI
Log
minor
ID =
32 : 04/13/2010 : 14:30:45 : Entity Presence : /FB1/FM2/PRSNT :
Device Absent
313
Tue Apr 13 14:31:07 2010 IPMI
Log
minor
ID =
31 : 04/13/2010 : 14:30:45 : Entity Presence : /FB0/FM0/PRSNT :
Device Present
312
Tue Apr 13 14:31:07 2010 IPMI
Log
minor
ID =
30 : 04/13/2010 : 14:30:45 : Entity Presence : /PS1/PRSNT : Device
Present
311
Tue Apr 13 14:31:07 2010 IPMI
Log
minor
ID =
2f : 04/13/2010 : 14:30:45 : Entity Presence : /P1/BR1/CH0/D2/P :
Device Absent
310
Tue Apr 13 14:31:07 2010 IPMI
Log
minor
ID =
2e : 04/13/2010 : 14:30:45 : Entity Presence : /P0/BR1/CH1/D3/P :
Device Absent
The message also appears for the component which is not displayed on ILOM.
301
Tue Apr 13 14:31:07 2010 IPMI
Log
minor
ID = 25 : 04/13/2010 : 14:30:43 : Entity Presence : /MB/P0/MR0/P : Device
Absent
278
Tue Apr 13 14:31:06 2010 IPMI
Log
minor
ID =
e : 04/13/2010 : 14:30:40 : Entity Presence : /FB1/PRSNT : Device
Present
Workaround:
None. These messages are not the error messages. The message is displayed at the
point when ILOM restarted, in order to reload the component information, and can
be safely ignored.
Appendix A
Fixed Issues
123
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.
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.
Shown below is an event example in time of failure.
Configuration:
PCIE#0: Fibre Channel card
PCIE#1: void
PCIE#2: void
PCIE#3: void
PCIE#4: void
PCIE#5: void
The ILOM CLI interface output example:
/SYS/MB/RISER1/PCIE1/F20CARD
Properties:
type = F20 Card
ipmi_name = RSR1/PCIE1/F20
fault_state = OK
clear_fault_action = (none)
FRU Status in the prtdiag -v command output:
# prtdiag -v
...
=========================== FRU Status ===========================
Location
Name
Status
-----------------------------------------------------...
SYS/MB/RISER1/PCIE1
F20CARD
enabled
...
Workaround:
None. This can be safely ignored. To check the fibre channel card mount, use IO
Devices of the prtdiag command of Solaris OS.
124
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
The prtdiag command execution result:
# prtdiag
...
=========================== IO Devices ===========================
Slot +
Bus
Name +
Model
Status
Type Path
----------------------------------------------------------------...
MB
FIBRE fibre-channel
/pci@500/pci@0/pci@9/fibre-channel
...
OUTPUT Power and OUTPUT Current May Be
Incorrectly Displayed on the T5220 Server (CR
6942129)
This issue is resolved by updating the system firmware to 7.2.10 or later.
When you mounted one or two units of PSU of a certain version or later (*) on the
T5220 server, the showpower command execution result shows the OUTPUT Power
(W) and OUTPUT Current (A) values which are larger than the respective INPUT
values.
(*): To check whether or not the relevant PSU is mounted on your server, use the
following command.
[ILOM command]
See the show /SYS/PS0 command and the show /SYS/PS1 command execution
result, to check whether the following part number is included.
fru_part_number = 3002235
[ALOM CMT compatible shell command]
See the showfru /SYS/PS0 command and the showfru /SYS/PS1 command
execution result, to check whether the following part number is included.
/Sun_Part_Number_DataR/Sun_Part_No: 3002235
Event occurrence example:
Appendix A
Fixed Issues
125
When you mounted two units of PSU of a certain version or later (*):
sc> showpower -v
----------------------------------------------------------------Power Supplies:
----------------------------------------------------------------INPUT
OUTPUT
Power
Power
Supply
Status
(W)
(W)
----------------------------------------------------------------/SYS/PS0
OK
140.0
215.0 <-- (*)
/SYS/PS1
OK
160.0
250.0 <-- (*)
----------------------------------------------------------------Total Power
300.0
----------------------------------------------------------------INPUT
INPUT
INPUT
OUTPUT
OUTPUT
OUTPUT
Volt
Current
limit
Volt
Current
limit
Supply
(V)
(A)
(A)
(V)
(A)
(A)
----------------------------------------------------------------/SYS/PS0
103.2
1.36
10.00
12.1
17.77
62.00
/SYS/PS1
100.8
1.59
10.00
12.0
20.83
62.00
~~~~~
(*)
Workaround:
None. System Firmware's way of referring to the data of PSU of a certain version or
later was wrong. PSU itself has no problem, and the displayed data can be safely
ignored.
126
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Solaris OS Issues
TABLE A-4 lists the Solaris OS issues that have been fixed.
TABLE A-4
Fixed Solaris OS Issues
CR
Description
Workaround
6243759
(6479347)
The Solaris prtdiag command displays device
paths incorrectly for e1000g driver devices.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Force load all instances of the e1000g driver
and then restart the picld daemon as follows:
# devfsadm -i e1000g
# svcadm restart svc:/system/picl
Another workaround is to use the -r option
when booting or rebooting the system.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
6527622
After the OS panic, the server may display the
following message and stop at the ok prompt.
WARNING: promif_ldom_setprop: ds
response timeout
WARNING: unable to store boot command
for use on reboot
Note - Fixed in Solaris patch ID 127111-05 or
later.
Set auto-boot?=true or use the boot
command to start the server manually.
6536482
Currently, cpumem does not diagnose the
fbr/fbu errors.
Note - Fixed in Solaris patch ID 127127-11 or
later.
6552999
Performing a Control-C while the prtdiag -v
command is running causes blank
environmental data fields when run again.
The missing output is persistent until the picld
SMF service is restarted.
Note - Fixed in the Solaris 10 10/08 OS or by
installing patch ID 13094-01 or later.
If the environmental data is missing from the
prtdiag output, restart the picld SMF service
in the control domain with the following
command:
# svcadm restart picl
You can also upgrade the OS or install the patch
to avoid encountering this issue.
Appendix A
Fixed Issues
127
TABLE A-4
Fixed Solaris OS Issues (Continued)
CR
Description
Workaround
6554813
During the transmission using the GLDv3
(Generic LAN Driver version 3) compliant
Ethernet driver, if you execute the ifconfig
command with the modlist
(modinsert/modremove) option, the software
ring procedure of GLDv3 module could cause a
deadlock.
Note - Fixed in Solaris patch ID 127127-11 or
later.
Add the following entry to the /etc/system
file and reboot the system.
set ip:ip_soft_rings_cnt=0
6555956
Servers might experience panics generated from
the PCIe root complex.
A panic could occur during reboot with the
following message:
"Fatal error has occurred in: PCIe root
complex."
The panic only occurs during a reboot and has
never been observed during a reboot that
follows the panic. The panic can occur even if no
external USB devices are connected to the server.
Note - Fixed in the Solaris 10 5/08 OS or later.
If your server experiences this panic, perform
the workarounds described in “Servers Might
Experience Panics Generated From the PCIe
Root Complex (CR 6555956)” on page 131.
If you are not running the Solaris 10 10/08 OS,
this issue is also resolved by installing patch ID
128304-03 or later.
6566442
The prtdiag command output may be incorrect Note - Fixed in Solaris patch ID 127127-11 or
later.
• Information of memory is displayed as left
None.
aligned.
• Though the CPU threads have been
disabled, the FRU Status shows "All
FRUs are enabled"
• Information of a FAN replaced by hot
swapping is not displayed.
• Some of the memory configuration
information is not displayed.
6572985
During long SunVTS test runs, the SunVTS
cryptotest could fail intermittently with an
error similar to the following:
"cryptotest.FATAL n2rng0:
SUNW_RANDOM generate failed:
values generated fall outside
statistical tolerance"
6578410
The server might hang when trying to boot with
an Infiniband HBA card installed.
Note - Fixed in Solaris patch ID 139667-01 or
later.
Install the SunVTS Patch number 127294-01 (or
later).
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Add the following setting to the /etc/system
file:
set tavor:tavor_iommu_bypass = 0
You can also upgrade the OS or install the patch
to avoid encountering this issue.
128
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-4
Fixed Solaris OS Issues (Continued)
CR
Description
Workaround
6586624
The Solaris prtdiag and prtpicl commands
might not display complete information, as
follows:
• If the prtdiag -v option is specified, the
firmware version and the chassis serial
number might not be displayed.
• The prtpicl command will not always
display the physical-platform section.
Note - Fixed in System Firmware 7.0.9 or later.
Use alternative methods to obtain the
information you need as described in
“Information Missing From prtpicl and
prtdiag Commands (CR 6586624)” on
page 133.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
6586847
The Solaris prtdiag command without the -v
option does not show failures in the output.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Use the -v option when running the prtdiag
command.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
6587389
The Solaris prtdiag -v command might
display information with missing spaces,
making the output difficult to read.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Use the showenvironment command from the
ALOM CMT compatibility CLI as follows:
sc> showenvironment
For more details, see “The prtdiag -v
Command Has Formatting Issues (CR 6587389)”
on page 134.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
6588452
Booting the Solaris OS from an external USB
DVD-ROM drive could cause a panic and fail to
boot.
For more information, see “Booting the Solaris
OS From an External USB DVD-ROM Drive
Could Cause a Panic (CR 6588452)” on page 133.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Use the built-in DVD drive, or use a drive whose
subclass is not 2, 3, or 4.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
6588550
The Solaris prtdiag -v command is slow to
respond on the SPARC Enterprise T5120 servers.
The command might take as long as 5 minutes to
display output and therefore appears to hang.
Note - Fixed in Solaris patch ID 139502-01 or
later.
Be aware of the delay, and wait for the output.
Do not perform a Control-C.
Appendix A
Fixed Issues
129
TABLE A-4
Fixed Solaris OS Issues (Continued)
CR
Description
Workaround
6589612
The raidctl -l command continuously
outputs the following output:
# raidctl -l
Controller: 1
Volume:c1t0d0
Volume:c1t2d0
Disk: 0.0.0
Disk: 0.0.0
...
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Use the Control-C keyboard sequence to stop the
output.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
6592238
You might not be able to remove a RAID 1
volume after RAID 1 and RAID 0 volumes are
created.
When two volumes are created through the
onboard SAS controller (or any controller that
uses the mpt driver), the raidctl utility is
unable to delete one of the RAID volumes and
cannot list the correct disk information. When
this occurs, the following is the error message is
displayed:
# raidctl -l
Device record is invalid.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
Update the OS to the latest version or install the
mandatory patches to avoid encountering this
issue in the future.
6594506
After certain hardware error events, it is possible
that Solaris PSH events are no longer
transported between the SP and the domain.
For examples, see “PSH Events Are no Longer
Transported (CR 6594506)” on page 135.
Note - Fixed in the Solaris 10 5/08 OS (and
later) and in the Solaris 10 8/07 OS with patch
ID 127127-11 or later installed.
See “PSH Events Are no Longer Transported
(CR 6594506)” on page 135.
You can also upgrade the OS or install the patch
to avoid encountering this issue.
6596503
130
The output of the Solaris prtpicl -v
command might show CPU cores or strands
with an operational status of enabled when the
cores or strands do not exist.
Note - Fixed in System Firmware 7.1.6.d or
later.
Instead, use the output from the prtdiag or
prtpicl -c cpu commands.
You can also update the System Firmware to the
latest version to avoid encountering this issue.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-4
Fixed Solaris OS Issues (Continued)
CR
Description
Workaround
6581309
The selection message, r)eboot, o)k
prompt, h)alt?, appears on the OS console;
but if you select "o", you might see the following
messages.
Example 1:
r)eboot, o)k prompt, h)alt? o
WARNING: promif_ldom_setprop: ds
response timeout
Example 2:
r)eboot, o)k prompt, h)alt? o
WARNING: promif_ldom_setprop: ds
response timeout
WARNING: LDOMs Variable Update request
failed!
NOTICE: Unable to complete Domain
Service protocol version handshake
WARNING: Unable to connect to Domain
Service providers
WARNING: Unable to update LDOM Variable
Note - Fixed in Solaris patch ID 137111-01 or
later.
These messages have no effect on your server.
Apply patch ID 137111-01 (or later).
6601028
The LEDs of TX (data transmitting) and RX (data Note - Fixed in Solaris patch ID 137137-09 or
later.
receiving) on XAUI Card do not show correct
status of data transmission.
Please ignore these LED's status.
6886514
Boot drive may report "drive type unknown"
for Solaris format command. For details, see
“Boot Drive May Report "drive type unknown"
for Solaris format Command (CR 6886514)” on
page 138.
Note - Fixed in Solaris patch ID 124630-32 or
later.
For recovery procedures, see “Boot Drive May
Report "drive type unknown" for Solaris format
Command (CR 6886514)” on page 138.
6718841
Sun Explorer may fail to collect the ILOM data
(Tx000). If failed, it may take more than 30
minutes to return an error.
Note - Fixed in System Firmware 7.2.2.e or
later.
You can collect the ILOM data (Tx000) in
another way.
For details, see “Sun Explorer May Fail to
Collect the ILOM Data (Tx000) (CR 6718841)” on
page 136.
Servers Might Experience Panics Generated From
the PCIe Root Complex (CR 6555956)
This issue is resolved for servers running the Solaris 10 5/08 OS or later.
A panic could occur during reboot with the following message:
"Fatal error has occurred in: PCIe root complex."
Appendix A
Fixed Issues
131
The panic only occurs during a reboot and has never been observed during a reboot
that follows the panic. The panic can occur even if no external USB devices are
connected to the server.
Workarounds:
If your server experiences this panic, perform one or more of the following
workarounds:
■
To ensure that the system reboots and continues to function after a panic,
configure the server to automatically reboot using one of the following methods:
■
Using the ILOM CLI:
-> set /HOST/bootmode script="setenv auto-boot? true"
-> set /HOST/bootmode script="setenv auto-boot-on-error? true"
■
Using the ALOM CMT compatibility CLI:
sc> bootmode bootscript="setenv auto-boot? true"
sc> bootmode bootscript="setenv auto-boot-on-error? true"
■
To eliminate the possibility of the panic, disable the USB (only perform this
workaround if you do not use USB devices, including the built-in DVD drive):
■
Using the ILOM CLI:
-> set /SYS/MB/PCIE-IO/USB component_state=Disabled
■
Using the ALOM CMT compatibility CLI:
sc> disablecomponent /SYS/MB/PCIE-IO/USB
All devices on the USB will be disabled, including the DVD drive. Be aware that
the service processor will generate a fault and turn on the fault LED.
If you need to enable the USB, use the following commands:
■
Using the ILOM CLI:
-> set /SYS/MB/PCIE-IO/USB component_state=Enabled
■
Using the ALOM CMT compatibility CLI:
sc> enablecomponent /SYS/MB/PCIE-IO/USB
132
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Information Missing From prtpicl and
prtdiag Commands (CR 6586624)
This issue is resolved by updating the system firmware to 7.0.9 or later.
The prtdiag command might not display environmental and FRU status. If the -v
option (verbose) is specified, the firmware version and the chassis serial number
might not be displayed.
In addition, the prtpicl command might not display the physical-platform section.
Use one of the following alternative methods to obtain missing information:
■
Alternative for the prtdiag command – Use the following ALOM CMT
compatibility CLI commands:
sc>
sc>
sc>
sc>
■
showenvironment - displays the system’s environmental status
showfru component NAC - displays a component’s FRU status
showplatform - displays the Chassis Serial Number
showhost - displays the firmware version
Alternative for the prtpicl command – Walk through the targets of the show
SYS command with the ILOM CLI and the ILOM graphical user interface. Refer to
the Integrated Lights Out Manager (ILOM) 2.0 User’s Guide for details.
Booting the Solaris OS From an External USB
DVD-ROM Drive Could Cause a Panic (CR
6588452)
This issue is resolved for servers running the Solaris 10 5/08 OS and later. If you are
running Solaris 10 8/07, you can fix this issue with patch ID 127127-11 or later.
Booting the Solaris 10 OS from an external USB DVD-ROM drive could panic the
server and fail to boot the OS. This situation happens because the Solaris OS names
the device storage@1, and the System Firmware names the device cdrom@1.
Appendix A
Fixed Issues
133
Both the OpenBoot firmware and Solaris OS follow the 1275 USB bindings rules to
name nodes. For example:
TABLE :
1275 USB Bindings Rules for Naming Nodes
bInterface Class
bInterface Subclass
bInterface Protocol
Name
0x08
1
Any
storage
0x08
2
Any
cdrom
0x08
3
Any
tape
0x08
4
Any
floppy
0x08
5
Any
storage
0x08
6
Any
storage
0x08
Any
Any
storage
The Solaris 10 OS always names the node as storage@n. Therefore, the storage
device with a subclass of 2, 3, or 4 (SPARC Enterprise T5120 and T5220 must be 2)
cannot boot with Solaris 10 OS DVD.
Workaround: Use the drive whose subclass is not 2, 3, or 4 as the replacement.
The prtdiag -v Command Has Formatting
Issues (CR 6587389)
This issue is resolved for servers running the Solaris 10 5/08 OS and later. If you are
running Solaris 10 8/07, you can fix this issue with patch ID 127127-11 or later.
Some of the information displayed by the prtdiag(1M) command is difficult to read
when the -v option is used. White space is missing between the first and second
fields in the report.
The following formatting issues are displayed in the prtdiag -v command output:
134
■
Fans sensors – Missing spaces tab between Location and Sensor columns.
■
Temperature sensors – DIMMs missing spaces tab between Location and Sensor
columns.
■
LEDs – Location missing for SERVICE, LOCATE, ACT, PS_FAULT, TEMP_FAULT,
and FAN_FAULT DIMMs. Missing spaces tab between Location and LED.
■
Locations of sensors – have the first portion of their location truncated, resulting
in no location being reported for some items such as system status LEDs.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
To see this formatting information, use the showenvironment command in the
ALOM CMT compatibility CLI:
sc> showenvironment - displays the system environmental status
PSH Events Are no Longer Transported (CR
6594506)
This issue is resolved for servers running the Solaris 10 5/08 OS and later. If you are
running Solaris 10 8/07, you can fix this issue with patch ID 127127-11 or later.
After certain hardware error events, it is possible that PSH events are no longer
transported between the service processor (SP) and the domain. The following
scenarios are subject to this problem:
■
In a non-LDoms environment, an unrecoverable error occurs in the Solaris
domain.
■
In an LDoms environment, an unrecoverable error occurs in the control domain.
■
In either an LDoms or non-LDoms environment, a fatal error occurs in the system
(a fatal error resets the system at the hardware level).
Note – In an LDoms environment, unrecoverable errors in a uncontrolled LDoms
guest domain are not subject to this problem.
For example, an unrecoverable error in the control domain causes Solaris to panic.
Messages similar to the following are reported to the control domain console:
SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, VER: 1, SEVERITY: Major
EVENT-TIME: 0x46c61864.0x318184c6 (0x1dfeda2137e)
PLATFORM: SUNW,SPARC-Enterprise-T5220, CSN: -, HOSTNAME: wgs48-100
SOURCE: SunOS, REV: 5.10 Generic_Patch
DESC: Errors have been detected that require a reboot to ensure system
integrity. See http://www.sun.com/msg/SUNOS-8000-0G for more information.
AUTO-RESPONSE: Solaris will attempt to save and diagnose the error telemetry
IMPACT: The system will sync files, save a crash dump if needed, and reboot
REC-ACTION: Save the error summary below in case telemetry cannot be saved
Or, an unrecoverable error causes the firmware to abort and messages similar to the
following are reported to the SP console when logged into the ALOM CMT
compatibility CLI console:
Aug 17 22:09:09 ERROR: HV Abort: <Unknown?> (228d74) - PowerDown
Appendix A
Fixed Issues
135
After the control domain recovers, a diagnosis is performed. Messages to the console
indicate the cause of the unrecoverable error. For example:
SUNW-MSG-ID: SUN4V-8000-UQ, TYPE: Fault, VER: 1, SEVERITY: Critical
EVENT-TIME: Fri Aug 17 18:00:57 EDT 2007
PLATFORM: SUNW,SPARC-Enterprise-T5220, CSN: -, HOSTNAME: wgs48-100
SOURCE: cpumem-diagnosis, REV: 1.6
EVENT-ID: a8b0eb18-6449-c0a7-cc0f-e230a1d27243
DESC: The number of level 2 cache uncorrectable data errors has exceeded
acceptable levels. Refer to http://sun.com/msg/SUN4V-8000-UQ for more
information.
AUTO-RESPONSE: No automated response.
IMPACT: System performance is likely to be affected.
REC-ACTION: Schedule a repair procedure to replace the affected resource,
the identity of which can be determined using fmdump -v -u <EVENT_ID>.
At this point, the problem might have been encountered. This problem will prevent
future PSH events (for example, new hardware errors, correctable or uncorrectable)
from being transported into the domain and properly diagnosed.
Workaround: After the domain recovers and the diagnosis message is printed to the
Solaris console, reset the service processor as follows:
[In case of ILOM command mode]
-> reset /SP
Are you sure you want to reset /SP (y/n)? y
[In case of ALOM CMT compatible shell]
sc> resetsc
Are you sure you want to reset the SC [y/n]? y
Once the SP is restarted and you are able to log in as the admin (which means all
daemons are ready), type the following in the Solaris control domain:
# fmadm unload etm
# fmadm load /usr/platform/sun4v/lib/fm/fmd/plugins/etm.so
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.
136
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Sun Explorer may fail to collect the ILOM data (Tx000).
If failed, it may take more than 30 minutes to return an error.
Workaround: You can collect the ILOM data (Tx000) in another way.
1. Specify the option as follows.
# /opt/SUNWexplo/bin/explorer -w !Tx000
2. Confirm the version of ILOM.
Depending on the version of ILOM, the data collection method varies.
■
How to check the version
- ILOM mode
-> version
SP firmware 3.0.3.20.c
~ <-- ILOM3.0
SP firmware build number: 45383
SP firmware date: Tue Jun 2 15:38:58 PDT 2009
SP filesystem version: 0.1.22
->
- ALOM mode
sc> showsc version
SP firmware version: 3.0.3.20.c
~ <-- ILOM3.0
sc>
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 the
"Collect SP Data to Diagnose System Problems" section to collect the SP data
information.
■
In ILOM 2.x or earlier
Collect the ILOM and ALOM data and supply it to service engineers along with
the Sun Explorer output.
a. Collect the following data on ILOM.
show /SP/users
show /SP/users/admin
show /HOST
Appendix A
Fixed Issues
137
b. Create an ALOM compatible user and collect the following data on ALOM.
consolehistory -v
showcomponent
showdate
showenvironment
showfaults -v
showfru
showhost
showkeyswitch
showlogs -v -g 0 -p p
shownetwork
showplatform -v
showsc
showsc version -v
showusers
c. Reset ILOM.
-> reset /SP
Are you sure you want to reset /SP (y/n)? y
Performing hard reset on /SP
Boot Drive May Report "drive type unknown" for
Solaris format Command (CR 6886514)
This issue is resolved with Solaris patch ID 124630-32 or later.
During a period extending from mid-September to early October 2009
(approximately 3 weeks) a patch was preinstalled on some SPARC Enterprise T5120
and T5220 servers, which introduced a latent bug into those systems. The bug is
described as "latent" because it is activated only when the Solaris format command
is used. Otherwise, the bug has no effect on system behavior or performance.
When a system administrator or other user with root (/) privileges enters the
format command on a system containing this bug, the boot drive will report "drive
type unknown". This fault condition presents two problems for the administrator:
138
■
The administrator will be unable to access unused portions of the boot drive
because of the unknown drive type error.
■
The presence of mounted partitions blocks use of the format utility's auto
configure feature. Attempts to bypass this restriction by booting from the network
or removable media could put the system in an unbootable state.
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
The Workaround section below describes a procedure you can use to recover from
this "drive type unknown" fault mode without the risks associated with the network
and media boot methods.
Workaround: The sequence of steps shown in CODE EXAMPLE 1 must be followed
exactly as shown. To simplify tracking of the procedure, the steps are organized into
nine sections:
1. Determine whether or not the system's boot device is affected.
2. Shut server down and restart in single user mode with the root filesystem
mounted read only.
3. Mount the tmpfs /tmp filesystem to provide a working area.
4. Capture the boot drive's 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 full
access to the boot drive.
7. Run the format utility to restore the drive's "type".
8. Use the fmthard command and stored information to complete the recovery.
9. Verify the success of the recovery.
CODE EXAMPLE A-1
Procedure for Recovering a Boot Drive's "drive type"
1. Determine if the boot drive is affected:
root@host-1 # uname -a
SunOS host-1 5.10 Generic_141414-10 sun4v sparc SUNW,SPARC-Enterprise-T5220
root@host-1 # mount -p | head -1
/dev/dsk/c0t0d0s0 - / ufs - no rw,intr,largefiles,logging,xattr,onerror=
panic
root@host-1 # format c0t0d0s0 <========== boot device determined previously
/dev/dsk/c0t0d0s0 is currently mounted on /. Please see umount(1M).
/dev/dsk/c0t0d0s1 is currently used by swap. Please see swap(1M).
FORMAT MENU:
disk
- select a disk
type
- select (define) a
partition - select (define) a
format
- format and analyze
repair
- repair a defective
label
- write label to the
analyze - surface analysis
disk type
partition table
the disk
sector
disk
Appendix A
Fixed Issues
139
CODE EXAMPLE A-1
defect
backup
verify
save
inquiry volname !<cmd>
quit
format> disk
Procedure for Recovering a Boot Drive's "drive type"
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
show vendor, product and revision
set 8-character volume name The jumpstart install process
execute <cmd>, then return
The jumpstart install process
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <drive type unknown> <========== problem indication
/pci@0/pci@0/pci@2/scsi@0/sd@0,0
Specify disk (enter its number)[0]: ^C <========== quit with <ctrl>C
format> quit
root@host-1 #
2. Shut the server down; then bring it up in single user mode with root filesystem mounted read only.
root@host-1 # init 0
Oct 20 16:26:56 host-1 syslogd: going down on signal 15
svc.startd: The system is down.
syncing file systems... done
Program terminated
SPARC Enterprise T5220, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.30.4, 3968 MB memory available, Serial #xxxxxxxx.
Ethernet address 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
milestone=none
SunOS Release 5.10 Version Generic_141414-10 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Booting to milestone "none".
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
140
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
CODE EXAMPLE A-1
Procedure for Recovering a Boot Drive's "drive type"
Root password for system maintenance (control-d to bypass): <====== login
single user mode
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode
Oct 20 18:06:11 su: 'su root' succeeded for root on /dev/console
Sun Microsystems Inc.SunOS 5.10GenericJanuary 2005
Sourcing //.profile-EIS.....
3. Mount the tmpfs /tmp filesystem to provide a working area.
root@ # mount -F tmpfs /tmp
root@ # cd /tmp
4. Capture the boot drive's existing vtoc in a file stored in /tmp. Use the raw device of the boot device
determined at the beginning -- i.e ., use /dev/rdsk/c?t?d?s? not /dev/dsk/c?t?d?s?
root@ # prtvtoc /dev/rdsk/c0t0d0s0 > /tmp/vtoc <======boot disk vtoc saved
in /tmp/vtoc
5. Make a copy of the fmthard utility for use in the /tmp work area.
root@ # cp /usr/sbin/fmthard /tmp
6. Set and export the NOINUSE_CHECK variable:
root@ # setenv NOINUSE_CHECK=1
root@ # export NOINUSE_CHECK
7. Run the format utility to restore the drive's "type".
root@ # format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <drive type unknown> <========== drive type unknown is the issue
/pci@0/pci@0/pci@2/scsi@0/sd@0,0
Specify disk (enter its number): 0
Appendix A
Fixed Issues
141
CODE EXAMPLE A-1
Procedure for Recovering a Boot Drive's "drive type"
Format will now present the following menu, choose 0. Auto configure
AVAILABLE DRIVE TYPES:
0. Auto configure
1. Quantum ProDrive 80S
2. Quantum ProDrive 105S
[...]
17. Zip 250
18. Peerless 10GB
19. other
Specify disk type (enter its number): 0
c0t0d0: configured with capacity of 68.35GB <======= drive type corrected
<SUN72G cyl 14087 alt 2 hd 24 sec 424> <======= drive type corrected
selecting c0t0d0
[disk formatted]
Following Auto configure, the correct drive value should be reported.
FORMAT MENU:
disk
type
partition current
format
repair
label
analyze
defect
backup
verify
save
inquiry
volname
!<cmd>
quit
format> label
Ready to label
format> quit
root@ #
142
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
show vendor, product and revision
set 8-character volume name The jumpstart install process
execute <cmd>, then return
disk, continue? y
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
CODE EXAMPLE A-1
Procedure for Recovering a Boot Drive's "drive type"
8. Use the fmthard command and stored information to complete the recovery.
root@ # /tmp/fmthard -s /tmp/vtoc /dev/rdsk/c0t0d0s0 <=== raw boot device
used to capture vtoc.
fmthard: New volume table of contents now in place.
root@ #
9. Verify the success of the recovery.
root@ # format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@0/pci@0/pci@2/scsi@0/sd@0,0
Specify disk (enter its number): 0
selecting c0t0d0
[disk formatted]
FORMAT MENU:
disk
- select a disk
type
- select (define) a disk type
partition - select (define) a partition table
current
- describe the current disk
format
- format and analyze the disk
repair
- repair a defective sector
label
- write label to the disk
analyze
- surface analysis
defect
- defect list management
backup
- search for backup labels
verify
- read and display labels
save
- save new disk/partition definitions
inquiry
- show vendor, product and revision
volname
- set 8-character volume name The jumpstart install process
!<cmd>
- execute <cmd>, then return
quit
format> partition
PARTITION
0
1
2
3
4
MENU:
- change
- change
- change
- change
- change
'0'
'1'
'2'
'3'
'4'
partition
partition
partition
partition
partition
Appendix A
Fixed Issues
143
CODE EXAMPLE A-1
Procedure for Recovering a Boot Drive's "drive type"
5
- change '5' partition
6
- change '6' partition
7
- change '7' partition
select - select a predefined table
modify - modify a predefined partition table
name
- name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> print
Current partition table (original):
Total disk cylinders available: 14087 + 2 (reserved cylinders)
Part
0
1
2
3
4
5
6
7
Tag
root
swap
backup
unassigned
unassigned
unassigned
unassigned
unassigned
Flag
wm
wu
wm
wm
wu
wu
wu
wu
Cylinders
825 - 3298
0 - 824
0 - 14086
3299 - 5772
0
0
0
0
Size
12.00GB
4.00GB
68.35GB
12.00GB
0
0
0
0
Blocks
(2474/0/0)
(825/0/0)
(14087/0/0)
(2474/0/0)
(0/0/0)
(0/0/0)
(0/0/0)
(0/0/0)
25175424
8395200
143349312
25175424
0
0
0
0
partition> quit
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
defect
backup
verify
save
inquiry
volname
!<cmd>
quit
format> disk
144
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
show vendor, product and revision
set 8-character volume name The jumpstart install process
execute <cmd>, then return
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
CODE EXAMPLE A-1
Procedure for Recovering a Boot Drive's "drive type"
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@0/pci@0/pci@2/scsi@0/sd@0,0
Specify disk (enter its number)[0]:
selecting c0t0d0
[disk formatted]
format> quit
The drive type recovery is complete, reboot the server:
root@ # reboot
syncing file systems... done
rebooting...
Resetting...
#
SPARC Enterprise T5220, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.30.4, 3968 MB memory available, Serial #xxxxxxxx.
Ethernet address 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. All rights reserved.
Use is subject to license terms.
Hostname: host-1
The / file system (/dev/rdsk/c0t0d0s0) is being checked.
Reading ZFS config: done.
host-1 console login:
Appendix A
Fixed Issues
145
LDoms Related Issues
TABLE A-5 lists the LDoms related issues that have been fixed.
TABLE A-5
Fixed LDoms Related Issues
CR
Description
Workaround
6543749
A guest domain wanboot miniroot download
could take more than 30 minutes.
During boot or installation over wide area
networks, the time it takes to download the
miniroot could significantly increase when using
a virtual network device.
This performance degradation is relevant only
when trying to boot or install over wide area
networks using a virtual network device. A
similar boot or installation using a physical
network device works as expected, as does a
traditional local area net boot, or installing from
a virtual network device.
Note - Fixed in System Firmware 7.1.0.g or
later.
Be aware of the time needed to boot or perform
installations over a wide area network with a
virtual network device.
You can also update the System Firmware to the
latest version to avoid encountering this issue in
the future.
6567748
Domain status might not be reported accurately.
For example, the status reported for a domain
might be Running when the OS is not running.
This problem is encountered when the domain
status is reported by ILOM (BI and CLI) and
from the ALOM CMT compatibility
showplatform command.
The ambiguity also exists in the ILOM control
MIB, but not in the platform entity MIB. Thus,
the ambiguous domain status might be visible to
third-party systems monitoring tools if they
monitor this entry.
Note - Fixed in System Firmware 7.1.0.g or
later.
Ignore the domain status information from all
CLIs and BI output as well as from the domain
status entry in the ILOM control MIB. Retrieve
the true status of the domain by accessing the
domain console.
You can also update the System Firmware to the
latest version to avoid encountering this issue in
the future.
146
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
TABLE A-5
Fixed LDoms Related Issues (Continued)
CR
Description
Workaround
6592934
In the unlikely event that POST times out before
completing its test cycle, the firmware issues the
following message to the console:
Note - Fixed in System Firmware 7.1.0.g or
later.
If the error is observed on the console during
boot, power cycle the system, and ensure that
POST runs to completion.
You can also boot without running POST.
You can also update the System Firmware to the
latest version to avoid encountering this issue in
the future.
ERROR: POST timed out. Not all
system components tested.
The system continues to boot, but in a degraded
state. During the boot process the following
error messages are displayed:
WARNING: Unable to connect to Domain
Service providers
WARNING: Unable to get LDOM Variable
Updates
WARNING: Unable to update LDOM Variable
Any programs or services that depend on an
LDC channel run in a degraded state, or not at
all. Some programs that require LDC to function
are ldmd, fmd, and eeprom.
6593132
Changes to OpenBoot PROM variables with
non-default LDoms configuration do not persist.
If an LDoms variable is set to a non-default
value when an LDoms configuration is saved to
the service processor, and then later changed
back to its default value, the change to its
default value will not persist after a power cycle.
Note - Fixed in System Firmware 7.0.9 or later.
Save the SP configuration after changing an
LDoms variable. Example:
# ldm remove-spconfig my-new-config
# ldm add-spconfig my-new-config
You can also update the System Firmware to the
latest version to avoid encountering this issue in
the future.
6594395
The ldm set-variable command allows you
to set an LDoms variable to any arbitrary string.
If an LDoms variable is set to a value that is not
valid, the OpenBoot firmware issues a warning
message during boot with a list of correct values,
but without giving the name of the variable in
question.
Note - Fixed in System Firmware 7.1.0.g or
later.
For more information, refer to the Logical
Domains (LDoms) 1.0.1 Release Notes.
You can also update the System Firmware to the
latest version to avoid encountering this issue in
the future.
Appendix A
Fixed Issues
147
TABLE A-5
Fixed LDoms Related Issues (Continued)
CR
Description
Workaround
6597761
rm-io followed by multiple set-vcpu
operations might cause the firmware to abort or
ldmd core dump.
During a single delayed reconfiguration
operation, do not attempt to add CPUs to a
domain if any CPUs were previously removed
during the same delayed reconfiguration.
Note - Fixed in System Firmware 7.0.9 or later.
Either cancel the existing delayed
reconfiguration first (if possible), or commit it
(by rebooting the target domain), and then apply
the CPU addition.
Failure to heed this restriction can, under certain
circumstances, lead to the firmware returning a
parse error to the LDoms Manager, resulting in
the LDoms Manager aborting. Additionally, if
any VIO devices had been removed during the
same delayed reconfiguration operation, when
the LDoms manager restarts after the abort, it
incorrectly detects the need to perform a
recovery operation. This situation results in a
corrupt configuration, followed by a power
down.
You can also update the System Firmware to the
latest version to avoid encountering this issue in
the future.
148
SPARC Enterprise T5120 and T5220 Servers Product Notes • November 2010
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising