Fujitsu M9000, M4000, M5000, M3000, M8000 User Manual

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

Product Notes for XCP Version 1124

Manual Code: C120-0066-01EN August 2018, Revision A

Copyright © 2018, Fujitsu Limited. All rights reserved. Oracle and/or its affiliates 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 descr ibed 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 C ONDITIONS, 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 © 2018, Fujitsu Limited. Tous droits réservés. Oracle et/ou ses sociétés affiliées ont 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 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 correspond re à des marques appartenant à d’autres propriétaires.

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.

Preface xi

1. Software Requirements 1

XCP, Oracle Solaris OS and Required Patches 1

Obtaining XCP and Oracle Solaris Patches 4

Web Browser 4

Existing XCP Firmware Versions and Support Information 5

2. XCP 1124 and XCP 1124-related Information 7

What’s New in XCP 1124 7

Notes and Limitations 8

Limitations for SPARC64 VII+ and SPARC64 VII Processors 8

Notes on Secure Socket Layer (SSL) 3.0 8

Notes on SSH 8

Notes on Active Directory 8

Notes on LDAP/SSL 9

Notes on Power Consumption Monitoring Function (M3000 Server) 9

Notes on Airflow Indicator 9

Notes on NTP Server 9

Notes on the NTP Server Referring to the Local Clock 10

Notes on Timezones 11

Notes on XSCF Web 11

Limitations on Audit 13

Miscellaneous Notes and Limitations 13

XCP 1124 Issues and Workarounds 15

Updating to XCP 1124 16

Importing the XCP File 16

Updating from a Version Earlier Than XCP 1050

(M4000/M5000/M8000/M9000 Servers) 16

Updating from a Version Earlier Than XCP 1070

(M8000/M9000 Servers) 16

3. Information About Software 19

Notes and Limitations 19

Notes on RCI Function 19

Notes on Remote Maintenance 20

Before Setting the Remote Maintenance Service 20

The Timezone Setting for REMCS Agent Function 20

XCP Issues and Workarounds 20

Known Issues and Workarounds in XCP 1124 21

XCP Issues Fixed in XCP 1124 25

XCP Issues Fixed in XCP 1123 25

XCP Issues Fixed in XCP 1122 26

XCP Issues Fixed in XCP 1121 26

XCP Issues Fixed in Releases Earlier Than XCP 1121 27

Oracle Solaris OS Issues and Workarounds 59

Oracle Solaris Issues and Workarounds for All Supported Releases 60

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/11 66

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 9/10 67

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/09 68

vi SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/09 70

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/08 72

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/08 76

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/07 81

Software Documentation Updates 87

Updates of the SPARC Enterprise M3000/M4000/M5000/M8000/M9000

Servers XSCF User’s Guide 94

Configuring XSCF Routing 94

Updates of the SPARC Enterprise M3000/M4000/M5000/M8000/M9000

Servers XSCF Reference Manual 96

forcerebootxscf(8) Command 96

Miscellaneous Information 98

Identifying Degraded Memory in a System 98

Identifying Different Memory Sizes in a System Board 98

▼ Using the showdevices Command 98

▼ Using the prtdiag Command to Identify Memory Size 99

Identifying Permanent Memory in a Target Board 100

4. Information About Hardware of M3000 Server 101

Notes and Limitations 101

Notes on Hardware RAID 101

Notes on Using the Hardware RAID 101

Notes on Building or Deleting the Hardware RAID 102

Notes on Operating the Hardware RAID 102

Notes on raidctl(1M) Command 102

Notes on DVD Drive and Discs 103

Notes on the Use of USB Memory 103

Power Control and Operator Panel Mode Switch 103

Limitation for 1027A-Z/X1027A-Z 104

Limitation for 4447A-Z/X4447A-Z 104

Contents vii

Patches for Emulex PCI Express (PCIe) Adapters 104

Hardware RAID Function 105

Requirements for Hardware RAID Support 105

Hardware Documentation Updates 105

Updates of SPARC Enterprise M3000 Server Service Manual 107

Removing the Motherboard Unit 107

5. Information About Hardware of M4000/M5000 Servers 109

Notes and Limitations 109

Notes on Server Installation 109

Notes on DVD Drive and Discs 110

Notes on the Use of USB Memory 110

Power Control and Operator Panel Mode Switch 110

Notes on Air Filter 111

Limitation for 1027A-Z/X1027A-Z 111

Limitation for 4447A-Z/X4447A-Z 111

Patches for Emulex PCI Express (PCIe) Adapters 112

Hardware Issues and Workarounds 112

Sun Crypto Accelerator 6000 112

Hardware Documentation Updates 112

6. Information About Hardware of M8000/M9000 Servers 115

Notes and Limitations 115

Notes on Using a RAID-capable IOUA 115

Notes on Hardware RAID 116

Notes on Using the Hardware RAID 116

Notes on Building or Deleting the Hardware RAID 116

Notes on Operating the Hardware RAID 116

Notes on raidctl(1M) Command 117

viii SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

Notes on DVD Drive and Discs 117

Notes on the Use of USB Memory 117

Power Control and Operator Panel Mode Switch 118

Limitation for 1027A-Z/X1027A-Z 118

Limitation for 4447A-Z/X4447A-Z 119

Patches for Emulex PCI Express (PCIe) Adapters 119

Hardware Issues and Workarounds 119

DVD Drives and cfgadm 119

Sun Crypto Accelerator 6000 119

Hardware RAID Function 120

Requirements for Hardware RAID Support 120

Hardware Documentation Updates 121

Updates of SPARC Enterprise M8000/M9000 Servers Site Planning Guide 122

M9000 Servers Installation Area 123

Updates of SPARC Enterprise M8000/M9000 Servers Service Manual 126

I/O Unit (IOU) Mounting Locations 126

Miscellaneous Information 127

Cabinet Stabilization Measures 127

Method of Securing the Cabinet to the Floor Surface 128

Contents ix

x SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

Preface

These product notes contain important and late-breaking information about the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 servers. It covers hardware, software, firmware, and documentation, covering the latest XSCF Control Package (XCP) release.

Note – The M3000/M4000/M5000/M8000/M9000 servers are

based on high-performance and highly-reliable SPARC64 VII+ or SPARC64 VII processors.

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

Note – Once an XCP version newer than the XCP version supported by this manual

is released, only the manuals related to the new XCP version are subsequently updated. You must therefore check the manuals for the latest XCP version in addition to those related to the XCP version you are using.

Global Site

http://www.fujitsu.com/global/products/computing/servers/unix/sp arc-enterprise/downloads/manuals/

Japanese Site

http://www.fujitsu.com/jp/products/computing/servers/unix/sparcenterprise/downloads/manual/

This section includes:

■ “Audience” on page xii

■ “How to Use This Document” on page xii

■ “Related Documentation” on page xiii

■ “Documentation Feedback” on page xvi

Audience

This notes is written for experienced system administrators with working knowledge of computer networks and advanced knowledge of the Oracle Solaris Operating System (Oracle Solaris OS).

How to Use This Document

This document is intended for all models of the M3000/M4000/M5000/M8000/M9000 servers. Read the appropriate related items depending on your server, as shown in the table below.

Chapter of This Document M3000 M4000/M5000 M8000/M9000

Chapter 1 Software Requirements OOO

Chapter 2 XCP 1124 and XCP 1124-related Information OOO

Chapter 3 Information About Software OOO

Chapter 4 Information About Hardware of M3000 Server O

Chapter 5 Information About Hardware of M4000/M5000 Servers

Chapter 6 Information About Hardware of M8000/M9000 Servers

Chapter 1, Chapter 2, and Chapter 3 provide the information related to firmware and software for all servers. These chapters contain the descriptions which are specific to particular models, too. The relevant server name is clearly stated.

xii SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

Chapter 4, Chapter 5, and Chapter 6 provide the information related to hardware. Each chapter describes each model. The information which is common in all models is provided in all of these chapters. As a result, the description may be overlapped when you retrieve the hardware-related information of multiple models.

Documentation Feedback

If you have any comments or requests regarding this document, or if you find any unclear statements in the document, please state your points specifically on the form at the following website:

http://www.fujitsu.com/global/about/resources/contact/

xvi SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

CHAPTER

Software Requirements

This section contains the software requirements of SPARC Enterprise M3000/M4000/M5000/M8000/M9000 (M3000/M4000/M5000/M8000/M9000) servers.

■ “XCP, Oracle Solaris OS and Required Patches” on page 1

■ “Obtaining XCP and Oracle Solaris Patches” on page 4

■ “Web Browser” on page 4

■ “Existing XCP Firmware Versions and Support Information” on page 5

XCP, Oracle Solaris OS and Required Patches

The supported XCP and Oracle Solaris Operating System (Oracle Solaris OS) depends on the processors being installed on the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 servers.

This section lists supported XCP, and Oracle Solaris OS and mandatory patches for the M3000/M4000/M5000/M8000/M9000 servers.

Note – Apply the patches in the following order. For the procedures of CPU

upgrade including the patches, see SPARC Enterprise M8000/M9000 Servers Service Manual.

TAB LE 1 -1 Supported XCP, Oracle Solaris OS, and Required Patches

Server: Processors XCP Oracle Solaris OS Required Patches

M4000/M5000: SPARC64 VII+ 2.66 GHz M8000/M9000: SPARC64 VII+ 3.00 GHz

M4000/M5000: SPARC64 VII 2.53 GHz M8000/M9000: SPARC64 VII 2.88 GHz

M4000/M5000: SPARC64 VII 2.4 GHz M8000/M9000: SPARC64 VII 2.52 GHz

1100 or later • Oracle Solaris 11 11/11

• Oracle Solaris 10 8/11

• Oracle Solaris 10 9/10

• Oracle Solaris 10 10/09

• Oracle Solaris 10 5/09

• Oracle Solaris 10 10/08

• Oracle Solaris 10 5/08

• Oracle Solaris 10 8/07

1090 or later • Oracle Solaris 11 11/11

• Oracle Solaris 10 8/11

• Oracle Solaris 10 9/10

• Oracle Solaris 10 10/09

• Oracle Solaris 10 5/09

• Oracle Solaris 10 10/08

• Oracle Solaris 10 5/08

• Oracle Solaris 10 8/07

1070 or later*• Oracle Solaris 11 11/11

• Oracle Solaris 10 8/11

• Oracle Solaris 10 9/10

• Oracle Solaris 10 10/09

• Oracle Solaris 10 5/09

• Oracle Solaris 10 10/08

• Oracle Solaris 10 5/08

• Oracle Solaris 10 8/07

No patches required No patches required No patches required No patches required All patches contained in

the PTF R10021 or later All patches contained in

The PTF R10021 or later All patches contained in

The PTF R10021 or later

No patches required No patches required No patches required No patches required All patches contained in

the PTF R10021 or later All patches contained in

the PTF R10021 or later

No patches required No patches required No patches required No patches required No patches required No patches required 137137-09 119254-51 or later

125891-01 or later 127755-01 or later 127127-11

2 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 1-1

Server: Processors XCP Oracle Solaris OS Required Patches

M4000/M5000: SPARC64 VI 2.15 GHz M8000/M9000: SPARC64 VI 2.28/2.4

GHz

Supported XCP, Oracle Solaris OS, and Required Patches (Continued)

1040 or later • Oracle Solaris 11 11/11

• Oracle Solaris 10 8/11

• Oracle Solaris 10 9/10

• Oracle Solaris 10 10/09

• Oracle Solaris 10 5/09

• Oracle Solaris 10 10/08

• Oracle Solaris 10 5/08

• Oracle Solaris 10 8/07

• Oracle Solaris 10 11/06

No patches required No patches required No patches required No patches required No patches required No patches required 137137-09

No patches required 118833-36

††

125100-04 or later 120068-03 or later 123839-07 or later 125424-01 or later 125075-01 or later 125670-02 or later

M3000: SPARC64 VII+ 2.86 GHz 1101 or later • Oracle Solaris 11 11/11

• Oracle Solaris 10 8/11

• Oracle Solaris 10 9/10

M3000: SPARC64 VII 2.75 GHz 1091 or later • Oracle Solaris 11 11/11

• Oracle Solaris 10 8/11

• Oracle Solaris 10 9/10

• Oracle Solaris 10 10/09

• Oracle Solaris 10 5/09

No patches required No patches required

‡

No patches required

No patches required No patches required No patches required No patches required All patches contained in

The PTF R10021 or later

• Oracle Solaris 10 10/08

All patches contained in The PTF R10021 or later

M3000: SPARC64 VII 2.52 GHz 1080 or

later*

†

• Oracle Solaris 11 11/11

• Oracle Solaris 10 8/11

• Oracle Solaris 10 9/10

• Oracle Solaris 10 10/09

• Oracle Solaris 10 5/09

• Oracle Solaris 10 10/08

• Oracle Solaris 10 5/08

No patches required No patches required No patches required No patches required No patches required No patches required 119254-59, 138866-01,

137137-09, 138504-04

* If 8GB DIMM is installed on a server, update XCP to XCP 1081 or later. † XCP 1080 is the first XCP release for the M3000 server. ‡ When you install a version earlier than Oracle Solaris 10 9/10, onboard LAN (bge driver) does not work. Be sure to use Oracle Solaris

10 9/10 or later. ** For more information on the PTF, contact a sales representative or a qualified service engineer. ††Apply 118833-36 before 125100-04.

Chapter 1 Software Requirements 3

Note – You cannot boot a domain mounted with the SPARC64 VII processors using

the Oracle Solaris 10 8/07 installation DVD. Use the Oracle Solaris 10 5/08 or later installation DVD to boot a domain mounted with the SPARC64 VII processors.

For additional Oracle Solaris OS information, see “Oracle Solaris OS Issues and

Workarounds” on page 59.

Obtaining XCP and Oracle Solaris Patches

For the information on how to get the latest XCP firmware or the latest patch for Oracle Solaris OS, contact your sales representative.

Web Browser

Many web browsers support the XSCF Web. The browsers in TABLE 1-2 have demonstrated compatibility with the XSCF Web through testing. For other information about XSCF Web, see “Notes on XSCF Web” on page 11.

TABLE 1-2 Tested Web Browser Versions

Web Browser Application Version

Microsoft Internet Explorer 6.0/7.0/8.0/9.0/10.0/11.0

Mozilla Firefox (Windows) 3.6.25/8.0/9.0/ESR10.0/ESR17.0/ESR24.2/

ESR38.4/ESR45/ESR52/ESR60

Mozilla Firefox (Oracle Solaris 10) 2.0/3.5.9/3.6.22

Mozilla Firefox (Oracle Solaris 11) 6.0

4 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

Existing XCP Firmware Versions and Support Information

The following lists the XCP firmware versions that have previously been released for the SPARC Enterprise series, as well as the main support and update information for each version. For the support information for XCP 1113 or earlier, see the "What's New Information" of each version's Product Notes.

TABLE 1-3

XCP Version Main Support Information

XCP 1124 Security fixes.

XCP 1123 • Security fixes.

XCP 1122 Support of SHA256 Web server certificates and TLS 1.2.

XCP 1121 Improvement of XCP firmware defects.

XCP 1120 • Improvement of XCP firmware defects.

XCP 1119 Security fixes.

XCP 1118 Improvement of XCP firmware defects.

XCP 1117 Enhancement of the investigation information at the time of the

XCP 1116 • Support of the -b option of the sethttps(8) command.

XCP 1115 • Support of the forcerebootxscf(8) command

XCP 1114 • Enhancement of the investigation information at the time of occurrence

Previous XCP Version Releases and Support Information

• Improvement of XCP firmware defects.

• Security fixes.

occurrence of "XSCF process down detected"

• Enhancement of the diagnostic function for the "FMEM checksum error" event.

• Enhancement of file check and other XSCF diagnostic information

of an XSCF watchdog timeout *

* If this fix is not applied, the cause of the occurrence of an XSCF watchdog timeout may not be identifiable.

Chapter 1 Software Requirements 5

6 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

CHAPTER

XCP 1124 and XCP 1124-related Information

This section describes the information about XCP 1124 and XCP 1124-related information.

■ “What’s New in XCP 1124” on page 7

■ “Notes and Limitations” on page 8

■ “XCP 1124 Issues and Workarounds” on page 15

■ “Updating to XCP 1124” on page 16

What’s New in XCP 1124

This release offers the following improvement:

■ Security fixes. (RTIF1-180702-001)

Notes and Limitations

This section describes the notes and limitations at the time of this release.

Limitations for SPARC64 VII+ and SPARC64 VII Processors

