Fujitsu SPARC Enterprise M4000, SPARC Enterprise M5000 Product Notes

SPARC Enterprise

™

M4000/M5000 Servers

Product Notes

For XCP Version 1091

Manual Code C120-E611-04EN
Part No. 875-4633-13
April 2010, Revision A

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

Sun Microsystems, Inc. and Fujitsu Limited each own or control intellectual property rights relating to products and technology 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. The intellectual property rights of Sun Microsystems, Inc. and Fujitsu Limited in such products, technology and this
document include, without limitation, one or more of the United States patents listed at http://www.sun.com/patents and one or more
additional patents or patent applications in the United States or other countries.

This document and the product and technology to which it pertains are distributed under licenses restricting their use, copying, distribution,
and decompilation. No part of such product or technology, or of this document, may be reproduced in any form by any means without prior
written authorization of Fujitsu Limited and Sun Microsystems, Inc., and their applicable licensors, if any. The furnishing 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 Fujitsu Limited or Sun Microsystems, Inc., 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 suppliers to Fujitsu Limited and/or Sun Microsystems, Inc., including software and font technology.

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

This distribution may include materials developed by third parties.

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

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

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

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

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

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

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

Disclaimer: The only warranties granted by Fujitsu Limited, Sun Microsystems, Inc. or any affiliate of either of them in connection with this
document or any product or technology described herein are those expressly set forth in the license agreement pursuant to which the product
or technology is provided. EXCEPT AS EXPRESSLY SET FORTH IN SUCH AGREEMENT, FUJITSU LIMITED, SUN MICROSYSTEMS, INC.
AND THEIR AFFILIATES MAKE NO REPRESENTATIONS OR WARRANTIES OF ANY KIND (EXPRESS OR IMPLIED) REGARDING SUCH
PRODUCT OR TECHNOLOGY OR THIS DOCUMENT, WHICH ARE ALL PROVIDED AS IS, AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, 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 Fujitsu Limited, Sun Microsystems, Inc. or any of their affiliates have any liability to any
third party under any legal theory for any loss of revenues or profits, loss of use or data, or business interruptions, or for any indirect, special,
incidental or consequential damages, even if advised of the possibility of such damages.

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

Please

Recycle

Contents

Contents iii

Preface vii

Technical Support vii

Software Resources viii

Accessing Documentation viii

Fujitsu Welcomes Your Comments ix

General Information About XCP 1091 1

What’s New in XCP 1091 1

Active Directory and LDAP/SSL 2

Configuring XSCF for Active Directory Support 3

Configuring XSCF for LDAP/SSL Support 4

New proxyuser System Account 4

Supported Firmware and Software 4

Solaris Patch Information 5

Patches for Solaris 10 5/08 6

Patches for Solaris 10 8/07 6

Patches for Solaris 10 11/06 6

Patches for Emulex PCI Express (PCIe) Cards 7

iii

Updating to XCP 1091 7

Resetting the XSCF Firmware 7

Updating from a Version Earlier Than XCP 1050 7

Functionality Issues and Limitations 8

Limitations for SPARC64 VII Processors 8

Notes on Active Directory 8

Notes on LDAP/SSL 8

Notes on NTP Server 8

Notes on the NTP Server Referring to the Local Clock 9

Notes on XSCF Web 10

General Functionality Issues and Limitations 11

Information About Hardware 13

Notes on Server Installation 13

Notes on DVD Drives and Discs 13

Notes on the Use of USB Memory 14

Power Control and Operator Panel Mode Switch 14

Hardware Issues and Workarounds 15

Sun Crypto Accelerator 6000 Cards 15

Hardware Documentation Updates 15

Updates of the SPARC Enterprise M4000/M5000 Servers Installation Guide (-

05) 16

Initializing the XSCF Unit 16

Information About Software 18

XCP Issues and Workarounds 18

Known Issues and Workarounds in XCP 1091 18

XCP Issues Fixed in XCP 1091 20

XCP Issues Fixed in Releases Earlier Than XCP 1091 21

Solaris OS Issues and Workarounds 35

iv SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Solaris OS Issues for All Supported Releases 35

Solaris OS Issues Fixed in Solaris 10 10/09 39

Solaris OS Issues Fixed in Solaris 10 5/09 40

Solaris OS Issues Fixed in Solaris 10 10/08 41

Solaris OS Issues Fixed in Solaris 10 5/08 44

Solaris OS Issues Fixed in Solaris 10 8/07 48

Software Documentation Updates 53

Identifying Degraded Memory in a System 57

Identifying Different Memory Sizes in a System Board 57

Using the showdevices Command 57

Using the prtdiag Command 58

Identifying Permanent Memory in a Target Board 59

Contents v

vi SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Preface

These product notes contain late-breaking information about the SPARC
Enterprise™ M4000/M5000 servers hardware, software, or documentation that
became known after the documentation set was published.

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

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

Global Site

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

Japanese Site

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

North American Site

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

Technical Support

If you have technical questions or issues that are not addressed in the SPARC
Enterprise M4000/M5000 servers documentation, contact a sales representative or a
certified service engineer.

vii

Software Resources

The Solaris™ Operating System and Sun Java™ Enterprise System software are
preinstalled on your SPARC Enterprise M4000/M5000 servers.

Contact a sales representative or a certified service engineer for software resources
for your SPARC Enterprise M4000/M5000 servers.

Note – For latest patch information go to:

Global Site

http://www.fujitsu.com/global/support/software/security/products

-s/patch-info/

Japanese Site

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

North American Site

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

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

Accessing Documentation

Note – Information in these product notes supersedes the information in the SPARC

Enterprise M4000/M5000 servers documentation set.

Instructions for installing, administering, and using your SPARC Enterprise
M4000/M5000 servers are provided in the SPARC Enterprise M4000/M5000 servers
documentation set.
The documentation set is available for download from the following website:

Global Site

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

Japanese Site

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

North American Site

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

viii SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1090 • April 2010

Sun Microsystems Software (for Solaris OS, etc.) Related Manuals

http://docs.sun.com/

Fujitsu Welcomes Your Comments

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

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

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

For Users in Other Countries:
SPARC Enterprise contact

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

Preface ix

x SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1090 • April 2010

General Information About XCP 1091

This section describes the general information about XCP 1091.

■ “What’s New in XCP 1091” on page 1

■ “Supported Firmware and Software” on page 4

■ “Updating to XCP 1091” on page 7

■ “Functionality Issues and Limitations” on page 8

What’s New in XCP 1091

In XCP version 1091, the following new feature is introduced:

■ The XCP 1091 firmware introduces the Active Directory and LDAP/SSL features.

See “Active Directory and LDAP/SSL” on page 2.

■ The following new XSCF commands are supported:

■ setad(8)

■ showad(8)

■ setldapssl(8)

■ showldapssl(8)

For detail, see the manual pages for each command.

1

Active Directory and LDAP/SSL

The XCP 1091 release introduces support for the Active Directory®1 and LDAP/SSL
features.

■ Active Directory is a distributed directory service from Microsoft

®1

Corporation.

Like an LDAP directory service, it is used to authenticate users.

■ LDAP/SSL offers enhanced security to LDAP users by way of Secure Socket

Layer (SSL) technology. It uses LDAP directory service to authenticate users.

Note – For security reasons, XSCF uses only LDAP over SSL protocol (LDAPS) to

communicate with an Active Directory server or an LDAP/SSL server.

Active Directory and LDAP/SSL each provides both authentication of user
credentials and authorization of the user access level to networked resources. They
use authentication to verify the identity of users before they can access system
resources, and to grant specific access privileges to users in order to control their
rights to access networked resources.

User privileges are either configured on XSCF or learned from a server based on
each user's group membership in a network domain. A user can belong to more than
one group. User domain is the authentication domain used to authenticate a user.
Active Directory authenticates users in the order in which the users' domains are
configured.

Once authenticated, user privileges can be determined in the following ways:

■ In the simplest case, user’s privileges are determined directly through the Active

Directory or LDAP/SSL configuration on the XSCF. There is a defaultrole
parameter for both Active Directory and LDAP/SSL. If this parameter is
configured or set, all users authenticated via Active Directory or LDAP/SSL are
assigned privileges set in this parameter. Setting up users in an Active Directory
or LDAP/SSL server requires only a password with no regard to group
membership.

■ If the defaultrole parameter is not configured or set, user privileges are learned

from the Active Directory or LDAP/SSL server based on the user’s group
membership. On XSCF, the group parameter must be configured with the
corresponding group name from the Active Directory or LDAP/SSL server. Each
group has privileges associated with it which are configured on the XSCF. A
user’s group membership is used to determine the user’s privileges once
authenticated.

Three types of groups can be configured: administrator, operator, and custom. To
configure an administrator or operator group, only group name is required.

1. Microsoft and Active Directory are either registered trademarks or trademarks of Microsoft Corporation in
the United States and/or other countries.

2 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

An administrator group has platadm, useradm, and auditadm privileges
associated with it. An operator group has platop, and auditop privileges
associated with it. To configure a custom group, both group name and privileges are
required. For each type of group, up to five groups can be configured. A user
assigned to more than one group receives the sum of all privileges associated with
those groups.

To support these new features, two new configuration screens (Active Directory
and LDAP over SSL) have been added to the Settings menu of the XSCF Web.
Remote users can log in and use the XCSF Web once they have been authenticated
by Active Directory or LDAP/SSL.

Configuring XSCF for Active Directory Support

The commands setad(8) and showad(8) let you set and view the Active Directory
configuration from the command line.

By default, Active Directory support is disabled. To enable Active Directory support,
use the following command:

XSCF> setad enable

To disable Active Directory support, use the following command:

XSCF> setad disable

To show if Active Directory support is enabled or disabled, enter:

XSCF> showad

Use the setad(8) command with its various parameters to configure Active
Directory. For example, you can use it to set up one primary and five alternate
Active Directory servers, assign group names and privileges, configure a particular
user domain, control logging of diagnostic messages, and more. User domain can be
configured explicitly through the setad userdomain command on XSCF, or
entered at login prompt using the form, user@domain.

See the setad(8) and showad(8) man pages, and the note about these commands in

TABLE 13.

General Information About XCP 1091 3

Configuring XSCF for LDAP/SSL Support

The commands setldapssl(8) and showldapssl(8) let you set and view
LDAP/SSL configuration from the command line. These commands do for
LDAP/SSL what the setad(8) and showad(8) commands do for Active Directory,
and support many of the same parameters.

For more information, see the setldapssl(8) and showldapssl(8) man pages.

New proxyuser System Account

To support Active Directory and LDAP/SSL, this release features a new system
account named proxyuser. Verify that no user account of that name already exists.
If one does, use the deleteuser(8) command to remove it, then reset XSCF before
using the Active Directory or LDAP/SSL feature.

Supported Firmware and Software

The following firmware and operating system (OS) are supported depending on the
processors being installed on the SPARC Enterprise™ M4000/M5000 servers.

TABLE 1 Supported Firmware and Operating System Versions

Installed Processors XCP Version Operating System Version

SPARC64 VI processors XCP 1040 or later Solaris 10 11/06 or later, with required

patches

SPARC64 VII processors

2.4GHz XCP 1071 or later Solaris 10 8/07 or later, with required
patches

2.53GHz XCP 1090 or later Solaris 10 8/07 or later, with required
patches

Note – 8GB DIMM is supported in XCP 1081 or later.

4 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

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

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

You can download the latest files of firmware at the following websites.

Global Site:

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

Japanese Site:

http://primeserver.fujitsu.com/sparcenterprise/download/firmware/

Many web browsers support the XSCF Web. The browsers in

TABLE 2 have

demonstrated compatibility with the XSCF Web through testing. For other
information about XSCF Web, see “Notes on XSCF Web” on page 10.

TABLE 2 Tested Web Browser Versions

Web Browser Application Version

Microsoft® Internet Explorer

Firefox (Solaris 10) 2.0

* Microsoft and Internet Explorer are either registered trademarks or trademarks of Microsoft Corporation in the

United States and/or other countries.

† The Firefox 3 is not supported in XSCF Web.

®*

6.0, 7.0, or 8.0

†

Solaris Patch Information

This section lists mandatory patches for the SPARC Enterprise M4000/M5000
servers.

For additional Solaris Operating System information, see “Solaris OS Issues and

Workarounds” on page 35.

Note – See “Software Resources” on page viii for information on how to find the

latest patches. Installation information and README files are included in the patch
download.

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

upgrade including the patches, see SPARC Enterprise M4000/M5000 Servers Service
Manual.

General Information About XCP 1091 5

Patches are not required for servers running Solaris 10 10/08 OS or later.

Patches for Solaris 10 5/08

The following patch is required for Solaris 10 5/08 OS only on servers containing
SPARC64 VI processors or SPARC64 VII 2.4GHz processors:

■ 137137-09

For Solaris 10 5/08 OS on servers containing SPARC64 VII 2.53GHz processors,
apply all patches contained in the PTF R10021 or later. For more information on the
PTF, contact a sales representative or a qualified service engineer.

Patches for Solaris 10 8/07

The following patches are required for Solaris 10 8/07 OS only on servers containing
SPARC64 VII 2.4GHz processors:

■ 119254-51 or later

■ 125891-01 or later

■ 127755-01 or later

■ 127127-11

For Solaris 10 8/07 OS on servers containing SPARC64 VII 2.53GHz processors,
apply all patches contained in the PTF R10021 or later. For more information on the
PTF, contact a sales representative or a qualified service engineer.

Patches for Solaris 10 11/06

The following patches are required for Solaris 10 11/06 OS. Note that Solaris 10
11/06 does not support SPARC64 VII processors, even with these required patches:

■ 118833-36 (Install 118833-36 before 125100-04.)

■ 125100-04 or later

■ 120068-03 or later

■ 123839-07 or later

■ 125424-01 or later

■ 125075-01 or later

■ 125670-02 or later

6 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Patches for Emulex PCI Express (PCIe) Cards

The following Emulex cards require drivers supplied in patch 120222-26:

■ XSEFC402AF Sun StorageTek Enterprise Class 4Gb Dual-Port Fibre Channel PCI-

E HBA

■ XSEFC401AF Sun StorageTek Enterprise Class 4Gb Single-Port Fibre Channel PCI-

E HBA

Updating to XCP 1091

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

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

Resetting the XSCF Firmware

After updating the XCP firmware to 1091, do not fail to reset the XSCF by using the
rebootxscf(8) command.

Updating from a Version Earlier Than XCP 1050

■ You cannot update to XCP 1091 directly.

If you are currently running a version earlier than XCP 1050, you must first
update to an interim version of XCP between 1050 and 1070 (inclusive) before
updating to XCP 1091. Refer to the product notes document for the interim
version for instructions.

■ Delete any accounts named "admin".

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

General Information About XCP 1091 7

Functionality Issues and Limitations

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

Limitations for SPARC64 VII Processors

Caution – You must complete the upgrades to the XCP firmware and to Solaris OS

before inserting SPARC 64 VII processors into the chassis.

Notes on Active Directory

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

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

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

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

Notes on LDAP/SSL

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

Notes on NTP Server

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

attention to the following points:

■ XSCF must be connected to an external NTP server

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

same NTP server as XSCF is using

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

8 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Notes on the NTP Server Referring to the Local Clock

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

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

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

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

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

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

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

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

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

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

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

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

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

General Information About XCP 1091 9

● Change the stratum value of the NTP server

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

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

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

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

Notes on XSCF Web

■ Under the Windows 7

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

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

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

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

■ To use XSCF Web on the SPARC Enterprise M4000/M5000 servers which are

installed the XCP 1080, disable the cache function of your browser. If you leave
the browser cache function enabled, the old cached data might be displayed. To
disable the cache funtion:

■ Internet Explorer 6 and 7

[Tools] -> [Internet Options...] -> [Advanced] tab and check the "Do not save
encrypted pages to disk" box.

■ Netscape 7.1 or later

[Edit] -> [Preferences] -> [Advanced] -> [Cache] -> [Compare the page in the
cache to the page on the network] setting and select the "Every time I view the
page" radio button.

2

and Internet Explorer 8.0 environment, XSCF Web does

2. Windows is either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.

10 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

■ Firefox 2

Type "about:config" in address box, then type "cache" in filter box. Change
the "browser.cache.check_doc_frequency" settings value to "1."

■ Using the XSCF Web, when you import XCP or update the firmware, Session ID

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

■ When you use the XSCF Web, if a plug-in such as the search tool installed with

the browser, remove the plug-in or disable the pop-up blocking.

General Functionality Issues and Limitations

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

Issues and Workarounds” on page 35.

■ The following functions displaying the power consumption and exhaust air are

not supproted on M4000/M5000 servers.

■ power and air operands of the shownevironment(8) command

■ XSCF Web.

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

SNMP Agent Function obtains invalid values of power consumption and exhaust air.

■ SPARC Enterprise M4000/M5000 servers are cold service machines. Hot-

swapping of the CPU module (CPUM), memory board (MEMB), I/O unit (IOU),
or XSCF unit is not supported.

■ For this XCP release, the XSCF browser user interface (XSCF Web) does not

support the External I/O Expansion Unit Manager feature.

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

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

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

controller, the following notification signals are not supported:

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

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

(*ALARM)

■ For 1027A-Z/X1027A-Z, PCIe Dual 10 Gigabit Ethernet Fiber XFP cards, these

limits apply:

■ Do not use more than two cards per domain.

General Information About XCP 1091 11

■ Do not use these cards in an External I/O Expansion Unit.

■ For 4447A-Z/X4447A-Z, PCIe Quad-port Gigabit Ethernet Adapter UTP cards,

these maximum limits apply:

■ No more than four cards in an External I/O Expansion Unit (two per PCIe I/O

boat).

■ No more than four cards in a SPARC Enterprise M4000 server domain.

■ No more than eight cards in a SPARC Enterprise M5000 server domain.

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

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

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

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

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

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

■ At this time the restoredefaults(8) command is not supported.

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

supported.

12 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Information About Hardware

This section describes the special instructions and the issues about the SPARC
Enterprise M4000/M5000 servers hardware.

■ “Notes on Server Installation” on page 13

■ “Notes on DVD Drives and Discs” on page 13

■ “Notes on the Use of USB Memory” on page 14

■ “Power Control and Operator Panel Mode Switch” on page 14

■ “Hardware Issues and Workarounds” on page 15

■ “Hardware Documentation Updates” on page 15

Notes on Server Installation

The plug (NEMA L6-20) of the power cables supplied with the SPARC Enterprise
M4000/M5000 servers has the following dimensions.

Confirm in advance that the plug does not become an obstruction when plugged
into the input power source at the installation site.

■ Outside diameter of the connector part of the plug: 50 mm

■ Maximum outside diameter of the plug cover: 57 mm

■ Plug cover length from the connector end: 69.9 mm

Notes on DVD Drives and Discs

See the "Notes on DVD Drives and Discs in SPARC Enterprise" on the website below
before using the CD/DVD discs in the standard DVD drive mounted in this server.

Information About Hardware 13

URL:

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

Notes on the Use of USB Memory

To execute the dumpconfig(8), restoreconfig(8) or snapshot(8) command, if
you specify USB memory as the destination to store data, prepare the USB memory
as a medium in advance.
The data stored will include the information about the system. To use USB memory,
you need to pay attention to the management of the USB memory in which the data
stored, from the data security viewpoint.

We do not provide guarantees to every USB memory from any manufacturers that
currently on the market against its connectivity to XSCF and proper operation.
Depending on the USB memory in use, defects such as the XSCF firmware error or
reset may occur. In case such defects occurred, stop the use of USB memory
immediately.

