Information About XCP 1100 Firmware

C H A P T E R 2

This chapter covers this XCP firmware release. Unless otherwise noted, the information here applies to all platforms in this series: the M3000/M4000/M5000/M8000/M9000 servers.

What’s New

This section also includes information about features or restrictions added in the current release.

The airflow indicator feature was supported on earlier releases of M3000 and M8000/M9000 servers. Beginning with the XCP 1100 release it also is supported on M4000/M5000 servers. Airflow monitoring measurement values are for reference only.

This release introduces support for the SPARC64 VII+ processor on M4000/M5000 and M8000/M9000 servers.

Note - SunVTS version 7.0ps10 is the first SunVTS release supported on servers with SPARC64 VII+ processors.

Upgrading and Downgrading XCP

Upgrading to XCP 1100

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 this XCP release. 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 an update to XCP 1100 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 1100 release, execute the following command afterward to clear old-style audit logs:

XSCF> restoredefaults -c xscfu

XCP Functionality Issues and Limitations

This section describes known XCP firmware issues.

Note - 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 Blueprint document, Using NTP to Control and Synchronize System Clocks: http://www.sun.com/blueprints/0701/NTP.pdf

TABLE 2-1 XCP Functionality Issues and Limitations
M3000	M4000/M5000	M8000/M9000	Issue
o	o	o	In the `settimezone -c adddst` command, when you set eight or more letters to the abbreviation of time zone and the name of Daylight Saving Time, execution of the `showlogs` command induces a segmentation fault and results in an error. [CR 6789066] Workaround: Specify the abbreviation of time zone and the name of Daylight Saving Time in seven letters or less.
o	o	o	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`, `proxyuser`, `root`, `rpc`, `rpcuser`, and `sshd`. See Remote Initial Login
o	o	o	An XSCF user account user name cannot match an LDAP user name, and an XSCF user account number (UID) cannot match an LDAP UID number.
o	o	o	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.
o	o	o	Before using the XSCF Web, disable pop-up blocking and remove any plug-ins such as the search tool installed with the browser.
o	o	o	XSCF-LAN is compliant with auto-negotiation. Set the network device that 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.
	o	o	For this XCP release, the XSCF browser user interface (XSCF Web) does not support the External I/O Expansion Unit Manager feature.
	o	o	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.
o	o	o	The XCP 1093 release was the first XCP release to support a domain running Oracle Solaris 10 9/10 with the processor groups observability feature enabled. Please refer to Oracle Solaris 10 9/10 Product Notes for more information.

XCP Known Issues (CRs) and Workarounds

This section lists significant CRs and, if available, suggested workarounds,

TABLE 2-2 XCP Known Issues (CRs) and Workarounds
CR ID	M3000	M4000/ M5000	M8000/ M9000	Description	Workaround
CR 6994665	o	o	o	Pressing Ctrl-Z can cause the XSCF shell terminal to stop working. If the XSCF is not accessible using a LAN connection, it will be not be possible to use the XSCF until the server is powered off and powered on.	Do not press Ctrl-Z when using the XSCF shell terminal. If pressing Ctrl-Z caused the terminal to stop working, reboot the XSCF using a XSCF LAN connection if available.