SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers ... · Contents vii Important Notes, Issues...

SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers

Product Notes for XCP Version 1101

Part No.: E21465-02April 2011

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.FUJITSU LIMITED provided technical input and review on portions of this material.Oracle and/or its affiliates and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in thisdocument, and such products, technology and this document are protected by copyright laws, patents, and other intellectual property laws andinternational treaties.This document and the product and technology to which it pertains are distributed under licenses restricting their use, copying, distribution, anddecompilation. No part of such product or technology, or of this document, may be reproduced in any form by any means without prior writtenauthorization of Oracle and/or its affiliates and Fujitsu Limited, and their applicable licensors, if any. The furnishings of this document to you does notgive 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 orrepresent 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/orlicensed 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. Pleasecontact 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. andin 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 bearingSPARC trademarks are based upon architectures developed by Oracle and/or its affiliates. SPARC64 is a trademark of SPARC International, Inc., usedunder 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 Oracleand/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 anyproduct 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 NOREPRESENTATIONS OR WARRANTIES OF ANY KIND (EXPRESS OR IMPLIED) REGARDING SUCH PRODUCT OR TECHNOLOGY OR THISDOCUMENT, 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 NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Unlessotherwise 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 theiraffiliates 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 forany 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, AREDISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

PleaseRecycle

Copyright © 2011, Oracle et/ou ses sociétés affiliées. Tous droits réservés.FUJITSU LIMITED a fourni et vérifié des données techniques de certaines parties de ce composant.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 ettechnologies 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, ladistribution et la décompilation. Aucune partie de ce produit, de ces technologies ou de ce document ne peut être reproduite sous quelque forme que cesoit, 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 éventuelsbailleurs 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 produitou 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 oude 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 parcopyright 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 technologiesrelatives 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 surdemande 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 marquedé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 deFujitsu 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. Lesproduits 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 SPARCInternational, Inc., utilisée sous licence par Fujitsu Microelectronics, Inc. et Fujitsu Limited. Tout autre nom mentionné peut correspondre à des marquesappartenant à d’autres propriétaires.United States Government Rights - Commercial use. U.S. Government users are subject to the standard government user license agreements of Oracleand/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 rapportavec ce document ou tout produit ou toute technologie décrits dans les présentes correspondent aux garanties expressément stipulées dans le contrat delicence régissant le produit ou la technologie fournis. SAUF MENTION CONTRAIRE EXPRESSÉMENT STIPULÉE DANS CE CONTRAT, ORACLE OUFUJITSU 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, YCOMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE À LA QUALITÉ MARCHANDE, À L’APTITUDE À UNE UTILISATIONPARTICULIÈRE OU À L’ABSENCE DE CONTREFAÇON, SONT EXCLUES, DANS LA MESURE AUTORISÉE PAR LA LOI APPLICABLE. Sauf mentioncontraire 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 oul’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, detout 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 dommageindirect, 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, ESTFORMELLEMENT EXCLUE, DANS LA MESURE AUTORISÉE PAR LA LOI EN VIGUEUR, Y COMPRIS NOTAMMENT TOUTE GARANTIEIMPLICITE RELATIVE À LA QUALITÉ MARCHANDE, À L’APTITUDE À UNE UTILISATION PARTICULIÈRE OU À L’ABSENCE DECONTREFAÇON.

Contents

Preface ix

1. Introduction 1

Compatible Hardware, Firmware, and Software Matrix 2

Obtaining Oracle Solaris Patches 3

Compatible Web Browsers 4

2. Information About XCP 1101 Firmware 5

What’s New in This Release 5

Upgrading and Downgrading XCP 6

Upgrading to This Release 6

Updating the OpenBoot PROM Firmware 6

Upgrading From a Version Earlier Than XCP 1050 6

Domain Restart Required After Certain Type of XCP Upgrade 6

Downgrading XCP Firmware 7

XCP Functionality Issues and Limitations 7

XCP Known Issues (CRs) and Workarounds 9

3. Information About Software 11

Capacity on Demand (COD) 11

COD Changes 11

v

Remote Initial Login 12

Fault Management 12

Identifying Degraded Memory in a System 13

▼ To Identify Degraded Memory in a System 13

Sun Java Enterprise System 14

Enabling the Web Console SMF Service 14

▼ To Enable the Web Console SMF Service 14

Software Functionality Issues and Limitations 15

Oracle Solaris OS Issues (CRs) and Workarounds 16

Known Issues in All Supported Oracle Solaris Releases 16

CR 6660168 18

Issues Fixed in Oracle Solaris 10 9/10 19






Software Documentation Updates 34

4. Information About Hardware 35

Important Notes, Issues and Workarounds – All M-Series Servers 35

Booting From a WAN Boot Server 35

Booting Multiple Systems From a Single J4200 JBOD Storage Array 36

Notes on the Use of USB Memory 36

Hardware Functionality Issues and Limitations 37

Important Notes, Issues and Workarounds – M3000 Servers Only 37

Patches for Emulex PCI Express (PCIe) Cards 37


vi SPARC Enterprise Mx000 Servers Product Notes for XCP 1101 • April 2011

Important Notes, Issues and Workarounds – M4000/M5000 and M8000/M9000Servers Only 38

DVD Drives and cfgadm 38

F20 PCIe Cards 38

Sun Crypto Accelerator 6000 Cards 39

U320 PCIe SCSI Card 39

Patches for QLogic PCIe Cards 39

Patches for Emulex PCI Express (PCIe) Cards 39


Hardware Documentation Updates for the M3000 Server 41

Hardware Documentation Updates for the M4000/M5000 Servers 41

Hardware Documentation Updates for the M8000/M9000 Servers 41

Contents vii

viii SPARC Enterprise Mx000 Servers Product Notes for XCP 1101 • April 2011

Preface

These product notes contain important and late-breaking information about theSPARC Enterprise M3000/M4000/M5000/M8000/M9000 servers – sometimes calledM-Series servers – from Oracle Corporation and Fujitsu Limited. It covers hardware,software, firmware, and documentation related to the XCP 1101 firmware release.

Some references to server names and document names are abbreviated forreadability. For example, if you see a reference to the M9000 server, note that the fullproduct name is the SPARC Enterprise M9000 server. And if you see a reference tothe XSCF Reference Manual, note that the full document name is the SPARC EnterpriseM3000/M4000/M5000/M8000/M9000 Servers XSCF Reference Manual.

Besides this document, you also should read, at minimum, the overview guide foryour server, the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 ServersAdministration Guide, and the SPARC Enterprise M3000/M4000/M5000/M8000/M9000Servers XSCF User’s Guide.

At publication of this document, M-Series servers were shipping with XCP 1101firmware supported or installed. That might no longer be the latest available version,or the version now installed. Always see the Product Notes that apply to thefirmware on your server, and those that apply to the latest firmware release.

This chapter includes the following sections:

■ “Audience” on page x

■ “Related Documentation” on page x

■ “Text Conventions” on page xii

■ “Syntax of the Command-Line Interface (CLI)” on page xiii

■ “Documentation Feedback” on page xiii

ix

AudienceThis document is written for experienced system administrators with workingknowledge of computer networks and advanced knowledge of the Oracle SolarisOperating System (Oracle Solaris OS).

Related DocumentationThe following table lists related M-Series documents, which can be viewed online atthe following locations:

Hardware documents:

M3000 server:http://www.oracle.com/pls/topic/lookup?ctx=E19867-01&id=homepage


M5000 server,http://www.oracle.com/pls/topic/lookup?ctx=E19580-01&id=homepage



Software documents:

http://www.oracle.com/technetwork/documentation/sparc-mseries-servers-252709.html

Oracle Solaris Operating System documents:

http://www.oracle.com/technetwork/documentation/index.html

Related M-Series Server Documents

SPARC Enterprise M3000 Server Site Planning Guide

SPARC Enterprise M4000/M5000 Servers Site Planning Guide

SPARC Enterprise M8000/M9000 Servers Site Planning Guide

SPARC Enterprise Equipment Rack Mounting Guide