You must complete the upgrades to the XCP and to Oracle Solaris OS before installing the CPU/memory board unit which is mounted with the SPARC 64 VII+ and SPARC64 VII processors on your server.

Notes on Secure Socket Layer (SSL) 3.0

Due to security reasons, SSL 3.0 cannot be used with XCP 1119 or later. Use Transport Layer Security (TLS) 1.0. Use Transport Layer Security (TLS) 1.0 for XCP 1121 or earlier. Use Transport Layer Security (TLS) 1.2, 1.1, or 1.0 for XCP 1122 or later.

Notes on SSH

Due to security reasons, XCP 1123 and later restrict the use of some algorithms at SSH connection. If the SSH connection to the XSCF fails, consider updating the SSH client and changing the settings.

Notes on Active Directory

■ While Active Directory is enabled, when you attempt to login to XSCF via the

telnet, you might fail to login due to timeout of the query to secondary alternated server or later.

■ If the specified timeout is too brief for the configuration, the login process or

retrieval of user privilege settings could fail. In such case, specify larger value for the timeout and then execute again.

8 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

Notes on LDAP/SSL

If the specified timeout is too brief for the configuration, the login process or retrieval of user privilege settings could fail. In such case, specify larger value for the timeout and try again.

Notes on Power Consumption Monitoring Function (M3000 Server)

■ The amount of power consumption might not be indicated correctly in the MIB

information, in the showenvironment power command output, and on the XSCF Web in the following cases; and you should wait for one minute and check the value again.

■ During the server powering on or powering off, or for a while after the power-

on or power-off complete

■ During the active replacement of power supply unit, or for a while after the

active replacement complete

■ The figures on the power consumption monitoring function represent the

dissipation power from the server. The figures of peripheral devices are not included.

Notes on Airflow Indicator

■ The amount of exhaust air might not be indicated correctly in the MIB

information, in the showenvironment air command output, and on the XSCF Web in the following cases; and you should wait for one minute and check the value again.

■ During the server powering on or powering off, or for a while after the power-

on or power-off complete

■ During the active replacement of power supply unit, or for a while after the

active replacement complete

■ The figures on the airflow indicator represent the volume of air exhausted from

the server. The figures of peripheral devices are not included.

Notes on NTP Server

■ We recommend the domain to use the XSCF Unit as NTP server. In this case, pay

attention to the following points:

■ XSCF must be connected to an external NTP server.

Chapter 2 XCP 1124 and XCP 1124-related Information 9

■ When you connect one or more NTP servers in addition to XSCF, connect the

same NTP server as XSCF is using.

For details on NTP server, contact a service engineer. For details on NTP settings, refer to the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

Notes on the NTP Server Referring to the Local Clock

When the NTP server which XSCF refers to is referring to the server's own system time (local clock), and when the address of "127.127.1.0" is set to that local clock, time synchronization in XSCF might fail.

The address of the XSCF's own local clock is fixed to "127.127.1.0." On the other hand, when the address of the local clock of the NTP server which XSCF refers to is set to "127.127.1.0," the address of the clock source (refid) has the same value as the address of the XSCF's own local clock. An NTP server like this is excluded from the target of XSCF time synchronization.

You can execute the showntp -l command to refer to the address of the NTP server's own clock source which is set in XSCF and the address of the XSCF's own local clock.

XSCF> showntp -l remote refid st t when poll reach delay offset jitter ==============================================================================

192.168.1.2 LOCAL(0) 3 u 10 1024 377 0.000 0.000 0.000 *127.127.1.0 .LOCL. 5 l 28 64 377 0.000 0.000 0.008

Of the two NTP server outputs, the upper (192.168.1.2) indicates the NTP server which is set by using the setntp(8) command. The refid is LOCAL(0), which means that the local clock which has the address of "127.127.1.0" is set to the clock source of this NTP server. On the other hand, the lower indicates the XSCF's own local clock. The address of the XSCF's own local clock is fixed to "127.127.1.0." Due to this, the NTP server (192.168.1.2) is excluded from the target of XSCF time synchronization; which results in the XSCF synchronizes with its own local clock.

With any of the following measures to avoid the trouble, time can be correctly synchronized with the NTP server which is set by using the setntp(8) command.

■ Change the clock source that the NTP server being set in XSCF refers to

Use the showntp -l command and check the clock source of the NTP server which is set in XSCF. An NTP server which indicates the refid of LOCAL(0) in the output is referring to the local clock which has the address of "127.127.1.0," and you should change it to refer to another clock source.

When you change the clock source of an NTP server, make sure in advance that it has no impact on other NTP clients.

10 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

■ Change the address of the local clock of the NTP server

Of the NTP server which XSCF refers to, change the address of the local clock to "127.127.1.1," "127.127.1.2," or "127.127.1.3." Change /etc/inet/ntp.conf of Oracle Solaris OS. To enable the change, restart of the NTP daemon is required.

When you change the address of the local clock of an NTP server, make sure in advance that it has no impact on other NTP clients.

■ Change the stratum value of the NTP server

Of the NTP server which XSCF refers to, change the stratum value to "1." An NTP server which has the stratum value of "1" becomes the most significant clock source and has no refid. Therefore, there is no chance that it will have the same address as the XSCF's own local clock.

When you change the stratum value of an NTP server, make sure in advance that it has no impact on other NTP clients.

■ Change the address of the XSCF's own local clock

By using the setntp -m localaddr=value command, change the address of the XSCF's own local clock. In value, specify the least significant byte of the clock address of the local clock 127.127.1.x for value. A numeric from 0 to 3 can be specified. By specifying either from 1 to 3, the address of an NTP server which is referring to the local clock does not correspond to the address of the XSCF internal local clock anymore, and a server which is referring to the local clock can also be set as the NTP server of XSCF.

Notes on Timezones

The time zones (regions/location names) supported by the XSCF can be changed to support the latest time zone information.

For any previously set time zone that the system can no longer use, the XSCF switches from this unusable time zone to Coordinated Universal Time (UTC) and operates in UTC.

When the set time zone operates in UTC, execute the settimezone -c settz -a command, and check the settable time zones. If the time zone list does not have a set time zone, set a time zone again.

Notes on XSCF Web

■ When you use Mozilla Firefox (Windows version) 45ESR as the Web browser with

XCP 1121 or earlier, the XSCF Web menu may not appear.

Chapter 2 XCP 1124 and XCP 1124-related Information 11

■ Using the XSCF Web function, when you change from a SHA1 Web server

certificate to a SHA256 Web server certificate, re-create the certificate with the sethttps command.

■ Under the Windows 7 with Internet Explorer 8.0, 9.0, or 10.0 environment, XSCF

Web does not support the use through the built-in Administrator account.

■ On Internet Explorer 8.0, when you move the on-screen horizontal frame up or

down to change the frame height and use the [Monitor Msg Show/Hide] button, the screen background color may turn black. In this case, click Refresh on the View menu or press [F5] key to refresh the display, to go back to the screen right after the login.

When you moved the on-screen horizontal frame up or down to change the frame height, do not use the [Monitor Msg Show/Hide] button.

■ M4000/M5000/M8000/M9000 servers:

XSCF Web does not support the External I/O Expansion Unit Manager feature. The M3000 server does not support External I/O Expansion Unit.

■ M3000/M4000/M5000 servers:

Using the XSCF Web, when you import XCP or update the firmware, Session ID error may be displayed on the web browser. And in the Autologout setting, when you specify the timeout period as over 30 minutes, Internal Server Error might be displayed when you perform the firmware update. Please close the current browser and open the new browser to reconnect to XSCF Web.

M8000/M9000 servers: Using the XSCF Web, when you import XCP or update the firmware, Session ID error may be displayed on the web browser. And Internal Server Error might be displayed when you perform the firmware update. Please close the current browser and open the new browser to reconnect to XSCF Web.

■ When you use the XSCF Web under Internet Explorer 6 or 7, or Firefox 2

environment, remove the plug-in if a plug-in such as the search tool installed with the browser, or disable the pop-up blocking.

When you use the XSCF Web under Internet Explorer 8, 9, 10, or 11, or Firefox 3, 6, 8, 9, 10, or 17 environment, disable the pop-up blocking.

■ When you use the XSCF Web under Firefox 3, 6, 8, 9, 10, or 17 environment and

attempt to log in to XSCF, you may be prompted by the browser to save the login ID/password. In this case, do not save the login ID/password. If you save the login ID/password, the stored data can be displayed unexpectedly on the LDAP, SMTP and REMCS web pages.

Use one of two settings described below, to disable the browser's ID/password remember function:

■ Disable the entire browser ID/password remember function.

Click on the [Tools] menu, and select [Preferences]. On the [Security] panel, see [Passwords] and uncheck the [Remember passwords for sites] checkbox.

12 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

■ Designate the XSCF Web address as an exception to the ID/password save

operation. Click on the [Tools] menu, and select [Preferences]. On the [Security] panel, see

[Passwords] and check the [Remember passwords for sites] checkbox. Then, on the dialog for the ID/password saving which appears in the login attempt to XSCF, click the [Never for This Site] button. As a result, the XSCF Web address will be registered in the [Exceptions] list to the ID/password save operation, and the dialog to prompt the ID/password saving will no longer be displayed in the subsequent login attempts to XSCF.

■ When using FireFox ESR 38.4 as the Web browser with XCP 1120 or earlier, the

display of Domain ID and Status in [Menu] - [Domain Operation] - [Domain Power] may appear distorted. If the display is distorted, Power ON and other operations are not available from the above menu. If this problem occurs, use the XSCF shell.

■ The browser layout may appear distorted in Internet Explorer 9, 10, or 11

environment. If this occurs, enable Compatibility View in Internet Explorer.

Limitations on Audit

■ The log file transfer function of the audit log set with the setaudit archive

command and the setaudit disable command is not supported at present.

■ If the policy for writing to an audit record is set to stop temporarily ("suspend"),

degradation due to an error may occur or the XSCF may be reset. In the setaudit(8) command, specify overwriting ("count") by default for the write policy for the audit trail. For details of this issue, see "RTIF1-141209-001."

Miscellaneous Notes and Limitations

Note – M4000/M5000/M8000/M9000 servers:

For dynamic reconfiguration (DR) and hot-plug issues, see “Oracle Solaris OS Issues

and Workarounds” on page 59.

■ The log archive feature by the setarchiving(8) and the showarchiving(8)

commands, and the [Log Archives] menu of XSCF Web is not supported.

■ M4000/M5000/M8000/M9000 servers:

The following functions displaying the power consumption is not supported on M4000/M5000/M8000/M9000 servers.

■ power operand of the showenvironment(8) command

■ XSCF Web

Chapter 2 XCP 1124 and XCP 1124-related Information 13

Note – Invalid values will be displayed by executing the commands or menu.

SNMP Agent Function obtains invalid values of power consumption.

■ M4000/M5000 servers:

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

■ M8000/M9000 servers:

Do not use the internal CD-RW/DVD-RW drive unit and the TAPE drive unit at the same time.

■ When you use the external power control interface of the external power

controller, 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)

■ M8000/M9000 servers:

On the M8000/M9000 servers with XCP 1050 or later, the dual XSCF Unit feature is working. Therefore, you can not downgrade M8000/M9000 servers with XCP 1050 or later to XCP 1040 or XCP 1041, which does not support dual XSCF Unit feature.

■ You cannot use the following user account names, as they are reserved for system

use: root, bin, daemon, adm, operator, nobody, sshd, rpc, rpcuser, ldap, apache, ntp, admin, proxyuser, and default.

■ XSCF-LAN is compliant with auto-negotiation. When you connect XSCF-LAN

and the network device which has been fixed to the full-duplex mode, according to the IEEE 802.3 rule, XSCF-LAN communicates in the half-duplex mode. Due to this, network communication speed may slow down or communication error may occur. Do not fail to set the network device which connects with XSCF-LAN to the auto-negotiation mode.

■ M4000/M5000/M8000/M9000 servers:

While you are performing DR operation to a COD board, do not execute the

addcodactivation(8)/addcodlicense(8)/deletecodactivation(8)/ deletecodlicense(8)/setcod(8) command.

■ At this time the -e, -l, -P options of the snapshot(8) command are not

supported.

■ An XSCF user account user name cannot match an LDAP user name, and an

XSCF user account number (UID) cannot match an LDAP UID number.

■ In case that any failure occurred on a system board and failed to read the FRU

information of system board, XSCF regards the system board as a COD board. The showboards -va command displays the COD status as "y." In this case, replace the failed system board.

14 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

■ An XSCF internal database failure may be detected following the occurrence of an

XSCF storage failure, etc. If so, the same database failure may be detected again in the XSCF, or the XSCF may be degraded. The following describes the operation for this problem in each model and how to restore the XSCF.

■ M3000/M4000/M5000 server:

[XCP 1091 or earlier] If an XSCF internal database failure is detected, the XSCF restarts and continues the operation. Consequently, the same database failure may be detected again. If so, the domain may stop or reboot. <How to restore> After shutting down all domains, replace the motherboard unit (MBU) or the XSCF unit (XSCFU).

[XCP 1092 or later] If an XSCF internal database failure is detected, the XSCF degrades itself so that the same database failure is not detected again. In this case, the domain neither stops nor reboots but instead continues the operation. <How to restore> After shutting down all domains, replace the MBU or XSCFU.

■ M8000/M9000 server:

[XCP 1091 or earlier] If an XSCF internal database failure is detected, the XSCF restarts and continues the operation. Consequently, the same database failure may be detected again. If so, the domain neither stops nor reboots but instead continues the operation. <How to restore> Execute the replacefru command to replace the XSCFU.

[XCP 1092 or later] If an XSCF internal database failure is detected, the XSCF degrades itself so that the same database failure is not detected again. In this case, the domain neither stops nor reboots but instead continues the operation. <How to restore> Execute the replacefru command to replace the XSCFU.

XCP 1124 Issues and Workarounds

For known XCP issues and possible workarounds in XCP 1124, see “Known Issues

and Workarounds in XCP 1124” on page 21. For fixed XCP issues in XCP 1124, see “XCP Issues Fixed in XCP 1123” on page 25.

Chapter 2 XCP 1124 and XCP 1124-related Information 15

Updating to XCP 1124

To update your XCP to XCP 1124, please pay attention to the following points depending on your current XCP version.

You can upgrade to XCP 1124 from XCP version 1050 or later. Refer to the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for instructions.

Importing the XCP File

Once the XCP file is imported, update the firmware immediately. If the XCP file is merely imported, the versions of the XSCF firmware and OpenBoot PROM firmware running on the system remain the old ones. If the CPU/memory board unit or motherboard unit is replaced or the XSCF unit is replaced/switched in this status, the firmware of the unit cannot be matched with the original firmware version, and attempts to replace/switch the unit or start the domain will fail.

Updating from a Version Earlier Than XCP 1050 (M4000/M5000/M8000/M9000 Servers)

■ Updating directly to XCP 1071 or a later version is not possible.

First, update your XCP to any version between XCP 1050 and XCP 1070, and then update to XCP 1071 or later. For the procedure to update to any version between XCP 1050 and XCP 1070, see the Product Notes of the respective version.

■ Delete any accounts named "admin".

Any accounts named admin must be deleted prior to updating to XCP 1050 or later. This account name is reserved in XCP 1050 and later. Use the deleteuser(8) command to delete the account.

Updating from a Version Earlier Than XCP 1070 (M8000/M9000 Servers)

■ After a firmware update from XCP 1061 or earlier to XCP 1070 or XCP 1071, both

the active and standby XSCFs enter the Halt state. To work around this problem, be sure to reset the XSCFs after the firmware update, by using the rebootxscf(8) command.

16 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

■ On a domain which has been in operation during the XCP update to 1124, when

you perform Dynamic Reconfiguration (DR) to add or replace the SPARC64 VII processors, you need to update the OpenBoot PROM firmware. The OpenBoot PROM firmware is updated as you update the XCP and restart the domain. For this reason, it is strongly recommended to restart all the domains after you update the firmware to XCP 1124, regardless of whether you added or replaced the SPARC64 VII processors.

Chapter 2 XCP 1124 and XCP 1124-related Information 17

18 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

CHAPTER

Information About Software

This section describes the special instructions and the issues about the M3000/M4000/M5000/M8000/M9000 servers software.

■ “Notes and Limitations” on page 19

■ “XCP Issues and Workarounds” on page 20

■ “Oracle Solaris OS Issues and Workarounds” on page 59

■ “Software Documentation Updates” on page 87

■ “Miscellaneous Information” on page 98

Notes and Limitations

Notes on RCI Function