To connect the USB memory to the USB port for XSCF, connect the USB memory
directly to the USB port. If connected via USB hub or USB extension cables, it may
cause errors.

Power Control and Operator Panel Mode Switch

You can use the mode switch on the operator panel to switch between system
power-on/off when you use the remote power control utilizing the RCI function or
the automatic power control system (APCS).

For details, see the "Limitations and Cautions" in "Preface" of the SPARC Enterprise
M4000/M5000 Servers Service Manual.

14 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Hardware Issues and Workarounds

Sun Crypto Accelerator 6000 Cards

If you are not using the correct version of the Sun Crypto Accelerator (SCA) 6000
card driver, hot-plug operations on SCA 6000 cards can cause SPARC Enterprise
M4000/M5000 servers to panic or hang. Version 1.1 of the SCA6000 driver and
firmware supports hot-plug operations after the required bootstrap firmware
upgrade has been performed. Version 1.0 of the SCA6000 driver does not support
hot-plug and should not be used.

Hardware Documentation Updates

This section contains late-breaking hardware information that became known after
the documentation set was published and corrections in the SPARC Enterprise
M4000/M5000 servers hardware documentation.

TABLE 3 lists known documentation updates.

TABLE 3 Hardware Documentation Updates

Title Page Number Update

SPARC Enterprise
M4000/M5000 Servers
Installation Guide (-05)

2-8 TABLE 2-3 "Power Cords"

The following note will be added.

Note - For the servers that have the B-type plug, confirm that

a 20A overcurrent protection device is available outside the
server. If one is not available, prepare an external 20A
overcurrent protection that can be achieved by means of no-fuse
breakers (NFBs) or fuses. The B-type plug refers to plugs other
than grounding-type ones with two parallel blades, such as the
NEMA L6-30, L6-20, L6-15, and L5-15.

3-8 3.3.2 "Initializing the XSCF Unit" will be changed. See

“Initializing the XSCF Unit” on page 16 for detail.

Information About Hardware 15

Updates of the SPARC Enterprise M4000/M5000 Servers Installation Guide (-05)

The following information supersedes the information in the SPARC Enterprise
M4000/M5000 Servers Installation Guide (-05).

Initializing the XSCF Unit

This is to correct 3.3.2 "Initializing the XSCF Unit" on page 3-8.

To use full XSCF functionality, various settings need to be set.

1. Set the required settings.

See section "Setting up XSCF" in the SPARC Enterprise
M3000/M4000/M5000/M8000/M9000 Servers XSCF User's Guide for details on how to

set these settings.

The following settings are required:

■ Registration of an XSCF user account and password and user privileges

(adduser, password, setprivileges)

■ User account of a field engineer (FE) (for maintenance)

■ Date and time settings (setdate, settimezone)

■ Confirmation of XSCF host public key (showssh)

■ SSH/telnet settings (setssh, settelnet)

■ Network interface, routing, and DNS-related settings (setnetwork, setroute,

setnameserver, etc.)

Note – Reset the XSCF unit with the applynetwork and rebootxscf commands.

■ Domain to Service Processor Communications Protocol (DSCP) configuration

(setdscp)

■ Altitude setting (setaltitude)

Note – setaltitude must be followed by a rebootxscf to apply the altitude

setting.

■ Dual power feed option setting (setdualpowerfeed)

16 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Note – setdualpowerfeed requires a complete chassis power cycle (all power

cords removed) to apply any changes. Make certain to allow 30 seconds before
plugging the power cords back into the chassis.

To perform XSCF initial settings, use the XSCF default user account. Until user
accounts for user environment is registered, log in with a default user account and
default password. The privileges of the default user are useradm and platadm.

2. Log in to the XSCF Shell using a user account and password set during Step 1.

See the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User's
Guide for details on how to log in to the user account.

Information About Hardware 17

Information About Software

This section describes the special instructions and the issues about the SPARC
Enterprise M4000/M5000 servers software.

■ “XCP Issues and Workarounds” on page 18

■ “Solaris OS Issues and Workarounds” on page 35

■ “Software Documentation Updates” on page 53

■ “Identifying Degraded Memory in a System” on page 57

■ “Identifying Different Memory Sizes in a System Board” on page 57

■ “Identifying Permanent Memory in a Target Board” on page 59

XCP Issues and Workarounds

This section contains information about XCP issues. TABLE 4, TABLE 5, and TAB LE 6 list
issues you might encounter, depending upon which XCP release you are using.

Known Issues and Workarounds in XCP 1091

TABLE 4 lists known XCP issues and possible workarounds in XCP 1091.

TABLE 4 Known Issues and Workarounds in XCP 1091

ID Description Workaround

RTIF1­080725-001

18 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

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

No workaround is available.

Confirm that the SNMP trap host is working
and re-execute the setsnmp(8) command
using the correct user name.

TABLE 4 Known Issues and Workarounds in XCP 1091 (Continued)

ID Description Workaround

RTIF1­080725-002

When the SNMPv3 trap has been set, after the
watchdog timeout occurred in XSCF and XSCF

Reset the XSCF.

reset, the subsequent SNMP traps will not be
notified.

RTIF1­081225-001

In the settimezone -c adddst command,
when you set eight or more letters to the
abbreviation of time zone and the name of

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

Daylight Saving Time, execution of the
showlogs command induces a segmentation
fault and results in an error.

RTIF1­090108-003

Date and time of the Last Update which
displayed on the XSCF Web may not be

Please refresh the display.

updated.

RTIF1­090427-004

RTIF1­090427-005

RTIF1­090824-001

RTIF1­091021-001

RTIF1­091109-002

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

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

The XSCF might go down and require a
reboot, or you might see console error
messages and a core dump
(ereport.chassis.software.core) when
one of these conditions occurs:

• A local account has been created with a user
ID explicitly assigned to a value larger than
65536 (adduser -u uid).

• An LDAP account has been used that has a
UID value larger than 65536.

While Active Directory is enabled, if you log in
to XSCF using the user name that registered in
the Active Directory server, the
showconsolepath(8) command displays not
the log-in user name but "proxyuser."

In XSCF, a host route cannot be set. When you
use the setroute(8) command and set the
netmask to 255.255.255.255, it returns an
invalid parameter.

To set 129 characters or more, use XSCF Shell.

No workaround is available.

Use XSCF Web.

Use only user accounts with a user ID (UID)
value between 100 and 60000. This is the range
of auto-assigned UIDs for the XSCF command
adduser(8).

No workaround is available.

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

Information About Software 19

TABLE 4 Known Issues and Workarounds in XCP 1091 (Continued)

ID Description Workaround

RTIF1-­091109-003

RTIF1­091109-004

RTIF1­091105-001

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

However, when you specify two or more same
IP address values or domain names to delete
all the DNS servers or the search paths which
are same, it returns an invalid parameter.

When you start up a domain from a disk
connected to the 8-Gbps fibre channel card
(SE0X7F21F, SE0X7F22F), if you fail to specify
the correct device path, an error log with no
message might be registered.

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

The loadcert console operand is missing in
the usage of the setad(8) command and the
setldapssl(8) command.

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

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

No workaround is available.

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

XCP Issues Fixed in XCP 1091

TABLE 5 lists XCP issues fixed in XCP 1091.

TABLE 5 XCP issues Fixed in XCP 1091

ID Description Workaround

RTIF1­070418-009

RTIF1­070528-002

20 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

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

While XSCF is running, watchdog timeout
may occur and XSCF may reboot.

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

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

TABLE 5 XCP issues Fixed in XCP 1091 (Continued)

ID Description Workaround

RTIF1­071102-002

RTIF1­081006-011

RTIF1­090427-002

RTIF1­090729-001

RTIF1­091109-001

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

command setsnmp enable.

SNMP trap host configuration changes are not
valid until setsnmp disable and setsnmp
enable.

After the XSCF reset or switching, you cannot
login to XSCF using the LDAP server.

When you use the sethttps(8) command to
create a self-signed web server certificate, if
the number of characters specified in a
parameter exceeds 100, it might result in an
internal error and you might fail to create the
certificate.

Once domain detected a failure related to
DIMM or PCI, the error log about this detected
failure is registered every time you reset XSCF.

Modify the SNMP setting:
XSCF> setsnmp disable
XSCF> setsnmp enable

No workaround is available.

Log in to active XSCF with initial account and
execute the following command to re-import
the certificate chain.

'setldap -c <remote file>'

Specify up to 100 characters in the parameter
and execute the sethttps(8) command again.

This error log can be safely ignored.

XCP Issues Fixed in Releases Earlier Than XCP 1091

TABLE 6 lists XCP issues that have been fixed in releases earlier than XCP 1091.

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091

ID Description Workaround

RTIF1­070418-004

RTIF1­070418-005

RTIF1­070418-010

All domains must be powered off before
upgrading the XCP firmware.

If you log in to the XSCF while it is still
booting, you may get a bash$ prompt instead
of the XSCF> prompt, and be unable to
perform most operations.

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

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

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

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

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

Information About Software 21

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­070418-011

Some commands that update configuration
data take a relatively long time to execute.

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

RTIF1­070418-012

RTIF1­070418-020

RTIF1­070418-021

RTIF1­070418-022

RTIF1­070418-023

RTIF1­070418-025

RTIF1­070528-001

RTIF1­070802-001

The fault (memory.block.ue) is encountered
and reported periodically.

When using the XSCF Web to import a
firmware image, if the image is corrupted (for
example, if the browser window is closed
during import), the flashupdate command
might later report an internal error.

CR ID 6537996 is similar.

Attempting to move a COD board using the
moveboard(8) command might fail.

The XSCF firmware monitors itself and if it
detects any anomolies, it will force a reboot.

Using the rebootxscf(8) command may
result in a process down error, and possibly an
FMA event with MSG ID SCF-8005-NE.

showaudit all shows a long list of defaults
in the policy section after the database is
cleared.

