Fujitsu M10, SPARC M10 Product Notes

Download

Page 1

Fujitsu M10/SPARC M10 Systems

Product Notes for XCP Version 2240

Manual Code: C120-0012-02EN March 2015

Page 2

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 described in this document, and such products,

technology and this document are protected by copyright laws, patents, and other intellectual property laws and international treaties.

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

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

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

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

registered trademark of The Open Group.

UNIX

is a

Oracle

and Java are registered trademarks of Oracle and/or its affiliates.

Fujitsu

and the Fujitsu logo are registered trademarks of Fujitsu Limited.

SPARC

Enterprise, SPARC64, SPARC64 logo and all SPARC trademarks are trademarks or registered trademarks of SPARC International, Inc. in the United States and other

countries and used under license.

names may be trademarks of their respective owners.

Other If

this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S.

GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered

U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,

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

Copyright Oracle Oracle même, ces produits, technologies et ce document sont protégés par des lois sur le droit d’auteur, des brevets, et d'autres lois sur la propriété intellectuelle et des traités internationaux. Ce 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 affiliés et de Fujitsu Limited, et de leurs éventuels concédan ts de licence. Ce document, bien qu'il vous ait été fourni, ne vous confère aucun droit et aucune licence, exprès 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 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ère s. Conformément Veuillez contacter Oracle et/ou ses affiliés ou Fujitsu Limited. Cette distribution peut comprendre des composants développés par des parties tierces. Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie. UNIX Oracle Fujitsu SPARC dans d'autres pays. Tout Si compte du Gouvernement des Etats-Unis, la notice suivante s'applique : U.S.

use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. Avis 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 ENTITE DECLINENT TOUT ENGAGEMENT OU GARANTIE, QUELLE QU'EN SOIT LA NATURE (EXPRESSE OU IMPLICITE) CONCERNANT CE PRODUIT, CETTE TECHNOLOGIE OU CE DOCUMENT, LESQUELS SONT FOURNIS EN L'ETAT. EN OUTRE, TOUTES LES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON, SONT EXCLUES, DANS LA MESURE AUTORISEE 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 EXCLUE, DANS LA MESURE AUTORISEE PAR LA LOI EN VIGUEUR, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE,

The only warranties granted by Oracle and Fujitsu Limited, and/or any affiliate in connection with this document or any product or technology described herein are those

EXPRESSLY SET FORTH IN SUCH AGREEMENT, ORACLE OR FUJITSU LIMITED, AND/OR THEIR AFFILIATES MAKE NO REPRESENTATIONS OR WARRANTIE

ANY KIND (EXPRESS OR IMPLIED) REGARDING SUCH PRODUCT OR TECHNOLOGY OR THIS DOCUMENT, WHICH ARE ALL PROVIDED AS IS, AND ALL EXPRESS

IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS

PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED

et/ou ses affiliés ont fourni et vérifié des données techniques de certaines parties de ce composant. et/ou ses affiliés et Fujitsu Limited détiennent et contrôlent chacun des droits de propriété intellectuelle relatifs aux produits et technologies décrits dans ce document. De

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.

soit, de la part d'Oracle ou de Fujitsu Limited, ou des sociétés affiliées de l'une ou l'autre entité.

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 le droit d’auteur et/ou cédés sous

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.

est une marque déposée de The OpenGroup.

Java sont des marques déposées d'Oracle Corporation et/ou de ses affiliés.

logo Fujitsu sont des marques déposées de Fujitsu Limited.

et le

Enterprise, SPARC64, le logo SPARC64 et toutes les marques SPARC sont utilisées sous licence et sont des marques déposées de SPARC International, Inc., aux Etats-Unis et

autre nom mentionné peut correspondre à des marques appartenant à leurs propriétaires respectifs.

logiciel, ou la documentation qui l'accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence de ce logiciel ou l'utilise pour le

GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered

U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,

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

MENTION CONTRAIRE EXPRESSEMENT STIPULEE AU DIT CONTRAT, ORACLE OU FUJITSU LIMITED ET/OU LES SOCIETES AFFILIEES A L'UNE OU L'AUTRE

DOCUMENTATIO N EST FOURNIE "EN L'ETAT" ET TOUTE AUTRE CONDITION, DECLARATION ET GARANTIE, EXPRESSE OU TACITE, EST FORMELLEMENT

L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.

Page 3

Preface　ix

Chapter 1　Software Requirements　1

XCP/Oracle Solaris and Required SRU/Patch　1

Notes on using Oracle Solaris 10　4

Notes when using a version older than Oracle VM Server for SPARC

3.1.0.1　4

Required XCP/Oracle Solaris and required SRU/patch to enable

dynamic reconfiguration of physical partition　5

Required XCP/Oracle Solaris and required SRU/patch

dynamic reconfiguration of PCIe endpoint device　5

Software supporting Software on Chip　6

How to Obtain XCP and Oracle Solaris SRU/Patch/Oracle VM Server for

SPARC　7

Web Browser　7

Existing XCP Firmware Versions and Support Information　7

Chapter 2　XCP 2240-Related Information　11

Latest Information on XCP 2240　11

Notes and Restrictions

Notes on Secure Socket Layer (SSL) 3.0　12

Restrictions on audit　12

Notes on dynamic reconfiguration of physical partitions　12

enable

iii

Page 4

Notes on mixing SPARC64 X+ processors with SPARC64 X processors

Notes and restrictions on the SR-IOV functions　13

Notes on OpenBoot PROM　14

Notes on maintenance for CPU memory units, motherboard unit, XSCF

unit, PSU backplane, or crossbar backplane unit　15

Notes on CPU Activation　17

Notes and restrictions on XSCF Web

Notes on firmware update　19

Notes on configurations with a PCI expansion unit connected　21

Notes on dual power feed setting　23

Notes on Active Directory　23

Notes on LDAP over SSL　23

Notes on the logical domain time　24

Notes on Timezones　26

Notes on power supply interlock function (RCIL)　26

Other notes

and restrictions　27

XCP 2240 Problems and Workarounds　32

Chapter 3　Information on Software　33

Notes and Restrictions　33

Notes on support for disks with an EFI (GPT) label　33

Notes on Oracle VM Server for SPARC　34

Notes on live migration of Oracle VM Server for SPARC　35

Notes on a case when

recovery mode of Oracle VM Server for SPARC is

enabled　37

Notes on a case where openssl is used　38

Notes on remote maintenance service　39

Notes on SNMP　40

Problems with XCP and Workarounds　41

Problems that might occur with XCP 2240 and workarounds　41

Problems resolved in XCP 2240　83

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 2015iv

Page 5

Problems resolved in XCP 2232　90

Problems resolved in XCP 2231　90

Problems resolved in XCP 2230　90

Problems resolved in XCP 2221　96

Problems resolved in XCP 2220　96

Problems resolved in XCP 2210　106

Problems resolved in XCP 2092　114

Problems resolved in XCP 2091　115

Problems resolved in XCP 2090　116

Problems

resolved in XCP 2080　125

Problems resolved in XCP 2070　128

Problems resolved in XCP 2052　139

Problems resolved in XCP 2051　139

Problems resolved in XCP 2050　140

Problems resolved in versions prior to XCP 2050　145

Problems with Oracle Solaris and Workarounds　159

Problems that might occur in any versions of Oracle

workarounds　159

Problems that might occur with Oracle Solaris 11 and workarounds

166

Problems that might occur with Oracle Solaris 10 and workarounds

168

Problems resolved in Oracle Solaris 11.2　168

Chapter 4　Information on SPARC M10-1 Hardware　179

Notes and Restrictions　179

Notes on using external DVD drive　179

Solaris and

Notes on

using USB memory　179

Problems with Hardware and Workarounds　180

Chapter 5　Information on SPARC M10-4 Hardware　181

Notes and Restrictions　181

Notes on using external DVD drive　181

Contents v

Page 6

Notes on using USB memory　181

Problems with Hardware and Workarounds　182

Chapter 6　Information on SPARC M10-4S Hardware　183

Notes and Restrictions　183

Notes on using external DVD drive　183

Notes on using USB memory　183

Restrictions on replacing crossbar box　184

Restrictions on adding expansion rack 2　185

Problems with Hardware and Workarounds

185

Chapter 7　Information on PCI Expansion Unit Hardware　187

Direct I/O Function for the PCI Expansion Unit　187

Setting/displaying the direct I/O function　187

Problems with PCI Expansion Units and Workarounds　188

Problems and their workarounds for all versions of the PCI expansion

unit firmware　188

Problems resolved in version 1180 of

189

the PCI expansion unit firmware

Problems resolved in version 1170 of the PCI expansion unit firmware

191

Problems resolved in version 1150 of the PCI expansion unit firmware

195

Problems resolved in version 1130 of the PCI expansion unit firmware

196

Problems resolved in version 1120 of the PCI expansion unit firmware

198

Problems resolved in version 1110 of the PCI expansion unit firmware

198

Problems resolved in version 1100 of the PCI expansion unit firmware

199

Chapter 8　Contents of Revision of Documentation　201

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 2015vi

Page 7

Fujitsu M10/SPARC M10 Systems Safety and

Contents of Revision of

Compliance Guide

201

PSU Detail Information of ErP directive Lot 3　202

Contents vii

Page 8

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 2015viii

Page 9

Preface

This document describes the latest information about XSCF Control Package (XCP) and the important and latest information regarding hardware, firmware, software, and documents of SPARC M10 Systems.

Note -

If a newer version of XCP than the version supported in this document is released, only the document supporting the latest version of XCP is updated. In addition to reading this document, visit the following websites to see the document supporting the latest version of XCP. Check the contents and documents related to XCP version that you use.

■

Japanese site

http://jp.fujitsu.com/platform/server/sparc/manual/

■

Global site

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

Fujitsu M10 is sold as SPARC M10 Systems by Fujitsu in Japan. Fujitsu M10 and SPARC M10 Systems are identical products.

usage to confirm whether there are any corrections in the

This preface includes the

■

Audience

■

How to Use This Document

■

How to Use This Document

This document supports all models of SPARC M10 Systems. Depending on the server you use, read the related items listed in the following table.

Chapter titles in this document SPARC M10-1 SPARC M10-4 SPARC M10-4S

Chapter 1 Software Requirements xxx

Chapter 2 XCP 2240-Related Information xxx

Chapter 3 Information on Software xxx

Chapter 4 Information on SPARC M10-1 Hardware x

Chapter 5 Information on SPARC M10-4 Hardware x

Chapter 6 Information on SPARC M10-4S Hardware x

Chapter 7 Information on PCI Expansion Unit Hardware x (when

introduced)

Chapter

Contents of Revision of Documentation xxx

The information about firmware and software, which are described in Chapter 1,

Chapter 2, and Chapter 3, is common to all models. Some of the information

related to a specific model. In such case, the applicable model name is indicated.

The information about hardware devices is provided in Chapter 4, Chapter 5, and

Chapter 6 separately for each model. The contents common to all models are

described in all chapters describing hardware. Therefore, hardware information about multiple models, you will find that some contents are duplicated in some chapters.

Check the information on the PCI expansion unit (Chapter 7) when the PCI expansion unit is introduced.

Contents of revision of documents (Chapter 8) are provided in each document. Check whether the contents of your document have been revised.

x (when introduced)

when you check the

x (when introduced)

are only

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 2015x

Page 11

Disposal and recycling

Note -

This information is applicable to SPARC M10 systems sold within Japan by Fujitsu.

For product disposal and recycling (paid service), contact your sales representatives.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 2015xii

Page 13

Documentation Feedback

If you have any comments or requests regarding this document, please take a moment to share it with us by indicating the manual code, manual title, and page, and stating your points specifically through the following websites:

■

Japanese site

http://jp.fujitsu.com/platform/server/sparc/manual/

■

Global site

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

Preface xiii

Page 14

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 2015xiv

Page 15

Chapter 1

Software Requirements

This chapter describes the software requirements for using SPARC M10 Systems.

■

XCP/Oracle Solaris and Required

XCP/Oracle Solaris and Required SRU/Patch

How to Obtain XCP and Oracle Solaris SRU/Patch/Oracle VM Server for SPARC

Web Browser

Existing XCP Firmware Versions and Support Information

SRU/Patch

The following lists XCP, Oracle Solaris, and required SRU/patch supported on SPARC M10 Systems.

Table 1-1

Server XCP Oracle Solaris Required packages(*4)

SPARC M10-1

SPARC64

X+

3.2 GHz

SPARC64 X

2.8 GHz

XCP, Oracle Solaris, and required SRU/patches supported by the SPARC M10 system

Required products(*5)

2210 or later

2012 or later

Oracle Solaris 11.2 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 11.1 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 10 1/13 Oracle VM Server for SPARC 3.0 or

later(*3)

Oracle Solaris 11.2 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 11.1 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 10 1/13 Oracle VM Server

later(*3)

for SPARC 3.0 or

Required SRU(*4) Required patch(*5)

None

SRU1.4 or later(*3)

150310-02 or later

None

SRU1.4 or later(*3)

150310-02 or later

Page 16

Table 1-1

Server XCP Oracle Solaris Required packages(*4)

XCP, Oracle Solaris, and required SRU/patches supported by the SPARC M10 system (continued)

Required products(*5)

SPARC M10-4

SPARC64

X+

3.4 GHz

2210 or later

Oracle Solaris 11.2 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 11.1 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 10 1/13 Oracle VM Server for SPARC 3.0 or

later(*3)

SPARC64 X

2.8 GHz

2012 or later

Oracle Solaris 11.2 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 11.1 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 10 1/13 Oracle VM Server

later(*3)

SPARC M10-4S (Direct inter-chassis connection)

SPARC64

X+

3.7 GHz

2210 or later

Oracle Solaris 11.2 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 11.1 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

SPARC64 X

3.0 GHz

2031 or later

Oracle Solaris 10 1/13(*6)

Oracle Solaris 11.2 system/ldoms(*1)

Solaris 11.1 system/ldoms(*1)

Oracle

Oracle VM Server for SPARC 3.0 or later(*3)(*7)(*8)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 10 1/13(*6)

Oracle VM Server for SPARC 3.0 or later(*3)(*7)(*8)

SPARC M10-4S (Connection through crossbar box)

SPARC64

X+

3.7 GHz

2210 or later

Oracle Solaris 11.2 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 11.1 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

SPARC64 X

3.0 GHz

2043 or later

Oracle Solaris 10 1/13(*6)

Oracle Solaris 11.2 system/ldoms(*1)

Oracle VM Server for SPARC 3.0 or later(*3)(*7)(*8) 150310-02 or

system/ldoms/ldomsmanager(*2)

Oracle Solaris 11.1 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

for SPARC 3.0 or

Required SRU(*4) Required patch(*5)

None

SRU1.4 or later(*3)

150310-02 or later

None

SRU1.4 or later(*3)

150310-02 or later

None

SRU1.4 or later(*3)(*7)

150310-02 or later(*8)

None

SRU1.4 or later(*3)(*7)

150310-02 or later(*8)

None

SRU1.4 or later(*3)(*7)

later(*8)

None

SRU1.4 or later(*3)(*7)

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 20152

Page 17

Table 1-1

Server XCP Oracle Solaris Required packages(*4)

*1 Required for the control domain and the guest domain. Included in group/system/solaris-large-server and group/system /s ol aris-small-server.

*2 Required only for the control domain. Included in group/system/solaris-large-server and group/system/solaris-small-server. *3 Required only for the control domain. *4 For Oracle Solaris 11. *5 For Oracle Solaris 10. *6 If Oracle Solaris 10 1/13 is to be run in the control domain, the CPUs that can be assigned to the control domain

*7 Refer to "Notes when using a version older than Oracle VM Server for SPARC 3.1.0.1". *8 Refer to "Notes on using Oracle Solaris 10".

XCP, Oracle Solaris, and required SRU/patches supported by the SPARC M10 system (continued)

Required products(*5)

Oracle Solaris 10 1/13(*6)

mounted on logical system boards with LSB numbers 0 to 7. There are no LSB number limitations on the CPUs that can be assigned to the guest domain. If the Oracle Solaris 10 1/13 is run in the guest domain, however, up to 1024 CPUs guest domain.

Note -

When Oracle Solaris 11.1/Oracle Solaris 11.2 is installed or booted from DVD media in

Oracle VM Server for SPARC 3.0 or later(*3)(*7)(*8)

(vcpus) can be assigned to a single

Required SRU(*4) Required patch(*5)

150310-02 or later(*8)

are those CPUs that are

a SPARC M10 system, the following two messages are displayed. Ignore these messages because they have no impact on installation work.

[Message example 1] Dec 21 02:18:22 solaris genunix: NOTICE: core_log: ldmd[1978] core dumped: /tmp/core Dec 21

02:18:22 solaris svc.startd[9]: ldoms/ldmd:default failed fatally: transitioned to

maintenance (see 'svcs -xv' for details)

[Message example 2] SUNW-MSG-ID: SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major EVENT-TIME: Fri Dec 21 02:18:50 UTC 2012 PLATFORM: ORCL,SPARC64-X, CSN: 2081210008, HOSTNAME: solaris SOURCE: software-diagnosis, REV: 0.1 EVENT-ID: 5cf4edb8-0613-cbe0-acb1-a9a28a2fac10 DESC: A service failed - a start, stop or refresh

method failed. AUTO-RESPONSE: The service has been placed into the maintenance state. IMPACT: svc:/ldoms/ldmd:default is unavailable. REC-ACTION: Run 'svcs -xv svc:/ldoms/ldmd:default' to determine the generic reason why the service failed, the location of any logfiles, and a list of other services impacted. Please refer to the associated reference document at http://support.oracle.com/msg/SMF-8000-YX for the

latest service procedures and policies regarding this diagnosis.

Chapter 1　Software Requirements 3

Page 18

Note -

When Oracle Solaris 11.1 is installed in SPARC M10 Systems, the following message

appears at the start of Oracle Solaris.

[Example of message] WARNING: failed to instantiate provider ldmd for process 753 WARNING: failed to instantiate provider ldmd for process 753 Sep 24 06:15:59 svc.startd[11]: svc:/ldoms/ldmd:default: Method "/opt/SUNWldm/bin/ldmd_ start" failed with Sep 24 06:15:59 svc.startd[11]: ldoms/ldmd:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)

After Oracle Solaris 11.1 is installed, apply SRU1.4 or later. Then, the Oracle VM Server for SPARC package is updated to the version supporting SPARC M10 Systems, and such message will no longer be output.

exit status 95.

For other information about Oracle Solaris, see "Problems with Oracle Solaris and

Workarounds."

Notes on using Oracle Solaris 10

■

[SPARC M10-4S] When the control domain is running on Oracle Solaris 10 with Oracle VM Server

for SPARC version 3.1.0.1 or older, if the physical partition dynamic reconfiguration

(PPAR DR) feature is enabled, the ldoms/ldmd service fails to start and Oracle VM for SPARC does not work.

The PPAR DR feature is enabled at the time of shipment. Therefore, either disable the PPAR DR feature before setting up logical domains, or, update Oracle VM Server for SPARC to

Configuration of the PPAR DR feature is performed with the setpparmode(8) command of XSCF firmware. For details on the setpparmode(8) command, refer to Fujitsu M10/SPARC M10 Systems XSCF Reference Manual.

To update Oracle VM Server for SPARC version to 3.1.0.1, apply patch no. 150817-01 after installing Oracle

■

[SPARC M10-4S] When Oracle Solaris 10 is running on the control domain, in order to perform dynamic reconfiguration of physical partitions (PPAR DR) with the

deleteboard(8), addboard(8) commands, update to Oracle VM Server for SPARC

3.1.1 or newer. When updating to 3.1.1, apply patch 150817-02 after installing Oracle VM Server for

version 3.1.0.1 or later.

Server for SPARC 3.1.

SPARC 3.1.

Notes when using a version older than Oracle VM Server for SPARC 3.1.0.1

[SPARC M10-4S] When the physical partition dynamic reconfiguration (PPAR DR) feature is enabled

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 20154

Page 19

on an

Oracle VM Server for SPARC version that is older than 3.1.0.1, the ldoms/ldmd service fails to start and thus Oracle VM Server for SPARC does not function. If using an Oracle VM Server for SPARC version that is older than 3.1.0.1, disable the PPAR DR feature before setting Configuration of the PPAR DR feature is performed with the setpparmode(8) command of XSCF firmware. For details on the setpparmode(8) command, refer to Fujitsu M10/SPARC M10 Systems XSCF Reference Manual. Meanwhile, in case of Oracle Solaris 11, Oracle VM Server for SPARC 3.1.0.1 is included in SRU11.1.14.

up logical domains.

Required XCP/Oracle Solaris and required SRU/patch to enable dynamic reconfiguration of physical partition

The following lists XCP, Oracle Solaris, and required SRU/patch to enable dynamic reconfiguration of physical partition.

Table 1-2

Server XCP Oracle Solaris Required packages

SPARC M10-4S

*1 Required for the control domain and the guest domain. Included in group/system/solaris-large-server and group/system/solaris-smallserver. *2 Required only for the control domain. Included in group/system/solaris-large-server and group/system/solaris-small-server. *3 Required for the control domain and the guest domain. Though SRU11.1.14 includes Oracle VM Server for SPARC 3.1.0.1, the modification for Solaris 11.1 to SRU11.1.15 and later. *4 Required only for the control domain. *5 Do not apply patch 150400-01 to 150400-06.

List of XCP, Oracle Solaris, and required SRU/patches needed for physical partition dynamic reconfiguration

Required products

2220 or later

Oracle Solaris 11.2 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 11.1 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 10 1/13 Oracle VM Server for SPARC 3.1(*4) 150817-02 or

fix BugID#17709858 is required to ensure stable DR functionality. This issue has been resolved in

Required SRU Required patch

None

SRU11.1.14 or later(*3)

later(*4)(*5)

Required XCP/Oracle Solaris and required SRU/patch to enable dynamic reconfiguration of PCIe endpoint device