The RCI function is supported on any of the following servers.

■ The server which you purchased in Japan from Fujitsu

■ The server which is bearing the Fujitsu logo on the front surface, regardless of

area of purchase

When using the RCI function such as RCI build procedure, see the SPARC Enterprise

M3000/M4000/M5000/M8000/M9000 Servers RCI Build Procedure and the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers RCI User's Guide.

1. This refers to the server which has the black-colored chassis and is exclusively bearing the Fujitsu logo on the front surface.

Notes on Remote Maintenance

This section is explained the notes on using the remote maintenance service. For details on making settings and using the remote maintenance service, see the manuals about the remote maintenance service in the Enhanced Support Facility User’s Guide for REMCS.

Before Setting the Remote Maintenance Service

Before using the remote maintenance service on your M3000/M4000/M50900/M8000/M9000 server, you have to complete the settings for the REMCS Agent function on XSCF Web.

Be sure to complete the necessary settings for using XSCF Web such as enabling the HTTPS, on XSCF shell. After completing, specify the settings for REMCS Agent function on XSCF Web.

For detail on the settings for XSCF Web, see SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

The Timezone Setting for REMCS Agent Function

The REMCS agent uses the current server timezone. So when you change the server timezone by XSCF, the "Periodical Connection Schedule" setting is required again for updating the information of the REMCS center.

XCP Issues and Workarounds

For known XCP issues and possible workarounds in XCP 1124, see "“Known Issues

and Workarounds in XCP 1124” on page 21." For XCP issues that have been fixed,

see "XCP Issues Fixed" for each version.

20 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

Known Issues and Workarounds in XCP 1124

TABLE 3-1 lists known XCP issues and possible workarounds in XCP 1124.

TABLE 3-1 Known Issues and Workarounds in XCP 1124

M4000

ID M3000

M8000

M5000

M9000 Description Workaround

RTIF1070914-025

RTIF1071116-001

RTIF1071126-002

RTIF1080725-001

RTIF1080725-002

O When you execute XCP Sync on the

Firmware Update page, after 15 minutes, the error message "Another

flashupdate is now processing" or "The page cannot be displayed" may appear.

O DR operations might fail (with a

misleading message regarding the board being unavailable for DR) after the addfru(8) or replacefru(8) command have been used for active replacement. This happens when the active replacement is done without the diagnostic test in the maintenance menu.

O When the server is being installed,

and the mainline switch is turned on for the first time, these error messages might be displayed:

PSU shortage

XSCF watchdog timeout XSCFU hang-up is detected XSCF process down detected

OOOIn setsnmp addv3traphost, when

the authentication failed due to the reasons such as the trap host not working, or the wrong user name or password, the subsequent SNMP traps will not be notified.

OOOWhen the SNMPv3 trap has been set,

after the watchdog timeout occurred in XSCF and XSCF reset, the subsequent SNMP traps will not be notified.

No workaround is available. However, the XCP Sync process has been continuously executed. Check the XSCF update completion message on the monitoring message to confirm the completion of Sync process.

Do not fail to execute the diagnosis in the maintenance menu of the addfru(8) or replacefru(8) command. In case of missing the diagnostic test in the maintenance menu of the addfru(8) or the replacefru(8) command, execute the testsb(8) command or delete the CPU/memory board unit using the deletefru(8) command and then retry the addfru(8) command.

Turn off the system AC power, then turn it on again.

When the error log is displayed again, turn off the system AC power, then turn it on again. To turn on the system power that you turned off, wait at least 30 seconds before power-on.

No workaround is available. Confirm that the SNMP trap host is

working and re-execute the setsnmp(8) command using the correct user name.

Reset the XSCF.

Chapter 3 Information About Software 21

TAB LE 3 -1 Known Issues and Workarounds in XCP 1124 (Continued)

M4000

ID M3000

RTIF1-

O When FRUs are cold-replaced (with

081016-002

M8000

M5000

M9000 Description Workaround

the system off), (after poweron) the monitor process might not generate entries in the monitor message log identifying the replacement operation that has occurred.

RTIF1081225-001

OOOIn the settimezone -c adddst

command, when you set eight or more letters to the abbreviation of time zone and the name of Daylight Saving Time, execution of the showlogs command induces a segmentation fault and results in an error.

No workaround is available.

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

RTIF1090108-003

RTIF1090427-005

RTIF1090731-001

RTIF1100331-002

RTIF1110222-001

OOODate and time of the Last Update

which displayed on the XSCF Web may not be updated.

OOOWhen you use the

setpasswordpolicy(8) command and set "9999999999" (10 digits) in Different Characters, the showpasswordpolicy(8) command displays "-1."

O While a DIMM correctable error (CE)

has been occurred, when XSCF failover is started, a message "XSCFU hang-up is detected" might appear in the error log.

OOOWhen you start up a domain from a

disk that is connected to the 8 Gbps fibre channel card (SE0X7F21F, SE0X7F22F) and if it is unable to start the domain due to causes such as disk failure, an error log of "FRU: /UNSPECIFIED" might be registered.

OOOIf setpasswordpolicy -r is set to 0,

existing XSCF users are unable to change their password and get the error message, password:

Operation failed.

Please refresh the display.

No workaround is available. Use XSCF Web.

This error log can be safely ignored.

No workaround is available.

Do not execute the command "setpasswordpolicy -r 0".

22 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-1 Known Issues and Workarounds in XCP 1124 (Continued)

M4000

ID M3000

RTIF1-

OOOAfter regenerating XSCF host public

120329-001

M8000

M5000

M9000 Description Workaround

key with setssh -c genhostkey, other connected XSCF users may encounter a “permission denied” error when executing the XSCF command line.

RTIF1120329-003

O O The fault information that is held in

the domain, and that can be checked with the Oracle Solaris OS fmadm faulty command is sent to the XSCF every time the domain is restarted or the XSCF is reset. On the other hand, the XSCF holds a history of the fault information it has received in the past from the domain, and exercises control to ensure that the same failure is not registered in the error log.

However, replacing the XSCF unit on the M4000/M5000 server or replacing the motherboard unit (MBU) on the M3000 server restores the failure history information held by the XSCF to its initial values. As a result, failures resolved in the past may be registered again as new failures in the error log.

XSCF reboot is required after generating the XSCF host key.

If a new failure occurs after replacing the XSCF unit or MBU, check the failure occurrence time and UUID in the fmdump -V output to judge whether the failure has been resolved in the past or is a new failure.

Also, if any fault information on failures already resolved remains in the domain, execute the Oracle Solaris OS fmadm repair command during maintenance to reset the fault information.

Chapter 3 Information About Software 23

TAB LE 3 -1 Known Issues and Workarounds in XCP 1124 (Continued)

M4000

ID M3000

RTIF1-

OOOSuppose that the audit system is

141209-001

M8000

M5000

M9000 Description Workaround

configured so that writing to audit records stops temporarily when the audit trail reaches its full capacity. An XSCF shell or XSCF Web operation at this time may lead to an XSCF reset due to the mistaken detection of one of the following errors: "Hardware

access error." or "SCF panic detected."

This problem occurs even when the XSCF shell is automatically run regularly to monitor the logical domain status by using PRIMECLUSTER software.

You can check the contents of the currently set audit system by using the showaudit(8) command. In the following example, "Policy on full trail" is "suspend," indicating that writing to the audit record has been set to stop temporarily. Also, "Audit space free" is "0," indicating that the audit trail has reached its full capacity.

[Example]

XSCF> showaudit all Auditing: enabled Audit space used: 4194304

(bytes) Audit space free: 0 (bytes) Records dropped: 0 Policy on full trail:

suspend

omitted

Execute the setaudit -p count command to configure the audit system to delete new audit records when the audit trail has reached its full capacity. (Default).

[How to restore] Perform the following procedure.

1. Perform login authentication using the default user account.

2. Execute the restoredefaults xscf command.

3. Execute the setaudit -p count command to configure the audit system to delete new audit records when the audit trail has reached its full capacity. (Default)

24 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

XCP Issues Fixed in XCP 1124

TABLE 3-2 lists XCP issues fixed in XCP 1124.

TABLE 3-2 XCP Issues Fixed in XCP 1124

M4000

ID M3000

M8000

M5000

M9000 Description Workaround

RTIF1-

OOOSecurity fixes. Update the XCP firmware to XCP 1124

180702-001

XCP Issues Fixed in XCP 1123

TABLE 3-3 lists XCP issues fixed in XCP 1123.

TABLE 3-3 XCP Issues Fixed in XCP 1123

M4000

ID M3000

RTIF1-

OOOWhen the XSCF is specified as an NTP

170605-001

RTIF1-

OOOSecurity fixes.

170609-001

M8000

M5000

M9000 Description Workaround

server that Oracle Solaris refers to, no polling response can be obtained from the XSCF, and synchronization with the NTP server might fail.

(CVE-2016-6304, CVE-2016-2182, CVE-2016-2183, CVE-2016-6302, CVE2016-6306, CVE-2016-6515, CVE-20173731, CVE-2016-7431, CVE-2016-7429, CVE-2016-7433)

For detail, see the Oracle website related to the following:

Critical Patch Updates

or newer.

Set an NTP server other than the XSCF of the current system as an NTP server that Oracle Solaris refers to.

Update the XCP firmware to XCP 1123 or newer.

Chapter 3 Information About Software 25

XCP Issues Fixed in XCP 1122

TABLE 3-4 lists XCP issues fixed in XCP 1122.

TAB LE 3 -4 XCP Issues Fixed in XCP 1122

M4000

ID M3000

M8000

M5000

M9000 Description Workaround

RTIF1161006-002

OOOThe reporting of an error or the

remote reporting of a hardware setting change notification may not reach the REMCS center.

XCP Issues Fixed in XCP 1121

TABLE 3-5 lists XCP issues fixed in XCP 1121.

TAB LE 3 -5 XCP Issues Fixed in XCP 1121

M4000

ID M3000

RTIS1-

OOOIf the SNMP Agent Status setting was

151212-001

RTIF1-

OOOSecurity fixes.

161006-004

M8000

M5000

M9000 Description Workaround

changed when in the enable state, SNMP Agent Status becomes disable.

You can check Agent Status from the Agent Status display of the showsnmp command.

(CVE-2015-3183, CVE-2015-2808) For detail, see the Oracle website

related to the following: Critical Patch Updates

No workaround is available.

After changing the SNMP Agent Status setting once to disable with the setsnmp command, set Agent Status to enable with the setsnmp command.

Update the XCP firmware to XCP 1121 or newer.

26 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

XCP Issues Fixed in Releases Earlier Than XCP 1121

TABLE 3-6 lists XCP issues that have been fixed in releases earlier than XCP 1121.

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121

M4000

ID M3000

RTIF1070418-004

RTIF1070418-005

RTIF1070418-009

OOOWhile XSCF is running, a process may

M8000

M5000

M9000 Description Workaround

O O All domains must be powered off

before upgrading the XCP.

O O If you log in to the XSCF while it is

still booting, you may get a bash$ prompt instead of the XSCF> prompt, and be unable to perform most operations.

go down, a watchdog timeout may occur, or a hang-up may occur. After this, XSCF may reset.

Power off domains before using the flashupdate(8) command to upgrade XCP firmware.

Log out of the bash$ prompt and wait for the XSCF to finish booting.

M8000/M9000 servers: Check that XSCF is started. If there is XSCF unit which is not started, execute the replacefru(8) command, and then uninstall the XSCF unit and install it again. Or stop all the domains and then execute the system power off/on (AC OFF/ON). To turn on the system power that you turned off, wait at least 30 seconds before power-on.

M4000/M5000 servers: Check that XSCF is started. If not started, stop all the domains and then execute the system power off/on (AC OFF/ON). To turn on the system power that you turned off, wait at least 30 seconds before power-on.

M3000 server: Check that XSCF is started. If not started, stop the domain and then execute the system power off/on (AC OFF/ON). To turn on the system power that you turned off, wait at least 30 seconds before power-on.

Chapter 3 Information About Software 27

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1070418-010

RTIF1070418-011

RTIF1070418-012

RTIF1070418-020

M8000

M5000

M9000 Description Workaround

OOThe showdomainstatus -a

command shows domain status as Powered Off, but the showboards -a command shows the domain is testing.

O O Some commands that update

configuration data take a relatively long time to execute.

OOThe fault (memory.block.ue) is

encountered and reported periodically.

O O When using the XSCF Web to import a

firmware image, if the image is corrupted (for example, if the browser window is closed during import), the flashupdate command might later

Use the showboards command to check the status of domain power.

The showdomainstatus command takes a longer time to show the correct status.

Do not cancel set* commands. They appear to hang, but eventually complete in about 30 seconds.

An uncorrectable error exists in a DIMM and the DIMM should be replaced.

Use the command getflashimage

-d to delete the corrupted image. If

necessary, reboot the XSCF Unit, then use the flashupdate command again to clear the internal error.

report an internal error. CR ID 6537996 is similar.

RTIF1070418-021

RTIF1070418-022

O O Attempting to move a COD board

using the moveboard(8) command might fail.

O O The XSCF firmware monitors itself

and if it detects any abnormalities, it will force a reset.

Use the deleteboard(8) and addboard(8) commands instead of the moveboard(8) command.

Allow the XSCF Unit to finish resetting. It will return to normal operation within approximately 5 minutes.

RTIF1070418-023

OOUsing the rebootxscf(8) command

may result in a process down error,

Ignore this event.

and possibly an FMA event with MSG ID SCF-8005-NE.

RTIF1070418-025

OOshowaudit all shows a long list of

defaults in the policy section after the database is cleared.

Update the database with the following:

setaudit -a opl=enable

setaudit -a opl=default

RTIF1070528-001

O O When you have updated the

/etc/ttydefs file of Oracle Solaris

No workaround is available.

OS to disable the console flow control, you cannot disable the console flow control on the telnet via a server.

28 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1-

OOOWhile XSCF is running, watchdog

070528-002

M8000

M5000

M9000 Description Workaround

timeout may occur and XSCF may reboot.

M4000/M5000/M8000/M9000 servers: Check that XSCF is started. If not started, stop all the domains and then execute the system power off/on (AC OFF/ON). To turn on the system power that you turned off, wait at least 30 seconds before power-on.

RTIF1070802-001

RTIF1070823-001

O O When connected to telnet, the login or

the password prompt doesn't appear.

O O Using the XSCF Web, when you

selected [SSH] on the snapshot screen, the maximum number of character input for Host, Directory, ID, and

Disconnect the telnet session and try again.

To specify the value which exceeds the maximum number of character input for the XSCF Web, use XSCF

Shell. Password doesn't correspond to the maximum number of character input on the XSCF Shell.

RTIF1070823-002

RTIF1070823-003

O O When you display the Logical tree on

the XSCF Web, there may be multiple displays of the same domain, depending on the domain configuration.

O O When you display the Logical tree on

the XSCF Web, the hardware configuration of CPU or memory which assigned to the domain appears differently from the actual domain

On the Menu, select System Board

Configuration and refer to the domain

configuration from XSB Status (All).

Or use the showboards(8) command

to refer to the domain configuration.

On the Menu, select Device Status to

refer to the domain hardware

configuration. Or use the

showdevices(8) command to refer to

the domain hardware configuration. configuration.

Chapter 3 Information About Software 29

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1-

OOOM8000/M9000 servers:

070824-001

M8000

M5000

M9000 Description Workaround

When remote power control mode of interlocking mechanism for power supply to domain, is enabled, after

M8000/M9000 servers: After XSCF Unit is replaced, configures the RCI again and sets the

remote power control mode. XSCF Unit is replaced, the interlocking for power supply by RCI cannot work.

RTIF1070824-002

RTIF1070824-003

RTIF1070824-004

RTIF1070824-005

M3000/M4000/M5000 servers: When remote power control mode of interlocking mechanism for power supply to domain, is enabled, after the motherboard unit is replaced, the interlocking for power supply by RCI cannot work.

O O On the XSCF Web, when you select

Domain Mode Configuration to perform various settings, the pop-up screen may not appear but "Undefined" may be displayed on the screen.

O O On the XSCF Web, while the XCP

import is in process from the [Firmware Update] screen, when you execute the [REFRESH] button, the pop-up of "Uploading Now!" disappears and the XCP import terminates abnormally.

O O On the XSCF Web, on the [Domain

Status] screen, when you select an XSB displayed on the Domain Component List, and in case the selected XSB is not yet mounted or is Uni-XSB, the pop-up screen displays no data.

O O On the XSCF Web, when you changed

