Sun SPARC Enterprise M3000 Servers Product Notes for XCP 1090

C H A P T E R 1

This chapter contains the following sections:

What’s New

Supported Firmware and Software Versions

Solaris Patch Information

Obtaining Solaris Patches

Upgrading to XCP 1090

Functionality Issues and Limitations

Additional Information and Procedures

What’s New

Support for the new XSCF command showdateoffset(8) is new in XCP 1090.

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

Airflow indicator support was added in XCP 1082.

For more information, see Airflow Indicator.

Power consumption monitoring was added in XCP 1081.

For more information, see Power Consumption Monitoring.

Airflow Indicator

The Airflow indicator confirms the amount of airflow emitted while the SPARC Enterprise M3000 server is up and running.

The Airflow indicator value indicates the volume of air exhausted from the server . The value does not include the peripheral devices.

To display the amount of exhaust air, use the showenvironment air command.

XSCF> showenvironment air
Estimated Air Flow:63CMH

Note - Airflow monitoring measurement values are for reference only.

For details of the showenvironment(8) command, refer to the man page. For installation details of the SPARC Enterprise M3000 server, see the SPARC Enterprise M3000 Server Site Planning Guide and the SPARC Enterprise M3000 Server Installation Guide.

You can also obtain the exhaust air data using the SNMP agent function. To obtain the data of exhaust air using the SNMP agent function, install the latest XSCF extension MIB definition file to the SNMP manager. For details on the XSCF extension MIB definition file, see the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

Power Consumption Monitoring

The power consumption monitoring function confirms the amount of power consumed while the SPARC Enterprise M3000 server is up and running.

To display the power consumption, use the showenvironment power command.

XSCF> showenvironment power
Permitted AC power consumption:470W
Actual AC power consumption:450W

For details of the showenvironment(8) command, see the man page. For installation details of the SPARC Enterprise M3000 server, see the SPARC Enterprise M3000 Server Site Planning Guide.

Note - Power consumption monitoring measurement values are for reference only. The power consumption value of the server varies by the conditions such as the power supply in use, CPU types, system configurations, or system load.

You can also obtain the power consumption data using the SNMP agent function. To obtain the power consumption data using the SNMP agent function, install the latest XSCF extension MIB definition file to the SNMP manager. For details on the XSCF extension MIB definition file, see the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

When there is a change in the power system, such as in the following occurrences, wait for one minute, then check the value again.

During the server power-on or power-off, or after the power-on or power-off is complete

During the active replacement of a power supply unit, or after the active replacement is complete

Supported Firmware and Software Versions

The Solaris Operating System and Sun Java trademark Enterprise System software are preinstalled on new SPARC Enterprise M3000s.

The following table lists the firmware and operating system (OS) versions that are supported in this release.

TABLE 1-1 Minimum Firmware and Operating System Versions for the M3000 Server
Firmware and Operating System	Version
XSCF Control Package (XCP) Airflow monitoring Power consumption monitoring	XCP 1082 XCP 1081
Solaris Operating System	Solaris 10 10/08 Solaris 10 5/08, with required patches ^[1]

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 and 7.0

Solaris Patch Information

This section lists mandatory patches for the M3000 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. For additional Solaris OS information see Solaris OS Issues and Workarounds.

Patches for Solaris 10 5/08

The following patches are required for all M3000 servers running Solaris 10 5/08. They should be installed in the order listed.

1. 119254-59 (patchadd patch) - Reboot the system before proceeding.

2. 138866-01 - Reboot into single user mode before proceeding.

3. 137137-09 (KU patch) - Reboot the system before proceeding.

4. 138504-04 SunVTS7.0PS3.

Patches for Emulex PCI Express (PCIe) Cards

The following Emulex cards require drivers supplied in patch 120222-27 or later:

XSEFC402AF Sun StorageTek Enterprise Class 4-Gigabit Dual-Port Fiber Channel PCIe HBA

XSEFC401AF Sun StorageTek Enterprise Class 4-Gigabit Single-Port Fiber Channel PCIeHBA

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

Upgrading to XCP 1090

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

Resetting the XSCF Firmware

After updating the XCP firmware, use the rebootxscf(8) command to reset the XSCF.

Functionality Issues and Limitations

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

Limitation for Power Consumption Monitoring Function

The amount of power consumption may not be indicated correctly in the MIB information, in the showenvironment power command output, and on the XSCF Web in the following cases; and you should wait for one minute and check the value again.

During the server powering on or powering off, or for a while after the power-on or power-off complete

During the active replacement of power supply unit, or for a while after the active replacement complete

General Functionality Issues and Limitations

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 information displayed about air flow volume pertains to the SPARC Enterprise servers only. Air flow volume for peripheral devices is not displayed.

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

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

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.

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.

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 M3000 server is 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.

XSCF Web Browser Issues

The XSCF Web browser interface occasionally truncates output. Some examples: When you selected SSH on the snapshot screen, the maximum number of character input for Host, Directory, ID, and Password doesn’t correspond to the maximum number of character input on the XSCF Shell. The Panic Log page only displays the last 50 lines of the panic message (CR 6756052). The browser interface displays only the last two digits of the non-audit log size limit (CR 6742502).

To see the full output use the XSCF Shell command-line interface (CLI).

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 M3000 server 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 software is a comprehensive set of software and life cycle services that make the most of your software investment. The software and installation instructions can be found at the following web address:

http://www.sun.com/software/javaenterprisesystem/index.jsp

The software might not include patches that are mandatory for your server. After installing the software, refer to Solaris Patch Information for information about checking for and installing required patches.

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 WebConsole SMF service.

Enable the Web Console SMF Service

# svcadm enable svc:/system/webconsole:console

Booting Multiple OPL Systems From a Single J4200 JBOD Storage Array

Sun Storage J4200 SAS JBOD arrays have six general-purpose SAS connectors. With FW version 3A32 or higher, each of them can be connected to separate SAS initiators, therefore up to six systems can be connected to the array. Each system can use a different disk on the array as its boot device. J4200 arrays have 12 disks, so each boot device can be mirrored for higher reliability.

J4200 SAS arrays can be configured into multiple zones to provide a more secure environment.

Related Information

Sun StorageTek Common Array Manager Software documentation, at: http://docs.sun.com/app/docs/prod/stor.arrmgr#hic
See especially:

Sun StorageTek Common Array Manager Software Release Notes 6.4.1

Sun StorageTek Common Array Manager User Guide for Open Systems

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

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