JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
SPARC Enterprise M3000/M4000/M5000/ M8000/M9000 Servers

Product Notes for XCP Version 1115

search filter icon
search icon

Document Information

Using This Documentation

1.  Introduction

Hardware, Firmware, and Software Compatibility

Obtaining Oracle Solaris Patches

2.  Information About XCP 1115 Firmware

XCP Support for RAID-Capable IOUA Cards in M8000/M9000 Servers

Upgrading and Downgrading XCP

XCP Compatibility

Upgrading to This Release

Updating the OpenBoot PROM Firmware

Upgrading From a Version Earlier Than XCP 1050

Upgrading an M8000/M9000 Server From a Version Earlier Than XCP 1082

Domain Restart Required After Certain Type of XCP Upgrade

Downgrading XCP Firmware

XCP Functionality Issues and Limitations

XCP Known Issues (CRs) and Workarounds

3.  Information About Software

Software Compatibility

Capacity on Demand (COD)

COD Changes in XCP 1101

COD Changes in XCP 1102

Sun Flash Accelerator F20 PCIe Card

Remote Initial Login

Fault Management

Identifying Degraded Memory in a System

To Identify Degraded Memory in a System

Sun Java Enterprise System

Enabling the Web Console SMF Service

To Enable the Web Console SMF Service

Software Functionality Issues and Limitations

Oracle Solaris OS Issues (CRs) and Workarounds

Known Issues in All Supported Oracle Solaris Releases

Issues Fixed in Oracle Solaris 10 8/11

Issues Fixed in Oracle Solaris 10 9/10

Issues Fixed in Oracle Solaris 10 10/09

Issues Fixed in Oracle Solaris 10 5/09

Issues Fixed in Oracle Solaris 10 10/08

Issues Fixed in Oracle Solaris 10 5/08

Issues Fixed in Oracle Solaris 10 8/07

Software Documentation Updates

Updates for Man Pages

Updates for Software Manuals

4.  Information About Hardware

Important Notes, Issues and Workarounds – All M-Series Servers

Hardware Compatibility

Booting From a WAN Boot Server

Booting Multiple Systems From a Single J4200 JBOD Storage Array

Notes on the Use of USB Memory

Hardware Functionality Issues and Limitations

Important Notes, Issues and Workarounds – M3000 Servers Only

Patches for Emulex PCI Express (PCIe) Cards

Daughter Card Installed on the MBU_A

Hardware Functionality Issues and Limitations

Important Notes, Issues and Workarounds – M4000/M5000 and M8000/M9000 Servers Only

For M4000/M5000 Servers Determine if any CPUM is Licensed Under Capacity On Demand (COD)

For M8000/M9000 Servers Determine if any CPU is Licensed Under COD

M9000 Server Installation Area

Warning Label on M9000 Server AC Section

RAID-Capable IOUA

DVD Drives and cfgadm

F20 PCIe Cards

Sun Crypto Accelerator 6000 Cards

U320 PCIe SCSI Card

Patches for QLogic PCIe Cards

Patches for Emulex PCI Express (PCIe) Cards

Hardware Functionality Issues and Limitations

Hardware Documentation Updates for the M3000 Server

Hardware Documentation Updates for the M4000/M5000 Servers

Hardware Documentation Updates for the M8000/M9000 Servers

Important Notes, Issues and Workarounds – All M-Series Servers

Hardware Compatibility

For current hardware compatibility information, see Hardware, Firmware, and Software Compatibility.

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.10 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 Oracle Solaris 10 OS that you are using. You can find Oracle Solaris 10 OS documentation here:

http://www.oracle.com/technetwork/documentation/index.html

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

Booting Multiple 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 arrays can be configured into multiple zones to provide a more secure environment.

For related information, see Sun StorageTek Common Array Manager Software documentation, at:

http://www.oracle.com/technetwork/documentation/disk-device-194280.html#hic

See especially:

Notes on the Use of USB Memory

To execute the dumpconfig(8), restoreconfig(8) or snapshot(8) command, if you specify USB memory as the destination to store data, prepare the USB memory as a medium in advance.

The data stored will include the information about the system. To use USB memory, you need to pay attention to the management of the USB memory in which the data is stored, from the data security viewpoint.

Proper operation and connectivity to the XSCF of every USB memory currently on the market cannot be guaranteed. Depending on the USB memory in use, defects such as the XSCF firmware error or reset might occur. In case such defects occurred, stop the use of USB memory immediately.

To connect the USB memory to the USB port for the XSCF, connect the USB memory directly to the USB port. If connected through the USB hub or USB extension, it might cause errors.

Hardware Functionality Issues and Limitations

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

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

https://wikis.oracle.com/display/SystemsComm/Cross+Platform+IO+Support