The following lists XCP, Oracle Solaris, and required SRU/patch to enable dynamic reconfiguration of PCIe endpoint device.

Chapter 1　Software Requirements 5

Page 20

Table 1-3

Server XCP Oracle Solaris Required packages

SPARC M10-1 SPARC M10-4

SPARC M10-4S

List of XCP, Oracle Solaris, and SRU/patches needed for dynamic reconfiguration of PCIe endpoint device

Required SRU Required patch

SRU11.2.2 or later

2230 or later

Required products

Oracle Solaris 11.2 system/ldoms(*1)

system/ldoms/ldomsmanager(*2)

Oracle Solaris 11.1(*4) system/ldoms(*1) SRU11.1.17 or

later(*3)

Oracle Solaris 10 1/13 Oracle VM for SPARC 3.1(*5)(*6) 150817-03 or

later(*5)

*1 Required for the control domain and other domains. Included in group/system/solaris-large-server and group/system/solaris-small-server.

*2 Required only for the control domain. Included in group/system/solaris-large-server and group/system/solaris-small-server. *3 Required for the control domain and other domains. *4 Can be used only in domains other than the control domain. *5 Required only for the control domain. *6 There are patches required other than the Oracle VM Server for SPARC Oracle VM Server for SPARC 3.1.1.1" in the Oracle VM Server for SPARC 3.1.1.1, 3.1.1, and 3.1 Release Notes.

patch. For details, see "Required Oracle Solaris OS Versions for

Software supporting Software on Chip

The Software on Chip (SoC) on the SPARC64 X+/SPARC64 X processor can be used with the software below.

When used with Oracle Database

Table 1-4

Function Operating environment

The decimal floating-point arithmetic processing (Oracle Number)

SIMD (In-memory processing) Oracle Database 12c Enterprise Edition

Cryptographic processing Oracle Database 12c Enterprise Edition

Software supporting Software on Chip (when used with Oracle Database)

Oracle Database 12c or later Oracle Solaris 11.1 or later

Oracle Database In Memory Oracle Solaris 11.1 or later

Oracle Advanced Security Oracle Solaris 11.1 or ;ater

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 20156

Page 21

When used with user application

Table 1-5

Function Operating environment

The decimal floating-point arithmetic processing (IEEE754)

SIMD

Software supporting Software on Chip (when used with user application)

Oracle Solaris Studio 12.4 or later Oracle Solaris 11.2 SRU12.2.4 or later

How to Obtain XCP and Oracle Solaris SRU/Patch/Oracle VM Server for SPARC

The customers who subscribed SupportDesk can obtain the latest XCP firmware and Oracle Solaris SRU/patch/Oracle VM Server for SPARC from the SupportDesk-Web.

Web Browser

Table 1-6 lists the web browsers on which the XSCF Web operation is confirmed. For

other information about XSCF Web, see "Notes and restrictions on XSCF Web."

Table 1-6

Web browser Version

Microsoft Internet Explorer 8.0, 9.0, 10.0, and 11.0

Firefox 10.0 or later

Version of web browser of which operation has been confirmed

Existing XCP Firmware Versions and Support Information

The following lists the XCP firmware versions that have been released for the SPARC

Chapter 1　Software Requirements 7

Page 22

M10 System, as well as the main support and update information for each version.

Table 1-7

XCP version Main support information CMU version

XCP 2240 - Support for the DNS round-robin for the host name of the

Existing XCP firmware versions and support information

NTP server

02.24.0000

- Support for 1984 LDC endpoints per guest domain

- Support for Dynamic PCIe bus assignment provided with Oracle VM Server for SPARC 3.2

XCP 2232 Security fixes 02.23.0000

XCP 2231 Security fixes 02.23.0000

XCP 2230 - Support for Internet Explorer 10 and

11 in

XSCF Web

02.23.0000

- Support for Extensible Firmware Interface GUID Partition Table (EFI GPT) labels

- Support for recovery mode provided by Oracle VM Server for SPARC 3.1

- Support for the function for dynamically reconfiguring PCIe endpoint devices through combination with Oracle

Server for SPARC

- Support for Oracle

Solaris kernel zones

XCP 2221 Improvement of XCP firmware defects 02.22.0000

XCP 2220 - Support of the dynamic reconfiguration (DR) function of

the system board in a physical partition (PPAR)

02.22.0000

- Support for XSCF startup mode function (SPARC M10-1)

XCP 2210 - Support for SPARC64 X+ processors

- Support for CPU operational mode which specifies how CPU should operate

02.21.0000

- Enable the factory default configuration for the dynamic reconfiguration of physical partitions feature.

- The LDAP, Active Directory, LDAP over SSL features have been supported for the XSCF user account

- The SR-IOV feature in combination with Oracle VM Server for SPARC, has been supported

- The "no-io" has been supported

feature when configuring physical partition

XCP 2092 Improvement of XCP firmware defects 02.09.0000

XCP 2091 Improvement of XCP firmware defects 02.09.0000

XCP 2090 - Support of 64 GB memory

02.09.0000

- Support of multiple specifications of the port and community string for the Trap host of the SNMP agent function

- Support for automatic XCP firmware version synchronization

between chassis when maintenance is done in off state of the input power supply

XCP 2080 Support of the Auto Service Request (ASR) function 02.08.0000

XCP 2070 Improvement of XCP firmware defects 02.07.0000

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 20158

Page 23

Table 1-7

XCP version Main support information CM U version

XCP 2052 - Support of the AES algorithm encryption function for the

Existing XCP firmware versions and support information (continued)

SNMP agent function

02.05.0002

- Support of different memories in the chassis

XCP 2051 Improvement of XCP firmware defects 02.05.0001

XCP 2050 Support of the direct I/O function for the PCI expansion

unit (SPARC M10-4S)

XCP 2044 Support of the direct I/O function for the PCI

unit (SPARC M10-1/M10-4)

expansion

02.05.0000

02.04.0004

XCP 2042 Support of the crossbar box (configuration of up to 16 BB) 02.04.0001

XCP 2041 Support of the PCI expansion unit 02.04.0001

XCP 2032 Improvements related to the Oracle VM Server for SPARC

software

02.03.0001

XCP 2031 Support of SPARC M10-4S (configuration of up to 4 BB) 02.03.0001

XCP 2013 Improvement of XCP firmware defects 02.01.0003

XCP 2012 Support of SPARC M10-1/M10-4 02.01.0002

Note -

When the CMU firmware version is updated, turn off the power of the physical partition and then turn it on again to complete the CMU firmware update. For details on firmware update, see "16.1 Updating the XCP Firmware" in the Fujitsu M10/SPARC M10 Systems System Operation and Administration Guide.

Note -

The CMU firmware version may differ with the XCP version. For example, in XCP 2042, the XSCF version is 02.04.0002, whereas the CMU version is

02.04.0001.

Chapter 1　Software Requirements 9

Page 24

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201510

Page 25

Chapter 2

XCP 2240-Related Information

This chapter provides XCP 2240-related information.

■

Latest Information on XCP 2240

This section describes major changes in XCP 2240. This XCP version modifies XSCF firmware and CMU firmware.

Latest Information on XCP 2240

Notes and Restrictions

XCP 2240 Problems and Workarounds

Note -

After the firmware update completes, power-off/power-on of the physical partition may be required. For details on firmware update, see "16.1 Updating the XCP Firmware" in the Fujitsu

10/SPARC M10 Systems System Operation and Administration Guide.

■

If XSCF is an NTP client, the DNS round-robin applied to the NTP server can be used. For details, see the setntp(8) command and the showntp(8) command in Fujitsu M10/SPARC M10 Systems XSCF Reference Manual.

■

The maximum number of logical domain channels (LDC) which can be specified per guest domain has been expanded from 768 to 1984. For details on logical domain channels, see Oracle VM Server for SPARC Release

Notes of the version you are using.

■

Dynamic PCIe bus assignment provided with Oracle VM Server for SPARC 3.2 is supported. For details, see "Dynamic PCIe Bus Assignment" in Oracle VM Server

for SPARC 3.2 Administration Guide and Oracle VM Server for SPARC 3.2 Release Notes.

Page 26

Notes and Restrictions

This section describes notes and restrictions that are known as of this release.

Notes on Secure Socket Layer (SSL) 3.0

For security reasons, you cannot use SSL 3.0 with XCP 2240 or later. Use Transport Layer Security (TLS) 1.0.

Restrictions 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 problem, see

Notes on dynamic reconfiguration of physical partitions

"RTIF2-141208-001."

■

In case of dynamic reconfiguration of physical partitions, when adding an I/O device, it is necessary to either stop the domain or use the delayed reconfiguration feature to integrate the I/O device into the logical domain, after executing the addboard(8) command. Moreover, when removing an I/O device, after removing the I/O stopping the domain or using the delayed reconfiguration feature, execute the deleteboard(8) command in order to disconnect the system board. For details on each procedure, refer to the Fujitsu M10/SPARC M10 Systems Domain Configuration Guide.

Note that you can add and delete I/O devices without stopping the logical domains later.

■

After dynamic reconfiguration of a physical partition, the execution results of prtdiag(1M) command executed from the control domain may differ from the actual physical configuration. Executing "svcadm restart picl" can update to the latest information.

■

While adding or removing system boards with the addboard(8) or deleteboard(8) command of the DR feature, do not reboot all the XSCFs with either the "rebootxscf -a" command or from the XSCF Web interface. If such an operation is

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

and without delayed reconfiguration on Oracle Solaris 11.2 SRU11.2.8 or

･

device by

March 201512

Page 27

performed, not only the DR processing will terminate abnormally, Oracle Solaris

on a

running physical partition may hang, hardware failure may occur, physical

partitions may stop abnormally and replacement of parts may become necessary.

■

If even one logical domain in the OpenBoot PROM state is situated in the physical partition, dynamically reconfiguring the physical partition causes it to end with an error. Execute dynamic reconfiguration of the physical partition after changing the logical domain to any of the following states: state where Oracle Solaris is running, bound state, or inactive state.

■

Do not specify either "unbind=resource" or "unbind=shutdown" at the "-m" option

the deleteboard(8) command when executing dynamic reconfiguration of physical partitions where the version of Oracle VM Server for SPARC is earlier than 3.2, as there is a chance of the logical domain to hang or the deleteboard(8) command to Due to this problem, memory module (DIMM) of different capacities cannot be mounted on a chassis, which is the target of the dynamic reconfiguration of physical partitions. Make sure that the mounted memory modules (DIMMs) on chassis whose physical partition is the target of dynamic reconfiguration, are all of

same capacity.

the

Meanwhile, there is no problem if the number of DIMMs differs from chassis to chassis.

■

Do not apply patches 150400-01 to 150400-06 on Oracle Solaris 10. In such a case, dynamic reconfiguration of physical partitions may cause system panic (CR

17510986).

fail.

Notes on mixing SPARC64 X+ processors with SPARC64 X processors

To mix SPARC64 X+ processors with SPARC64 X processors, configure each type in a unit of the SPARC M10 system chassis, which is the system board configuration unit. SPARC64 X+ processors cannot be mixed with SPARC64 X processors and mounted together inside each chassis in the SPARC M10 system. In the there are systems configured with the CPU memory unit lower (CMUL) and CPU memory unit upper (CMUU). These units must have the same processor.

SPARC M10-4/M10-4S,

Notes and restrictions on the SR-IOV functions

Notes

■

If the maintenance of PCI Express (PCIe) cards that use the SR-IOV function is performed either with dynamic reconfiguration (DR) of physical partitions or with PCI hot plugging (PHP), execute the following procedure beforehand:

1. Remove all virtual functions (VF) from the I/O domains by executing the "ldm

remove-io" command.

Chapter 2　XCP 2240-Related Information 13

Page 28

2. Destroy all virtual functions (VF) by executing the "ldm destroy-vf" command.

Regarding maintenance using DR or PHP, refer to either Fujitsu M10-4/Fujitsu

M10-4S/SPARC M10-4/SPARC M10-4S Service Manual or PCI Expansion Unit for Fujitsu M10/SPARC M10 Systems Service Manual.

Regarding details on the "ldm" command, refer to Oracle VM Server for

Administration Guide of the version you are using.

SPARC

After performing maintenance with DR or PHP, execute the following procedure,

necessary.

3. Create virtual functions (VF) by executing the "ldm create-vf" command.

4. Assign the virtual functions (VF) to the I/O domains using the "ldm add-io" command.

■

The on-board LAN interfaces of SPARC M10 systems support the SR-IOV feature.

■

The static SR-IOV feature is supported from Oracle VM Server for SPARC 3.0 onwards.

■

The dynamic SR-IOV feature is supported from Oracle VM Server for SPARC 3.0 onwards.

■

For details on the SR-IOV feature, refer to Oracle VM Server for SPARC Administration

Guide of the version you are using. For the necessary fixes when using the SR-IOV

feature, refer to Oracle VM Server for SPARC Release Notes of the version you are using.

■

For a list of PCI cards that support the SR-IOV feature, refer to Fujitsu M10/SPARC M10 Systems PCI Card Installation Guide.

Notes on OpenBoot PROM

■

If you execute the sendbreak(8) command after the OpenBoot PROM banner appears on the domain console but before OpenBoot PROM startup is completed, the following error message is output. In this case, the boot command becomes unable to be executed. FATAL: OpenBoot initialization sequence prematurely terminated.

In this case, set the OpenBoot the ok prompt, and execute the reset-all command. When OpenBoot PROM is restarted, set auto-boot? to true, and execute the boot command.

■

When you use the XSCF firmware setpparparam(8) command to set an OpenBoot PROM environment variable, such as nvramrc, the maximum number of characters that can be set is 254. If you want to set a string of 255 or more characters in an OpenBoot PROM environment variable, such as nvramrc, do Solaris environment. Note that, however, the maximum number of characters is

1024.

■

The OpenBoot PROM device aliases disk and net are not created for Oracle VM Server for SPARC disks and logical domains to which no network is assigned. To execute disk boot or network boot by specifying the device alias disk or net, set the

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

PROM environment variable auto-boot? to false at

so in the OpenBoot PROM or Oracle

March 201514

･

Page 29

device aliases disk and net by using the OpenBoot PROM nvalias command.

■

From XCP 2210 onwards, at the time of starting up OpenBoot PROM, the following message is output to the domain console before the OpenBoot PROM banner is displayed.

NOTICE:EnteringOpenBoot. NOTICE:FetchingGuestMDfromHV. NOTICE:Startingadditionalcpus. NOTICE:InitializingLDCservices. NOTICE:ProbingPCIdevices. NOTICE:FinishedPCIprobing.

■

Suppose the following: The environment variable multipath-boot? of OpenBoot PROM is true; the boot -L command is executed to display boot environments (BEs) that, existing in the root pool, allow booting; and the number of a boot environment is selected from the displayed interactive menu. The system does not return to The number of restarts depends on the environment variable boot-device of OpenBoot PROM. OpenBoot PROM restarts as many times as the number of configured devices and then the message "ERROR: All device paths in boot-device have failed." is displayed and the ok prompt reappears.

To avoid this problem, set the environment variable multipath-boot? of OpenBoot PROM to false before executing the boot -L command or execute the boot

device_path -L command.

the ok prompt, but restarts OpenBoot PROM.

Notes on maintenance for CPU memory units, motherboard unit, XSCF unit, PSU backplane, or crossbar backplane unit

■

[SPARC M10-1/SPARC M10-4S] When replacing a motherboard unit or a PSU backplane, mounted on SPARC M10-1 or when replacing an XSCF unit or a crossbar backplane unit, mounted on a crossbar box, if any of the following conditions are true, execute the following procedures to solve the problems reported in RTIF2-130806-001, fixed in XCP 2220.

XCP firmware version is XCP 2210 or older.

The microSD card of the old motherboard unit or the old XSCF unit is not used.

* As

XSCF firmware writes onto the microSD card, mounted on the FRUs, if the XSCF firmware because failing to do so will result in the occurrence of the problem reported in RTIF2-130806-001.

- If the setting specifying the XSCF as an NTP client is disabled:

XCP 2210 or older, the following procedure is necessary

Chapter 2　XCP 2240-Related Information 15

which has been

Page 30

Perform the ordinary replacement procedure.

- If the setting specifying the XSCF as an NTP client is enabled:

Disconnect the LAN cable from the XSCF-LAN port and then perform replacement.

After the XSCF starts, connect the serial cable to the serial port.

not connect the LAN cable at

Execute the setdate(8) command to set the XSCF time.

After this, the XSCF is reset.

Connect the LAN cable to the XSCF-LAN port.

Execute the version command to confirm the firmware version information.

the XCP firmware version does not match that used before the

update the firmware. For details, see "16.1.3 Updating firmware" in the Fujitsu M10/SPARC M10 Systems System Operation and Administration Guide.

you replace the microSD card, the CMU firmware versions do not match. However, you do not need to perform an update. The following example shows "02.01.0001" (*1 in

the current XCP, and "02.00.0006" (*2 in the execution example) as the CMU firmware version of the reserve XCP. Thus, you can see that the CMU firmware versions do not match.

the execution example) as the CMU firmware version

this time.

replacement,

XSCF> BB#00-XSCF#0(Master) XCP0(Current):2011 CMU



XSCF XCP1(Reserve):2011 CMU



XSCF CMUBACKUP #0:02.01.0001 #1:.. XSCF>

XSCF>

version-cxcp-v



:

POST

:

OpenBootPROM:4.34.0+1.2.0 Hypervisor

:

:

POST

:

OpenBootPROM:4.34.0+1.0.5 Hypervisor

:

Execute the testsb command to confirm that the FRU requiring recognized normally.

testsb-a



Execute the showstatus command to confirm that the FRU is operating normally after the completion of maintenance.

Nothing is displayed in the normal state.

02.01.0001

1.20.0

:

0.21.11

02.01.0001

02.00.0006

1.13.0

0.21.3

02.01.0001

(*1)



(*2)



maintenance is

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201516

Page 31

xscf>

■

showstatus



Power on the physical partition.

After the logical domain starts up, the logical domain time have a time lag. If there

is a

time lag, set the correct time.

The setting information of the CPU Activation and the CPU Activation key may be deleted when the CPU memory unit lower (CMUL) or the motherboard unit (MBU) is replaced. To restore the setting information of CPU Activation and the CPU Activation key, it is necessary to save the setting information of Activation and CPU Activation key beforehand, using the dumpconfig(8) command and restore them with the restoreconfig(8) command.

the CPU

To replace the CPU memory unit lower (CMUL) or to install the SPARC M10-4S,

execute the replacefru(8) or addfru(8) command and follow the maintenance menu.

Suppose that the system contains a crossbar box or consists of multiple SPARC M10-4S units and that the firmware is XCP 2044 or later. If the CPU memory unit lower (CMUL) is replaced or if the SPARC M10-4S is installed without using the maintenance menu, the XSCF of the replaced/installed device

may not start.

Should this occur, turn off the input power to the replaced/installed SPARC M10-4S. Subsequently, using the maintenance menu, replace the CPU memory unit lower (CMUL) or install the SPARC M10-4S again.

■

[SPARC M10-4S] From XCP 2090 onwards, automatic synchronization of firmware versions between chassis, when replacement of CPU Memory Unit lower (CMUL) or XSCF unit, expansion of SPARC M10-4S or crossbar box is performed in off state of the input power supply, without using the maintenance menu, has been enabled.

After replacement or

progress. BB#xx, please wait for XSCF firmware update complete." message is output after logging in to the master XSCF, the XCP firmware is in the process of being updated automatically.

expansion of components, if the "XSCF firmware update now

Automatic synchronization of XCP firmware versions can be confirmed by the "XCP firmware version synchronization completed" message, which is output by the "showlogs monitor", "showlogs event", or "showmonitorlog" command.

Do not execute the following until the firmware update is complete.

- Turn off the input power supply

- Execute the poweron(8) command

- Execute the testsb(8) command

- Execute the diagxbu(8) command

- Execute

the getflashimage(8) or the flashupdate(8) command

Notes on CPU Activation

■

If the XSCF setting information is initialized by executing the restoredefaults(8) command in XCP 2032 or earlier, the information of the CPU Activation key is also

Chapter 2　XCP 2240-Related Information 17

Page 32

initialized. When executing the restoredefaults(8) command, save the CPU Activation key in advance before restoring it or register the key again.

In addition, when you replace a CPU memory unit or motherboard, the CPU Activation key may be erased. For details, see "Notes on maintenance for CPU

memory units, motherboard unit, backplane unit."

■

If you execute the restoredefaults -c xscf command on XCP 2041 or later, the information of the CPU Activation key is deleted not only from the XSCF unit but also from the backup information in the XSCF. On the other hand, even if you execute the restoredefaults -c factory command, the Activation key is not deleted.

XSCF unit, PSU backplane, or crossbar

information of the CPU

To initialize all settings to factory defaults including the information of the CPU Activation key, use the -c factory -r activation option.

■

XSCF setting information saved by the dumpconfig(8) command contains CPU Activation information and CPU Activation keys. You can use the restoreconfig(8) command to restore the CPU Activation information and CPU Activation keys that were saved with the dumpconfig(8) command.

Therefore, if you configure CPU Activation or install a CPU Activation key when configuring settings for the XSCF, such as when configuring an XSCF network or physical partition (PPAR), we recommend that you first save the CPU Activation information and CPU Activation key by using the dumpconfig(8) command. To save and restore only CPU Activation keys, execute the dumpcodactivation(8) and restorecodactivation(8) commands, respectively. Activation information cannot be saved and restored. Use the showcod(8) and setcod(8) commands to reconfigure CPU Activation.

Note, however, that CPU

Notes and restrictions on XSCF Web

Notes

Common to browsers

(1)

■

When you import XCP or update the firmware by using XSCF Web, "Session is invalid" may appear on the web browser.

■