When you have updated the /etc/ttydefs
file of Solaris to disable the console flow
control, you cannot disable the console flow
control on the telnet via a server.

When connected to telnet, the login or the
password prompt doesn't appear.

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

Use the command getflashimage -d to
delete the corrupted image. If necessary, reboot
the XSCF Unit, then use the flashupdate
command again to clear the internal error.

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

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

Ignore this event.

Update the database with the following:

setaudit -a opl=enable
setaudit -a opl=default

No workaround is available.

Disconnect the telnet session and try again.

RTIF1­070823-001

Using the XSCF Web, when you selected SSH
on the snapshot screen, the maximum number
of character input for Host, Directory, ID, and

To specify the value which exceeds the
maximum number of character input for the

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

22 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­070823-002

When you display the Logical tree on the
XSCF Web, there may be multiple displays of
the same domain, depending on the domain
configuration.

On the Menu, select System Board
Configuration and refer to the domain
configuration from XSB Status (All). Or use the
showboards(8) command to refer to the
domain configuration.

RTIF1­070823-003

When you display the Logical tree on the
XSCF Web, the hardware configuration of CPU
or memory which assigned to the domain
appears differently from the actual domain

On the Menu, select Device Status to refer to
the domain hardware configuration. Or use the
showdevices(8) command to refer to the
domain hardware configuration.

configuration.

RTIF1­070824-001

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

After XSCF Unit is replaced, configures the
RCI again and sets the remote power control

mode.
replaced, the interlocking for power supply by
RCI cannot work.

RTIF1­070824-002

RTIF1­070824-003

On the XSCF Web, when you select Domain
Mode Configuration to perform various
settings, the pop-up screen may not appear but
"Undefined" may be displayed on the screen.

On the XSCF Web, while the XCP import is in
process from the Firmware Update screen,

Select Domain Mode Configuration one more

time and perform the settings. Or once

terminate the XSCF Web and then perform the

settings.

None available at this time.

when you execute the REFRESH button, the
pop-up of "Uploading Now!" disappears and
the XCP import terminates abnormally.

RTIF1­070824-004

On the XSCF Web, on the Domain Status
screen, when you select an XSB displayed on

None available at this time.

the Domain Component List, and in case the
selected XSB is not yet mounted or is Uni-XSB,
the pop-up screen displays no data.

RTIF1­070824-005

On the XSCF Web, when you changed the
Refresh Interval value of the Monitor Message

Ignore the pop-up and close the screen.

Frame, the invalid pop-up "Confirmation
Domain mode" may appear.

RTIF1­070824-006

On the tab browser, to the same host, when
you perform multiple log-in with the user

When you use the tab browser, do not perform

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

RTIF1­070824-007

When you change configuration on the XSCF
Web, if you select cancel on the confirmation

From the Menu, select the original

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

Information About Software 23

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­070824-008

On the Domain Configuration screen, when
you select an undefined Domain ID, the

None available at this time.

Configuration Policy remains as the content
which previously displayed.

RTIF1­070824-009

On the System Board Configuration screen,
when you execute Detail, it is displayed as if

None available at this time.

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

RTIF1­070824-011

While using Firefox 2, in the Configuration
policy setting on the Domain Configuration

From the Menu, select the Domain

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

RTIF1­070904-002

When the snapshot CLI attempts to write to a
USB stick that has write protect set results in

Do not attempt to use write-protected USB

devices for collecting snapshot.
an I/O error.

RTIF1­070904-003

An incorrect domain state is reported. After
the command sendbreak(8) to domain is

No workaround is available. This is expected

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

RTIF1­070904-005

Time can't be synchronized with the NTP
server.

Check the stratum value of the NTP server.

The stratum value of XSCF is "5." The NTP

server which the XSCF refers to must be a

server on which the stratum value is smaller

than 5. When you changed the NTP server to

refer to, reboot the XSCF.

When the stratum value has been set correctly

and the time can't be synchronized, use the

showntp(8) command to check the jitter value

to be displayed.

If this value is large, please reboot the XSCF.

RTIF1­070904-006

While executing the domain power-on,
domain reset or DR, in case the XSCF reboot
occurred, the process may be aborted in some

Execute the domain reset one more time, or

power off the domain and then power on

again.
or all of the XSB.

24 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­070912-001

If an invalid SMTP server is configured, a
subsequent attempt to disable email service
(using the setemailreport CLI) may block
for up to 30 minutes.

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

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

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

RTIF1­070914-001

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

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

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

RTIF1­070914-002

When the XSCF switching performed, the
monitor message doesn't show the number of

Execute the

showhardconf(8) command to

refer to the state of XSCFU.

XSCFU which turned Active.

RTIF1­070914-003

RTIF1­070914-005

RTIF1­070914-006

RTIF1­070914-007

RTIF1­070914-008

RTIF1­070914-009

When the XSCF switching performed, there
may be "SCF: Board control error
(DMA timeout)" stored in the error log.

On the XSCF Web, when using Internet
Explorer 7, on the User Accounts screen, User
Local Accounts doesn't show the Status of each
user.

When you set the XSCF user account name to
the maximum 32 characters, you can log in,
but then, when you execute the XSCF Shell or
operate the XSCF Web, "Permission
denied" occurs.

On the XSCF Web, when you use Internet
Explorer and select Log Archives, the Status of
Log Archiving screen doesn't show the status
information.

On the XSCF Web, when you select POP or
SMTP-auth on the SMTP screen to enter
Password, the input value doesn't appear as
"*".

On the XSCF Web, when selected POP or
SMTP-auth on the SMTP screen, the setting
can be done while the input field remains
blank. And despite the setting done, the past
setting data appears.

No workaround is available.

This message can be safely ignored.

None available at this time.

Use up to 31 characters to set the XSCF user
account name.

None available at this time.

None available at this time.

None available at this time.

Information About Software 25

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­070914-010

On the XSCF Web, on the SNMPv3 Security
Settings screen, when you select Add User or

When you set the SNMP User with 16 digits or
more, use the showsnmpusm(8) command.

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

RTIF1­070914-011

On the XSCF Web, on the SNMPv3 Security
Settings screen, when you select Change

Do not fail to set Confirm Password which is a

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

RTIF1­070914-012

On the XSCF Web, on the SNMP-Properties
screen, when you don't select Trap Host and

None available at this time.

execute the Remove button, the invalid
message "The trap host will be
removed" appears as a pop-up. And when you
select OK on the pop-up screen, the invalid
message "Remove trap host failed.
setsnmp: invalid trap type" appears.

RTIF1­070914-013

On the XSCF Web, on the Audit-Properties
screen, when you execute the Add Policy

Set the correct user name or execute the Cancel

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

RTIF1­070914-014

On the XSCF Web, when you use a user
account without an appropriate privilege to

None available at this time.

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

RTIF1­070914-015

On the XSCF Web, when you select User
Manager to add the user account, the user

To specify a user name of 20 characters or

more, use the adduser(8) command.
name to be specified is limited up to 20
characters.

26 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­070914-016

On the XSCF Web, when you select LDAP to
perform the LDAP configuration, if you
execute Save while the LDAP Search Timeout

Since "0" is an invalid value in the LDAP
Search Timeout, do not fail to set a value other

than 0.
remains as its default value "0," it results in
"LDAP Configuration Update Failed.

Save LDAP Configuration Data
failed," and the setting can't be stored.

RTIF1­070914-017

On the XSCF Web, when you select LDAP and
input the LDAP Search Timeout with a value
which exceeds the maximum 2147483647

None available at this time. The maximum

2147483647 seconds will be set to the LDAP

Search Timeout.
seconds, it doesn't result in parameter error.

RTIF1­070914-018

On the XSCF Web, when you use a user
account without an appropriate privilege to
select LDAP and execute the Delete button, it

The configuration is not deleted. To show the

configuration information again, select LDAP

from the Menu.
results in a privilege error but the
configuration information which has been
displayed will be cleared and seems as if
deleted.

RTIF1­070914-019

The CLI 'showldap -c' (which displays
current LDAP certificates) will show proper
data only when used with the same user

Use the same user account for all LDAP

display or configuration operations, for both

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

RTIF1­070914-020

On the User Account setting page on the User
Manager screen, after the password change

To change the password, select User Manager

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

RTIF1­070914-021

During the OpenBoot PROM process, when
you power off the domain, the error log of

This error log can be safely ignored.

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

RTIF1­070914-023

When you specify the domain ID or XSB
number which are not supported on the

To specify the available domain ID or XSB

number on the machine.
machine, there appears the parameter error
message.

Information About Software 27

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­070914-024

When you display the physical tree on the
XSCF Web, the warning mark is displayed on

None available at this time.

the link card for External I/O expansion unit.

RTIF1­070914-026

The XSCFU cannot act as a reliable NTP source
for domains.

All domains should be configured to use a
NTP source other than the XSCFU.

RTIF1­070915-001

RTIF1­071102-001

RTIF1­071116-001

RTIF1­071116-003

RTIF1­071116-004

RTIF1­071129-001

On the Domain Configuration screen, when
you newly define the Domain Component List,
the parameter error may be displayed.

The XSCF firmware monitors itself and if it
detects any inconsistencies, it forces an XSCF
reboot.

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

Using the XSCF Web, when you selected COD,
codusage details cannot be displayed correctly.

When Internet Explorer 7 browser is used, the
License key deletion cannot be executed on the
BUI COD page.

If the following message is displayed on XSCF
console, the XSCF might not start:

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

In addition, this error log might be be
registered:

XSCF process down detected

When you define the Domain Component List,
use CLI.

No workaround is available. Allow the XSCF
Unit to finish rebooting. It returns to normal
operation within approximately 5 minutes.

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

deletefru(8) command and then retry the
addfru(8) command.

Use showcodusage(8) command to display
the codusage.

Use deletecodlicense(8) command to
delete a license key. Or use other browsers:

• Microsoft Internet Explorer 6.0

• Firefox 2.0 or later

