Sun SPARC Enterprise M4000/M5000 Servers Product Notes

This document includes these sections:


New in XCP 1071

In XCP Version 1071 SPARC64trademark VII processors are supported on SPARC Enterprise M4000/M5000 servers.

For information about installing SPARC64 VII processors, see Adding SPARC64 VII Processors to Your Server -- Service Representatives Only. Note that only authorized service representatives may perform installation.


Supported Firmware and Software Versions

TABLE 1 lists the minimum required versions of some supported software and firmware on Sun SPARC Enterprise M4000/M5000 servers. If you are upgrading from an earlier version of XCP firmware, also refer to Upgrading to XCP 1071.


TABLE 1 Minimum Software and Firmware Versions

Software or Firmware

Version

XSCF Control Package

Capacity on Demand (COD) support:

 

XCP 1050

Solaris Operating System

 

Solaris 10 11/06, with required patches[1], or

Solaris 10 8/07, with required patches*


TABLE 2 lists minimum supported versions of Web browsers for use with the XSCF Web.


TABLE 2 Minimum Web Browser Versions

Web Browser Application

Version

Firefox

2.0

Microsoft Internet Explorer

6.0

Mozilla

1.7

Netscape Navigator

7.1


Using a WAN Boot Server

If you plan to boot your Sun SPARC Enterprise M4000/M5000 server from a Solaris WAN boot server on the network, you must have the appropriate wanboot executable intalled to provide the needed hardware support. See Booting From a WAN Boot Server for details.


Solaris Patch Information

Solaris patches are required for:

Always refer to the patch README for information about patch requirements and special installation instructions.

The patch identifiers listed in this section represent the minimum level of the patches that must be installed. The two-digit suffix represents the minimum revision level of the patch.

Check http://sunsolve.sun.com for the latest patch revision, and refer to Latest Solaris Patches for information on how to find the latest patches and for general installation instructions.

Required Patches for Solaris 10 8/07 with SPARC64 VII CPUs

The following patches are required for Solaris 10 8/07 OS only on servers containing SPARC64 VII CPUs. Install them in the order in which they are listed:

1. 119254-51 - SunOS 5.10: Install and Patch Utilities Patch

2. 125891-01 - SunOS 5.10: libc_psr_hwcap.so.1 patch

3. 127755-01 - SunOS 5.10: Fault Manager patch

4. 127127-11 - SunOS 5.10: kernel patch

In addition, if you are using any of the PCI-E or PCI-X cards listed in the next two sections, you must also install additional patches.

Patches for Emulex PCI-E and PCI-X Cards

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

Patches for QLogic PCI-E and PCI-X Cards

The following QLogic cards require drivers supplied in patch 125166-10:

Required Patches for Solaris 10 11/06 OS

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. Install the patches in the order in which they are listed:

1. 118833-36 - Reboot your domain before proceeding.

2. 125100-10 - See the patch README file for a list of other patch requirements.

3. 123839-07

4. 120068-03

5. 125424-01

6. 118918-24

7. 120222-21

8. 125127-01 - Reboot your domain before proceeding.

9. 125670-02

10. 125166-05


Upgrading to XCP 1071

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

Updating the OpenBoot PROM Firmware

To complete updating the OpenBoottrademark PROM (OBP) firmware in the target domain, be sure to restart the domain. You should restart the domain as soon as possible after completing the update.

Upgrading From XCP 104n

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


General Functionality Issues and Limitations

This section describes known hardware and software issues in this release.



caution icon Caution - For dynamic reconfiguration (DR) and hot-plug issues, see Solaris OS Issues and Workarounds.




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


Then you must set the following parameter in the system specification file (/etc/system):

set heaplp_use_stlb=0

Then reboot the domain.

For more information, refer to CR 6718173 in TABLE 5.


Hardware Installation and Service Issues

TABLE 3 lists known issues for which a defect change request ID has been assigned. The table also lists possible workarounds. To check for availability of new patches that fix these issues, go to:

http://sunsolve.sun.com


TABLE 3 Hardware Issues and Workarounds

CR ID

Description

Workaround

6433420

The domain console might display a Mailbox timeout or IOCB interrupt timeout error during boot.

Issue a reset-all command from the OBP (OK) prompt and reboot.


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

U320 PCIe SCSI Card

U320 PCIe SCSI card, part numbers 375-3357-01/02, is not supported in PCI cassettes for Sun SPARC Enterprise M4000/M5000 servers. Customers must use
375-3357-03 or later.