If the timeout of the XSCF shell is short when you import XCP by using XSCF Web, XCP importing fails. Set the timeout of the XSCF shell to 30 minutes or longer. Select the [menu] tab and select [XSCF] - [Settings] - [Autologout] menu. Then, enter a value of 30 minutes

Internet Explorer

(2)

If you use XSCF Web of a version XCP 2221 or earlier while you are in Internet Explorer 10 or 11, you may see distorted screen layouts, such as disordered tables or superposed characters. If you see a distorted XSCF Web screen layout

the above environment, use Internet Explorer 9 or earlier or Firefox.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

or greater in [Time-out value].

･

March 201518

Page 33

However, this problem does not affect system operation.

Firefox

(3)

■

If you use XSCF Web in a Firefox environment, the browser may prompt you to save the login ID and password when you log in to the XSCF. In this case, do not save the login ID and password. If you save the login ID and password, the saved data may

Note -

systems sold within Japan by Fujitsu.

displayed on LDAP, SMTP, and REMCS web pages.

Remote Customer Support System (REMCS) is supported only for SPARC M10

Configure either of the following settings to disable the login ID/password save function of the browser:

- Disable the login ID/password save function throughout the browser. Select

[Tools] - [Options] - [Security] tab, and uncheck [Remember passwords for sites]

[Passwords].

- Specify

[Options] - [Security] tab, and check [Remember passwords for sites] in [Passwords]. Then, click the [Never Remember Password for This Site] button in the dialog box that appears for ID and password saving when you log XSCF. This registers the address of the XSCF in the [Exceptions] list for ID and password saving, and the dialog box for ID and password saving does not appear at subsequent logins to the XSCF.

the site as an exception to login ID and password saving. Select [Tools] -

in to the

Restrictions

Common to browsers

(1)

There are no restrictions known at present.

Internet Explorer

(2)

If you use Internet Explorer 8 in a Windows 7 environment, built-in Administrator

accounts cannot be used.

Firefox

(3)

There are no restrictions known at present.

Notes on firmware update

■

[SPARC M10-4S] If you update the firmware by executing the flashupdate(8) command or using XSCF Web, the time for the processing depends on the number of SPARC M10-4S chassis or crossbar boxes that configure the system.

■

The relationship of the master XSCF and the standby XSCF after the update of the XSCF firmware depends on the version of the updated XCP. The following table shows the relationship between the master XSCF and the standby XSCF as well as the operation of firmware update, for each XCP version.

Chapter 2　XCP 2240-Related Information 19

Page 34

Table 2-1

XCP version Relationship between master XSCF and standby

Difference between firmware update in XCP 2050 or later and in XCP 2044 or earlier

XSCF

XCP 2050 or later The master XSCF and the standby XSCF

that have been switched over during update will return to the status before the switchover.

XCP 2044 or earlier The master XSCF and the standby XSCF

that have been switched over during update will stay switched over.

Operation during firmware update

1. Execute the flashupdate(8) command from the master XSCF of BB#00.

-> The XSCF of BB#00 that has executed the flashupdate(8) command is in the standby status reset.

immediately after XSCF

-> XSCF automatic switchover is performed after the update has been completed.

-> When XSCF automatic switchover is completed, the XSCF of BB#00 that has executed the flashupdate(8) command is restored to the status of the original master.

2. Confirm that the update has been completed by referring message "XCP update has been completed." from the master XSCF of BB#00.

the log

1. Execute the flashupdate(8) command from the master XSCF of BB#00.

-> The XSCF of BB#00 flashupdate(8) command is in the standby status immediately after XSCF reset.

that has executed the

-> XSCF automatic switchover is not performed after the update has been completed. For this reason, the XSCF of BB#00 that has executed the flashupdate (8) command will stay in the standby status.

2. Confirm that the completed by referring to the log message "XCP update has been completed." from the master XSCF of BB#01.

update has been

3. To restore the status of the master and standby XSCFs to the status before the update, execute the switchscf(8) command from the master XSCF of BB#01 to restore the the master.

XSCF of BB#00 to

■

When updating firmware, errors described in "Problems with XCP and

Workarounds" may occur. In such a case, take the actions described in workarounds,

then update again.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201520

Page 35

Notes on configurations with a PCI expansion unit connected

■

[SPARC M10-1] If one of the following cases, the logical domain configuration of physical partitions (PPARs) is restored to the factory-default state at the next startup. Moreover, when there is a guest domain in the logical domain configuration, the OpenBoot PROM environment variable is initialized.

- Firmware of version XCP 2043 or

in a

configuration with a PCI expansion unit connected.

- A PCI expansion unit is added to or removed from a system with firmware of XCP 2044 or later.

Save the logical domain configuration information to an XML file from Oracle Solaris in advance. Execute the ldm list-constraints -x command to save the logical domain configuration information to an XML file. Execute the ldm init-system -i command to restore the logical domain configuration information from an XML

file. Make a note of the OpenBoot PROM environment variable setting information

for the control domain beforehand so that you can subsequently reconfigure it.

To display the information, execute the printenv command in the ok prompt. For details of these procedures, see "1.7.2 How to save the configuration information and the OpenBoot PROM environment variable in the logical domain and subsequently restore them" Systems Service Manual.

If you need to save/restore information related to the PCI expansion unit configuration, see the information in the following table.

earlier is updated to that of XCP 2044 or later

the PCI Expansion Unit for Fujitsu M10/SPARC M10

Table 2-2

Mounting of PCI expansion unit

No factory-default Unnecessary Unnecessary

No Guest domain exists. Unnecessary Unnecessary

Yes factory-default Unnecessary Unnecessary

Yes Guest domain exists. Necessary (XML) Necessary

■

Required work regarding the PCI expansion unit configuration

Domain configuration Re constructing Oracle

[SPARC M10-4/M10-4S]

Server for SPARC

config

Setting OpenBoot PROM environment variables again

If either of the tasks is performed with the setpciboxdio(8) command, using firmware of version XCP 2044 or later for the SPARC M10-4 or version XCP 2050

later for the SPARC M10-4S, the logical domain configuration of the physical partitions (PPARs) is restored to the factory default at when the domain configuration includes a guest domain, the OpenBoot PROM environment variable is initialized.

the next startup. Moreover,

- The enable/disable setting for the direct I/O function of the PCI expansion unit is

Chapter 2　XCP 2240-Related Information 21

Page 36

changed.

- A PCI expansion unit is added, removed, or replaced for a PCI slot of SPARC M10 chassis for which the direct I/O function of a PCI expansion unit is enabled.

Save the logical domain configuration information to an XML file from Oracle Solaris in advance. Execute the ldm list-constraints domain configuration information to an XML file. Execute the ldm init-system -i command to restore the logical domain configuration information from an XML file. Also, write down in advance the setting information of the OpenBoot PROM environment variable for the control domain, and set it information, execute the printenv command in the ok prompt. For details of these procedures, see "1.7.2 How to save the configuration information and the OpenBoot PROM environment variable in the logical domain and subsequently restore them" in the PCI Expansion Unit for Fujitsu M10/SPARC M10 Systems Manual.

-x command to save the logical

again. To display the

Service

If you need to save/restore various information when you change the enable/ disable setting of the direct I/O function of PCI expansion units by executing the setpciboxdio(8) command, the information in the following table applies.

Table 2-3

Configuration of PCI expansion unit

Yes/No factory-default Unnecessary Necessary

Yes/No Guest domain exists. Necessary (XML) Necessary

Note -

direct I/O function is disabled. Therefore, no information needs to be saved/restored.

Table 2-4

Maintenance environment Domain configuration Re constructing

When addition/removal is performed by stopping the PPAR

When a faulty PCI expansion unit(*1) is replaced by stopping the PPAR

Work for switching the enable/disable setting by executing the setpciboxdio command

Domain configuration Re constructing Oracle

Server for SPARC

config

If you add, remove, or replace a PCI expansion unit for a PCI slot chassis for which the direct I/O function of a PCI expansion unit is enabled, by executing the setpciboxdio(8) command, the cases in which you need to save/restore information are listed in the following table.

In maintenance on a PCI expansion unit with the PCI hot plug (PHP) function, the

Work to be performed after you add, remove, or replace a PCI expansion unit for a PCI slot of SPARC M10 chassis for which the direct I/O function is enabled

Oracle VM Server

for SPARC config

factory-default Guest domain exists.

Unnecessary

Necessary (XML)

Unnecessary

Necessary (XML)

Setting OpenBoot PROM environment variables again

of SPARC M10

Setting OpenBoot PROM environment variables again

Unnecessary Necessary

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201522

Page 37

Table 2-4

(continued)

Maintenance environment Domain configuration Reconstructing

When a normal PCI expansion unit(*1) is replaced by stopping the PPAR

*1 Includes cases in which a link card, link cable, management cable, or link board is replaced.

Work to be performed after you add, remove, or replace a PCI expansion unit for a PCI slot of SPARC M10 chassis for which the direct I/O function is enabled

Setting OpenBoot PROM environment variables again

Unnecessary Unnecessary

factory-default Guest domain exists.

Oracle VM Server for SPARC config

Unnecessary Unnecessary

Notes on dual power feed setting

The power supply unit of the SPARC M10 system is redundantly configured. Enabling or disabling the dual power feed function with the setdualpowerfeed(8) command does not affect the behavior of a redundantly configured system. Therefore, when the display results of the showdualpowerfeed(8) and showhardconf (8) commands, which are dependent on the command, also fall under any of the following conditions, the behavior of the redundantly configured system is not affected.

■

The showhardconf(8) command displays "Power_Supply_System: Dual;" when the showdualpowerfeed(8) command displays "Dual power feed is enabled."

■

The showhardconf(8) command displays "Power_Supply_System: Single;" when the showdualpowerfeed(8) command displays "Dual power feed is disabled."

The system administrator can use this setting function as a memo for determining whether the power supply unit has a dual power feed configuration.

setting of the setdualpowerfeed(8)

Notes on Active Directory

■

If Active Directory is enabled and you try login via telnet, inquiry to the second and subsequent alternative servers may time out, causing the login to fail.

■

If the value set by the timeout operand of the setad(8) command is small, and you log in to the XSCF, the user privilege may not be assigned to you. In this case, increase the timeout setting value and try again.

Notes on LDAP over SSL

If the value set by the timeout operand of the setldapssl(8) command is small, and you log in to the XSCF, the user privilege may not be assigned to you. In this case, increase the timeout setting value and try again.

Chapter 2　XCP 2240-Related Information 23

Page 38

Notes on the logical domain time

Suppose the physical partition (PPAR) has been kept active for a long time on the system with the XCP version earlier than XCP 2232. Then restarting the physical partition may cause the Oracle Solaris time to deviate. This problem (RTIF2-140711-

001) is solved in XCP 2240 and later XCP versions. However, partition right after firmware update from XCP 2232 or earlier to XCP 2240 or later may cause the Oracle Solaris time to deviate. Also, after the physical partition (PPAR) has been kept active for a long time, restarting the physical partition may cause the time of logical domains control domain to deviate. (RTIF2-141204-001) To solve these problems, restart the physical partition, boot Oracle Solaris in single-user mode, execute the date(1M) command, and then set the correct time. The following shows the workaround procedure.

Execute the poweroff -p command to power off the target physical partition.

Also, stop

the logical domains within the physical partition.

restarting a physical

other than the

XSCF> PPAR-IDstopoweroff:xx Continue?[y|n]:y xx:Poweringoff *Note* Thiscommandonlyissuestheinstructiontopower-off. Theresultoftheinstructioncanbecheckedbythe"showlogspower". XSCF>

poweroff-pxx



XSCF> PPAR-IDPPARStatus 00Poweredoff

XSCF> MonJan2314:53:00JST2012

Note -

set the time by executing the setdate command.

Execute the showpparstatus(8) command to confirm the physical partition is powered off. Confirm the PPAR Status displays "Powered off."

showpparstatus-pxx



Execute the showdat e( 8) command to display the clock time of XSCF.

showdate



Set the clock to the right time if it is incorrect. Power off all physical partitions if you

Starting the physical partition may cause the logical domain time to deviate. Use the NTP server to set the logical domain time, or, if it is the control domain, perform steps 4 to 9 in the following procedure, execute the date(1M) command in single-user mode, and set the control domain time.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201524

Page 39

Specify false for the OpenBoot PROM environment variable auto-boot?,

execute the setpparparam(8) command, and disable the autoboot function of the control domain.

XSCF> PPAR-IDofPPARsthatwillbeaffected:xx OpenBootPROMvariablebootscriptwillbechanged. Continue?[y|n]:

XSCF> DomainIDstopoweron:xx Continue?[y|n]: xx:Poweringon *Note* Thiscommandonlyissuestheinstructiontopower-on. Theresultoftheinstructioncanbecheckedbythe"showlogs power". XSCF>

XSCF> : omitted {0}ok

setpparparam-pxx-sbootscript"setenvauto-boot?false"



Execute the poweron(8) command to power on the target physical partitions.

poweron-pxx



Execute the console(8) command to switch to the console of the control domain.

console-p0



Execute the boot -s

{0}ok

10.

11.

12.



boot-s



Execute the date(1M) command of Oracle Solaris to display the control domain time.

Set the control domain time by executing the date(1M) command.

xxxx

date



Enter the escape command such as ".#" from the control domain console of the physical partition, and return to XSCF

Execute the showdate(8) command to display the XSCF time to confirm that the control domain time of the target physical partition is the same as the clock time of XSCF.

If necessary, specify true for OpenBoot PROM environment variable auto-boot?, Execute the setpparparam(8) command, and enable the autoboot

command to start Oracle Solaris in single-user mode.

shell.

Chapter 2　XCP 2240-Related Information 25

Page 40

function of the control domain.

XSCF> XSCF>

13.

setpparparam-p



Similarly, execute the ldm add-spconfig command for the guest domain after adjusting the time of Oracle Solaris.

-sbootscript"setenvauto-boot?false"





Notes on Timezones

The time zones (regions/place names) supported by the XSCF can be changed to support the latest time zone information. For any previously set time zone that the system cannot use anymore, the XSCF switches from this unusable time zone to Coordinated Universal Time (UTC) and operates in UTC. When the set time command, and check the settable time zones. If the time zone list does not have a set time zone, set a time zone again.

zone operates in UTC, execute the settimezone -c settz -a

Notes on power supply interlock function (RCIL)

■

Do not register the same node with multiple power supply interlocking groups. If power supply interlocking is performed by registering a single node with multiple power supply interlocking groups, the operation may not be as intended. With the setremotepwrmgmt(8) command, you cannot confirm whether a single node is registered with multiple

modifying a power supply interlocking group management information file,

take care not to cause overlaps.

■

Do not register an I/O node with multiple power control groups. If the same I/O node is set with multiple power supply interlocking groups, and both of the conditions below are met, the I/O node is turned on and off alternately.

- setremotepwrmgmt -c enable is executed, and the power supply function is enabled.

- There is a power control group in which one or more host nodes are on, and there is a power control group in which all the host nodes are off.

If you accidentally register an I/O node with multiple power control groups, use setremotepwrmgmt -c disable use clearremotepwrmgmt to delete the power control group setting. After deletion, create a power supply interlocking group management information file

that the I/O node is not registered with multiple groups, and then use

setremotepwrmgmt -c config to register it again.

■

If XCP 2080 or earlier is used together with a single SPARC M10 system that is connected to an external I/O device, do not use the power supply interlocking function. The external I/O device may be erroneously powered off when the XSCF

power supply interlocking groups. When creating

interlocking

to disable power supply interlocking first and then

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201526

Page 41

reset.

■

For a management file to set the power supply interlocking function, use CR and LF, or LF as linefeed code.

■

For a management file to set the power supply interlocking function, you need to specify the MAC address regardless of the node type. Otherwise, the following error occurs when you execute the setremotepwrmgmt(8) command. [Example]

