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
Sun Blade Zone Manager Not Ready
Missing SAS-2 Components 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
If you are trying to assign storage module resources to a server module that does not have a SAS-2 REM, you will see a “Not SAS-2 Capable” error listed in the Sun Blade Zone Manager.
What to look for:
The following table provides examples of how the web interface and CLI might look like when you have servers that are not SAS-2 capable.
|
Actions to perform:
Only server modules with a SAS-2 REM can be assigned storage module resources.
Check that the server module ILOM service processor has the latest supported ILOM firmware.
Check that the server module REM has the latest supported firmware.