Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco MDS 9000 SAN-OS Software

Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.0(1)

Downloads

Table Of Contents

Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.0(1)

Contents

Introduction

System Requirements

Components Supported

Determining the Software Version

Downloading Software

Upgrading Your Cisco MDS SAN-OS Software Image

Performing a Nondisruptive Software Upgrade on Generation 1 Modules

Upgrading with IVR Enabled

Selecting the Correct Software Image for an MDS 9500 Series Switch

Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.0(1)

Migrating from Supervisor-1 Modules to Supervisor-2 Modules

Configuring Generation 2 Switching Modules

Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch

New Features in Cisco MDS SAN-OS Release 3.0(1)

FCIP Tape Read Acceleration

Fabric Binding for Fibre Channel

FICON Port Swapping Enhancement

Generation 2 Switching Module Support

IKE Digital Certificates

IKE Fully Qualified Domain Names

IKE Host Name Support

IPsec Authentication Enhancements

IVR Enhancements

FICON Port Numbering

iSCSI Server Load Balancing (iSLB)

iSNS Cloud Discovery

IPv6

IPv6 Access Control Lists (IPv6-ACLs)

CFS Over IP Distribution

CFS Support for Allowed Domain ID Lists

In-Order Delivery Enhancements

CLI Enhancements

AAA Server Enhancements

SSH Authentication Enhancements

Call Home Enhancements

Online Health Management System Enhancements

McDATA Native Interoperability

Increased Zone Limit per VSAN

MS-CHAP

boot auto-copy Command Enabled by Default

N-Port Identifier Virtualization

RSCN Timer Configuration

Modem Support for Supervisor-2 Modules

Configuration Check

SMI-S 1.1.0 Support

New SAN-OS MIBs

SFP Diagnostic Information

Crossbar Management

Fabric Manager Server Enhancements

Performance Prediction Trending

Configurable RRD

Custom Report Performance Chart

Server Performance Summary Report

Data Collection Auto-Update

Event Forwarding

Filtering by User-Defined Groups

SNMP over TCP/IP

EMC Call Home

New Hardware Features

Cisco MDS 9513 Director

Cisco MDS 9500 Series Supervisor-2 Module

Cisco MDS 9000 48-Port 4-Gbps Fibre Channel Switching Module

Cisco MDS 9000 24-Port 4-Gbps Fibre Channel Switching Module

Cisco MDS 9000 12-Port 4-Gbps Fibre Channel Switching Module

Cisco MDS 9000 4-Port 10-Gbps Fibre Channel Switching Module

Crossbar Module

X2 Transceiver

Gigabit Ethernet SFP Transceiver

Limitations and Restrictions

Reconfiguring SSM Ports

Downgrading from Cisco MDS SAN-OS Release 3.0(1)

Downgrading from Cisco SAN-OS Release 3.2(1)

ISNS Server

CWDM SFPs

10-Gbps Inter-Switch Links

Configuring Default Settings for the Default Zone

Caveats

Resolved Caveats

Open Caveats

Related Documentation

Release Notes

Compatibility Information

Regulatory Compliance and Safety Information

Hardware Installation

Cisco Fabric Manager

Command-Line Interface

Troubleshooting and Reference

Installation and Configuration Note

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Product Alerts and Field Notices

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.0(1)

Release Date: April 17, 2006

Text Part Number: OL-8795-01 Z0

This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the "Related Documentation" section.

Note Release notes are sometimes updated with new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Family Release Notes: http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_release_notes_list.html

Table 1 shows the on-line change history for this document.

Table 1 Online History Change

Revision
Date
Description

A0

04/17/2006

Created release notes

B0

04/19/2006

Added DDTS CSCsd92429.

C0

05/04/2006

Added DDTS CSCeg53114, CSCei79457, and CSCsd87853.

Removed DDTS CSCeh22523, CSCei67982.

D0

05/22/2006

Added DDTS CSCsc20106, CSCsd89872, CSCsd94019, CSCsd94229, CSCsd97090, CSCse14087, CSCsd94718, CSCse12209, CSCse13769, and CSCse14032.

Removed CSCeh52973.

Revised the following sections: Upgrading, Reconfiguring SSM Ports, Migrating, Generation 2, Downgrading, and Limitations.

E0

05/25/2006

Updated New Features and Limitations sections.

Removed CSCse14087.

F0

06/23/2006

Added DDTS CSCsd95862, CSCsd19272, CSCse36768.

Updated the New Features in Cisco MDS SAN-OS Release 3.0(1) section.

Removed CSCeg33121, CSCeg12962, CSCeg84871, CSCeg90336, CSCeh04183, CSCeh30951, CSCeh70232, CSCeh93109, CSCei10774, CSCei36082, CSCei79457, CSCei53783, CSCsc46451, CSCsc95884, CSCec31365, CSCeg53114, CSCeg55238, CSCeh34828, CSCei48889,CSCei91676, CSCei91968, CSCej08751, CSCin92870, CSCin95789, and CSCsd71701.

G0

07/07/2006

Corrected the CWDM part numbers in Table 2.

H0

08//3/2006

Revised DDTS CSCsd89872 and CSCse84811

I0

08/18/2006

Added DDTS CSCse89151

J0

08/22/2006

Revised the Downgrading from Cisco MDS SAN-OS Release 3.0(1) section.

Added DDTS CSCse65400.

K0

09/05/2006

Added DDTS CSCsd78967 and CSCse88606.

L0

09/7/2006

Added DDTS CSCec28084.

M0

09/13/2006

Added DDTS CSCsf21970.

N0

09/22/2006

Added the external crossbar module part number.

O0

11/29/2006

Added a note to the Downgrading section on having iSCSI enabled during a downgrade.

Added a Limitation and Restriction about CWDM SFPs.

P0

11/30/2006

Added DDTS CSCin95789, CSCsd15794, CSCsd21187, CSCsd81137, CSCse22145, CSCse41442, CSCse70275, CSCse71420, CSCsf18552, CSCsf96043, CSCsf98427, CSCsg01963, CSCsg12020, and CSCsg15392.