x SPARC Enterprise Mx000 Servers Product Notes for XCP 1101 • April 2011

SPARC Enterprise M3000 Server Getting Started Guide*

SPARC Enterprise M4000/M5000 Servers Getting Started Guide*

SPARC Enterprise M8000/M9000 Servers Getting Started Guide*

SPARC Enterprise M3000 Server Overview Guide

SPARC Enterprise M4000/M5000 Servers Overview Guide

SPARC Enterprise M8000/M9000 Servers Overview Guide

SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers Important Legal and Safety Information*

SPARC Enterprise M3000 Server Safety and Compliance Guide

SPARC Enterprise M4000/M5000 Servers Safety and Compliance Guide

SPARC Enterprise M8000/M9000 Servers Safety and Compliance Guide

External I/O Expansion Unit Safety and Compliance Guide

SPARC Enterprise M4000 Server Unpacking Guide*

SPARC Enterprise M5000 Server Unpacking Guide*

SPARC Enterprise M8000/M9000 Servers Unpacking Guide*

SPARC Enterprise M3000 Server Installation Guide

SPARC Enterprise M4000/M5000 Servers Installation Guide

SPARC Enterprise M8000/M9000 Servers Installation Guide

SPARC Enterprise M3000 Server Service Manual

SPARC Enterprise M4000/M5000 Servers Service Manual

SPARC Enterprise M8000/M9000 Servers Service Manual

External I/O Expansion Unit Installation and Service Manual

SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers Administration Guide

SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide

SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF Reference Manual

SPARC Enterprise M4000/M5000/M8000/M9000 Servers Dynamic Reconfiguration (DR) User’s Guide

SPARC Enterprise M4000/M5000/M8000/M9000 Servers Capacity on Demand (COD) User’s Guide

SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers Product Notes†

SPARC Enterprise M3000 Server Product Notes

SPARC Enterprise M4000/M5000 Servers Product Notes


Preface xi

Text ConventionsThis manual uses the following fonts and symbols to express specific types ofinformation.

SPARC Enterprise M8000/M9000 Servers Product Notes

External I/O Expansion Unit Product Notes

SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers Glossary

* This is a printed document.

† Beginning with the XCP 1100 release.

Font/symbol Meaning Example

AaBbCc123 What you type, when contrastedwith on-screen computer output.This font represents the example ofcommand input in the frame.

XSCF> adduser jsmith

AaBbCc123 The names of commands, files, anddirectories; on-screen computeroutput.This font represents the example ofcommand output in the frame.

XSCF> showuser -PUser Name: jsmithPrivileges: useradm

auditadm

Italic Indicates the name of a referencemanual, a variable, or user-replaceable text.

See the SPARC EnterpriseM3000/M4000/M5000/M8000/M9000Servers XSCF User’s Guide.

" " Indicates names of chapters,sections, items, buttons, or menus.

See Chapter 2, "System Features."


xii SPARC Enterprise Mx000 Servers Product Notes for XCP 1101 • April 2011

Syntax of the Command-Line Interface(CLI)The command syntax is as follows:

■ A variable that requires input of a value must be put in Italics.

■ An optional element must be enclosed in [].

■ A group of options for an optional keyword must be enclosed in [] and delimitedby |.

Documentation FeedbackIf you have any comments or requests regarding this document, go to the followingweb site:

http://www.oraclesurveys.com/se.ashx?s=25113745587BE578

Preface xiii

http://www.oraclesurveys.com/se.ashx?s=25113745587BE578

xiv SPARC Enterprise Mx000 Servers Product Notes for XCP 1101 • April 2011

CHAPTER 1

Introduction

This document describes the XCP 1101 firmware release as supported on M-Series(M3000/M4000/M5000/M8000/M9000) servers. Except where noted otherwise, theinformation in this document applies to all of these servers.

This chapter contains important information that applies to firmware, hardware andsoftware as of this firmware release. Other sections describe matters limited tofirmware, software, or hardware.

Note – Oracle publishes Product Notes for regular firmware releases, such as XCP1100, but for only some updates, such as XCP 1101. Always check the Oraclefirmware download site for the latest available firmware and its associatedREADME file.

Generally, Product Notes content supersedes that of other product documentationbecause Product Notes are published more frequently. However, in case of a conflict,compare the publication date on each document’s title page.

1

Compatible Hardware, Firmware, andSoftware MatrixPlease check the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Server,Processor, and Software Requirements Matrix at the following URL:

https://supporthtml.oracle.com/ep/faces/secure/km/DocumentDisplay.jspx?id=1145383.1

The matrix lists supported hardware, firmware and operating system (OS) versions,as well as required software patches. Always refer to a patch’s README forinformation about patch requirements and special installation instructions. The two-digit suffix of each patch represents the minimum revision level of the patch. Checkhttp://myoraclesupport.com for the latest patch revision. Apply patches in theorder listed.

Caution – Before installing any processor – such as the SPARC64 VII+ processor –verify that your server satisfies all requirements for that processor type. Suchrequirements include minimum required XCP firmware and Oracle Solaris OSversions, and all required patches.

2 SPARC Enterprise Mx000 Servers Product Notes for XCP 1101 • April 2011

http://myoraclesupport.com

https://supporthtml.oracle.com/ep/faces/secure/km/DocumentDisplay.jspx?id=1145383.1

Obtaining Oracle Solaris PatchesThe Oracle Sun Connection Update Manager can be used to reinstall the patches ifnecessary or to update the system with the latest set of mandatory patches. For moreinformation about the Sun Connection Update Manager, refer to the Sun UpdateConnection System Administration Guide at:

http://docs.sun.com/app/docs/prod/updconn.sys

Or visit:

http://wikis.sun.com/display/SunConnection/Update+Manager

Installation information and README files are included in the patch downloads.

Two options are available to register your system and to use the Oracle SunConnection Update Manager to obtain the latest Oracle Solaris OS patches:

■ Use the Update Manager GUI to obtain patches. For more information, refer tothe Sun Update Connection documentation at the links mentioned previously.

■ Use the smpatch(1M) command to obtain patches. For more information, refer tothe smpatch(1M) man page or the reference manual collection for your version ofthe Oracle Solaris OS.

Caution – For SPARC Enterprise M4000/M5000 servers running the Oracle Solaris10 11/06 OS, patches 123003-03 and 124171-06 must be installed on your systemprior to using Sun Connection Update Manager. These patches can be downloadedfrom http://myoraclesupport.com. Note that Oracle Solaris 10 11/06 does notsupport SPARC64 VII processors.

Chapter 1 Introduction 3

http://docs.sun.com/app/docs/prod/updconn.sys

http://wikis.sun.com/display/SunConnection/Update+Manager

http://myoraclesupport.com.

Compatible Web BrowsersMany web browsers support the XSCF Web. The browsers in TABLE 1-1 havedemonstrated compatibility with the XSCF Web through testing.

TABLE 1-1 Tested Web Browser Versions

Web Browser Application Version

Mozilla Firefox 3.0 and 3.5.9

Microsoft Internet Explorer 7.0 and 8.0


CHAPTER 2

Information About XCP 1101Firmware

This chapter covers updates to XCP firmware in this release as well as other notablechanges.

See also “Compatible Hardware, Firmware, and Software Matrix” on page 2.

Note – This release is an update of the XCP 1100 firmware. For more informationabout the XCP 1100 release, see the SPARC EnterpriseM3000/M4000/M5000/M8000/M9000 Servers Product Notes for XCP Version 1100.

What’s New in This Release■ The XCP 1101 firmware now supports the M3000 server with 2.86 GHz

processors.

■ This XCP 1101 release introduces support for a new Capacity on Demand (COD)permit delivery system. See “Capacity on Demand (COD)” on page 11.

5

Upgrading and Downgrading XCP

Upgrading to This ReleaseFor information about upgrading your firmware, see the SPARC EnterpriseM3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

Note – After upgrading XCP firmware, use the rebootxscf(8) command to resetthe XSCF.

Updating the OpenBoot PROM FirmwareTo complete updating the OpenBoot PROM (OBP) firmware in the target domain,restart the domain as soon as possible after completing the update.

Upgrading From a Version Earlier Than XCP 1050If you are currently running a version earlier than XCP 1050, you cannot directlyupgrade to this XCP release. You must first upgrade to an interim version of XCP(between 1050 and 1070, inclusive). Contact your Oracle representative for access toolder XCP releases.

Note – Use the deleteuser(8) command to delete any accounts named adminprior to updating to XCP 1050 or later. The admin account name is reserved startingin XCP 1050.

Domain Restart Required After Certain Type ofXCP UpgradeOn a domain that has been in operation during an update from an XCP versionbetween XCP 1050 and 1070 (inclusive), when you perform dynamic reconfiguration(DR) to add or replace the SPARC64 VII processors, you need to update theOpenBoot PROM firmware. The OpenBoot PROM firmware is updated as you


update the XCP and restart the domain. For this reason, restart all the domains afteryou update the firmware to the latest XCP release, regardless of whether you addedor replaced the SPARC64 VII processors.

Downgrading XCP FirmwareDowngrading your XCP firmware to an earlier release would remove improvementsand corrections provided in the latest release and could lead to a system failure dueto mismatched dependencies. However, if you must downgrade your XCP release,execute the following command afterward to clear old-style audit logs:

XCP Functionality Issues andLimitationsThis section describes known XCP firmware issues.

Note – Do not use the Service Processor (SP) as the Network Time Protocol (NTP)server. Using an independent NTP server provides optimal reliability in maintainingconsistent time on the SP and the domains. For more information about NTP, see theSun Blueprint document, Using NTP to Control and Synchronize System Clocks:http://www.sun.com/blueprints/0701/NTP.pdf

XSCF> restoredefaults -c xscfu

Chapter 2 Information About XCP 1101 Firmware 7

http://www.sun.com/blueprints/0701/NTP.pdf

TABLE 2-1 XCP Functionality Issues and Limitations

M3000M4000/M5000

M8000/M9000 Issue

o o o You cannot use the following user account names, as they arereserved for system use: adm, admin, apache, bin, daemon,default, ldap, nobody, ntp, operator, proxyuser, root, rpc,rpcuser, and sshd. See “Remote Initial Login” on page 12

o o o An XSCF user account user name cannot match an LDAP user name, andan XSCF user account number (UID) cannot match an LDAP UID number.

o o o When you import XCP or update the firmware using the XSCF, you mightsee Web session ID errors displayed on the web browser. When youspecify the timeout period as over 30 minutes in the Autologout setting,Internal Server Errors might be displayed. To reconnect to the XSCF Web,close the current browser and open the new browser.

o o o Before using the XSCF Web, disable pop-up blocking and remove anyplug-ins such as the search tool installed with the browser.

o o o XSCF-LAN is compliant with auto-negotiation. Set the network devicethat connects with XSCF-LAN to the auto-negotiation mode. Otherwisewhen you connect the XSCF-LAN and the network device (fixed to thefull-duplex mode, according to the IEEE 802.3 rule) the XSCF-LANcommunicates in half-duplex mode and network communication speedmight slow down or communication errors might occur.

o o For this XCP release, the XSCF browser user interface (XSCF Web) doesnot support the External I/O Expansion Unit Manager feature.

o o Due to DR and ZFS file system interoperability issues, M4000/M5000servers are shipped pre-installed using the UFS file system. See CR6522017 in TABLE 3-2.

o o o The XCP 1093 release was the first XCP release to support a domainrunning Oracle Solaris 10 9/10 with the processor groups observabilityfeature enabled. Please refer to Oracle Solaris 10 9/10 OS Product Notesfor more information.


XCP Known Issues (CRs) andWorkaroundsThis section lists significant CRs and, if available, suggested workarounds,

TABLE 2-2 XCP Issues and Workarounds

CR ID M3000M4000/M5000

M8000/M9000 Description Workaround

7009084 o o o If setpasswordpolicy -r is set to 0,existing XCSF users are unable to changetheir password and get the error message,password: Operation failed

Do not execute the command:setpasswordpolicy -r 0

See the entry for this command inTABLE 3-9.

7012224 o o o On occasion, messages similar to thefollowing might appear on the domainconsole during OS reboot or shutdown:

Nov 30 16:56:36 sca-m5k-3-a ip:ipsec_check_inbound_policy: PolicyFailure for the incoming packet (notsecure); Source 192.168.224.001,Destination 192.168.224.002.

Such messages from the OS areinformational only. You can safely ignorethem.

Ignore the alarms.

7018644 o o Faults marked as REPAIRED/RESOLVED ona domain are resent to the XSCF each timethe domain is rebooted or the XSCF isrebooted. If the XSCF is not replaced, this isnot a problem and no new fault is generated.However, if the XSCF on M4000/M5000servers or the MBU on M3000 servers isreplaced, a new fault for the resolvedproblem might be generated.

When a new fault is generated afterthe XSCF or MBU is replaced,check the solaris -u uid infmdump -V output to determine ifthe fault is genuine.

7020161 o In M3000 servers with SPARC64 VII+ (2.86GHz processors), Permitted AC powerconsumption is shown as 470W. The correctvalue is 505W.

There is no workaround.

Chapter 2 Information About XCP 1101 Firmware 9

CHAPTER 3

Information About Software

This chapter describes Oracle Solaris software issues and workarounds as related tothis XCP firmware release. See also “Compatible Hardware, Firmware, and SoftwareMatrix” on page 2.

Your server was shipped with the Oracle Solaris Operating System and JavaEnterprise System software preinstalled.

Capacity on Demand (COD)The XCP 1101 firmware introduces a new release of the Capacity on Demand (COD)feature. See the latest version of the SPARC Enterprise M4000/M5000/M8000/M9000Servers Capacity on Demand (COD) User’s Guide.

COD ChangesThe new version of COD:

■ Introduces a new, streamlined process for acquiring COD keys through Oracle’sE-Delivery process. Any old-style keys in your COD database will continue towork, even when new-style keys are also present.

■ Supports unlocked COD keys that are not assigned to a server’s individualChassis HostID and can be installed on other servers. New COD keys include theword UNLOCKED.

■ Ends support for the headroom feature. If you have any COD processors runningon headroom, either uninstall the number of COD processors from domains equalto the number in violation or purchase and install COD Hardware Activation

11

Options for those COD resources in use but not yet purchased. Then executesetcod 0 to set headroom to zero, and power the domain off then on to ensureonly authorized COD resources are installed.

Note – The XCP 1100 firmware release introduced support for theshowcodactivationhistory(8) command, which lets you view or transfer CODactivation history.

Remote Initial LoginIn addition to the standard default login, M-Series servers are delivered with atemporary login called admin to enable remote initial login, through a serial port.The admin user privileges are fixed to useradm and cannot be changed. You cannotlog in as temporary admin using the standard UNIX user name and passwordauthentication or SSH public key authentication. The temporary admin account hasno password, and one cannot be added for it.

The temporary admin account is disabled after someone logged in as the defaultuser or as temporary admin has successfully added the first user with validpassword and privileges.

For more information about login account names, see also TABLE 2-1 in Chapter 2.

Fault ManagementFault management software does not differentiate between SPARC64 VII+ andSPARC64 VII processors. Ereport/fault event strings display SPARC64 VII for bothprocessor types, for example:

fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.core.ce


However, the FRU field of the fault does contain the correct part number, allowingyou to identify the processor type. For example:

Identifying Degraded Memory in aSystem

▼ To Identify Degraded Memory in a System1. Log in to XSCF.

2. Type the following command:

3. The following example reveals that DIMM number 0A on the motherboard unithas degraded memory:

XSCF> fmdump -vNov 19 00:58:18.6244 1147afbe-d006-4d46-8cf2-d9b6e5a893dc SCF-8007-AR 100% fault.chassis.SPARC-Enterprise.cpu.SPARC64-VII.way.ce