the Refresh Interval value of the Monitor Message Frame, the invalid pop-up "Confirmation Domain mode" may appear.

M3000/M4000/M5000 servers:

After the motherboard unit is

replaced, configures the RCI again

and sets the remote power control

mode.

Select Domain Mode Configuration

one more time and perform the

settings. Or once terminate the XSCF

Web and then perform the settings.

None available at this time.

Ignore the pop-up and close the

screen.

30 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1070824-006

M8000

M5000

M9000 Description Workaround

O O On the tab browser, to the same host,

when you perform multiple log-in with the user accounts of different

When you use the tab browser, do not perform multiple log-in to the same

host. user privileges, the user privilege of the last log-in user account will be applied to those pages which you've already logged in.

RTIF1070824-007

O O When you change configuration on

the XSCF Web, if you select cancel on

From the Menu, select the original

configuration page again. the confirmation dialog or perform forced close, the original configuration page may be unavailable.

RTIF1070824-008

O O On the [Domain Configuration]

screen, when you select an undefined

None available at this time.

Domain ID, the Configuration Policy remains as the content which previously displayed.

RTIF1070824-009

O On the [System Board Configuration]

screen, when you execute Detail, it is

None available at this time.

displayed as if the CPUM and the memory of MBU are all mounted on the PSB#0 side. And in the detail display of PSB#0, memory is displayed as "22 + 2."

RTIF1070824-011

O O While using Firefox 2, in the

Configuration policy setting on the

From the Menu, select the [Domain

Configuration] page again. [Domain Configuration] screen, when you specify a domain which is in operation, an error display pop-up appears. When you click on the [Back] button on this error display pop-up and click on the [Cancel] button on the inquiry screen to re-display the data, the system remains in the error message screen.

RTIF1070904-001

O CLIs executed in Standby XSCF

should display "Permission denied".

Only the following CLIs can be

executed on the Standby XSCF:

snapshot(8), switchscf(8).

Do not attempt to run any other CLI

on the Standby XSCF. Such attempts

will report various errors.

Chapter 3 Information About Software 31

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1070904-002

M8000

M5000

M9000 Description Workaround

O O When the snapshot CLI attempts to

write to a USB stick that has write

Do not attempt to use write-protected USB devices for collecting snapshot.

protect set results in an I/O error.

RTIF1070904-003

RTIF1070904-005

RTIF1070904-006

RTIF1070912-001

O O An incorrect domain state is reported.

After the command sendbreak(8) to domain is issued, showdomainstatus(8) continues to show the state as "Running" when the domain is actually at "ok" prompt.

O O Time can't be synchronized with the

NTP server.

O O While executing the domain power-

on, domain reset or DR, in case the XSCF reset occurred, the process may be aborted in some or all of the XSB.

O O If an invalid SMTP server is

configured, a subsequent attempt to disable e-mail service (using the setemailreport CLI) may block for up to 30 minutes.

No workaround is available. This is expected behavior of the sendbreak(8) operation.

Check the stratum value of the NTP server.

The stratum value of XSCF is "5." The NTP server which the XSCF refers to must be a server on which the stratum value is smaller than 5. When you changed the NTP server to refer to, reboot the XSCF.

When the stratum value has been set correctly and the time can't be synchronized, use the showntp(8) command to check the jitter value to be displayed.

If this value is large, please reboot the XSCF.

Execute the domain reset one more time, or power off the domain and then power on again.

Wait for the CLI to complete. The rest of the system will function normally during this time.

• The CLI can also be aborted by ^C. Note that the operation (disabling e-mail report) is completed, even if ^C is used.

• showemailreport can be used to confirm that the e-mail service has been disabled.

32 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1070914-001

M8000

M5000

M9000 Description Workaround

O O While executing the firmware update

by using the flashupdate(8) command or BUI, when the import of XCP executed by using the

Do not execute the import of XCP by using the getflashimage(8) command or BUI, while executing the

firmware update. getflashimage(8) command or BUI, the firmware update aborts.

RTIF1070914-002

O O When the XSCF switching performed,

the monitor message doesn't show the number of XSCF unit which turned

Execute the showhardconf(8)

command to refer to the state of XSCF

unit. active.

RTIF1070914-003

O O When the XSCF switching performed,

there may be "SCF: Board control

No workaround is available.

This message can be safely ignored. error (DMA timeout)" stored in

the error log.

RTIF1070914-005

O O On the XSCF Web, when using

Internet Explorer 7, on the [User

None available at this time.

Accounts] screen, User Local Accounts doesn't show the Status of each user.

RTIF1070914-006

O O When you set the XSCF user account

name to the maximum 32 characters,

Use up to 31 characters to set the

XSCF user account name. you can log in, but then, when you execute the XSCF Shell or operate the XSCF Web, "Permission denied" occurs.

RTIF1070914-007

O O On the XSCF Web, when you use

Internet Explorer and select [Log

None available at this time.

Archives], the [Status of Log Archiving] screen doesn't show the status information.

RTIF1070914-008

O O On the XSCF Web, when you select

[POP] or [SMTP-auth] on the [SMTP]

None available at this time.

screen to enter Password, the input value doesn't appear as "*".

RTIF1070914-009

O O On the XSCF Web, when selected

[POP] or [SMTP-auth] on the [SMTP]

None available at this time.

screen, the setting can be done while the input field remains blank. And despite the setting done, the past setting data appears.

Chapter 3 Information About Software 33

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1070914-010

M8000

M5000

M9000 Description Workaround

O O On the XSCF Web, on the [SNMPv3

Security Settings] screen, when you select [Add User] or [Copy User] of

When you set the SNMP User with 16 digits or more, use the

showsnmpusm(8) command. the [SNMP User-Based Security Model (USM)], the [Create or Copy User] screen appears as a pop-up. On this screen, when you set the SNMP User with 16 digits or more, it will be registered correctly but the web browser screen displays up to 15 digits.

RTIF1070914-011

O O On the XSCF Web, on the [SNMPv3

Security Settings] screen, when you

Do not fail to set Confirm Password

which is a field must be entered. select [Change Password] of the [SNMP User-Based Security Model (USM)], the [Change Password] screen appears as a pop-up. On this screen, despite the [Confirm Password] is a field which must be entered, it is not displayed with the note "* Indicates require field."

RTIF1070914-012

O O On the XSCF Web, on the [SNMP-

Properties] screen, when you don't

None available at this time.

select [Trap Host] and execute the [Remove] button, the invalid message "The trap host will be removed" appears as a pop-up. And when you select [OK] on the pop-up screen, the invalid message "Remove

trap host failed. setsnmp: invalid trap type" appears.

RTIF1070914-013

O O On the XSCF Web, on the [Audit-

Properties] screen, when you execute the [Add Policy] button, the [Set User

Set the correct user name or execute

the [Cancel] button to close the pop-

up screen. Policy] appears as a pop-up. On this screen, when you specified a user name which is not registered in XSCF and an input error resulted, the value entered won't be cleared though you execute the [Reset] button to clear the specified user name.

34 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1070914-014

M8000

M5000

M9000 Description Workaround

O O On the XSCF Web, when you use a

user account without an appropriate

None available at this time.

privilege to select [Snapshot], set the parameters of [Start time] or [End time] and execute the [Download] button, it doesn't result in a privilege error but the parameter error will be displayed.

RTIF1070914-015

O O On the XSCF Web, when you select

[User Manager] to add the user account, the user name to be specified

To specify a user name of 20 characters or more, use the adduser(8) command.

is limited up to 20 characters.

RTIF1070914-016

O O On the XSCF Web, when you select

[LDAP] to perform the LDAP configuration, if you execute [Save]

Since "0" is an invalid value in the [LDAP Search Timeout], do not fail to

set a value other than 0. while the [LDAP Search Timeout] remains as its default value "0," it results in "LDAP Configuration

Update Failed. Save LDAP Configuration Data failed,"

and the setting can't be stored.

RTIF1070914-017

O O On the XSCF Web, when you select

[LDAP] and input the [LDAP Search Timeout] with a value which exceeds

None available at this time. The

maximum 2147483647 seconds will be

set to the [LDAP Search Timeout]. the maximum 2147483647 seconds, it doesn't result in parameter error.

RTIF1070914-018

O O On the XSCF Web, when you use a

user account without an appropriate privilege to select [LDAP] and execute

The configuration is not deleted. To

show the configuration information

again, select [LDAP] from the Menu. the [Delete] button, it results in a privilege error but the configuration information which has been displayed will be cleared and seems as if deleted.

Chapter 3 Information About Software 35

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1070914-019

M8000

M5000

M9000 Description Workaround

OOThe CLI 'showldap -c' (which

displays current LDAP certificates) will show proper data only when used with the same user account that

Use the same user account for all LDAP display or configuration operations, for both CLI and XSCF

Web . had originally provided certificate information using 'setldap -c'. Any other user account will generate "Permission denied" error. Similarly, the XSCF Web’s [LDAP Configuration] pop-up screen will display no data, when a different user account is used.

RTIF1070914-020

O O On the User Account setting page on

the [User Manager] screen, after the

To change the password, select [User

Manager] on the Menu again. password change resulted in "Change Password Error," when you click on the [REFRESH] button, there appears the error message "No user. The request is aborted."

RTIF1070914-021

O O During the OpenBoot PROM process,

when you power off the domain, the

This error log can be safely ignored.

error log of Domain hang-up detected (level3) may be registered.

RTIF1070914-023

O O When you specify the domain ID or

XSB number which are not supported

Specify the available domain ID or

XSB number on the server. on the server, there appears the parameter error message.

RTIF1070914-024

O O When you display the physical tree on

the XSCF Web, the warning mark is

None available at this time.

displayed on the link card for External I/O expansion unit.

RTIF1070914-026

O O The XSCFU cannot act as a reliable

NTP source for domains.

All domains should be configured to

use a NTP source other than the

XSCFU.

RTIF1070915-001

O O On the [Domain Configuration]

screen, when you newly define the

When you define the Domain

Component List, use CLI. Domain Component List, the parameter error may be displayed.

36 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1071011-001

M8000

M5000

M9000 Description Workaround

O When the server is being installed,

and the mainline switch is turned on

Turn off the system AC power, then

turn it on again. for the first time, these error messages might be displayed:

XSCFU hang-up is detected XSCF process down detected DB synchronization timeout

RTIF1071102-001

O O The XSCF firmware monitors itself

and if it detects any inconsistencies, it forces an XSCF reboot.

No workaround is available. Allow

the XSCF Unit to finish rebooting. It

returns to normal operation within

approximately 5 minutes.

RTIF1071102-002

RTIF1071116-001

OOOThe snmp daemon might quit. To restart the snmp daemon, issue the

command setsnmp enable.

