JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Blade Storage Module M2 Service Manual
search filter icon
search icon

Document Information

Preface

Product Information Web Site

Related Books

About This Documentation (PDF and HTML)

Documentation Comments

Change History

Introduction to the Sun Blade Storage Module M2

Terminology Used In This Document

Storage Module Features

Storage Module Components

Accessory Kit Contents

Maintaining the Sun Blade Storage Module M2

Options and Replaceable Components

Antistatic Procedures and Precautions

Replacing a Disk Drive (CRU)

Replacing the Storage Module (FRU)

Upgrading Storage Module Firmware

Diagnosing Storage Module Faults

Diagnosing Faults Using CMM ILOM

Diagnosing Faults Using MegaRAID Storage Manager Software

Diagnosing Faults With SunVTS Software

Diagnosing Faults With LEDs and Indicators

Specifications

Physical

Environmental and Electrical

Index

Terminology Used In This Document

The following terminology is used in this document.

chassis
The Sun Blade 6000 Modular System enclosure.
CMM
Chassis Monitoring Module. An Integrated Lights Out Manager component of the Sun Blade 6000 Modular System used to access and manage servers and storage modules in the chassis.
multipath
This is a dual path connection from a host to the storage module. Provides two paths to the storage components in the storage module for failover. Path failover is managed through REM firmware when you create logical drives using the REM firmware utilities.
NEM
Network Express Module. A networking I/O component that plugs into a Sun Blade Modular System chassis. The chassis contains two NEM slots: NEM 0 and NEM 1.
REM
A RAID Expansion Module. Also referred to as a Host Bus Adapter (HBA), or an initiator. Acts as an interface between the host and connected storage. Supports the creation of RAID volumes on connected storage. Provides disk management and monitoring of connected storage.
SAS–2
Serial Attached SCSI version 2. Supports up to 6 Gb/s data transfer rate. The combination of SAS-2 devices, such as REMs, NEMs and storage modules inside the chassis creates a SAS–2 domain connecting shared storage to servers. Access to the chassis SAS-2 domain is managed by the CMM.
SAS-2 NEM
Any Network Express Module that supports SAS–2 connectivity. Only NEMs that support SAS-2 can be used with the Sun Blade Storage Module M2. For example, the Sun Blade 6000 Virtualized Multi-Fabric 10GE NEM M2.
SAS target
A device containing logical units and target ports that receives requests from, and responds to, an initiator. An example of a target device is a hard disk. Other terms used to describe a SAS target are “device” and “end device.”
SATA
Serial ATA (or Serial Advanced Technology Attachment). Supports up to 1.5Gb/s data transfer rate for SATA and 3Gb/s for SATA-II. SATA devices are single port/single path.
server module
A Sun Blade server module that fits in the Sun Blade 6000 Module System. Server modules use storage in the storage module. Might also be known as a ”host”, “blade” or a “server blade”.
single path
This is a single path connection from a host to the storage module (for example, if there is only one NEM in the chassis, or the target device is SATA). No path failover is available.
storage module
The Sun Blade Storage Module M2. Might also be known as a “disk module” or a “disk blade”.
zoning
Zoning in SAS-2 is a mechanism to manage large SAS topologies. Zoning is used to partition the chassis SAS–2 domain into smaller groups and provides the mechanism necessary to manage these groups. The storage module uses PHY resolved zoning. Each SAS-2 expander PHY is assigned to a zone group including any device attached to that PHY. The expander contains a permission table that defines access control between devices in each zone group (by default, all devices within a zone group can interact with each other). Refer to the SAS-2 specification for more details.