About This Documentation (PDF and HTML)
Overview of the Sun Blade Storage Module M2
Installing the Storage Module Into the Chassis
Assigning and Managing Storage
Overview of the Sun Blade Storage Module M2 Product Notes
Supported Firmware, Hardware and Software
Solaris Operating System Issues
Performing Maintenance and Hot Plug Actions
Importing Existing Virtual Drives to a Replacement REM
Storage Module Sensors and Indicators
Viewing the CMM ILOM Event Log
Missing SAS-2 Components Error
Server Module Not SAS-2 Capable Error
Newly Inserted NEM is Not Discovered
Storage Module Becomes Inaccessible at Host and ILOM /CH/BLx/fault_state is "Faulted"
Storage Module Becomes Inaccessible at Host and ILOM /CH/BLx/STATE is "Degraded"
Storage Module Fault LED is On
SAS Path Disappears and ILOM /CH/NEMx/fault_state is "Faulted"
NEM STATE (/CH/NEMx/STATE) is Not "Running"
NEM /CH/NEMx/OK Indicator is in Standby Blink
Introduction to the Sun Blade Storage Module M2
Maintaining the Sun Blade Storage Module M2
When CMM ILOM starts, it can take several minutes for all the ILOM services to come online. The amount of time it take depends on how many devices are installed in the chassis. If you attempt to perform zone management actions before the all ILOM services are online, you will see a “not ready” error message.
What to look for:
If you attempt to use the Sun Blade Zone Manager before the services are online, what you see depends on whether you are using the web interface or the CLI.
Note - The “not ready” message could appear whether zoning is enabled or disabled.
|
Actions to perform:
If you encounter this issue, wait an additional five minutes and then try again. You need to close and reopen, or refresh the page if you are in the CMM ILOM web interface.