O DR operations might fail (with a

Do not fail to execute the diagnosis in

the maintenance menu of the

addfru(8) or replacefru(8)

command. In case of missing the

diagnostic test in the maintenance

menu of the addfru(8) or the

replacefru(8) command, execute

the testsb(8) command or delete the

CPU/memory board unit using the

deletefru(8) command and then

retry the addfru(8) command.

RTIF1071116-003

O O Using the XSCF Web, when you

selected [COD], codusage details

Use showcodusage(8) command to

display the cod usage. cannot be displayed correctly.

RTIF1071116-004

O O When Internet Explorer 7 browser is

used, the License key deletion cannot be executed on the BUI COD page.

Use deletecodlicense(8)

command to delete a license key. Or

use other browsers:

• Microsoft Internet Explorer 6.0

• Firefox 2.0 or later

• Netscape Navigator 7.1 or later

RTIF1071116-005

O While system power on, when the

XSCF switching performed by

No workaround is available. This

message can be safely ignored. switchscf(8) command, PANIC might be generated in XSCF before it switches, and "SHUTDOWN timeout" may be stored in the error log.

Chapter 3 Information About Software 37

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1071116-006

M8000

M5000

M9000 Description Workaround

O While XSCF is running, error message

of "hang-up is detected" might be displayed to XSCF console, and XSCF may reboot.

Check that XSCF is started. If not started, use the rebootxscf(8) command to restart XSCF, or stop all the domains and then execute the system power off/on (AC OFF/ON). To turn on the system power that you turned off, wait at least 30 seconds before power-on.

RTIF1071129-001

O O If the following message is displayed

on XSCF console, the XSCF might not

Replace the XSCF Unit.

start:

dbs[xxx]: ERR: scdb_init_all(): xx, No space left on device

In addition, this error log might be registered:

XSCF process down detected

RTIF1071129-002

O O When performing XSCF Shell

commands remotely using SSH on the

None available at this time.

remote-control device, the following messages might be displayed:

stty: standard input: Invalid argument

RTIF1071129-003

O O An error log cannot be registered in

XSCF when the following message is

No workaround is available.

displayed on Oracle Solaris OS by the I/O error:

SUNW-MSG-ID: SUN4-8000-4P,

TYPE: Fault

RTIF1071129-004

O O The following messages are displayed

and you might not boot Oracle Solaris OS:

Confirm the OpenBoot PROM environment variable. If the variable has errors, set the variable again.

• Abnormal OpenBoot

environment variable Boot process failed

• ERROR: Invalid token ''

FATAL: NVRAM contents corrupt; Reinitializing NVRAM parameters.

38 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1071227-001

M8000

M5000

M9000 Description Workaround

O O In XSCF, write of date and time may

become an error. When the domain

Execute the rebootxscf(8) command

to restart XSCF. powered on, the following message may appear and the domain may fail to be powered on.

Poweron canceled due to invalid system date and time.

RTIF1071227-002

O O When the showhardconf(8)

command executed in an environment with the External I/O Expansion Unit, the showhardconf(8) command may

Press Ctrl-C to terminate the

showhardconf(8) command and

execute the showhardconf(8)

command again. appear as if hang up.

RTIF1071227-003

O O When a non-existent device name

specified to the Boot device path and resulted in the OS Boot error, the status of I/O unit may become

Specify the correct device name to the

Boot device path.

When the status of I/O unit became

"Degraded," replace the I/O unit. "Degraded."

Chapter 3 Information About Software 39

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1080313-001

M8000

M5000

M9000 Description Workaround

O O When you set XSCF as the NTP server

of the domain, following message may appear on the domain console at the domain start and you may fail to perform time synchronization.

ntpdate[xx]: no server suitable for synchronization

Perform either one of the following workarounds depending on the mode which has been set in the xntpd of the domain.

Note - In case of step mode, the time correction induces the time step. When the time step occurred, it may affect the applications running on the domain.

•In case of step mode: Specify the -w option to execute the ntpdate(1M) command. Until it succeeds in synchronizing with the NTP server, the ntpdate command retry continues at regular intervals. In the retries, the message which indicates that it failed to synchronize with the NTP server can be safely ignored. When the synchronization completed, the time will be corrected to the time of the NTP server.

•In case of slew mode: Execute the ntpdate(1M) command without specifying the w option. In slew mode, the time variance from the NTP server will be corrected at 0.5 ms/second intervals. The message which indicates that it failed to synchronize with the NTP server can be safely ignored. Before the time completely corrected, there remains a time variance between the NTP server and the domain.

40 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1080325-001

M8000

M5000

M9000 Description Workaround

O O M4000/M5000 servers:

When you turn on AC power, or when you execute the rebootxscf(8) command, you may become unable to log in to XSCF and your press on the POWER switch on the operator panel may fail to turn on the power.

M4000/M5000 servers: Before turning on AC power, or executing the rebootxscf(8) command, please confirm that XSCF LAN has been correctly connected and linked up.

In case the situation in question occurred, please turn off the power of all domains and then execute the system power off/on. To turn on the power that you turned off, wait at least 30 seconds before power-on.

RTIF1080404-001

M8000/M9000 servers: When you turn on AC power, or when you execute the rebootxscf(8) or switchscf(8) command, either of the following situations may occur.

• Following error message gets registered in the error log, the status becomes Faulted, and the standby XSCF becomes unable to start.

Device error on serial interconnection between XSCFUs

• You become unable to log in to XSCF and your press on the POWER switch on the operator panel can't turn on the power.

O O Following a dynamic reconfiguration

operation using the XSCF commands deleteboard(8) and addboard(8), you might see I/O channel degradation, resulting in error messages and entries in the corresponding ereport.

If you run into this problem, the fmdump(8) command will report the following error by mistake:

ereport.chassis.SPARCEnterprise. asic.ioc.ch.leaf.fe

M8000/M9000 servers: Before turning on AC power, or executing the rebootxscf(8) or switchscf(8) command, please confirm that XSCF LAN has been correctly connected and linked up.

In case the situation in question occurred, please take either of the following actions.

•Use the replacefru(8) command to reattach the standby XSCF unit.

• Turn off the power of all domains and then execute the system power off/on. To turn on the power that you turned off, wait at least 30 seconds before power-on.

The MSG-ID assigned to the error displayed and the actual behavior may not be consistent, and reset or degradation may not occur. Contact a qualified service engineer and give the error code that displayed by using the showlogs error command.

Chapter 3 Information About Software 41

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1080404-002

M8000

M5000

M9000 Description Workaround

O O When you use the command

setsnmpusm passwd to set a

Always set a password of at least

eight characters. password, if you set a password of fewer than eight characters, a segmentation fault occurs.

RTIF1080512-001

O O When you specify "localhost" to the

hostname of the sethostname(8) command and reset XSCF by using

Do not specify "localhost" to the

hostname of the sethostname(8)

command. the applynetwork(8) and the rebootxscf(8) commands, a process goes down in XSCF.

RTIF1080512-002

O When the NTP setting are enabled, a

message as follows may appear on the

This message can be safely ignored.

No workaround is available. XSCF console.

Output sample:

-xx.xxx.xxx.xxx mode 4 code 1 auth 0 clock_filter: n 8 off -0.000310 del 0.001300 dsp 0.001158 jit 0.000172, age 0 clock_update: at 637535 assoc 2 local_clock: assocID 54190 offset -

0.000309657 freq -9.765 state 4

...

RTIF1080512-003

O O To a domain which is in Quad-XSB

configuration, when you perform active addition of PCI cards and then restart the domain, active addition of

Do not perform active addition of PCI

cards. When you failed in active

addition of PCI cards, stop the

domain to add on the cards. PCI cards may become unavailable afterwards.

RTIF1080520-001

RTIF1080526-001

O BUI Domain Operation page mistakes

the operation demand for Domain 8 or 9, and it issues it to DID#00 wrongly.

O O When the system is stressed with

many faults, the fmd process on the

Do not perform active addition of PCI

cards. When you failed in active

addition of PCI cards, stop the

domain to add on the cards.

Reboot the service processor using the

XSCF command rebootxscf(8). service processor might hang. Once this happens, fma commands on the service processor can fail or hang.

42 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1080620-001

M8000

M5000

M9000 Description Workaround

O O The SNMP trap not notified in the

event that the power cable of the

No workaround is available.

server got unplugged accidentally.

RTIF1080725-003

RTIF1080725-004

RTIF1080808-001

RTIF1081006-001

RTIF1081006-002

RTIF1081006-003

O O The initial value that set with the

setdomparam set-defaults option differs from the initial value of OpenBoot PROM.

parameters current value expected value

diag-level none(0x00) min(0x20)

auto-boot? false(0x00) true(0xff)

OOOAfter set the Daylight Saving Time by

using the XSCF shell, XSCF Web does not show the correct time in the Logs menu.

O O On the cluster system using the

PRIMECLUSTER software, when there are 10 or more RCI units, the RCI busy status may be temporarily unreleased and output the following syslog message:

SA_pprcir.so to test host host_name failed

OOOThe error log "XSCF FMEM write

error" recorded and the firmware

update might fail.

OOOIn the setemailreport(8)

command, when you specified over 255 characters in the SMTP address, an error results.

O During the domain operation, after

the XSCF reset due to the XSCF unit failure, the hardware status shows Deconfigure in the status of CPU and memory.

In the OpenBoot PROM prompt (ok), execute the set-defaults command to restore the OpenBoot PROM environmental variables to the initial value.

No workaround is available. Use the showlogs(8) command of the

XSCF shell.

Refer to the manual of the PRIMECLUSTER software to check the cluster status. If no problem found on the status, this message can be safely ignored. If any problem, follow the instructions on the manual to solve the problem.

Power off (AC OFF) the system, and power on (AC ON) again. Then, reexecute the firmware update.

Do not specify over 255 characters in the SMTP address.

Replace the motherboard unit only. When no failure found on the memory, you do not need to replace the memory.

Chapter 3 Information About Software 43

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1-

OOODuring the firmware update, there

081006-004

M8000

M5000

M9000 Description Workaround

might be the following output message and a XSCF panic might

Reset XSCF and use the

flashupdate(8) command to retry

the firmware update. occur.

kernel BUG in jffs2_do_read_inode at fs/jffs2/readinode.c:XXX!

RTIF1081006-005

OOOThe network configuration on the

XSCF Web does not support the

Use the setnetwork -r command

on the XSCF shell. function equivalent to the setnetwork -r command. And when you specified localhost or localdomain to the host name or the domain name, the error message "SessionID has expired" appears.

RTIF1081006-006

OOOThe panic log on the XSCF Web might

not be displayed from the top of the message.

When the output is insufficient,

execute the showlogs panic

command on the XSCF shell.

RTIF1081006-007

RTIF1081006-011

RTIF1081016-001

RTIF1081016-003

OOOThe password(8) command indicates

that the user operand is optional but will fail if a user operand is not included when other options are specified.

OOOSNMP trap host configuration

changes are not valid until setsnmp disable and setsnmp enable.

OOOPower failure at the commercial AC

supply connector to the UPS does not send notification/send trap.

OOOIn Internet Explorer 6 or 7, clicking on

the [Reset] button then the [OK] button from the [Settings]-[Audit][Add Policy] pop-up screen will log the user out with message:

Error Session Error Session ID has been expired

No workaround is available.

Specify the user operand to execute

the password(8) command when you

specify other options.

Modify the SNMP setting:

XSCF> setsnmp disable

XSCF> setsnmp enable

No workaround is available.

Log back into the browser interface

and use the [Backspace] key to clear

text in the [User] text box of the pop-

up screen instead of using the [Reset]

button.

44 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1081030-001

M8000

M5000

M9000 Description Workaround

O The information related to the defined

LSB cannot be displayed on XSCF Web [Domain Configuration] page

Use the showdcl(8), addboard(8), deleteboard(8), moveboard(8)

command on the XSCF shell. with an account which has single domain privilege larger than DID15. In addition, the operation for such LSB by [XSB Config...] button cannot be performed.

RTIF1081030-002

OOOWhen the timezone other than three

characters has been set, the error logs

Use the showlogs(8) command on

the XSCF shell. cannot be displayed on XSCF Web [Error Log] page.

In addition, XSCF Web [Panic Log] and [IPL Message Log] pages display the date on the table with "---".

RTIF1081104-001

OOOThe monitor message log might not be

registered when a PCI slot error detected.

No workaround is available.

Use the showlogs error command

or the fmdump command to check the

fault information of PCI slot.

RTIF1090108-001

OOOThe domain console may display this

message:

This message can be safely ignored.

ipsec_check_inbound_policy: Policy Failure for the incoming packet (not secure)

RTIF1090108-002

OOOIn the dual power feed system, when

the power failure and the power

You need to remove and insert the

power cable. recovery occurred repeatedly on one line, all domains will be forcibly powered off. And in the power recovery from the forced power-off, a PSU illegal configuration might be registered in the error log and the power recovery might not be started.

Chapter 3 Information About Software 45

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1090108-004

M8000

M5000

M9000 Description Workaround

O When you replaced the XSCF unit by

using the replacefru(8) command, there may be the DB synchronization timeout error log and the replacement may fail.

Turn off all mainline switches and then turn on again.

Or, just after the XSCF reset using the rebootxscf(8) command, execute the replacefru(8) command and extract and insert the XSCF unit which failed in replacement. If time passed after the XSCF reset, the replacefru(8) command may fail again. In such a case, re-execute the rebootxscf(8) command and the subsequent processes.

RTIF1090115-001

OOOWhen you execute the settelnet -

c disable command, the Telnet service will be stopped immediately.

After you stopped the Telnet service, execute the rebootxscf(8) command

to reset XSCF. However, unless you reset XSCF by using the rebootxscf(8) command, you might fail in the subsequent restart of the Telnet service.

RTIF1090122-001

OOO"Power recovery" message is

output before a PSU has recovered.

After the "Power recovery"

message is output, wait 60 seconds

before removing power from another

PSU.

RTIF1090220-001

OOOIn a system connecting multiple hosts

and one or more I/O units with RCI,

All the RCI hosts shall be powered on.

the power-on operation to one of those RCI hosts may not power on any of the RCI I/O units.

46 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1-

OOOM3000 server:

090220-002

M8000

M5000

M9000 Description Workaround

After replaced the motherboard unit, the RCI power interlocking setting restores to its default value.

M3000 server: If you have set the power interlocking to a value other than the default, replace the motherboard unit and then use the setpwrmode(1M) command to set the power interlocking setting again.

RTIF1090427-001

RTIF1090427-002

RTIF1090427-003

RTIF1090427-004

M4000/M5000/M8000/M9000 servers: After replaced the XSCF unit, the RCI power interlocking setting restores to its default value.

OOODespite the normal status of ppp

network interface for the XSCF-toOracle Solaris OS communication, SNMP MIB notifies abnormal (down) status.

OOOAfter the XSCF reset or switching, you

cannot login to XSCF using the LDAP server.

O After changed the SNMP

configuration, when the XSCF switching occurred, the SNMP function may be disabled.

OOOIn the setting of the LDAP server, the

number of characters which can be specified differs between XSCF Web and XSCF Shell. On XSCF Web, you can enter up to 128 characters.

M4000/M5000/M8000/M9000 servers: If you have set the power interlocking to a value other than the default, replace the XSCF unit and then use the setpwrmode(1M) command to set the power interlocking setting again.

No workaround is available.

No workaround is available. Log in to active XSCF with initial

account and execute the following command to re-import the certificate chain.

'setldap -c <remote file>'

No workaround is available. In case this event occurred, the

following command may restore the function.

setsnmp disable setsnmp disable (run "setsnmp

disable" twice)

setsnmp enable

To set 129 characters or more, use XSCF Shell.

Chapter 3 Information About Software 47

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1-

OOOAfter you set https (using the self

090430-001

M8000

M5000

M9000 Description Workaround

certificate authority) by XSCF and

To set the self certificate authority, do

not specify a blank character. created a web server certificate, https is not enabled.

RTIF1090508-001

OOOIn a domain mounted with the 10

Gigabit Ethernet card (SE0X7HE1F), when you set the OpenBoot PROM environmental variable diag- switch? to true, the following warning message appears on the console; and at the same time, "Msg:

Device error (FCode informed error)" is recorded in the error log.

The entire output can be safely

ignored.

To avoid these outputs, execute the

following command at the ok prompt

and set the OpenBoot PROM

environmental variable diag-

switch? to false.

setenv diag-switch? false

WARNING: /pci@7,700000: FCODE map-in doesn't match decoded register type;

And when you execute the showstatus(8) command, "Degraded" might be indicated to the FRU which has installed the relevant card.

RTIF1090729-001

OOOWhen you use the sethttps(8)

command to create a self-signed web server certificate, if the number of

Specify up to 100 characters in the

parameter and execute the

sethttps(8) command again. characters specified in a parameter exceeds 100, it might result in an internal error and you might fail to create the certificate.

RTIF1090824-001

OOOThe XSCF might go down and require

a reboot, or you might see console error messages and a core dump (ereport.chassis.software.cor e) when one of these conditions

Use only user accounts with a user ID

(UID) value between 100 and 60000.

This is the range of auto-assigned

UIDs for the XSCF command

adduser(8). occurs:

• A local account has been created

with a user ID explicitly assigned to a value larger than 65536 (adduser

-u uid).

• An LDAP account has been used

that has a UID value larger than

65536.

48 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1-

OOOWhile Active Directory is enabled, if

091021-001

M8000

M5000

M9000 Description Workaround

you log in to XSCF using the user

No workaround is available.

name that registered in the Active Directory server, the showconsolepath(8) command displays not the log-in user name but "proxyuser."

RTIF1091105-001

RTIF1091109-001

OOOThe loadcert console operand is

missing in the usage of the setad(8) command and the setldapssl(8) command.

OOOOnce domain detected a failure

related to DIMM or PCI, the error log

For how to use the loadcert console operand of the setad(8) command and the setldapssl(8) command, see the man page.

This error log can be safely ignored.

about this detected failure is registered every time you reset XSCF.

RTIF1091109-002

OOOIn XSCF, a host route cannot be set.

When you use the setroute(8)

To set a host route, do not specify the netmask (-m option).

command and set the netmask to

255.255.255.255, it returns an invalid parameter.

RTIF1091109-003

OOOWhen you use the setnameserver(8)

command or the DNS setting of XSCF Web to register the DNS server or the search path, you can specify two or more same IP address values or domain names.

However, when you specify two or more same IP address values or

To delete all the DNS servers or the search paths which are same, specify just one corresponding address or domain name.

In doing so, all the DNS servers or the search paths which are same will be deleted. Register the data again as

needed. domain names to delete all the DNS servers or the search paths which are same, it returns an invalid parameter.

Chapter 3 Information About Software 49

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1-

OOOWhen you start up a domain from a

091109-004

M8000

M5000

M9000 Description Workaround

disk connected to the 8-Gbps fibre

No workaround is available.

channel card (SE0X7F21F, SE0X7F22F), if you fail to specify the correct device path, an error log with no message might be registered.

In the same way, when you start up a domain from a disk connected to the 8-Gbps fibre channel card (SE0X7F21F, SE0X7F22F), even if the domain cannot be started due to reasons such as disk failure, the error log might not be registered.

RTIF1100331-001

OOOWhen you use the sethttps(8)

command to create the self CA (Certificate Authority) or a CSR with

When you create the self CA or a CSR, do not specify only spaces in the e-

mail operand. specifying only spaces (for example, " ") in the e-mail operand, the HTTPS function might be disabled after XSCF reset.

RTIF1100713-001

OOOWhile the Oracle Solaris 10 OS is

running, if the occurrence of RED State Exception or watchdog reset or

No workaround is available.

When this problem occurred, turn off

the domain power and then turn on. the execution of the reset xir

command lead to the domain CPU reset, the following message might be displayed on the console and the domain might hang up.

Failed to complete trap processing. mid=0xXX

RTIF1100713-002

O Though the mainline switch is on, the

showhardconf(8) command might

No workaround is available.

wrongly display the PSU status as "Breaker off" or "Input fail."

RTIF1101019-001

OOOWhen you start up a domain from a

hard disk that is connected to the 8Gbps fibre channel card (SE0X7F21F, SE0X7F22F) and if you specified an erroneous value after "@" of the disk node, the message of "Fast Data Access MMU Miss" might be displayed on the console and an error

No workaround is available.

When this event occurred, change the

environmental variable 'auto-boot?'

setting to false and use the reset-

all command to reset the domain.

Then, specify the correct value after

"@" of the disk node and execute the

boot command. log of the TT=0x68 trap might be

registered.

50 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1101029-001

M8000

M5000

M9000 Description Workaround

O When you use the setroute(8)

command to set the gateway address and if you mistake the setting or the gateway has been stopped, XSCF hangs up.

To set the gateway address, confirm that the specified address is correct.

Before resetting XSCF by using the rebootxscf(8) command, confirm that the gateway is operating properly.

RTIF1101102-001

O When the RCI of XSCF#0 and XSCF#1

both got the communication error, the

No workaround is available.

RCI asynchronous monitoring of PRIMECLUSTER does not stop normally but gets the monitoring timeout, which delays the switching of the clusters after the error detected.

RTIF1101215-001

RTIF1110216-001

OOOWhile XSCF is running, a process may

go down. After this, XSCF may reset.

O When you execute the

showenvironment power command on the M3000 server with SPARC64 VII+ processors, an incorrect value of

No workaround is available. This error log can be safely ignored.

No workaround is available. The correct value is 505 W for AC

power supply model and is 510 W for DC power supply model.

"Permitted AC power consumption" will be displayed with 470 W.

RTIF1110222-002

OOOXSCF sends Rst packets without AH

header when dscp disconnects,

This message can be safely ignored.

resulting in false security vulnerability alarms.

The domain console may display this message:

ipsec_check_inbound_policy: Policy Failure for the incoming packet (not secure).

RTIF1110523-001

RTIF1110526-001

OOOFrom the OpenBoot PROM prompt

(ok), when you use the nvalias command and try setting a devalias to the environmental variable nvramrc, it may fail with the message "Can't create new alias

because nvramrc is full."

OOOInvoking ' setsnmp' without options

results in segmentation fault.

In case this event occurred, redo the settings of any devalias which is already defined in the environmental variable nvramrc, by using the nvalias command. Then, in order to set the failed devalias, execute the nvalias command once again.

To view ' setsnmp' usage options, use 'setsnmp -h'

Chapter 3 Information About Software 51

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1111005-001

M8000

M5000

M9000 Description Workaround

O O M4000/M5000 servers:

When the system board is mounted

M4000/M5000 servers:

No workaround is available. with the onboard I/O device, if you use the addboard(8) or moveboard(8) command to add or move it by DR, operation may fail.

RTIF1111028-001

M8000/M9000 servers: When the system board is mounted with one or more PCI cards, if you use the addboard(8) or moveboard(8) command to add or move it by DR, operation may fail.

However, when it is mounted with the IOUA card only, this event does not occur.

In either case, the following message appears on the destination domain console of the system board addition or move:

interpreter[xxxx]: ABORT: Bus

Error: Fault Addr: 0xXXXXXXXX efdaemon[xxx]: Wait pid: xxxx

status: xxx WARNING: IKP: Unable to

probe PCI leaf (x-x-x)

OOOIn the setemailreport(8),

setsmtp(8) or setupplatform(8)

command, any of the following characters in the e-mail address will result in an error.

!#$%&'*+/=?^`{|}~

M8000/M9000 servers:

No workaround is available.

Do not specify these characters in the

e-mail address.

52 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1111227-001

M8000

M5000

M9000 Description Workaround

O O In case of connecting an External I/O

Expansion Unit, a message

No workaround is available.

"watchdog timeout" might be registered in an error log under the following conditions:

•Executes the switchscf(8) command on an M8000/M9000 server.

•Executes the rebootxscf(8) command on an M4000/M5000 server.

RTIF1120216-001

O O Using PCI hot-plug, when you

perform active addition of a PCI card or perform active maintenance or active addition of an external I/O

Stop the target domain before the addition of a PCI card or before the maintenance or addition of an external I/O expansion unit.

expansion unit, operation may fail.

RTIF1120319-001

OOOAn internal module of the fmd

process (case-close module) turns

No workaround is available.

disable. If you continue the operation in a

situation that the case-close module is disabled, an fmd process failure occurs and resets XSCF.

RTIF1120322-001

OOOWhile starting the XSCF, SSH service

might be disabled and cannot perform SSH connection.

Wait for the XSCF finish starting, and then retry SSH connection. If SSH service has been disabled, reset the XSCF using the rebootxscf(8) command.

RTIF1120326-001

RTIF1120329-004

OOOExecuting the setldap -p command

with a password that contains a colon (:) causes a problem with the LDAP configuration.

OOOWhen the XSCF unit is monitored by

Ops Center, the service processor can

No workaround is available. To recover, execute

restoreconfig(8) to restore the last working LDAP configuration.

Disable Ops Center monitoring of the

XSCF unit. sometimes reset or failover unexpectedly.

RTIF1120424-001

O There is a low probability that FRU

replacement, which is performed by

No workaround is available.

the replacefru(8) command, fails during the replacement of XSCF boards in reaction to an XSCF board failure.

Chapter 3 Information About Software 53

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1120611-001

M8000

M5000

M9000 Description Workaround

O O When an External I/O Expansion Unit

error occurs with the following error

No workaround is available.

code, the showlogs(8) command may fail to display an error message or the component that needs to be replaced.

Code: XXXXXXXX-00XXXXXX11XXXXXXXXXXXXXX

RTIF1120703-001

O O There is a low probability that the

XSCF restart fails, when the XSCF reset occurs due to an XSCF

No workaround is available. If the defect occurred, contact a

qualified service engineer.

malfunction.

RTIF1121112-001

RTIF1121112-002

OOOAt the XSCF start, when the machine

administration of Enhanced Support Facility (ESF) which operates in the domain detected an error, process failure may occur which leads to the XSCF reset.

O When a temporary blackout occurred

on the M3000 server which is mounted with the SPARC64 VII+ processor, the "Power subsystem failure(detector=2)"

error is detected erroneously and the domain may be suspended.

No workaround is available.

M4000/M5000/M8000/M9000 servers:

Check that XSCF is started. If not started, stop all the domains

and then execute the system power off/on (AC OFF/ON).

To turn on the system power that you turned off, wait at least 30 seconds before power-on.

M3000 server: Check that XSCF is started. If not started, stop the domain and

then execute the system power off/on (AC OFF/ON).

To turn on the system power that you turned off, wait at least 30 seconds before power-on.

No workaround is available. When this event occurred, power off

and wait at least 30 seconds before power-on.

If not recovered with the above workaround, contact a qualified service engineer.

54 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1-

OOOAfter the getflashimage -v

121112-003

M8000

M5000

M9000 Description Workaround

command execution, the URI of the send file and the receive file in

No workaround is available.

Read the URI display of the send file

and the receive file in reverse order. transfer from 'A' to 'B' is displayed

vice versa.

RTIF1121112-004

RTIF1121112-005

OOOAfter the fmdump(8) command

execution, the FRU information of each event may fail to display the last one character in part, serial, and revision.

O O In the following configuration, active

replacement or active addition of a PCI card may fail. On this occasion, Ap_Id format and devices may not be shown correctly by cfgadm(1M).

No workaround is available.

When the FRU at the time of event

occurrence is mounted, you can use

the showhardconf(8) command to

confirm the FRU information.

In the relevant configuration, stop the

domain and perform cold addition or

cold replacement and then start the

domain.

To add a PCI card to the

M4000/M5000 servers, perform the M4000/M5000 servers:

• Active addition of a PCI card to

active addition of a PCI card to a slot

other than PCIE#1.

PCIE#1

• Active addition of a PCI card to a

To restore, reboot the domain.

PCI slot on the External I/O Expansion Unit

• Active replacement or active

addition of a link card on PCIE#1 which is connected with the External I/O Expansion Unit

M8000/M9000 servers:

• Active addition of a PCI card to a

PCI slot on the External I/O Expansion Unit

RTIS1130218-004

OOOAfter updating the firmware, the Fault

Management MIB Trap might not be reported.

Execute the following command or

reset the XSCF.

XSCF> setsnmp disable

XSCF> setsnmp enable

RTIF1120329-002

O M9000 server:

When using the expansion cabinet,

No workaround is available.

the depleted life (lifetime) of the energy storage module (ESM) on a Sun Flash Accelerator F20 PCIe card might be inaccurately reported or cannot be displayed. A depleted ESM might not be reported.

Chapter 3 Information About Software 55

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1-

OOOIf the domain POR reset is executed

130404-001

M8000

M5000

M9000 Description Workaround

while a domain shutdown is being executed, the domain status may be erroneously displayed as Running

Once the domain shutdown processing is completed, execute the domain POR reset.

To restore, restart the domain.

(Waiting for OS Shutdown) after the domain is restarted.

RTIF1130404-002

OOOIn an environment in which RCI is

used, the setrci -c state command may not correctly display the power status of the server.

If the above status occurs in a configuration with multiple servers and I/O units connected by RCI, the I/O unit power may erroneously be turned off when the power to one server is off.

If the power status display is incorrect for a server, first turn off the power to the server. If the power to the server cannot be turned off, disconnect the RCI cable of the server, together with the T-branch connector, and then turn off the power.

After turning off the power to a server that does not correctly display the power status, restore the system by first disconnecting the server and then restarting the input power (AC OFF/ON).

RTI F1130404-003

OOOIn a configuration with multiple servers

and I/O units connected by RCI, connecting a powered-on I/O unit to a powered-off server with an RCI cable may erroneously turn off the I/O unit power.

To connect a powered-on I/O unit to a server with an RCI cable, either connect the I/O unit before turning on the server input power (AC ON), or connect the I/O unit to the server when the server power is on.

Connecting with the power off in cases where the server RCI settings are initialized does not cause a problem.

RTIF1130719-001

O O If a memory failure occurs after the

following error is detected, POST

No workaround is available.

diagnosis may hang up without isolating the faulty memory.

Msg: DIMM serious error Msg: Unexpected Trap type

(tt=0x32)

RTI F1130801-001

OOOThe following error log may be registered

when the restoredefaults(8) command is executed on XCP 1115:

XSCF self diagnosis warning detection.

This error log may be ignored.

This trouble can be worked around by re-setting the XSCF configuration.

As a permanent solution, upgrade to XCP 1116 or newer.

56 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTI F1-

OOOWhile XSCF is running, "XSCF panic

130801-002

M8000

M5000

M9000 Description Workaround

detected" or "XSCF Watchdog timeout" may be detected, and XSCF

may reset.

M3000/M4000/M5000 servers:

Check that XSCF is started.

If not started, stop all the domains and

then execute a system power off/on (AC

OFF/ON).

To turn on the system power that you

turned off, wait at least 30 seconds before

power-on

M8000/M9000 servers:

Check that XSCF is started.

If there is an XSCF unit that has not

started, execute the replacefru(8)

command, and then uninstall the

XSCF unit and install it again. Or stop

all the domains and then execute a

system power off/on (AC OFF/ON).

To turn on the system power that you

turned off, wait at least 30 seconds

before power-on.

RTIF1140131-001

O O In a configuration with even

numbered domains, if the following operation is executed when half of the domains have become inactive ("Degraded" state) due to failures or configuration violations, either all the running domains stop or the restarting of such domains fails

[Operation]

1. Remove all XSBs of the domains which have become inactive (by executing the "deleteboard -c unassign" command).

Before executing the operations,

explained in "Explanation", please

execute any of the following

procedures.

• Perform maintenance to fix the malfunctions and configuration violations.

•Stop all domains.

[How to restore] Perform maintenance to fix the

malfunctions and configuration violations. Restart the domain after that.

2. Execute poweron or reboot on any of the domains which has not become inactive.

RTIF1140611-001

OOOSecurity fixes. (CVE-2014-0224)

For detail, see the Oracle website

Update the XCP firmware to XCP 1118 or newer.

related to the following:

Critical Patch Updates

RTIF1141002-001

OOOSecurity fixes (CVE-2014-7169. See

MOS Doc Id 1934739.1)

Update the XCP firmware to XCP 1118 or newer.

Chapter 3 Information About Software 57

TAB LE 3 -6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1141117-001

OOOSecurity fixes. (CVE-2014-3566)

M8000

M5000

M9000 Description Workaround

For details, see the Oracle website

Update the XCP firmware to XCP 1119 or newer.

related to the following:

Critical Patch Updates

RTIF1150605-001

O When using the addfru(8) or

replacefru(8) command for the maintenance of the CPU/memory

No workaround is available. Update the XCP firmware to XCP 1120

or newer.

board unit, executing the system board diagnostic test may cause the XSCF process to fail.

RTIF1150605-002

OOOIt may be temporarily impossible to

No workaround is available. Wait a few hours before attempting to

Even if it is possible to log in to the XSCF shell, executing the console command may end with an error and the following message displayed:

"console: error while loading shared libraries: libgcc_s_nof.so.1: cannot open shared object file Input/output error"

RTIF1150605-003

O If the active XSCF unit fails, and

active replacement is performed for that failed XSCF, synchronous processing of logs between the active and standby XSCF units may not be performed normally, and the log data below will not be inherited by the replacement XSCF unit.

If this issue occurs during active

replacement of the active XSCF unit,

turn off the power to all domains and

then turn off and on the input power

(AC OFF/ON).

To turn on the input power that you

turned off, wait at least 30 seconds

before power-on.

• showlogs power

• showlogs event

58 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-6 XCP Issues Fixed in Releases Earlier Than XCP 1121 (Continued)

M4000

ID M3000

RTIF1150608-001

RTIF1150707-001

OOOSecurity fixes. (CVE-2013-5704, CVE-

M8000

M5000

M9000 Description Workaround

O If you specify the USB device with

XCP 1119 and execute the XSCF shell commands below, or execute XSCF Web menu items corresponding to the XSCF shell commands below, the system displays "Unable to mount USB device" and the process fails.

• dumpconfig

• getflashimage

• restoreconfig

• setad

• setldapssl

• showcodactivationhistory

• snapshot

2014-3570, CVE-2014-3572, CVE-20148275, CVE-2015-0204, CVE-2015-0235)

For detail, see the Oracle website related to the following:

Critical Patch Updates

Use the remote host instead of the USB device and execute the command or operate XSCF Web.

Or, after updating the firmware to another version other than XCP 1119, execute the command or operate XSCF Web.

Update the XCP firmware to XCP 1120 or newer.

Oracle Solaris OS Issues and Workarounds

This section contains information about Oracle Solaris OS issues. TABLE 3- 7, TA BLE 3- 8,

TABLE 3-9, TABLE 3-10, TABLE 3-11, TABLE 3-12, TABLE 3-13, and TABLE 3- 14 list issues you

might encounter, depending upon which Oracle Solaris OS release you are using.

Oracle Solaris Issues and Workarounds for All Supported Releases

TABLE 3-7 lists Oracle Solaris OS issues that you might encounter in any supported

release of Oracle Solaris OS.

Chapter 3 Information About Software 59

TAB LE 3 -7 Oracle Solaris OS Issues and Workarounds for All Supported Releases

M4000

CR ID M3000

M8000

M4000

M9000 Description Workaround

4816837 O O System hangs when executing parallel

hot plug operation with SP DR in suspend phase.

6449315 O The Oracle Solaris OS cfgadm(1M)

command does not unconfigure a DVD drive from a domain on a M8000/M9000 server.

6459540 O O The DAT72 internal tape drive on a

server may time out during tape operations. The device might also be identified by the system as a QIC drive.

No workaround is available.

Disable the Volume Management

Daemon (vold) before unconfiguring

a DVD drive with the cfgadm(1M)

command.

To disab le vold, stop the daemon by

issuing the command

/etc/init.d/volmgt stop. After

the device has been removed or

inserted, restart the daemon by

issuing the command

/etc/init.d/volmgt start.

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,0

x8c,

0x8c,3;

There are four spaces between

SEAGATE DAT and DAT72-000.

6466617 O O Performing a hot plug operation with

the PCI-Express slot too quickly

Pause a few seconds between the

issue of each cfgadm -c command. interrupts a PCI leaf reset and occurs the following error:

cfgadm: Component system is busy error

60 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-7 Oracle Solaris OS Issues and Workarounds for All Supported Releases (Continued)

M4000

CR ID M3000

6481002 OOOInstalling the Oracle Solaris OS from

M8000

M4000

M9000 Description Workaround

the network using certain PCI-Express cards may cause a panic.

If you are using a Sun PCI-E Dual Gigabit Ethernet MMF Adapter or a Sun PCI-E Dual Gigabit Ethernet UTP Adapter, do not install the Oracle Solaris OS using either of these cards. Instead, use other network devices, such as the onboard Gigabit Ethernet or another network device.

6515648 O O "Replumb Failed" error appears

when dr@0:SB1::memory fails.

Once the DR operation is complete, it can be plumbed up manually.

Example steps to re-plumb the interface manually:

# ifconfig interface plumb xxx.xxx.xxx.xxx netmask +

broadcast + up

# ifconfig interface group group- name

# ifconfig interface addif xxx.xxx.xxx.xxx -failover

deprecated up

This workaround assumes that the /etc/hostname.interface file is correctly configured for the IPMP group and does not need any modification. The IP addresses used in the example above should match what was previously used and what matches the /etc/hostname.<interface> file.

6516135 O O Ap_Id format and devices may not be

shown correctly by cfgadm(1M).

Use the following operations to display all of the PCI slots.

1) devfsadm (at Oracle Solaris OS prompt)

2) cfgadm

