Sun SPARC Enterprise M8000/M9000 Servers Product Notes |
This document includes these sections:
In XCP Version 1070, the following new feature is introduced:
TABLE 1 lists the minimum required versions of some supported software and firmware for XCP 1070 on Sun SPARC® Enterprise M8000/M9000 servers.
Solaris 10 11/06, with required patches[1] |
TABLE 2 lists minimum supported versions of Web browsers for use with the XSCF Web.
If you plan to boot your Sun SPARC Enterprise M8000/M9000 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.
Currently, patches are required only for servers running Solaris 10 11/06 OS. The following patches are required:
These patch identifiers represent the minimum level of the patches that must be installed. The two-digit suffix represents the minimum revision level of the patch. Check SunSolve.Sun.COM for the latest patch revision, and see Latest Solaris Patches for information on how to find the latest patches.
Install the following patches in numerical order.
Always refer to the patch README for information about patch requirements and special installation instructions. For general installation instructions, refer to Latest Solaris Patches.
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
If you are upgrading to XCP 1070 from a version of XCP 1041 or lower, refer to Upgrading From XCP 1041 or Lower for important instructions.
If you are upgrading from a more recent version of XCP, refer to the Sun SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for instructions.
This section describes known hardware and software issues in this release.
![]() |
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. |
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:
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. |
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:
TABLE 4 lists XCP issues and possible 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.
TABLE 5 lists Solaris OS issues that you might encounter in any supported release of Solaris OS.
The Solaris cfgadm(1M) command does not unconfigure a DVD drive from a domain on a Sun SPARC Enterprise M8000/M9000 server. |
Disable the Volume Management Daemon (vold) before unconfiguring a DVD drive with the cfgadm(1M) command. To disable vold, stop the daemon by issuing the command /etc/init.d/volmgt stop. After the device has been removed or inserted, restart the daemon by issuing the command /etc/init.d/volmgt start. |
|
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: |
|
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. |
|
Set the maximum size of the ZFS ARC lower. For detailed assistance, contact your authorized service representative. |
||
The error message network initialization failed appears repeatedly after a boot net installation. |
||
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. |
||
In Solaris domains that include SPARC64 VII processors, workloads that make heavy use of the Solaris kernel might not scale as expected when you increase the thread count to a value greater than 256. |
For Solaris domains that include SPARC64 VII processors, limit domains to a maximum of 256 threads. |
|
Hot-plug operations on Sun Crypto Accelerator (SCA)6000 cards can cause Sun SPARC Enterprise M8000/M9000 servers to panic or hang. |
Version 1.0 of the SCA6000 driver does not support hot-plug and should not be attempted. Version 1.1 of the SCA6000 driver and firmware supports hot-plug operations after the required bootstrap firmware upgrade has been performed. |
|
On Sun SPARC Enterprise M8000/M9000 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. |
||
Permanent memory DR operation during XSCF failover might cause domain panic. |
Do not start an XSCF failover while a DR operation is running. Wait for a DR operation to finish before starting the failover. If you start the failover first, wait for the failover to finish before starting the DR operation. |
|
When XSCF switchover happens after the SB has been added using the addboard command, the console is no longer available. |
||
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: |
||
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. |
|
The DR deleteboard(8) and moveboard(8) operations might hang if any of the following conditions exist: The domain contains system boards with different memory size. |
Avoid performing DR operations if any of the following conditions exist:
|
|
For Solaris domains that include SPARC 64 VII processors, a single domain of 256 threads or more might hang for an extended period of time under certain unusual situations. Upon recovery, the uptime command will show extremely high load averages. |
For Solaris domains that include SPARC 64 VII processors, do not exceed a domain size of 256 virtual processors in a single Solaris domain. This means a maximum of 32 CPUs in a single domain configuration (maximum configuration for an M8000 server). |
|
The Solaris command lockstat(1M) might cause a system panic. |
||
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. |
|
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 fmdt |
|
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: |
svcadm clear fmd 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. |
||
DR might cause the domain to hang if either of the following conditions exist: |
1. Set the following parameter in the system specification file (/etc/system): set drmach:drmach_disable_mcopy=1 |
|
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. |
|
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. |
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 7 lists issues that have been fixed in Solaris 10 8/07 OS. You might encounter them in Solaris 10 11/06.
![]() |
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 8 lists issues and possible workarounds for Sun Management Center software.
This section contains late-breaking information on the software documentation that became known after the documentation set was published.
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 |
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 |
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: |
|
Sun SPARC Enterprise M4000/M5000/M8000/M9000 Servers Administration Guide |
“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: |
|
Sun SPARC Enterprise M4000/M5000/M8000/M9000 Servers Administration Guide |
“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 |
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 |
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 |
The viewaudit(8) man pages show incorrect output for Example 5 and Example 6. |
1. Delete any routes configured on the lan#0 and lan#1 interfaces (failover interfaces).
Note - The applynetwork -n command will not run unless some network configuration has changed. Reseting the host name (sethostname) to exactly what it is will prompt the command to run. |
The following example shows two routes that must be deleted.
XCP 1050 or later supports dual XSCF configuration. The Inter-SCF Network provides an internal communication link between the two XSCF Units (active and standby).
If you do not explicitly set the IP addresses on the ISN network, XCP will use the following default values:
In case the IP address of XSCF-LAN or DSCP conflicts with the default subnet address of ISN, it is necessary to specify the IP address of ISN. The following is an example.
XSCF>setnetwork xscf#0-if -m 255.255.255.0 192.168.12.11 XSCF>setnetwork xscf#1-if -m 255.255.255.0 192.168.12.12 XSCF>applynetwork |
3. Delete any accounts named admin.
Use the showuser -lu command to list all XSCF accounts. Any accounts named admin must be deleted prior to upgrading to XCP 1070. The admin account name is reserved. Use the deleteuser command to delete the account.
Note - For more information on admin accounts, see TABLE 9, Software Documentation Updates. |
Note - Do not access the XSCF units via the “Takeover IP address.” |
Note - LAN connections are disconnected when the XSCF resets. Use the XSCF serial connection to simplify the XCP upgrade procedure. |
1. Log in to the XSCF#0 using an account with platform administrative privileges.
2. Verify that there are no faulted or deconfigured components by using the showstatus(8) command.
If any failures are listed, contact your authorized service representative before proceeding.
4. Confirm that all domains are stopped:
5. Move the key position on the operator panel from Locked to Service.
6. Collect an XSCF snapshot to archive the system status for future reference.
7. Upload the XCP 1070 upgrade image by using the command getflashimage(8).
The XSCF Web on XSCFU#0 can also be used to upload the XCP 1070 upgrade image. For more detailed information about using XSCF Web and the getflashimage(8) command, see the Sun SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.
8. Update the firmware by using the flashupdate(8) command.
Specify the XCP version to be updated. In this example, it is 1070.
![]() |
Caution - The flashupdatecommand will update one bank, reset the XSCF, and commence update of the second bank. Before proceeding to Step 9, you must verify that the current and reserve banks are both updated. If both banks indicate XCP revision 1070, proceed to the next step. |
9. Confirm completion of the update.
Confirm no abnormality happens while updating XCSF_B#0.
10. Confirm that both the current and reserve banks of XSCFU#0 display the updated XCP versions.
XSCF> version -c xcp XSCF#0 (Active ) XCP0 (Reserve): 1070 XCP1 (Current): 1070 XSCF#1 (Standby) XCP0 (Reserve): 0000 XCP1 (Current): 0000 |
If the Current and Reserve banks on XSCF#0 do not indicate XCP revision 1070, contact your authorized service representative.
11. Confirm the servicetag(8) facility is enabled.
a. Check the servicetag facility status by using the showservicetag(8) command.
b. If it is currently disabled, you must enable it.
c. Reboot the XSCF to enable the servicetag facility.
d. Wait until XSCF firmware reaches the ready state.
This can be confirmed when the READY LED of the XSCF remains lit, or the following message appears on the serial console:
12. Turn off all the server power switches for 30 seconds.
13. After 30 seconds, turn the power switches back on.
14. Wait until XSCF firmware reaches the ready state.
This can be confirmed when the READY LEDs of XSCF_B#0 and XSCF_B#1 remain lit.
15. Log on to XSCFU#0 using a serial connection or LAN connection.
16. Confirm no abnormality has occurred by using the showlogs error -v and showstatus commands.
Because XSCF#1 is not yet running XCP 1070, XSCF#0 is unable to communicate with XSCF#1. Therefore, it is normal that showstatus will show that XSCF#1 has faulted.
If you encounter any hardware abnormality of the XSCF contact your authorized service representative.
17. Confirm and update the imported XCP image again.
Specify the XCP version to be updated. In this example, it is 1070. XSCF#1 will be updated, and then XSCF#0 updated, again.
When the firmware update for XSCF#0 is complete, XSCF#1 is active.
18. Log in to XSCFU#1 using a serial connection or LAN connection.
19. Confirm completion of the update by using the showlogs event command.
Confirm no abnormality is found during the update.
20. Confirm that both the current and reserve banks of XSCFU#0 display the updated XCP versions.
XSCF> version -c xcp XSCF#1 (Active ) XCP0 (Reserve): 1070 XCP1 (Current): 1070 XSCF#0 (Standby) XCP0 (Reserve): 1070 XCP1 (Current): 1070 |
If the Current and Reserve banks on XSCF#0 do not indicate XCP revision 1070, contact your authorized service representative.
21. Confirm that switching over between XSCF units works properly.
a. Switch between the Active and Standby states:
XSCF> switchscf -t Standby The XSCF unit switch between the Active and Standby states. Continue? [y|n] :y |
b. When the READY LED on XSCFU_B#1 remains lit, log in to XSCFU#0 using a serial connection or LAN connection.
c. Confirm XSCF#1 is now the standby, and that XSCF#0 has become the active unit:
d. Confirm no new errors have been recorded since the check in Step 16:
e. Confirm that XSCF#1 has entered the active state:
f. Confirm that no failures are found in system initialization:
23. Log in to XSCFU#0 and confirm all domains start up properly.
24. Check that there are no new errors.
25. Move position of the key switch on the operator panel from Service to Lock.
This section contains instructions for accomplishing some of the workarounds mentioned earlier in this document.
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 M8000/M9000 server from a WAN boot server, you must have the appropriate wanboot executable installed to provide the needed hardware support. If you have added SPARC64 VII processors to your server, for example, you must perform this procedure even if you have performed it previously, before the new processors were added.
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
1. Install the Solaris 10 OS on the WAN boot server.
Install the version of Solaris 10 OS that is required for your server. For information about minimum software requirements, refer to Supported Firmware and Software Versions.
2. Copy the wanboot executable from that Solaris release to the appropriate location on the install server.
For more detailed information, refer to the Solaris 10 Installation Guide: Network-Based Installations. For Solaris 10 8/07, for example, the information in the English document is here:
http://docs.sun.com/app/docs/doc/820-0177/6nbuennmi?a=view
3. Create a WAN boot miniroot from the Solaris 10 OS.
For Solaris 10 8/07, for example, the information in the English document is here:
http://docs.sun.com/app/docs/doc/820-0177/eypqx?a=view
If you do not upgrade the wanboot executable, the Sun SPARC Enterprise M8000/M9000 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 |
Log in to XSCF anf type the following command:
The following example identifies DIMM number 0A on Memory Board #5 has degraded memory.
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.:
1. Log in to XSCF and type the following command:
The following example shows that 00-0 has 64 Gbytes of memory while the other system boards have 16 Gbytes.
On the domain, execute the prtdiag command.
The following example displays different memory sizes.
1. Log in to XSCF and type the following command:
The following example shows a display of the showdevices -d command where 0 is the domain_id.
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-2, with 1674 Mbytes.
If the board includes permanent memory, when you execute the deleteboard command or the moveboard command, the following notice is displayed:
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.