Software and Firmware Issues

This section describes specific software and firmware issues and workarounds. To obtain patches and to check for availability of new patches that fix these issues, go to:

http://sunsolve.sun.com

XCP Issues and Workarounds

TABLE 4 lists XCP issues and possible workarounds.


TABLE 4 XCP Issues and Workarounds

ID

Description

Workaround

6565422

The Latest communication field in showarchiving is not updated regularly.

Disabling and re-enabling archiving refreshes the Latest communication field in showarchiving output.

6624646

Sun Connection Update Manager GUI might fail to register correctly.

Use the command-line interface (CLI) if you run into any GUI registration issues.

6664134

Certain service processor-detected faults are not reported by the XSCF command fmadm faulty, nor will such faults be passed along as an ereport to the domain.

Use the XSCF command showstatus or fmdump instead.

6674742

When the system is stressed with many faults, the fmd process on the service processor might hang. Once this happens, fma commands on the service processor can fail or hang.

Reboot the service processor using the XSCF command rebootxscf.

6665174

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

If you run into this problem, the fmdump(8) command will show a report:

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

An authorized service represenative can perform further diagnosis or clear the errors.

6675409

If COD licensed capacity is changed while a COD board is undergoing DR, some of the COD CPUs might be marked as Faulted.

This will require a service action to correct.

Do not attempt to modify the COD licensed capacity while a DR operation is in progress on a COD board.

COD licensed capacity is modified by adding or removing licenses (with the addcodlicense or deletecodlicense commands) or by changing headroom (with the setcod command). Do not use these commands (or equivalent browser operations) while a DR operation is in progress. You can change the COD licensed capacity after the DR operation is completed.

6679286

When you use the command setsnmpusm passwd to set a password, if you set a password of fewer than eight characters, a segmentation fault occurs.

Always set a password of at least eight characters.


Solaris OS Issues and Workarounds

This section contains information about Solaris OS issues. TABLE 5, TABLE 6, and TABLE 7 list issues you might encounter, depending upon which Solaris OS release you are using.

Solaris Issues for All Supported Releases

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


TABLE 5 Solaris OS Issues and Workarounds for All Supported Releases

CR ID

Description

Workaround

6459540

The DAT72 internal tape drive might time out during tape operations.

The device might also be identified by the system as a QIC drive.

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

 

tape-config-list=

"SEAGATE DAT DAT72-000",

"SEAGATE_DAT____DAT72-000",

"SEAGATE_DAT____DAT72-000";

SEAGATE_DAT____DAT72-000=1,0x34,0,0x9639,4,0x00,0x8c,0x8c,

0x8c,3;

 

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

6511374

Memory translation warning messages might appear during boot if memory banks were disabled due to excessive errors.

After the system is rebooted, the fmadm repair command can be used to prevent a recurrence of the problem on the next boot.

6522017

Domains using the ZFS file system cannot use DR.

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

6531036

The error message network initialization failed appears repeatedly after a boot net installation.

There is no workaround.

6533686

When XSCF is low on system resources, DR deleteboard or moveboard operations that relocate permanent memory might fail with one or more of these errors:

SCF busy 
DR parallel copy timeout

This applies only to Quad-XSB configured System Boards hosting multiple domains.

Retry the DR operation at a later time.

6572827

On Sun SPARC Enterprise M4000/M5000 platforms, one of the columns in the IO Devices section of the output from prtdiag -v is "Type". This reports "PCIe", "PCIx", "PCI" or "UNKN" for each device. The algorithm used to compute this value is incorrect. It reports "PCI" for PCI-X leaf devices and "UNKN" for legacy PCI devices.

There is no workaround.

6588555

Resetting the XSCF during a DR operation on permanent memory might cause domain panic.

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

6589833

The DR addboard command might cause a system hang if you are adding a Sun StorageTek Enterprise Class 4Gb Dual-Port Fibre Channel PCI-E HBA card (SG-XPCIE2FC-QF4) at the same time that an SAP process is attempting to access storage devices attached to this card. The chance of a system hang is increased if the following cards are used for heavy network traffic:

  • X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
  • X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

There is no workaround.

6592302

Unsuccessful DR operation leaves memory partially configured.

It might be possible to recover by adding the board back to the domain with an addboard -d command.

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.

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

6614737