6519290 OOOLarge amounts of I/O on swap

devices can cause the system to appear hung by overwhelming the

Set the following to /etc/system and then reboot the domain:

set maxfastscan=0x2000

I/O system. The amount of I/O required can be generated through a number of ways, eg memory shortage, heavy use of /tmp etc.

Chapter 3 Information About Software 61

TAB LE 3 -7 Oracle Solaris OS Issues and Workarounds for All Supported Releases (Continued)

M4000

CR ID M3000

6522017 O O DR and ZFS may not be used in the

M8000

M4000

M9000 Description Workaround

same domain.

This has been fixed in Oracle Solaris

11.1 SRU3.4.

Reduce the amount of kernel memory

that ZFS can allocate by setting the

zfs_arc_max parameter in the

/etc/system file. The following

example sets the maximum size to 512

Mbytes.

set zfs:zfs_arc_max =

0x20000000

6529714 O O Warning messages occur while trying

No workaround is available. to configure more than four PCIe Quad-port Gigabit Ethernet UTP Low Profile Adapter (X4447A-Z) or PCIe Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter (X1027A-Z) into one I/O Boat.

6530753 O O Some of the PCI slots in the External

I/O Expansion Unit PCI slots are not displayed during a normal boot operation.

Use one of the following operations to

display all of the PCI slots.