Problem in: hc:///chassis=0/cmu=1/cpu=0 Affects: hc:///chassis=0/cmu=1/cpu=0 FRU: hc://:product-id=SPARC Enterprise M8000:chassis-id=2030638006:server-id=aaa-dc1-3-sf0:serial=PP1032026V:part=CA06620-D061 B1 \371-4929-02:revision=0a01/component=/CMU#1/CPUM#0 Location: /CMU#1/CPUM#0

XSCF> showstatus

XSCF> showstatusMBU_A Status: Normal;

MEM#0A Status:Degraded

Chapter 3 Information About Software 13

Sun Java Enterprise SystemThe Sun Java Enterprise System software is a comprehensive set of software and lifecycle services that make the most of your software investment. It might not includepatches that are mandatory for your server.

Note – Due to an issue that arises from the installation of the Java Enterprise System5 Update 1 on your system, it might be necessary to enable the WebConsole SMFservice.

Enabling the Web Console SMF Service

▼ To Enable the Web Console SMF Service● Log in to a terminal as root, then enable the service.

If you have to reload the software, go to the following web site for download andinstallation instructions:


If you download a fresh copy of software, that software might not include patchesthat are mandatory for your server. After installing the software, verify that allrequired patches are installed and install any that are not.

# svcadm enable svc:/system/webconsole:console



Software Functionality Issues andLimitationsThis section describes software functionality issues and limitations in this release.

TABLE 3-1 Software Functionality Issues and Limitations

M3000M4000/M5000

M8000/M9000 Issue

o o o The setsnmp(8) and showsnmp(8) commands do not notify the user ofauthorization failure. Upon such failure, confirm that the SNMP trap hostis working and re-execute the command using the correct user name.

o The following functions, which display power consumption, are notsupported on M4000/M5000 servers. Any values displayed are invalid:

• The power operand of the showenvironment(8) command.• XSCF Web.

o o o In the settimezone -c adddst command, when you set eight or moreletters to the abbreviation of time zone and the name of Daylight SavingTime, execution of the showlogs command induces a segmentation faultand results in an error. [CR 6789066]

Workaround: Specify the abbreviation of time zone and the name ofDaylight Saving Time in seven letters or less.

o The M3000 server does not support External I/O Expansion Units.

o o o Only M3000 servers with a SPARC64 VII+ (2.86 GHz) processor let youuse the raidctl(1M) command to create a hardware RAID volume usingthe onboard SAS/LSI controller.All M-Series servers support use of the raidctl(1M) command to viewdisk/controller status, and on any PCI host bus adapter (HBA) installed inthe system.The RAID-creation limitation was once designated as CR 6723202. There isno workaround.


Oracle Solaris OS Issues (CRs) andWorkaroundsThis section contains information about Oracle Solaris OS issues known at time ofpublication. The following tables list issues you might encounter, depending in parton which Oracle Solaris OS release you are using.

Known Issues in All Supported Oracle SolarisReleasesTABLE 3-2 lists Oracle Solaris OS issues that you might encounter in any OracleSolaris release. If your domains are not running the latest Oracle Solaris release, alsotake notice of CRs fixed in releases later than yours, as noted in the tables thatfollow.

TABLE 3-2 Solaris OS Issues and Workarounds for All Supported Releases (1 of 3)

CR ID M3000M4000/M5000


CR 4816837 o o System hangs when executingparallel hot-plug operationwith SP DR in suspend phase.


CR 6459540 o o The DAT72 internal tape driveconnected to M4000/M5000/M8000/M9000 servers mighttime out during tapeoperations.The device might also beidentified by the system as aQIC drive.

Add the following definition to/kernel/drv/st.conf:

tape-config-list=

"SEAGATE DAT DAT72-000",

"SEAGATE_DAT DAT72-000",

"SEAGATE_DAT DAT72-000";

SEAGATE_DAT DAT72-000=1,0x34,0,0x9639,4,0x00,0x8c,0x8c,

0x8c,3;

There are four spaces between SEAGATE DATand DAT72-000.

CR 6522017 o o Domains using the ZFS filesystem cannot use DR.

Set the maximum size of the ZFS ARC lower.For detailed assistance, contact your authorizedservice representative.


CR 6531036 o o o The error message networkinitialization failedappears repeatedly after a bootnet installation.


CR 6532215 o o o volfs or dscp services mightfail when a domain is booted.

Restart the service. To avoid the problem, issuethe following commands.# svccfg -s dscp setprop \start/timeout_seconds=count: 300# svccfg -s volfs setprop \start/timeout_seconds=count: 300# svcadm refresh dscp# svcadm refresh volfs

CR 6588650 o o On occasion, aM4000/M5000/M8000/M9000server is unable to DR after anXSCF failover to or frombackup XSCF


CR 6589644 o When XSCF switchoverhappens on an M8000/M9000server after the system boardhas been added using theaddboard command, theconsole is no longer available.

The console can be recovered by pressingCTRL-q.

CR 6592302 o o Unsuccessful DR operationleaves memory partiallyconfigured.

It might be possible to recover by adding theboard back to the domain with an addboard-d command. Otherwise try deleteboard(8)again.

CR 6611966 o o DR deleteboard(8) andmoveboard(8) operationsmight fail. Example formessages on domain:drmach: WARNING: Devicedriver failure: /pcidcs: <xxxx>config_change_state:

Hardware specific failure:unconfigure SB1: Devicedriver failure: /pci

Try DR operations again.

CR 6660168 o o o See “CR 6660168” on page 18,removed from this table due tothe length of the description.

CR 6674266 o o This CR is a duplicate of CR 6611966.


CR ID M3000M4000/M5000



CR 6660168If a ubc.piowbeue-cpu error occurs on a domain, the Oracle Solaris FaultManagement cpumem-diagnosis module might fail, causing an interruption in FMAservice. If this happens, you will see output similar to the following sample in theconsole log:

Workaround: If fmd service fails, issue the following command on the domain torecover:

CR 6745410 o o o Boot program ignores the Kadboption which causes the systemnot to boot.

Use kmdb instead of kadb.

CR 6794630 o o o An attempt to use the GUI toinstall Oracle Solaris in adomain larger than 2TB mightfail.

Use the command-line interface to install theOracle Solaris OS.

CR 7009469 o Creating a RAID using theraidctl(1M) command generatesa warning message on initialprocess. Subsequent RAIDconfigurations do not.

None.

SUNW-MSG-ID: FMD-8000-2K, TYPE: Defect, VER: 1, SEVERITY: MinorEVENT-TIME: Fri Apr 4 21:41:57 PDT 2008PLATFORM: SUNW,SPARC-Enterprise, CSN: 2020642002,HOSTNAME: <hostname>SOURCE: fmd-self-diagnosis, REV: 1.0EVENT-ID: 6b2e15d7-aa65-6bcc-bcb1-cb03a7dd77e3DESC: A Oracle Solaris Fault Manager component has experiencedan error that required the module to be disabled. Refer tohttp://sun.com/msg/FMD-8000-2K for more information.AUTO-RESPONSE: The module has been disabled. Eventsdestined for the module will be saved for manual diagnosis.IMPACT: Automated diagnosis and response for subsequent eventsassociated with this module will not occur.REC-ACTION: Use fmdump -v -u <EVENT-ID> to locate the module. Usefmadm reset <module> to reset the module.

# svcadm clear fmd


CR ID M3000M4000/M5000



Then restart cpumem-diagnosis:

Issues Fixed in Oracle Solaris 10 9/10TABLE 3-3 lists issues that have been fixed in the Oracle Solaris 10 9/10 OS. You mightencounter them in earlier releases.

# fmadm restart cpumem-diagnosis

TABLE 3-3 Oracle Solaris OS Issues and Workarounds Fixed in Oracle Solaris 10 9/10

CR ID M3000M4000/M5000


CR 6888928 o o o The IPMP interface fails since probepackets are not sent through thatinterface. Problem occurs withM3000/M4000/M5000/M8000/M900.Seen on servers running the OracleSolaris 10 10/09 OS and IPMP, or anyOracle Solaris release running IPMPwith Patch 141444-09 installed.