The DR deleteboard(8) and moveboard(8) operations might hang if any of the following conditions exist:

A DIMM has been degraded.

The domain contains system boards with different memory size.

Avoid performing DR operations if any of the following conditions exist:

  • Degraded memory - To determine whether the system contains degraded memory, use the XSCF command showstatus. For sample output see Identifying Degraded Memory in a System.
  • Differing memory sizes - To determine whether the domain contains system boards with different memory sizes, display the list of memory sizes using the XSCF command showdevices or the prtdiag command on the domain. For sample output, see Identifying Different Memory Sizes in a System Board.

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

6619344

The Sun Crypto Accelerator (SCA) 6000 card might not work if hot-plug configured into slot 1.

To avoid the defect, do not hot-plug this card in slot 1.

6625734

Systems with large number of processors in a single domain environment might have suboptimal performance with certain workloads.

Use processor sets to bind application processes or LWPs to groups of processors. Refer to the psrset(1M) man page for more information.

6623226

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

Do not use the Solaris lockstat(1M) command or the dtrace lockstat provider.

6632549

fmd service on domain might fail to maintenance mode after DR operations.

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

# svcadm clear fmd

6660168

If a ubc.piowbeue-cpu error occurs on a domain, the Solaris Fault Management cpumem-diagnosis module might fail, causing an interruption in FMA service.

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

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

# svcadm clear fmd 

Then restart cpumem-diagnosis:

# fmadm restart cpumem-diagnosis

 

SUNW-MSG-ID: FMD-8000-2K, TYPE: 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. 

6660197

DR might cause the domain to hang if more than 256 memory errors are detected.

Follow these steps:

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

set drmach:drmach_disable_mcopy=1 

2. Reboot the domain.

6663570

DR operations involving the lowest number CPU might cause the domain to panic.

Do not use DR to remove the system board that hosts the CPU with the lowest CPU ID. Use the Solaris prtdiag command to identify the CPU with the lowest CPU ID.

6668237

After DIMMs are replaced, the corresponding DIMM faults are not cleared on the domain.

Use the command fmadm repair fmri|uuid to record the repair. Then you can use the command fmadm rotate to clear out any leftover events.

6718173

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

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

set heaplp_use_stlb=0

Then reboot the domain.


Solaris Issues Fixed in Solaris 10 5/08

TABLE 6 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 6 Solaris OS Issues and Workarounds Fixed in Solaris 10 5/08

CR ID

Description

Workaround

6348554

Using the cfgadm -c disconnect command on the following cards might hang the command:

  • SG-XPCIE2FC-QF4 Sun StorageTek Enterprise Class 4Gb Dual-Port Fibre Channel PCI-E HBA
  • SG-XPCIE1FC-QF4 Sun StorageTek Enterprise Class 4Gb Single-Port Fibre Channel PCI-E HBA
  • SG-XPCI2FC-QF4 Sun StorageTek Enterprise Class 4Gb Dual-Port Fibre Channel PCI-X HBA
  • SG-XPCI1FC-QF4 Sun StorageTek Enterprise Class 4Gb Single-Port Fibre Channel PCI-X HBA

Do not perform cfgadm -c disconnect operation on the affected cards.

6472153

If you create a Solaris Flash archive on a non-Sun SPARC Enterprise M4000/M5000 sun4u server and install it on a Sun 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.

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

# sttydefs -r console
# sttydefs -a console -i "9600 hupcl opost onlcr crtscts" -f "9600"

 

This procedure is required only once.

6522433

The incorrect motherboard might be identified by fmdump for cpu faults after reboot.

None at this time.

6527811

The showhardconf(8) command on the XSCF cannot display PCI card information that is installed in the External I/O Expansion Unit, if the External I/O Expansion Unit is configured using PCI hot-plug.

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

6545143

There is a low probability that a system panic can occur during trap processing of a TLB miss for a user stack address. The problem can occur if the user stack is unmapped concurrently with the user process executing a flush windows trap (ta 3). The panic message will contain the following string:

bad kernel MMU trap at TL 2

There is no workaround.

 

6545685

If the system has detected Correctable MemoryErrors (CE) at power-on self-test (POST), the domains might incorrectly degrade 4 or 8 DIMMs.

Increase the memory patrol timeout values used via the following setting in /etc/system and reboot the system:

set mc-opl:mc_max_rewrite_loop = 20000

6546188