• Netscape Navigator 7.1 or later

Replace the XSCF Unit.

28 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­071129-002

When performing XSCF Shell commands
remotely using SSH on the remote-control

None available at this time.

device, the following messages might be
displayed:

stty: standard input: Invalid
argument

RTIF1­071129-003

An error log cannot be registered in XSCF
when the following message is displayed on

No workaround is available.

Solaris OS by the I/O error:
SUNW-MSG-ID: SUN4-8000-4P, TYPE:

Fault

RTIF1­071129-004

The following messages are displayed and you
might not boot Solaris OS:

• Abnormal OpenBoot environment

Confirm the OpenBoot PROM environment

variable. If the variable has errors, set the

variable again.

variable Boot process failed

• ERROR: Invalid token '' FATAL:

NVRAM contents corrupt;
Reinitializing NVRAM parameters.

RTIF1­071227-001

In XSCF, write of date and time may become
an error. When the domain powered on, the

Execute the rebootxscf(8) command to

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

Poweron canceled due to invalid
system date and time.

RTIF1­071227-002

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

Press Ctrl-C to terminate the

showhardconf(8) command and execute the

showhardconf(8) command again.

command may appear as if hang up.

RTIF1­071227-003

When a non-existent device name specified to
the Boot device path and resulted in the OS
Boot error, the status of I/O unit may become
"Degraded."

Specify the correct device name to the Boot

device path.

When the status of I/O unit became

"Degraded," replace the I/O unit.

Information About Software 29

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­080313-001

When you set XSCF as the NTP server of the
domain, following message may appear on the
domain console at the domain start and you
may fail to perform time synchronization.

ntpdate[xx]: no server suitable for

synchronization

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

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

•In case of step mode:

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

•In case of slew mode:

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

RTIF1­080325-001

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

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

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

30 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­080404-001

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

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

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

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

RTIF1­080404-002

When you use the command setsnmpusm
passwd to set a password, if you set a

Always set a password of at least eight

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

RTIF1­080512-001

When you specify "localhost" to the
hostname of the sethostname(8) command

Do not specify "localhost" to the hostname of

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

RTIF1­080512-003

To a domain which is in Quad-XSB
configuration, when you perform active
addition of PCI cards and then restart the

Do not perform active addition of PCI cards.

When you failed in active addition of PCI

cards, stop the domain to add on the cards.
domain, active addition of PCI cards may
become unavailable afterwards.

RTIF1­080526-001

When the system is stressed with many faults,
the fmd process on the service processor might

Reboot the service processor using the XSCF

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

RTIF1­080620-001

The SNMP-trap not notified in the event that
the power cable of the server got unplugged

No workaround is available.

accidentally.

RTIF1­080725-003

RTIF1­080725-004

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

parameters current value expected value

diag-level none(0x00) min(0x20)
auto-boot? false(0x00) true(0xff)

After set the Daylight Saving Time by using
the XSCF shell, XSCF Web does not show the
correct time in the Logs menu.

In the OpenBoot PROM prompt (ok>), execute

the set-defaults command to restore the

OpenBoot PROM environmental variables to

the initial value.

No workaround is available.

Use the

showlogs(8) command of the XSCF

shell.

Information About Software 31

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­080808-001

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

SA_pprcir.so to test host host_name

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

failed

RTIF1­081006-001

The error log "XSCF FMEM write error"
recorded and the firmware update might fail.

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

RTIF1­081006-002

RTIF1­081006-004

RTIF1­081006-005

RTIF1­081006-006

RTIF1­081006-007

RTIF1­081016-001

In the setemailreport(8) command, when
you specified over 255 characters in the SMTP
address, an error results.

During the firmware update, there might be
the following output message and a XSCF
panic might occur.

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

The network configuration on the XSCF Web
does not support the function equivalent to the
setnetwork -r comand. And when you
specified localhost or localdomain to the host
name or the domain name, the error message
"SessionID has expired" appears.

The panic log on the XSCF Web might not be
displayed from the top of the message.

The password(8) command indicates that the
[user] operand is optional but will fail if a
[user] operand is not included when other
options are specified.

Power failure at the commercial AC supply
connector to the UPS does not send
notification/send trap.

Do not specify over 255 characters in the SMTP
address.

Reset XSCF and use the flashupdate(8)
command to retry the firmware update.

Use the setnetwork -r command on the
XSCF shell.

When the output is insufficient, execute the
showlogs panic command on the XSCF shell.

No workaround is available.
Specify the user operand to execute the

password(8) command when you specify
other options.

No workaround is available.

RTIF1­081016-003

In Internet Explorer 6 or 7, clicking on the
[Reset] button then the [OK] button from the
Settings->Audit->Add Policy poupup screen
will log the user out with message:

Log back into the browser interface and use
the backspace key to clear text in the ’User’
text box of the popup screen instead of using
the Reset button.

Error
Session Error
Session ID has been expired

32 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­081030-002

When the timezone other than three characters
has been set, the error logs cannot be

Use the showlogs(8) command on the XSCF

shell.
displayed on XSCF Web "Error Log" page.

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

RTIF1­081104-001

The monitor message log might not be
registered when a PCI slot error detected.

No workaround is available.

Use the showlogs error command or the

fmdump command to check the fault

information of PCI slot.

RTIF1­090108-001

The domain console may display this message:

ipsec_check_inbound_policy: Policy

This message can be safely ignored.

Failure for the incoming packet
(not secure)

RTIF1­090108-002

In the dual power feed system, when the
power failure and the power recovery

You need to remove and insert the power

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

RTIF1­090115-001

When you execute the settelnet -c
disable command, the Telnet service will be

After you stopped the Telnet service, execute

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

RTIF1­090122-001

"Power recovery" message is output before
a PSU has recovered.

After the "Power recovery" message is

output, wait 60 seconds before removing

power from another PSU.

RTIF1­090220-001

RTIF1­090220-002

In a system connecting multiple hosts and one
or more I/O units with RCI, the power-on
operation to one of those RCI hosts may not
power on any of the RCI I/O units.

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

All the RCI hosts shall be powered on.

If you have set the power interlocking to a

value other than the default, replace the XSCF

unit and then use the setpwrmode(1M)

command to set the power interlocking setting

again.

Information About Software 33

TABLE 6 XCP Issues Fixed in Releases Earlier Than XCP 1091 (Continued)

ID Description Workaround

RTIF1­090427-001

Despite the normal status of ppp network
interface for the XSCF-to-Solaris OS

No workaround is available.

communication, SNMP MIB notifies abnormal
(down) status.

RTIF1­090430-001

After you set https (using the self certificate
authority) by XSCF and created a web server

To set the self certificate authority, do not
specify a blank character.

certificate, https is not enabled.

RTIF1­090508-001

In a domain mounted with the 10 Gigabit
Ethernet card (SE0X7HE1F), when you set the
OpenBoot PROM environmental variable
diag-switch? to true, the following
warning message appears on the console; and
at the same time, "Msg: Device error
(FCode informed error)" is recorded in
the error log.

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

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

The entire output can be safely ignored.

To avoid these outputs, execute the following
command at the ok prompt and set the
OpenBoot PROM environmental variable

diag-switch? to false.

setenv diag-switch? false

34 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Solaris OS Issues and Workarounds

This section contains information about Solaris OS issues. TABLE 7, TA BLE 8, TABLE 9,

TABLE 10, TA BLE 11 and TAB LE 12 list issues you might encounter, depending upon

which Solaris OS release you are using.

Solaris OS Issues for All Supported Releases

TABLE 7 lists Solaris OS issues that you might encounter in any supported release of

Solaris OS.

TABLE 7 Solaris OS Issues and Workarounds for All Supported Releases

CR ID Description Workaround

4816837 System hangs when executing parallel hot

plug operation with SP DR in suspend phase.

No workaround is available.

6459540 The DAT72 internal tape drive on a SPARC

Enterprise M4000/M5000 server may time out
during tape operations.

6466617 Performing a hot plug operation with the PCI-

Express slot too quickly interrupts a PCI leaf
reset and occurs the following error:

cfgadm: Component system is busy
error

Add the following definition to

/kernel/drv/st.conf:

tape-config-list =
"SEAGATE DAT DAT72-000",
"SEAGATE_DAT____DAT72-000",
"SEAGATE_DAT____DAT72-000";
SEAGATE_DAT____DAT72-000=

1,0x34,0,0x9639,4,0x00,0x8c,0x8c,
0x8c,3;

There are four spaces between SEAGATE DAT
and DAT72-000.

Pause a few seconds between the issue of each
cfgadm -c command.

Information About Software 35

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

CR ID Description Workaround

6481002 Installing the Solaris from the network using

certain PCI-Express cards may cause a panic.

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

6515648 "Replumb Failed" error appears when

dr@0:SB1::memory fails.

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

Example steps to re-plumb the interface
manually:

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

# ifconfig interface group group-name
# ifconfig interface addif xxx.xxx.xxx.xxx

-failover deprecated up

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

6516135 Ap_Id format and devices may not be shown

correctly by cfgadm(1M).

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

1) devfsadm (at Solaris prompt)

2) cfgadm

6519290 Large amounts of I/O on swap devices can

cause the system to appear hung by
overwhelming the I/O system. The amount of

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

set maxfastscan=0x2000

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

6522017 DR and ZFS may not be used in the same

domain.

Reduce the amount of kernel memory that ZFS
can allocate by setting the zfs_arc_max
parameter in the /etc/system file. The
following example sets the maximum size to
512 Mbytes.

set zfs_arc_max = 0x20000000

36 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

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

CR ID Description Workaround

6529714 Warning messages occur while trying to

No workaround is available.
configure more than four X4447A-Z or
X1027A-Z1 cards into one I/O Boat.

6530753 Some of the PCI slots in the External I/O

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

Use one of the following operations to display

all of the PCI slots.

• boot -r (at open boot prompt)

• devfsadm -C (at Solaris prompt)