XSCF> Password: Downloadsuccessful:213Byteat2103.000KB/s Checkingfile... Thedefinitionof[MACAddress]in[ftp://xx.xx.xx.xx/rpmgroup.csv]isinvalid. XSCF>

setremotepwrmgmt-cconfig-uguestftp://xx.xx.xx.xx/rpmgroup.csv



You need to set the MAC address regardless of the node type of the I/O node, master though the MAC addresses of some nodes are not set and left "blank" in "Chapter

host node, host node, or remote power supply control unit. This is required

Examples of Power Supply Interlocking Configuration" in the Fujitsu M10/

SPARC M10 Systems RCIL User Guide.

Other notes and restrictions

Notes

■

When the mode switch on the operation panel is set to Service mode, the power cannot be turned on by using the power switch on the operation panel. To turn on the power using the power switch on the operation panel, set the mode switch on the operation panel to the

■

To add the 64 GB memory, apply XCP 2090 or later.

■

[SPARC M10-1/M10-4/M10-4S] The maximum number of users who can concurrently connect to the XSCF via Telnet and SSH is as follows:

- M10-1: 20 users

- M10-4: 40 users

- M10-4S (without crossbar box): 40 users

- M10-4S (with crossbar box): 70 users

If the maximum allowable number of users is exceeded, access is

■

XSCF-LAN is compliant with auto-negotiation. If you connect XSCF-LAN to a network device that is fixed to full-duplex mode, the XSCF-LAN communicates in half-duplex mode according to the IEEE 802.3 protocol. This may slow down the speed of network communication or cause communication error. Be sure to set auto-negotiation for network

■

Settings made by the setdualpowerfeed(8) command are immediately applied.

Locked mode position.

devices to which you connect XSCF-LAN.

denied.

Chapter 2　XCP 2240-Related Information 27

Page 42

Therefore, the XSCF does not need to be reset.

■

The ioxadm poweroff(8) command can be specified with the -f option only for a power supply unit.

■

Configuring a memory mirror setting by using the setupfru(8) command should

done when the physical partition (PPAR) to which the target system board

(PSB) belongs is powered off.

■

To display a man page, set TERM=vt100 for the terminal software.

■

When configuring a physical partition (PPAR), do not set a BB-ID that does not exist in the system as the PPAR-ID. For example, if BB-IDs 00 and 01 exist in the system, you can set 00 or 01 as the PPAR-ID. If you set 02 as the PPAR-ID, the PPAR with unable to start.

■

Among the information displayed by executing the showhardconf(8) command, the PCI Express (PCIe) card information of the guest domain will be reflected after Oracle Solaris of the corresponding guest domain has started.

■

As of XCP 2032, the default value for the power save operation set by the setpparmode(8) command is changed from "enabled" to "disabled."

■

When you execute the testsb(8) or diagxbu(8) command, a PPAR-ID of "PPAR#30" that does not exist may appear in an error log suspected area. This indicates that

error was detected on the system board (PSB) while diagnosing. The output

PPAR-ID does not have any meaning.

■

We recommend to connect the control domain console via the XSCF-LAN port.

PPAR-ID 02 becomes

When a large amount of data is output by connecting to the control domain console via a serial port, the data may not be displayed properly.

■

[SPARC M10-4S] The time taken for processing a command that displays the system configuration

status (such as showhardconf(8) command, showboards(8) command, and

showpparstatus(8) command) depends on the number of SPARC M10-4S chassis

crossbar boxes that configure the system.

■

[SPARC M10-4S] For a system configured with multiple chassis, chassis BB#01 or XBBOX#81 may become the master XSCF first.

■

[SPARC M10-4S] Depending on the system configuration, it may take time to reboot.

■

If you add a SPARC M10-4S to the SPARC M10-4S on which XCP 2032 is installed, update to the latest firmware in advance.

■

When you execute the setsnmpvacm(8) command specifying createview as the operand, you cannot set an access restriction using the OID mask of MIB. When you execute the setsnmpvacm(8) command specifying createview as the operand,

not use the OID mask of MIB.

■

If a takeover IP address has been set, the UDP packet sender IP address and Agent Address for the SNMP Trap of SNMPv1 are different. The IP address assigned to each XSCF-LAN (physical IP address) is stored as the UDP packet sender IP address, while the takeover IP address (virtual IP Address.

address) is stored as the Agent

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201528

Page 43

■

The device path of the I/O device that has been used changes if a CPU memory unit upper (CMUU) is added to add two CPUs when the I/O bus reconfiguration

enabled in SPARC M10-4 or SPARC M10-4S with two CPUs installed.

As for the ioreconfigure that can be specified by

-m function of the setpparmode (8) command, leave it as the default, false, and disable the I/O bus reconfiguration function.

If you enable the I/O bus reconfiguration function by specifying true to the ioreconfigure, it may be necessary to reinstall Oracle Solaris.

■

With a logical domain running Oracle Solaris 11, updating to XCP 2050 or later allows you to have an increased maximum number of PCIe cards on one root complex (RC). To install a PCIe card after updating to XCP 2050 or later, perform the steps below

the control domain.

This example ldm-set1 and factory-default, are stored.

Check the configuration information of the logical domain stored in XSCF.

assumes that two sets of configuration information currently in use,

primary# ldm-set1[current] factory-default

Execute the following commands on all of the logical domains, including the

control domain.

Specify the name of the logical domain for ldom.

primary# primary#

Store the updated configuration information for the logical domain again.

Delete the stored ldm-set1 and then store the information again.

primary# primary#

Restart all logical domains.

■

An XSCF user account name cannot be the same as an LDAP user name. In addition, an XSCF user account UID cannot be the same as an LDAP UID.

■

When starting OpenBoot PROM, even if an error is detected with the GFX 550e graphics card (TechSource, PCIExpress Graphics Board), nothing may be output

the console.

ldmlist-spconfig



ldmset-variablefix_atu=true



ldmremove-variablefix_atu



ldmrm-spconfigldm-set1



ldmadd-spconfigldm-set1



ldom

The problem can be confirmed from the following error log output with the showlogs error command, which registers the faulty component (suspect component) as

"UNSPECIFIED".

Chapter 2　XCP 2240-Related Information 29

Page 44

XSCF> Date:MMMDDhh:mm:ssJST2014



■

showlogserror



Code:80000000-00ffff0000ff0000ff-030000010000000000000000 Status:AlarmOccurred:MMMDDhh:mm:ss.sssJST2014 FRU:/UNSPECIFIED Msg:I/Odeviceerrordetected

[SPARC M10-4S] If cold replacement is performed on a system with several SPARC M10-4S and crossbar boxes, the XSCF may not start. Perform the following procedure depending on the target components for cold replacement.

- Perform the following procedure when replacing crossbar boxes (XBBOX):

Turn off the input power (AC OFF)

Replace the XSCF unit (XSCFU).

When performing this procedure, swap the microSD card in the old XSCF unit

the new XSCF unit, before replacing the XSCF unit itself.

Turn on the input power (AC ON) of the XBBOX.

- Perform the following procedure when are mounted on the crossbar box (XBBOX):

the following cases, replacement of microSD card is unnecessary. For details

maintenance, refer to Fujijtsu M10-4/Fujitsu M10-4S/SPARC M10-4/SPARC

M10-4S Service Manual.

XSCF unit (XSCFU), crossbar unit (XBU), XSCF interface unit (XSCFIFU), crossbar backplane unit (OPNL), power supply unit (PSU), fan (FAN).

(XBBP), fan backplane unit (FANBP), operation panel

the target XBBOX.

replacing the following components that

- Perform the following procedure when replacing SPARC M10-4S or CPU memory unit lower (CMUL):

Execute the replacefru(8) command and follow the maintenance menu to perform the replacement.

■

[SPARC M10-4S] When maintenance is performed by either the replacefru(8) or the addfru(8) command, terminate the command using the "c" option. If the flashupdate(8) command is executed before terminating the above commands, in case of systems comprising of a number of SPARC M10-4S, automatic switchover to master XSCF may not be

executed after firmware update is complete.

[How to Restore]

After maintenance is completed using either the replacefru(8) or the addfru(8) command, use the "c" option to terminate the command. If switchover to the master XSCF is not performed after the completion of firmware update, execute the switchscf(8) command on the master XSCF master XSCF.

command to switchover to the

Restrictions

■

At this point, no-mem, to be set with the -s option of the setpcl(8) command, is not

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201530

Page 45

supported.

■

Alive monitoring between the XSCF and a Hypervisor is not supported. Alive monitoring between the XSCF and a Hypervisor cannot be enabled/disabled even

using the setpparmode(8) command.

■

[SPARC M10-4S] Suppose that the XSCF was switched while connecting to the control domain console in the SPARC M10-4S that is composed of more than two chassis. In that case, connection to the control domain console may not be established until all the SPARC M10-4S chassis have been restarted if an reconnect the control domain console to the switched master XSCF.

attempt has been made to

If all XSCFs have not been restarted due to an error in the XSCF, establish a connection to the control domain console again. Replace a failed XSCF or CPU memory unit lower (CMUL) if a connection domain console.

■

[SPARC M10-4S]

cannot be established to the control

The poweroff(8) and reset(8) commands may not be executed normally if all XSCF have not been restarted due to an error in a XSCF in the SPARC M10-4S that is composed of more than two chassis.

To disconnect the power of a physical partition (PPAR), login to the control domain Then, disconnect the power of the PPAR using the poweroff -f command on the XSCF firmware. The reset(8) command cannot be used in this state.

■

The -c wait option, which is used to set the wait time before the system is started for the setpowerupdelay(8) command, is not supported at present.

■

Replacement of a crossbar box using the replacefru(8) command is not supported

crossbar box" in "Chapter 6 Information on SPARC M10-4S Hardware."

■

Addition of a crossbar box using the addfru(8) command is not supported at present. For how to add a crossbar box, see "Restrictions on adding expansion rack

2" in

■

[SPARC M10-4S]

the PPAR and execute the shutdown(1M) command on Oracle Solaris.

present. For how to replace a crossbar box, see "Restrictions on replacing

"Chapter 6 Information on SPARC M10-4S Hardware."

If you power on all physical partitions (PPAR) in a system that has more than one PPARs with the poweron(8) command, the startup time taken when specifying power-on of PPAR is longer than the time taken for batch power-on by specifying

-a.

■

[SPARC M10-4/M10-4S] As for the ioreconfigure that can be specified by -m function of the setpparmode (8) command, leave it as the default, false, and disable the I/O bus reconfiguration function. If you enable the I/O bus reconfiguration function by specifying true to the ioreconfigure, it may be necessary to reinstall Oracle

■

[SPARC M10-4S]

Solaris.

If showhardconf -M is executed, it may not be possible to display one screen at a time if both of the conditions below are met. Do not execute showhardconf -M.

- System configured with 2BB or more

- One or more SPARC M10-4S units are subject to an XSCF reset

by the

Chapter 2　XCP 2240-Related Information 31

Page 46

rebootxscf(8) command, so they cannot communicate.

■

[SPARC M10-1] If firmware update to the version of XCP 2070 or earlier is executed when the physical partition (PPAR) is powered on, the logical domains may stop.

Be sure to execute firmware update when the physical partition (PPAR) is powered off. See "RTIF2-131004-001" of "Problems resolved in XCP 2070" for issue.

■

The XSCF user account's user privilege, managed by the LDAP server which is specified by either by the setldap(8) command, or by specifying [XSCF] - [Setting]

[User Manager] - [LDAP] on the XSCF Web, cannot be set up with [XSCF] [Setting] - [User Manager] - [Account] on the XSCF with the setprivileges(8) command on XSCF shell prompt.

Web. Set up user privilege

this

XCP 2240 Problems and Workarounds

See "Problems that might occur with XCP 2240 and workarounds" for information on problems that can occur with XCP 2240. See "Problems resolved in XCP 2240" for information on problems resolved in XCP 2240.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201532

Page 47

Chapter 3

Information on Software

This chapter describes special instructions and problems concerning the SPARC M10 Systems software.

■

Notes and Restrictions

Problems with XCP and Workarounds

Problems with Oracle Solaris and Workarounds

Notes on support for disks with an EFI (GPT) label

The default disk label that is effective when Oracle Solaris is installed has changed from VTOC (SMI) to EFI (GPT). If you need a disk with a VTOC (SMI) label, execute the format -e command of Oracle Solaris to apply the VTOC (SMI) label and then install Oracle Solaris. For details Reference Manual. In addition, be sure to select [Use a slice on the disk] for the [Solaris slice] screen on the Oracle Solaris installation menu to ensure that the disk is VTOC (SMI) labeled.

-------------------------------------------------------------------------



OracleSolariscanbeinstalledonthewholediskorasliceonthedisk.

Thefollowingsliceswerefoundonthedisk.

Slice

#

-----------------------------------------------Unused Unused Unused

0

1

3

SolarisSlices:6.0GBunknownBoot

Size(GB)Slice

0.1Unused

0.1rpool

0.0Unused

#

5

6

7

the format(1M) command, see the Oracle Solaris

Size(GB)

0.0

5.7

0.0

Page 48

Unused





Esc-2_ContinueEsc-3_BackEsc-6_HelpEsc-9_Quit

-------------------------------------------------------------------------

4

■

If an EFI (GPT) labeled disk is used, Oracle Solaris booting from a disk more than

■

If an EFI (GPT) labeled disk is used, any second GPT header is not supported on a virtual disk.

0.0backup

Usethewholedisk

Useasliceonthedisk

2

6.0

TiB that is treated as a virtual disk is not supported.

Notes on Oracle VM Server for SPARC

■

If logical domains are reconfigured by Oracle VM Server for SPARC or if the guest domain is reset with the XSCF firmware's reset(8) command after executing the "ldm unbind-domain/ldm bind-domain" command and before executing the "ldm add-spconfig" command, a guest domain other than what had been specified may

reset. Or, logical domain with the ldm add-spconfig command. If you reset the guest domain before saving it, execute the ldm stop command from the control domain, not from XSCF.

■

If you specify a logical domain configuration for next time you start, use the ldm set-config command in place of ldm add-spconfig -r. If you use the ldm add-spconfig -r command to specify a logical domain configuration for next time you start, and operate a guest domain with the reset(8) command

■

If you execute the ldm migrate-domain command with Oracle VM Server for SPARC for live migration, the following problems occur with the XSCF.

- If you execute the showdomainstatus(8) command, "Unknown" is the status

displayed for the migrated guest domain. If you execute the ldm add-spconfig command from the migrated control domain to save configuration information, the status will be displayed normally

- After live migration is executed, if showdomainstatus(8) is then executed at the

migration source, "Host stopped" is the status displayed for the migrated and non-existent guest domain.

- When a physical partition (PPAR) is powered off

not all of the guest domains may be shut down correctly.

- When a guest domain is reset by the reset(8) command, a guest domain other

than the specified one may be reset. If you reset the guest domain, execute from the guest domain, and not from

- If SNMP is set, the name of the guest domain in trap notification may be incorrect.

■

The migration with the ldm migrate-domain command is not supported if the

the specified guest domain is not reset. Save a configuration of the

of the XSCF firmware, another guest domain may be reset.

the showdomainstatus(8) command.

the poweroff(8) command,

XSCF.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201534

Page 49

logical domain at the migration source is in the OpenBoot PROM state. Perform migration with the ldm migrate-domain command after changing the logical domain at the migration source to either of the following states (CR

15858731):

- Stopped state (bound state)

- State where Oracle Solaris is running

■

Be sure to start the ldmd service (svc:/ldoms/ldmd:default) of the control domain.

■

A boot disk with an EFI GPT disk label is supported by the following systems: SPARC M10 systems to which XCP 2230 or later is applied and SPARC T-series or M-series systems to which SysFW 8.4 or SysFW 9.1 or later is applied. However, SPARC M10 systems to which XCP 2221 disk with an EFI GPT disk label. Therefore, do not migrate to a SPARC M10 system to which XCP 2221 or earlier is applied from a SPARC M10 system to which XCP 2230 or later is applied or a SPARC T-series SysFW 8.4 or SysFW 9.1 or later is applied.

earlier is applied do not support a boot

or M-series to which

You can determine whether the boot disk is EFI GPT labeled by executing the devinfo(1M) command of Oracle Solaris on the raw device of the boot disk.

- In case the EFI GPT disk label is not attached:

devinfo-i/dev/rdsk/c2d0s0



/dev/rdsk/c2d0s0

In case the EFI GPT disk label is attached:

00

73728



512



devinfo-i/dev/rdsk/c1d0s0



devinfo:/dev/rdsk/c1d0s0:ThisoperationisnotsupportedonEFIlabeled devices

Notes on live migration of Oracle VM Server for SPARC

■

The "sparc64-class1" value of the cpu-arch property is being supported from Oracle VM Server for SPARC 3.1.1 onwards. For details on the cpu-arch property and its configuration options, refer to the Reference Manual of your Oracle VM Server for SPARC.

■

The values of the cpu-arch property which supports live migration, differs according to the category of the operation mode of the CPUs on the physical partition and the version of Oracle VM Server for SPARC. Please refer to the following table. For details on CPU operational modes of physical partitions, refer

section 7.2.1 of Fujitsu M10/SPARC M10 Systems System Operation and

Administration Guide.

Chapter 3　Information on Software 35



Page 50

Table 3-1

Migrate from

Run on SPARC64 X+

Run on SPARC64 X compatible

Run on SPARC64 X

List of cpu-arch properties that support live migration (On Oracle VM Server for SPARC 3.1.1 or later)

Migrate to Run on SPARC64 X+ Run on SPARC64 X compatible

Run on SPARC64 X

generic, native, sparc64-class1 generic, sparc64-class1

generic, sparc64-class1 generic, native, sparc64-class1

Table 3-2

Migrate from

Run on SPARC64 X+

Run on SPARC64 X compatible

Run on SPARC64 X

Table 3-3

Migrate from

Run on SPARC64 X+

Run on SPARC64 X compatible

Run on SPARC64 X

■

List of cpu-arch properties that support live migration (On Oracle VM Server for SPARC 3.1 or 3.1.0.1)

Migrate to Run on SPARC64 X+ Run on SPARC64 X compatible

Run on SPARC64 X

generic, native generic

generic generic, native

List of cpu-arch properties that support live migration (For Oracle VM Server for SPARC 3.0)

Migrate to Run on SPARC64 X+ Run on SPARC64 X compatible

Run on SPARC64 X

native none

none generic, native

When executing live migration of the domain with the kernel zone operating, from a SPARC M10 system with XCP 2230 or newer, the following output is displayed, and live migration fails.

ldmmigrate-domainldg1root@target-name



TargetPassword: Failureoccurredwhilepreparingdomainldg1forsuspend



operation LivemigrationfailedbecauseKernelZonesareactive. StopKernelZonesandretry. Timeoutwaitingfordomainldg1tosuspend DomainMigrationofdomainldg1failed,domainsuspendfailure. DomainMigrationofLDomldg1failed

To execute live migration of a domain with kernel zone operating, stop the kernel zone beforehand.

■

Live migration from a SPARC M10 system with XCP 2210 or newer, to another SPARC M10 system with XCP 2092 or older fails and produces the following error message:

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201536

Page 51

primary#

ldmmigrateldg1root@target-name



TargetPassword: Domainldg1isusingfeaturesofthesystemfirmwarethatarenotsupportedin

theversionofthefirmwarerunningonthetargetmachine.



DomainMigrationofLDomldg1failed.

When performing live migration from a SPARC M10 system with XCP 2210 or newer, to another SPARC M10 system, make sure to update the XCP firmware of the target system to XCP 2210 or newer.

Refer to the following table for the feasibility of performing live migration based

the version

of the firmware.

Table 3-4

Migrate from

SPARC M10 Systems (XCP 2230 or later)

SPARC M10 Systems (XCP 2210 or later)

SPARC M10 Systems (XCP 2092 or earlier)

SPARC T-series SPARC M-series (*1)

(SysFW 8.4 or later)

SPARC T-series SPARC M-series (*1) (SysFW 8.3 or earlier)

*1 It is a system like SPARC M5/M6 which supports Oracle VM Server for SPARC. *2 Live migration is possible only for cpu-arch=generic.

Version of the firmware that support live migration

Migrate to SPARC M10

Systems (XCP 2230 or later)

SPARC M10 Systems (XCP 2210 or later)

available available(*2) not available available not available

available available not available available available

available available available available available

available available not available available not available

available available available available available

SPARC M10 Systems (XCP 2092 or earlier)

SPARC T-series SPARC M-series (*1)

(SysFW 8.4 or later)

SPARC T-series SPARC M-series(*1) (SysFW 8.3 or earlier)

Notes on a case when recovery mode of Oracle VM Server for SPARC is enabled

■

Suppose that a system disk in a physical partition (PPAR (PPAR #A)) in which recovery mode is enabled is switched to a system disk that has been used for another PPAR (PPAR #B). The PPAR #A domain configuration information held

the XSCF may be overwritten on the PPAR #B domain configuration information.

If you want to use recovery mode to switch the system disk to the system disk that has been used for another PPAR and boot from the new system disk, perform the

Chapter 3　Information on Software 37

Page 52

following: Uninstall Oracle VM Server for SPARC from the system disk prior to switching. After the switch is completed, reinstall Oracle VM Server for SPARC on the system disk.

■

Suppose that you add a system board using dynamic reconfiguration of physical partitions in the condition where the domain configuration has been recovered in the degraded configuration. The added resource is not allocated automatically to any logical domain. Allocate the added resource manually. Alternatively, execute the ldm set-spconfig command to select

then reboot the physical partition using the poweron(8) and poweroff(8) commands.

■

Suppose that you delete a system board (PSB) using the deleteboard(8) command

where the version of Oracle VM Server for SPARC is earlier than 3.2 while the physical partition (PPAR) is powered on after the domain configuration is recovered in the degraded configuration. This deleteboard(8) command may fail.

After a domain

delete a system board using dynamic reconfiguration of physical partitions.

■

Suppose the firmware is updated to XCP 2230 or later and the recovery mode supported in Oracle VM Server for SPARC 3.1.1.1 or later is enabled. If the physical partition is started with the logical domain configuration information created with XCP 2221 or earlier after those operations, the following message

may

output to the console of the physical partition.

configuration is recovered in the degraded configuration, do not

the original domain configuration and

warning:Configuration'xxxx'couldnotbeimportedfromthe systemcontroller.



This is because the recovery mode of the logical domain configuration information created with XCP 2221 or earlier is not enabled. Execute the ldm add-spconfig command of Oracle VM for SPARC on the control domain and save the logical domain configuration information.

Notes on a case where openssl is used

Oracle Solaris provides accelerated cryptographic libraries for SPARC M10 systems. These libraries can be used by using the PKCS11 engine of OpenSSL. See man pages

openssl(5), engine(3openssl), and evp(3openssl), or the following OpenSSL documents:

http://www.openssl.org/docs/crypto/engine.html http://www.openssl.org/docs/crypto/evp.html

Please note:

■

The PKCS11 engine is the only way in OpenSSL to obtain the acceleration of cryptographic functions from the encryption arithmetic unit of the SPARC64 X processor.

■

The implementation of PKCS11 engine for OpenSSL in Oracle Solaris requires the enabling of EVP model for digest and encryption methods supported by engine.

- The following digest methods have been optimized for the SPARC64 X

processor:

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201538

Page 53

SHA1, SHA224, SHA256, SHA384, SHA512

- The following encryption methods have been optimized for the SPARC64 X processor:

DES-CBC, DES-EDE3-CBC, DES-ECB, DES-EDE3 AES-128-CBC, AES-192-CBC, AES-256-CBC AES-128-ECB, AES-192-ECB, AES-256-ECB AES-128-CTR, AES-192-CTR, AES-256-CTR

Here is an example on calling the accelerated version of AES method on SPARC64 X:

opensslspeed-enginepkcs11-evpAES-256-CBC



The following public SPARC64 X processor from Oracle Solaris 11.2.

RSA512, RSA1024, RSA2048 DSA512, DSA1024, DSA2048

key encryption methods have been optimized for the

The following is an example of the command to invoke the RSA2048 method optimized for the SPARC64 X processor.

opensslspeed-enginepkcs11rsa2048



■

To use the optimized digest method or encryption method in the PKCS11 engine with an application using the OpenSSL library (libssl, libcrypto), enable the EVP interface explained in evp(3openssl).



Notes on remote maintenance service

Note -

Enhanced Support Facility (ESF) and Remote Customer Support System (REMCS) are

supported only for SPARC M10 systems sold within Japan by Fujitsu.

This section describes notes when using the remote maintenance service. See

Enhanced Support Facility User's Guide for REMCS for how to set and use REMCS.

Before setting the remote maintenance service

To use the remote maintenance service with SPARC M10 Systems, you must perform settings for the REMCS agent function by using XSCF Web. In addition, the REMCS agent uses timezone information of XSCF. Perform the following settings in advance with the XSCF shell:

■

Setting necessary for using the XSCF Web, such as enabling the HTTPS setting

■

Setting the timezone for XSCF

After completing the above settings, perform settings for the REMCS agent function

Chapter 3　Information on Software 39

Page 54

using the XSCF Web. See Fujitsu M10/SPARC M10 Systems System Operation and Administration Guide for details of the XSCF Web settings and timezone settings.

Timezone for the REMCS agent function

The REMCS agent uses the timezone currently set for the system. For this reason, when you change the system timezone with XSCF, set the periodical connection schedule again to update the information of REMCS center.

Notes on SNMP

■

When using the SNMPv3 agent, after setting up the authentication protocol and the encryption protocol using the setsnmp(8) command, be sure to set up User-based Security Model (USM) management information using the setsnmpus m(8) command and View-based Access Control Model (VACM) management

information using the setsnmpvacm(8) command. Specification of the authentication

protocol and the encryption protocol is required in the SNMPv3 agent setup process. Moreover, the password, set up when executing the setsnmp(8) and setsnmpusm(8) commands, will also be necessary.

■

If a server, on which the SNMP manager is not running, is registered as the inform trap host of SNMPv3, execution of setsnmp(8), setsnmpusm(8) or setsnmpvacm(8) commands may output the "Agent restart failed" message. This message is output when there is an abnormality in the restarting of the SNMP agent, but SNMP agent works properly even if this messages is output, it has no effect on the system. Register the trap host after the SNMP manager had been started.

■

If the setsnmp(8) command is executed with the "addtraphost" or the "addv3traphost"

operands and a trap host is registered with the host name consisting of 16 or more characters, the UDP address of the trap that is reported to the trap host, becomes the IP address that is assigned to the XSCF-LAN (physical IP address), instead of the takeover IP address (virtual takeover IP address is set up.

IP address). This symptom occurs when a

If the host name of the trap host consists more than 16 characters, register the trap host with its IP address, not its host name.

[Workaround]

If a host name with more than 16 characters has already been registered, the setsnmp(8) command with either the "remtraphost" or the "remv3traphost" operands to remove the trap host and register the trap host again with the IP address.

■

When the trap host is registered with the setsnmp(8) command, the following message may be output.

the

execute

iptablesv1.4.7:host/network'example.com'notfound Try'iptables-h'or'iptables--help'formoreinformation.

This message indicates that the name resolution has not been executed for the host name of the registered host.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201540

Page 55

Although the trap host has been properly registered, traps are not reported to the trap host as name of the trap host could not be resolved.

Set up the name server by executing the setnameserver(8) command and conduct name resolution for the target host.

Problems with XCP and Workarounds

This section describes problems with XCP and workarounds for each version.

Problems that might occur with XCP 2240 and workarounds

The following table lists the problems that might occur with XCP 2240 and workarounds for them.

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

130109-003

RTIF2-

130219-004

RTIF2-

130219-006

Problems that might occur with XCP 2240 and workarounds

SPARC M10-

xx xIf you use the setpcl(8) command to

change the LSB number of a SPARC M10 system chassis to which a PCI expansion unit is connected and start Oracle Solaris

the logical domain configuration, you cannot display the configuration information of the PCI expansion unit by

executing the showhardconf(8) command.

xIf an error occurs with a crossbar unit

mounted on a crossbar box, many instances of "failed to read/write interrupt mask register" may be registered in the error log.

xx xIf you restart an XSCF by using the

flashupdate(8) or rebootxscf(8) command while a physical partition (PPAR) is being powered on, the POST may stop in

state where the diagnosis is completed

(Initialization Complete).

Use the setdomainconfig(8) command to set the logical domain configuration to the factory-default, and power on the physical partition (PPAR). Then, configure the logical domain again.

There is no effective workaround. Power off the physical partition (PPAR) and replace the crossbar unit in the crossbar box.

Execute the reset por command, or power off the PPAR by using the poweroff -f command

again.

and then power it

Chapter 3　Information on Software 41

Page 56

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

130305-001

RTIF2-

130305-002

RTIF2-

130305-007

RTIF2-

130305-013

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx x

xx xIf an error in the CPU or memory is

xx xFRU registered in the error log is

x x x While XSCF is starting, process down,

"The limit of power has been exceeded" is

registered in the event log if you perform

the following. Execute the setpowercapping(8) command to set the power consumption limiting function to "Enable", the power consumption maximum allowable value to "Specify 100 percent (default)", and the time extension when exceeding the maximum allowable power consumption to "none." Then, turn on the input power supply or turn off the partition (PPAR).

detected and if the XSCF is switched while the XSCF is notifying the error information to the control domain, the error information may not be notified again to the control domain. Because of this, the error information displayed with the showlogs error displayed in the Fault Report output by the fmdump command.

displayed as "PPAR#30" if the configuration

error of the system board (PSB) is detected when executing the testsb(8) command or diagxbu(8) command.

panic or watchdog timeout occurs, which may cause XSCF to be reset.

power to the physical

command is not

There is no effective workaround. Ignore this event log.

There is no effective workaround.

Maintain according to the FRU displayed

the showlogs error command.

There is no effective workaround.

Maintain the applicable PSB of SPARC M10 system chassis.

Confirm that XSCF is successfully started.

If it is not started, turn off the power of the physical partition (PPAR), and then disconnect the input power supply to the system and back on again (AC OFF/ON).

When recycling the power supply to the system, wait for 30 seconds or more to turn on the input power supply disconnecting. In case XSCF is not started even if recycling the input power supply to the system, replace the CPU memory unit lower (CMUL) or the motherboard unit

(MBU).

RTIF2-

130305-020

xIf an XSCF panic or hang-up occurs, an

error log showing that "XSCF hang-up is detected" may be posted many times.

There is no effective workaround. Ignore the logs with the same contents that were notified at the same period of time considering that they are caused by the same reason.

after

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201542

Page 57

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

130305-022

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xThe poweron(8) command may fail with

the output of the following message if an error log showing that "XSCF hang-up is detected" was detected and an "unknown" system board (PSB) was found by the showboards(8) command. The same can be said for the instruction

power-on using the XSCF Web, APCS,

the power supply interlocking.

There is no effective workaround. Use the showboards(8) command to replace the XSCF of the PSB, which is shown as "unknown".

Not powering on : An internal error has occurred. Please contact your system administrator.

RTIF2-

130305-023

RTIF2-

130305-025

RTIF2-

130329-005

RTIF2-

130410-001

RTIF2-

130410-002

xWhen

If an error occurs in the DC-DC converter

of a

crossbar unit, "XB-XB interface link-up error." is erroneously registered instead of the correct error log of "LSI detected errors with power subsystem failure."

xIf the poweroff(8) command is executed

the system that has more than one physical partition (PPAR), it takes time for the processing because the power of the PPARs is disconnected one by one. Depending on the system configuration,

may take about one hour.

you turn on the input power supply in SPARC M10-1, READY LED of XSCF remains blinking and the system may not start.

xThe diagnosis of the system board may

fail during the power-off of the system board (PSB) by executing the diagxbu(8)

testsb(8) command, displaying the following message. [Warning:010] An internal error has occurred.

xThe switching of an XSCF may fail if the

XSCF is switched by executing the switchscf(8) command while a physical partition (PPAR) is being powered on.

There is no effective workaround. Check for power errors if the error log of "XB-XB interface link-up error" was registered. Ignore the error log for "XB-XB interface link-up error" if a power error has occurred.

There is no effective workaround.

There is no effective workaround. Power off the input power supply and then power it on again.

There is no effective workaround. Execute the showboards(8) command to check that the [Pwr] field of the relevant

set to "n".

PSB is If the field is set to "y", execute the showboards(8) command every few minutes to check that the field changes to "n".

Do not switch an XSCF by using the switchscf(8) command while a PPAR is being powered on.

Chapter 3　Information on Software 43

Page 58

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

130410-003

RTIF2-

130516-002

RTIF2-

130516-004

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xIf a physical partition (PPAR) is powered

on in

the system that satisfies all the following conditions, other PPAR may also be powered on.

- The power supply interlocking is

enabled with the setremotepwrmgmt (8) command.

- A node is created whose SubNodeID is

not set in a power supply interlocking management

item.

- Multiple PPARs are configured.

xIf XSCF switching or an XSCF reset

occurs while the physical partition (PPAR) is being powered off, it may be impossible to turn off the power.

xIf a hardware failure occurs in a 4BB or

greater configuration, automatic cluster switching may fail.

If 16 or more guest nodes are incorporated

into a single cluster, the following warning message may be output to the console of the control domain.

- When power supply interlocking is not necessary Disable power supply interlocking with setremotepwrmgmt -c disable and then delete the power supply interlocking setting with the clearremotepwrmgmt (8) command.

- When power supply interlocking is necessary If the system has multiple PPARs, create a management file for power supply interlocking by specifying a PPAR-ID as a SubNodeID, and then register the power supply interlocking setting with setremotepwrmgmt -c config.

There is no effective workaround.

While powering off PPAR, do not use the switchscf(8) command to perform XSCF switching or the rebootxscf(8) command

perform an

If automatic cluster switching fails,

follow the procedure in the manual of the cluster software to perform switching

manually.

SA SA_xscf????.so to test host ??? failed

RTIF2-

130516-006

xIf XSCF switching occurs while multiple

physical partitions (PPARs) are being powered on at the same time, it may take more than usual to power them on.

There is no effective workaround.

Do not switch an XSCF by using the switchscf(8) command while PPARs are being powered on.

XSCF reset.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201544

Page 59

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

130702-001

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xxIf the following applies, "I/O devices

error detected" is detected at the time of PPAR power-on and control domain reboot: In SPARC M10-4/M10- 4S, the CPU memory unit upper (CMUU) is added to a configuration that has been operated with only the CPU memory unit lower (CMUL) and false has been

the IOreconfigure setting of the

physical partition (PPAR).

There is no workaround for errors that are detected at power-on after the addition. Making the following setting prevents the error detection that occurs every time the PPAR is powered on or the control domain is rebooted.

set

1. After starting Oracle Solaris, the ldm rm-io command to delete the

PCIe root complex of the added CMUU from the configuration of the control domain.

2. Execute the ldm add-spconfig command to save the constructed logical domain configuration to the XSCF.

RTIF2-

130710-001

RTIF2-

130711-003

If XSCF switching is performed using the

switchscf(8) command, in rare cases, the standby XSCF may not start.

x Before active replacement of the XSCF

unit of the crossbar box is completed, the replacefru(8) command is completed normally.

There is no effective workaround. [How to restore] Turn off and then turn on the input power supply (AC OFF/ON) to every SPARC M10-4S or execute the replacefru(8) command to perform pseudo replacement (replacement work without replacing any parts) of the SPARC M10-4S that does not start.

When you use the replacefru(8) command to replace the XSCF unit, the following message may appear after you replace the XSCF unit. If it does, wait for

minutes, and then enter The replacement of XBBOX#xx/XSCFU has completed normally.[f:finish] :

RTIF2-

130802-003

xWhen you replace the XSCF unit of the

crossbar box by using the replacefru(8) command, the command is completed normally, but the following error log may be registered. The suspected location indicated by this error log is incorrect.

Replace the XSCF unit of the same crossbar box command again. If you have turned off the input power (AC OFF) during the replacement work, disconnect and then connect all the XSCF BB control cables.

SCF:Board control error (link failed)

RTIF2-

130919-001

xIn case of a system comprising of several

SPARC M10-4S, if input power is turned off and on (AC OFF/ON) on a number of SPARC M10-4S chassis, while some other slave chassis are running, the physical partitions may not start.

When performing AC OFF/ON, do so on all the chassis comprising [How to Restore] Turn off input power of all the chassis comprising the system and then turn on the input power.

"f".

using the replacefru(8)

a system.

execute

Chapter 3　Information on Software 45

Page 60

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

131001-002

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

x While a physical partition (PPAR) is

operating or when a PPAR is turned off, master/standby XSCF switching may occur. If master/standby switching occurs, the following message is displayed on the console of the master XSCF.

There is no effective workaround. As a result switching occurs, but this does not affect the system, and the system can be

operated continuously.

Kernel panic - not syncing: MBC Dual ifcut interrupt.

RTIF2-

131112-001

RTIF2-

131112-013

RTIF2-

131126-003

xx xIf data is transmitted via SSH by the

snapshot(8) -t command, this transmission

may be delayed by about 10 to 30 minutes in comparison with transfer using USB devices and XSCF Web.

Suppose that multiple physical partitions

(PPARs) are simultaneously started by the poweron -a command. The error message "Error storing configuration variable. LDC is not up Configuration variable setting will not persist after a reset or power cycle" may be output to the OS console after the message "Unable

connect to Domain Service providers."

Solaris may be started without

Oracle applying the OpenBoot PROM environment variable specified with the setpparparam(8) command.

x x x Update of the PCI expansion unit

firmware may fail. If it fails, "LINKCARD update is failed" appears in the event log. [Example]

There is no effective workaround. Even if transfer is delayed, there is no problem with the collected data.

There is no effective workaround. Restart the control domain for the physical partition (PPAR) for which the error message was output.

There is no effective workaround. Execute the ioxadm -c update command

update the PCI expansion unit

firmware again. SCF:LINKCARD update is failed (LINKCARD=1, bank=0, PCIBOX version=1130: last version=1120)

RTIF2-

131213-001

xIn a configuration with 3 or more BBs, or

with crossbar boxes, when the XSCF master/standby switchover is executed due to some abnormality on the master XSCF, the master XSCF may fail to switch over to the standby XSCF and start up as another master XSCF. Due to this, the

seems to contain two master

system XSCFs. Normal behavior of a system is not guaranteed when there are two master XSCFs in the system. This state can be confirmed by a lighted MASTER LED at the rear panel of two chassis.

There is no effective workaround.

[How to restore]

The system can be when the number of master XSCFs automatically returns to one after a few

minutes.

If the number of master XSCFs does not return to one even after 15 minutes, press the RESET switch at the rear panel of all existing SPARC M10 systems and crossbar boxes. The system can

operated normally after that.

of this defect, master/standby

operated normally

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201546

Page 61

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

131213-002

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xWhile in the process of adding or

removing a system board (PSB) using the addboard(8) or deleteboard(8) command

the DR feature, if another physical partition is rebooted due to hardware failure or the poweroff(8)/poweron(8)/ reset(8) command is executed on it, the executed addboard(8) or deleteboard(8) command may detect timeout and terminate abnormally.

Do not execute the poweroff(8)/poweron (8)/reset(8) command while the addboard(8) or deleteboard(8) command

being executed. There is no effective workaround if any hardware failure occurs while executing DR. [How to restore] Check the status of the system board

(PSB) using the showboards(8) command.

Execute the addboard(8) or deleteboard (8) command after that.

RTIF2-

131213-003

xWhile executing the poweroff(8)/

poweron(8)/reset(8) command on a physical partition, if the addboard(8) or the deleteboard(8) command of the DR feature is executed on another physical partition to add or remove a system board (PSB), the addboard(8) or deleteboard(8) command may detect timeout and terminate abnormally.

Do not execute the addboard(8) or deleteboard(8) command while the poweroff(8)/poweron(8)/reset(8) command is being executed elsewhere. There is no effective workaround if DR is executed while also executing power supply operations on another physical partition. [How to restore] Execute the following:

1. Execute the showboards(8) command.

2. Check the status of /Pwr/Conn/Conf/

Test of the system board (PSB) to confirm the end of power operations.

End of power-on/reset: The status of Pwr/Conn/Conf/Test is

"y y y

End of power-off: The status of Pwr/Conn/Conf is "n n

respectively

3. Re-execute the addboard(8) or the

deleteboard(8) command.

RTIF2-

131213-010

xx x

When the firmware of the PCI Expansion

Unit is updated with the "ioxadm –c update" command, process down may occur at the XSCF firmware.

There is not effective workaround. Re-execute the "ioxadm –c update" command to update the PCI Expansion Unit firmware again.

passed" respectively.

Chapter 3　Information on Software 47

Page 62

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

131213-011

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

When a SPARC M10-4S or a crossbar box

added using the addfru(8) command, the following message is output and the addition may fail. [Warning:036] Failed to find BB#x. The BB-ID setting and/or the cable connections of the BB#x will be wrong. Please confirm the BB-ID setting and the cable connections. Do you want to try to add BB#x again? [a:add|c:cancel] :

When the following maintenance menu

output after executing the addfru(8)

command, input power on the SPARC

M10-4S or the crossbar box to be added and execute the next operation (step 2) after 20 minutes.

Please execute the following steps:

1) After the added device is connected with the system, please turn breaker of the BB#x.

2) Please select[f:finish] :

[How to restore] Input "a" in response to the "[a:add|c: cancel] :" message and re-execute the addfru(8) command.

the

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201548

Page 63

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

131213-012

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

x After replacing SPARC M10 with the

replacefru(8) command, diagnosis processing may not terminate properly.

There is no effective workaround. [How to restore] Re-execute the replacefru(8) command.

[Example]The replacement of BB#2: Diagnostic tests for BB#2 have started. Initial diagnosis is about to start, Continue?[y|n] :y PSB#02-0 power on sequence started.

0.....30.....end

Initial diagnosis started. [7200sec]

0..... 30..... 60..... 90.....120.....150.....180.....

210.....240.....

270.....300.....330.....360.....390.....420.....450

.....480.....510.....

540.....570.....600.....630.....660.....690.....720

.....750.....780.....

810.....840.....870.....900..end

Initial diagnosis has completed. PSB power off sequence

0..... 30..... 60..... 90.....120.....150.....180.....

started. [1200sec]

210.....240.....

270.....300.....330.....360.....390.....420.....450

.....480.....510.....

540.....570.....600.....630.....660.....690.....720

.....750.....780.....

810.....840.....870.....900.....930.....960.....990

.....1020.....1050.....

1080.....1110.....1140.....1170.....1200end

Failed to power off. Please check the FRU.

An internal error has occurred. Please contact your system administrator. done

RTIF2-

131213-014

xx x

[Warning:030] testsb failed.[c:cancel] :

If the time zone of XSCF is changed using

the settimezone(8) command, the time zone of Oracle Solaris on that physical partition, which is booted after the change, gets misaligned to the tune of the time difference before and after changing the time zone of the XSCF. [Example] If the time zone before setup was UTC and after setup is misalignment of Oracle Solaris will be 9 hours.

JST, the time

There is no effective workaround. Boot the Oracle Solaris after executing the resetdateoffset(8) command and set

the right time on the Oracle Solaris.

Chapter 3　Information on Software 49

Page 64

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

131213-019

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

x x x While XSCF is starting after being

powered on, watchdog timeout may occur and XSCF is reset. After this reset is completed, the configuration information

the components mounted on the system cannot be checked by the showhardconf(8) command.

Moreover, error logs regarding the following configurations may be registered. Msg:Indispensable parts are (PSU).

not installed

There is no effective workaround.

[How to restore]

Re-execute power off and on.

Msg:Indispensable parts are not installed (FAN). Msg:Indispensable parts are not installed (OPNL). Msg:PSU shortage Msg:FAN shortage

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201550

Page 65

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

131213-022

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

x After firmware update, if the XCP

version is checked by the version(8) command or the XSCF Web interface, versions of each crossbar box (XBBOX) or the XCP of SPARC M10-4S (BB) may not

the same as the updated XCP version. In the following example, although the firmware has been updated from XCP 2042, the XCP of "XCP0

(Reserve):" of BB#00 has not been updated.

version -c xcp -v

XSCF>

to XCP2052

There is no effective workaround. [How to restore] Specify the BB-ID of the crossbar box (XBBOX) or of the SPARC M10-4S (BB), which was not updated, to the "rebootxscf -b BB-ID" command and execute it to reset the XSCF of the specified chassis.

XBBOX#80-XSCF#0 (Master) XCP0 (Reserve): 2052 XSCF : 02.05.0002 XCP1 (Current): 2052 XSCF : 02.05.0002 XBBOX#81-XSCF#0 (Standby) XCP0 (Current): 2052 XSCF : 02.05.0002 XCP1 (Reserve): 2052 XSCF : 02.05.0002 BB#00-XSCF#0 XCP0 (Reserve): 2042 CMU : 02.05.0002 POST : 1.43.0 OpenBoot PROM : 4.34.0+1.22.0 Hypervisor : 0.27.8 XSCF : 02.04.0000 XCP1 (Current): 2052 CMU : 02.05.0002 POST :

1.43.0 OpenBoot PROM : 4.34.0+1.22.0 Hypervisor : 0.27.8 XSCF : 02.05.0002

RTIF2-

140121-001

RTIF2-

140212-003

xx x

If the input power is turned off (AC OFF)

while the XSCF is processing large amounts of data, only occasionally, XSCF may not start-up when the input power

turned on (AC ON) again.

xx xThe OID information of "scfPsbInfo" in

the definition file of XSCF extension MIB

not updated even if the information of

the system board (PSB) is updated.

There is no effective workaround. Contact a field engineer if this problem occurs.

Restart the snmp daemon using any of the setsnmp(8), setsnmpusm(8) or the setsnmpvacm(8) commands or reset XSCF.

Chapter 3　Information on Software 51

Page 66

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140212-005

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx xIn the OID information of

"scfComponentStatusEvent" in the definition file of XSCF extended MIB, the path information of the suspected components may be denoted as "unspecified" in the trap notification.

There is no effective workaround.

This symptom occurs when the OID "FaultEventCode" information is any of the following: 05018113 05018123 05018133 05018211 05018221 05018231

RTIF2-

140212-007

x x x When an attempt is made to register a

password containing 256 or more characters, in the password input prompt

either the setsnmp(8) or the setsnmpusm(8) command, only 255 characters are registered.

When setting up a password equal to or

longer than 256 letters, use the password

option of either the

setsnmpusm(8) command, instead of

using the password input prompt.

[How to restore] If a password equal to or longer than 256 characters has been registered using the password input prompt, remove the target user data with either the "setsnmp remv3traphost" or the "setsnmpusm delete" command and then register the

user again.

RTIF2-

140212-008

RTIF2-

140212-011

RTIF2-

140212-012

x x x When powering on, or rebooting a

physical partition (PPAR), even if the process is stopped due to the failure of a component, the POWER LED of the operation panel keeps blinking.

xIf the XSCF master/standby switchover

occurs when the physical partition (PPAR) is running, in some very rare cases, XSCF process down may occur and the XSCF may be reset.

xIn a system configuration with 3 or more

BBs or with a crossbar box, if the XSCF master/standby switchover occurs for 60

more times, a process down may occur

the slave XSCF and the slave XSCF is

reset.

There is no effective workaround.

There is no effective workaround. The system can be operated continuously as it will be restored after being reset.

There is no effective workaround. The slave XSCF will be restored and the system can be used continuously after that.

setsnmp(8) or the

the reset

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201552

Page 67

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140212-013

RTIF2-

140212-014

RTIF2-

140212-016

RTIF2-

140212-021

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx xDue to the failure of a DIMM, the "CPU

internal fatal error", which suspects the motherboard unit (MBU), CPU memory unit lower (CMUL) or the CPU memory unit upper (CMUU), may be registered when powering on the physical partition (PPAR).

x x x Even if the "CPU cache degraded (CPU

#xx)" error is detected, the CHECK LED

the operation panel may not light up.

xx xWhen resetting XSCF, the "snmpd

[XXXXX] svrSP: error doAction ACTION_CONTROL_LED" error message regarding SNMP may be displayed on the XSCF serial terminal.

xIf any of the physical partitions is reset

due to some hardware failure, in the middle of the execution of the testsb(8) command, the testsb(8) command may terminate abnormally. The following is an example of such an error.

There is no effective workaround. If after replacing the MBU, CMUL CMUU in question, the same error is registered again, replace all the DIMMs that are mounted on the MBU, CMUL and the CMUU.

There is no effective workaround.

There is no effective workaround. Ignore this message.

There is no effective workaround. [How to restore] Execute maintenance on the failed hardware after confirming it with the showlogs(8) command. After that, execute the testsb(8) command again.

[Example]

testsb

XSCF>

PSB_NO

Initial diagnosis is about to start, Continue?[y|n] :y SB power on

sequence started.

0.....30.....end

Initial diagnosis started. [7200sec]

0..... 30..... 60..... 90.....120.....150.....180.....

210.....240.....

270.....300.....330..

Hardware error occurred by initial diagnosis. SB power off sequence started. [1200sec]

0..... 30..... 60..... 90.....120.....150.....180.....

210.....240.....

270.....300.....330.....360.....390.....420.....450

.....480.....510.....

540.....570.....600.....630.....660.....690.....720

.....750.....780.....

810.....840.....870.....900.....930.....960.....990

.....1020.....1050.....

1080.....1110.....1140.....1170.....1200end

Failed to power off. Please check the FRU.

An internal error has occurred. Please contact your system administrator. done.

Chapter 3　Information on Software 53

Page 68

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140227-004

RTIF2-

140227-005

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx xIf a link card is removed from the system

PCI hot plugging (PHP), using the cfgadm(1M) command on the logical domain on which it is mounted, and thus power supply to it is stopped, the "LINK CARD 12C error" log may be mistakenly registered.

xAt the time of cold replacement or cold

addition of CPU memory unit lower (CMUL) or SPARC M10 chassis, if the following conditions are met, the "XCP firmware version synchronization failed" message may be registered to the event log and maintenance or addition fails.

- Two or more CMUL or SPARC

chassis is cold replaced or cold added

one time.

M10

- The XCP versions of replacement

components do not match the version

the master XCP.

There is no effective workaround. Ignore this link card has been stopped for sure and the system can be operated continuously.

When cold replacing or cold adding two

more CMUL or SPARC M10 chassis,

use the replacefru(8) or addfru(8)

command to perform the operations

one.

[How to restore]

Execute any of the following procedures.

- Procedure 1

Perform AC OFF/ON

Execute the flashupdate(8)

command, specifying the XCP version.

XSCF>

flashupdate -c update -m xcp -s

xxxx

xxxx is the XCP version of the master

XSCF

- Procedure 2 Execute the replacefru(8) command to perform a pseudo replacement of the CMUL or SPARC M10 chassis that failed to be cold replace.

RTIF2-

140227-009

RTIF2-

140227-010

xx xIf XSCF login is performed with a XSCF

user account, whose privileges are managed by a LDAP server, specified by the setldap(8) command, execution of commands in the XSCF shell or operations on the XSCF Web may take a while.

xThe following improper error message is

displayed when the "addboard -c configure" command is executed, specifying a non-existent system board (PSB):

In case of a LDAP server, specified by the setldap(8) command, workaround. Specify the LDAP server with the setldapssl(8) command.

There is no effective workaround. Execute the "addboard -c configure" command, specifying existent

PPAR is currently unavailable for DR, because XBU status has failed Or The current configuration does not support this operation

RTIF2-

140304-001

x When performing AC OFF/ON, in some

very rare cases. the "SCF process down detected" error message is registered and XSCF fails to start.

There is no effective workaround. If this symptom has occurred, contact the

maintenance staff.

error log. Power supply to the

one

-f

there is no effective

PSBs.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201554

Page 69

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140304-002

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx xThe "SCF process down detected" error

log may be registered when the flashupdate(8) command is running.

There is no effective workaround. [When restoration is not required] If both of the following conditions are met, there is no need for restoration. It may be assumed that firmware update has completed properly.

- The reveals that the following diagnostic message along with the "Msg: SCF process down detected" error message had been registered when the flashupdate(8) command was running.

[Example] Diagnostic Code: 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 666c6173 68757064 6174652e xxxxxxxx 00000000 00000000 0000 where, xxxxxxxx is

"showlogs error -rv" command

- The "showlogs event" command displays the "XCP update has been completed" event log.

[How to restore] Re-execute the flashupdate(8) command.

RTIF2-

140304-003

xx xIn case of SNMPv3, if the trap host name

registered by the setsnmp(8) command contains a colon (:), it does not show up properly by the showsnmp(8) command. [Example] In case the trap host name is "test:

In case of SNMPv3, do not register a trap host name with the setsnmp(8) command, that contains a colon (:). If such a trap host name has already been registered, use the following command to remove the trap host name:

example.com" , the host name is shown

"test" and port number is shown as "0".

setsnmp remv3traphost -u 'username' -p 'port_nunber' trap_host_name

indefinite

In such a case, be number. If the port number is not specified when removing a trap host name that includes a colon(:), the "Entry does not exist" message is displayed and the trap host name is not removed. The port number specified at the time of removal should be wrongly displayed by the showsnmp(8) command, but the one specified at the time of registration.

Chapter 3　Information on Software 55

sure to specify a port

the one, which is not

Page 70

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140304-004

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xIn case of a SPARC M10-4S that is

attached to cross-bar box, if XSCF failure occurs on a portion of chassis when the physical partition (PPAR) is in the powered on state, the follow symptom may occur:

- Symptom 1 When the poweroff(8) command is executed, the power on the PPAR turned off, but the command prompt does not respond for about 20 minutes.

If XSCF failure has occurred, replace the CPU memory XSCF unit.

[How to restore]

- Case of symptom 1 After about 20 minutes, the poweroff(8) command ends properly and the prompt comes back.

- Case of symptom 2 Forcibly power off the PPAR using the "poweroff -f" command.

- Symptom 2 When the PPAR is powered on, the "XB-XB interface fatal error" error is produced, the power on process is repeated and it does not end properly.

RTIF2-

140304-005

xOn a physical partition (PPAR) that is

composed of several SPARC M10-4S (system board) , after a system board has been degraded due to failure, if the setpciboxdio(8) command is executed to disable/enable the direct I/O feature of the PCI card mounted on the PCI expansion unit which is attached to degraded chassis, without powering off the PPAR first, the following message is output and the command fails: "This operation cannot be done because the PPAR including a PSB of the target

BB is

powered on" This symptom occurs when the state of system board is like the following, which

be derive from either the

can showhardconf(8) or the showboards(8) command. [Example] When PSB#01-0 (BB#01) has been degraded.

showhardconf

XSCF> ...

Change the configuration of I/O feature with the setpciboxdio(8) command only after removing the degraded system board from the physical partition with the deleteboard(8) command.

[Example]

the

deleteboard -c unassign 01-0

XSCF>

After changing the configuration of the direct I/O feature, assign the system board to the PPAR with the addboard(8) command and then mount board onto the PPAR, following the

maintenance procedure. [Example]

addboard -c assign -p 0 01-0

XSCF>

Meanwhile, from XCP 2210 onwards, this

problem can be solved by performing

maintenance on the degraded chassis by the replacefru(8) command. In such a case, the above procedure is unnecessary.

* BB#01 Status:Deconfigured; ...

showboards -a

XSCF> PSB PPAR-ID(LSB) Assignment Pwr Conn Conf Test

Fault

--- ------------ ----------- ---- ---- ---- -------

-------01-0 00(01)

Passed Faulted

Assigned

n n

unit lower (CMUL) or the

the direct

the system

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201556

Page 71

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140304-006

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx xNo error log is registered when any of

the following occurs :

- the power supply (PSU) fails due to PSU shortage (power off started), PSU shortage, and the wrong PSU is installed.

Execute the replacefru(8) command to perform cold replacement if a PSU is replaced for the first time after any of the error logs shown in [Description] is registered. In such a case, do not perform active replacement or

- if the errors re-occur on the PSU of the same chassis.

- after active replacement or hot replacement replacefru(8) command

of the PSU by the

When the power supply unit (PSU) fails due to any of the following errors, and after active replacement or hot replacement of the PSU by the replacefru(8) command, if any of the following errors re-occur on the PSU of

the same chassis, no error log is registered.

- PSU shortage (power off started)

- PSU shortage

- Wrong PSU is installed

RTIF2-

140304-007

RTIF2-

140402-001

xx xThe following special characters cannot

xWhen replacing power supply units

(PSUs) with the replacefru(8) command,

the [f] key in the menu of the

replacefru(8) command is pressed within

seconds after mounting the new PSU, any problem in the new PSU cannot be detected.

field for the [Settings] - [Service] [SMTP], [Settings] - [Email Reporting], [Settings] - [Audit], and [Settings] [CoDActivation] menus on the XSCF We

included in the mail address input

See "Workaround for RTIF2-140304-007".

Use the setemailreport(8) command of the XSCF shell.

b. "!" "#" "$" "%" "&" "'" "*" "+" "/" "=" "?" "^"

RTIF2-

140402-003

"`" "{" "|"

xx xWhen using XSCF Web in Internet

Explorer, if you attempt to delete the second and subsequent User/Group settings of [Groups] and [View Access] of VACM in the [XSCF] - [Settings] [Service] - [SNMP Security] menu, an error message is output and the deletion cannot be executed.

"}" "~"

Execute the deletion by

Firefox or the setsnmpvacm(8)

command of the XSCF shell.

hot replacement.

using XSCF Web

Chapter 3　Information on Software 57

Page 72

Table 3-5

nfig

RTI No. 1 4 4S Description Workaround

RTIF2-

140403-001

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx xIf you connect to the control domain

console by executing the console(8) command on the XSCF serial terminal and then execute any of the following while the control domain console outputs

message, the "SCF process down detected" error may occur and the XSCF may be reset.

- Entering "#" to

domain console

disconnect the control

Execute the console(8) connecting to the XSCF via telnet or ssh,

terminate the console(8) command

after powering off the PPAR.

- Executing the console(8) command by

specifying the -f option from another terminal to forcibly connect to the control domain console of the physical partition (PPAR)

- Executing the switchscf(8) command to

switch the master XSCF

- Executing the rebootxscf(8) command

reset the XSCF

RTIF2-

140407-001

x x x Suppose you attempt to execute the

dumpconfig(8) command to save XSCF setting information, and then execute the restoreconfig(8) command to restore the XSCF setting information in the same chassis or other chassis. In this case, some settings may not be saved/restored or may be excessively restored on other chassis. The following

settings are not saved/ restored in the same chassis or other chassis.

- Setting values for power operation at

power recovery, set with the setpowerschedule -c recover command

- Setting values for enabling/disabling

ASR function, set with the setservicetag (8) command

- PPAR DR feature setting values set

with the setpparmode -p ppar_id ppar_dr command for XCP 2210 or later of the SPARC M10-4S.

- Setting values for configuring a power

supply interlocking group, changing its settings, and enabling/disabling the power supply interlocking function for the group, set with the setremote

wrmgmt(8) command

-m

There is no effective workaround.

[How to restore]

Execute the following procedure.

1. Before saving the XSCF setting information with the dumpconfig(8) command, confirm the following settings.

Setting for power operation at power

recovery(recover mode) [Example] Not powering on at power recovery

showpow erschedule -a -m state

XSCF>

PPAR-ID schedule member recover mode

------- -------- ------ ------------

ASR function (Service Tag)

enable/disable setting

showservicetag

XSCF> Enabled

PPAR DR feature enable/disable setting

[Example] Disabled

showpparmode -p 0

XSCF>

--- Omitted --PPAR DR(Current) :PPAR DR(Next) :off

Power supply interlocking group setting

Savi

enable

command after

off

uration and settin

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201558

Page 73

Table 3-5

han

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

The following settings are excessively restored on the same or other chassis.

- Information on the time difference between XSCF and the hypervisor of each physical partition (PPAR)

The following settings are excessively restored on other chassis.

[Example] Saving management file to ftp server when registering one power supply interlocking group XSCF>

ftp://server[:port]/path/file

- Setting values for the LDAP client, set with the setldap(8) command

- Setting values for the client, set with the setldapssl(8) command

LDAP over SSL

- Configuration setting values for the Active Directory, set with the setad(8) command

- Setting values for the SNMP agent, set with the setsnmp(8)/setsnmpusm(8)/ setsnmpvacm(8) command

- Setting values for the SMTP service, set with the setsmtp(8) command

[Example] Enabled XSCF>

[Remote Power Management Group#01 Information] Remote Power Management Status :[Enable]

--- Omitted ---

Time difference between XSCF and the hypervisor of each PPAR

[Example]

getremotepwrmgmt -G 1

Power supply interlocking function enable/disable setting

showremotepwrmgmt

- Setting values for the e-mail notification

function, set with the setemailreport(8) command

Furthermore, since the PPAR DR feature setting values cannot be saved/restored, powering on the PPAR after executing the following procedure switches the logical domain configuration information

the factory-default state.

1. Execute the setpparmode -p ppar_id -m

ppar_dr command to enable/disable the PPAR DR feature.

Execute the dumpconfig(8) command

save XSCF setting information.

3. Initialize the chassis to factory defaults

executing the initbb(8) or the

restoredefaults(8) command.

4. Restore the XSCF configuration

information of the chassis in procedure

with executing the restoreconfig(8)

command.

5. Power on the PPAR by executing the

poweron(8) command.

showdateoffset -a

XSCF> PPAR-ID Domain Date Offset

--- Omitted ---

2. Execute the dumpconfig(8) command

save the XSCF setting information.

3. If the XSCF setting information is to be restored restoreconfig(8) command on that chassis to confirm the following settings before restoring the XSCF setting information.

LDAP client setting [Example] To display all LDAP setting information except the CA certificate and password

showldap

XSCF> Bind Name: Base Distinguished Name: Not set LDAP Search Timeout:

Password:

Bind LDAP Servers: CERTS: No

ges

there is a time difference between XSCF and the hypervisor of each PPAR

sec sec

sec

on another chassis, execute the

Not set

Chapter 3　Information on Software 59

Page 74

Table 3-5

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

LDAP over SSL client setting

[Example] To display enabled/disabled

status of LDAP over SSL

showldapssl

XSCF>

usermapmode: disabled state: disabled strictcertmode: disabled timeout: 4 logdetail: none

Configuration setting of the Active Directory

[Example] To display enabled/disabled status of the Active Directory

showad

XSCF> dnslocatormode: disabled expsearchmode: disabled state: disabled strictcertmode: disabled timeout: 4 logdetail: none

SNMP agent setting

[Example] To display the SNMP agent setting information

showsnmp

XSCF> Agent Status: Agent Port: System Location: System Contact: System Description: Unknown Trap Hosts: None SNMP V1/V2c: None

[Example] To display the setting information for the SNMPv3 agent USM

showsnmpusm

XSCF> Username

--------

user_name

[Example] To

information for the SNMPv3 agent VACM

showsnmpvacm

XSCF> Groups: Groupname

--------test_group Views: None Access: None

SMTP service setting

[Exam

le] To displa

Disabled

161

Unknown

Auth Encrypt

---- ------SHA DES

display the setting

Username

-------user_name

the SMTP settin

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201560

Page 75

Table 3-5

hyp

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

formatio

i XSCF>

showsmtp

Mail Server: Port: 25 Authentication Mechanism: none Reply Address:

E-mail notification function setting [Example] To display the e-mail report setting information

showemailreport

XSCF> E-Mail Reporting: disabled

4. Execute the restoreconfig(8) command

restore the XSCF setting information.

5. After restoring the XSCF setting

information with the restoreconfig(8) command, execute the command below to implement a reset using the setting values confirmed in step 1. Or, initialize the time difference.

Restoring setting for power operation

power recovery [Example] Not powering on at power recovery

setpowerschedule -a -c

XSCF>

recover=off

Restoring ASR function (Service Tag) enable/disable setting

[Example] Setting to enable

setservicetag -c

XSCF>

Restoring PPAR DR feature enable/disable setting

[Example] Setting to disable

setpparmode -p 0 -m ppar_dr=off

XSCF>

Restoring configuration and setting changes of power supply interlocking group and enable/disable setting of

power supply interlocking function [Example] Restoring setting information based on management file saved to FTP server

setremotepwrmgmt -c

XSCF>

"ftp://server[:port]/path/file"

[Example] Enabled when saving

setremotepwrmgmt -c enable

XSCF>

Initializing time difference between

XSCF a

enable

ervisor of each PPAR

config

Chapter 3　Information on Software 61

Page 76

Table 3-5

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

After cleari information to 0, power on the physical partition, synchronize the Oracle Solaris time with the NTP server, or adjust the time with the date(1) command.

[Example] Time difference existing at

saving

resetdateoffset -y -a

XSCF>

6. When restoring to another chassis, execute the command in step 3 again,

reconfirm the settings.

and

If the settings after restore differ from the settings before restore, execute the command below to implement a reset

using the values confirmed in step 3.

Restoring LDAP client setting

[Example] Setting LDAP search timeout

value to 60 seconds

setldap -T 60

XSCF>

Restoring LDAP over SSL client setting

[Example] Setting LDAP over SSL to

disable

setldapssl disable

XSCF>

Restoring Active Directory configuration

settings

[Example] Setting Active Directory to

disable

setad disable

XSCF>

Restoring SNMP agent settings

[Example] Stopping SNMP agent

setsnmp disable

XSCF> setsnmp: Agent disabled.

[Example] Registering SNMPv3 agent user

setsnmpusm create -a SHA -p

XSCF>

xxxxxxxx

[Example] Registering SNMPv3 agent

group

setsnmpvacm creategroup -u

XSCF>

user_name test_group

Restoring SMTP service settings

[Example] Setting port number 25 for

e-mail server

setsmtp -s port=25

XSCF>

Restoring e-mail notification settings [Example] Disabling e-mail report function

setemailreport -s enable=no

XSCF>

g the time difference

yyyyyyyy user_name

-e

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201562

Page 77

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140407-003

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx xIf [Ctrl] + [t] is pressed in response to the

prompt that appears after starting OpenBoot PROM, the following trap related error message is output on the domain console of the logical domain.

There is no effective workaround. [How to restore] From the ok prompt, execute the reset-all command to restart OpenBoot PROM. {0} ok

reset-all

{0} ok ERROR: Last Trap: Fast Instruction Access MMU Miss TL: 1 %TL:1 %TT:64 %TPC:1056e6f20 %TnPC:1056e6f24 %TSTATE:4420001600 %CWP:0 %PSTATE:16 AG:0 PEF:1 RED:0 MM:0 TLE:0 CLE:0 MG:0 IG:0

IE:1 PRIV:1 AM:0

%ASI:20 %CCR:44 XCC:nZvc ICC:nZvc %TL:2 %TT:183 %TPC:f0248e68 %TnPC:f0200c80 %TSTATE:14420001400 %CWP:0 %PSTATE:14 AG:0 IE:0 PRIV:1 AM:0 PEF:1 RED:0 MM:0 TLE:0 CLE:0 MG:0 IG:0 %ASI:20 %CCR:44 XCC:nZvc ICC:nZvc

--- Omitted --?? Called from (f0227228) at f0227240 0 (emit Called from (lf at f020c3c8 (lf Called from lf

f020c404 lf Called from crlf at f020c424 pop-base Called from (f0225fe0) at f0226024 pop-base Called from (f0225fe0) at f0226024 (f0225fe0) Called from (f0248350) at f024838c 7fffffffffffff98 80000000fecdaff8 (f02081dc) Called from (f0248350) at f024837c {0} ok

RTIF2-

140407-005

xxSuppose that the system is operated

continuously without replacing a CPU memory unit lower (CMUL) or CPU memory unit upper (CMUU) having a faulty DC-DC converter (DDC). In such case, even if an error occurs with the CPU mounted on the CMUL or CMUU

avin

the fault

DDC, CPU related

Immediately replace the CMUU or CMUL where the DDC failure has occurred.

Chapter 3　Information on Software 63

Page 78

Table 3-5

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

failures may not be detected, a physical partition (PPAR) may hang up.

d the

For a DDC failure, confirm whether any

the following error logs is registered. Msg: Critical low voltage error Or Msg: Critical high voltage error Or Msg: Power subsystem failure

RTIF2-

140407-006

RTIF2-

140407-008

RTIF2-

140409-001

RTIF2-

140409-002

xx x

xx x If you disconnect and then connect the

xFor a SPARC M10-4S chassis with the

XSCF stopped, or with the input power off (AC OFF), even if you execute the initbb -f command to forcibly disconnect the chassis from the system, the chassis remains assigned to the physical partition (PPAR). To check this phenomenon, execute the showboards(8) command to whether Assignment of the target SPARC

M10-4S chassis (PSB) remains "Assigned".

Pwr Conn Conf Test

--------

showboards -av

XSCF>

PSB R PPAR-ID(LSB) Assignment

---- - ------------ ----------- ---- ---- ---- -------

00-0

00(00)

Assigned

Passed Normal

01-0 * 00(01)

Unmount Normal

Fault

Assigned

confirm

y y

n n

xIf the poweroff(8) command is executed

and the master chassis XSCF is reset during the time that it takes for a prompt

to be

returned, the following power on/power off operation cannot be executed.

An error may be detected in the Realtime

Clock (RTC) built into the SPARC M10 system and XSCF may not start.

USB memory while the executed snapshot(8) command is collecting information into the memory, the hardware error below ma

detected.

There is no effective workaround.

[How to restore]

Perform the following on the disconnected

SPARC M10-4S chassis.

1. Execute the replacefru(8) command to replace the chassis.

2. Power on (AC ON) the replacement chassis.

- If

the READY LED of the XSCF or

XSCF unit is lit

Complete replacefru(8) command execution by following the maintenance menu.

Execute the initbb(8) command to disconnect the system.

- If

the READY LED of the XSCF or

XSCF unit is not lit

Remove the chassis and replace the XSCF unit or CPU memory unit lower (CMUL) where a failure is suspected.

There is no effective workaround. If this phenomenon occurs, turn off the input power to all chassis and

it on

again.

There is no effective workaround.

[How to restore] Turn off the input power to the system and then turn it on again (AC OFF/ON).

Do not connect and then disconnect the USB memory while information is being collected into the memory by the snapshot(8) command.

[How to restore]

chassis from the

then turn

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201564

Page 79

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140409-003

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

Msg: DMA timeout error Hard detected At this time, the logical domain is continuously operated but the functions that access hardware (e.g., power on/off, monitoring function) no longer operate.

xx xAn error log due to hardware is

erroneously registered in the following cases.

Tur and then turn it on again (AC OFF/ON).

There is no effective workaround. Read the "Alarm" status as "Notice".

off t

- A watchdog timeout occurs due to a software factor

- XSCF RESET switch is pressed

- XSCF panic occurs due to firmware

[Example]

- Incorrect

Status: Alarm FRU: /FIRMWARE,/MBU Msg: SCF panic detected

- Correct

Status: Notice FRU: /FIRMWARE,/MBU

detected

During execution of the restoreconfig(8) command, do not power on or off the physical partition (PPAR) or execute diagnosis of the [How to restore]

RTIF2-

140410-002

Msg: SCF panic

xx x If, during execution of the restoreconfig

(8) command, you power on or off the physical partition (PPAR) or execute diagnosis of the system board, the operations in progress are interrupted.

- If the PPAR power on process is interrupted

Execute the poweron -f command to forcibly power off the PPAR.

- If the PPAR power off process or system board diagnosis is interrupted

Turn off the input power to all SPARC M10 system chassis or crossbar box chassis, and then turn it on again (AC-OFF/ON).

RTIF2-

140410-003

xWith the system input power off, if the

CPU memory unit lower (CMUL) is replaced or if the SPARC M10-4S is added without using the maintenance menu, the following error log may be registered as a result of automatic synchronization of XCP firmware versions.

There is no effective workaround. Ignore this error log.

Alarm: :SCF:Gaps between XBBOX-ID Or Alarm: :SCF:Gaps between BB-ID

e input power to the system

system board.

Chapter 3　Information on Software 65

Page 80

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140410-005

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx xIf a hardware error is detected

immediately after powering off or restarting the physical partition (PPAR), the PPAR power off or restart process may be stopped, and may not be completed. To check whether this phenomenon has occurred, power off or restart the PPAR and then execute the showpparprogress (8) command. If power on state and the power off process has not completed after at least one minute has passed, this phenomenon has occurred.

the PPAR remains in the

There is no effective workaround.

[How to restore] If the PPAR power supply remains in the power-on state 30 minutes executing the showpparprogress(8) command, turn off the input power to all chassis and then turn it on again

(AC-OFF/ON).

[Example of unsuccessful power off]

showpparprogress -p 0

XSCF> This PPAR is powered on. Normally, when the PPAR power off completes, the power off sequence PPAR state are as follows.

and

[Example of successful power off]

showpparprogress -p 0

XSCF> PPAR Power Off CPU Stop PSU Off

PPAR#0 [1/3]

PPAR#0 [2/3]

PPAR#0 [3/3] The sequence of power control is completed.

RTIF2-

140410-008

RTIF2-

140410-009

RTIF2-

140507-003

x Even if the XSCF DUAL control cable is

reconnected after the system input power has been turned on with this cable disconnected, data synchronization between the master chassis and standby chassis cannot be secured. Continuous system operation is possible. However, after switching the master and standby XSCFs, normal system operation is guaranteed. This is because information

the old master XSCF is not reflected in

the new XSCF.

If the input power to the standby or slave

chassis is turned off, a "Board control error (MBC link error)" error log may be registered.

After adding or removing a system board

with the dynamic reconfiguration of physical partitions (PPAR), if the PPAR is

owered off, the output of the

not

Before turning on the input power, confirm that the XSCF DUAL control cable is correctly inserted.

[How to restore] Execute the rebootxscf -a command to reset all XSCFs.

There is no effective workaround. Ignore this error log.

There is no effective workaround.

[How to Restore] After the "PPAR-ID x: Reset" message is

output to the event log, re-execute the

after

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201566

Page 81

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140507-004

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

owpparprogress(8) command

s mistakenly shows the status of the procedure of powering on the system.

xx xIn a system which implements daylight

saving time, if the current time is changed with the "setdate -s" command

to a

time that is within one hour of the

ending of daylight saving time, the time

changed to a time beyond daylight

saving time.

owpparprogress(8) command for the

s right display.

To set up the local time to something around the daylight saving time, use the "setdate -u" command and set the time in UTC.

[Example] If the ending of daylight saving October 31 AM 2:00 and the local time being attempted to set to October 31 AM 1:40 (JDT), the time is set to the standard local time of October 31 AM 1:47 (JST).

showdate

XSCF>

time be

Wed Apr 30 10:16:57 JDT 2014

setdate -y -s 103101402014.00

XSCF> Fri Oct 31 01:40:00

JST 2014

The XSCF will be reset. Continue? [y|n]

: Thu Oct 30 16:40:00 UTC 2014

showdate

XSCF> Fri Oct 31 01:47:16 JST 2014

RTIF2-

140507-005

RTIF2-

140507-006

RTIF2-

140507-007

xx xIf a failure is detected in DC-DC

converter (DDC), the "Power subsystem failure" error log may be registered twice.

xx xWhen error logs (Critical ultrahigh

temperature at XXX) at the time of abnormality of components due to high temperature (ultrahigh temperature level) are registered and the system is forcibly stopped, if the "showlogs power" command is executed, the "Cause" column of power log may show "-".

After a DC-DC converter (DDC) fault has

been detected, if the system is run continuously without replacing the FRU that appears in the error logs, the following error is mistakenly detected at every turning off of input power.

There is no effective workaround. Ignore the 2nd error log. Moreover,

replace the faulty FRU as soon as possible.

There is no effective workaround.

Replace the faulty FRU. Moreover, as this error message has no effect on the functioning of the

Msg: Power-off failure

RTIF2-

140507-008

xThe testsb(8) command detects the

"STICK Stop Register error (does not stop)" or the "STICK does not stop (CPU)" error messa

e and ma

fail.

There is no effective workaround. [How to Restore] Collect diagnosis information by executi

system, ignore it.

e snapshot(8) command.

Chapter 3　Information on Software 67

Page 82

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140507-009

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

After t

off/on the input power (AC OFF/ON) of all the chassis and then contact the

maintenance staff.

xx x

Even when rotation abnormality is found

both fans at the same time in the same

fan unit, error log for only one fan is registered and thus the system is not shutdown. As a result, temperature of components like CPU may rise.

There is no effective workaround.

[How to Restore] If the system is not shut down when fan rotation abnormality is detected, if any of

following symptom is confirmed in

the the two fans which comprises the faulty

fan unit, change the following fan unit as soon as possible:

e collectio

- The "showenvironment fan" command shows that the number of rotation has been decreased.

- Visual judgment reveals that the number of rotation has been stopped.

a system with three or more BBs or

RTIF2140507010

RTIF2-

140507-011

xx xIf cold replacement of CPU memory unit

xIn

with cross boxes, if the master/standby switchover if executed for more than 256 times, the "SCF process down detected" error is detected on the slave XSCF and XSCF "coremgrd" may cause process down.

lower (CMUL) or a motherboard unit (MBU) is done in the following procedure, the physical partitions (PPAR) may not start.

1. Execute the "restoredefaults -c factory" command.

2. After XSCF has stopped, turn off the input power of the system (AC OFF).

3. Replace the replacing the microSD card.

CMUL or MBU without

4. Turn on the input power of the system.

Do not perform consecutive XSCF master/standby switchover. [How to Restore]

the XSCF.

Reset The system will become usable.

Replace CMUL or MBU in the following procedure.

1. Execute the "restoredefaults -c factory" command.

2. To stop XSCF as in procedure 1, turn off/on the input power of the system (AC OFF/ON) and then confirm XSCF has started.

3. Replace the targeted CMUL or MBU.

[How to Restore]

Restore with the following procedure:

1. Turn off the input power of the system (AC OFF).

2. Temporarily mount the microSD card that was mounted on the CMUL or MBU, when the "restoredefaults -c factory" command was executed, to new unit.

3. Confirm that XSCF has started after turning on the input power (AC ON).

4. Turn off the input power of the system (AC OFF).

5. Extract the microSD card that was

oraril

tem

complete, turn

ted and mount the

mou

that

the

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201568

Page 83

Table 3-5

phy

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

origi

al microSD card.

6. Turn on the input power of the system (AC ON).

RTIF2-

140507-012

RTIF2-

140507-014

RTIF2-

140507-016

RTIF2-

140507-021

xIn a system with several SPARC M10-4S,

if a

crossbar box or the XSCF unit of a crossbar box is replaced after powering off all chassis and then the input power is turned on, the following error log may be registered. Indispensable parts are not installed (OPNL). Indispensable parts are not installed (FAN). Indispensable parts are not installed (PSU).

xWhen replacefru(8), addfru(8) or,

rebootxscf(8) command is executed, the "XSCF hang-up is detected" error message may be detected at the slave XSCF.

After configuring the XSCF network with

the setnetwork(8) command and applying the configuration by the applynetwork(8) command, if the shownetwork(8) command is executed without executing the rebootxscf(8) command, the displayed IP address may not match the IP address that is being used on the present system.

In the middle of performing diagnosis by

the "-p" and "-b" options of the diagxbu(8) command, if a failure occurs

the physical partition specified by the "-p" option, the diagxbu(8) command may terminate abnormally and powering off the SPARC M10 chassis, specified by the "-b" option may fail.

When replacing a crossbar box, do so after turning off the input power (AC OFF) of the target crossbar box only. When replacing the XSCF unit of a crossbar box, execute the replacefru(8) command to do so. Refer to Fujitsu M10-4/Fujitsu M10-4S/

SPARC M10-4/SPARC M10-4S Service Manual for replacing the crossbar box or

the XSCF unit in the crossbar box. [How to Restore] Turn off/on the input power (AC OFF/ON) of the replaced crossbar box.

There is no effective workaround. Ignore this error log as the command in question is terminated properly and thus

has no effect on the system.

After executing the applynetwork(8)

command to apply network configurations

the XSCF, execute the rebootxscf(8)

command to reset the XSCF.

There is no effective workaround. [How to Restore] Perform the

1. Turn off the input power (AC OFF) of SPARC M10 chassis using the "-b" option of the diagxbu(8) command.

2. Select the SPARC M10 chassis by the "-b" option of the replacefru(8) command.

3. When the message for the replacement

SPARC M10 chassis is output in the maintenance power (AC ON) of the SPARC M10 chassis without replacing it.

RTIF2-

140507-022

xWhen the crossbar cable of the crossbar

unit (XBU) in SPARC M10-4S is in bad electrical contact, the crossbar cable

onents are depicted wit

com

umber

There is no effective workaround. [How to Restore] Perform the following procedures:

1. Power off t

following procedure:

menu, turn on the input

sical

artition

Chapter 3　Information on Software 69

Page 84

Table 3-5

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

"#"s as t

e result of the showhardconf (8) command. [Example] When the crossbar cable is loose: + FRU-Part-Number:################; Ver:####h; + Type:#######; Length: #;

(PPAR) by t

2. Check the physical state of the crossbar cable (loose connection, disconnection etc.) who component information is depicted by a number of "#"s.

3. Execute the poweron(8) command to power on the PPAR.

4. Check the component information of the target crossbar cable with the showhardconf(8) command.

[Example] When the properly connected: + FRU-Part-Number:2123628-2 ; Ver:3920h; + Type:Optic; Length: 2;

RTIF2-

140602-001

x x x When the input power of a PCI

expansion unit is turned off (AC OFF), an error log is registered but, notification through SNMP trap or REMCS is not performed. Confirmation that the input power of a PCI expansion unit had been turned off can be seen in the output of

"showlogs error" command, like the

the following:

There is no effective workaround.

Date: May 29 20:03:05 JST 2014

Code: 10000400-00d4000000ff0000ff-

1100002a0000000000000000

Status: Information

Occurred: May 29 20:03:00.905 JST 2014

FRU: /BB#0/PCI#8/PCIBOX#2003/

PSU#0

Msg: AC FAIL Diagnostic Code:

RTIF2-

140605-001

00000000

Suppose the following scenario: You turn

(PPAR) that consists of multiple SPARC M10-4S chassis. The status of the PPAR/domain is between self diagnosis test (POST) completion (Initialization Complete) and OpenBoot PROM start com

00083230 30330000 0000 00080000 00000000 0000 00080000 00000000 0000 00000000 00000000 00000000

00000000 00000000 0000

the power to a physical partition

letio

enBoot Runni

). If the

There is no effective workaround.

[How to restore]

Perform one of the following operations:

- Execute the rebootxscf -a command.

- From XSCF Web, reset all XSCFs.

- Turn off the power to the PPAR, and then turn it on again.

e poweroff(8) command.

crossbar cable is

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201570

Page 85

Table 3-5

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

XSCF in a SPARC M10-4S i resets in this status, you may be unable to switch to the control domain console.

e PPAR

You can confirm that this event has occurred by executing the showlogs event command and confirming that an event log for console path switching was registered during the time between POST diagnosis completion and PROM start completion.

OpenBoot

[Example] Event log message issued when PPAR_ID is 0 POST Diag complete from PPAR (PPAR

--- Omitted --PPAR ID 0: Console path is switched

--- Omitted --PPARID 0 GID 00000000 state change (OpenBoot Running)

RTIF2-

140605-002

x Suppose that all but one of the system

boards (PSBs) that make up a physical partition (PPAR) are faulty. If you attempt to use the DR function to disconnect the normal PSB by executing the deleteboard(8) command, this command times out and terminates abnormally. In addition, if you execute the deleteboard(8)

function after then in an attempt to disconnect another PSB in the same PPAR, the command always times out. Furthermore, you can no longer connect

the control domain console by

executing the console(8) command.

command using the

[Example] deleteboard(8) command timeout

deleteboard -c disconnect 00-0

XSCF> PSB#00-0 will be unconfigured PPAR immediately. Continue?[y|n] :

from

If all but one of the PSBs are faulty, first turn off the power to the PPAR, and then execute the deleteboard(8) command to disconnect the normal PSB.

to restore]

[How Execute the following procedure:

1. Execute the rebootxscf -a command to reset the XSCF.

2. Check the error logs and messages to identify the cause of the error.

3. Eliminate the cause of the error.

4. Perform the operation described in "6.3.1 Example operation for unassigning a system board" or "6.3.3 Example operation for reserving the unassignment of a system board" in the

Fujitsu M10/SPARC M10 Systems Domain Configuration Guide.

All domains are temporarily suspended, proceed?[y|n] :

Start unconfigure preparation of PSB. [1200sec]

0..... 30..... 60..... 90.....120.....150.....180.....

210.....240.....\

270.....300.....330.....360.....390.....420.....450

.....480.....510.....\

Chapter 3　Information on Software 71

Page 86

Table 3-5

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

540.....570.....600.....630.....660.....690.....720

.....750.....780.....\

810.....840.....870.....900.....930.....960.....990

.....1020.....1050.....-

1080.....1110.....1140.....1170.....end

Timeout detected during unconfiguration

PSB#00-0.

XSCF>

RTIF2-

140605-006

x x x When the OS panics, a large volume of

panic messages may be sent to the XSCF.

this case, the XSCF cannot handle the large volume of panic messages. As a result, the codd process fails and OS-panic error logs are registered in large quantities as shown below. [Example] OS panic error logs

showlogs error -v

XSCF>

and process failure

There is no effective workaround.

[How to restore] The system is restored when the XSCF is reset by codd process failure.

Date: Dec 20 14:44:26 JST 2013 Code: 40000000-00ffff0000ff0000ff01b900060000000000000000 Status: Warning Occurred: Dec 20 14:44:26.513 JST 2013 FRU: /UNSPECIFIED Msg: XSCF command: System status change (OS panic) (PPARID#00, path: 00) Diagnostic Code: 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000 Date:

Dec 20 15:00:01 JST 2013 Code: 20000000-00fcff00b0000000ff010400010000000000000000 Status: Notice Occurred: Dec 20 14:59:56.838 JST 2013 FRU: /FIRMWARE,/XBBOX#81/XSCFU Msg: SCF process down detected Diagnostic Code: 00000000 00000000 0000 51000000 00000000 0000 00000000 00000000 0000 636f6464 2e323537 382e627a 32000000 00000000 00000000 0000 You can check codd by confirming that the first four bytes on the fourth line the [Diagnostic Code:] have the value "636f6464".

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201572

Page 87

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140606-001

RTIF2-

140606-004

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

x x x Suppose that a cluster system is built to

fulfill the following condition: It is composed of multiple SPARC M10 Systems chassis each of which includes

10 or

more guest domains (10 or more

cluster nodes) running in one physical

partition (PPAR). Moreover, PRIMECLUSTER

software is installed on each of these guest domains. Alternatively, the cluster system is composed of multiple PPARs within the SPARC M10 Systems chassis.

you execute the poweroff -f command

one PPAR to forcibly turn off the power to that PPAR, the XSCF may slow down, panic, and

then reset.

x Suppose that you execute the addboard

(8) and reset por commands to add a system board (PSB) to a physical partition (PPAR) that fulfills both of the conditions below. You may see an error

message "No analytical target" repeatedly.

Also, Oracle Solaris running on this PPAR may hang up.

- The SPARC M10-4S (including a

crossbar box) has a building-block configuration.

- Power is supplied only to a PPAR

made up of one PSB.

Confirm that less than 10 cluster nodes are included in one PPAR that exists on

instance of SPARC M10-1, SPARC M10-4, or SPARC M10-4S. [How to restore] The system will be available as is because the poweroff(8) command continues being processed after the XSCF has panicked and reset.

To add a PSB to a PPAR that fulfills the conditions shown on the left, use one the following methods:

- Turn off the power to the PPAR, and

then execute the addboard(8) command to add a PSB.

- After executing the addboard(8)

command to add a PSB, turn off the power to the PPAR, turn it on again, and then rebuild the PPAR.

- Using the DR

addboard(8) command to add a PSB.

[How to restore]

- If the error message "No analytical

target" is not displayed

Execute the poweroff(8) command to turn off the power to the PPAR, and then execute the poweron(8) command

turn on the power to the PPAR.

error message "No analytical

- If the

target" is displayed

Execute the poweroff -f command to forcibly turn off the power to the PPAR and then execute the poweron(8) command to turn on the power to the PPAR.

RTIF2-

140606-008

x Suppose that you are attempting the

following: Adding a system board (PSB) with the addboard -c configure command using dynamic reconfiguration

physical partitions (PPARs) or disconnecting a PSB using the deleteboard -c unassign or deleteboard -c disconnect command. If a

If there is a standby XSCF that fulfills the condition shown on the left, execute the addboard(8) or deleteboard(8) command after the standby XSCF has restarted. Check whether the XSCF has restarted,

executing the showhardconf(8)

command to confirm that the [Status] of

e SPARC M10-4S chassis (BB#xx) that

function, execute the

Chapter 3　Information on Software 73

Page 88

Table 3-5

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

ditions below is fulfilled, switching

co between master and standby XSCFs occurs. If the restarting XSCF mentioned in the condition description is the standby XSCF, it becomes the master XSCF after the switching. However, the previous master XSCF is reset and deactivated. [Condition]

- In the case of addboard

The XSCF for the PSB to be added restarting.

The XSCF for one of the PSBs making

the PPAR to which the PSB is to be

added is restarting.

- In the case of deleteboard

The XSCF for one of the PSBs making

the PPAR from which the PSB is to

deleted is

restarting.

cludes the XSCF is "Normal".

[Example]

- The XSCF at BB#02 is running. XSCF> SPARC M10-4S;

--- Omitted --BB#02 Status:Normal; Role:Slave; Ver:2220h; Serial:1234567890;

- The XSCF at BB#02 is restarting. XSCF> SPARC M10-4S;

--- Omitted --BB#02 Status:Cannot communicate;

[How to restore] Even if switching between master and standby XSCFs occurs, you can continue

using the

(8) or deleteboard(8) command has been executed correctly.

showhardconf

If the previous master XSCF has stopped, execute the following procedure:

1. Execute the poweroff -a command to

turn off the power to all PPARs.

2. Turn off the input power to the SPARC

M10-4S chassis set on the master

standby XSCFs and then turn it on again.

3. Log in to the master XSCF and execute

the showhardconf(8) command to confirm that the [Status] of the SPARC M10-4S chassis for the standby XSCF is "Normal".

RTIF2-

140616-001

The showhardconf(8) command executed

on a

SPARC M10-1 does not display [Type] for the power supply unit (PSU). Either "Type: A" or "Type: B" should be displayed as the PSU type. The meaning

each value of "Type" is as follows:

- Type: A: PSU for SPARC64 X

- Type: B: PSU for SPARC64 X+

you execute the showhardconf(8)

When

command, it displays "FRU-Part-

Number:CAXXXXX-XXXX-X/xxxxxxx ;"

part of the PSU information. You can determine the PSU type by checking the value of "CAXXXXX-XXXX-X" in this information.

- If the value of CAXXXXX-XXXX-X is "CA01022-0750-M"

Type: A: PSU for SPARC64 X

- If the value of CAXXXXX-XXXX-X is "CA01022-0751-M"

Type: B: PSU for SPARC64 X+

If multiple PSU types are mounted

mixed, you can determine the PSU type

ecki

system because the addboard

and

e value of "XXXXXX" in

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201574

Page 89

Table 3-5

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

e error log "Code:80000000-

t XXXXXX0000ff0000ffxxxxxxxxxx000000 00000000" output by the showlogs error command.

- If the value of XXXXXX is "002400" Type: A: PSU for SPARC64 X

- If the value of XXXXXX is "002401" Type: B: PSU for SPARC64 X+

RTIF2-

140616-002

xx xWhen the procedure below is executed,

the error message "An internal error has occurred. Please contact your system administrator." is displayed at execution

the prtfru(8) command and the

command abnormally terminates.

After starting or resetting the XSCF, execute the prtfru(8) command before executing the snapshot(8) command. [How to restore] Execute the rebootxscf -a command to reset all XSCFs.

1. Turn on the input power and then execute the rebootxscf(8) or switchscf(8) command to start or reset the

XSCF.

2. Execute the snapshot(8) command.

3. Execute the prtfru(8) command.

RTIF2-

140616-004

xWhen you execute the switchscf(8)

command, XSCF master/standby switching may take time. As a result, the following error may occur:

There is no effective workaround. If the current master XSCF differs from what you intended, re-execute the switchscf(8) command.

Master switch synchronization timeout.

RTIF2-

140616-005

xIf you turn off the input power of the

master XSCF (AC OFF) and then turn it

again (AC ON) when the power to the physical partition (PPAR) is off, error handling may fail due to the temporary absence of the master XSCF. In addition, the PPAR may remain abnormal you may be unable to power on the PPAR again.

that

There is no effective workaround. [How to restore] Turn off the input power to all SPARC M10-4S chassis that make up the system and then turn it on again.

You can determine the occurrence of this phenomenon by executing the showboards(8) command. If the value of "Pwr Conn Conf" displayed as the master XSCF PSB status is "n y n," this phenomenon has occurred. [Example] If the master

showboards -a

XSCF>

XSCF is BB#00:

PSB PPAR-ID Assignment Pwr Conn Conf Test

Fault

--- ------- ----------- ---- ---- ---- ------- -------00-0 00(00) Assigned Passed Normal 01-0 01(00) Assigned Passed Normal

n y n

y y n

Chapter 3　Information on Software 75

Page 90

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

140804-002

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

xx xAlthough the showstatus(8) command is

executed when there are no faulty components, the message "No failures found in System Initialization." indicating that there is no faulty component does not appear.

There is no effective workaround. If no message appears, there are no faulty components. You can continue system

operation.

[Example]

showstatus

XSCF> XSCF>

RTIF2-

140808-002

RTIF2-

140808-003

x When the showhardconf(8) command is

executed after the input power is turned off and then on, information on the configuration of components installed on the system may not be recognized.

xx xAfter the occurrence of a component

failure, you may fail to power off the physical partition (PPAR). This phenomenon may occur when the following procedure is performed:

1. While the PPAR is being reactivated due to a component failure, the poweroff(8) command is executed without the -f option.

2. After the PPAR PPAR reactivation failure due to a component failure, the poweron(8) command is executed to power on the PPAR.

is powered off upon a

There is no effective workaround.

[How to restore] Execute the rebootxscf -a command to reset all XSCFs.

Do not execute the poweroff(8) command while the PPAR is being reactivated due

to a

component failure.

[How to Execute the shutdown command from

Oracle Solaris to power off the PPAR.

[Example]

shutdown -y -g0 -i5

3. The poweroff(8) command is executed without the -f option.

RTIF2-

140929-001

RTIF2-

140929-002

RTIF2-

141008-001

x x x "NOTICE: Unable to get TX queue state!"

displayed mistakenly if Oracle Solaris

started in the system configured with

Oracle Solaris kernel zones.

xx xThe setting of the power supply

interlocking function (RCIL) disappears

if a

microSD card, which is mounted on a mother board unit (MBU) or a CPU memory unit lower (CMUL), is replaced

the system with a single unit configuration of SPARC M10-1, SPARC M10-4 or SPARC M10-4S.

xx xThe setsnmp(8), setsnmpusm(8), or

setsnmpvacm(8) command may fail to reflect settings properly if the settings are

ed to valid immediatel

cha

after bei

There is no effective workaround. Ignore this message.

There is no

[How to restore]

See the Fujitsu M10/SPARC M10 Systems RCIL User Guide, and reconfigure RCIL.

Be sure to wait 30 seconds or more if the settings are changed to valid after being changed to invalid.

[How to restore]

restore]

effective workaround.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201576

Page 91

Table 3-5

han

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

ged to invalid.

c [Example] The command fails, and some

the settings (Enabled MIB Modules)

are not reflected properly:

setsnmp disable

XSCF>

setsnmp enable

XSCF> setsnmp: Agent enable failed

showsnmp

XSCF>

Execute t

of 30

After executing the command again, confirm the settings are reflected as expected executing the showsnmp(8), showsnmpusm(8), or showsnmpvacm(8) command.

seconds or more.

Agent Status: Enabled Agent Port: 161 System Location: System-Location System Contact: System-Contact

：

Status: Enabled Community String: public Enabled MIB Modules: None <-- not reflected XSCF> "SP

MIB" is displayed in "Enabled MIB Modules" when the settings are reflected properly.

RTIF2-

141031-002

RTIF2-

141111-001

xx xExpiration date for the self-authenticated

certificate used by the HTTPS service will arrive in 1 year, not in 10 years.

xx xOn SPARC M10-1/M10-4 or SPARC

M10-4S in a single-chassis configuration, the content of the scheduled operation setting for automatic power-on/poweroff is lost and automatic power-on/ power-off becomes disabled. It occurs even when the PSU backplane (PSUBP) and the microSD card, or the PSU backplane unit (PSUBPU) and the microSD card are same time as shown in the following procedure.

not replaced at the

1. Turn off the input power (AC OFF)

and replace PSUBP or PSUBPU.

2. Turn on the input power (AC ON) and

start XSCF.

3. Turn off the input power (AC OFF)

and replace the microSD card on the

board unit (MBU) or CPU

mother memor

unit lower (CMUL).

You can access to XSCF Web even though the certificate has expired. Use the same certificate, or create a certificate,

import a certificate with the sethttps(8)

command.

To take over the content of the scheduled operation setting from the replaced FRU, disable/enable the scheduled operation after the first FRU is replaced. Execute the following procedure.

1. Replace the first FRU. (step 1 in the Description)

2. Disable the scheduled operation.

setpowerschedule -a -c

XSCF>

control=disable

3. Enable

setpowerschedule -a -c

XSCF>

control=enable

4. Execute step 2 and the subsequent steps in the Description.

[How to restore]

- If the dumpconfig(8) command is used

save the XSCF setting information,

execute the restoreconfig(8) command

d restore the XSCF settin

e command again after a lapse

the scheduled operation again.

Chapter 3　Information on Software 77

Page 92

Table 3-5

RTI No. 1 4 4S Description Workaround

RTIF2-

141111-002

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

Note that this problem occurs eve microSD card is replaced first.

xx xIf any of the following events occur and

the XSCF is reset, an incorrect error log may be registered. In addition, the XSCF time after the error occurrence time may

initialized to January 1, 1970.

- XSCF panic

- watchdog timeout

- The RESET switch on the rear panel pressed

The following cases when incorrect error logs are registered and the error occurrence times are also initialized.

two examples show the

formation.

- If the XSCF setting information is not saved, execute the setpowerschedule(8) command and reset the scheduled operation.

There is no effective workaround. Do not press the RESET

urgent and required.

[How to restore] After turning off the power of the physical partition (PPAR), turn off and then turn on (AC OFF/ON) the input power of the system. By turning on the power again, the XSCF time is restored automatically.

[Example 1] Date: Jan 01 09:05:40 JST 1970 Code: 80002008-000e010000ff0000ff018b00010000000000000000 Status: Alarm Occurred: Jan 01 09:04:56.276 JST 1970 FRU: /MBU Msg: Hardware access error. Diagnostic Code: 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 00000000

00000000 00000000 00000000 00000000 00000000 0000 [Example 2] Date: Jan 01 09:05:51 JST 1970 Code: 10000000-000e010000ff0000ff010240020000000000000000 Status: Information Occurred: Jan 01 09:05:35.008 JST 1970 FRU: /MBU Msg: TWI access error Diagnostic Code: 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000

RTIF2-

141204-001

xx xIf the guest domain has been kept active

for a long time, powering off and then powering on a physical partition (PPAR) ma

cause the

uest domain time to

Immediately before powering off a physical partition or resetting it, execute the ldm add-spconfig from Oracle VM Server for SPARC, a

switch unless it

d store the latest

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201578

Page 93

Table 3-5

ntp

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

deviate. This phenomenon occurs under the following conditions.

- A guest domain is configured (*1), and

- a long period of time passes after the ldm add-spconfig command is executed from Oracle VM Server for SPARC (*2), and

- a physical partition power is turned on

reset *1 Time deviation does not control domain.

occur on the

guest domai

XSCF. [How to restore] If the guest domain time deviates, boot Oracle Solaris in single-user mode, and then synchronize the time. [Example] Setting of 18:30:00 on June 27, 2014

date 0627183014.00

*2 Time deviation comes to about 20 seconds per month.

RTIF2-

141208-001

x x x Suppose that the audit system is

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 error." or "SCF panic detected."

access

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

trail" is

Execute the setaudit -p count command

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

command. The audit log is erased. You can execute the setaudit command.

3. Execute the setaudit -p count

command to configure the audit system

delete new audit records when the audit trail has reached its full capacity. (Default)

[Example]

showaudit all

XSCF> Auditing: enabled Audit space used: 4194304 (bytes) Audit space free: 0 (bytes) Records dropped: 0

on full trail: suspend

Policy

--- Omitted ---

RTIF2-

141226-001

xIf time synchronization of the master

XSCF and the NTP server fails during master/standby XSCF switching, the XSCF time ma

deviate a

d the

There is no effective workaround. [How to restore] If ntpd is not active when the NTP client

setti

configuration information

restoredefaults xscf

XSCF or the NTP server settin

Chapter 3　Information on Software 79

Page 94

Table 3-5

nag

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

ot start. If ntpd is not active, a

may message "NTP is unavailable." is output

executing the showntp -l command.

abled, execute the rebootxscf(8)

command to reset XSCF.

Note that this problem does not occur if the NTP client setting of XSCF and the NTP server setting are disabled.

RTIF2-

150126-001

xx xIf XSCF is reset while the system is

operating with the power supply interlocking function enabled, the power

of an

external I/O device may be turned

off incorrectly.

Disable the power supply interlocking function by RCIL, and enable it again

every time after the power of the physical

partition (PPAR) is

This also applies when the power of the

PPAR is automatically turned on due to power failure, power recovery, auto power control system (APCS), RCIL, etc.

[Example]

setremotepwrmgmt -c disable

XSCF>

setremotepwrmgmt -c enable

XSCF>

Perform the following procedure when you cannot perform this workaround due to a system operation issue.

- When two or more SPARC M10 systems are registered to the power supply interlocking group

Do no

reset XSCF at the same time as XSCF resetting of other SPARC M10 system.

- When only a single SPARC M10 system

registered to the power supply interlocking group Perform either (1) (1) Disable only the power-off of the

power supply interlocking function.

Execute "setremotepwrmgmt -c disable" to disable the power supply interlocking.

Specify "0x01" for the Linkage value in the management file of the power supply interlocking.

[Example] 1,1,0x01, 00000000000000000000000000000011, 0x01,0x00,,,10.20.300.40,0x20,aa:bb:cc:dd: ee:f0,,,,,,,,,, 1,2,0x10, 00000000000000000000000000000022, 0x01,0x00,,,10.20.300.41,0x20,aa:bb:cc:dd: ee:f1,,,,,,,,,,

Execute "setremotepwrmgmt -c config [file name]" to apply ma

turned on.

or (2) below.

ement file.

the

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201580

Page 95

Table 3-5

phy

RTI No. 1 4 4S Description Workaround

RTIF2-

150129-001

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

(2) Disable the power supply

interlocking function.

2. If

x[1]

the input voltage drops, usually a power failure notification is issued and the power of the physical partition is turned off. However, if the input voltage of SPARC M10-1 drops instantaneously, no power failure notification is issued and the power of the physical partition is turned off.

you execute the console(8)

[2] If

command to switch to the control domain console and input texts or keys during the physical partition power-off due to the trouble in [1], the following error log may be detected and the mother board unit (MBU) may need to be replaced.

There is no effective workaround. If "MBC-CPU interface fatal error" is detected, replace the MBU. If "MBC-CPU interface fatal error" is not detected, turn off the input power supply and then turn it on again.

Execute "setremotepwrmgmt -c enable" to enable the power supply interlocking.

Execute "setremotepwrmgmt -c disable" to disable the power supply interlocking.

the external I/O device is ETERNUS, set the ETERNUS to LOCAL mode for operation.

MBC-CPU interface fatal error

Check all are satisfied to see if the trouble in [1] occurs.

the following five conditions

- Any of the following error logs is registered.

MBU:SCF:failed to read/write interrupt mask register

MBU:SCF:failed to read/write active status register

Voltage out of range error

- Oracle Solaris is not accessible via the network.

- No power failure notification is issued. (*1)

- The physical partition status display that you can check by the showpparstatus(8) command is not

dated and indicates the

sical

Chapter 3　Information on Software 81

Page 96

Table 3-5

RTI No. 1 4 4S Description Workaround

Problems that might occur with XCP 2240 and workarounds (continued)

SPARC M10-

partitio than "Powered Off").

- You can access XSCF, but the execution result of the showlogs power command does not include "SCF Reset" indicating that XSCF is reset.

*1: If a power failure notification is

In addition, the following error log is detected in many cases when the trouble

[1] occurs: failed to read/write extended active status register

active (the status is ot

issued, usually the following log is registered by the showlogs event command.

PSU input power failure(/PSU#0)

input power failure(/PSU#1)

PSU

Workaround for RTIF2-140304-007

If PSU is replaced by the replacefru(8) command, after mounting the new PSU, wait

for at least 30 seconds before pressing the [f] key of the menu of replacefru(8) command.

Doyouwanttocontinue?[r:replace|c:cancel]: Pleaseexecutethefollowingsteps:

1)RemovePSU#n.

2)Executeeitherthefollowing: 2-1)Afterinstallingtheexchangeddevice,pleaseselect'finish'.



2-2)Ifyouwanttosuspendthemaintenancewithoutexchangingdevice,





[f:finish|c:cancel]:

pleaseselect'cancel'.

[How to restore] If both PSUs become "Deconfigured" without performing workarounds, active replacement of the PSUs cannot be done with the replacefru(8) command.

Maintenance/ReplacementMenu PleaseselectaFRUtobereplaced. No.FRU

------------------------------------



------------------------------------------------------------------------------

Select[1,2|b:back]: [Warning:307] PSU#1cannotbereplaced.Pleaseverifytheconfiguration. Select[1,2|b:back]: [Warning:307]



/PSU#0 /PSU#1





Status

Deconfigured Deconfigured



Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201582

Page 97

PSU#1cannotbereplaced.

To restore, after removing the replaced PSUs without the replacefru(8) command, use the replacefru(8) command to replace the PSUs.

Problems resolved in XCP 2240

The following table lists the problems resolved in XCP 2240.

Table 3-6

RTINo. 1 4 4S Description Workaround

RTIF2-

130305-003

RTIF2-

140227-001

RTIF2-

140314-001

Problems resolved in XCP 2240

SPARC M10-

xx xIf you reconnect the input power cable

soon after it is unplugged, the error log

PSUs detect 100V and 200V at AC inputs indicating that an error in the configuration of the input power supply may be registered.

- XCP 2041 or later Wrong PSU is installed

- XCP 2032 or PSUs detect 100V and 200V at AC inputs

xWhen the cross-bar boxes are powered

(AC ON) for the first time, the "SCF panic detected" or the "XSCF hang up is detected" error log may be registered when XSCF is started.

xIn

case of a SPARC M10-1, to which XCP 2210 is applied, if an internal component failure occurs in Type B motherboard unit (MBU), it may not be detected and the following error may be registered in numbers.

- Voltage problem within MBU

FRU: /MBU Msg: Critical low voltage error

Or,

- Fan speed

FRU: /FAN#x, /MBU Msg: FAN speed too low

earlier

problem

There is no effective workaround. Ignore this error log.

There is no effective workaround. [How to restore]

1. Confirm that all crossbar boxes and SPARC M10-4S are displayed showhardconf(8) command.

2. Perform AC OFF/ON on all crossbar boxes and SPARC M10-4S.

3. Check the master XSCF with the showbbstatus(8) command. If XBBOX#81 had been switched to master XSCF, use the switchscf(8) command to make XBBOX#80 the master XSCF.

There is no effective workaround. [How to restore] Replace the MBU.

with the

Chapter 3　Information on Software 83

Page 98

Table 3-6

RTINo. 1 4 4S Description Workaround

RTIF2-

140507-013

RTIF2-

140515-001

Problems resolved in XCP 2240 (continued)

SPARC M10-

x x x Even if two default gateways are set up

using the setroute(8) command, connection from other networks is possible only on either XSCF-LAN#0 or XSCF-LAN#1.

xIn

order to configure the XSCF startup mode function, after changing the startup mode with the xscfstartupmode(8) command or setting the operation panel mode switch to "Locked" or "Service", if the rebootxscf(8) command is executed to reset XSCF, the new startup mode gets enabled. However, under normal circumstances, the configuration of startup mode is not enabled when XSCF

reset using the rebootxscf(8) command.

It is

enabled only when the input power

the system is turned off/on (AC OFF/ON).This state can be confirmed by the "xscfstartupmode -d" command, as follows:

the

Among XSCF-LAN#0 and XSCF-LAN#1,

use the IP address of the gateway that

can be connected to.

There is no effective workaround.

[Example] When startup mode is set to "fast" after setting mode switch to "Locked"

xscfstartupmode -d

XSCF>

the operation panel

Setting Mode: normal Current Mode: normal

xscfstartupmode -m fast

XSCF>

rebootxscf -a

XSCF>

xscfstartupmode -d

XSCF> Setting Mode: fast[need AC OFF/ON] Current Mode: fast However, the correct result will be that the "Current Mode" be "normal" like the following:

xscfstartupmode -d

XSCF> Setting Mode: fast [need

OFF/ON]

Current Mode: normal

RTIF2-

140523-001

xIn

the event of an instantaneous power failure lasting 11 ms or more, the CHECK LED on the operation panel will remain

after recovery, and the XSCF may not

start.

There is no

[How to restore]

After turning off the input power, wait

for at least 10 seconds before turning it

again. Therefore, even if the system is set to automatically start after recovery, it may not actually start automatically.

effective workaround.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201584

Page 99

Table 3-6

RTINo. 1 4 4S Description Workaround

RTIF2-

140616-003

RTIF2-

140710-001

Problems resolved in XCP 2240 (continued)

SPARC M10-

xx xIf microSD card in the XSCF or in the

XSCF unit is faulty, you may be unable to access the data in the restored XSCF. In this case, when you execute the setservicetag(8) command, it will abnormally terminate with the error message "An internal error has occurred.

Please contact your system administrator."

x x x After you replace a motherboard or CPU

memory unit lower (CMUL), the XCP firmware version should differ from the pre-replacement version. Nevertheless, the message "XCP version of XSCF and Back-Panel mismatched!" that should appear at the time of login to XSCF is not displayed.

There is no effective workaround. [How to restore]

Replace the motherboard unit (MBU), the

CPU memory unit lower (CMUL), or the XSCF unit (XSCFU).

There is no effective workaround. [How to restore] When replacing a component, execute the following procedure:

1. Before replacement, execute the version(8) command to check the XCP version.

[Example]

version -c xcp

XSCF> BB#00-XSCF#0 (Master) XCP0 (Current): 2051 XCP1 (Reserve): 2051

2. After replacement, execute the version(8) command to check the XCP version again.

3. If the XCP versions before and after replacement flashupdate(8) command to update the firmware.

[Example] Updating to XCP 2052

flashupdate -c update -m xcp -s

XSCF>

2052

not match, execute the

Chapter 3　Information on Software 85

Page 100

Table 3-6

RTINo. 1 4 4S Description Workaround

RTIF2-

140711-001

Problems resolved in XCP 2240 (continued)

SPARC M10-

xx xAfter Oracle Solaris has been kept active

for a long time, powering off and then powering on a physical partition (PPAR) may cause the Oracle Solaris time to deviate. This phenomenon occurs in one of the following cases:

There is

Note -

2232 or earlier to XCP 2040 or later for which this problem has been resolved, see the "RTIF2-140711-001 additional

information".

- The setting specifying the XSCF as an NTP client is enabled and the Solaris does not use the NTP server.

- The setting specifying the XSCF as an NTP client is enabled and Oracle Solaris uses the NTP server. At the time

Oracle Solaris booting, the ntpdate command is not executed or the ntpdate command fails to correct the time.

Oracle

[How to restore]

Execute the following procedure to boot

Oracle Solaris in single-user mode and

set the time.

1. Execute the power off the PPAR.

2. Execute the showpparstatus(8) command to confirm that the status is "Powered off" meaning that the PPAR

disconnected.

3. Set the environment variable

auto-boot? of OpenBoot PROM to "false."

setpparparam -p PPAR-ID -s

XSCF>

bootscript "setenv auto-boot? false"

4. Execute the poweron(8) command to power on the PPAR.

5. Execute the console(8) command to connect to the control domain console and display the ok prompt.

6. Boot Oracle Solaris in single-user mode.

boot -s

{0} ok

7. Execute the date command to set the Oracle Solaris time.

[Example] Setting of 18:30:00 on June 27,

2014

date 0627183014.00

no effective workaround.

update the firmware from XCP

poweroff(8) command to

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240

･

March 201586

Fujitsu M10, SPARC M10 Product Notes

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Preface

Audience

How to Use This Document

Related Documentation

Information on firmware

Disposal and recycling

Documentation Feedback

XCP/Oracle Solaris and Required SRU/Patch

Notes on using Oracle Solaris 10

Notes when using a version older than Oracle VM Server for SPARC 3.1.0.1

Required XCP/Oracle Solaris and required SRU/patch to enable dynamic reconfiguration of physical partition

Required XCP/Oracle Solaris and required SRU/patch to enable dynamic reconfiguration of PCIe endpoint device

Software supporting Software on Chip

How to Obtain XCP and Oracle Solaris SRU/Patch/Oracle VM Server for SPARC

Web Browser

Existing XCP Firmware Versions and Support Information

Latest Information on XCP 2240

Notes and Restrictions

Notes on Secure Socket Layer (SSL) 3.0

Restrictions on audit

Notes on dynamic reconfiguration of physical partitions

Notes on mixing SPARC64 X+ processors with SPARC64 X processors

Notes and restrictions on the SR-IOV functions

Notes on OpenBoot PROM

Notes on maintenance for CPU memory units, motherboard unit, XSCF unit, PSU backplane, or crossbar backplane unit

Notes on CPU Activation

Notes and restrictions on XSCF Web

Notes on firmware update

Notes on configurations with a PCI expansion unit connected

Notes on dual power feed setting

Notes on Active Directory

Notes on LDAP over SSL

Notes on the logical domain time

Notes on Timezones

Notes on power supply interlock function (RCIL)

Other notes and restrictions

XCP 2240 Problems and Workarounds

Notes and Restrictions

Notes on support for disks with an EFI (GPT) label

Notes on Oracle VM Server for SPARC

Notes on live migration of Oracle VM Server for SPARC

Notes on a case when recovery mode of Oracle VM Server for SPARC is enabled

Notes on a case where openssl is used

Notes on remote maintenance service

Notes on SNMP

Problems with XCP and Workarounds

Problems that might occur with XCP 2240 and workarounds

Problems resolved in XCP 2240