The system panics when running hot-plug (cfgadm) and DR operations (addboard and deleteboard)on the following cards:

  • X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
  • X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

There is no workaround.

6551356

The system panics when running hot-plug (cfgadm) to configure a previously 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
  • X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

Note - Do not use cfgadm -c unconfigure to disconnect the I/O card. Use cfgadm -c disconnect to completely remove the card. After waiting at least 10 seconds, the card might be configured back into the domain using the cfgadm -c configure command.

6556742

The system panics when DiskSuite cannot read the metadb during DR. This bug affects the following cards:

  • SG-XPCIE2FC-QF4, 4Gb PCI-e Dual-Port Fibre Channel HBA
  • SG-XPCIE1FC-QF4, 4Gb PCI-e Single-Port Fibre Channel HBA
  • SG-XPCI2FC-QF4, 4Gb PCI-X Dual-Port Fibre Channel HBA
  • SG-XPCI1FC-QF4, 4Gb PCI-X Single-Port Fibre Channel HBA

Panic can be avoided when a duplicated copy of the metadb is accessible via another Host Bus Adaptor.

6559504

Messages of the form nxge: NOTICE: nxge_ipp_eccue_valid_check: rd_ptr = nnn wr_ptr = nnn will be observed on the console with the following cards:

  • X4447A-Z, PCI-e Quad-port Gigabit Ethernet Adapter UTP
  • X1027A-Z1, PCI-e Dual 10 Gigabit Ethernet Fiber XFP Low profile Adapter

These messages can be safely ignored.

6563785

Hot-plug operation with the following cards might fail if a card is disconnected and then immediately reconnected:

  • SG-XPCIE2SCSIU320Z Sun StorageTek PCI-E Dual-Port Ultra320 SCSI HBA
  • SGXPCI2SCSILM320-Z Sun StorageTek PCI Dual-Port Ultra320 SCSI HBA

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

6564934

Performing a DR deleteboard operation on a board which includes Permanent Memory 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

Reconfigure 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 operation, the system panics when the 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

Add the following line to /etc/system and reboot the system:

 

set ip:ip_soft_rings_cnt=0 

6571370

Use of the following cards have been observed to cause data corruption in stress test under 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

Add the following line in /etc/system and reboot the system:

set nxge:nxge_rx_threshold_hi=0

6589546

prtdiag does not show all IO devices of the following cards:

  • SG-XPCIE2FC-EM4 Sun StorageTek Enterprise Class 4Gb Dual-Port Fibre Channel PCI-E HBA
  • SG-XPCIE1FC-EM4 Sun StorageTek Enterprise Class 4Gb Single-Port Fibre Channel PCI-E HBA

Use prtdiag -v for full output.


Solaris Issues Fixed in Solaris 10 8/07

TABLE 7 lists issues that have been fixed in Solaris 10 8/07 OS. You might encounter them in Solaris 10 11/06.



caution icon Caution - If you are running a version of Solaris earlier than Solaris 10 8/07, the system might panic or trap during a normal operation. For further information, see CR ID 6534471 in TABLE 7.


 
TABLE 7 Solaris OS Issues and Workarounds Fixed in Solaris 10 8/07

CR ID

Description

Workaround

6495303

The use of a PCIe Dual-Port Ultra320 SCSI controller card (SG-(X)PCIE2SCSIU320Z) in IOU Slot 1 on a Sun SPARC Enterprise M4000/M5000 server might result in a system panic.

Do not use this card in IOU Slot 1.

 

6498283

Using the DR deleteboard command while psradm operations are running on a domain might cause a system panic.

There is no workaround.

6508432

A large number of spurious PCIe correctable errors can be recorded in the FMA error log.

To mask these errors, add the following entry to /etc/system and reboot the system:

set pcie:pcie_aer_ce_mask = 0x2001

6510861

When using the PCIe Dual-Port Ultra320 SCSI controller card (SG-(X)PCIE2SCSIU320Z), a PCIe correctable error causes a Solaris panic.

Add the following entry to /etc/system to prevent the problem:

set pcie:pcie_aer_ce_mask = 0x31c1

6520990

When a domain reboots, SCF might not be able to service other domains that share the same physical board. DR operation can exceed the default timeout period and panic can occur.

Increase the DR timeout period by setting the following statement in /etc/system and reboot your system.:

set drmach:fmem_timeout = 30

6530178

