Sun SPARC Enterprise M4000/M5000 Servers Product Notes |
This document includes these sections:
In XCP Version 1071 SPARC64 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.
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.
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.
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 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.
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.
The following Emulex cards require drivers supplied in patch 120222-26:
The following QLogic cards require drivers supplied in patch 125166-10:
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.
8. 125127-01 - Reboot your domain before proceeding.
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.
To complete updating the OpenBoot 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.
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.
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. |
Then you must set the following parameter in the system specification file (/etc/system):
For more information, refer to CR 6718173 in TABLE 5.
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. |
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, 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.
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 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. |
||
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. |
||
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. |
|
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. |
|
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. |
||
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:
|
|
The Sun Crypto Accelerator (SCA) 6000 card might not work if hot-plug configured into slot 1. |
||
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. |
|
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. |
|
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: |
|
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. |
||
DR might cause the domain to hang if more than 256 memory errors are detected. |
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. |
|
If your domain is running one of the following versions of Solaris OS, the system might panic/trap during normal operation: |
Set the following parameter in the system specification file (/etc/system): set heaplp_use_stlb=0 |
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. |
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 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 |
Log in to XSCF and 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.:
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.
This 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 shows a display of the prtdiag command.
This example displays varying memory sizes.
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-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:
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 - 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.”
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.
3. Turn off the power to all domains.
4. Confirm that all domains have stopped.
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.
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 - 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.
12. Use the showlogs(8) and showstatus(8) commands to confirm that no abnormality has occurred.
13. Change the key position on the operator panel from Service to Locked.
14. Power on the existing domains.
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.
18. Confirm that the target domain has been correctly started.
19. Use the showlogs(8)and showstatus(8) commands to confirm that no abnormality has occurred.
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.
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:
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.
4. Turn off the power for all the domains.
5. Confirm that the power is off for the domains.
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.
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.
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:
12. Turn off the power to all the domains.
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.
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 - 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.
5. Use the showlogs(8) and showstatus(8) commands to confirm that no abnormality has occurred.
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.
9. Confirm that all the domains have been correctly started.
10. Use the showlogs(8)and showstatus(8) commands to confirm that no abnormality has occurred.
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 - 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.
5. Use the showlogs(8)and showstatus(8) commands to confirm that no abnormality has occurred.
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.
9. Confirm that the target domain has been correctly started.
10. Use the showlogs(8)and showstatus(8) commands to confirm that no abnormality has occurred.
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.