About This Documentation (PDF and HTML)
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
Management and ILOM Current Issues
Capping Power Values in ILOM Web Interface
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)
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)
When the ILOM start /SYS command is issued to power on the host, it will occasionally fail with the following message:
start: Insufficient power available for this operation: The chassis Available Power must exceed the chassis Ticketed Power by greater than the power budget requirement of this blade (see power ticket denied message in the CMM event log)
The above message may not accurately describe the correct reason for the failure of the host system to power on. Although insufficient available power is one possible cause, other factors such as hardware malfunction, system faults on the peer node of the same blade, and/or chassis CMM failures may result in the same error.
If you encounter this error, do the following to help in identifying the source of the problem:
Check the health of the peer node on the same blade.
Check the health of the chassis CMM.
Inspect the system event logs for issues that might be related.
Confirm that sufficient power is available at the chassis level.