DR addboard command can hang. Once the problem is observed, further DR operations are blocked. Recovery requires reboot of the domain.

There is no workaround.

6534471

Systems might panic/trap during normal operation.

Make sure you have the correct /etc/system parameter and reboot the system:

set heaplp_use_stlb=0 

6539084

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.

A fix is available in patch 125670-01.

 

6539909

Do not use the following I/O cards for network access when you are using the boot net install 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

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

 


Sun Management Center Software Issues and Workarounds

TABLE 8 lists issues and possible workarounds for Sun Management Center software.


TABLE 8 Sun Management Center Issues and Workarounds

CR ID

Description

Workaround

6654948

When viewing the PlatAdmin System Components table, you might experience a delay of about 26 minutes before an alarm is displayed. There is no actual error, just a delay.

There is no workaround.



Software Documentation Updates

This section contains late-breaking information on the software documentation that became known after the documentation set was published.


TABLE 9 Software Documentation Updates

Document

Page Number

Change

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

 

The glossaries included in each of the documents supporting SPARC Enterprise M4000/M5000/M8000/M9000 servers have been removed from those documents. In their place, a separate document has been created, the SPARC Enterprise M4000/M5000/M8000/M9000 Servers Glossary.

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

Page 9-6

Section 9.2.2, “Supported Browsers.” Refer to TABLE 2 for the correct list of web browsers supported by the XSCF Web.

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

Page 2-2

Section 2.1.1, “Setup Summary by the XSCF Shell.” Add the following note:

Note - In addition to the standard default login, Sun SPARC Enterprise M4000/M5000/M8000/M9000 servers are delivered with a temporary login called admin to enable remote initial login, through a serial port. Its privileges are fixed to useradm and cannot be changed. You cannot log in as temporary admin using the standard UNIX user name and password authentication or SSH public key authentication. It has no password, and one cannot be added for it.

 

The temporary admin account is disabled after someone logs in as the default user, or after someone logged in as temporary admin has successfully added the first user with valid password and privileges.

 

If, before the default login is used, you cannot log in as temporary admin, you can determine if someone else has done so by executing the following command:

showuser -l

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

Page 8

“Logging in to the System” section. Add the following note:

Note - In addition to the standard default login, Sun SPARC Enterprise M4000/M5000/M8000/M9000 servers are delivered with a temporary login called admin to enable remote initial login, through a serial port. Its privileges are fixed to useradm and cannot be changed. You cannot log in as temporary admin using the standard UNIX user name and password authentication or SSH public key authentication. It has no password, and one cannot be added for it.

 

The temporary admin account is disabled after someone logs in as the default user, or after someone logged in as temporary admin has successfully added the first user with valid password and privileges.

 

If, before the default login is used, you cannot log in as temporary admin, you can determine if someone else has done so by executing the following command:

showuser -l

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

Page 70

“About Auditing” section. Add the following note at the end of the “Audit File Tools” section:

Note - This chapter describes how to set up archived log files. The SP Security (SUNWspec) Package gives administrators and service providers a means to view those files. To display the XSCF audit log files archived to your server, use the viewauditapp(8) and mergeaudit(8) off-platform audit file viewers.

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

adduser(8) man page

The maximum length of the user name is 31 characters. The adduser(8) man page erroneously documents a maximum user name length of 32 characters.

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

sendbreak(8) man page

The sendbreak(8) command will not work when the domain mode is set to on while the mode switch on the operator panel is set to locked. Refer to the setdomainmode(8) man page for more information.

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

viewaudit(8) man page

The viewaudit(8) man pages show incorrect output for Example 5 and Example 6.



Additional Software Procedures

This section contains instructions for accomplishing some of the workarounds mentioned earlier in this document.

Booting From a WAN Boot Server

The WAN boot installation method enables you to boot and install software over a wide area network (WAN) by using HTTP. To support booting the Sun SPARC Enterprise M4000/M5000 server from a WAN boot server, you must have the appropriate wanboot executable installed to provide the needed hardware support.

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

http://docs.sun.com/app/docs/prod/solaris.10

If you do not upgrade the wanboot executable, the Sun SPARC Enterprise M4000/M5000 server will panic, with messages similar to the following:


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

Identifying Degraded Memory in a System


procedure icon  To Identify Degraded Memory in a System

single-step bullet  Log in to XSCF and type the following command:


XSCF> showstatus

The following example identifies 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.:


procedure icon  To Use the showdevices Command