• cfgadm (twice at Solaris prompt)

6531036 The error message network

initialization failed can appear

No workaround is available. This message can

be safely ignored.
repeatedly after boot net installation.

6532215 volfs or dscp service may fail when domain is

booted.

Restart the service if the failure is observed. To

avoid the problem, issue the following

commands.

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

# svccfg -s dscp setprop

start/timeout_seconds=count: 300

# svccfg -s volfs setprop
svc:/system/filesystem/volfs:defaul

t: Method or service exit timed
out. Killing contract 59.

6537511 Bluetooth partner is hung during security tests

start/timeout_seconds=count: 300

# svcadm refresh dscp

# svcadm refresh volfs

Restart application server
execution

6565553

6674266

DR deleteboard(8) and moveboard(8)
operations might fail.

Example for messages on domain:

drmach: WARNING: Device driver
failure: /pci

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

6592302 Unsuccessful DR operation leaves memory

partially configured.

6619344 The Sun Crypto Accelerator (SCA) 6000 card

might not work if hot-plug configured into slot

1.

No workaround is available.

Try DR operations again.

Tr y deleteboard(8) again.

To avoid the defect, do not hot-plug this card

in slot 1.

Information About Software 37

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

CR ID Description Workaround

6660168 If a ubc.piowbeue-cpu error occurs on a

domain, the Solaris Fault Management
cpumem-diagnosis module might fail, causing

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

# svcadm clear fmd

an interruption in FMA service.

If this happens, you will see the following
output in the console log:

SUNW-MSG-ID: FMD-8000-2K, TYPE:

Then restart cpumem-diagnosis:

# fmadm restart cpumem-diagnosis

Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Fri Apr 4 21:41:57 PDT

2008
PLATFORM: SUNW,SPARC-Enterprise,

CSN: 2020642002, HOSTNAME:
<hostname>

SOURCE: fmd-self-diagnosis, REV:

1.0
EVENT-ID: 6b2e15d7-aa65-6bcc-bcb1-

cb03a7dd77e3
DESC: A Solaris Fault Manager

component has experienced an error
that required the module to be
disabled. Refer to
http://sun.com/msg/FMD-8000-2K for
more information.

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

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

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

6668237 After DIMMs are replaced the corresponding

DIMM faults are not cleared on the domain.

Use the following commands:
# fmadm repair fmri|uuid
# fmadm rotate

6745410 Boot program ignoresthe Kadb option which

Use kmdb instead of kadb.

causes the system not to boot.

38 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

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

CR ID Description Workaround

6872501 If 139555-08 has been applied to the domain,

cores are not offlined when requested by the
XSCF.

6888928 IPMP interface fails since probe packets are not

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

Use fmdump(8) with its -v option on the

Service Processor to identify the faulty core.

Once identified, use psradm(1M) on the

domain to offline the core.

This has been fixed in patch 142900-02.

[Workaround]

Disable probe-based failure detection.

Solaris OS Issues Fixed in Solaris 10 10/09

TABLE 8 lists issues that have been fixed in Solaris 10 10/09 OS. You might encounter

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

TABLE 8 Solaris OS Issues Fixed in Solaris 10 10/09

CR ID Description Workaround

6572827 The prtdiag -v command reports PCI bus

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

6800734 The deleteboard(8) command hang in a

domain.

6816913 The XSCF showdevices(8) command displays

the incorrect processor cache size (MB) for
fractional processor cache sizes, such as
displaying "5" when the correct display would
be "5.5."

6821108 DR and showdevices(8) command do not

work after XSCF reset.

This has been fixed in patch 141444-09.

[Workaround]

No workaround is available.

This has been fixed in patch 141444-09.

No workaround is available.

Use the prtdiag(1M) command on the

domain to report processor information.

This has been fixed in patch 140589-02.

[Workaround]

Reset the XSCF service processor twice. Half

the SAs (Security Associations) are deleted the

first time, half are deleted the second time, so

the second addition succeeds and IPsec

communication is reestablished.

Information About Software 39

TABLE 8 Solaris OS Issues Fixed in Solaris 10 10/09 (Continued)

CR ID Description Workaround

6827340 DR and Memory patrol might fail due to

command error.

This has been fixed in patch 142344-01.

No workaround is available.

Solaris OS Issues Fixed in Solaris 10 5/09

TABLE 9 lists issues that have been fixed in Solaris 10 5/09 OS. You might encounter

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

TABLE 9 Solaris OS Issues Fixed in Solaris 10 5/09

CR ID Description Workaround

6588555 XSCF reset during DR operation to the

permanent memory might cause domain
panic.

6623226 The Solaris command lockstat(1M) or the

dtrace lockstat provider might cause a system
panic.

6680733 Sun Quad-port Gigabit Ethernet Adapter UTP

(QGC) & Sun Dual 10 GigE Fiber XFP Low
Profile Adapter (XGF) NICs might panic under
high load conditions.

6689757 Sun Dual 10 GigE Fiber XFP Low Profile

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

The XFP optical transceiver is
broken or missing.

This has been fixed in patch 139555-08.

[Workaround]

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

This has been fixed in patch 140336-01.

[Workaround]
Do not use the Solaris lockstat(1M)

command or the dtrace lockstat provider.

This has been fixed in patch 139570-01.

This has been fixed in patch 139570-01.

[Workaround]

Check and make sure that both XFP optical
transceivers are firmly seated in the housing.
Do not mix INTEL and Sun XFP optical
transceivers in the same Adapter.

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

40 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Solaris OS Issues Fixed in Solaris 10 10/08

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

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

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

CR ID Description Workaround

6511374 Unexpected error messages may be displayed

on console after changing the system
configuration.

Example:

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

6533686 When XSCF is low on system resources, DR

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

SCF busy
DR parellel copy timeout

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

6608404 Hot-plug of the X4447A-Z, PCI-e Quad-port

Gigabit Ethernet Adapter UTP card in slot 1
might cause other network devices to fail.

This has been fixed in patch 137137-09.

This message can be safely ignored.

This has been fixed in patch 138397-01.

[Workaround]

Retry the DR operation at a later time.

To avoid the defect, do not install this card in

slot 1.

Information About Software 41

TABLE 10 Solaris OS Issues Fixed in Solaris 10 10/08 (Continued)

CR ID Description Workaround

6614737 The DR deleteboard(8) and moveboard(8)

operations might hang if any of the following

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

conditions exist:

• A DIMM has been degraded.

• The domain contains system boards with
different memory size.

[Workaround]

Avoid performing DR operations if any of the
listed conditions exist.

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

Target Board” on page 59.

To determine whether the domain contains
system boards with different memory sizes,
display the list of memory sizes using the
XSCF showdevices(8) command or the
prtdiag(8) command on the domain. For
sammple of output, see “Identifying Degraded

Memory in a System” on page 57

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

6632549 fmd service on domain might fail to

This has been fixed in patch 138050-01.

maintenance mode after DR operations.

[Workaround]

If fmd service fails, issue the following
commands on the domain to recover:

# svcadm clear fmd

6660197 DR might cause the domain to hang if either of

This has been fixed in patch 138397-01.

the following conditions exist:

• A domain contains 256 or more CPUs.

• Memory error occurred and the DIMM has
been degraded.

[Workaround]

1. Set the following parameterin the system

specification file (/etc/system):

set drmach:drmach_disable_mcopy = 1

2. Reboot the domain.

42 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 10 Solaris OS Issues Fixed in Solaris 10 10/08 (Continued)

CR ID Description Workaround

6679370 The following message may be output on the

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

This has been fixed in patch 137137-09.

Note - Before adapting the patch, delete the

following setting from /etc/system:
set pcie_expected_ce_mask = 0x2001

SUNW-MSG-ID: SUN4-8000-75, TYPE:
Fault, VER: 1, SEVERITY: Critical

...
DESC:
A problem was detected in the PCI-

Express subsystem.
Refer to http://sun.com/msg/SUN4-

8000-75 for more information.
...

6720261 If your domain is running one of the following

versions of Solaris OS, the system might
panic/trap during normal operation:

• Solaris 10 5/08 OS

• An earlier version of Solaris 10 OS with
patch ID 127127-11

[Workaround]
Add the following to /etc/system and then

reboot the domain.

set pcie_expected_ce_mask = 0x2001

This has been fixed in patch 137137-09.

[Workaround]

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

set heaplp_use_stlb=0

Then reboot the domain.

Information About Software 43

Solaris OS Issues Fixed in Solaris 10 5/08

TABLE 11 lists issues that have been fixed in Solaris 10 5/08 OS. You might encounter

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

TABLE 11 Solaris OS Issues Fixed in Solaris 10 5/08

CR ID Description Workaround

6472153 If you create a Solaris Flash archive on a non-

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

6522433 After the CPU hardware error occurred, the

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

6527811 The showhardconf(8) command on the XSCF

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

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

[Workaround]

Just after installing Solaris OS from a Solaris
Flash archive, telnet into the SPARC Enterprise
M4000/M5000 server to reset the console's
TTY flags a follows:

# sttydefs -r console
# sttydefs -a console -i "9600 hupcl

opost onlcr crtscts" -f "9600"

This procedure is required only once.

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

[Workaround]

Check system status on XSCF.

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

44 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 11 Solaris OS Issues Fixed in Solaris 10 5/08 (Continued)

CR ID Description Workaround

6536564 showlogs(8) and showstatus(8) command

on XSCF might report wrong I/O component

For Solaris 10 8/07 or earlier, this has been

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

[Workaround]

To avoid this problem, issue the following

commands on the domain.

# cd /usr/platform/SUNW,SPARC-

Enterprise/lib/fm/topo/plugins

# mv ioboard.so ioboard.so.orig

# svcadm restart fmd

If the following messages are displayed on the

domain, contact a service engineer.

Example:

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

Defect, VER: 1, SEVERITY: Minor

EVENT-TIME: Sun May 6 18:22:24 PDT

2007