Q0

12/07/2006

Added DDTS CSCsd99599.

R0

02/01/2007

Added DDTS CSCsg03171.

S0

02/22/2007

Added DDTS CSCsd92433, CSCsd97376, CSCse99087, CSCsg29400, CSCsg35972, CSCsg62359, CSCsg82792, CSCsh27840, and CSCsh31236.

T0

04/04/2007

Added DDTS CSCsd41578 and CSCsh83200.

Added the section "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch".

Added the section "Configuring Default Settings for the Default Zone".

U0

06/11/2007

Added DDTS CSCsh24256.

V0

07/18/2007

Removed DDTS CSCei82909.

W0

08/24/2007

Added DDTS CSCsd83775.

X0

10/23/2007

Removed DDTS CSCsh31236.

Added information about Downgrading from Cisco SAN-OS Release 3.2(1) to the "Limitations and Restrictions" section.

Y0

04/30/2008

Added DDTS CSCso63465.

Z0

11/13/2008

Added the "Performing a Nondisruptive Software Upgrade on Generation 1 Modules" section.


Contents

This document includes the following sections:

•Introduction

•System Requirements

•Upgrading Your Cisco MDS SAN-OS Software Image

•New Features in Cisco MDS SAN-OS Release 3.0(1)

•Fabric Manager Server Enhancements

•New Hardware Features

•Limitations and Restrictions

•Caveats

•Related Documentation

•Obtaining Documentation

•Documentation Feedback

•Cisco Product Security Overview

•Obtaining Technical Assistance

•Obtaining Additional Publications and Information

Introduction

The Cisco MDS 9000 Family of Multilayer Directors and Fabric Switches provides industry-leading availability, scalability, security, and management, allowing you to deploy high performance storage-area networks with lowest total cost of ownership. Layering a rich set of intelligent features onto a high performance, protocol agnostic switch fabric, the Cisco MDS 9000 Family addresses the stringent requirements of large data center storage environments: uncompromising high availability, security, scalability, ease of management, and seamless integration of new technologies.

The Cisco MDS 9000 Family SAN-OS is the underlying system software that powers the Cisco MDS 9500 series, 9200 series, and 9100 series multilayer switches. The Cisco SAN-OS provides intelligent networking features, such as multiprotocol and multitransport integration, virtual SANs (VSANs), advanced security, sophisticated debug analysis tools, and unified SAN management.

System Requirements

This section describes the system requirements for Cisco MDS SAN-OS Release 3.0(1) and includes the following topics:

•Components Supported

•Determining the Software Version

•Downloading Software

Components Supported

Table 2 lists the software and hardware components supported by the Cisco MDS 9000 Family.

Note To use the Cisco Storage Services Enabler package, Cisco MDS SAN-OS Release 1.3(5) or later must be installed on the MDS switch.

Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components  

Component
Part Number
Description
Applicable Product

Software

M95S2K9-3.0.1

MDS 9500 Supervisor/Fabric-2, SAN-OS software.

MDS 9500 Series only

M95S1K9-3.0.1

MDS 9500 Supervisor/Fabric-I, SAN-OS software.

MDS 9500 Series only

M92S1K9-3.0.1

MDS 9216 Supervisor/Fabric-I, SAN-OS software.

MDS 9200 Series only

M91S1K9-3.0.1

MDS 9100 Supervisor/Fabric-I, SAN-OS software.

MDS 9100 Series only

License

M9500ENT1K9

Enterprise package.

MDS 9500 Series

M9200ENT1K9

Enterprise package.

MDS 9200 Series

M9100ENT1K9

Enterprise package.

MDS 9100 Series

M9500FIC1K9

Mainframe package.

MDS 9500 Series

M9200FIC1K9

Mainframe package.

MDS 9200 Series

M9100FIC1K9

Mainframe package.

MDS 9100 Series

M9500FMS1K9

Fabric Manager Server package.

MDS 9500 Series

M9200FMS1K9

Fabric Manager Server package.

MDS 9200 Series

M9100FMS1K9

Fabric Manager Server package.

MDS 9100 Series

M9500EXT1K9

SAN Extension over IP package for IPS-8 module.

MDS 9500 Series

M9200EXT1K9

SAN Extension over IP package for IPS-8 module.

MDS 9200 Series

M9500EXT14K9

SAN Extension over IP package for IPS-4 module.

MDS 9500 Series

M9200EXT14K9

SAN Extension over IP package for IPS-4 module.

MDS 9200 Series

M9500EXT12K9

SAN Extension over IP package for MPS 14+2 module.

MDS 9500 Series

M9200EXT12K9

SAN Extension over IP package for MPS 14+2 module.

MDS 9200 Series

M9500SSE1K9

Storage Services Enabler package.

MDS 9500 Series with ASM or SSM

M9200SSE1K9

Storage Services Enabler package.

MDS 9200 Series with ASM or SSM

Chassis

DS-C9513

MDS 9513 director (13-slot modular chassis with 11 slots for switching modules, and 2 slots reserved for Supervisor 2 modules only—SFPs1 sold separately).

MDS 9513 only

DS-C9509

MDS 9509 director, base configuration (9-slot modular chassis includes 7 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).

MDS 9509 only

DS-C9506

MDS 9506 director (6-slot modular chassis includes 4 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).

MDS 9506 only

DS-C9216-K9

MDS 9216 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).

MDS 9216 only

DS-C9216A-K9

MDS 9216A 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).

MDS 9216A only

DS-C9216i-K9

MDS 9216i 16-port semi-modular fabric switch (includes 14 1-Gbps/2-Gbps Fibre Channel ports, 2 Gigabit Ethernet ports, power supply, and expansion slot—SFPs sold separately).

MDS 9216i only

DS-C9140-K9

MDS 9140 fixed configuration (non-modular) fabric switch (includes 8 full rate ports and 32 host-optimized ports).

