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

Document Information

Preface

Product Information Web Site

Related Books

About This Documentation (PDF and HTML)

Documentation Comments

Change History

Hardware Installation

Overview of the Sun Blade Storage Module M2

System Requirements

Installing the Storage Module Into the Chassis

Storage Module Indicators

Assigning and Managing Storage

Product Notes

Overview of the Sun Blade Storage Module M2 Product Notes

Supported Firmware, Hardware and Software

Hardware Issues

Solaris Operating System Issues

Linux Operating System Issues

Administration

Assigning Storage to Hosts

SAS Device Access to the Chassis SAS-2 Domain

Host Access to Storage Module Resources Using the Sun Blade Zone Manager

System Requirements

How to Assign Storage to Hosts Using the CMM ILOM Web Interface

How to Assign Storage to Hosts Using the CMM ILOM CLI

Managing Storage

Performing Maintenance and Hot Plug Actions

Importing Existing Virtual Drives to a Replacement REM

Storage Module Sensors and Indicators

Troubleshooting

Service

Introduction to the Sun Blade Storage Module M2

Maintaining the Sun Blade Storage Module M2

Diagnosing Storage Module Faults

Specifications

Index

SAS Device Access to the Chassis SAS–2 Domain

The internal chassis SAS-2 domain is managed by the CMM. The CMM detects SAS devices (such as NEMs, REMs, and the storage modules) that are connected to the chassis midplane and allows them to access the SAS-2 domain as follows:

The CMM in conjunction with the SAS-2 NEM determines whether a SAS device is allowed access to the SAS-2 domain. A SAS-2 NEM has two components: the SAS component and the network component.

The following illustration shows how different SAS components within the chassis are allowed access. Note that SAS-1 devices are not allowed to access the SAS-2 domain.


Note - In the example below, a SAS-1 disk blade would not be accessible by any server module in the chassis.


image:Graphic showing access to SAS-2 domain.

Although SAS-1 devices cannot participate in the SAS-2 domain, the networking portion is not affected. A server module with SAS-1 devices can still access the networking component of a SAS–2 NEM, as shown in the following illustration.

image:Graphic showing access to network ports of the NEM.

See also: