Sun SPARC Enterprise M4000/M5000 Servers Product Notes for XCP 1090

C H A P T E R 1

This chapter contains the following sections:

What’s New in XCP 1090

Minimum Required Firmware, Operating Systems and Browsers

Solaris Patch Requirements

Upgrading to XCP 1090

Functionality Issues and Limitations

Additional Information and Procedures

What’s New in XCP 1090

Support for the new XSCF command showdateoffset(8).

For details, see the manual page online or in the reference manual.

The XCP 1090 firmware is the first XCP release to support the SPARC64 VII 2.53 GHz processor. Earlier XCP firmware releases do not support this faster version of the processor, which in other respects is functionally identical to all SPARC64 VII processors See Minimum Required Firmware, Operating Systems and Browsers.

Minimum Required Firmware, Operating Systems and Browsers

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

TABLE 1-1 lists the first firmware and operating system (OS) versions that are required for SPARC64 VI and SPARC64 VII processors..

TABLE 1-1 Minimum Required Firmware and Operating System Versions
Processor Type	Minimum XCP Version	Minimum Operating System Version
SPARC64 VI processors	XCP 1040	Solaris 10 11/06 - with patches ^[1] required Solaris 10 10/08 - with no patches required
SPARC64 VII processors, 2.4 GHz	XCP 1070	Solaris 10 8/07 - with patches* required Solaris 10 10/08 - with no patches required
SPARC64 VII processors, 2.4 GHz with 8GB DIMMs	XCP 1081	Solaris 10 8/07 - with patches* required Solaris 10 10/08 - with no patches required
SPARC64 VII processors, 2.53 GHz	XCP 1090	Solaris 10 8/07 - with the Solaris 10 10/09 Patch Bundle required Solaris 10 10/09 - with no patches required

Note - As for all releases, installation of the SunAlert Patch Cluster is recommended. Also, note that the Solaris 10 10/09 Patch Bundle is also known as MU8.

Many web browsers support the XSCF Web. The browsers in TABLE 1-2 have demonstrated compatibility with the XSCF Web through testing.

TABLE 1-2 Tested Web Browser Versions
Web Browser Application	Version
Firefox	2.0 and 3.0
Microsoft Internet Explorer	6.0, 7.0, and 8.0

Solaris Patch Requirements

This section lists mandatory patches, patch bundles, and SunAlert patch clusters for the M4000/M5000 servers. 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. Apply patches in the order listed.

Solaris 10 5/09 with SPARC64 VII 2.53 GHz Processors

The Solaris 10 10/09 Patch Bundle is required, and the SunAlert Patch Cluster is recommended. See:

http://sunsolve.sun.com/show.do?target=patches/patch-access

Solaris 10 10/08 with SPARC64 VII 2.53 GHz Processors

The Solaris 10 10/09 Patch Bundle is required, and and the SunAlert Patch Cluster is recommended. See:

http://sunsolve.sun.com/show.do?target=patches/patch-access

Solaris 10 5/08 with SPARC64 VII 2.53 GHz Processors

The Solaris 10 10/09 Patch Bundle is required, and and the SunAlert Patch Cluster is recommended. See:

http://sunsolve.sun.com/show.do?target=patches/patch-access

Solaris 10 5/08 with SPARC64 VII 2.4 GHz Processors, SPARC64 VI Processors, or Both

Patch 137137-09 - SunOS 5.10: kernel patch.

Solaris 10 8/07 with SPARC64 VII 2.53 GHz Processors

The Solaris 10 10/09 Patch Bundle is required and the SunAlert Patch Cluster is recommended. See:

http://sunsolve.sun.com/show.do?target=patches/patch-access

You cannot do a fresh install of the Solaris 10 8/07 OS on a domain that contains SPARC64 VII processors. The following two workarounds apply:

Create a fully patched image, then use Jumpstart.

Start the OS install on a domain that contains only SPARC64 VI processors, add the required patches, then add the SPARC64 VII processors to the domain.

Note - See http://sunsolve.sun.com/search/document.do?assetkey=1-62-252447-1

Solaris 10 8/07 with SPARC64 VII 2.4 GHz Processors

The following patches are required for Solaris 10 8/07 OS only on servers containing SPARC64 VII 2.4 GHz processors. Install them in the order 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

Solaris 10 8/07 OS with patch 127127-11 might panic/trap during normal domain operation. (CR 6720261) To prevent this you must set the following parameter in the system specification file (/etc/system):

set heaplp_use_stlb=0

Then reboot the domain.

You cannot do a fresh install of the Solaris 10 8/07 OS on a domain that contains SPARC64 VII processors. The following two workarounds apply:

Create a fully patched image, then use Jumpstart.

Start the OS install on a domain that contains only SPARC64 VI processors, add the required patches, then add the SPARC64 VII processors to the domain.

Solaris 10 8/07 with SPARC64 VI Processors

None.

Solaris 10 11/06

Caution - For Sun SPARC Enterprise M4000/M5000 servers running the Solaris 10 11/06 OS, patches 123003-03 and 124171-06 must be installed on your system prior to using Sun Connection Update Manager. These patches can be downloaded from http://sunsolve.sun.com.

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

Patches for Emulex PCI Express (PCIe) Cards

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

Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCIe HBA (part SG-XPCIE2FC-EM4)

Sun StorageTek Enterprise Class 4-Gigabit Single-Port Fiber Channel PCIe HBA (part SG-XPCIE1FC-EM4)

Patches for QLogic PCIe Cards

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

Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCIe HBA (part SG-XPCIE2FC-QF4)

Sun StorageTek Enterprise Class 4-Gigabit Single-Port Fiber Channel PCIe HBA (part SG-XPCIE1FC-QF4)

Obtaining Solaris Patches

The Sun^sm Connection Update Manager can be used to reinstall the patches if necessary or to update the system with the latest set of mandatory patches. For more information about the Sun Connection Update Manager, refer to the Sun Update Connection System Administration Guide at:

http://docs.sun.com/app/docs/prod/updconn.sys

Or visit:

http://wikis.sun.com/display/SunConnection/Update+Manager

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

There are two options available to register your system and to use the Sun Connection Update Manager to obtain the latest Solaris OS patches:

Use the Update Manager GUI to obtain patches.

For more information, refer to the Sun Update Connection documentation at the links mentioned previously.

Use the smpatch(1M) command to obtain patches.

For more information, refer to the smpatch(1M) man page or the reference manual collection for your version of the Solaris OS.

Upgrading and Downgrading XCP

Upgrading to XCP 1090

For information about upgrading your firmware, see the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

Note - After upgrading XCP firmware, use the rebootxscf(8) command to reset the XSCF.

Upgrading From a Version Earlier Than XCP 1050

If you are currently running a version earlier than XCP 1050, you cannot directly upgrade to XCP 1090. You must first upgrade to an interim version of XCP (between 1050 and 1070, inclusive). Contact your Oracle representative for access to older XCP releases.

Note - Use the deleteuser(8) command to delete any accounts named admin prior to updating to XCP 1050 or later. The admin account name is reserved starting in XCP 1050.

Domain Restart Required After Certain Type of XCP Upgrade

On a domain that has been in operation during the update to XCP 1090 from a version between XCP 1050 and 1070 (inclusive), when you perform dynamic reconfiguration (DR) to add or replace the SPARC64 VII processors, you need to update the OpenBoot PROM firmware. The OpenBoot PROM firmware is updated as you update the XCP and restart the domain. For this reason, restart all the domains after you update the firmware to the latest XCP release, regardless of whether you added or replaced the SPARC64 VII processors.

Downgrading XCP Firmware

Downgrading your XCP firmware to an earlier release is not advised. However, if you must downgrade your XCP 1090 release, execute the following command afterward to clear old-style audit logs:

XSCF> restoredefaults -c xscfu

Functionality Issues and Limitations

This section describes known issues in this release.

Limitations for SPARC64 VII Processors

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

General Functionality Issues and Limitations

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.

The following functions displaying the power consumption and exhaust air are not supported on M4000/M5000 servers:

The power and air operands of the showenvironment(8) command

XSCF Web

Note - Invalid values will be displayed by executing the commands or menu. SNMP Agent Function obtains invalid values for power consumption and exhaust air.

You cannot use the following user account names, as they are reserved for system use: adm, admin, apache, bin, daemon, default, ldap, nobody, ntp, operator, root, rpc, rpcuser, and sshd.

Do not use the Service Processor (SP) as the Network Time Protocol (NTP) server. Using an independent NTP server provides optimal reliability in maintaining consistent time on the SP and the domains. For more information about NTP, see the Sun BluePrints document, Using NTP to Control and Synchronize System Clocks: http://www.sun.com/blueprints/0701/NTP.pdf

When you use the external power control interface of the external power controller, the following notification signals are not supported:

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

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

When you import XCP or update the firmware using the XSCF you might see Web session ID errors displayed on the web browser. When you specify the timeout period as over 30 minutes in the Autologout setting Internal Server Errors might be displayed. To reconnect to the XSCF Web, close the current browser and open the new browser.

For this XCP release, the XSCF browser user interface (XSCF Web) does not support the External I/O Expansion Unit Manager feature.

Contact your sales representative for tape drive unit options on SPARC Enterprise M4000/M5000 servers.

Disable pop-up blocking and remove any plug-ins such as the search tool installed with the browser when you use the XSCF Web.

XSCF-LAN is compliant with auto-negotiation. Set the network device which connects with XSCF-LAN to the auto-negotiation mode. Otherwise when you connect the XSCF-LAN and the network device (fixed to the full-duplex mode, according to the IEEE 802.3 rule) the XSCF-LAN communicates in half-duplex mode and network communication speed might slow down or communication errors may occur.

Due to DR and ZFS file system interoperability issues, M4000/M5000 servers are shipped pre-installed using the UFS file system. See CR 6522017 in TABLE 3-2.

The M4000/M5000 servers are cold service machines. Hot-swapping of the CPU module (CPUM), memory board (MEMB), I/O unit (IOU), or XSCF unit is not supported.

For information about I/O options and storage, such as the number of cards supported in a domain, see the Sun Cross Platform IO Support page:

http://wikis.sun.com/display/PlatformIoSupport/Home/

The use of the External I/O Expansion Unit to connect the host server to an external boot disk drive is not supported.

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

Additional Information and Procedures

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

Logging In to the System

In addition to the standard default login, the servers are delivered with a temporary login called admin to enable remote initial login, through a serial port. The admin user 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. The temporary admin account 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 showuser -l command.

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 M4000/M5000 servers from a WAN boot server, you must have the appropriate wanboot executable installed and OpenBoot version 4.24 or above 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 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

Sun Java Enterprise System

The Sun Java trademark Enterprise System is a comprehensive set of software and life cycle services that make the most of your software investment. For an overview and documentation, go to:

http://www.sun.com/service/javaes/index.xml

Note - Due to an issue that arises from the installation of the Java Enterprise System 5 Update 1 on your system (CR 6644798), it might be necessary to enable the Web Console SMF service.

Enable the Web Console SMF Service

# svcadm enable svc:/system/webconsole:console

If you have to reload the software, go to the following web site for download and installation instructions:

http://www.sun.com/software/preinstall

If you download a fresh copy of software, that software might not include patches that are mandatory for your server. After installing the software, refer to Solaris Patch Requirements for information about checking for and installing required patches.

^{1 (TableFootnote) See Solaris Patch Requirements.

Check http://sunsolve.sun.com for the latest patch revision.}