• boot -r (at open boot prompt)

• devfsadm -C (at Oracle Solaris OS prompt)

• cfgadm (twice at Oracle Solaris OS prompt)

6531036 OOOThe error message network

initialization failed appears

No workaround is available. This

message can be safely ignored. repeatedly after a boot net installation.

6532215 OOOvolfs or dscp service may fail when

domain is booted.

Restart the service if the failure is

observed. To avoid the problem, issue

the following commands.

svc:/platform/sun4u/dscp:defa ult: Method "/lib/svc/method/svc-dscp start" failed with exit status 95.

# svccfg -s dscp setprop

start/timeout_seconds=count:

300

# svccfg -s volfs setprop

start/timeout_seconds=count:

svc:/system/filesystem/volfs: default: Method or service exit timed out. Killing

300

# svcadm refresh dscp

# svcadm refresh volfs contract 59.

62 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-7 Oracle Solaris OS Issues and Workarounds for All Supported Releases (Continued)

M4000

CR ID M3000

6565553 6611966 6674266

M8000

M4000

M9000 Description Workaround

OODR deleteboard(8) and

moveboard(8) operations might fail.

Example for messages on domain:

No workaround is available. Try DR operations again.

drmach: WARNING: Device driver failure: /pci

dcs: <xxxx> config_change_state: Hardware specific failure: unconfigure SB1: Device driver failure: /pci

6588650 O O On occasion, the system is unable to

No workaround is available. DR after an XSCF failover or XSCF reboot.

6589644 O After added the system board by DR,

when the switching occurred on the redundant XSCF Units, the domain

The console can be recovered by

pressing Ctrl-q (the [Ctrl] key and

the [q] key). console may hang up.

6592302 O O Unsuccessful DR operation leaves

Tr y deleteboard(8) again. memory partially configured.

6619344 O The Sun Crypto Accelerator (SCA)

6000 might not work if hot-plug

To avoid the defect, do not hot-plug

this card in slot 1. configured into slot 1.

6625734 O Systems with large number of

processors in a single domain environment may have suboptimal performance with certain workloads.

Use processor sets to bind application

processes or LWPs to groups of

processors. Refer to the psrset(1M)

man page for more information.

Chapter 3 Information About Software 63

TAB LE 3 -7 Oracle Solaris OS Issues and Workarounds for All Supported Releases (Continued)

M4000

CR ID M3000

6660168 OOOIf a ubc.piowbeue-cpu error

M8000

M4000

M9000 Description Workaround

occurs on a domain, the Oracle Solaris Fault Management cpumem-diagnosis module might fail, causing an

If FMA service fails, issue the following command on the domain to recover:

# svcadm clear fmd

interruption in FMA service. If this happens, you will see the

following output in the console log:

SUNW-MSG-ID: FMD-8000-2K, TYPE: Defect, VER: 1,

Then restart cpumem-diagnosis:

# fmadm restart cpumemdiagnosis

SEVERITY: Minor EVENT-TIME: Fri Apr 4

21:41:57 PDT 2008 PLATFORM: SUNW,SPARC-

Enterprise, CSN: 2020642002, HOSTNAME: <hostname>

SOURCE: fmd-self-diagnosis, REV: 1.0

EVENT-ID: 6b2e15d7-aa65-6bccbcb1-cb03a7dd77e3

DESC: A Solaris Fault Manager component has experienced an error that required the module to be disabled. Refer to http://sun.com/msg/FMD-80002K for more information.

AUTO-RESPONSE: The module has been disabled. Events destined for the module will be saved for manual diagnosis.

IMPACT: Automated diagnosis and response for subsequent events associated with this module will not occur.

REC-ACTION: Use fmdump -v -u <EVENT-ID> to locate the module. Use fmadm reset <module> to reset the module.

6745410 OOOBoot program ignores the Kadb option

Use kmdb instead of kadb.

which causes the system not to boot.

64 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-7 Oracle Solaris OS Issues and Workarounds for All Supported Releases (Continued)

M4000

CR ID M3000

6765239 O If a SAS device containing multiple

M8000

M4000

M9000 Description Workaround

SAS targets is connected to the onboard external SAS interface, it will not work properly. The enumeration

Use a FUJITSU SAS card

(SE0X7SA1F/SE0X7SA1X).

Alternatively, check for the

availability of a patch for this defect. of target IDs within the device may change across reboots.

7009469 O Creating a RAID configuration using

No workaround is available. the raidctl(1M) command generates a warning message on initial process. Subsequent RAID configurations do not.

7135497 O On systems with the RAID-capable

IOUA card and running Oracle Solaris 11, after a RAID volume is deleted

Execute cfgadm(1M):

cfgadm -c unconfigure cn where cn

is the controller number. using raidctl -d , the format

utility does not display the disk.

18055846 O O When adding a PCI Expansion Unit

by PCI hot plugging (PHP), Oracle Solaris may panic by producing the following message:

There is no effective workaround.

Do not hot plug a PCI Expansion

Unit. There is no problem in hot

replacing in respect to the same slot.

panic[cpuX]/thread= XXXXXXXXXX: Fatal error has occurred in: PCIe fabric.(0xX)(0xXX).

Chapter 3 Information About Software 65

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/11

TABLE 3-8 lists issues that have been fixed in Oracle Solaris 10 8/11 OS. You might

encounter them in supported releases earlier than Oracle Solaris 10 8/11.

TAB LE 3 -8 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/11

M4000

CR ID M3000

6344060 O A lot of following ereports are

6794630 O An attempt to use the GUI to install

6966086 O bge interface can not enable Jumbo

7009474 OOOAfter applying 144563-01 or 144563-02

M8000

M4000

M9000 Description Workaround

outputted when both interfaces bge1 and bge2 are in use.

ereport.io.device.badint_limi t

ereport.io.service.lost

This issue is caused on the M3000 server with SPARC64 VII+ processors.

Oracle Solaris OS in a domain larger than 2TB might fail.

Frame function. This issue is caused on the M3000

server with SPARC64 VII+ processors.

patch, bge interface does not display link up/down message on console and syslog when plugging/unplugging.

This has been fixed in patch 144563-

02.

[Workaround] No workaround is available.

This has been fixed in patch 124630-

45.

[Workaround] Use the Command Line interface to

install Oracle Solaris OS.

This has been fixed in patch 144563-

02.

[Workaround] No workaround is available.

This has been fixed in patch 144500-

19.

[Workaround] Check the link status by using the

"link_state" parameter from the kstat(1M) output.

66 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 9/10

TABLE 3-9 lists issues that have been fixed in Oracle Solaris 10 9/10 OS. You might

encounter them in supported releases earlier than Oracle Solaris 10 9/10.

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

M4000

CR ID M3000

6668237 OOOAfter DIMMs are replaced the

6872501 OOOIf 139555-08 has been applied to the

6888928 OOOIPMP interface fails since probe

M8000

M4000

M9000 Description Workaround

corresponding DIMM faults are not cleared on the domain.

domain, cores are not offlined when requested by the XSCF. This CR effects only Oracle Solaris 10 5/09, Oracle Solaris 10 10/09, and an earlier version of Oracle Solaris OS with patch 139555-08.

packets are not sent through that interface. Problem occurs with M3000/M4000/M5000/M8000/M9000 servers running any Oracle Solaris release running IPMP with patch 141444-09 installed.

This has been fixed in patch 143527-

01.

[Workaround]

Use the following commands:

# fmadm repair fmri|uuid

# fmadm rotate

This has been fixed in patch 143359-

02.

[Workaround]

Use fmdump(8) with its -v option on

the Service Processor to identify the

faulty core. Once identified, use

psradm(1M) on the domain to offline

the core.

This has been fixed in patch 142900-

02.

[Workaround]

Disable probe-based failure detection.

Chapter 3 Information About Software 67

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/09

TABLE 3-10 lists issues that have been fixed in Oracle Solaris 10 10/09 OS. You might

encounter them in supported releases earlier than Oracle Solaris 10 10/09.

TABLE 3-10 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/09

M4000

CR ID M3000

6572827 OOOThe prtdiag -v command reports

6724307 O Scheduler decisions systems are

6800734 O O The deleteboard(8) command hang

M8000

M5000

M9000 Description Workaround

PCI bus types incorrectly. It reports "PCI" for PCI-X leaf devices and "UNKN" for legacy PCI devices.

occasionally unbalanced. Sometimes two threads will be on one

core (causing both to run at about half speed) while another core is idle. For many OpenMP and similar parallel applications, the application performance is limited by the speed of the 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 least one uneven schedule event.

in a domain.

This has been fixed in patch 141444-

09.

[Workaround] No workaround is available.

This has been fixed in patch 141414-

01.

[Workaround] Use processor sets to prevent uneven

threads to core assignment.

This has been fixed in patch 141444-

09.

[Workaround] No workaround is available.

68 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-10 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/09 (Continued)

M4000

CR ID M3000

6816913 O O The XSCF showdevices(8) command

M8000

M5000

M9000 Description Workaround

displays the incorrect processor cache size (MB) for fractional processor

Use the prtdiag(1M) command on

the domain to report processor

information. cache sizes, such as displaying "5" when the correct display would be "5.5."

6821108 O O DR and showdevices(8) command

do not work after XSCF reset.

This has been fixed in patch 140589-

02.

[Workaround]

Reset the XSCF service processor

twice. Half the SAs (Security

Associations) are deleted the first

time, half are deleted the second time,

so the second addition succeeds and

IPsec communication is reestablished.

6827340 OOODR and Memory patrol might fail due

to command error.

This has been fixed in patch 142344-

01.

[Workaround]

No workaround is available.

Chapter 3 Information About Software 69

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/09

TABLE 3-11 lists issues that have been fixed in Oracle Solaris 10 5/09 OS. You might

encounter them in supported releases earlier than Oracle Solaris 10 5/09.

TAB LE 3 -11 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/09

M4000

CR ID M3000

6588555 O O M8000/M9000 servers:

6623226 OOOThe Oracle Solaris OS command

M8000

M5000

M9000 Description Workaround

XSCF failover during DR operation to the permanent memory might cause domain panic.

M4000/M5000 servers: XSCF reset during DR operation to the permanent memory might cause domain panic.

lockstat(1M) or the dtrace lockstat provider might cause a system panic.

This has been fixed in patch 139555-

08.

[Workaround] M8000/M9000 servers:

Do not start an XSCF failover while a DR operation is running. Wait for a DR operation to finish before starting the failover. If you start the failover first, wait for the failover to finish before starting the DR operation.

M4000/M5000 servers: Do not start an XSCF reset while a DR operation is running. Wait for a DR operation to finish before starting the reset.

This has been fixed in patch 140336-

01.

[Workaround] Do not use the Oracle Solaris OS

lockstat(1M) command or the dtrace lockstat provider.

70 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-11 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/09 (Continued)

M4000

CR ID M3000

6680733 O O O Sun Quad-port Gigabit Ethernet

M8000

M5000

M9000 Description Workaround

Adapter UTP (QGC) & Sun Dual 10

This has been fixed in patch 139570-

01. GigE Fiber XFP Low Profile Adapter (XGF) NICs might panic under high load conditions.

[Workaround] If possible, use the card in x8 slot.

Otherwise, no workaround is available.

6689757 O O O Sun Dual 10 GigE Fiber XFP Low

Profile Adapter (XGF) with a single or improperly installed XFP optical transceivers might cause the following error to show on the console:

The XFP optical transceiver is broken or missing.

6725885 O cfgadm will display non-existent

M3000 system boards (SB1 to SB15).

This has been fixed in patch 139570-

01.

[Workaround] Check and make sure that both XFP

optical transceivers are firmly seated in the housing. Do not mix INTEL and Sun XFP optical transceivers in the same Adapter.

Do NOT plumb a port with the ifconfig command if the port does not contain an XFP optical transceiver or it contains one but the transceiver is not in use.

This has been fixed in patch 140401-

01.

[Workaround] The cfgadm output for SB1-SB15 can

be ignored.

Chapter 3 Information About Software 71

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/08

TABLE 3-12 lists issues that have been fixed in Oracle Solaris 10 10/08 OS. You might

encounter them in supported releases earlier than Oracle Solaris 10 10/08.

TABLE 3-12 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/08

M4000

CR ID M3000

6511374 O O Unexpected error messages may be

6533686 O O When XSCF is low on system

6535018 O In Oracle Solaris domains that include

6608404 O Hot-plug of the PCIe Quad-port

M8000

M5000

M9000 Description Workaround

displayed on console after changing the system configuration.

Example:

WARNING: Translation error source /LSB0/B0/0, PA 3c000000000, target /LSB0/B0/20000000

resources, DR operations involving relocating permanent memory, such as deleteboard(8) or moveboard(8), might fail with one or more of these errors:

SCF busy DR parallel copy timeout

This applies only to Quad-XSB configured system boards hosting multiple domains.

SPARC64 VII processors, workloads that make heavy use of the Oracle Solaris kernel might not scale as expected when you increase the thread count to a value greater than

256.

Gigabit Ethernet UTP Low Profile Adapter (X4447A-Z) in slot 1 might cause other network devices to fail.

This has been fixed in patch 137137-

09.

[Workaround] This message can be safely ignored.

This has been fixed in patch 138397-

01.

[Workaround] Retry the DR operation at a later time.

This has been fixed in patch 137111-

01.

[Workaround] For Oracle Solaris domains that

include SPARC64 VII processors, limit domains to a maximum of 256 threads.

To avoid the defect, do not install this adapter in slot 1.

72 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-12 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/08 (Continued)

M4000

CR ID M3000

6614737 O O The DR deleteboard(8) and

M8000

M5000

M9000 Description Workaround

moveboard(8) operations might hang

For Oracle Solaris 10 5/08 or earlier, this has been in patch 137111-01.

if any of the following conditions exist:

• A DIMM has been degraded.

• The domain contains system boards

[Workaround] Avoid performing DR operations if

any of the listed conditions exist.

with different memory size.

To determine whether the system contains degraded memory, use the XSCF showstatus(8) command. For sample output, see “Identifying

Degraded Memory in a System” on page 98.

To determine whether the domain contains system boards with different memory sizes, display the list of memory sizes using the XSCF

showdevices(8) command or the prtdiag(8) command on the domain.

For sample of output, see “Identifying

Different Memory Sizes in a System Board” on page 98

6619224 O For Oracle Solaris domains that

include SPARC 64 VII processors, a single domain of 256 threads (128 cores) or more might hang for an extended period of time under certain unusual situations. Upon recovery, the uptime command will show extremely high load averages.

If a DR command hangs, reboot the domain to recover.

This has been fixed in patch 137111-

03.

[Workaround] For Oracle Solaris domains that

include SPARC 64 VII processors, do not exceed a domain size of 256 virtual CPUs in a single Oracle Solaris domain. This means a maximum of 32 CPU chips in a single domain configuration (maximum configuration for an M8000 server).

Chapter 3 Information About Software 73

TABLE 3-12 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/08 (Continued)

M4000

CR ID M3000

6632549 O O fmd service on domain might fail to

M8000

M5000

M9000 Description Workaround

maintenance mode after DR

This has been fixed in patch 138050-

01.

operations.

[Workaround] If fmd service fails, issue the

following commands on the domain to recover:

# svcadm clear fmd

6660197 O O DR might cause the domain to hang if

either of the following conditions

This has been fixed in patch 138397-

01.

exist:

• A domain contains 256 or more CPUs.

• Memory error occurred and the DIMM has been degraded.

[Workaround]

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

set drmach:drmach_disable_mcopy = 1

1. Reboot the domain.

6679370 OOOThe following message may be output

on the console during the system booting, the External I/O Expansion Unit adding by hotplug, or the FMEMA operating by DR.

This has been fixed in patch 137137-

09.

Note - Before adapting the patch, delete the following setting from /etc/system:

set pcie_expected_ce_mask =

SUNW-MSG-ID: SUN4-8000-75,

0x2001

TYPE: Fault, VER: 1, SEVERITY: Critical

... DESC:

[Workaround] Add the following to /etc/system

and then reboot the domain.

A problem was detected in the PCI-Express subsystem.

Refer to

set pcie_expected_ce_mask = 0x2001

http://sun.com/msg/SUN4-800075 for more information.

...

74 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-12 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/08 (Continued)

M4000

CR ID M3000

6720261 OOOM4000/M5000/M8000/M9000

M8000

M5000

M9000 Description Workaround

servers:

This has been fixed in patch 137137-

09. If your domain is running one of the following versions of Oracle Solaris OS, the system might panic/trap during normal operation:

• Oracle Solaris 10 5/08 OS

• An earlier version of Oracle Solaris

10 OS with patch ID 127127-11

[Workaround] Set the following parameter in the

system specification file (/etc/system):

set heaplp_use_stlb=0

Then reboot the domain.

M3000 server: If your domain is running Oracle Solaris 10 5/08 OS, the system might panic/trap during normal operation:

Chapter 3 Information About Software 75

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/08

TABLE 3-13 lists issues that have been fixed in Oracle Solaris 10 5/08 OS. You might

encounter them in supported releases earlier than Oracle Solaris 10 5/08.

TABLE 3-13 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/08

M4000

CR ID M3000

5076574 O A PCIe error can lead to an invalid

6402328 O System panic might happen due to be

6472153 O O If you create an Oracle Solaris OS

M8000

M5000

M9000 Description Workaround

fault diagnosis on a large M8000/M9000 domain.

over the interrupt number limit when one domain has seven or more IOUA cards.

Flash archive on a nonM4000/M5000/M8000/M9000 sun4u server and install it on a M4000/M5000/M8000/M9000 sun4u server, the console's TTY flags will not be set correctly. This can cause the console to lose characters during stress.

For Oracle Solaris 10 8/07 or earlier, this has been fixed in patch 127127-11.

[Workaround] Create a file

/etc/fm/fmd/fmd.conf containing the following lines;

setprop client. buflim 40m setprop client. memlim 40m

For Oracle Solaris 10 8/07 or earlier, this has been fixed in patch 127127-11.

[Workaround] Use six or less IOUA cards on one

domain.

For Oracle Solaris 10 8/07 or earlier, this has been fixed in patch 137046-01.

[Workaround] Just after installing Oracle Solaris OS

from an Oracle Solaris Flash archive, telnet into the M4000/M5000/M8000/M9000 server to reset the console's TTY flags a follows:

# sttydefs -r console # sttydefs -a console -i

"9600 hupcl opost onlcr crtscts" -f "9600"

This procedure is required only once.

76 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-13 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/08 (Continued)

M4000

CR ID M3000

6505921 O Correctable error on the system PCIe

M8000

M5000

M9000 Description Workaround

bus controller generates an invalid fault.

For Oracle Solaris 10 8/07 or earlier, this has been fixed in 120011-14 and 125369-05.

[Workaround] Contact a qualified service engineer.

6522433 O O After the CPU hardware error

occurred, the fmdump(1M) command on the domain may display an incorrect faulty component.

6527811 O O The showhardconf(8) command on

the XSCF cannot display PCI card information that is installed in External I/O Expansion Unit, if the External I/O Expansion Unit is configured using PCI hotplug.

For Oracle Solaris 10 8/07 or earlier, this has been fixed in patch 127127-11.

[Workaround] Check system status on XSCF.

For Oracle Solaris 10 8/07 or earlier, this has been fixed in patch 128346-01.

[Workaround] No workaround is available.

Chapter 3 Information About Software 77

TABLE 3-13 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/08 (Continued)

M4000

CR ID M3000

6536564 O O showlogs(8) and showstatus(8)

M8000

M5000

M9000 Description Workaround

command on XSCF might report

For Oracle Solaris 10 8/07 or earlier,

this has been fixed in patch 125369-05. wrong I/O component due to wrong diagnosis by Oracle Solaris Fault management Architecture when faults in I/O devices occur.

[Workaround]

To avoid this problem, issue the

following commands on the domain.

# cd

/usr/platform/SUNW,SPARC-

Enterprise/lib/fm/topo/plugin

# mv ioboard.so

ioboard.so.orig

# svcadm restart fmd

If the following messages are

displayed on the domain, contact a

service engineer.

Example:

SUNW-MSG-ID: SUNOS-8000-1L,

TYPE: Defect, VER: 1,

SEVERITY: Minor

EVENT-TIME: Sun May 6

18:22:24 PDT 2007

PLATFORM: SUNW,SPARC-

Enterprise, CSN: BE80601007,

HOSTNAME: sparc

6545143 O O There is a low probability that a

system panic can occur during trap

For Oracle Solaris 10 8/07 or earlier,

this has been fixed in patch 127111-08. processing of a TLB miss for a user stack address. The problem can occur if the user stack is unmapped concurrently with the user process

[Workaround]

No workaround is available. executing a flush windows trap (ta

3). The panic message will contain the following string:

bad kernel MMU trap at TL 2

78 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-13 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/08 (Continued)

M4000

CR ID M3000

6545685 O O If the following message displayed on

M8000

M5000

M9000 Description Workaround

the OS console, memory degradation

For Oracle Solaris 10 8/07 or earlier,

this has been fixed in patch 127111-08. or XSB deconfiguration may occur in the subsequent reboot.

[Workaround]

Add the following to /etc/system Example:

mc-opl: WARNING: mc-opl rewrite timeout on /LSB0/B0

6546188 O O The system panics when running

hotplug (cfgadm(1M)) and DR

and then reboot the domain:

set mc-opl:

mc_max_rewrite_loop = 20000

For Oracle Solaris 10 8/07, this has

been fixed in patch 127741-01. operations (addboard(8) and deleteboard(8)) on the following adapters:

No workaround is available.

• PCIe Quad-port Gigabit Ethernet

UTP Low Profile Adapter (X4447AZ)

• PCIe Dual 10 Gigabit Ethernet Fiber

XFP Low Profile Adapter (X1027AZ)

6551356 O O The system panics when running

hotplug (cfgadm(1M)) to configure a

For Oracle Solaris 10 8/07, this has

been fixed in patch 127741-01. previously unconfigured adapter. The message "WARNING: PCI

Expansion ROM is not accessible" will be seen on the

console shortly before the system panic. The following cards are affected by this defect:

• PCIe Quad-port Gigabit Ethernet

UTP Low Profile Adapter (X4447A-

[Workaround]

Perform cfgadm -c disconnect to

completely remove the card. After

waiting at least 10 seconds, the card

may be configured back into the

domain using the cfgadm -c

configure command.

• PCIe Dual 10 Gigabit Ethernet Fiber

XFP Low Profile Adapter (X1027AZ)

Chapter 3 Information About Software 79

TABLE 3-13 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/08 (Continued)

M4000

CR ID M3000

6559504 O O Messages of the form nxge: "NOTICE:

M8000

M5000

M9000 Description Workaround

nxge_ipp_eccue_valid_check:

For Oracle Solaris 10 8/07, this has been fixed in patch 127741-01.

rd_ptr = nnn wr_ptr = nnn" will be

observed on the console with the following adapters:

[Workaround] These messages can be safely ignored.

• PCIe Quad-port Gigabit Ethernet UTP Low Profile Adapter (X4447AZ)

• PCIe Dual 10 Gigabit Ethernet Fiber XFP Low Profile Adapter (X1027AZ)

6564934 O O Performing a DR deleteboard(8)

operation on a board which includes

For Oracle Solaris 10 8/07, this has

been fixed in patch 127741-01. Permanent Memory when using the following adapters results in broken connections:

• PCIe Quad-port Gigabit Ethernet

UTP Low Profile Adapter (X4447AZ)

• PCIe Dual 10 Gigabit Ethernet Fiber

XFP Low Profile Adapter (X1027A-

[Workaround]

Re-configure the affected network

interfaces after the completion of the

DR operation. For basic network

configuration procedures, refer to the

ifconfig man page for more

information.

6568417 O O After a successful CPU DR

deleteboard(8) operation, the

For Oracle Solaris 10 8/07 or earlier,

this has been fixed in patch 127111-02. system panics when the following adapters are in use:

• PCIe Quad-port Gigabit Ethernet

UTP Low Profile Adapter (X4447AZ)

• PCIe Dual 10 Gigabit Ethernet Fiber

[Workaround]

Add the following line to

/etc/system and reboot the system:

set ip:ip_soft_rings_cnt=0

XFP Low Profile Adapter (X1027AZ)

6571370 O O Use of the following adapters have

been observed to cause data

For Oracle Solaris 10 8/07, this has

been fixed in patch 127741-01. corruption in stress test under laboratory conditions:

• PCIe Quad-port Gigabit Ethernet

UTP Low Profile Adapter (X4447AZ)

• PCIe Dual 10 Gigabit Ethernet Fiber

XFP Low Profile Adapter (X1027A-

[Workaround]

Add the following line in

/etc/system and reboot the system:

set

nxge:nxge_rx_threshold_hi=0

80 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-13 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/08 (Continued)

M4000

CR ID M3000

6584984 O On the M8000/M9000 servers,

6589546 O O prtdiag(8) command does not show

M8000

M5000

M9000 Description Workaround

busstat(1M) command may cause rebooting of domains.

all I/O devices of the following adapters:

• Sun StorageTek Enterprise Class 4Gb Dual-Port Fibre Channel PCIe HBA (XSEFC402AF)

• Sun StorageTek Enterprise Class 4Gb Single-Port Fibre Channel PCIe HBA (XSEFC401AF)

For Oracle Solaris 10 8/07 or earlier, this has been fixed in patch 127127-11.

No workaround is available. Do not use busstat(1M) command.

Check for the availability of a patch for this defect.

For Oracle Solaris 10 8/07 or earlier, this has been fixed in patch 127127-11.

[Workaround] Use prtdiag -v for full output.

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/07

TABLE 3-14 lists issues that have been fixed in Oracle Solaris 10 8/07 OS. You might

encounter them in supported releases earlier than Oracle Solaris 10 8/07.

Note – CR ID 6534471: Improper handling of large page in kernel memory may

cause random panics. Implement the workaround for CR ID 6534471 or check for the availability of a patch and install it immediately. This bug has been fixed by 12510006 and Oracle Solaris 10 8/07.

Chapter 3 Information About Software 81

TABLE 3-14 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/07

M4000

CR ID M3000

M8000

M5000

M9000 Description Workaround

6303418 O A M9000 server with a single domain

and 11 or more fully populated system boards might hang under heavy stress.

6416224 O O System performance can degrade

using a single NIC card with more than 5,000 connections.

6441349 O O The system may hang if there is an

I/O error in the system.

6485555 O O On-board Gigabit Ethernet NVRAM

corruption could occur due to a race condition.

The window of opportunity for this race condition is very small.

For Oracle Solaris 10 11/06, this has been fixed in patch 120011-01.

[Workaround] Do not exceed 170 CPU threads. Limit the number of CPU threads to

one per CPU core by using the Oracle Solaris psradm command to disable the excess CPU threads. For example, disable all odd-numbered CPU threads.

For Oracle Solaris 10 11/06, this has been fixed in patch 120011-08.

[Workaround] Use multiple NIC cards to split

network connections.

For Oracle Solaris 10 11/06, this has been fixed in patch 120011-07.

No workaround is available.

For Oracle Solaris 10 11/06, this has been fixed in patch 120011-08.

No workaround is available.

82 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

TABLE 3-14 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/07 (Continued)

M4000

CR ID M3000

6496337 O O The "cpumem-diagnosis" module may

M8000

M5000

M9000 Description Workaround

fail to load after uncorrectable

For Oracle Solaris 10 11/06, this has been fixed in patch 125369-05.

error(UE) panic. Systems will function correctly but

events normally automatically diagnosed by FMA using this module will require manual diagnosis.

Example:

SUNW-MSG-ID: FMD-8000-2K, TYPE: Defect, VER: 1, SEVERITY: Minor

EVENT-TIME: Thu Feb 15 15:46:57 JST 2007

[Workaround] If problem occurred, implement the

following workaround:

1. Remove the following file.

# rm /var/fm/fmd/ckpt/cpumemdiagnosis/cpumem-diagnosis

1. Restart fmd service. # svcadm restart fmd

PLATFORM: SUNW,SPARCEnterprise, CSN: BE80601007, HOSTNAME: col2-ff-em7-d0

To avoid this problem in advance, add "rm -f

/var/fm/fmd/ckpt/cpumemdiagnosis/cpumem-diagnosis" in /lib/svc/method/svc-dumpadm

file as below.

# We haven't run savecore on a dump device yet

# savedev=none

6498283 O O Using the DR deleteboard(8)

command while psradm operations are running on a domain might cause a system panic.

rm -f /var/fm/fmd/ckpt/cpumemdiagnosis/cpumem-diagnosis

For Oracle Solaris 10 11/06, this has been fixed in patch 120011-07.

[Workaround] No workaround is available.

Chapter 3 Information About Software 83

TABLE 3-14 Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/07 (Continued)

M4000

CR ID M3000

6499304 O O CPU isn't offlined and unexpected

M8000

M5000

M9000 Description Workaround

message is displayed on console when

For Oracle Solaris 10 11/06, this has been fixed in patch 125369-05.

many correctable error(CE) occurs. Example:

SUNW-MSG-ID: FMD-8000-11,

[Workaround] Check CPU status on XSCF.

TYPE: Defect, VER: 1, SEVERITY: Minor EVENT-TIME: Fri Feb 2 18:31:07 JST 2007

PLATFORM: SPARC-Enterprise, CSN: BE80601035, HOSTNAME: FF2-35-0

6502204 O O Unexpected error messages may be

displayed on console on booting after

For Oracle Solaris 10 11/06, this has been fixed in patch 125369-05.

CPU UE panic. Example:

SUNW-MSG-ID: FMD-8000-11, TYPE: Defect, VER: 1, SEVERITY: Minor EVENT-TIME: Tue Jan 9 20:45:08 JST 2007

[Workaround] If you see unexpected messages, use

the XSCF command showdomainstatus(8) to check system status on XSCF.

PLATFORM: SUNW,SPARCEnterprise, CSN: 2030636002, HOSTNAME: P2-DC1-16-d0

6502750 O O Notification message for inserted or

removed card by PCI hot plug may

For Oracle Solaris 10 11/06, this has been fixed in patch 120011-08.

not output.

No workaround is available.

6508432 O O Many correctable errors (CE) may

occur, and despite these are the

For Oracle Solaris 10 11/06, this has been fixed in patch 120011-08.

correctable errors, domain may panic.

[Workaround] Set the following to /etc/system

and then reboot the domain:

set pcie:pcie_aer_ce_mask = 0x2001

6508434 O O The domain may panic when an

additional PCI-X card is installed or a

For Oracle Solaris 10 11/06, this has

been fixed in patch 120011-08. PCI-X card is replaced by using PCI hot plug.

[Workaround]

Do not insert a different type of PCI-X

card on the same PCI slot by using

PCI hot plug.

84 SPARC Enterprise Mx000 Servers Product Notes for XCP Version 1124 • August 2018

Fujitsu M9000, M4000, M5000, M3000, M8000 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Preface

Audience

How to Use This Document

Related Documentation

Documentation CD

Information Required for Server Operation

Documentation Feedback

Software Requirements

XCP, Oracle Solaris OS and Required Patches

Obtaining XCP and Oracle Solaris Patches

Web Browser

Existing XCP Firmware Versions and Support Information

XCP 1124 and XCP 1124-related Information

What’s New in XCP 1124

Notes and Limitations

Limitations for SPARC64 VII+ and SPARC64 VII Processors

Notes on Secure Socket Layer (SSL) 3.0

Notes on SSH

Notes on Active Directory

Notes on LDAP/SSL

Notes on Power Consumption Monitoring Function (M3000 Server)

Notes on Airflow Indicator

Notes on NTP Server

Notes on the NTP Server Referring to the Local Clock

Notes on Timezones

Notes on XSCF Web

Limitations on Audit

Miscellaneous Notes and Limitations

XCP 1124 Issues and Workarounds

Updating to XCP 1124

Importing the XCP File

Updating from a Version Earlier Than XCP 1050 (M4000/M5000/M8000/M9000 Servers)

Updating from a Version Earlier Than XCP 1070 (M8000/M9000 Servers)

Information About Software

Notes and Limitations

Notes on RCI Function

Notes on Remote Maintenance

Before Setting the Remote Maintenance Service

The Timezone Setting for REMCS Agent Function

XCP Issues and Workarounds

Known Issues and Workarounds in XCP 1124

XCP Issues Fixed in XCP 1124

XCP Issues Fixed in XCP 1123

XCP Issues Fixed in XCP 1122

XCP Issues Fixed in XCP 1121

XCP Issues Fixed in Releases Earlier Than XCP 1121

Oracle Solaris OS Issues and Workarounds

Oracle Solaris Issues and Workarounds for All Supported Releases

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/11

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 9/10

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/09

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/09

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 10/08

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 5/08

Oracle Solaris OS Issues Fixed in Oracle Solaris 10 8/07