General Information About XCP 1081

Power consumption monitoring makes it possible to routinely measure the amount of power consumed while the SPARC Enterprise M3000 server is up and running. The measured power consumption data can be utilized in grasping the current status of or in redesigning the power facilities of the installation site.

To display the power consumption, use the showenvironment power XSCF command. You can also obtain the power consumption data using the SNMP agent function.

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

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

Note - To optimize the power facilities of the computer room or of the office, it is necessary to measure the power consumption of the SPARC Enterprise M3000 server for a certain period of time. If you plan the installation in the computer room or in the office, please contact a certified service engineer.

Supported Firmware and Software Versions

TABLE 1 lists the firmware and operating system (OS) versions that are supported in this release.

TABLE 1 Minimum Firmware and Operating System Versions for the M3000 Server
Firmware and Operating System	Version
XSCF Control Package (XCP)	XCP 1081
Solaris Operating System	Solaris 10 10/08 Solaris 10 10/05, with required patches ^[1]

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

TABLE 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 10/08

Patches are not required for servers running Solaris 10 10/08 OS or later.

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

Solaris 10 5/08 OS 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.

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

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

Using the Update Manager GUI to Obtain Patches

Using the smpatch CLI to Obtain Patches

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

Using the Update Manager GUI to Obtain Patches

1. As root, launch the Update Manager from either of the following:

From JDS Launch menu:

Click Launch->Applications->System Tools->Update Manager

From a terminal window:

Type /usr/bin/updatemanager

2. Complete the registration.

If you have already registered, proceed to Step 3.

If you have not yet registered, the Update Manager interface guides you through the registration process. Follow the onscreen instructions.

Note - If you are unable to complete registration using the Sun Connection Update Manager GUI, use the command-line interface (CLI) option to obtain patches. See Using the smpatch CLI to Obtain Patches.

3. In the Available tab in the Update Manager, open the Update Collection drop-down menu and select Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers.

Update Manager analyzes your system for any patches that are needed.

4. If a kernel patch is recommended, select it by clicking the box to the left of the patch ID, then click the Install button.

The patch is downloaded to /var/sadm/spool.

Note - Kernel patches (such as patch 118833-xx, for example) require special instructions for installation (see the patch README for specifics). They are often download-only (interactive) patches, requiring manual installation. You must install kernel patches before any others in order for any remaining patches in the patch set to be installed.

5. For a kernel patch, continue by typing:

# cd /var/sadm/spool

# unzip patchid-xx.jar

6. Follow the installation instructions in the file
/var/sadm/spool/patchid-xx/README.patchid-xx.

7. After installing patchid-xx, restart the system with the shutdown command.

Using the reboot command does not complete installations of patches that require a restart. You must use the Update Manager or the shutdown command.

# shutdown -i6

8. Launch the Update Manager again, and select the collection, as in Step 3.

9. If the Update Manager does not automatically start a new analysis, click the Check for Updates button.

10. Select any patches that are listed by checking the boxes to the left of the patch IDs.

11. Click the Install button.

Update Manager downloads and installs the patches.

12. If any of the patches require a system restart, follow the instructions in Step 7.

If any patches are installed that require restart, Update Manager offers to restart the system. Alternatively, you can use the shutdown command, as described in Step 7. For patches that require restart, you must perform the restart in order for the installation to take effect.

The patch installation is now complete.

Using the `smpatch` CLI to Obtain Patches

1. Copy the file /usr/lib/breg/data/RegistrationProfile.properties to your /tmp directory.

2. Edit the file /tmp/RegistrationProfile.properties to add your user name, password, network proxy (if necessary), and port (if required).

Note - The user name and password is a Sun Online Account. To create an account, go to http://sunsolve.sun.com.

3. Register your system.

# sconadm register -a -r /tmp/RegistrationProfile.properties

4. Obtain the correct patches.

# smpatch set patchpro.patchset=sem3k4k5k8k9k

5. Install any kernel patches.

Kernel patches, such as 118833-xx, can be downloaded through the Sun Connection Update Manager.

a. Download the patch to your /var/sadm/spool directory.

# smpatch update -i patchid-xx

b. Unzip the patch.

# cd /var/sadm/spool

# unzip patchid-xx.jar

c. Install the patch by following the installation instructions in the file: /var/sadm/spool/patchid-xx/README.patchid-xx.

6. Restart the system

Using the reboot command does not complete installation of patches that require a restart. You must use the Update Manager or the shutdown command.

# shutdown -i6

7. Display a list of patches.

# smpatch analyse

8. Download and install the patches.

# smpatch update

9. If any of the patches requires a system restart, see Step 6.

If any patches are installed that require restart, Update Manager offers to restart the system. Alternatively, you can use the shutdown command, as described in Step 6. For patches that require restart, you must perform the restart in order for the installation to take effect.

The patch installation is now complete.

Upgrading to XCP 1081

You can upgrade to XCP 1081 from XCP version 1080. Refer to the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for instructions.

Resetting the XSCF Firmware

After updating the XCP firmware to 1081 or later use the rebootxscf(8) command to reset the XSCF.

Updating the OpenBoot PROM Firmware

To complete updating the OpenBoot trademark 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.

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.

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 Into 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 server’s 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.

Enabling the Web Console SMF Service

# svcadm enable svc:/system/webconsole:console

Identifying System Memory

Identifying Degraded Memory in a System

XSCF> showstatus

The following example identifies DIMM number 0A on the motherboard unit has degraded memory.

XSCF> showstatus
      MBU_A Status:Normal;
*       MEM#0A Status:Degraded;

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

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