single-step bullet  Log in to XSCF and type 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   65536    2402  0x0000000000000000  131072
00  01-0   16384       0  0x000003c000000000  131072
00  01-1   16384       0  0x0000038000000000  131072
00  01-2   16384       0  0x0000034000000000  131072
00  01-3   16384       0  0x0000030000000000  131072
 
...

This example shows that 00-0 has 64 Gbytes of memory, while the other system boards have 16 Gbytes.


procedure icon  To Use the prtdiag Command to Identify Memory Size

single-step bullet  On the domain, execute the prtdiag command.


# prtdiag

The following example shows a display of the prtdiag command.


# prtdiag
 
...
 
============================ Memory Configuration ============================
 
Memory  Available           Memory     DIMM    # of  Mirror Interleave
LSB    Group   Size                Status     Size    DIMMs Mode Factor
---    ------  ------------------  -------    ------  ----- ------- ----------
 00    A        32768MB            okay       2048MB     16 no       8-way
 00    B        32768MB            okay       2048MB     16 no       8-way
 01    A         8192MB            okay       2048MB      4 no       2-way
 01    B         8192MB            okay       2048MB      4 no       2-way
 02    A         8192MB            okay       2048MB      4 no       2-way
 02    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
 04    A         8192MB            okay       2048MB      4 no       2-way
 04    B         8192MB            okay       2048MB      4 no       2-way
 
...

This example displays varying memory sizes.

Identifying Permanent Memory in a Target Board


procedure icon  To Identify Permanent Memory in a Target Board

single-step bullet  Log in to XSCF and type 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   65536    2402  0x0000000000000000  131072
00  01-0   16384       0  0x000003c000000000  131072
00  01-1   16384       0  0x0000038000000000  131072
00  01-2   16384       0  0x0000034000000000  131072
00  01-3   16384       0  0x0000030000000000  131072
 
...

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

The example shows permanent memory on 00-0, with 2402 Mbytes.

If the board includes permanent memory, when you execute the deleteboard command or the moveboard command, the following notice is displayed:


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


Adding SPARC64 VII Processors to Your Server -- Service Representatives Only



Note - You must be an authorized service representative to install SPARC64 VII processors in your server.


This section describes procedures for installing SPARC64 VII processors in SPARC Enterprise M4000/M5000 servers:



Note - Before upgrading firmware to XCP 1071, refer to Upgrading to XCP 1071.




caution icon Caution - You must complete the upgrades to the XCP firmware and to Solaris before inserting SPARC 64 VII processors into the chassis.


For more information about configuring combinations of processors in domains, refer Section 2.2.13, “Domain Mode Configuration,” in the Sun SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide. In particular, see the section “SPARC64 VI and SPARC64 VII Processors and CPU Operational Modes.”


procedure icon  To Add a New SPARC64 VII CPU Module as a New Domain



Note - If you want to install Solaris 10 8/07 on the new domain, you must install from a patched image on the installation server. (See Step 20.)


1. Log in to the XSCF using an account with platadm privileges.

2. Use the showstatus(8) command to confirm that no FRU is currently listed in Faulted or Deconfigured status.


XSCF> showstatus 
No failures found in System Initialization.

3. Turn off the power to all domains.


XSCF> poweroff -a 

4. Confirm that all domains have stopped.


XSCF> showlogs power

5. Change the key position on the operator panel from Locked to Service.

6. Collect an XSCF snapshot to archive system status prior to upgrade.

If a problem should occur during the upgrade procedure, a snapshot of the system status might be helpful.


XSCF> snapshot -t user@host:directory 

7. Update the XCP version to 1071.

Before updating firmware to XCP 1071, refer to Upgrading to XCP 1071. For instructions for updating the firmware, refer to the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

8. Install the CPU module (CPUM) in the server.

For instructions, refer to Chapter 12, “CPU Module Replacement,” in the SPARC Enterprise M4000/M5000 Servers Service Manual. Note that this procedure involves powering down the entire server.



caution icon Caution - After installing the CPU module, you must reconnect the power cable to the power supply.


9. Log in to the XSCF again, using an account with platadm or fieldeng privileges.

10. Using the testsb(8) command, perform an initial diagnosis of the newly installed CPU module.

The following example shows a test after adding PSB#01 to a SPARC Enterprise M5000 server:


XSCF> testsb 01 
Initial diagnosis is about to start. Continue? [y|n] : y
Initial diagnosis is executing.
Initial diagnosis has completed.
XSB Test Fault
---- ------- --------
01 Passed Normal

11. Use the showhardconf(8) command to confirm that the installed CPU module is recognized by the server and that the error indicator asterisk (*) is not displayed.


XSCF> showhardconf -M 

12. Use the showlogs(8) and showstatus(8) commands to confirm that no abnormality has occurred.


XSCF> showlogs error -v 
XSCF> showstatus 

13. Change the key position on the operator panel from Service to Locked.

14. Power on the existing domains.


XSCF> poweron -a 

15. Set the following for the added CPU module:

Refer to Chapter 2, “Setting Up XSCF,” in the the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for information about these settings.

16. Use the setdomainmode(8) command to disable the autoboot function of the domain.

Refer to the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide and the setdomainmode(8) man page for more information.

17. Power on the new domain.


XSCF> poweron -d domain_id 

18. Confirm that the target domain has been correctly started.


XSCF> showlogs power 

19. Use the showlogs(8)and showstatus(8) commands to confirm that no abnormality has occurred.


XSCF> showlogs error -v 
XSCF> showstatus 

20. Install a version of Solaris OS that supports SPARC64 VII processors.

Refer to Supported Firmware and Software Versions for information about supported software versions.

If you are installing Solaris 10 8/07 on the new domain, you must install from a patched image on the installation server. For information about patches required to run Solaris 10 8/07 with SPARC64 VII processors, refer to Required Patches for Solaris 10 8/07 with SPARC64 VII CPUs. For information about network-based installations, refer to Solaris 10 8/07 Installation Guide: Network-Based Installations (part 820-0177).

21. Use the setdomainmode(8) command to enable the autoboot function of the domain.

The autoboot function is applied by a domain reboot. For more information, refer to the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide and the setdomainmode(8) man page.

Adding SPARC64 VII Processors to an Existing Domain

If you are adding SPARC64 VII processors to an existing domain, you must follow the following steps:

1. To Prepare to Add SPARC64 VII Processors to an Existing Domain

2. Choose one of the following procedures, depending on your installation goal:


procedure icon  To Prepare to Add SPARC64 VII Processors to an Existing Domain

1. If necessary, upgrade to a version of Solaris OS that supports SPARC64 VII processors.

Refer to Supported Firmware and Software Versions for information about supported software versions. Apply any required patches.

2. Log in to the XSCF using an account with platadm privileges.

3. Use the showstatus(8) command to confirm that no FRU is currently listed in Faulted or Deconfigured status.


XSCF> showstatus 
No failures found in System Initialization.

4. Turn off the power for all the domains.


XSCF> poweroff -a 

5. Confirm that the power is off for the domains.


XSCF> showlogs power 

6. Change the key position on the operator panel from Locked to Service.

7. Collect an XSCF snapshot to archive system status prior to upgrade.

If a problem should occur during the upgrade procedure, a snapshot of the system status might be helpful.


XSCF> snapshot -t user@host:directory 

8. Update the XCP version to 1071.

Before updating firmware to XCP 1071, refer to Upgrading to XCP 1071. For instructions for updating the firmware, refer to the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

9. Log in to the XSCF again, using an account with platadm or fieldeng privileges.

10. Power on all the domains, and apply OpenBoot PROM firmware.


XSCF> poweron -a 

The ok prompt is displayed. You do not need to start the Solaris OS.

11. Using the version command, check the updated OpenBoot PROM version.

For XCP 1071, the version of OpenBoot PROM is 02.03.0000. Your output should look similar to the following:


XSCF> version -c cmu -v 
 
DomainID 00 : 02.02.0000
DomainID 01 : 02.02.0000
DomainID 02 : 02.03.0000
DomainID 03 : 02.03.0000
...
DomainID 15 : 02.02.0000
 
XSB#00-0 : 02.02.0000 (Current), 01.01.0000 (Reserve)
XSB#00-1 : 02.02.0000 (Current), 01.01.0000 (Reserve)
XSB#00-2 : 02.02.0000 (Current), 01.01.0000 (Reserve)
XSB#00-3 : 02.02.0000 (Current), 02.01.0000 (Reserve)
XSB#01-0 : 02.02.0000 (Reserve), 02.03.0000 (Current)
XSB#01-1 : 02.02.0000 (Reserve), 02.03.0000 (Current)
XSB#01-2 : 02.02.0000 (Reserve), 02.03.0000 (Current)
XSB#01-3 : 02.02.0000 (Reserve), 02.03.0000 (Current)
...