PLATFORM: SUNW,SPARC-Enterprise,

CSN: BE80601007, HOSTNAME: sparc

6545143 There is a low probability that a system panic

can occur during trap processing of a TLB miss

For Solaris 10 8/07 or earlier, this has been

fixed in patch 127111-08.
for a user stack address. The problem can
occur if the user stack is unmapped
concurrently with the user process executing a

No workaround is available.

flush windows trap (ta 3). The panic message
will contain the following string:

bad kernel MMU trap at TL 2

6545685 If the following message displayed on the OS

console, memory degradation or XSB

For Solaris 10 8/07 or earlier, this has been

fixed in patch 127111-08.
deconfiguration may occur in the subsequent
reboot.

[Workaround]

Add the following to /etc/system and then
Example:

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

reboot the domain:

set mc-opl: mc_max_rewrite_loop =

20000

Information About Software 45

TABLE 11 Solaris OS Issues Fixed in Solaris 10 5/08 (Continued)

CR ID Description Workaround

6546188 The system panics when running hotplug

(cfgadm(1M)) and DR operations

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

(addboard(8) and deleteboard(8)) on the
following cards:

No workaround is available.

• X4447A-Z, PCI-e Quad-port Gigabit
Ethernet Adapter UTP

• X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet
Fiber XFP Low profile Adapter

6551356 The system panics when running hotplug

(cfgadm(1M)) to configure a previously

For Solaris 10 8/07, this has been fixed in

patch 127741-01.
unconfigured card. The message "WARNING:
PCI Expansion ROM is not accessible" will be
seen on the console shortly before the system
panic. The following cards are affected by this
defect:

• X4447A-Z, PCI-e Quad-port Gigabit

Ethernet Adapter UTP

[Workaround]

Perform cfgadm -c disconnect to

completely remove the card. After waiting at

least 10 seconds, the card may be configured

back into the domain using the cfgadm -c

configure command.

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

Fiber XFP Low profile Adapter

6559504 Messages of the form nxge: NOTICE:

nxge_ipp_eccue_valid_check: rd_ptr = nnn

For Solaris 10 8/07, this has been fixed in

patch 127741-01.
wr_ptr = nnn will be observed on the console
with the following cards:

• X4447A-Z, PCI-e Quad-port Gigabit

Ethernet Adapter UTP

[Workaround]

These messages can be safely ignored.

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

Fiber XFP Low profile Adapter

6564934 Performing a DR deleteboard(8) operation

on a board which includes Permanent Memory

For Solaris 10 8/07, this has been fixed in

patch 127741-01.
when using the following network cards
results in broken connections:

• X4447A-Z, PCI-e Quad-port Gigabit

Ethernet Adapter UTP

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

Fiber XFP Low profile Adapter

[Workaround]

Re-configure the affected network interfaces

after the completion of the DR operation. For

basic network configuration procedures, refer

to the ifconfig man page for more

information

6568417 After a successful CPU DR deleteboard(8)

operation, the system panics when the

For Solaris 10 8/07 or earlier, this has been

fixed in patch 127111-02.
following network interfaces are in use:

• X4447A-Z, PCI-e Quad-port Gigabit

Ethernet Adapter UTP

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

Fiber XFP Low profile Adapter

[Workaround]

Add the following line to /etc/system and

reboot the system:

set ip:ip_soft_rings_cnt=0

46 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 11 Solaris OS Issues Fixed in Solaris 10 5/08 (Continued)

CR ID Description Workaround

6571370 Use of the following cards have been observed

to cause data corruption in stress test under

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

laboratory conditions:

• X4447A-Z, PCI-e Quad-port Gigabit
Ethernet Adapter UTP

• X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet
Fiber XFP Low profile Adapter

6589546 prtdiag(8) command does not show all I/O

devices of the following cards:

[Workaround]
Add the following line in /etc/system and

reboot the system: set

nxge:nxge_rx_threshold_hi=0

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

• XSEFC402AF Sun StorageTek Enterprise
Class 4Gb Dual-Port Fibre Channel PCI-E
HBA

[Workaround]
Use prtdiag -v for full output.

• XSEFC401AF Sun StorageTek Enterprise
Class 4Gb Single-Port Fibre Channel PCI-E
HBA

Information About Software 47

Solaris OS Issues Fixed in Solaris 10 8/07

TABLE 12 lists issues that have been fixed in Solaris 10 8/07 OS. You might encounter

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

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

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

TABLE 12 Solaris OS Issues Fixed in Solaris 10 8/07

CR ID Description Workaround

6416224 System performance can degrade using a

single NIC card with more than 5,000
connections.

6441349 The system may hang if there is an I/O error

in the system.

6485555 On-board Gigabit Ethernet NVRAM

corruption could occur due to a race condition.

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

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

[Workaround]

Use multiple NIC cards to split network
connections.

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

No workaround is available.

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

No workaround is available.

48 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 12 Solaris OS Issues Fixed in Solaris 10 8/07 (Continued)

CR ID Description Workaround

6496337 The "cpumem-diagnosis" module may fail to

load after uncorrectable error(UE) panic.

For Solaris 10 11/06, this has been fixed in
patch 125369-05.

Systems will function correctly but events
normally automatically diagnosed by FMA
using this module will require manual
diagnosis.

Example:

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

EVENT-TIME: Thu Feb 15 15:46:57 JST
2007

PLATFORM: SUNW,SPARC-Enterprise,

[Workaround]

If problem occurred, implement the following

workaround:

1. Remove the following file.

# rm /var/fm/fmd/ckpt/cpumem­diagnosis/cpumem-diagnosis

2. Restart fmd service.

# svcadm restart fmd

CSN: BE80601007, HOSTNAME: col2-ff­em7-d0

To avoid this problem in advance,
add "rm -f /var/fm/fmd/ckpt/cpumem-

diagnosis/cpumem-diagnosis" in
/lib/svc/method/svc-dumpadm file as

below.

#
# We haven't run savecore on a

dump device yet
#
savedev=none

6498283 Using the DR deleteboard(8) command

while psradm operations are running on a
domain might cause a system panic.

6499304 CPU isn't offlined and unexpected message is

displayed on console when many correctable
error(CE) occurs.

Example:

SUNW-MSG-ID: FMD-8000-11, TYPE:
Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Fri Feb 2 18:31:07 JST
2007

PLATFORM: SPARC-Enterprise, CSN:
BE80601035, HOSTNAME: FF2-35-0

rm -f /var/fm/fmd/ckpt/cpumem­diagnosis/cpumem-diagnosis

#

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

No workaround is available.

For Solaris 10 11/06, this has been fixed in
patch 125369-05.

[Workaround]

Check CPU status on XSCF.

Information About Software 49

TABLE 12 Solaris OS Issues Fixed in Solaris 10 8/07 (Continued)

CR ID Description Workaround

6502204 Unexpected error messages may be displayed

on console on booting after CPU UE panic.

For Solaris 10 11/06, this has been fixed in
patch 125369-05.

Example:

SUNW-MSG-ID: FMD-8000-11, TYPE:
Defect, VER: 1, SEVERITY: Minor
EVENT-TIME: Tue Jan 9 20:45:08 JST
2007

[Workaround]

If you see unexpected messages, use the XSCF
command showdomainstatus(8) to check
system status on XSCF.

PLATFORM: SUNW,SPARC-Enterprise,
CSN: 2030636002, HOSTNAME: P2-DC1­16-d0

6502750 Notification message for inserted or removed

card by PCI hot plug may not output.

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

No workaround is available.

6508432 Many correctable errors (CE) may occur, and

despite these are the correctable errors,

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

domain may panic.

[Workaround]
Set the following to /etc/system and then

reboot the domain:

set pcie:pcie_aer_ce_mask = 0x2001

6508434 The domain may panic when an additional

PCI-X card is installed or a PCI-X card is

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

replaced by using PCI hot plug.

[Workaround]

Do not insert a different type of PCI-X card on
the same PCI slot by using PCI hot plug.

6509337 s10s_u3 wanboot fails - The server returned

No workaround is available.

416: Requested Range Not Satisfiable.

6510861 When Dual-Channel Ultra320 SCSI Card

(SE0X7SC2F, SE0X7SC2X) is mounted,

For Solaris 10 11/06, this has been fixed in

patch 120011-08.
correctable errors(CE) occur and system may
panic.

[Workaround]

Add the following entry to the /etc/system

file and then reboot the system:

set pcie:pcie_aer_ce_mask = 0x31c1

50 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 12 Solaris OS Issues Fixed in Solaris 10 8/07 (Continued)

CR ID Description Workaround

6520990 Domain may cause a panic when

deleteboard(8) command for kernel board

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

by using Dynamic Reconfiguration (DR).

[Workaround]

To mask this error, add the following entry to
the /etc/system file.

set drmach:fmem_timeout = 30

6530178 DR addboard(8) command can hang. Once

problem is observed, further DR operations are

For Solaris 10 11/06, this has been fixed in

patch 120011-07.
blocked. Recovery requires reboot of the
domain.

6530288 Ap_Id format may not be shown correctly by

cfgadm(1M) command.

No workaround is available.

For Solaris 10 11/06, this has been fixed in

patch 120011-07.

No workaround is available.

6534471 Systems may panic/trap during normal

operation.

For Solaris 10 11/06, this has been fixed in

patch 125100-06.

If a patch is not available, disable the kernel

large page sTLB programming. In the file

/etc/system, change the variable

heaplp_use_stlb to 0:

set heaplp_use_stlb=0

6535564 PCI hot plug to PCI slot #0, #1 or External I/O

Expansion Unit may fail on XSB added by DR.

For Solaris 10 11/06, this has been fixed in

patch 120011-08.

6539084 Under Solaris 10 11/06, there is a low

probability of a domain panic during reboot
when the Sun Quad GbE UTP x8 PCIe
(X4447A-Z) card is present in a domain.

[Workaround]

Use DR instead of PCI hot plug if need to add