MDS 9140 only

DS-C9120-K9

MDS 9120 fixed configuration, non-modular, fabric switch (includes 4 full rate ports and 16 host-optimized ports).

MDS 9120 only

External
crossbar module

DS-13SLT-FAB1

MDS 9513 Crossbar Fabric Module

MDS 9513 only

Supervisor modules

DS-X9530-SF2-K9

MDS 9500 Supervisor-2, module.

MDS 9500 Series only

DS-X9530-SF1-K9

MDS 9500 Supervisor/Fabric-I module.

Switching modules

DS-X9016

MDS 9000 16-port 1-Gbps/2-Gbps Fibre Channel module (SFPs sold separately).

MDS 9500 Series and 9200 Series

DS-X9032

MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel module (SFPs sold separately).

DS-X9112

MDS 9000 12-port 4-Gbps Fibre Channel module (SFPs sold separately).

MDS 9500 Series and 9200 Series, except for the MDS 9216

DS-X9124

MDS 9000 24-port 4-Gbps Fibre Channel module (SFPs sold separately).

MDS 9500 Series and 9200 Series, except for the MDS 9216

DS-X9148

MDS 9000 48-port 4-Gbps Fibre Channel module (SFPs sold separately).

MDS 9500 Series and 9200 Series, except for the MDS 9216

DS-X9704

MDS 9000 4-port 10-Gbps Fibre Channel module (SFPs sold separately)

MDS 9500 Series and 9200 Series, except for the MDS 9216

Services modules

DS-X9308-SMIP

8-port Gigabit Ethernet IP Storage services module.

MDS 9500 Series and 9200 Series

DS-X9304-SMIP

4-port Gigabit Ethernet IP Storage services module.

DS-X9032-SSM

MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel Storage Services Module (SSM).

DS-X9302-14K9

14-port Fibre Channel/2-port Gigabit Ethernet Multiprotocol Services (MPS-14/2) module.

Optics

DS-X2-FC10G-SR

X2/SC optics, 10-Gbps Fibre Channel for short wavelength mode.

MDS 9500 Series and 9200 Series, except for the MDS 9216

DS-X2-FC10G-LR

X2/SC optics, 10-Gbps Fibre Channel for long wavelength mode.

LC-type fiber-optic SFP

DS-SFP-FC-2G-SW2

2-Gbps/1-Gbps Fibre Channel—short wavelength SFP.

MDS 9000 Family

DS-SFP-FC-2G-LW2

2-Gbps/1-Gbps Fibre Channel—long wavelength SFP.

DS-SFP-FCGE-SW2

1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—short wavelength SFP.

DS-SFP-FCGE-LW2

1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—long wavelength SFP.

DS-SFP-GE-T2

1-Gbps Ethernet SFP.

DS-SFP-FC4G-SW3

4-Gbps/2-Gbps/1-Gbps Fibre Channel—short wavelength SFP for DS-X91xx switching modules.

DS-SFP-FC4G-MR3

4-Gbps/2-Gbps/1-Gbps Fibre Channel—long wavelength SFP for DS-X91xx switching modules only. Supports distances up to 4 km.

DS-SFP-FC4G-LW3

4-Gbps/2-Gbps/1-Gbps Fibre Channel—long wavelength SFP for DS-X91xx switching modules only. Supports distances up to 10 km.

CWDM4

DS-CWDM-xxxx

Gigabit Ethernet and 1-Gbps/2-Gbps Fibre Channel SFP LC interface xxxx nm, where xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm.

MDS 9000 Family

DS-CWDM-MUX-4

Add/drop multiplexer for four CWDM wavelengths.

DS-CWDM-MUX-8

Add/drop multiplexer for eight CWDM wavelengths.

DS-CWDMCHASSIS

Two slot chassis for CWDM add/drop multiplexers.

Power supplies

DS-CAC-6000W

6000-W AC power supply.

MDS 9513 only

DS-CAC-2500W

2500-W AC power supply.

MDS 9509 only

DS-CDC-2500W

2500-W DC power supply.

DS-CAC-3000W

3000-W AC power supply

DS-CAC-4000W-US

4000-W AC power supply for US (cable attached).

DS-CAC-4000W-INT

4000-W AC power supply international (cable attached).

DS-CAC-1900W

1900-W AC power supply.

MDS 9506 only

DS-CDC-1900W

1900-W DC power supply.

DS-CAC-845W

845-W AC power supply.

MDS 9200 Series only

DS-CAC-300W

300-W5 AC power supply.

MDS 9100 Series only

CompactFlash

MEM-MDS-FLD512M

MDS 9500 supervisor CompactFlash disk, 512 MB.

MDS 9500 Series only

Port analyzer adapter

DS-PAA-2, DS-PAA

A standalone Fibre Channel-to-Ethernet adapter that allows for simple, transparent analysis of Fibre Channel traffic in a switched fabric.

MDS 9000 Family

CD-ROM

M90FM-CD-212=

MDS 9000 Management Software and Documentation CD-ROM, spare.

MDS 9000 Family

1 SFP = small form-factor pluggable

2 Supported on the DS-X9530-SF1-K9, MDS 9500 Series Supervisor module only

3 Supported on the DS-X9530-SF2-K9, MDS 9500 Series Supervisor-2 module only

4 CWDM = coarse wavelength division multiplexing

5 W = Watt


Determining the Software Version

Note We strongly recommend that you use the latest available software release supported by your vendor for all Cisco MDS 9000 Family products.

To determine the version of Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the CLI, log in to the switch and enter the show version EXEC command.

To determine the version of Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the Fabric Manager, view the Switches tab in the Information pane, locate the switch using the IP address, logical name, or WWN, and check its version in the Release column.

Downloading Software

To download the latest Cisco MDS SAN-OS software, access the Software Center at this URL:

http://www.cisco.com/public/sw-center

Upgrading Your Cisco MDS SAN-OS Software Image

The Cisco MDS SAN-OS software is designed for mission-critical, high-availability environments. To realize the benefits of nondisruptive upgrades on the Cisco MDS 9500 Directors, we highly recommend that you install dual supervisor modules.

Use the following guidelines to nondisruptively upgrade your Cisco MDS SAN-OS Release 3.0(1):

•Install and configure dual supervisor modules.

•Upgrade the SSI boot images on the SSMs on the switch to a release version supported by your Cisco SAN-OS release. Refer to the Cisco MDS SAN-OS Release Compatibility Matrix for Storage Service Interface Images.

•Follow the upgrade path for your current release:

–Upgrading from Cisco SAN-OS Release 1.x to Release 3.x requires that you upgrade first to Cisco SAN-OS Release 1.3(4a), then upgrade to Cisco SAN-OS Release 2.1(2b), then upgrade to Cisco SAN-OS Release 3.0(1).

–Upgrading from Cisco SAN-OS Release 2.0(2b), 2.0(2c), 2.0(3), 2.1(2b), 2.1(2c), 2.1(2d), and 2.1(2e), allows you to nondisruptively upgrade directly to Release 3.0(1). If you do not have one of these releases installed, you must upgrade first to Cisco SAN-OS Release 2.1(2b) and then upgrade to Cisco SAN-OS Release 3.0(1).

–Upgrading from Cisco SAN-OS Release 2.x releases to Release 3.x requires that you upgrade first to Cisco SAN-OS Release 2.1(2b) and then upgrade to Cisco SAN-OS Release 3.0(1).

–If you have IVR enabled and you are upgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or Release 2.1.(2a), there are additional steps you should follow before upgrading. See "Upgrading with IVR Enabled" section.

–Upgrading for FICON from Cisco SAN-OS Release 1.x to Release 3.x requires that you upgrade first to Cisco SAN-OS Release 1.3(4a), then upgrade to Cisco SAN-OS Release 2.0(2b), then upgrade to Cisco SAN-OS Release 3.0(1).

•All Gigabit Ethernet ports are disruptive on upgrade or downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module. This impacts those nodes that are members of VSANs traversing an FCIP ISL and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the upgrade is in progress.

•Layer 3 switching on SSM ports are disruptive on upgrades or downgrades. Layer 2 switching can be nondisruptive under the following conditions:

–Upgrade the SSI boot images on the SSMs on the switch to a release version supported by your Cisco SAN-OS release. Refer to the Cisco MDS SAN-OS Release Compatibility Matrix for Storage Service Interface Images.

–All SMM applications are disabled. Use the show ssm provisioning CLI command to determine what applications are configured. Use the no ssm enable feature CLI command to disable these applications.

–No SSM ports are in auto mode. See Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.0(1).

–The EPLD version on the SSM is at 0x07 or higher. Use the show version module slot epld CLI command to determine your EPLD version. Refer to the Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images to upgrade your EPLD image.

–Refer to the Cisco MDS Storage Services Module Interoperability Support Matrix and the Managing Modules chapter in the Cisco MDS 9000 Family CLI Configuration Guide, Release 3.x, for information on upgrading your SSM.

•Use the show install all impact upgrade-image CLI command to determine if your upgrade will be nondisruptive.

•If you are using FCIP tape acceleration and you are upgrading from Cisco MDS SAN-OS Release 2.x to Release 3.x, you should disable the FCIP tape acceleration feature prior to the upgrade. After the upgrade, you should re-enable FCIP tape acceleration.

Caution Upgrading to Cisco MDS SAN-OS Release 2.1(2) or later from any release can disrupt traffic on any SSM installed on your MDS switch.

Note Upgrading from Cisco MDS SAN-OS Release 1.x directly to Cisco SAN-OS Release 3.x is disruptive to all Fibre Channel and Gigabit Ethernet ports.

Note Refer to the "Determining Software Compatibility" section of the Cisco MDS 9000 Family CLI Configuration Guide for more details.

Performing a Nondisruptive Software Upgrade on Generation 1 Modules

Generation 1 modules may reload during a nondisruptive SAN-OS software upgrade because of the CompactFlash being unable to partition for the new code. If that happens, the installer aborts and reloads the module.

This issue affects the following modules:

•DS-X9016, 16-port 1-Gbps/2-Gbps Fibre Channel module

•DS-X9032, 32-port 1-Gbps/2-Gbps Fibre Channel module

•DS-X9032-SSM, 32-port 1-Gbps/2-Gbps Fibre Channel Storage Services Module (SSM)

•DS-X9302-14K9, 14-port Fibre Channel/2-port Gigabit Ethernet Multiprotocol Services (MPS-14/2) module

This issue might be seen during an upgrade from Cisco SAN-OS Release 3.0(x), 3.1(x) or 3.2(x). It has been addressed for upgrades from SAN-OS Release 3.3(1) or higher. Therefore, you will not be impacted by this issue if you are running SAN-OS Release 3.3(1) when you upgrade to a higher SAN-OS release.

When this problem occurs, the module will automatically reload and may cause the Install All to stop, which will cause the upgrade to be unsuccessful. Error messages similar to the following may be displayed: 

Install has failed. Return code 0x40930020 (Non-disruptive upgrade of a module failed).

Please identify the cause of the failure, and try 'install all' again.

Module 2: Non-disruptive upgrading.

-- FAIL. Return code 0x40690009 (Error in downloading image for image upgrade).

To avoid this kind of unplanned disruption, follow the methods for identifying and correcting this issue described in Cisco Field Notice 63099, before proceeding with the SAN-OS upgrade.

This Field notice can be found under the Support, Products page for Cisco MDS9500 Series Multilayer Directors selection.

Upgrading with IVR Enabled

An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is running might be disruptive. Some possible scenarios include:

–FCIP connection flapping during the upgrade process resulting in fabric segmentation or merge.

–ISL flap results in fabric segmentation or merge because of hardware issues or a software bug.

–ISL port becomes part of PCP results in fabric segmentation or merge because of a port flap.

If this problem occurs, syslogs indicate RDI failure and the flapped lSL could remain in a down state because of a domain overlap. This is caused by conflicts between the allowed domains list and the virtual domain requested through RDI.

This issue was resolved in an earlier release, however upgrades from Cisco SAN-OS Release 2.1(1a), 2.1(1b), or 2.1(2a) to Release 3.0(1) when IVR is enabled requires that you use the following workaround.

For VSANS in interop mode 2 or 3, issue an IVR refresh, and then follow the upgrade guidelines listed in "Upgrading Your Cisco MDS SAN-OS Software Image" section.

To upgrade from Cisco SAN-OS Release 2.1(1a), 2.1(1b), or 2.1(2a) to Release 3.0(1) for all other VSANs with IVR enabled, follow these steps:

Step 1 Configure static domains for all switches in all VSANs where IVR is enabled. Configure the static domain the same as the running domain so that there is no change in domain IDs. Make sure that all domains are unique across all of the IVR VSANs. We recommend this step as a best practice for IVR-non-NAT mode. Issue the fcdomain domain {id} static vsan {vsan id} command to configure the static domains.

Note Complete Step 1 for all switches before moving to Step 2.

Step 2 Issue the no ivr virtual-fcdomain-add vsan-ranges 1-4093 command to disable RDI mode on all IVR enabled switches. This can cause traffic disruption.

Note Complete Step 2 for all IVR enabled switches before moving to Step 3.

Step 3 Check the syslogs for any ISL that was isolated.

Example Syslog Error Messages 

2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: 

%$VSAN 2005%$ Isolation of interface 

port-channel 52 (reason: unknown failure)

2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$ 

Isolation of interface port-channel 51 

(reason: domain ID assignment failure)

Step 4 Issue the following commands for the isolated switches in Step 3: 

switch(config)# vsan database

switch(config-vsan-db)# vsan vsan-id suspend

switch(config-vsan-db)# no vsan vsan-id suspend

Step 5 Issue the ivr refresh command to perform an IVR refresh on all the IVR enabled switches.

Step 6 Issue the copy running-config startup-config command to save the RDI mode in the startup configuration on all of the switches.

Step 7 Follow the normal upgrade guidelines for Release 3.0(1) in "Upgrading Your Cisco MDS SAN-OS Software Image" section.

If you are adding new switches running Cisco MDS SAN-OS Release 3.0(x), upgrade all your existing switches to Release 3.0(1) as described in this procedure. Then add new switches.

Note RDI mode should not be disabled for VSANs running in Interop-mode 2 or Interop-mode 3.

Selecting the Correct Software Image for an MDS 9500 Series Switch

The system and kickstart image that you use for an MDS 9500 Series switch depends on whether the switch is based on a Supervisor-1 module or a Supervisor-2 module, as shown in Table 3.

Table 3 Software Image for Supervisor Type

Supervisor Type
Switch
Image

Supervisor-1 module

MDS 9506 and 9509

Filename begins with m9500-sf1ek9

Supervisor-2 module

MDS 9506, 9509, and 9513

Filename begins with m9500-sf2ek9


Use the show module command to display the type of supervisor module in the switch.

For a Supervisor-1 module, the output might look like this: 

switch# show module

Mod  Ports  Module-Type                      Model              Status

---  -----  -------------------------------- ------------------ ------------

...

...

5    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    active*

6    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    ha-standby

For a Supervisor-2 module, the output might look like this: 

switch# show module

Mod  Ports  Module-Type                      Model              Status

---  -----  -------------------------------- ------------------ ------------

...

...

7    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *

8    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby

Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.0(1)

Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode. Because auto mode is the default for releases prior to Release 3.0(1), you should modify the configuration of the ports before upgrading a SAN-OS software image prior to Release 3.0(1) to avoid any traffic disruption.

For more information on upgrading SAN-OS software, see "Upgrading Your Cisco MDS SAN-OS Software Image" section.

If the configuration is not updated before the upgrade, the installation process for the new image will automatically convert all ports configured in auto mode to Fx mode. This might cause a disruption if the port is currently operating in E mode.

To make the configuration change without any traffic disruption, follow these steps:

Step 1 Verify the operational mode for each port on the SSM using the show interface command: 

switch# show interface fc 2/1 - 32

fc2/1 is up

    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)

    Port WWN is 20:4b:00:0d:ec:09:3c:00

    Admin port mode is auto             <-------- shows port is configured in auto mode

    snmp traps are enabled

    Port mode is F, FCID is 0xef0300   <-------- shows current port operational mode is F

    Port vsan is 1

    Speed is 2 Gbps

    Transmit B2B Credit is 3

Step 2 Change the configuration for the first port of the quad when the admin port mode is auto. (A quad is a group of four ports, supported by a data path processor (DPP). The groups are 1 to 4, 5 to 8, 9 to 12, and so on.) Do not leave the port mode set to auto.

a. Set the port admin mode to Fx if the current operational port mode is F or FL. 

switch# config t

switch(config)# interface fc 2/1

switch(config-if)# switchport mode fx

b. Set the port admin mode to E if the current operational port mode is E: 

switch# config t

switch(config)# interface fc 2/5

switch(config-if)# switchport mode e

Step 3 Change the configuration for ports 2, 3, and 4 of the quad:

a. If the admin port mode of these ports is auto or E, change the admin port mode to Fx. 

switch# config t

switch(config)# interface fc 2/2

switch(config-if)# switchport mode fx

b. If the first port in the port group has admin mode E or if the port is operational in E port mode, change the admin state of ports 2, 3, and 4 to shutdown. 

switch# config t

switch(config)# interface fc 2/2

switch(config-if)# shutdown

Step 4 Save the running configuration to the startup configuration before the upgrade procedure to ensure that the changes are preserved during and after the upgrade. To save the configuration, enter the following command: 

switch# copy running-config startup-config

Migrating from Supervisor-1 Modules to Supervisor-2 Modules

As of Cisco MDS SAN-OS Release 3.0(1), the Cisco MDS 9509 and 9506 Directors support both Supervisor-1 and Supervisor-2 modules. Supervisor-1 and Supervisor-2 modules cannot be installed in the same switch, except during migration. Both the active and standby supervisor modules must be of the same type, either Supervisor-1 or Supervisor-2 modules. For Cisco MDS 9513 Directors, both supervisor modules must be Supervisor-2 modules.

Caution Migrating your supervisor modules is a disruptive operation.

Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported.

To migrate from a Supervisor-1 module to a Supervisor-2 module, refer to the step-by-step instructions in the Cisco MDS 9000 Family CLI Configuration Guide.

Configuring Generation 2 Switching Modules

The Cisco MDS 9500 Multilayer Directors are designed to operate with any combination of Cisco MDS 9000 Generation 1 and Generation 2 modules. However, there are limitations to consider when combining the various modules and supervisors in the Cisco MDS 9500 Series platform chassis. The references listed in this section provide specific information about configurations that combine different modules and supervisors.

For information on configuring Generation 2 switching modules, refer to:

http://www.cisco.com/en/US/products/ps5989/products_configuration_guide_chapter09186a0080664c6b.html

For information on port index availability, refer to:

http://www.cisco.com/en/US/products/ps5990/products_installation_guide_chapter09186a0080419599.html

For information on Cisco MDS 9000 hardware and software compatibility, refer to:

http://www.cisco.com/en/US/products/ps5989/products_device_support_table09186a00805037ee.html

Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch

Cisco MDS SAN-OS software upgrades are disruptive on the following single supervisor Cisco MDS Family switches:

•MDS 9120 switch

•MDS 9140 switch

•MDS 9216i switch

If you are performing an upgrade on one of those switches, you should follow the nondisruptive upgrade path listed inthis section, even though the upgrade is disruptive. Following the nondisruptive upgrade path ensures that the binary startup configuration remains intact.

If you do not follow the upgrade path, (for example, you upgrade directly from SAN-OS Release 2.1(2b) to SAN-OS Release 3.0(1)), the binary startup configuration is deleted because it is not compatible with the new image, and the ASCII startup configuration file is applied when the switch comes up with the new upgraded image. When the ASCII startup configuration file is applied, there may be errors. Because of this, we recommend that you follow the nondisruptive upgrade path.

New Features in Cisco MDS SAN-OS Release 3.0(1)

This section lists the new software features in Cisco MDS SAN-OS Release 3.0(1).

FCIP Tape Read Acceleration

Tape drives can have one read I/O command outstanding at a time, which means that increased latency significantly impacts tape read performance. The Fibre Channel over IP (FCIP) tape read acceleration feature improves tape restore operation performance by reading ahead and buffering tape data on the switch. Subsequent tape reads are not impacted by the WAN link latency because the read ahead data is buffered at the switch closest to the host requesting the data.

Fabric Binding for Fibre Channel

Fabric binding ensures Inter-Switch Links (ISLs) are only enabled between specified switches in the fabric binding configuration. Cisco MDS SAN-OS 3.0(1) supports fabric binding for Fibre Channel VSANs as well as FICON VSANs.

FICON Port Swapping Enhancement

Provides the ability to port swap using the interface identifier when there are duplicate port numbers on a switch.

Generation 2 Switching Module Support

The Cisco MDS 9500 Series of switches support the following set of modules called Generation 2 modules.

•DS-X9148 MDS 9000, 48-port 4-Gbps Fibre Channel module.

•DS-X9124 MDS 9000, 24-port 4-Gbps Fibre Channel module.

•DS-X9112 MDS 9000, 12-port 4-Gbps Fibre Channel module.

•DS-X9704 MDS 9000, 4-port 10-Gbps Fibre Channel module.

Detailed information about configuring the new Generation 2 Fibre Channel switching modules is available in the Cisco MDS 9000 Family CLI Configuration Guide and the Cisco MDS 9000 Family Fabric Manager Configuration Guide.

IKE Digital Certificates

The IP security (IPsec) protocol uses the Internet Key Exchange (IKE) protocol to handle protocol and algorithm negotiation and to generate the encryption and authentication keys to be used by IPsec. While IKE can be used with other protocols, its initial implementation is with the IPsec protocol. IKE provides authentication of the IPsec peers, negotiates IPsec security associations, and establishes IPsec keys. IKE uses RFCs 2408, 2409, 2410, and 2412, and implements the draft-ietf-ipsec-ikev2-16.txt draft.

IKE Fully Qualified Domain Names

IKE for IPsec has been enhanced to allow users to enter fully qualified domain names instead of IP addresses.

IKE Host Name Support

An IKE identity host name can be specified instead of an IP address for preshared keys.

IPsec Authentication Enhancements

Certificate Authorities (CAs) manage certificate requests and issue certificates to participating IPsec network devices. When a new device attempts an IPsec connection, certificates are automatically exchanged and the device can be authenticated. Although IPsec can be implemented in your network without the use of a CA, using a CA provides manageability and scalability for IPsec.

IVR Enhancements

Inter-VSAN Routing (IVR) enhancements include the following:

•IVR Service Groups—You can have more than one active IVR service group.

•IVR Zone Renaming—You can rename IVR zones.

•IVR Zone Set Renaming—You can rename IVR zone sets.

•Active IVR Zone Set Copy—You can copy the IVR active zone set to the full IVR zone set to be edited and reactivated.

•Active IVR Topology Copy—You can copy the IVR active topology to the manually configured IVR topology.

FICON Port Numbering

A range of 255 port numbers are available for you to assign to all the ports on a switch. However, you can have more than 255 physical ports on a switch and the excess ports do not have port numbers in the default numbering scheme. When you have more than 255 physical ports on your switch, you can assign unimplemented port numbers (those that are not assigned by default to a slot in the chassis) to the ports, or assign duplicate port numbers if they are not used in the same FICON VSAN.

iSCSI Server Load Balancing (iSLB)

The iSCSI server load balancing (iSLB) feature provides a means to easily configure large scale iSCSI deployments containing hundreds or even thousands of initiators. iSLB provides the following features:

•The iSLB initiator configuration is simplified with support for initiator targets and auto-zones.

•Cisco Fabric Services (CFS) eliminates the need for manual configuration by distributing the iSLB initiator configuration among all MDS switches in the fabric.

•There is dynamic load balancing of iSLB initiators using iSCSI login redirect and VRRP.

iSNS Cloud Discovery

The Internet storage name service (iSNS) cloud discovery feature provides information to the iSNS server on the various interfaces reachable from an initiator by partitioning the interfaces on a switch into disjointed IP clouds. This discovery is achieved by sending messages to all other known IPS ports that are currently up and, depending on the response (or the lack of it), determines if the remote IPS port is in the same IP network or in a different IP network.

The iSNS server distributes cloud and membership information across all the switches using CFS. Therefore, the cloud membership view is the same on all the switches in the fabric.

IPv6

IP version 6 (IPv6) provides extended addressing capability beyond those provided in IP version 4 (IPv4) in Cisco MDS SAN-OS. The architecture of IPv6 has been designed to allow existing IPv4 users to transition easily to IPv6 while providing services such as end-to-end security, quality of service (QoS), and globally unique addresses. IPv6 provides the following enhancements over IPv4:

•Allows networks to scale and provide global reachability.

•Handles packets more efficiently because the IPv6 packet header format is simplified.

•Reduces the need for private address and network address translation (NAT).

•Provides simpler autoconfiguration of addresses.

IPv6 Access Control Lists (IPv6-ACLs)

IP version 6 access control lists (IPv6-ACLs) provide basic network security to all switches in the Cisco MDS 9000 Family. IPv6-ACLs restrict IP-related traffic based on the configured IP filters. A filter contains the rules to match an IP packet, and if the packet matches, the rule also stipulates if the packet should be permitted or denied.

Each switch in the Cisco MDS 9000 Family can have a maximum of 64 IPv6-ACLs and each IPv6-ACL can have a maximum of 256 filters.

CFS Over IP Distribution

Starting with SAN-OS Release 3.0(1), CFS can distribute application data over IP connections. Distribution over IP is transparent to the application, but the application must register with CFS for the application data to be distributed over IP. The following CFS applications register for the CFS-over-IP distribution option: NTP, role, RADIUS, TACACS+, syslogd, and Call Home.

CFS Support for Allowed Domain ID Lists

Allowed domain ID lists can be distributed in the fabric using the CFS infrastructure. There are two obvious benefits:

•Users can save time because they no longer have to enter the same fcdomain command on every switch in a VSAN to configure allowed domains. Instead, users can enter the command once and commit it across the entire fabric.

•Users are less likely to make typing mistakes or to forget to configure a switch—two common mistakes caused by repeated typing of the same command. With CFS, users are guaranteed that the same list of allowed domains is distributed to all switches in the fabric or to no switches in the fabric.

In-Order Delivery Enhancements

In-order delivery (IOD) of data frames guarantees frame delivery to a destination in the same order that they were sent by the originator. If the in-order guarantee feature is enabled, frames are delivered in order within the switch latency drop period. The in-order delivery feature can be enabled for a specific VSAN or for the entire switch.

CLI Enhancements

The Cisco MDS SAN-OS command-line interface (CLI) has been enhanced to support:

•Command variables. You can define variables that persist for the duration of a session or across sessions and switch reloads.

•Common command aliases. You can define command aliases that are global for all user sessions and that persist across reboots.

AAA Server Enhancements

Because an unresponsive AAA server introduces delay in processing of AAA requests, an MDS switch can periodically monitor an AAA server to check whether it is responding (or alive) to save time in processing AAA requests. The MDS switch marks unresponsive AAA servers as dead and does not send AAA requests to any dead AAA servers. An MDS switch periodically monitors dead AAA servers and brings them to the alive state once they are responding. This monitoring process verifies that an AAA server is in a working state before real AAA requests are sent its way. Whenever an AAA server changes to the dead or alive state, an SNMP trap is generated and the MDS switch warns the administrator that a failure is taking place before it can impact performance.

SSH Authentication Enhancements

SSH authentication on the Cisco MDS 9000 Family switches provides X.509 digital certificate support for host authentication. An X.509 digital certificate is a data item that vouches for the origin and integrity of a message. It contains encryption keys for secured communications and is "signed" by a trusted certificate authority (CA) to verify the identity of the presenter. You can configure your switch for either SSH authentication using an X.509 certificate or SSH authentication using a public key certificate, but not both.

Call Home Enhancements

A Call Home alert group can be customized with user-defined show commands whose output can be attached to a Call Home message being sent. Five commands can be specified per alert group.

Online Health Management System Enhancements

The online health management system (OHMS) has been enhanced to provide increased system health capabilities through new loopback testing features. OHMS also includes support for on-board failure logging (OBFL) for Generation 2 modules and loopback enhancements.

McDATA Native Interoperability

Release 3.0(1) includes commands to configure McDATA native mode interoperability.

Increased Zone Limit per VSAN

The maximum number of zones per VSAN has increased from 2000 to 8000. The maximum number of zones in the fabric is 8000.

MS-CHAP

The Microsoft Challenge Handshake Authentication Protocol (MS-CHAP) can be used for user logins to an MDS switch through a remote authentication server (RADIUS or TACACS+). MS-CHAP must be explicitly enabled to be used.

boot auto-copy Command Enabled by Default

The boot auto-copy command is enabled by default.

N-Port Identifier Virtualization

N-port identifier virtualization (NPIV) provides a means to assign multiple port IDs to a single N port. This feature allows multiple applications on the N port to use different identifiers and allows access control, zoning, and port security to be implemented at the application level. NPIV must be globally enabled for all VSANs on the MDS switch to allow the NPIV-enabled applications to use multiple N port FC IDs.

RSCN Timer Configuration

The Registered State Change Notification (RSCN) timer value can be configured per VSAN, and must be the same on all switches in the VSAN. Because the time-out value for each switch is configured manually, a misconfiguration occurs when different switches time out at different times. This misconfiguration means that different N ports in a network can receive RSCNs at different times. The Cisco Fabric Services (CFS) infrastructure alleviates this situation by automatically distributing the RSCN timer configuration information to all switches in a fabric.

Modem Support for Supervisor-2 Modules

There is new information available for configuring modem parameters on Supervisor-2 modules.

Configuration Check

The show incompatibility system command has been modified to indicate the commands to use to disable features before downgrading to an earlier system image.

SMI-S 1.1.0 Support

The Cisco MDS SAN-OS Release 3.0(1) embedded CIM agent is compliant with SMI-S version 1.1.0. The new CIM agent includes a new access point profile.

New SAN-OS MIBs

The following new Management Information Base (MIBs) are available for Cisco MDS SAN-OS Release 3.0(1):

•CISCO-COMMON-MGMT-MIB

•CISCO-IETF-VRRP-MIB

•CISCO-PKI-PARTICIPATION-MIB

Note If you use the CISCO-FICON-MIB, be aware that the MODULE-IDENTITY value has changed in Cisco MDS SAN-OS Release 3.0(1) to CiscoMgmt 375. In SAN-OS Release 2.0(1a) through Release 2.2(1f), the value of MODULE-IDENTITY was CiscoMgmt 88888.

SFP Diagnostic Information

Diagnostic information from small form-factor pluggable (SFP) optical transceivers is supported on the following Cisco MDS 9000 Fibre Channels switching modules:

•Cisco MDS 9000 48-port 4-Gbps Fibre Channel switching module

•Cisco MDS 9000 24-port 4-Gbps Fibre Channel switching module

•Cisco MDS 9000 12-port 4-Gbps Fibre Channel switching module

•Cisco MDS 9000 4-port 10-Gbps Fibre Channel switching module

The SFP diagnostic information enables you to quickly isolate physical layer problems, like contact problems, major failures within SFPs, or abnormal error rates associated with excessive optical attenuation. The following information is provided:

•Temperature

•Voltage and current

•Transmit power level

•Receive power level

Crossbar Management

The Cisco MDS 9500 Series Directors running Cisco MDS SAN-OS Release 3.0(1) or later support the following types of crossbars:

•Integrated crossbar—Located on the Supervisor 1 and Supervisor 2 modules. The Cisco MDS 9506 and 9509 Directors only use integrated crossbars.

•External crossbar—Located on an external crossbar switching module. External crossbar switching modules are required for Cisco MDS 9513 Directors.

You can mix and match Generation 1 and Generation 2 hardware on the Cisco MDS 9500 Series Directors running Cisco MDS SAN-OS Release 3.0(1) or later without compromising the integrity and availability of your SANs based on Cisco MDS 9500 Series Directors. However, to realize these benefits, there are several important operational requirements that you must consider when removing crossbars for maintenance activities. For information about these operational requirements, refer to the Cisco MDS 9000 Family CLI Configuration Guide and the Cisco MDS 9500 Series Hardware Installation Guide.

Fabric Manager Server Enhancements

This section lists the additional enhancements that are available through the the Fabric Manager Server, but not through the command-line interface.

Performance Prediction Trending

A Performance Prediction report in Fabric Manager Server allows you to more reliably predict when storage network connections will become over utilized. You can define the time horizon for the analysis in 3-, 6-, or 12- month intervals and the threshold level. Fabric Manager Server extrapolates the performance and lists in chronological order those interfaces that are expected to reach the threshold level in the specified time horizon.

Configurable RRD

Fabric Manager Server historical performance statistics are stored in a round-robin database (RRD) that holds up to one year of statistics. Performance statistics are rolled up progressively as the data ages to reduce the storage space requirements. The number of samples saved for each resolution can be configured, which allows you to manage the resolution and time period for the Fabric Manager Server historical performance statistics.

Custom Report Performance Chart

Custom reports allow users to optionally embed throughput performance charts for each table entry. If errors or discards are not zero, charts are also included for those statistics.

Server Performance Summary Report

This report allows users to view summary throughput, errors, and discard statistics for all connections on paths from a server to its storage devices, which makes it possible to rapidly pinpoint connectivity problems. The Server Performance Summary Report includes statistics for relevant connections from the server to switch, Inter-Switch Links (ISLs), and switch to storage connections in the paths.

Data Collection Auto-Update

The data collection auto-update feature eliminates most of the manual effort of keeping the Performance Manager data collection configuration up-to-date. Performance data can be collected on all host connections, storage connections, ISLs, and flows. As new host connections, storage connections, or ISLs are added, Fabric Manager Server automatically updates the data collector configuration to include them. Fabric Manager Server also updates the data collection configuration to add Fibre Channel flows, but the new flows must first be created.

Event Forwarding

Events logged by Fabric Manager Server can be forwarded to users through e-mail. All events within specific fabrics or VSANs that are at or above a user-selected severity level are forwarded. Multiple destinations can be configured to receive the e-mail. In addition, users can be paged by sending the e-mail to a paging gateway.

Filtering by User-Defined Groups

You can now define custom groups that contain switches, hosts, or storage devices. These groups filter out information that is not relevant to the group on the Cisco Fabric Manager topology map, in information tables (switch parameters), and in Fabric Manager Server reports. These groups supplement the existing user-defined grouping capabilities for creating host or storage enclosures.

SNMP over TCP/IP

SNMP messages can be transported over TCP rather than UDP for management traffic on the out-of-band Gigabit Ethernet management port (mgmt0).

EMC Call Home

Traps can be forwarded as XML data usin