About This Documentation (PDF and HTML)
Hardware Installation and Product Notes
Overview of the Sun Blade X6275 M2 Server Module
Installing and Powering On the Server Module
Overview of the Sun Blade X6275 M2 Server Module Product Notes
System Software Release Features
Integrated Lights Out Manager (ILOM)
Hardware, Firmware, and BIOS Issues
Hardware, Firmware, and BIOS Current Issues
Care and Handling of Server Modules with FMods
Setup and Power-On Recommendations for the Sun Blade 6000 Modular System Chassis
PCIe Link Speed Reduced With BIOS 10.2.6.0 (6994690)
PC-Check 6.27s Does Not Recognize Mellanox 10GbE Chip (6992284)
Performance Degradation When BIOS Hardware Prefetcher is Enabled
Identifying a Node's Onboard Device Versus a Node's PCIe EM (7072665)
Management and ILOM Current Issues
Reading Server Power Consumption in the CMM
The Server Will Not Boot if the CMM is Off-Line
Locate LED Programmed to Stay On for 30 Minutes (6793865)
Set Port Sharing Error Message Generated When Using SP ILOM Web Interface (6895495)
Green LED Should Slow Blink (1 Hz) During Firmware Upgrade (6862377)
IPMIflash Over USB Interface Fails Due to Unexpected Response to File-upload Command (6856369)
Missing Warning Message While Doing Backup Configuration Without Passphrase (6859295)
Erroneous Chassis Hot Insertion Event Logged After CMM Reboot (6797938)
CMM ILOM Becomes Unresponsive With Multiple CLI Sessions Open (6780171)
CMM ILOM Interface Becomes Unresponsive After Repeated Use (6798257)
Blade Power On Issues With the start /SYS Command (6784708)
SP Network Connection Lost When Issuing Incorrect ipmiflash -I pci Command (6850823)
Powering On Batches of Blades Might Cause a Node to Fail to Power On (6813202)
Softcap Power Limiting Does Not Work When the Host is Powered on After the SP Reboots (6890841)
PCIe EM Native Hot Plug Does Not Work (6804272)
ILOM Power Budget Status Does Not Function Properly When Disabled and Then Enabled (7009654)
ILOM Configurations Are Preserved During Upgrade Even After Specifying "No" (6971164)
OL/RHEL Error Message: PCI: BIOS Bug MCFG area at e0000000 is not E820-reserved
OL/RHEL Sound Server Informational Message: Error While Initializing the Sound Driver
SLES: Additional Software Driver Added May Not Work
SLES Error Message: Hotpluggable processor device is not present
SLES: 10GbE Driver Does Not Load Automatically During Boot (6994464)
Configuring the 10GbE Driver for Maximum Performance Can Cause Windows Blue Screens (7010601)
Getting Started Guide Contains Incorrect Power LED State Information
Installing the Oracle Solaris Operating System
Installing Red Hat Enterprise Linux
Installing the SLES Operating System
Introduction to Oracle VM Installation
Creating a PXE Installation Image for Oracle VM
Introduction to Windows Installation
Getting Started With Windows Server 2008 Installation
Installing the Windows Server 2008 R2 Operating System
Updating Critical Drivers and Installing Supplemental Software
Incorporating Device Drivers into a WIM Image for WDS
Administration, Diagnostics, and Service
Overview of the ILOM Supplement
Managing Power Usage and Monitoring Power Consumption
Configuring the Server Power Restore Policy
Switching the Default Serial Port Output Between SP and Host Console
Indicators, Sensors, and Traps
Introduction to Diagnostic Tools
U-Boot Diagnostic Startup Tests
Accessing the Pc-Check Diagnostics Utility on the Tools and Drivers CD/DVD
Server Module and Components Overview
Preparation Procedures for Service and Operation
Component Removal and Installation Procedures
From Power Management -> Allocation –> Power Allocation Plan, the Target Limit value can be in watts or a percent between:
138 watts (Installed Hardware Minimum power) and
295 watts (Allocated Power)
Note - Installed Hardware Minimum power is the recommended minimum power you can set and should be regarded as a reference.
Capping the power to this minimum value will have two issues:
CPU performance will be severely downgraded.
You may see a “power violation” in the CLI and ILOM SEL log (described below). This is due to the minimum power calculation which is hard to perfect. The calculation's accuracy should be taken into account for each component and for different usage patterns. The Violation status occurs since the system is not able to reduce power to below the Installed Hardware Minimum power due to the usage pattern.
On the Consumption tab under Power Management in the ILOM Web interface, the following warning might be seen for the target limit:
In case of a hard cap, you might see Warning: /Peak Permitted/ exceeds /Target Limit/.
In case of a soft cap, you might see Warning: /Actual Power/ exceeds /Target Limit/.
Through the ILOM CLI, the event is recorded as follows:
/SP/powermgmt/budget Properties: activation_state = enabled status = violation
The ILOM SEL will record a IPMI log similar to the following:
ID = 10e2 : 10/27/2009 : 14:28:56 : Power Supply : PWRBS : State Asserted
To avoid this, do not cap the power to this minimum value.