or remove PCI card on the XSB.

No workaround is available.

Information About Software 51

TABLE 12 Solaris OS Issues Fixed in Solaris 10 8/07 (Continued)

CR ID Description Workaround

6539909 Under Solaris 10 11/06, do not use the

following I/O cards for network access when
you are using the boot net install

Use an alternate type of network card or
onboard network device to install the Solaris
OS via the network.

command to install the Solaris

OS:

• X4447A-Z/X4447A-Z, PCIe Quad-port
Gigabit Ethernet Adapter UTP

• X1027A-Z/X1027A-Z, PCIe Dual 10 Gigabit
Ethernet Fiber XFP

6542632 Memory leak in PCIe module if driver attach

fails.

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

No workaround is available.

52 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Software Documentation Updates

This section contains late-breaking software information that became known after
the documentation set was published and corrections in the SPARC Enterprise
M4000/M5000 servers software documentation.

The corrections for SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers
XSCF Reference Manual, if not otherwise specified, also apply to the man pages which
XSCF provides. And they supersede the information on the man pages.

TABLE 13 lists known documentation updates.

TABLE 13 Software Documentation Updates

Title Page Number Update

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

password(8)
and

setpasswordp
olicy(8)

commands

setdualpower

feed(8)
command

sethttps(8)
command

The setad(8), setldapssl(8), showad(8), and the

showldapssl(8) will be added. See the setad(8),
setldapssl(8), showad(8), and the showldapssl(8)

commands man pages.

The maximum values of several options will be changed like as
follows:

Example) password -i: Valid values are integers with value of

-1 - 999999999.

The following description will be added in DESCRIPTION:

The dual power feed mode cannot be used with 100V power on
the M4000/M5000 servers.

The following description will be added in EXTENDED
DESCRIPTION:

The size of the file to be generated by sethttps(8) grows with
total character count typed in the operands of configuring the
self-certification authority and creating a self-signed web server
certificate, and creating a CSR. If the file to be generated is too
large for XSCF, the command fails with an error. If you see this
error, reduce the number of characters in the operands and
execute the sethttps(8) command again.

Information About Software 53

TABLE 13 Software Documentation Updates (Continued)

Title Page Number Update

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

setnameserve
r(8) command

• The following description will be added in OPERANDS:
You cannot specify the loopback address (127.0.0.0/8), the
network address, or a broadcast address.

• The following options for specifying a domain being referred
to DNS server will be added:

-c addsearch

-c delsearch

• Along with the addition of DNS search path, related
descritpion for DNS search path will be added in the

applynetwork(8), sethostname(8), and
shownameserver(8) commands. For details, see the the
setnameserver(8), applynetwork(8), sethostname(8),
and shownameserver(8) man pages.

setnetwork(8)

command

The following description will be added in OPERANDS:

You cannot specify the loopback address (127.0.0.0/8), the
network address, a broadcast address, or class D or E (224.0.0.0

- 255.255.255.255) address.

setntp(8)
command

• The following description will be added in OPERANDS:
You cannot specify the loopback address (127.0.0.0/8), the
network address, or a broadcast address.

• The following options for setting the local clock of XSCF will
be added:

-m localaddr=value

• Along with the addition of clock address, related descritpion
for local addresses will be added in the showntp(8)
command. For details, see the the setntp(8) and showntp(8)
man pages.

setroute(8)
command

• The following description will be added in OPTIONS:
You cannot specify the loopback address (127.0.0.0/8), the
network address, or a broadcast address.

• The description, " If you specified 0.0.0.0 in the -n option, do
not specify the -m option." in OPTIONS will be changed to
the following description:
If you specified 0.0.0.0 in the -n option, you must specify

0.0.0.0 in the -m option or you must omit the -m option.

setupfru(8)
command

The following description will be added in EXTENDED
DESCRIPTION:

Although a CMU with two CPUMs can be configured into
Quad-XSB mode on an M8000/M9000 server, the server
generates a "configuration error" message for these XSBs
that do not have a CPUM and memory.

54 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

TABLE 13 Software Documentation Updates (Continued)

Title Page Number Update

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

showdevices(

8) command

The following description will be added in EXTENDED
DESCRIPTION:

The showdevices(8) command displays a complete list of
devices when executed right after a Solaris OS boot or a DR
operation. However, when executed at other times,
showdevices does not display a complete list if the Solaris OS
has unloaded drivers for any unused devices. To be certain the
displayed list is complete, run the devfsadm command with -v
option on the domain before running showdevices. For more
information about the devfsadm command, see the Solaris
devfsadm(1M) man page.

showenvironm

ent(8)
command

Following information will be added.

"Airflow volume information is not supported on the
M4000/M5000 servers."

"The power consumption information is displayed on the
M3000/M4000/M5000 servers." will be replaced by "The power
consumption information is displayed on the M3000 server."

showhardconf

(8) command

XSCF man pages setad(8)

command

The example of M3000 server with DC power will be added in
the EXAMPLES section.

The following information has not yet been added to the
userdomain description in the OPERANDS section of the
setad(8) man pages:

A user domain can be configured explicitly through the setad
userdomain command on XSCF, or entered at login prompt
using the form, user@domain.

A part of the description of EXAMPLE6 will be changed as
follows:

userdomain can take the form of UserPricipalName (UPN) or
Distinguished Name (DN).

A part of the description of EXAMPLE12 will be changed as
follows:

XSCF> setad dnslocatorquery -i 2

'_ldap._tcp.gc._msdcs.<DOMAIN>.<PORT:3269>'

Information About Software 55

TABLE 13 Software Documentation Updates (Continued)

Title Page Number Update

XSCF man pages setldapssl(8)

command

The usermapmode description in the OPERANDS section will
be changed as follows:

Enable or disable use of the usermap. When enabled, user
attributes specified with the usermap operand, rather than
userdomain, are used for user authentication.

A part of the description of EXAMPLE6 in the EXAMPLES
section will be changed as follows:

userdomain can only take the form of Distinguished Name
(DN).

XSCF>

setldapssl userdomain -i 2
'uid=<USERNAME>,ou=yoshi,dc=example,
dc=aCompany,dc=com'

The examples for binddn, bindpw, and searchbase are
added in EXAMPLE7 in the EXAMPLES section.

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

8-19 8.1.10, two sections, "Confirming That the XSCF Firmware Is

The description of this feature, described in “Active Directory

and LDAP/SSL” on page 2, has not yet been added.

Updated When the XSCF Unit Is Replaced (in a System With a
Single XSCF Unit or Both Replacement in a System With
Redundant XSCF Units)" and "Confirming That the XSCF
Firmware Is Updated When the MBU Is Replaced (in the M3000
server) ", the step2 and step3 will be changed as below:

2. If the replacement unit and the replaced unit have different

versions, a message is displayed. In this case, the firmware is
not updated automatically. The operator must match the
number of the firmware versions.

3. When you update, follow the procedure in "Updating XCP

From External Media" or "Updating XCP From the Network"
to update XCP, and confirm the version.

56 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Identifying Degraded Memory in a System

1. Log in to XSCF.

2. Type the following command:

XSCF> showstatus

The following example identifies that DIMM number 0A on Memory Board #5 has
degraded memory.

XSCF> showstatus
MBU_B Status:Normal;
MEMB#5 Status:Normal;
* MEM#0A Status:Degraded;

Identifying Different Memory Sizes in a System Board

To identify if the domain contains system boards with different memory sizes, you
can use either of the following commands to display the list of memory sizes:

■ showdevices(8) command on the XSCF

■ prtdiag(1M) command on the domain

Using the showdevices Command

1. Log in to XSCF.

Information About Software 57

2. Type the following command:

XSCF> showdevices -d domain_id

The following example displays 00-0 has 64GB of memory while the other system
boards have 16GB.

XSCF> showdevices -d 1
Memory:

------­ board perm base domain target deleted remaining
DID XSB mem MB mem MB address mem MB XSB mem MB mem MB
01 00-0 63680 0 0x0000004000000000 260288
01 01-0 16384 7384 0x0000034000000000 260288
01 01-1 16384 0 0x0000030000000000 260288
01 01-2 16384 0 0x000002c000000000 260288
01 01-3 16384 0 0x0000028000000000 260288
...

Using the prtdiag Command

■ On the domain, execute the prtdiag command.

# prtdiag

The following example displays different memory sizes.

# prtdiag
============================ Memory Configuration ============================
Memory Available Memory DIMM # of Mirror Interleave
LSB Group Size Status Size DIMMs Mode Factor

--- ------ ------------------ ------- ------ ----- ------- ---------­00 A 8192MB okay 2048MB 4 no 2-way
00 B 8192MB okay 2048MB 4 no 2-way
01 A 8192MB okay 2048MB 4 no 2-way
01 B 8192MB okay 2048MB 4 no 2-way
03 A 8192MB okay 2048MB 4 no 2-way
03 B 8192MB okay 2048MB 4 no 2-way
...

58 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010

Identifying Permanent Memory in a Target Board

1. Log in to XSCF.

2. Execute the following command:

XSCF> showdevices -d domain_id

The following example shows a display of the showdevices -d command where 0
is the domain_id.

XSCF> showdevices -d 0

...

Memory:

------­ board perm base domain target deleted remaining
DID XSB mem MB mem MB address mem MB XSB mem MB mem MB
00 00-0 8192 0 0x0000000000000000 24576
00 00-2 8192 1674 0x000003c000000000 24576
00 00-3 8192 0 0x0000034000000000 24576

...

The entry for column 4 perm mem MB indicates the presence of permanent memory
if the value is non-zero.

The example shows permanent memory on 00-2, with 1674 MB.

If the board includes permanent memory, when you execute the deleteboard(8)
command or the moveboard(8) command, the following notice appears:

System may be temporarily suspended, proceed? [y|n]:

Information About Software 59

60 SPARC Enterprise M4000/M5000 Servers Product Notes for XCP Version 1091 • April 2010