Disable probe-based failuredetection. See IPMP Link-basedOnly Failure Detection withSolaris 10 Operating System(OS) (Doc ID 1008064.1)

CR 6668237 o o o After DIMMs are replaced, thecorresponding DIMM faults are notcleared on the domain.

Use the fmadm repairfmri|uuid to record the repair.Then use the fmadm rotatecommand to clear out anyleftover events.

CR 6872501 o o o Cores are not offlined when requestedby the XSCF. This CR affects onlyOracle Solaris 10 5/09 and OracleSolaris 10 10/09 releases.

Use fmdump(1M) with its -voption on the ServiceProcessor to identify the faultycore. Once identified, usepsradm(8) on the domain tooffline the core.


Issues Fixed in Oracle Solaris 10 10/09TABLE 3-4 lists issues that have been fixed in the Oracle Solaris 10 10/09 OS. Youmight encounter them in earlier releases.


CR ID M3000M4000/M5000


CR 6572827 o o o The prtdiag -v command reportsPCI bus types incorrectly. It reports“PCI” for PCI-X leaf devices and“UNKN” for legacy PCI devices.


CR 6724307 o Scheduler decisions are occasionallyunbalanced.Sometimes two threads will be on onecore (causing both to run at about halfspeed) while another core is idle. Formany OpenMP and similar parallelapplications, the applicationperformance is limited by the speed ofthe slowest thread.Uneven scheduling is not common,perhaps 1 in 50 or 1 in 100 decisions.But if there are 128 threads running,then the application might have at leastone uneven schedule event.

Use processor sets to preventuneven threads to coreassignment.

CR 6800734 o o deleteboard hangs in a domain There is no workaround.

CR 6816913 o o The XSCF showdevices commanddisplays the incorrect processor cachesize for fractional processor cachesizes, such as displaying “5MB” whenthe correct display would be “5.5MB.”

Use the prtdiag(1M)command on the domain toreport processor information.

CR 6821108 o o DR and showdevices don’t workafter XSCF reboot.

Reboot the XSCF serviceprocessor twice. Half the SAsare deleted the first time, halfare deleted the second time, sothe second addition succeedsand IPsec communication isreestablished.

CR 6827340 o o o DR and Memory patrol might fail dueto SCF command error.





CR ID M3000M4000/M5000


CR 6588555 o o Resetting the XSCF during a DRoperation on permanent memorymight cause domain panic.

Do not start an XSCF reset while a DRoperation is underway. Wait for the DRoperation to complete before startingthe reset.

CR 6623226 o o o The Oracle Solaris commandlockstat(1M) or the dtracelockstat provider might cause asystem panic.

Do not use the Oracle Solarislockstat(1M) command or the dtracelockstat provider.

CR 6680733 o o o Sun Quad-port Gigabit EthernetAdapter UTP (QGC) & Sun Dual 10GigE Fiber XFP Low ProfileAdapter (XGF) NICs might panicunder high load conditions.

If possible, use the card in x8 slot.Otherise, there is no workaround.

CR 6689757 o o o Sun Dual 10 GigE Fiber XFP LowProfile adapter (XGF) with a singleor improperly installed XFP opticaltransceivers might cause thefollowing error to show on theconsole:The XFP optical transceiveris broken or missing.

Check and make sure that both XFPoptical transceivers are firmly seated inthe housing.Do not mix INTEL and Sun XFP opticaltransceivers in the same adapter.Do NOT plumb a port with theifconfig command if the port doesnot contain an XFP optical transceiveror it contains one but the transceiver isnot in use.

CR 6725885 o cfgadm will display non-existentM3000 system boards (SB1 toSB15).

The cfgadm output for SB1-SB15 can beignored.


Issues Fixed in Oracle Solaris 10 10/08TABLE 3-6 lists issues that have been fixed in the Oracle Solaris 10 10/08 OS. Youmight encounter them in earlier releases.

TABLE 3-6 Oracle Solaris OS Issues and Workarounds Fixed in Oracle Solaris 10 10/08 (1 of 4)

CR ID M3000M4000/M5000


CR 6511374 o o Memory translation warning messagesmight appear during boot if memorybanks were disabled due to excessiveerrors.

After the system is rebooted, thefmadm repair command can beused to prevent a recurrence of theproblem on the next boot.

CR 6533686 o o When XSCF is low on system resources,DR deleteboard or moveboardoperations that relocate permanentmemory might fail with one or more ofthese errors:SCF busyDR parallel copy timeout

This applies only to Quad-XSBconfigured System Boards hostingmultiple domains.

Retry the DR operation at a latertime.

CR 6535018 o In Oracle Solaris domains that includeSPARC64 VII processors, workloadsthat make heavy use of the OracleSolaris kernel might not scale asexpected when you increase the threadcount to a value greater than 256.

For Oracle Solaris domains thatinclude SPARC64 VII processors,limit domains to a maximum of 256threads.

CR 6556742 o o o The system panics when DiskSuitecannot read the metadb during DR.This bug affects the following cards:• SG-XPCIE2FC-QF4, 4-Gigabit PCI-e

Dual-Port Fiber Channel HBA• SG-XPCIE1FC-QF4, 4-Gigabit PCI-e

Single-Port Fiber Channel HBA• SG-XPCI2FC-QF4, 4-Gigabit PCI-X

Dual-Port Fiber Channel HBA• SG-XPCI1FC-QF4, 4-Gigabit PCI-X

Single-Port Fiber Channel HBA

Panic can be avoided when aduplicated copy of the metadb isaccessible via another Host BusAdaptor.


CR 6589833 o o The DR addboard command mightcause a system hang if you are adding aSun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCI-EHBA card (SG-XPCIE2FC-QF4) at thesame time that an SAP process isattempting to access storage devicesattached to this card. The chance of asystem hang is increased if thefollowing cards are used for heavynetwork traffic:• X4447A-Z, PCI-e Quad-port Gigabit

Ethernet Adapter UTP• X1027A-Z1, PCI-e Dual 10 Gigabit

Ethernet Fiber XFP Low profileAdapter


CR 6608404 o o Hot-plug of the X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP cardin slot 1 might cause other networkdevices to fail.

To avoid the defect, do not installthis card in slot 1.

CR 6614737 o o The DR deleteboard(8) andmoveboard(8) operations might hang ifany of the following conditions exist:A DIMM has been degraded.The domain contains system boardswith different memory size.

Avoid performing DR operations ifany of the following conditionsexist:• Degraded memory – To determine

whether the system containsdegraded memory, use the XSCFcommand showstatus.

• Differing memory sizes – Todetermine whether the domaincontains system boards withdifferent memory sizes, displaythe list of memory sizes usingthe XSCF commandshowdevices or the prtdiagcommand on the domain.

If a DR command hangs, reboot thedomain to recover.


CR ID M3000M4000/M5000



CR 6619224 o For Oracle Solaris domains that includeSPARC64 VII processors, a singledomain of 256 threads or more mighthang for an extended period of timeunder certain unusual situations. Uponrecovery, the uptime command willshow extremely high load averages.

For Oracle Solaris domains thatinclude SPARC64 VII processors,do not exceed a domain size of 256virtual processors in a single OracleSolaris domain. This means amaximum of 32 CPUs in a singledomain configuration (maximumconfiguration for an M8000 server).

CR 6632549 o o fmd service on domain might fail togo into maintenance mode after DRoperations.

Issue the following command onthe domain:# svcadm clear fmd

CR 6660197 o o DR might cause the domain to hang ifeither of the following conditions exist:• A domain contains 256 or more

CPUs.• Memory error occurred and the

DIMM has been degraded.

1. Set the following parameter inthe system specification file(/etc/system):

set drmach:drmach_disable_mcopy=1

2. Reboot the domain.

CR 6679370 o o The following message might be outputon the console during system boot,addition of the External I/O ExpansionUnit using hotplug, or an FMEMAoperation by DR:SUNW-MSG-ID: SUN4-8000-75,TYPE: Fault, VER: 1, SEVERITY:Critical ... DESC:

A problem was detected in thePCIExpress subsystem.

Add the following to the/etc/system file, then reboot thedomain.set pcie_expected_ce_mask= 0x2001

CR 6720261 o o o If your domain is running Oracle Solaris10 5/08 OS, the system mightpanic/trap during normal operation.

Set the following parameter in thesystem specification file(/etc/system):set heaplp_use_stlb=0

Then reboot the domain.


CR ID M3000M4000/M5000



CR 6737039 o WAN boot of M3000 servers failsintermittently with a panic early in theboot process. Sample output:ERROR: Last Trap: Fast DataAccess MMU Miss%TL:1 %TT:68 %TPC:13aacc%TnPC:13aad0 %TSTATE:1605%PSTATE:16 ( IE:1 PRIV:1 PEF:1 )DSFSR:4280804b ( FV:1 OW:1 PR:1E:1 TM:1 ASI:80 NC:1 BERR:1 )DSFAR:fda6f000DSFPAR:401020827000 D-TAG:6365206f66206000

Power off and power on thechassis, then retry the operation.


CR ID M3000M4000/M5000



ed

in

00f



CR ID M3000M4000/M5000


CR 5076574 o A PCIe error can lead to an invalid faultdiagnosis on a large M8000/M9000domain.

Create a file /etc/fm/fmd/fmd.confcontaining the following lines:setprop client.buflim 40msetprop client.memlim 40m

CR 6348554 o o Using the cfgadm -c disconnectcommand on the following cards mighthang the command:• SG-XPCIE2FC-QF – 4Sun StorageTek

Enterprise Class 4-Gigabit Dual-PortFiber Channel PCI-E HBA

• SG-XPCIE1FC-QF4 – Sun StorageTekEnterprise Class 4-Gigabit Single-PortFiber Channel PCI-E HBA

• SG-XPCI2FC-QF4 – Sun StorageTekEnterprise Class 4-Gigabit Dual-PortFiber Channel PCI-X HBA

• SG-XPCI1FC-QF4 – Sun StorageTekEnterprise Class 4-Gigabit Single-PortFiber Channel PCI-X HBA

Do not perform cfgadm -cdisconnect operation on the affectcards.

CR 6402328 o If more than six IOUA (Base I/O Card)cards are used in a single domain, apanic might occur under high I/Ostress.

Limit the maximum number of IOUAsa single domain to 6.

CR 6472153 o o If you create a Oracle Solaris Flasharchive on a sun4u server other than anM4000/M5000/M8000/M9000 server,then install it on one of these servers,the console’s TTY flags will not be setcorrectly. This can cause the console tolose characters during stress.

Just after installing Oracle Solaris OSfrom a Oracle Solaris Flash archive,telnet into the M4000/M5000/M8000/M9000 server to reset theconsole’s TTY flags as follows:# sttydefs -r console# sttydefs -a console -i "96hupcl opost onlcr crtscts" -"9600"

This procedure is required only once.

CR 6505921 o Correctable error on the system PCIebus controller generates an invalid fault.

Create a file /etc/fm/fmd/fmd.confcontaining the following lines;setprop client.buflim 40m

setprop client.memlim 40m


CIit

CI.

e/

:,

n

CR 6522433 o o The incorrect motherboard might beidentified by fmdump for CPU faultsafter reboot.

Check system status on XSCF.

CR 6527811 o o The showhardconf(8) command onthe XSCF cannot display PCI cardinformation that is installed in theExternal I/O Expansion Unit, if theExternal I/O Expansion Unit isconfigured using PCI hot-plug.

There is no workaround. When each Pcard in the External I/O Expansion Unis configured using PCI hot-plug, the Pcard information is displayed correctly

CR 6536564 o o showlogs(8) and showstatus(8)command might report wrong I/Ocomponent.

To avoid this problem, issue thefollowing commands on the domain.# cd/usr/platform/SUNW,SPARCEnterprislib/fm/topo/plugins# mv ioboard.so ioboard.so.orig# svcadm restart fmd

Contact a service engineer if thefollowing messages are displayed:SUNW-MSG-ID: SUNOS-8000-1L, TYPEDefect, VER: 1, SEVERITY: MinorEVENT-TIME: Sun May 6 18:22:24PDT 2007 PLATFORM: SUNW,SPARC-Enterprise, CSN: BE80601007,HOSTNAME: sparc

CR 6545143 o o There is a low probability that a systempanic can occur during trap processingof a TLB miss for a user stack address.The problem can occur if the user stackis unmapped concurrently with the userprocess executing a flush windows trap(ta 3). The panic message will containthe following string:bad kernel MMU trap at TL 2


CR 6545685 o o If the system has detected correctablememory errors (CE) at power-on self-test (POST), the domains mightincorrectly degrade 4 or 8 DIMMs.

Increase the memory patrol timeoutvalues used via the following setting i/etc/system and reboot the system:set mc-opl:mc_max_rewrite_loop =20000


CR ID M3000M4000/M5000



CR 6546188 o o The system panics when running hot-plug (cfgadm) and DR operations(addboard and deleteboard) onthe following cards:• X4447A-Z, PCI-e Quad-port Gigabit




CR 6551356 o o The system panics when running hot-plug (cfgadm) to configure apreviously unconfigured card. Themessage “WARNING: PCI ExpansionROM is not accessible” will be seen onthe console shortly before the systempanic. The following cards are affectedby this defect:• X4447A-Z, PCI-e Quad-port Gigabit



Use cfgadm -c disconnect tocompletely remove the card. Afterwaiting at least 10 seconds, the cardmight be configured back into thedomain using the cfgadm -cconfigure command.

CR 6559504 o o Messages of the form nxge: NOTICE:nxge_ipp_eccue_valid_check:rd_ptr = nnn wr_ptr = nnn willbe observed on the console with thefollowing cards:• X4447A-Z, PCI-e Quad-port Gigabit



These messages can be safely ignored.

CR 6563785 o o Hot-plug operation with the followingcards might fail if a card is disconnectedand then immediately reconnected:• SG-XPCIE2SCSIU320Z – Sun

StorageTek PCI-E Dual-Port Ultra320SCSI HBA

• SGXPCI2SCSILM320-Z – SunStorageTek PCI Dual-Port Ultra 320SCSI HBA

After disconnecting a card, wait for afew seconds before re-connecting.


CR ID M3000M4000/M5000



R

em

em

n

CR 6564934 o o Performing a DR deleteboardoperation on a board which includesPermanent Memory when using thefollowing network cards results inbroken connections:• X4447A-Z, PCI-e Quad-port Gigabit



Reconfigure the affected networkinterfaces after the completion of the Doperation. For basic networkconfiguration procedures, refer to theifconfig man page for moreinformation.

CR 6568417 o o After a successful CPU DRdeleteboard operation, the systempanics when the following networkinterfaces are in use:• X4447A-Z, PCI-e Quad-port Gigabit

Ethernet Adapter UTP• X1027A-Z1, PCI-e Dual 10-Gigabit


Add the following line to /etc/systand reboot the system:set ip:ip_soft_rings_cnt=0

CR 6571370 o o Use of the following cards have beenobserved to cause data corruption instress test under laboratory conditions:• X4447A-Z, PCI-e Quad-port Gigabit

Ethernet Adapter UTP• X1027A-Z1, PCI-e Dual 10-Gigabit


Add the following line in /etc/systand reboot the system:set nxge:nxge_rx_threshold_hi=0

CR 6584984 o The busstat(1M) command with -woption might cause M8000/M9000server domains to reboot.

There is no workaround. Do not usebusstat(1M) command with -w optioon pcmu_p.

CR 6589546 o o prtdiag does not show all IO devicesof the following cards:• SG-XPCIE2FC-EM4 Sun StorageTek

Enterprise Class 4-Gigabit Dual-PortFiber Channel PCI-E HBA

• SG-XPCIE1FC-EM4 Sun StorageTekEnterprise Class 4-Gigabit Single-PortFiber Channel PCI-E HBA

