Cisco MDS SanOS Troubleshooting Guide -- Managing Storage Services Modules

From DocWiki

Revision as of 10:42, 15 July 2010 by Gkanmas (Talk | contribs)
Jump to: navigation, search

This chapter describes how to manage the Storage Services Module (SSM) and provides information about SSI images.

Contents



SSM Overview

The 32-port Fibre Channel Storage Services Module (SSM) for the Cisco MDS 9000 Family supports up to 32 Fibre Channel ports and provides distributed intelligent storage services.

Note Note: Cisco MDS 9500 Series switches running Cisco MDS SAN-OS Release 2.0(2b) or later support the SSM module.

The SSI image for the SSM is downloaded from the supervisor module. The image for an SSM can be specified using the SSI boot variable.

Note Note: The SSM can operate as a 32-port Fibre Channel switching module with the standard Cisco SAN-OS images for Release 2.1(2) or later. You need the SSI image if you use intelligent storage services.

The following table lists the features supported for the SSM :

Module Cisco MDS SAN-OS Release
2.0(1b) 2.0(2b), 2.0(3), 2.0(4), and 2.0(4a) 2.1(1a) 2.1(2) and later
SSM None Fibre Channel switching Fibre Channel switching Fibre Channel switching
Intelligent Storage Services Intelligent Storage Services Intelligent Storage Services
VSFN VSFN Nondisruptive upgrade for Fibre Channel switching traffic1

When you upgrade, or downgrade, the SSI boot image on an SSM, you might disrupt traffic through the module. The following table describes how updating the SSI boot image affects SSM traffic.

Cisco MDS SAN-OS Release Traffic Type Disrupts Traffic?

2.0(2b) through 2.1(1a)

All

Yes

2.1(2) and later

Layer 2 Fibre Channel switching only

No1

Both Layer 2 Fibre Channel switching and Layer 3 Intelligent Storage Services (such as FCWA, NASB, SANTap, and ISAPI virtualization)

Yes

Layer 3 Intelligent Storage Services (such as FCWA, NASB, SANTap, ISAPI virtualization) only

Yes

As shown in Table 3-2, Layer 3 Intelligent Storage Services traffic is disrupted when you update the SSI boot image. If you configure Layer 3 Intelligent Storage Services on your SSM, we recommend that you shut down these services before upgrading the SSI boot image. You can use dual fabric configuration to minimize the impact of shutting down Layer 3 services.

Initial Troubleshooting Checklist

Begin troubleshooting SSM issues by verifying that the following conditions are met:

Checklist

Check off

Verify that the SSI boot variable is set.

<img src="ts_ssm_files/ts_ssm-1.jpg" height="21" width="21" id="wp1147217" border="0" hspace="0" vspace="0"/>

Verify that the SSI image is present and pointed to by the SSI boot variable.

<img src="ts_ssm_files/ts_ssm-2.jpg" height="21" width="21" id="wp1147224" border="0" hspace="0" vspace="0"/>

Verify that the EPLD version is 2.1(2) or later for nondisruptive layer-2 upgrades.

<img src="ts_ssm_files/ts_ssm-3.jpg" height="21" width="21" id="wp1147231" border="0" hspace="0" vspace="0"/>

Verify that you have configured all SSM ports prior to upgrading to Cisco SAN-OS Release 3.0(1) or later. Do not use port mode auto.

<img src="ts_ssm_files/ts_ssm-4.jpg" height="21" width="21" id="wp1147238" border="0" hspace="0" vspace="0"/>

Verify that you have the appropriate licensing. The SSM can operate as a 32-port Fibre Channel switching module with no additional licensing requirements. The SSM requires the Storage Services Enabler package to provision intelligent storage services on the module.

<img src="ts_ssm_files/ts_ssm-5.jpg" height="21" width="21" id="wp1160647" border="0" hspace="0" vspace="0"/>

Common Troubleshooting Tools in Fabric Manager

Common Troubleshooting Commands in the CLI

SSM Issues

SSM Fails to Boot

Upgrading the SSI Image

Verifying the SSI Boot Image

Using the install ssi Command

Recovering a Replacement SSM

SSM Upgrade Is Disruptive

Installing EPLD Images on Modules


Back to Main Page: Cisco MDS SAN-OS Troubleshooting Guide

Rating: 0.0/5 (0 votes cast)

Personal tools