12. Turn off the power to all the domains.


XSCF> poweroff -a 

13. Continue with the appropriate installation procedure:

a. If you are adding a new SPARC64 VII-equipped CPU module to a domain configured with SPARC64 VI processors, continue with To Add a New SPARC64 VII CPU Module to a Domain Configured With SPARC64 VI.

b. If you are upgrading an existing SPARC64 VI CPU module in an existing domain to SPARC64 VII processors, continue with To Upgrade a SPARC64 VI CPU Module to SPARC64 VII on an Existing Domain.


procedure icon  To Add a New SPARC64 VII CPU Module to a Domain Configured With SPARC64 VI

Use this procedure if you are adding a new CPUM containing SPARC64 VII processors to an existing domain that is already configured with SPARC64 processors.

1. Install the CPUM in the server.

For instructions, refer to Chapter 12, “CPU Module Replacement,” in the SPARC Enterprise M4000/M5000 Servers Service Manual. Note that this procedure involves powering down the entire server.



caution icon Caution - After installing the CPU module, you must reconnect the power cable to the power supply.


2. Log in to the XSCF again, using an account with platadm or fieldeng privileges.

3. Using the testsb(8) command, perform an initial diagnosis of the newly installed CPU module.

The following example shows a test after adding PSB#01 to a SPARC Enterprise M5000 server:


XSCF> testsb 01 
Initial diagnosis is about to start. Continue? [y|n] : y
Initial diagnosis is executing.
Initial diagnosis has completed.
XSB Test Fault
---- ------- --------
01 Passed Normal

4. Use the showhardconf(8) command to confirm that the installed CPU module is recognized by the server and that the error indicator asterisk (*) is not displayed.


XSCF> showhardconf -M 

5. Use the showlogs(8) and showstatus(8) commands to confirm that no abnormality has occurred.


XSCF> showlogs error -v 
XSCF> showstatus 

6. Change the key position on the operator panel from Service to Locked.

7. Set the following for the CPU module:

Refer to Chapter 2, “Setting Up XSCF,” in the the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for information about these settings.

8. Power on all the domains.


XSCF> poweron -a 

9. Confirm that all the domains have been correctly started.


XSCF> showlogs power 

10. Use the showlogs(8)and showstatus(8) commands to confirm that no abnormality has occurred.


XSCF> showlogs error -v 
XSCF> showstatus 


procedure icon  To Upgrade a SPARC64 VI CPU Module to SPARC64 VII on an Existing Domain

1. Replace the SPARC64 VI CPU module with the SPARC64 VII CPU module.

For instructions, refer to Chapter 12, “CPU Module Replacement,” in the SPARC Enterprise M4000/M5000 Servers Service Manual. Note that this procedure involves powering down the entire server.



caution icon Caution - After installing the CPU module, you must reconnect the power cable to the power supply.


2. Log in to the XSCF again, using an account with platadm or fieldeng privileges.

3. Using the testsb(8) command, perform an initial diagnosis of the newly installed CPU module.

The following example shows a test after adding PSB#01 to a SPARC Enterprise M5000 server:


XSCF> testsb 01 
Initial diagnosis is about to start. Continue? [y|n] : y
Initial diagnosis is executing.
Initial diagnosis has completed.
XSB Test Fault
---- ------- --------
01 Passed Normal

4. Use the showhardconf(8) command to confirm that the installed CPU module is recognized by the server and that the error indicator asterisk (*) is not displayed.


XSCF> showhardconf -M 

5. Use the showlogs(8)and showstatus(8) commands to confirm that no abnormality has occurred.


XSCF> showlogs error -v 
XSCF> showstatus 

6. Change the key position on the operator panel from Service to Locked.

7. Set up and confirm the CPU operational mode of the domain.

For more information, refer to Chapter 2, “Setting Up XSCF,” in the the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

8. Power on all the domains.


XSCF> poweron -a 

9. Confirm that the target domain has been correctly started.


XSCF> showlogs power 

10. Use the showlogs(8)and showstatus(8) commands to confirm that no abnormality has occurred.


XSCF> showlogs error -v 
XSCF> showstatus 


1 (TableFootnote) See Solaris Patch Information for information about patches.