Use prtdiag -v for full output.


CR ID M3000M4000/M5000



estage


CR 6663570 o o DR operations involving the lowestnumbered CPU might cause the domainto panic.

Do not use DR to remove the systemboard that hosts the CPU with the lowCPU ID. Use the Oracle Solaris prtdicommand to identify the CPU with thlowest CPU ID.


CR ID M3000M4000/M5000


CR 6303418 o M9000 server with a single domain and11 or more fully populated systemboards might hang under heavy stress.

Do not exceed 170 CPU threads.Limit the number of CPU threads toone per CPU core by using the OracleSolaris psradm command to disablethe excess CPU threads. For example,disable all odd-numbered CPUthreads.

CR 6416224 o o System performance can degrade usinga single NIC card with more than 5,000connections.

Use multiple NIC cards to splitnetwork connections.

CR 6441349 o o I/O error can hang the system. There is no workaround.

CR 6485555 o o On-board Gigabit Ethernet NVRAMcorruption could occur due to a racecondition. The window of opportunityfor this race condition is very small.



CR ID M3000M4000/M5000



CR 6496337 o o The “cpumem-diagnosis” module mightfail to load after uncorrectable error(UE) panic. Systems will functioncorrectly but events normallyautomatically diagnosed by FMA usingthis module will require manualdiagnosis.Example:SUNW-MSG-ID: FMD-8000-2K, TYPE:Defect, VER: 1, SEVERITY: MinorEVENT-TIME: Thu Feb 15 15:46:57JST 2007 PLATFORM: SUNW,SPARC-Enterprise, CSN: BE80601007,HOSTNAME: col2-ffem7-d0

If the problem has already occurred:1. Remove the cpumemdiagnosis

file:# rm /var/fm/fmd/ckpt \/cpumemdiagnosis/cpumem-diagnosis

2. Restart fmd service:# svcadm restart fmd

To avoid this problem in advance, addthe following line in the file:/lib/svc/method/svc-dumpadm:

# savedev=nonerm -f/var/fm/fmd/ckpt/cpumemdiagnosis \/cpumem-diagnosis#

CR 6495303 o o The use of a PCIe Dual-Port Ultra320SCSI controller card (SG-(X)PCIE2SCSIU320Z) in IOU Slot 1 on aSPARC Enterprise M4000/M5000 servermight result in a system panic.

Do not use this card in IOU Slot 1.

CR 6498283 o o Using the DR deleteboardcommand while psradm operations arerunning on a domain might cause asystem panic.


CR 6499304 o o Unexpected message is displayed onconsole and CPU isn’t offlined whennumerous correctable errors (CEs)occur.Example:SUNW-MSG-ID: FMD-8000-11, TYPE:Defect, VER: 1, SEVERITY: MinorEVENT-TIME: Fri Feb 2 18:31:07JST 2007, PLATFORM: SPARC-Enterprise, CSN: BE80601035,HOSTNAME: FF2-35-0

Check CPU status on XSCF.


CR ID M3000M4000/M5000



CR 6502204 o o Unexpected error messages might bedisplayed on console on booting afterCPU UE panic.Example:SUNW-MSG-ID: FMD-8000-11, TYPE:Defect, VER: 1, SEVERITY: MinorEVENT-TIME: Tue Jan 9 20:45:08JST 2007 PLATFORM: SUNW,SPARC-Enterprise, CSN: 2030636002,HOSTNAME: P2-DC1- 16-d0

If you see unexpected messages, usethe showdomainstatus(8) commandto check system status on XSCF.

CR 650275 o o Inserted or removed hot-plugged PCIcard might not output notificationmessage.


CR 6508432 o o A large number of spurious PCIecorrectable errors can be recorded in theFMA error log.

To mask these errors, add thefollowing entry to /etc/system andreboot the system:set pcie:pcie_aer_ce_mask =0x2001

CR 6508434 o The domain might panic when anadditional PCI-X card is installed or aPCI-X card is replaced using PCI hot-plug.

Do not insert a different type of PCI-Xcard on the same PCI slot by usingPCI hot-plug.

CR 6510861 o o When using the PCIe Dual-PortUltra320 SCSI controller card (SG-(X)PCIE2SCSIU320Z), a PCIe correctableerror causes a Oracle Solaris panic.

Add the following entry to/etc/system to prevent theproblem:set pcie:pcie_aer_ce_mask =0x31c1

CR 6520990 o o When a domain reboots, SCF might notbe able to service other domains thatshare the same physical board. DRoperation can exceed the defaulttimeout period and panic can occur.

Increase the DR timeout period bysetting the following statement in/etc/system and reboot yoursystem:set drmach:fmem_timeout = 30

CR 6527781 o The cfgadm command fails whilemoving the DVD/DAT drive betweentwo domains.

There is no workaround. Toreconfigure DVD/Tape drive, executereboot -r from the domainexhibiting the problem.

CR 6530178 o o DR addboard command can hang.Once the problem is observed, furtherDR operations are blocked. Recoveryrequires reboot of the domain.


CR 6530288 o o cfgadm(1M) command might notcorrectly show Ap_Id format.



CR ID M3000M4000/M5000



CR 6534471 o o Systems might panic/trap duringnormal operation.

If a patch is not available, disable thekernel large page sTLB programming.In the file /etc/system, change theheaplp_use_stlb variable to 0:set heaplp_use_stlb=0

CR 6535564 o o PCI hot-plug to PCI slot #0, #1 orExternal I/O Expansion Unit might failon XSB added by DR.

Use DR instead of PCI hot plug ifneed to add or remove PCI card onthe XSB.

CR 6539084 o o There is a low probability of a domainpanic during reboot when the Sun QuadGbE UTP x8 PCIe (X4447A-Z) card ispresent in a domain.


CR 6539909 o o Do not use the following I/O cards fornetwork access when you are using theboot net install command toinstall the Oracle Solaris OS:• X4447A-Z/X4447A-Z, PCIe Quad-

port Gigabit Ethernet Adapter UTP• X1027A-Z/X1027A-Z, PCIe Dual 10-

Gigabit Ethernet Fiber XFP

Use an alternative type of networkcard or onboard network device toinstall the Oracle Solaris OS via thenetwork.

CR 6542632 o o Memory leak in PCIe module if driverattach fails.



CR ID M3000M4000/M5000



Software Documentation UpdatesThis section contains late-breaking information that became known after thedocumentation set was published or was very recently added.

Note – Online man pages generally are updated more frequently than the SPARCEnterprise M3000/M4000/M5000/ M8000/M9000 Servers XSCF Reference Manual. In case of aconflict, check the Last Modified date at the bottom of the man page.

TABLE 3-9 Changes to Man Pages

Man Page Change

addcodactivation(8),setcod(8), showcod(8),and showcodusage(8)

These man pages still describe the COD headroom feature, which isno longer supported. See “Capacity on Demand (COD)” on page 11.

showenvironment(8) The XCP 1100 firmware release introduced support of theshowenvironment air command on M4000/M5000 servers. Youcan now use it on any M-Series server.

setpasswordpolicy(8) A more complete description of the -r remember option is:Sets the number of passwords remembered in password history.Valid values are integers of 1 - 10. The initial setting is 3. A zerovalue is not supported and prevents further password modificationsby the user.

TABLE 3-10 Changes to Manuals

Document Title Change

SPARC EnterpriseM4000/M5000/M8000/M9000Servers Capacity on Demand(COD) User’s Guide

This document does not yet include instructions about settingheadroom to zero before upgrading to XCP 1101 firmware. See“Capacity on Demand (COD)” on page 11.


CHAPTER 4

Information About Hardware

This chapter describes issues about M3000/M4000/M5000/M8000/M9000 serverhardware as related to this XCP release.

See also “Compatible Hardware, Firmware, and Software Matrix” on page 2.

Important Notes, Issues andWorkarounds – All M-Series Servers

