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

COD Headroom

COD Warning and Violation Messages

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

CR 6660168

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

Capacity on Demand (COD)

The Capacity on Demand (COD) feature has not changed in this release. The information in this section might be of interest only to those updating from an earlier XCP release.

The XCP 1100 firmware release introduced support for the showcodactivationhistory(8) command, which lets you view or transfer COD activation history.

COD Changes in XCP 1101

The XCP 1101 firmware introduced a new release of the Capacity on Demand (COD) feature. See the latest version of the SPARC Enterprise M4000/M5000/M8000/M9000 Servers Capacity on Demand (COD) User's Guide. Changes include:

COD Changes in XCP 1102

COD Headroom

The XCP 1101 firmware ended support for the headroom feature on Oracle M-Series servers. Beginning with the XCP 1102 firmware, a non-zero headroom value resulted in a COD violation. If you have any COD processors running on headroom, either uninstall the number of COD processors from domains equal to the number in violation, or purchase and install COD Hardware Activation Options for those COD resources in use but not yet purchased. Then execute setcod 0 to set headroom to zero, and power the domain off then on to ensure only authorized COD resources are installed.

COD Warning and Violation Messages

Beginning with XCP 1102 firmware, if the COD headroom value is greater than zero when the server is upgraded, the COD software automatically resets it to zero and records a warning message stating so in the monitor log (viewable by showlogs(8)). However, each time the XSCF is initialized, the warning appears again. To avoid future warnings, execute setcod 0 to persistently set headroom to zero. In addition, if your server is employing headroom to use COD processors on powered-on domains, COD violations are logged and showcod(8) displays VIOLATION status. To stop the warning and violation messages, execute the procedures described in COD Headroom, above.