Booting From a WAN Boot ServerThe WAN boot installation method enables you to boot and install software over awide area network (WAN) by using HTTP. To support booting the M4000/M5000servers from a WAN boot server, you must have the appropriate wanbootexecutable installed and OpenBoot version 4.24.10 or above to provide the neededhardware support.

For information about WAN boot servers, refer to the Solaris 10 Installation Guide:Network-Based Installations for the version of Oracle Solaris 10 OS that you are using.You can find Oracle Solaris 10 OS documentation here:


If you do not upgrade the wanboot executable, the server will panic, with messagessimilar to the following:

35


Booting Multiple Systems From a Single J4200JBOD Storage ArraySun Storage J4200 SAS JBOD arrays have six general-purpose SAS connectors. WithFW version 3A32 or higher, each of them can be connected to separate SAS initiators,therefore up to six systems can be connected to the array. Each system can use adifferent disk on the array as its boot device. J4200 arrays have 12 disks, so each bootdevice can be mirrored for higher reliability. J4200 arrays can be configured intomultiple zones to provide a more secure environment.

For related information, see Sun StorageTek Common Array Manager Softwaredocumentation, at:http://www.oracle.com/technetwork/documentation/disk-device-194280.html#hic

See especially:

■ Sun StorageTek Common Array Manager Software Release Notes 6.4.1

■ Sun StorageTek Common Array Manager User Guide for Open Systems

Notes on the Use of USB MemoryTo execute the dumpconfig(8), restoreconfig(8) or snapshot(8) command,if you specify USB memory as the destination to store data, prepare the USBmemory as a medium in advance.

The data stored will include the information about the system. To use USB memory,you need to pay attention to the management of the USB memory in which the datais stored, from the data security viewpoint.

Proper operation and connectivity to the XSCF of every USB memory currently onthe market cannot be guaranteed. Depending on the USB memory in use, defectssuch as the XSCF firmware error or reset might occur. In case such defects occurred,stop the use of USB memory immediately.

To connect the USB memory to the USB port for the XSCF, connect the USB memorydirectly to the USB port. If connected through the USB hub or USB extension, itmight cause errors.

krtld: load_exec: fail to expand cpu/$CPUkrtld: error during initial load/link phasepanic - boot: exitto64 returned from client program


http://www.oracle.com/technetwork/documentation/disk-device-194280.html#hic

Hardware Functionality Issues and LimitationsThis section describes known issues in this release.

■ When you use the external power control interface of the external powercontroller, the following notification signals are not supported:

■ The OS panic or the server hardware error signal (*CPUN/RTNU).

■ The server hardware error signal (power fail, temperature error, and fan error)(*ALARM).

■ For information about I/O options and storage, such as the number of cardssupported in a domain, see the Sun Cross Platform IO Support page:

http://wikis.sun.com/display/PlatformIoSupport/Home/

Important Notes, Issues andWorkarounds – M3000 Servers Only

Patches for Emulex PCI Express (PCIe) CardsThe following Emulex cards require drivers supplied in patch 120222-27:

■ XSEFC402AF Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber ChannelPCIe HBA

■ XSEFC401AF Sun StorageTek Enterprise Class 4-Gigabit Single-Port FiberChannel PCIeHBA


■ For power-on after power-off, wait at least 30 seconds before turning the systempower back on by using the main line switch or the circuit breakers on thedistribution panel.

■ For servers that have the B-type plug, confirm that a 15A overcurrent protectiondevice is available outside the server. If one is not available, prepare an external15A 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 oneswith two parallel blades, such as the NEMA L6-30, L6-20, L6-15, and L5-15.

Chapter 4 Information About Hardware 37

http://wikis.sun.com/display/PlatformIoSupport/Home/

■ Connecting a SAS device containing multiple SAS targets to the onboard externalSAS interface is not supported. Instead, use a Sun StorageTek Host Bus Adaptor(SG-XPCIE8SAS-E-Z).

Important Notes, Issues andWorkarounds – M4000/M5000 andM8000/M9000 Servers Only

DVD Drives and cfgadm

The Oracle Solaris cfgadm(1M) command does not always unconfigure a DVD drivefrom a domain on SPARC Enterprise M8000/M9000 servers.

Disable the Volume Management Daemon (vold) before unconfiguring a DVD drivewith the cfgadm(1M) command. To disable vold, stop the daemon by issuing thecommand /etc/init.d/volmgt stop. After the device has been removed orinserted, restart the daemon by issuing the command /etc/init.d/volmgtstart.

F20 PCIe CardsThis release supports Sun Flash Accelerator F20 PCIe cards on M4000/M5000 andM8000/M9000 servers. These cards are not supported on M3000 servers.

On M4000/M5000 servers, configure the F20 card only in slots 1 and 3. Thisrestriction does not apply to M8000/M9000 servers.

For more information see the F20 documentation:


Note – The External I/O Expansion Unit does not support F20 cards.



Sun Crypto Accelerator 6000 CardsIf you are not using the correct version of the Sun Crypto Accelerator (SCA) 6000card driver, hot-plug operations on SCA 6000 cards can cause SPARC EnterpriseM8000/M9000 servers to panic or hang. Version 1.1 of the SCA6000 driver andfirmware supports hot-plug operations after the required bootstrap firmwareupgrade has been performed. Version 1.0 of the SCA6000 driver does not supporthot-plug and should not be used.

U320 PCIe SCSI CardThe U320 PCIe SCSI card, part number 375-3357-01/02, is not supported in PCIcassettes for SPARC Enterprise M8000/M9000 servers. Customers must use partnumber 375-3357-03 at a minimum.

Patches for QLogic PCIe CardsThe following QLogic cards require drivers supplied in patch 125166-10:

■ Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCIe HBA(part SG-XPCIE2FC-QF4)

■ Sun StorageTek Enterprise Class 4-Gigabit Single-Port Fiber Channel PCIe HBA(part SG-XPCIE1FC-QF4)

Patches for Emulex PCI Express (PCIe) CardsThe following Emulex cards require drivers supplied in patch 120222-27:

■ Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCIe HBA(part SG-XPCIE2FC-EM4)

■ Sun StorageTek Enterprise Class 4-Gigabit Single-Port Fiber Channel PCIe HBA(part SG-XPCIE1FC-EM4)



■ The use of the External I/O Expansion Unit to connect the host server to anexternal boot disk drive is not supported.

■ Do not use the CD-RW/DVD-RW drive unit and the TAPE drive unit at the sametime.

■ Power cables are not redundant on single power feed servers without the dualpower feed option. All power cables must be connected and powered on at alltimes.

■ DR operations on an M8000/M9000 server might fail with a misleading messageregarding the board being unavailable for DR after the addfru(8) orreplacefru(8) command has been used for active replacement. This happenswhen the active replacement is done without the diagnostic test in themaintenance menu. Execute the diagnosis in the maintenance menu of theaddfru(8) or replacefru(8) command to avoid this problem. To recover,execute the testsb(8) command or delete the CPU/memory board unit using thedeletefru(8) command and then retry the addfru(8) command.

■ Contact your sales representative for tape drive unit options.

■ The M4000/M5000 servers are cold-service machines. Hot-swapping of the CPUmodule (CPUM), memory board (MEMB), I/O unit (IOU), or XSCF unit is notsupported.


Hardware Documentation Updates forthe M3000 ServerThis section contains late-breaking hardware information that became known afterthe documentation set was published and corrections in the M3000 server hardwaredocumentation.

All M3000 hardware documents were up-to-date as of this release.

Hardware Documentation Updates forthe M4000/M5000 ServersThis section contains late-breaking hardware information that became known afterthe documentation set was published and corrections in the M4000/M5000 servershardware documentation.

All M4000/M5000 hardware documents were up-to-date as of this release.

Hardware Documentation Updates forthe M8000/M9000 ServersThis section contains late-breaking hardware information that became known afterthe documentation set was published and corrections in the M8000/M9000 servershardware documentation.

All M8000/M9000 hardware documents were up-to-date as of this release.


SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers ... · Contents vii Important Notes, Issues...

Documents

Transcript of SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers ... · Contents vii Important Notes, Issues...