MDS 9000 Family Release Notes
for Cisco MDS NX-OS Release 6.2(7)
Release Date: March 31, 2014
Part Number: OL-29201-03
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 “Obtaining Documentation and Submitting a
Service Request” section on page 52.
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/ps5989/prod_release_notes_list.html
Table 1 shows the online change history for this document.
Table 1
Online History Change
Revision
Date
Description
A0
March 31, 2014
Created the release notes.
B0
April 4, 2014
Added open caveats CSCuo00701 and CSCun82838.
C0
May 13, 2014
Added open caveats CSCun56276 and CSCuo24658.
D0
June 14, 2014
E0
July 11, 2014
•
Update the General Upgrading Guidelines section
•
Added open caveat CSCub40020.
Added open caveat CSCva31989.
Contents
This document includes the following:
•
Introduction, page 2
•
Components Supported, page 2
•
MDS 9000 Chassis and Module Support, page 10
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Introduction
•
Software Download Process, page 14
•
Upgrading Your Cisco MDS NX-OS Software Image, page 18
•
Downgrading Your Cisco MDS SAN-OS Software Image, page 23
•
New Software Features in Cisco NX-OS Release 6.2(7), page 26
•
Licensed Cisco NX-OS Software Packages, page 29
•
Limitations and Restrictions, page 31
•
Caveats, page 32
•
Obtaining Documentation and Submitting a Service Request, page 52
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.
Cisco MDS 9000 NX-OS software powers the award-winning Cisco MDS 9000 Series Multilayer
Switches. It is designed to create a strategic SAN platform with superior reliability, performance,
scalability, and features. Formerly known as Cisco SAN-OS, Cisco MDS 9000 NX-OS software is fully
interoperable with earlier Cisco SAN-OS versions and enhances hardware platform and module support.
Components Supported
Table 2 lists the NX-OS software part numbers and hardware components supported by the Cisco MDS
9000 Family.
Note
Table 2
For the latest information about supported transceivers, see the Cisco MDS 9000 Family Pluggable
Transceivers data sheet.
Cisco MDS 9000 Family Supported Software and Hardware Components
Componen
t
Part Number
Description
Applicable Product
Software
M97S3K9-6.2.7
MDS 9700 Supervisor/Fabric-1, NX-OS software
MDS 9710 Switch
M95S2K9-6.2.7
MDS 9500 Supervisor/Fabric-2, NX-OS software
MDS 9500 Series only
M92S3K9-6.2.7
MDS 9200 Supervisor/Fabric-1, NX-OS software
MDS 9250i Switch
M92S2K9-6.2.7
MDS 9200 Supervisor/Fabric-2, NX-OS software
MDS 9222i Switch
M91S3K9-6.2.7
MDS 9148 Supervisor/Fabric-3 NX-OS software
MDS 9148 Switch
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
2
OL-29201-03
Components Supported
Table 2
Cisco MDS 9000 Family Supported Software and Hardware Components (continued)
Componen
t
Part Number
Licenses
Description
Applicable Product
M9500SSE184K9z
Storage Services Enabler License for one MSM-18/4
module
MDS 9500 Series only
M9200ENT1K9
Cisco MDS 9200 Series Enterprise Package
MDS 9200 Series only
DCNM-SAN-M92-K9
Cisco Prime Data Center Network Manager
MDS 9250i Switch only
M9250IIOA
Cisco MDS 9250i I/O Accelerator Services package
MDS 9250i Switch only
M9250IDMMK9
Cisco MDS 9250i Data Mobility Manager package
MDS 9250i Switch only
M9250IDMMT6M
Cisco MDS 9250i DMM License - 6-month period
M9200FIC1K9 Cisco MDS 9200 Series Mainframe
Package
MDS 9250i Switch only
M9200XRC
Cisco MDS 9200 XRC Acceleration Package for IBM
series z, spare
MDS 9250i Switch only
M9222ISSE1K9
Storage Services Enabler License
MDS 9222i Switch only
M9200SSE184K9
Storage Services Enabler License for one MSM-18/4
module
MDS 9200 Series only
M95DMM184K9
Data Mobility Manager License for one MSM-18/4
module
MDS 9500 Series only
M9222IDMMK9
Data Mobility Manager License for Cisco MDS 9222i
MDS 9222i Switch
M92DMM184K9
Data Mobility Manager License for one MSM-18/4
module
MDS 9200 Series only
M95DMM184TSK9
Data Mobility Manager for one MSM-18/4 module —
Time limited to 180 days only
MDS 9500 Series only
M9222IDMMTSK9
Data Mobility Manager — Time limited to 180 days only MDS 9222i Switch only
M92DMM184TSK9
Data Mobility Manager for one MSM-18/4 module —
Time limited to 180 days only
MDS 9200 Series only
M92SSESSNK9
Cisco Storage Services Enabler License for SSN-16
(1 engine)
MDS 9200 Series only
M95SSESSNK9
Cisco Storage Services Enabler License for SSN-16
(1 engine)
MDS 9500 Series only
M92SMESSNK9
Cisco Storage Media Encryption License for SSN-16
(1 engine)
MDS 9200 Series only
M95SMESSNK9
Cisco Storage Media Encryption License for SSN-16
(1 engine)
MDS 9500 Series only
M92IOASSN
Cisco I/O Accelerator License for SSN-16 (1 engine)
MDS 9200 Series only
M95IOASSN
Cisco I/O Accelerator License for SSN-16 (1 engine)
MDS 9500 Series only
M92IOA184
Cisco I/O Accelerator License for MSM-18/4
MDS 9200 Series only
M95IOA184
Cisco I/O Accelerator License for MSM-18/4
MDS 9500 Series only
M9222IIOA
Cisco I/O Accelerator License for Cisco MDS 9222i base MDS 9222i Switch only
switch
M92EXTSSNK9
Cisco SAN Extension License for SSN-16 (1 engine)
MDS 9200 Series only
M95EXTSSNK9
Cisco SAN Extension License for SSN-16 (1 engine)
MDS 9500 Series only
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
3
Components Supported
Table 2
Cisco MDS 9000 Family Supported Software and Hardware Components (continued)
Componen
t
Part Number
Chassis
Supervisor
Modules
Description
Applicable Product
DS-C9710
Cisco MDS 9710 Multilayer Director (10-slot multilayer MDS 9710 switch
director with 2 half-width slots for Supervisor 1 modules,
with 8 slots available for switching modules — SFPs sold
separately)
DS-C9513
Cisco MDS 9513 Multilayer Director (13-slot multilayer MDS 9513 Switch
director with 2 slots for Supervisor-2 modules, with 11
slots available for switching modules — SFPs sold
separately)
DS-C9509
Cisco MDS 9509 Multilayer Director (9-slot multilayer MDS 9509 Switch
director with 2 slots for Supervisor modules, with 7 slots
available for switching modules — SFPs sold separately)
DS-C9506
Cisco MDS 9506 Multilayer Director (6-slot multilayer MDS 9506 Switch
director with 2 slots for Supervisor modules, with 4 slots
available for switching modules — SFPs sold separately)
DS-C9250I-K9
The Cisco MDS 9250i offers up to forty 16-Gbps Fibre
Channel ports, two 10 Gigabit Ethernet IP storage
services ports, and eight 10 Gigabit Ethernet Fibre
Channel over Ethernet (FCoE) ports in a fixed
two-rack-unit (2RU) form factor.
DS-C9222i-K9
Cisco MDS 9222i Multilayer Fabric Switch (3-rack-unit MDS 9222i Switch
(3RU) semimodular multilayer fabric switch with 18
4-Gbps Fibre Channel ports, 4 Gigabit Ethernet ports, and
a modular expansion slot for Cisco MDS 9000 Family
Switching and Services modules)
DS-C9148-K9
Cisco MDS 9148 48-Port Multilayer Fabric Switch (1RU MDS 9148 Switch
fixed-configuration multilayer fabric switch with 48
8-Gbps Fibre Channel ports)
DS-X97-SF1-K9
Cisco MDS 9700 Series Supervisor-1 Module
MDS 9700 Series
DS-X9530-SF2-K9
Cisco MDS 9500 Series Supervisor-2 Module
MDS 9500 Series
DS-X9530-SF2A-K9
Cisco MDS 9500 Series Supervisor-2A Module
MDS 9500 Series
MDS 9250i Switch
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
4
OL-29201-03
Components Supported
Table 2
Cisco MDS 9000 Family Supported Software and Hardware Components (continued)
Componen
t
Part Number
Description
Applicable Product
Switching
Modules
DS-X9448-768K9
Cisco MDS 9000 48-port 16-Gbps Fibre Channel
Switching Module with SFP LC connectors
MDS 9710 Switch
DS-X9848-480K9
Cisco MDS 48-Port 10-Gigabit Fibre Channel over
Ethernet (FCoE) Module with SFP LC connectors
MDS 9710 Switch
DS-X9112
Cisco MDS 9000 12-port 4-Gbps Fibre Channel
Switching Module with SFP LC connectors
MDS 9500 Series
Cisco 24-port 4-Gbps Fibre Channel Switching Module
with SFP LC connectors
MDS 9500 Series
Cisco MDS 9000 48-port 4-Gbps Fibre Channel
Switching Module with SFP LC
MDS 9500 Series
Cisco MDS 9000 Family 4-Port 10-Gbps Fibre Channel
Switching Module with SFP LC
MDS 9500 Series
DS-X9224-96K9
Cisco MDS 9000 24-Port 8-Gbps Fibre Channel
Switching Module with SFP and SFP+ LC connectors
MDS 9500 Series
DS-X9248-96K9
Cisco MDS 9000 48-Port 8-Gbps Fibre Channel
Switching Module with SFP and SFP+ LC connectors
MDS 9500 Series
DS-X9248-48K9
Cisco MDS 9000 4/44-Port Host-Optimized 8-Gbps Fibre MDS 9500 Series
Channel Switching Module with SFP and SFP+ LC
MDS 9222i Switch
connectors
DS-X9708-K9
Cisco MDS 9000 8-port 10-Gbps Fibre Channel over
Ethernet (FCoE) Module
MDS 9500 Series
DS-X9232-256K9
Cisco MDS 9000 32-port 8-Gbps Advanced Fibre
Channel Switching Module
MDS 9500 Series
DS-X9248-256K9
Cisco MDS 9000 48-port 8-Gbps Advanced Fibre
Channel Switching Module
MDS 9500 Series
DS-X9316-SSNK9
Cisco MDS 9000 Family 16-Port Storage Services Node
(SSN-16) — 16 fixed 1-Gbps Ethernet ports, plus 4
service engines that support 16 Gigabit Ethernet IP
storage services ports.
MDS 9500 Series
DS-X9124
DS-X9148
DS-X9704
Services
Modules
External
crossbar
module
MDS 9200 Series
MDS 9200 Series
MdS 9200 Series
MDS 9200 Series
MDS 9222i Switch
DS-X9304-18K9
MDS 9500 Series
Cisco MDS 9000 18/4-Port Multiservice Module
(MSM-18/4) — 18-port, 4-Gbps Fibre Channel plus
MDS 9200 Series
4-port Gigabit Ethernet IP services and switching module
with SFP LC connectors
DS-X9710-FAB1
Cisco MDS 9710 Crossbar Switching Fabric 1 Module
MDS 9710 Switch
DS-13SLT-FAB2
Cisco MDS 9513 Switching Fabric 2 Module
MDS 9513 Switch
DS-13SLT-FAB3
Cisco MDS 9513 Switching Fabric 3 Module
MDS 9513 Switch
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
5
Components Supported
Table 2
Cisco MDS 9000 Family Supported Software and Hardware Components (continued)
Componen
t
Part Number
Description
Applicable Product
DS-CAC-300W
300W AC power supply
MDS 9100 Series
DS-C24-300AC
300W AC power supply
MDS 9124 Switch
DS-CAC-845W
845W AC power supply for Cisco MDS 9200 Series
MDS9200 Series
DS-C50I-300AC
300W AC power supply
MDS 9250i Switch
DS-CAC-3000W
3000W AC power supply for Cisco MDS 9509
MDS 9509 Switch
DS-CAC-2500W
2500W AC power supply
MDS 9509 Switch
DS-CDC-2500W
2500W DC power supply
MDS 9509 Switch
DS-CAC-6000W
6000W AC power supply for Cisco MDS 9513
MDS 9513 Switch
DS-CAC-1900W
1900W AC power supply for Cisco MDS 9506
MDS 9506 Switch
CompactFl
ash
MEM-MDS-FLD512M
External 512-MB CompactFlash memory for supervisor
module
MDS 9500 Series
Port
Analyzer
Adapter
DS-PAA-2, DS-PAA
Standalone Fibre Channel-to-Ethernet adapter that allows MDS 9000 Family
for simple, transparent analysis of Fibre Channel traffic in
a switched fabric
Power
Supplies
Smart Card DS-SCR-K9
Reader
Storage Media Encryption (SME) Smart Card Reader
MDS 9000 Family
Smart Card DS-SC-K9
SME Smart Card
MDS 9000 Family
Table 3 lists the part numbers and optical components supported by the Cisco MDS 9000 Family.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
6
OL-29201-03
Components Supported
Table 3
Cisco MDS 9000 Family Supported Optics and Transceivers
Component Part Number
Description
Applicable Product
Optics
SFP-10G-SR /
DS-SFP-10GE-SR
10GBASE-SR SFP+ Module
MDS 9710,
MDS 9500 Series,
8-port 10-Gbps FCoE Module
(DS-X9708-K9),
MDS 9250i
SFP-10G-SR /
DS-SFP-10GE-LR
10GBASE-LR SFP+ Module
MDS 9710,
MDS 9500 Series,
8-port 10-Gbps FCoE Module
(DS-X9708-K9), MDS 9250i
SFP-10G-ER
10GBASE-ER SFP+ Module
MDS 9710,
MDS 9500 Series,
8-port 10-Gbps FCoE Module
(DS-X9708-K9),
MDS 9250i
SFP-H10GB-CU1M
10GBASE-CU SFP+ cable 1 meter
MDS 9500 Series,
8-port 10-Gbps FCoE Module
(DS-X9708-K9)
SFP-H10GB-CU3M
10GBASE-CU SFP+ cable 3 meter
MDS 9500 Series,
8-port 10-Gbps FCoE Module
(DS-X9708-K9)
SFP-H10GB-CU5M
10GBASE-CU SFP+ cable 5 meter
MDS 9500 Series,
8-port 10-Gbps FCoE Module
(DS-X9708-K9)
SFP-H10GB-ACU7M
10GBASE-CU SFP+ active copper
cable 7 meter
MDS 9500 Series,
8-port 10-Gbps FCoE Module
(DS-X9708-K9)
SFP-H10GB-ACU10M
10GBASE-CU SFP+ active copper
cable 10 meter
MDS 9500 Series,
8-port 10-Gbps FCoE Module
(DS-X9708-K9)
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
7
Components Supported
Table 3
Cisco MDS 9000 Family Supported Optics and Transceivers (continued)
Component Part Number
Description
Applicable Product
LC-type
fiber-optic
SFP
DS-SFP-FC16G-SW
SFP+ optics (LC type) for 16-Gbps
Fibre Channel for shortwave mode
MDS 9710, 48-port 16-Gbps Fibre Channel
Switching Module (DS-X9448-768K9),
MDS 9250i
DS-SFP-FC16G-LW
SFP+ optics (LC type) for 10-Gbps
Fibre Channel for longwave mode
MDS 9710, 48-port 16-Gbps Fibre Channel
Switching Module (DS-X9448-768K9),
MDS 9250i
DS-SFP-FC10G-SW
SFP+ optics (LC type) for 10-Gbps
Fibre Channel for shortwave mode
48-port 16-Gbps Fibre Channel Switching
Module (DS-X9448-768K9),
32-port 8-Gbps Advanced Fibre Channel
Module (DS-X9232-256K9),
48-port 8-Gbps Advanced Fibre Channel
Module (DS-X9248-256-K9)
DS-SFP-FC10G-LW
SFP+ optics (LC type) for 10-Gbps
Fibre Channel for longwave mode
48-port 16-Gbps Fibre Channel Switching
Module (DS-X9448-768K9),
32-port 8-Gbps Advanced Fibre Channel
Module (DS-X9232-256K9),
48-port 8-Gbps Advanced Fibre Channel
Module (DS-X9248-256-K9)
DS-SFP-FC8G-ER
SFP+ optics (LC type) for 2-, 4-, or
8-Gbps Fibre Channel for extended
reach (40 km reach)
MDS DS-X9200 Series switching modules,
MDS 9148
MDS 9250i
DS-SFP-FC8G-SW
SFP+ optics (LC type) for 2-, 4-, or MDS 9710,
8-Gbps Fibre Channel for shortwave MDS DS-X9200 Series switching modules,
mode
MDS 9250i
DS-SFP-FC8G-LW
SFP+ optics (LC type) for 2-, 4-, or MDS 9710,
8-Gbps Fibre Channel for longwave MDS DS-X9200 Series switching modules,
mode; supports distances up to 10 km MDS 9250i
DS-SFP-FC4G-SW
MDS 9124, MDS 9134, MDS 9148, MDS
SFP optics (LC type) for 1-, 2-, or
4-Gbps Fibre Channel for shortwave 9222i, DS-X9100, and DS-X9200 Series
switching modules
mode
DS-SFP-FC4G-MR
SFP optics (LC type) for 1-, 2-, or
MDS 9124, MDS 9134, MDS 9222i,
4-Gbps Fibre Channel for longwave DS-X9100, and DS-X9200 Series switching
mode; supports distances up to 4 km modules
DS-SFP-FC4G-LW
SFP optics (LC type) for 1-, 2-, or
MDS 9124, MDS 9134, MDS 9222i,
4-Gbps Fibre Channel for longwave DS-X9100, and DS-X9200 Series switching
mode; supports distances up to 10 km modules
DS-SFP-FCGE-SW
MDS 9000 Series
SFP optics (LC type) for 1-Gbps
Ethernet and 1- or 2-Gbps Fibre
Channel for shortwave mode; not for
use in 4-Gbps-capable ports
DS-SFP-FCGE-LW
MDS 9000 Series
SFP optics (LC type) for 1-Gbps
Ethernet and 1- or 2-Gbps Fibre
Channel for longwave mode; not for
use in 4-Gbps-capable ports
DS-SFP-GE-T
SFP (RJ-45 connector) for Gigabit
Ethernet over copper
MDS 9000 Series
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
8
OL-29201-03
Components Supported
Table 3
Cisco MDS 9000 Family Supported Optics and Transceivers (continued)
Component Part Number
Description
DS-CWDM-xxxx
Cisco
Coarse
Wavelength
- Division
Multiplexin
g (CWDM) DS-CWDM4Gxxxx
MDS 9000 Family
CWDM Gigabit Ethernet and 1- or
2-Gbps Fibre Channel SFP LC type,
where product number xxxx = 1470,
1490, 1510, 1530, 1550, 1570, 1590,
or 1610 nm
DWDM-X2-xx.xx
Dense
Wavelength
- Division
Multiplexin
g (DWDM)
MDS 9500 Series
DWDM X2 SC optics for 10-Gbps
Fibre Channel connectivity to an
MDS 9200 Series
existing Ethernet DWDM
infrastructure, with 15xx.xx nm
wavelength, where xx.xx = 60.61,
59.79, 58.98, 58.17, 56.55, 55.75,
54.94, 54.13, 52.52, 51.72, 50.92,
50.12, 48.51, 47.72, 46.92, 46.12,
44.53, 43.73, 42.94, 42.14, 40.56,
39.77, 38.98, 38.19, 36.61, 35.82,
35.04, 34.25, 32.68, 31.90, 31.12, or
30.33
DWDM-SFP-xxxx
Applicable Product
CWDM 4-Gbps Fibre Channel SFP MDS 9000 Family
LC type, where product number xxxx
= 1470, 1490, 1510, 1530, 1550,
1570, 1590, or 1610 nm
MDS 9000 Family
DWDM Gigabit Ethernet and 1- or
2-Gbps Fibre Channel SFP LC type,
where product number xxxx = 3033,
3112, 3190, 3268, 3425, 3504, 3582,
3661, 3819, 3898, 3977, 4056, 4214,
4294, 4373, 4453, 4612, 4692, 4772,
4851, 5012, 5092, 5172, 5252, 5413,
5494, 5575, 5655, 5817, 5898, 5979,
or 6061nm
DWDM-SFP10G-xx.xx 10GBASE-DWDM SFP+
Add/Drop
DS-CWDMOADM4A
Multiplexer
(ADM)
4-channel CWDM optical ADM
(OADM) module (Cisco CWDM
1470, 1490, 1510, or 1530 NM
Add/Drop Module)
MDS 9710 Director
MDS 9000 Family
DS-CWDMOADM4B
4-channel CWDM OADM module
MDS 9000 Family
(Cisco CWDM 1550, 1570, 1590, or
1610 NM Add/Drop Module)
DS-CWDM-MUX8A
ADM for 8 CWDM wavelengths
MDS 9000 Family
CWDM
DS-CWDMCHASSIS
Multiplexer
Chassis
2-slot chassis for CWDM ADMs
MDS 9000 Family
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
9
MDS 9000 Chassis and Module Support
MDS 9000 Chassis and Module Support
Table 4 lists the MDS hardware chassis supported by Cisco MDS NX-OS Release 6.2 7.
Table 4
Cisco MDS NX-OS 6.2 Chassis Support Matrix
Switch
NX-OS Release 6.2 Support
MDS 9710
Yes
MDS 9513
Yes
MDS 9509
Yes
MDS 9506
Yes
MDS 9250i
Yes1
MDS 9222i
Yes
MDS 9148
Yes
Cisco MDS 8-Gb Fabric Switch for HP c-Class Blade System
Yes
MDS 9134
No
MDS 9124
No
Cisco MDS 4-Gbps Fabric Switch for HP c-Class BladeSystem
No
Cisco MDS 4-Gbps Fabric Switch for IBM BladeCenter
No
1. This switch supports Cisco MDS NX-OS Release supports Release 6.2(5) and later.
Table 5 lists the MDS hardware chassis supported by Cisco MDS NX-OS Release 5.x.
Table 5
Cisco MDS NX-OS 5.x Chassis Support Matrix
Switch
NX-OS Release 5.x Support
MDS 9513
Yes
MDS 9509
Yes
MDS 9506
Yes
MDS 9222i
Yes
MDS 9216i
No
MDS 9148
Yes
Cisco MDS 8-Gb Fabric Switch for HP c-Class Blade System
Yes
MDS 9134
Yes1
MDS 9124
Yes1
Cisco MDS 4-Gbps Fabric Switch for HP c-Class BladeSystem
Yes1
Cisco MDS 4-Gbps Fabric Switch for IBM BladeCenter
Yes1
1. This switch supports Cisco MDS NX-OS Release 5.2(2) and later 5.x releases, but does not support Release 6.2(x).
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
10
OL-29201-03
MDS 9000 Chassis and Module Support
Table 6 lists the MDS hardware modules supported Cisco MDS NX-OS Release 6.2 Table 7 lists the
MDS hardware modules supported by Cisco MDS NX-OS 5.x. For the list of MDS hardware modules
supported by Cisco MDS SAN-OS 4.x, see Table 8. For the list of MDS hardware modules supported by
Cisco MDS SAN-OS 3.x, see Table 9.
Table 6
Module Support Matrix for Cisco MDS NX-OS Release 6.2
Module
Description
MDS 9700 Series
MDS 9500 Series
MDS 9200 Series
DS-X97-SF1-K9
MDS 9700 Supervisor-1 Module
Yes
N/A
N/A
DS-X9710-FAB1
MDS 9710 Fabric1 Module
Yes
N/A
N/A
DS-X9448-768K9
48-Port 16-Gbps Fibre Channel
Switching Module
Yes
No
No
DS-X9848-480K9
Cisco MDS 48-Port 10-Gigabit
Fibre Channel over Ethernet
Module
Yes
No
No
DS-X9530-SF2-K9
MDS 9500 Supervisor-2 Module
N/A
Yes
N/A
DS-X9530-SF2A-K9
MDS 9500 Supervisor-2A Module N/A
Yes
N/A
DS-13SLT-FAB3
MDS 9513 Fabric Module 3
N/A
Yes
N/A
DS-13SLT-FAB2
MDS 9513 Fabric Module 2
N/A
Yes
N/A
DS-13SLT-FAB1
MDS 9513 Fabric Module 1
N/A
Yes
DS-X9708-K9
8-port 10-Gbps FCoE Module
No
N/A
Yes
1,2
No
1
No
DS-X9232-256K9
32-port 8-Gbps Advanced Fibre
Channel Switching Module
No
Yes
DS-X9248-256K9
48-port 8-Gbps Advanced Fibre
Channel Switching Module
No
Yes1
No
DS-X9224-96K9
24-port 8-Gbps Fibre Channel
Switching Module
No
Yes3
No
DS-X9248-96K9
48-port 8-Gbps Fibre Channel
Switching Module
No
Yes3
No
DS-X9248-48K9
4/44-port Host Optimized 8-Gbps
Fibre Channel Switching Module
No
Yes
Yes
DS-X9316-SSNK9
16-port Storage Services Node
(SSN-16)
No
Yes
Yes
DS-X9304-18K9
18/4-Port Multiservice Module
(MSM-18/4)
No
Yes
Yes
DS-X9112
12-port 4-Gbps Fibre Channel
Switching Module
No
Yes
Yes
DS-X9124
24-port 4-Gbps Fibre Channel
Switching Module
No
Yes
Yes
DS-X9148
48-port 4-Gbps Fibre Channel
Switching Module
No
Yes
Yes
DS-X9704
4-port 10-Gbps Fibre Channel
Switching Module
No
Yes
Yes
1. Requires DS-13SLT-FAB3 or DS-13SLT-FAB2 in the MDS 9513.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
11
MDS 9000 Chassis and Module Support
2. Requires the Supervisor-2A module.
3. Requires DS-13SLT-FAB2 in the MDS 9513.
Table 7
Module Support Matrix for Cisco MDS NX-OS 5.x
Module
Description
MDS 9500 Series
MDS 9222i
NX-OS
5.2(x)
NX-OS
5.0(x)
NX-OS 5.2(x)
NX-OS 5.0(x)
DS-X9530-SF2-K9
MDS 9500 Supervisor-2
Module
Yes
Yes
N/A
N/A
DS-X9530-SF2A-K9
MDS 9500 Supervisor-2A
Module
Yes
Yes
N/A
N/A
DS-13SLT-FAB3
MDS 9513 Fabric Module 3
Yes
No
N/A
N/A
DS-13SLT-FAB2
MDS 9513 Fabric Module 2
Yes
Yes
N/A
N/A
DS-13SLT-FAB1
MDS 9513 Fabric Module 1
No
Yes
N/A
N/A
1,2
No
No
No
DS-X9232-256K9
32-port 8-Gbps Advanced Fibre Yes
Channel Switching Module
1
No
No
No
DS-X9248-256K9
48-port 8-Gbps Advanced Fibre Yes1
Channel Switching Module
No
No
No
DS-X9224-96K9
24-port 8-Gbps Fibre Channel
Switching Module
Yes1
Yes3
No
No
DS-X9248-96K9
48-port 8-Gbps Fibre Channel
Switching Module
Yes1
Yes3
No
No
DS-X9248-48K9
4/44-port Host Optimized
8-Gbps Fibre Channel
Switching Module
Yes
Yes
Yes
Yes
DS-X9316-SSNK9
16-port Storage Services Node
(SSN-16)
Yes
Yes
Yes
Yes
DS-X9304-18K9
18/4-Port Multiservice Module
(MSM-18/4)
Yes
Yes
Yes
Yes
DS-X9112
12-port 4-Gbps Fibre Channel
Switching Module
Yes
Yes
Yes
Yes
DS-X9124
24-port 4-Gbps Fibre Channel
Switching Module
Yes
Yes
Yes
Yes
DS-X9148
48-port 4-Gbps Fibre Channel
Switching Module
Yes
Yes
Yes
Yes
DS-X9704
4-port 10-Gbps Fibre Channel
Switching Module
Yes
Yes
Yes
Yes
DS-X9708-K9
8-port 10-Gbps FCoE Module
Yes
1. Requires DS-13SLT-FAB3 or DS-13SLT-FAB2 in the MDS 9513.
2. Requires the Supervisor-2A module.
3. Requires DS-13SLT-FAB2 in the MDS 9513.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
12
OL-29201-03
MDS 9000 Chassis and Module Support
Table 8
Module Support Matrix for Cisco MDS NX-OS 4.x
Module
Description
MDS 9500
Series
MDS 9222i
MDS 9216i
DS-X9530-SF2-K9
MDS 9500 Supervisor-2 Module
Yes
N/A
N/A
N/A
N/A
1
DS-X9530-SF2A-K9
MDS 9500 Supervisor-2A Module
Yes
DS-X9530-SF1-K9
MDS 9500 Supervisor-1 Module
No
N/A
N/A
DS-13SLT-FAB2
MDS 9513 Fabric Module 2
Yes
N/A
N/A
DS-13SLT-FAB1
MDS 9513 Fabric Module 1
Yes
DS-X9224-96K9
24-port 8-Gbps Fibre Channel Switching Module
N/A
N/A
Yes
2
No
No
2
No
No
DS-X9248-96K9
48-port 8-Gbps Fibre Channel Switching Module
Yes
DS-X9248-48K9
4/44-port Host Optimized8-Gbps Fibre Channel
Switching Module
Yes
Yes
No
DS-X9316-SSNK9
16-port Storage Services Node (SSN-16)
Yes
Yes
Yes
DS-X9304-18K9
18/4-Port Multiservice Module (MSM-18/4)
Yes
Yes
Yes
DS-X9112
12-port 4-Gbps Fibre Channel Switching Module
Yes
Yes
Yes
DS-X9124
24-port 4-Gbps Fibre Channel Switching Module
Yes
Yes
Yes
DS-X9148
48-port 4-Gbps Fibre Channel Switching Module
Yes
Yes
Yes
DS-X9704
4-port 10-Gbps Fibre Channel Switching Module
Yes
Yes
Yes
DS-X9302-14K9
14/2-port Multiprotocol Services (MPS-14/2)
Module
Yes
No
Yes
DS-X9016
16-port 1-, 2-Gbps Fibre Channel Switching
Module
Yes
No
Yes
DS-X9032
32-port 1-, 2-Gbps Fibre Channel Switching
Module
Yes
No
Yes
DS-X9032-SSM
32-port Storage Services Module (SSM)
Yes
Yes
Yes
DS-X9308-SMIP
8-port 1-, 2-Gbps IP Switching Module
No
No
No
DS-X9304-SMIP
4-port 1-, 2-Gbps IP Switching Module
No
No
No
1. In software releases earlier than Cisco NX-OS Release 4.2(7a), the Supervisor-2A module appears as unsupported hardware in Device Manager, but the
Supervisor-2A module does work with Cisco NX-OS release 4.x software.
2. Requires DS-13SLT-FAB2 in the MDS 9513.
Table 9 lists the MDS hardware modules supported by Cisco MDS SAN-OS 3.x.
Table 9
Module Support Matrix for Cisco MDS SAN-OS 3.x
Module
Description
MDS 9500 MDS
Series
9222i
MDS
9216i
MDS
9216A
MDS
9216
DS-X9530-SF2-K9
MDS 9500 Supervisor-2 Module
Yes
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module
Yes
DS-X9530-SF1-K9
Yes
MDS 9500 Supervisor-1 Module
1
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
13
Software Download Process
Table 9
Module Support Matrix for Cisco MDS SAN-OS 3.x (continued)
Module
Description
MDS 9500 MDS
Series
9222i
MDS
9216i
MDS
9216A
MDS
9216
DS-13SLT-FAB2
MDS 9513 Fabric Module 2
Yes
N/A
N/A
N/A
N/A
DS-13SLT-FAB1
MDS 9513 Fabric Module 1
Yes
N/A
N/A
N/A
N/A
DS-X9224-96K9
24-port 8-Gbps Fibre Channel Switching
Module
No
No
No
No
No
DS-X9248-96K9
48-port 8-Gbps Fibre Channel Switching
Module
No
No
No
No
No
DS-X9248-48K9
4/44-port Host Optimized 8-Gbps Fibre
Channel Switching Module
No
No
No
No
No
DS-X9316-SSNK9
16-port Storage Services Node (SSN-16)
No
No
No
No
No
DS-X9304-18K9
18/4-Port Multiservice Module
(MSM-18/4)2
Yes
Yes
Yes
Yes
No
DS-X9112
12-port 4-Gbps Fibre Channel Switching
Module
Yes
Yes
Yes
Yes
No
DS-X9124
24-port 4-Gbps Fibre Channel Switching
Module
Yes
Yes
Yes
Yes
No
DS-X9148
48-port 4-Gbps Fibre Channel Switching
Module
Yes
Yes
Yes
Yes
No
DS-X9704
4-port 10-Gbps Fibre Channel Switching
Module
Yes
Yes
Yes
Yes
No
DS-X9302-14K9
14/2-port Multiprotocol Services
(MPS-14/2) Module
Yes
No
Yes
Yes
Yes
DS-X9016
16-port 1-, 2-Gbps Fibre Channel Switching Yes
Module
No
Yes
Yes
Yes
DS-X9032
32-port 1-, 2-Gbps Fibre Channel Switching Yes
Module
No
Yes
Yes
Yes
DS-X9032-SSM
32-port Storage Services Module (SSM)
Yes
Yes
Yes
Yes
Yes
DS-X9308-SMIP
8-port 1-, 2-Gbps IP Switching Module
Yes
No
Yes
Yes
Yes
DS-X9304-SMIP
4-port 1-, 2-Gbps IP Switching Module
Yes
Yes
Yes
Yes
Yes
1. In software releases earlier than Cisco NX-OS Release 3.3(5a), the Supervisor-2A module appears as unsupported hardware in Device Manager, but the
Supervisor-2A module does work with Cisco NX-OS release 3.x software.
2. Cisco SAN-OS Release 3.2(1) and later support the 18/4-Port Multiservice Module (MSM-18/4).
Software Download Process
Use the software download procedure to upgrade to a later version, or downgrade to an earlier version,
of an operating system. This section describes the software download process for the Cisco MDS NX-OS
software and includes the following topics:
•
Determining the Software Version, page 15
•
Determining Software Version Compatibility, page 15
•
Downloading Software, page 15
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
14
OL-29201-03
Software Download Process
•
Selecting the Software Image for an MDS 9148 Switch, page 16
•
Selecting the Software Image for an MDS 9222i Switch, page 16
•
Selecting the Software Image for an MDS 9500 Series Switch, page 17
•
Selecting the Software Image for an MDS 9710 Switch, page 17
•
NPE Software Images, page 17
Determining the Software Version
To determine the version of Cisco MDS NX-OS or 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 NX-OS or SAN-OS software currently running on a Cisco MDS
9000 Family switch using Cisco DCNM for SAN, 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.
Determining Software Version Compatibility
Table 10 lists the software versions that are compatible in a mixed SAN environment, the minimum
software versions that are supported, and the versions that have been tested. We recommend that you use
the latest software release supported by your vendor for all Cisco MDS 9000 Family products.
Table 10
Software Release Compatibility
Cisco NX-OS Software
Minimum NX-OS or SAN-OS
Release
Tested NX-OS and SAN-OS
Release
NX-OS Release 6.2(7)
NX-OS Release 6.2(5a) or later
NX-OS Release 6.2(5a) or later
NX-OS Release 6.2(5) or later
NX-OS Release 6.2(5) or later
NX-OS Release 6.2(3) or later
NX-OS Release 6.2(3) or later
NX-OS Release 6.2(1) or later
NX-OS Release 6.2(1) or later
NX-OS Release 5.2(x) or later
NX-OS Release 5.2(x) or later
NX-OS Release 5.0(1a) and later NX-OS Release 5.0(1a) and later
NX-OS Release 4.2(3) and later
NX-OS Release 4.2(3) and later
SAN-OS Release 3.3(5) and later SAN-OS Release 3.3(5) and later
Downloading Software
The Cisco MDS NX-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.
To download the latest Cisco MDS NX-OS software, access the Software Center at this URL:
http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
15
Software Download Process
See the following sections in this release note for details on how you can nondisruptively upgrade your
Cisco MDS 9000 switch. Issuing the install all command from the CLI, or using Cisco DCNM for SAN
to perform the downgrade, enables the compatibility check. The check indicates if the upgrade can
happen nondisruptively or disruptively depending on the current configuration of your switch and the
reason.
Compatibility check is done:
Module bootable
Impact
------ -------- -------------1
yes non-disruptive
2
yes
disruptive
3
yes
disruptive
4
yes non-disruptive
5
yes non-disruptive
6
yes non-disruptive
Install-type
-----------rolling
rolling
rolling
rolling
reset
reset
Reason
-----Hitless upgrade is not supported
Hitless upgrade is not supported
The show incompatibility system bootflash:system image filename command determines which
additional features need to be disabled.
Note
If you would like to request a copy of the source code under the terms of either GPL or LGPL, please
send an e-mail to [email protected].
Selecting the Software Image for an MDS 9148 Switch
The system and kickstart image that you use for an MDS 9148 switch is shown in Table 11.
Table 11
Software Images for MDS 9148 Switches
Cisco MDS 9148 Switch
Naming Convention
MDS 9148,
Cisco MDS 8Gb Fabric Switch for HP
c-Class BladeSystem
Filename begins with m9100-s3ek9
Selecting the Software Image for an MDS 9222i Switch
The system and kickstart image that you use for an MDS 9222i switch is shown in Table 12.
Table 12
Software Images for MDS 9222i Switch
Cisco MDS 92221 Switch
Naming Convention
MDS 9222i
Filename begins with m9200-s2ek9
Selecting the Software Image for an MDS 9250i Switch
The system and kickstart image that you use for an MDS 9250i switch is shown in Table 13.
Table 13
Software Images for MDS 9250i Switch
Cisco MDS 9250i Switch
Naming Convention
MDS 9250i
Filename begins with m9250-s5ek9
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
16
OL-29201-03
Software Download Process
Selecting the Software Image for an MDS 9500 Series Switch
The system and kickstart image that you use for an MDS 9500 Series switch with a Supervisor-2 or
Supervisor-2A module is shown in Table 14. Cisco NX-OS Release 6.x, Release 5.x, and Release 4.x do
not support the Supervisor-1 module.
Table 14
Software Images for MDS 9500 Series Switches
Cisco MDS 9500 Series Switch Type
Naming Convention
MDS 9513, 9509, and 9506
Filename begins with m9500-sf2ek9
Use the show module command to display the type of supervisor module in the switch. The following
is sample output from the show module command on a Supervisor-2 module:
switch# show module
Mod Ports Module-Type
--- ----- -------------------------------...
...
7
0
Supervisor/Fabric-2
8
0
Supervisor/Fabric-2
Model
Status
------------------ ------------
DS-X9530-SF2-K9
DS-X9530-SF2-K9
active *
ha-standby
Selecting the Software Image for an MDS 9710 Switch
The system and kickstart image that you use for an MDS 9710 switch is shown in Table 15.
Table 15
Software Images for MDS 9710 Switch
Cisco MDS 9710 Switch
Naming Convention
MDS 9710
Filename begins with m9700-sf3ek9
NPE Software Images
No payload encryption (NPE) images are available with Cisco MDS NX-OS Release 6.2(7) software.
The NPE images are intended for countries who have import restrictions on products that encrypt
payload data.
To differentiate an NPE image from the standard software image, the letters npe are included in the
image name as follows:
•
m9100-s3ek9-kickstart-mz-npe.6.2.7.bin
•
m9100-s3ek9-mz-npe.6.2.7.bin
•
m9200-s2ek9-kickstart-mz-npe.6.2.7.bin
•
m9200-s2ek9-mz-npe.6.2.7.bin
•
m9250-s5ek9-kickstart-mz-npe.6.2.7.bin
•
m9250-s5ek9-mz-npe.6.2.7.bin
•
m9500-sf2ek9-kickstart-mz-npe.6.2.7.bin
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
17
Upgrading Your Cisco MDS NX-OS Software Image
•
m9500-sf2ek9-mz-npe.6.2.7.bin
•
m9700-sf3ek9-kickstart-mz-npe.6.2.7.bin
•
m9700-sf3ek9-mz-npe.6.2.7.bin
When downloading software, ensure that you select the correct software images for you Cisco MDS
9000 Series switch. Nondisruptive software upgrades or downgrades between NPE images and non-NPE
images are not supported.
Upgrading Your Cisco MDS NX-OS Software Image
This section lists the guidelines recommended for upgrading your Cisco MDS NX-OS software image
and includes the following topics:
Note
•
General Upgrading Guidelines, page 18
•
Nondisruptive Upgrade Paths, page 20
•
FICON Supported Releases and Upgrade Paths, page 22
Before you begin the upgrade process, review the list of chassis and modules that Cisco MDS NX-OS
Release 6.2(7) supports. See the “MDS 9000 Chassis and Module Support” section on page 10.
For detailed instructions for performing a software upgrade using Cisco DCNM, see the Cisco DCNM
Release Notes, Release 6.2, which is available from the following website:
http://www.cisco.com/en/US/products/ps10495/prod_release_notes_list.html
General Upgrading Guidelines
Before upgrading your Cisco NX-OS software, you must determine if the following issue has occurred
in your switch:
%FLOGI-1-MSG_FLOGI_REJECT_FCID_ERROR after upgrade/switchover
An ISSU or ISSD involves a supervisor switchover, so it is very important that you determine if this issue
is present before a supervisor switchover occurs. If this issue is detected before the supervisor
switchover, the affected interfaces can be restored easily by entering the shutdown and no shutdown
command sequence.
The following example shows how to determine if the issue has occurred before a supervisor switchover:
switch# show flogi internal info | i key|Interface | i key p 1
Interface fc4/32: mode[F] [119f000] Mode: F State: UP Vsan: 237
Vsan no:237 Max flogi key:0x1002a(65578) num_fl[0x1]<<<Max flogi key greater than 65535
-Interface fc6/32: mode[F] [129f000] Mode: F State: UP Vsan: 237
Vsan no: 237 Max flogi key: 0x1(1) num_fl[0x1]
--
Look for the value for a Max flogi key that is greater than 65535.
In the example, the fc4/32 interface has encountered this issue, but the fc6/32 interface is normal.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
18
OL-29201-03
Upgrading Your Cisco MDS NX-OS Software Image
If you see that an interface has a Max flogi key greater than 65535 before a system switchover, ISSU, or
ISSD, you must disable the interface and then reenable it by using the shutdown command followed by
the no shutdown command. This process disrupts the devices on the interface that is being shut down.
After the devices relogin, the Max flogi key is reset to 1 and you can avoid this issue.
If an install and/or ISSU, or supervisor switchover has occurred, compare the number of devices fabric
login (FLOGI) with the number of devices in the Fibre Channel Name Server (FCNS) local database.
Enter the show flogi database and the show fcns database local commands and use the CLI outputs for
comparison. If the FLOGI database has fewer entries than the FCNS local database, the issue has
occurred.
Also, if the following error message appears after an install, ISSU, or supervisor switchover, the issue
might bug may have been encountered:
%FLOGI-1-MSG_FLOGI_REJECT_FCID_ERROR: %$VSAN xxx%$ [VSAN xxx, Interface fc4/19: mode[F]]
FLOGI rejected - FCID allocation failed with error 0x401b0000.
If you observe either of the above situations, open a case with the Cisco TAC.
Note
If the Max flogi key value is a large number and is incrementing, it indicates that a device is repeatedly
logging in. This situation might be a separate problem that needs further investigation. For assistance,
contact the Cisco TAC.
In addition, follow these general guidelines before performing a software upgrade:
•
Review the nondisruptive upgrade path to Release 6.2(7) in Table 16.
•
Install and configure dual supervisor modules before the upgrade.
•
Issue the show install all impact upgrade-image CLI command to determine if your upgrade will
be nondisruptive.
•
Be aware that some features impact whether an upgrade is disruptive or nondisruptive:
– Fibre Channel Ports: Fibre Channel ports can be nondisruptively upgraded without affecting
traffic on the ports. See Table 16 for the nondisruptive upgrade path for all NX-OS and SAN-OS
releases.
– Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during an upgrade or
downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MSM-18/4 module
and the MDS 9222i and MDS 9250i switch. Those nodes that are members of VSANs traversing
an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the
Gigabit Ethernet ports lose connectivity to iSCSI targets while the upgrade is in progress.
– FICON: If you have FICON enabled, the upgrade path is different. See the “FICON Supported
Releases and Upgrade Paths” section on page 22.
Note
In addition to these guidelines, you may want to review the information in the “Limitations and
Restrictions” section prior to a software upgrade to determine if a feature may possibly behave
differently following the upgrade.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
19
Upgrading Your Cisco MDS NX-OS Software Image
Nondisruptive Upgrade Paths
Use Table 16 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 6.2(7). Find
the image release number you are currently using in the “Current Release” column of the table and
follow the steps in the order specified to perform the upgrade.
Note
The software upgrade information in Table 16 applies only to Fibre Channel switching traffic.
Upgrading system software disrupts IP traffic and intelligent services traffic.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
20
OL-29201-03
Upgrading Your Cisco MDS NX-OS Software Image
Table 16
Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 6.2(7)
Current Release
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
Upgrade directly to NX-OS Release 6.2(7).
Release 6.2(5a),
6.2(5), 6.2(3),
6.2(1), 5.2(1),
5.2(2), 5.2(2a),
5.2(2d), 5.2(6),
5.2(6a), 5.2(6b),
5.2(8), 5.2(8a),
5.2(8b), 5.2(8c),
5.2(8d), and 5.2(8e)
All 5.0(x) releases
All 4.2(x) releases
and 4.1(x) releases
1.
Upgrade to NX-OS Release 5.2(x).
2.
Upgrade to NX-OS Release 6.2(7).
1.
Upgrade to NX-OS Release 5.0(8a).
2.
Upgrade to NX-OS Release 5.2(x).
3.
Upgrade to NX-OS Release 6.2(7).
1.
Upgrade to NX-OS Release 4.2(9).
2.
Upgrade to NX-OS Release 5.0(8a).
3.
Upgrade to NX-OS Release 5.2(x).
4.
Upgrade to NX-OS Release 6.2(7).
1.
Upgrade to SAN-OS Release 3.3(5b).
2.
Upgrade to NX-OS Release 4.2(9).
3.
Upgrade to NX-OS Release 5.0(8a).
4.
Upgrade to NX-OS Release 5.2(x).
5.
Upgrade to NX-OS Release 6.2(7).
1.
Upgrade to SAN-OS Release 3.3(1c).
2.
Upgrade to SAN-OS Release 3.3(5b).
3.
Upgrade to NX-OS Release 4.2(9).
4.
Upgrade to NX-OS Release 5.0(8a).
5.
Upgrade to NX-OS Release 5.2(x).
6.
Upgrade to NX-OS Release 6.2(7).
SAN-OS:
Release 3.3(2),
3.3(3), 3.3(4x), and
3.3(5x).
Release 3.3(1c), all
3.2(x), 3.1(x), and
3.0(x) releases)
Release 2.1(3),
2.1(2e), 2.1(2d), and
2.1(2b)
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
21
Upgrading Your Cisco MDS NX-OS Software Image
Table 16
Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 6.2(7) (continued)
Current Release
Nondisruptive Upgrade Path and Ordered Upgrade Steps
Release 2.1(2),
2.1(1b), 2.1(1a), and
2.0(x)
1.
Upgrade to SAN-OS Release 2.1(2b), 2.1(2d), 2.1(2e), or 2.1(3)
2.
Upgrade to SAN-OS Release 3.3(1c).
3.
Upgrade to SAN-OS Release 3.3(5b).
4.
Upgrade to NX-OS Release 4.2(9).
5.
Upgrade to NX-OS Release 5.0(8a).
6.
Upgrade to NX-OS Release 5.2(x).
7.
Upgrade to NX-OS Release 6.2(7).
1.
Upgrade to SAN-OS Release 1.3(4a).
2.
Upgrade to SAN-OS Release 2.1(2b).
3.
Upgrade to SAN-OS Release 3.3(1c).
4.
Upgrade to SAN-OS Release 3.3(5b).
5.
Upgrade to NX-OS Release 4.2(9).
6.
Upgrade to NX-OS Release 5.0(8a).
7.
Upgrade to NX-OS Release 5.2(x).
8.
Upgrade to NX-OS Release 6.2(7).
Release 1.x
FICON Supported Releases and Upgrade Paths
Cisco MDS NX-OS Release 6.2(7) is not a FICON-certified release.
Table 17 lists the SAN-OS and NX-OS releases that are certified for FICON. Refer to the specific release
notes for FICON upgrade path information.
Table 17
FICON Supported Releases
FICON Supported Releases
NX-OS
Release 6.2(5a)
Release 5.2(2)
Release 4.2(7b)
Release 4.2(1b)
Release 4.1(1c)
SAN-OS
Release 3.3(1c)
Release 3.2(2c)
Release 3.0(3b)
Release 3.0(3)
Release 3.0(2)
Release 2.0(2b)
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
22
OL-29201-03
Downgrading Your Cisco MDS SAN-OS Software Image
Use Table 18 to determine the nondisruptive upgrade path for FICON-certified releases. Find the image
release number you are currently using in the Current Release with FICON Enabled column of the table
and follow the recommended path.
Table 18
FICON Nondisruptive Upgrade Path
Current Release with
FICON Enabled
Upgrade Path
NX-OS Release 4.2(7b)
You can nondisruptively upgrade directly to NX-OS Release 5.2(2).
NX-OS Release 4.2(1b)
You can nondisruptively upgrade directly to NX-OS Release 4.2(7b).
NX-OS Release 4.1(1c)
You can nondisruptively upgrade directly to NX-OS Release 4.2(1b).
SAN-OS Release 3.3(1c)
You can nondisruptively upgrade directly to NX-OS Release 4.2(1b).
SAN-OS Release 3.2(2c),
3.0(3b), 3.0(3), and 3.0(2).
First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS
Release 4.2(1b).
Downgrading Your Cisco MDS SAN-OS Software Image
This section lists the guidelines recommended for downgrading your Cisco MDS SAN-OS software
image and includes the following topics:
•
Guidelines for Downgrading from Cisco MDS NX-OS Release 6.2(7) to Cisco MDS NX-OS
Release 6.2(5a), 6.2(5), 6.2(3), or 6.2(1), page 22
•
General Downgrading Guidelines, page 23
•
FICON Downgrade Paths, page 25
General Downgrading Guidelines
Follow these general guidelines before you perform a software downgrade:
•
Issue the system no acl-adjacency-sharing execute command to disable ACL adjacency usage on
Generation 2 modules. If this command fails, reduce the number of zones, IVR zones, TE ports, or
a combination of these in the system and issue the command again.
•
Disable all features not supported by the downgrade release. Use the show incompatibility system
downgrade-image command to determine what you need to disable.
•
Use the show install all impact downgrade-image command to determine if your downgrade will
be nondisruptive.
•
Be aware that some features impact whether a downgrade is disruptive or nondisruptive:
– Fibre Channel Ports: Fibre Channel ports can be nondisruptively downgraded without
affecting traffic on the ports. See Table 19 for the nondisruptive downgrade path for all SAN-OS
releases.
– Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during a downgrade.
This includes IPS modules and the Gigabit Ethernet ports on the MSM-18/4 module, and the
MDS 9222i switch. Those nodes that are members of VSANs traversing an FCIP ISL are
impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit
Ethernet ports lose connectivity to iSCSI targets while the downgrade is in progress.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
23
Downgrading Your Cisco MDS SAN-OS Software Image
– FICON: If you have FICON enabled, the downgrade path is different. See the “FICON
Downgrade Paths” section on page 25.
Use Table 19 to determine the nondisruptive downgrade path from Cisco NX-OS Release 6.2(7). Find
the NX-OS or SAN-OS image that you want to downgrade to in the To SAN-OS Release column of the
table and follow the steps in the order specified to perform the downgrade.
Note
The software downgrade information in Table 19 applies only to Fibre Channel switching traffic.
Downgrading system software disrupts IP and intelligent services traffic.
Note
Downgrading from Cisco MDS NX-OS Release 6.2(7) to Cisco MDS NX-OS Release 6.2(5a), 6.2(5),
6.2(3), or 6.2(1) on a Cisco MDS 9710 Director with 48-port 10-Gigabit FCoE module or VSAN
configurations require additional steps that must be performed before downgrading. For more
information, see Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide, Release 6.2(x).
Table 19
Nondisruptive Downgrade Path from NX-OS Release 6.2(7)
To NX-OS or
SAN-OS Release
Nondisruptive Downgrade Path and Ordered Downgrade Steps
NX-OS:
Downgrade directly from NX-OS Release 6.2(7).
Release 6.2(5a),
6.2(5), 6.2(3), 6.2(1),
5.2(1), 5.2(2), 5.2(2a),
5.2(2d), 5.2(6),
5.2(6a), 5.2(6b), and
5.2(8), 5.2(8a),
5.2(8b), 5.2(8c),
5.2(8d), and 5.2(8e)
All 5.0(x) releases
All 4.2(x) and 4.1(x)
releases
1.
Downgrade from NX-OS Release 6.2(7).
2.
Downgrade to NX-OS Release 5.2(x).
3.
Downgrade to NX-OS Release 5.0(x).
1.
Downgrade from NX-OS Release 6.2(7).
2.
Downgrade to NX-OS Release 5.2(x).
3.
Downgrade to NX-OS Release 5.0(x).
4.
Downgrade to NX-OS Release 4.2(x) or 4.1(x).
1.
Downgrade from NX-OS Release 6.2(7).
2.
Downgrade to NX-OS Release 5.2(x).
3.
Downgrade to NX-OS Release 5.0(x).
4.
Downgrade to NX-OS Release 4.2(x) or Release 4.1(x).
5.
Downgrade to SAN-OS Release 3.3(x).
SAN-OS:
All 3.3(x) releases
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
24
OL-29201-03
Downgrading Your Cisco MDS SAN-OS Software Image
Table 19
Nondisruptive Downgrade Path from NX-OS Release 6.2(7) (continued)
To NX-OS or
SAN-OS Release
All 3.2(x), 3.1(x),
3.0(x) releases, and all
2.1(x) releases.
All 2.0(x) releases.
Release 1.x
Nondisruptive Downgrade Path and Ordered Downgrade Steps
1.
Downgrade from NX-OS Release 6.2(7).
2.
Downgrade to NX-OS Release 5.2(x).
3.
Downgrade to NX-OS Release 5.0(x).
4.
Downgrade to NX-OS Release 4.2(x) or Release 4.1(x).
5.
Downgrade to SAN-OS Release 3.3(x).
6.
Downgrade to SAN-OS Release 3.2(x), Release 3.1(x)., Release 3.0(x), or
Release 2.1(x).
1.
Downgrade from NX-OS Release 6.2(7).
2.
Downgrade to NX-OS Release 5.2(x).
3.
Downgrade to NX-OS Release 5.0(x).
4.
Downgrade to NX-OS Release 4.2(x) or Release 4.1(x).
5.
Downgrade to SAN-OS Release 3.3(x).
6.
Downgrade to SAN-OS Release 2.1(2x).
7.
Downgrade to SAN-OS Release 2.0(x).
1.
Downgrade from NX-OS Release 6.2(7).
2.
Downgrade to NX-OS Release 5.2(x).
3.
Downgrade to NX-OS Release 5.0(x).
4.
Downgrade to NX-OS Release 4.2(x) or Release 4.1(x).
5.
Downgrade to SAN-OS Release 3.3(x).
6.
Downgrade to SAN-OS Release 2.1(2b).
7.
Downgrade to SAN-OS Release 1.3(4a).
8.
Downgrade to SAN-OS Release 1.x.
FICON Downgrade Paths
Table 20 lists the downgrade paths for FICON releases. Find the image release number that you want to
downgrade to in the To Release with FICON Enabled column of the table and follow the recommended
downgrade path.
Table 20
FICON Downgrade Path
To Release with FICON Enabled
Downgrade Path
NX-OS Release 5.2(2)
You can nondisruptively downgrade directly from NX-OS Release 6.2(5a)
NX-OS Release 4.2(7b)
You can nondisruptively downgrade directly from NX-OS Release 5.2(2).
NX-OS Release 4.2(1b)
You can nondisruptively downgrade directly from NX-OS Release 4.2(7b).
NX-OS Release 4.1(1c)
You can nondisruptively downgrade directly from NX-OS Release 4.2(1b).
SAN-OS 3.3(1c)
You can nondisruptively downgrade directly from NX-OS Release 4.1(1c).
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
25
New Hardware in Cisco MDS NX-OS Release 6.2(7)
Table 20
FICON Downgrade Path
To Release with FICON Enabled
Downgrade Path
SAN-OS 3.2(2c)
First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.2(2c).
SAN-OS 3.0(3b)
First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.0(3b).
SAN-OS 3.0(2)
First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.0(2).
New Hardware in Cisco MDS NX-OS Release 6.2(7)
This section briefly describes the new hardware introduced in Cisco NX-OS Release 6.2(7). For detailed
information about the new hardware, see the Cisco MDS 9250i Hardware Installation Guide that is
available from this URL:
http://www.cisco.com/en/US/partner/products/ps5989/prod_installation_guides_list.html
Cisco MDS 48-Port 10-Gigabit Fibre Channel over Ethernet Module
Ethernet Module
The Cisco MDS 48-Port 10-Gigabit Fibre Channel over Ethernet Module (DS-X9848-480K9) is
designed for the Cisco MDS 9710 Directors. The Cisco MDS 9710 Director supports up to eight 10
Gigabit Ethernet modules. These modules are hot-swappable and they support 10-Gigabit Ethernet ports
in SFP+ form factor.
The Cisco MDS 48-Port 10-Gigabit Ethernet module delivers integrated Fibre Channel over Ethernet
(FCoE), simplifies the network infrastructure and helps reduce costs. The FCoE module allows you to
extend the existing Fibre Channel SANs by using FCoE. The Cisco MDS 48-Port 10-Gigabit Ethernet
module supports connectivity to FCoE switching platforms and to FCoE devices. This module also
supports connectivity to FCoE initiators and targets that only send FCoE traffic.
New Software Features in Cisco NX-OS Release 6.2(7)
This section briefly describes the new software features introduced in Cisco NX-OS Release 6.2(7).
•
Enhanced the scalability for zones, maximum devices in the fabric and maximum devices in the
switch.
•
Forward Error Correction (FEC) for 16-Gbps ISL connections
•
Enhanced scalability for simultaneous FLOGIs for Cisco MDS 9500 Series switches
•
Restriction of the number of NPIV logins to not exceed the configuration limits in for Cisco MDS
9500 Series switches
•
Command-line interface (CLI) command changes, including the following:
– fcns bulk-notify
– rscn coalesce swrscn vsan
– switchport (added the max-npiv-limit and trunk-max-npiv-limit keyword.)
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
26
OL-29201-03
New Hardware in Cisco MDS NX-OS Release 6.2(5)
– switchport fec
– system port pacer mode F interface-login-threshold
– show fabric switch information vsan
New Hardware in Cisco MDS NX-OS Release 6.2(5)
This section briefly describes the new hardware introduced in Cisco NX-OS Release 6.2(5). For detailed
information about the new hardware, see the Cisco MDS 9250i Hardware Installation Guide that is
available from this URL:
http://www.cisco.com/en/US/partner/products/ps5989/prod_installation_guides_list.html
Cisco MDS 9250i Multiservice Fabric Switch
The Cisco MDS 9250i Multiservice Fabric Switch (DS-C9250I-K9) is an optimized platform for
deploying high-performance SAN extension solutions, distributed intelligent fabric services, and
cost-effective multiprotocol connectivity for both open systems and mainframe environments.
The Cisco MDS 9250i switch is an ideal solution for local office and remote branch-office SANs and
also in large-scale SANs operating the Cisco MDS 9700 and 9500 Series Multilayer director platforms.
The Cisco MDS 9250i switch offers 40 autosensing 2-, 4-, 8-, and 16-Gbps line-rate Fibre Channel ports,
eight 10-Gigabit Ethernet Fibre Channel over Ethernet (FCoE) ports, and two 10-Gigabit Ethernet IP
storage services ports in a fixed two-rack-unit (2RU) form factor.
New Software Features in Cisco NX-OS Release 6.2(5)
This section briefly describes the new software features introduced in Cisco NX-OS Release 6.2(5).
•
DMM support for Cisco MDS 9250i switch
•
FCIP support for Cisco MDS 9250i switch
•
FCR support for Cisco MDS 9250i switch
•
IOA support for Cisco MDS 9250i switch
•
Path Trace
•
Command-line interface (CLI) command changes, including the following:
– Changed the CLI output for the show ioa cluster flows command.
– Introduced the ioa-ping command.
– Introduced the ability to display IOA engine utilization.
– Introduced the ability to display hosts and targets by device alias in IOA.
New Software Features in Cisco NX-OS Release 6.2(3)
This section briefly describes the new software features introduced in Cisco NX-OS Release 6.2(3).
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
27
New Software Features in Cisco NX-OS Release 6.2(1)
•
Cisco MDS Data Mobility Manager (DMM) supports logical unit numbers (LUN) sizes that are
larger than 2 terabyte. The supported number of sessions per DMM job is more than 255. For more
information, see the Cisco MDS 9000 Family Data Mobility Manager Configuration Guide.
•
FC-Redirect (FCR) support for Cisco MDS 9710 Director. For more information on IOA, see the
Cisco MDS 9000 Family I/O Accelerator Configuration Guide. For more information on SME, see
the Cisco MDS 9000 Family Storage Media Encryption Configuration Guide.
•
Command-line interface (CLI) command changes, including the following:
– Changed the CLI output for the show fcdomain vsan command.
– Deprecated the show interface counters performance command.
New Software Features in Cisco NX-OS Release 6.2(1)
This section briefly describes the new software features introduced in Cisco NX-OS Release 6.2(1).
•
Generic Online Diagnostics
Starting with Cisco NX-OS Release 6.2(1), the Cisco MDS 9000 Family supports the generic online
diagnostics (GOLD) feature. With online diagnostics, you can test and verify the hardware
functionality of a device while the device is connected to a live network. In particular, the online
diagnostics help you verify that hardware and internal data paths are operating as designed so that
you can rapidly isolate faults.
For more information about this feature, see the Cisco MDS 9000 System Management
Configuration Guide at this URL:
http://www.cisco.com/en/US/products/ps5989/products_installation_and_configuration_guides_lis
t.html
•
Enhancement to map LDAP/AD users to Cisco NX-OS roles and allow both local and remote users
to use SSH or Telnet.
For more information about this feature, see the Cisco MDS 9000 Security Configuration Guide, at
this URL:
http://www.cisco.com/en/US/products/ps5989/products_installation_and_configuration_guides_lis
t.html
•
Command-line interface (CLI) command changes, including the following:
– Enhance the clear snmp counters command.
– Display ISL related information.
– Display a warning messages for a shared port interface when you bring down the port.
– Display throughput information for all ports on a line card or ISL or on a switch or chassis.
– Provide an estimated time for DMM job completion.
– Shorten the show dmm job job-id 50571379 session session_id (1-20) command to show dmm
job-id 50571379 session_id 1
Information about the modified CLI commands can be found in the Cisco MDS 9000 Command
Reference at this URL:
http://www.cisco.com/en/US/products/ps5989/prod_command_reference_list.html
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
28
OL-29201-03
Licensed Cisco NX-OS Software Packages
Licensed Cisco NX-OS Software Packages
Most Cisco MDS 9000 family software features are included in the standard package. However, some
features are logically grouped into add-on packages that must be licensed separately, such as the Cisco
MDS 9000 Enterprise package, SAN Extension over IP package, Mainframe package, and Data Mobility
Manager package. On-demand ports activation licenses are also available for the Cisco MDS 9250i
Multiservice Fabric Switch, Cisco MDS 9148 48-Port Multilayer Fabric Switch, and the Cisco MDS
8-Gb Fabric Switch for HP c-Class Blade System.
Note
A license is not required to use the Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE)
module (DS-X9708-K9) and the Cisco MDS 48-Port 10- Gigabit Fibre Channel over Ethernet Module
(DS-X9848-480K9).
Additional information about licensed Cisco NX-OS software packages is available at this URL:
http://www.cisco.com/en/US/partner/products/ps6029/products_data_sheets_list.html
Enterprise Package
The standard software package that is bundled at no charge with the Cisco MDS 9000 Family switches
includes the base set of features that Cisco believes are required by most customers for building a SAN.
The Cisco MDS 9000 family also has a set of advanced features that are recommended for all enterprise
SANs. These features are bundled together in the Cisco MDS 9000 Enterprise package. Refer to the
Cisco MDS 9000 Enterprise package fact sheet for more information.
SAN Extension over IP Package
The Cisco MDS 9000 SAN Extension over IP package allows the customer to use FCIP to extend SANs
over wide distances on IP networks using the Cisco MDS 9000 family IP storage services. Refer to the
Cisco MDS 9000 SAN Extension over IP package fact sheet for more information.
Mainframe Package
The Cisco MDS 9000 Mainframe package uses the FICON protocol and allows control unit port
management for in-band management from IBM S/390 and z/900 processors. FICON VSAN support is
provided to help ensure true hardware-based separation of FICON and open systems. Switch cascading,
fabric binding, and intermixing are also included in this package. Refer to the Cisco MDS 9000
Mainframe package fact sheet for more information.
Data Mobility Manager Package
The Cisco MDS 9000 Data Mobility Manager package enables data migration between heterogeneous
disk arrays without introducing a virtualization layer or rewiring or reconfiguring SANs. Cisco DMM
allows concurrent migration between multiple LUNs of unequal size. Rate-adjusted migration, data
verification, dual Fibre Channel fabric support, and management using Cisco DCNM for SAN provide
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
29
Deprecated and Changed Features
a complete solution that greatly simplifies and eliminates most downtime associated with data migration.
Refer to the Cisco MDS 9000 Data Mobility Manager package fact sheet for more information. The Data
Mobility Manager package is for use only with Cisco MDS 9000 Family switches.
On-Demand Port Activation License
On-demand ports allow customers to benefit from Cisco NX-OS Software features while initially
purchasing only a small number of activated ports on the Cisco MDS 9250i Multiservice Fabric Switch,
MDS 9148 48-Port Multilayer Fabric Switch, and the Cisco MDS 8-Gb Fabric Switch for HP c-Class
Blade System. As needed, customers can expand switch connectivity by licensing additional ports.
I/O Accelerator Package
The Cisco I/O Accelerator (IOA) package activates IOA on the Cisco MDS 9222i fabric switch, the
Cisco MDS 9000 18/4 Multiservice Module (MSM-18/4), and on the SSN-16 module. The IOA package
is licensed per service engine and is tied to the chassis. The number of licenses required is equal to the
number of service engines on which the intelligent fabric application is used.The SSN-16 requires a
separate license for each engine on which you want to run IOA. Each SSN-16 engine that you configure
for IOA checks out a license from the pool managed at the chassis level. SSN-16 IOA licenses are
available as single licenses.
XRC Acceleration License
The Cisco Extended Remote Copy (XRC) acceleration license activates FICON XRC acceleration on the
Cisco MDS 9222i switch and on the MSM-18/4 in the Cisco MDS 9500 Series directors. One license per
chassis is required. You must install the Mainframe Package and the SAN Extension over FCIP Package
before you install the XRC acceleration license. The Mainframe Package enables the underlying FICON
support, and the FCIP license or licenses enable the underlying FCIP support.
Deprecated and Changed Features
Zoning Features
LUN zoning, read-only zones, and broadcast zones are no longer supported. These features affect the
following hardware:
•
Cisco MDS 9250i Multiservice Fabric Switch
•
Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) Module
•
Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching Module
•
Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching Module
•
Cisco MDS 9000 48-port 16-Gbps Fibre Channel Switching Module
You cannot bring up these modules if these features are already configured. You should completely
remove all configurations that include these features before you attempt to bring up these modules. In
addition, you cannot configure these features after you bring up these modules.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
30
OL-29201-03
Limitations and Restrictions
In addition, the following software features are not supported or are changed in Cisco MDS NX-OS
Release 6.2(5a):
Note
•
Fibre Channel Security Protocol (FC-SP) is currently not supported on the Cisco MDS 9710
Director and on Cisco MDS 9250i Multiservice Fabric Switch.
•
Local switching is not supported on the Cisco MDS 9710 Director, but continues to be supported on
the Cisco MDS 9500 Series.
•
Online Health Management System (OHMS)—The Generic Online Diagnostics (GOLD) system
provides diagnostics for the Cisco MDS 9710 Director instead of the OHMS. In Cisco NX-OS
Release 6.2(5), the GOLD system does not provide any support for automation of corrective actions,
such as rebooting modules based on error thresholds.
OHMS is supported on Cisco MDS 9500 Series directors, Cisco MDS 9250i Multiservice Fabric Switch,
and Cisco MDS 9148 Multilayer Fabric Switch.
Cisco NX-OS Release 6.2(5) does not support the following hardware:
•
Cisco MDS 9134 Fabric Switch
•
Cisco MDS 9124 Fabric Switch
•
Cisco MDS 4-Gbps Fabric Switch for HP c-Class BladeSystem
•
Cisco MDS 4-Gbps Fabric Switch for IBM BladeCenter
Limitations and Restrictions
This section lists the limitations and restrictions. The following limitations are described:
•
ASCII File Can Be Copied to the Startup Configuration, page 31
•
Fibre Channel Security Protocol (FC-SP) Not Supported, page 31
•
Install Module Command Changes, page 32
•
Fabric Binding Error Message, page 32
•
IOA Scaling Support on Supervisor-2 Module, page 32
ASCII File Can Be Copied to the Startup Configuration
The copy bootflash:runnig-config.ascii startup-config command that was deprecated in an earlier
Cisco NX-OS release is enabled from Cisco NX-OS Release 6.2(1).
Fibre Channel Security Protocol (FC-SP) Not Supported
Cisco NX-OS Release 6.2(1) does not support the Fibre Channel Security Protocol (FC-SP) feature only
on the Cisco MDS 9710 Director.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
31
Caveats
Install Module Command Changes
The install module module-number bios command is not supported on the Cisco MDS 9710 switch in
Cisco NX-OS Release 6.2(1) and later releases. Use the install all command to upgrade the BIOS during
a software upgrade.
The install module module-number bios command continues to be supported in Cisco NX-OS Release
6.2(1) on Cisco MDS 9500 Series switches.
Fabric Binding Error Message
When fabric binding is enabled, an error message appears whenever the Mainframe Package license is
not installed, and also when the grace period is disabled. There is a functional impact associated with
the error message, and the feature is enabled correctly.
IOA Scaling Support on Supervisor-2 Module
In Cisco MDS NX-OS Release 6.2(5), I/O Accelerator (IOA) scaling is supported only on the
Supervisor-2A module and is not supported on the Supervisor-2 module.
Caveats
This section lists the open and resolved caveats for this release. Use Table 21 to determine the status of
a particular caveat. In the table, “O” indicates an open caveat and “R” indicates a resolved caveat.
Table 21
Open Caveats and Resolved Caveats Reference
NX-OS Software Release
(Open or Resolved)
NX-OS Software Release
(Open or Resolved)
6.2(5)
6.2(7)
CSCty82906
O
O
CSCue64981
O
R
CSCug22090
O
O
CSCuh37423
O
O
CSCui52280
O
O
CSCuj09522
O
O
CSCuj94303
O
O
CSCul12775
O
O
CSCul13809
O
O
CSCul64626
—
O
CSCum30306
O
O
CSCum87393
—
O
DDTS Number
Severity 2
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
32
OL-29201-03
Caveats
Table 21
Open Caveats and Resolved Caveats Reference (continued)
NX-OS Software Release
(Open or Resolved)
NX-OS Software Release
(Open or Resolved)
6.2(5)
6.2(7)
CSCun04994
—
O
CSCun11007
—
O
CSCun59595
—
O
CSCun76030
—
O
CSCun84332
—
O
CSCuo00701
—
O
CSCuo24658
O
O
CSCuo82450
O
O
CSCur81171
—
O
CSCuq64102
O
O
CSCuq98083
O
O
CSCuw82693
O
O
CSCuu76450
O
O
CSCub40020
O
O
CSCuf64822
O
O
CSCug14717
O
R
CSCug83123
O
O
CSCuh05972
O
O
CSCuh49283
O
O
CSCuh93233
O
R
CSCui21601
O
O
CSCuj42921
O
O
CSCuj68267
O
O
CSCuj77722
O
R
CSCuj83626
O
R
CSCuj99534
O
O
CSCul08289
O
O
CSCul46007
O
R
CSCul65496
O
O
CSCun29631
—
O
CSCun56276
—
O
CSCun82838
—
O
CSCuo01578
—
O
DDTS Number
Severity 3
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
33
Caveats
Table 21
Open Caveats and Resolved Caveats Reference (continued)
NX-OS Software Release
(Open or Resolved)
NX-OS Software Release
(Open or Resolved)
6.2(5)
6.2(7)
CSCum00691
—
O
CSCur52810
O
O
CSCuw06365
O
O
CSCus46630
O
O
CSCuv42986
O
O
CSCuf35479
O
O
CSCuj42272
O
R
CSCue48324
O
O
CSCva31989
O
O
O
R
CSCud07594
O
O
CSCuq00007
O
O
DDTS Number
Severity 4
Severity 5
CSCts46166
Severity 6
Resolved Caveats
•
CSCuh93233
Symptom: The Switched Port Analyzer (SPAN) feature does not work after a member of a port
channel is removed.
Condition: This situation occurs only when the monitor session source is a port channel.
Workaround: This issue is resolved.
•
CSCuj77722
Symptom: On the Cisco MDS 9250i switch that is connected to a Cisco Nexus 5000 switch for
virtual Fibre Channel links, an In-Service Software Upgrade (ISSU) operation becomes a disruptive
process.
Condition: This situation occurs if the Cisco Nexus 5000 switch in N_port virtualization (NPV)
mode is connected to the Cisco MDS 9250i switch and the host and or target is connected to the
Cisco Nexus 5000 switch.
Workaround: This issue is resolved.
•
CSCuj83626
Symptom: If there is a Switched Port Analyzer (SPAN) session to inband and the switch is reloaded,
the SPAN session becomes inactive, and packets are not spanned to the SPAN destination.
Condition: A Cisco MDS switch is reloaded when a SPAN session exists from an inband port.
Workaround: This issue is resolved.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
34
OL-29201-03
Caveats
•
CSCul46007
Symptom: For a Cisco MDS 9250i switch, an FCoE Ethernet Interface Monitor window displays
Rx and Tx as 0.
Condition: This situation occurs when the interval for monitoring the Ethernet interface is set to 5
seconds in Data Center Network Manager (DCNM).
Workaround: This issue is resolved.
•
CSCuj42272
Symptom: On a Cisco MDS 9000 switch, when a fan fails, the board LED and fan LED turn red.
Condition: This situation occurs when one of the fans fails.
Workaround: This issue is resolved.
•
CSCue64981
Symptom: The zone set import operation fails when you try to recover a merge failure between two
switches if there are three or more ISLs connected.
Condition: When there are three or more E-port ISLs connected between two switches and if the
zone merge has failed, the recovery action of Zone import fails. The symptom occurs only if there
are three or more ISLs.
Workaround: This issue is resolved.
•
CSCts46166
Symptom: The hidden TFTP server is accessible on the mngt0 interface.
Condition: This situation can occur if the IP address is configured on the mngt0 interface.
Workaround: This issue is resolved.
Open Caveats
•
CSCty82906
Symptom: The Storage Media Encryption (SME) cluster creation fails and the following error
message appears:
Log file is:\Documents and Settings\username\ciscosmartcardapplet.log
[Wed Mar 21 15:50:40 IST 2012]:Thread[thread
applet-com.cisco.dcbu.web.client.sme.applet.SmartcardApplet-1,4,https://172.16.1.1/sme
/jsp/-threadGroup]:Initializing...
[Wed Mar 21 15:50:42 IST 2012]:Thread[thread
applet-com.cisco.dcbu.web.client.sme.applet.SmartcardApplet-1,4,https://172.16.1.1/sme
/jsp/-threadGroup]:Module is
Module Name: gclib.dll [Wed Mar 21 15:50:42 IST
2012]:Thread[Thread-11,4,https://172.16.1.1/sme/jsp/-threadGroup]:
[Wed Mar 21 15:50:42 IST
2012]:Thread[Thread-11,4,https://172.16.1.1/sme/jsp/-threadGroup]:Looking for
smartcard reader...
[Wed Mar 21 15:50:51 IST
2012]:Thread[Thread-11,4,https://172.16.1.1/sme/jsp/-threadGroup]:Exception reading
smartcard:CKR_OPERATION_NOT_INITIALIZED
[Wed Mar 21 15:50:51 IST
2012]:Thread[Thread-11,4,https://172.16.1.1/sme/jsp/-threadGroup]:<fieldset
class="cuesStatusBoxError"
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
35
Caveats
Condition: This issue occurs if you create an SME cluster for recovery option as 2 of 3 by using
Mozilla Firefox, version 11.0 or Microsoft Internet Explorer, version 8, on the Microsoft XP
operating system, and then rekey the master key.
Workaround: None.
•
CSCug22090
Symptom: When an In-Service Software Upgrade (ISSU) is performed from Cisco NX-OS Release
5.2(6b) to Release 6.2(1), LLDP command-line interface (CLI) commands are not available. In this
situation, LLDP is running and traffic is flowing normally even after the ISSU, but the CLI
commands are not available.
This symptom might be seen when feature-set fcoe was enabled on the original image, and feature
lldps commands were working in the original image. Following the ISSU to Cisco NX-OS Release
6.2.1 image, the commands are not available.
Workaround: Following the ISSU, enter the feature lldp command on the switch to make the
LLDP commands available on the switch.
switch(config)# feature lldp
switch(config)# show lldp ?
CSCui52280- Sev 2 O
•
CSCui52280
Symptom: Address Resolution Protocol (ARP) process fails for IP over Fibre Channel (IPFC).
Condition: This issue occurs when the Cisco MDS 9000 switches are connected through virtual
Fibre Channel (vFC) interfaces.
Workaround: None.
•
CSCuj09522
Symptom: The Switched Port Analyzer (SPAN) functionality does not work after adding a VSAN
filter and then removing the filter.
Condition: This situation occurs when the source is an F_port and the destination is a local SD_
port.
Workaround: None.
•
CSCtr50223
Symptom: On the MDS 9513 switch, when an MSM-18/4 module boots up, it sends a request to the
supervisor module to mount the modflash on the MSM-18/4 module. If there is a timeout or error in
response, the following syslog appears:
sw-dc5-br2-12 %LC_MNT_MGR-SLOT3-2-LC_MNT_MGR_ERROR: SUP mount failed. MTS receive
timedout
sw-dc5-br2-12 %PROC_MGR-SLOT3-2-ERR_MSG: ERROR: PID 1144 (lc_mnt_mgr) exited
abnormally, exit status (0xa)
sw-dc5-br2-12 %MODULE-2-MOD_MINORSWFAIL: Module 3 (serial: JAE1141ZB43) reported a
failure in service lc_mnt_mgr
This issue might be seen when the supervisor module is unusually busy and cannot process the
mount request from the MSM-18/4 module, or the actual mount command on the supervisor takes a
long time.
Workaround: Reload the MSM-18/4 module in the same slot/module where the modflash mount
failed. A request will be sent to the supervisor to mount the modflash.
•
CSCug14717
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
36
OL-29201-03
Caveats
Symptom: If beaconing is configured on some ports, LEDs might stop blinking after a supervisor
switchover or module reload.
Condition: This might be seen following a supervisor switchover or a module reload.
Workaround: None.
•
CSCud07594
Symptom: In a virtual SAN (VSAN), the inter-switch link (ISL) might fail after entering the
suspend command, followed by the no suspend command.
Condition: This situation occurs if the no suspend command is entered after a VSAN suspend
operation.
Workaround: After entering the suspend command, wait for at least 5 to 15 minutes and then use
the no suspend command.
•
CSCuj94303
Symptom: Traffic between two Cisco MDS 9250i switches might stop when the write acceleration
feature is enabled during traffic flow.
Condition: This situation occurs if there are more than 11 tunnels.
Workaround: Disable the write acceleration feature on all of the tunnels or move all tunnels to a
PortChannel.
•
CSCul13809
Symptom: Several control protocols are impacted because of the FCoE data traffic congestion in
the traffic flows passing through, or originating, or terminating on a Cisco MDS 9250i switch that
runs the default 7e network-qos policy.
Condition: This is a known limitation with 7e policy. With the 7e template, all control and data
FCoE traffic is sent to a single queue. When congestion in the network is present, in addition to data
packets, control packets also are impacted, which results in timeouts and drops for several control
protocols. Control protocols might display errors.
Workaround: Use the 6e template throughout the fabric so that the control and data traffic are
placed in different queues and do not impact each other.
•
CSCul65496
Symptom: Tape acceleration cannot be enabled on the Cisco MDS 9250i switch if the Transmission
Control Protocol (TCP) connections are set to 5.
Condition: The tcp-connections command is used to set the TCP connection to 5.
Workaround: Set TCP connections to 2.
•
CSCuj42921
Symptom: Inserting and removing an SFP in quick succession might cause the read operation to fail
before completion with NACK errors, and the searching for supported speeds fails. This situation
might prevent a port from coming up and the following error appears:
speed not supported by transceiver
Condition: This situation occurs with specific SFPs during removal and reinsertion.
Workaround: Avoid quickly removing and inserting an SFP. After removing an SFP, wait for few
seconds before reinserting it.
•
CSCuj68267
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
37
Caveats
Symptom: The In-Service Software Upgrade (ISSU) or In-Service Software Downgrade (ISSD) of
more than one Cisco MDS 9250i switch that are connected to one another might cause the VE/E
links between them to go down.
Condition: This situation occurs if an ISSU or ISSD is simultaneously performed on Cisco MDS
9250i switches that are interconnected.
Workaround: Perform an ISSU or ISSD in a progressive method. For example, after the upgrade
or downgrade completes on one switch, move on to another.
•
CSCuj99534
Symptom: During an In-Service Software Upgrade (ISSU), the Cisco MDS 9250i switch displays
the following errors:
2013 Oct 10 14:09:07 sw234-9250i %ACLTCAM-2-ACL_TCAM_PHY_TCAM_WRITE_FAILED: Value
write to hardware TCAM failed(ASIC: 1, Input TCAM, Address: 775, Num Entries: 1,
Error: Broken pipe).
2013 Oct 10 14:09:07 sw234-9250i %ACLTCAM-2-ACL_TCAM_PHY_TCAM_WRITE_FAILED: Value
write to hardware TCAM failed(ASIC: 2, Input TCAM, Address: 609, Num Entries: 1,
Error: Broken pipe).
Condition: The Cisco MDS 9250i switch has 200 I/O Accelerator (IOA) disk flows.
Workaround: None.
More information: The Cisco MDS 9250i switch supports up to 180 disk flows.
•
CSCul08289
Symptom: The Cisco MDS 9250i switch displays a powered-off power supply module as redundant.
Condition: Two supply modules are operational and one is powered off.
Workaround: Ensure that all three supply modules are operational.
•
CSCui21601
Symptom The Cisco MDS 9710 Director does not allow a copy running saving configuration and a
switch reload operation.
Condition: Active Fibre Channel Redirect (FC-Redirect) configurations are present in Cisco MDS
9710 Director.
Workaround: Remove the Cisco MDS 9710 Director from the fabric.
•
CSCum00691
Symptom: If both the Fibre Channel and Fibre Channel over Ethernet (FCoE) links with the same
equal-cost multipath (ECMP) entries) between two switches, traffic does not flow.
Workaround: VLAN-VSAN mapping should be numerically identical when ECMPs exist with a
mix of FC and FCoE paths. For example, map VSAN 10 to VLAN 10, VSAN 11 to VLAN 11, and
so on.
•
CSCun29631
Symptom: Activation zone mode change or any such change operation failing is Stage Fabric
Configuration (SFC) stage with the following error:
Invalid data
Condition: When you configure a member of type symbolic-nodename with a name that has more
than 240 characters in it and attempt to activate the zone set or perform a zone mode change.
Workaround: Configure zone members of type symbolic-nodename with the names that have fewer
than 240 characters.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
38
OL-29201-03
Caveats
•
CSCun56276
Symptom: The following priority flow control (PFC) incompatibility warnings are logged to syslog
even though there are no compatibility issues between the FCoE peers on the specified links:
%ETH-QOS-2-QOSMGR_DCBXP_PFC_CMP_FAIL_MSG: Ethernet1/37 - qos config
'Priority-flow-control' not compatible with the peer
Condition: These messages are incorrectly logged during In Service Switch Upgrade (ISSU) or In
Service Switch Downgrade (ISSD) on for FCoE interfaces even though there are no compatibility
issues.
Workaround: None.
More Information: This is a cosmetic issue.
•
CSCun82838
Symptom: On a Cisco MDS 9500 Series switch with a dual supervisor, after switchover to standby
supervisor, the ilc_helper process crashes.
Condition: This situation occurs during the Data Mobility Manager (DMM) operations after a
switchover.
Workaround: Purge the module and reenable the Storage Service Interface (SSI) software and
configure the DMM again.
•
CSCuo01578
Symptom: The RewriteEngineLoopback test fails and get error is disabled on the Cisco MDS 9710
Director with 48-port 10-Gigabit FCoE.
Condition: An In-Service Software Upgrade (ISSU) is performed from any of Cisco NX-OS
Releases versions 6.2.1, 6.2.3, and 6.2.5 to 6.2.7 or sequentially from 6.2.1 to 6.2.3, and then to
6.2.7.
Workaround: If there are multiple fabric modules in the chassis, reload each fabric module one
after the other. For example, reload the fabric module 1, wait for the module to complete the reload
process, wait for 2 to 3 minutes and then reload the next fabric module. You must not reload all fabric
modules at the same time. After reloading all fabric modules, clear the diagnostic result using the
diagnostic clear result module command.
•
CSCul12775
Symptom: The Cisco MDS 9250i switch incorrectly displays that the Ternary Content Addressable
Memory (TCAM) is full even if enough memory is available.
Condition: This situation occurs if the IOA flows go into the security region and some TCAM
entries are deleted or added.
Workaround: None.
•
CSCul64626
Symptom: Ethernet SPAN does not capture the egress traffic from a Fibre Channel node to the FCoE
nodes.
Condition: This situation occurs when Ethernet SPAN is configured on a Fibre Channel node of an
MDS 9000 Series switch and the corresponding FCoE node is receiving traffic from the Fibre
Channel node.
Workaround: None.
•
CSCuh37423
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
39
Caveats
Symptom: After changing the device alias configuration, the I/O Accelerator (IOA) flows remain
unchanged until the reactivation of the zone set.
Condition: This situation occurs during a device-alias add, delete, or rename operation.
Workaround: None.
•
CSCum87393
Symptom: Packets drop on the egress of the Cisco MDS 48-Port 10-Gigabit Fibre Channel over
Ethernet module because of the congestion timeout check.
Condition: If the congestion timeout value is set to 100 ms for edge ports on the Cisco MDS 9710
Director with the Cisco MDS 48-Port 10-Gigabit Fibre Channel over Ethernet module, it causes the
FCoE ISL to flap continuously.
Workaround: Set the timeout value to 500 ms.
More Information: Only the 500 ms timeout value is supported.
•
CSCun04994
Symptom: Fibre Channel trace does not work on the Cisco MDS 48-Port 10-Gigabit Fibre Channel
over Ethernet (FCoE) module.
Workaround: Use Path Trace to trace the path between two domains or a domain and an end device.
•
CSCun11007
Symptom: The server interface connected to the N_port virtualization (NPV) switch might flap if 5
or more FDISC rejects are sent from the core switch within 10 seconds.
Condition: This occurs if the core switch rejects NPV FDISC logins in a short time or if the server
is bursting logins that are getting rejected.
Workaround: Make sure that no rejects occur for NPV FDISC logins on a server interface that is
connected to the NPV switch.
•
CSCun59595
Symptom: During a high CPU utilization, if any access to the bootflash or compact flash occurs,
USDs might crash, and this can result in switch reload.
Condition: This situation occurs during the scale configuration or a high CPU utilization if any copy
to bootflash or access to compact flash causes the heartbeat failure.
Workaround: Based on the CPU utilization, perform the access to the bootflash.
Further Problem Description: Copying an image to bootflash causes more IDE interrupts, and the
CPU processes the interrupts and does not give control to other USDs to communicate with the
watchdog, and this issue causes the USD to crash.
•
CSCun76030
Symptom: On the Cisco MDS 9710 Director with the 48-Port 10-Gigabit Fibre Channel over
Ethernet module, packet drop occurs when the FCoE port generates pause frame during a
congestion.
Condition: When the distance between Cisco MDS switches are distantly located and a congestion
occurs.
Workaround: None.
•
CSCun84332
Symptom: On the Cisco MDS 48-Port 10-Gigabit FCoE module, the ECMP fails with multiple
FCoE ISL.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
40
OL-29201-03
Caveats
Condition: This situation occurs if one of these conditions is true:
–
Two switches with multiple FCoE ISLs are connected. For example, the host is connected to
one switch and the target on another switch.
– Multiple IVR flows are configured for any of these host-target combinations:
FC host to FCoE target, FC host to FC target, and FCoE host to FC target
Workaround: None.
•
CSCuo00701
Symptom: The normal operation of Data Mobility Manager (DMM) might be affected as follows:
– DMM Initiator-Target (IT) flows for migration jobs cannot be configured.
– DMM IT flows might encounter I/O traffic issues if either the initiator or target are physically
moved to another switch.
Condition: This situation occurs if at least one of the switches in the fabric has the FCNS bulk
notification feature enabled or if the DMM-specific Initiator or Target are moved to a switch that has
the FCNS bulk notification feature enabled.
Workaround: Disable the FCNS bulk notification feature on the appropriate switches.
•
CSCuo24658
Symptom: After a switch upgrade to NX-OS 6.2(1) or later, a previously working AAA
authenticated user who is configured for non network-operator privileges (such as network-admin)
only receives network-operator privileges. This user is no longer able to configure the switch via
CLI or SNMP.
The CLI user will show as having 'network-operator' role:
switch# show user-account fieldsupport
user:fieldsupport
roles:network-operator
If the SNMP user exists, it will show as having 'network-operator' role:
switch# show snmp user fieldsupport
______________________________________________________________
SNMP USERS
______________________________________________________________
User
Auth Priv(enforce) Groups
____
____ _____________ ______
fieldsupport
md5
des(no)
network-operator
Condition: This issue only affects logins that meet all of the following conditions:
1) are logins to MDS switches
2) are authenticated remotely via RADIUS
3) have multiple vendor-specific attributes (VSAs) defined as a single Cisco-AV Pair, for example,
shell and SNMP version 3 settings:
shell:roles="operations-user fieldsupport" snmpv3:auth=SHA priv=AES-128
This issue does not occur if the 'shell:roles' VSA is defined alone (even with multiple roles
assigned).
Workaround: On the AAA server, create a separate RADIUS policy for NX-OS 6.2(x) users that
splits Cisco-AV Pairs into true attribute pairs. For example:
Cisco-AVPair #1:
shell:roles="operations-user fieldsupport
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
41
Caveats
Cisco-AVPair #2:
snmpv3:auth=SHA priv=AES-128
Assign this policy conditionally on the requesting RADIUS client IP address (that is, a Cisco MDS
switch mgmt0 IP address). Continue to use the original policy with the old format for RADIUS
authentication requests from switches running NX-OS earlier than 6.2(1).
If the RADIUS server does not support conditional assignment of policies by RADIUS client IP
address then an alternate method is possible. Create a local user on the switch with local role
assignment which will override the remotely supplied role using the following commands:
switch(config)# no username <userid>
switch(config)# username <userid> password ! role fieldsupport
Further Problem Description: This issue was introduced in NX-OS release 6.2(1) due to changes
to make RADIUS VSA handling consistent across NX-OS platforms.
•
CSCug83123
Symptom: If a nondefault logging level is set for LLDP, and if a switchover occurs, the running
configuration will not show the logging level lldp 5.
Condition: This situation occurs when LLDP sets a nondefault logging level by using the logging
level lldp command and if a switchover occurs.
Workaround: None.
•
CSCuh49283
Symptom: One of the symptoms is observed:
– A zone member goes offline.
– A Registered State Change Notification (RSCN) is not sent to zone members.
– The device-mapping entry, port world wide name (pWWN) associated to a device alias is not
displayed in the Dynamic Port VSAN Membership (DPVM) database.
– The show running-configuration ivr command does not display the changes when a device
alias member in an Inter-VSAN Routing zone (IVR zone) is renamed.
– The port world wide name (pWWN) associated with the device alias is found dissociated in the
port security database.
– A device alias member is not found in the port security database.
Condition: This situation occurs when all or one of the conditions is met:
– A user attempts to perform a device-alias operation in batch, such as renaming an offline device
alias to an existing online device alias or vice versa.
– A device alias was renamed.
– A device alias was deleted and an existing device alias is renamed to the deleted device alias in
the same commit.
– A device alias, which is not configured, resides in the DPVM database, and an online device is
renamed to the former.
– The IVR distribute option is enabled and the device alias is in enhanced mode, and the changes
in a device alias are not updated to the IVR running configuration.
Workaround: Add the offline member to the device alias database, revert to the previous name if
you have renamed a device alias, and flap the ports that are connected to the affected zone member.
•
CSCuh05972
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
42
OL-29201-03
Caveats
Symptom: When you use the show topology and show fcs ie commands, a few attributes such as
switch name, and management interface address are not displayed.
Condition: When the initial discovery is incomplete either because of the congestion that results in
packet drops or the target switch does not respond.
Workaround: Use the fcs start-discovery command and then use the show topology and show fcs
ie command to display the topology details including the switch name, management interface
address, and vendor name.
Further Problem Description: If you use the show topology command, the switch name, the data
for peer interfaces are displayed appropriately.
•
CSCub40020
Symptom: After an In Service Software Upgrade (ISSU), In Service Software Downgrade (ISSD),
or supervisor switchover, devices fail to FLOGI into the switch, and the following error is logged in
the syslog:
%FLOGI-1-MSG_FLOGI_REJECT_FCID_ERROR after upgrade/switchover
Condition: This situation occurs if one or all of the following occur:
1.
The Max flogi key is greater than 65535. The key can get this high if there are repeated FLOGIs
on an interface. After the key exceeds 65535, this issue occurs. However, this situation does not
impact end devices.
2.
If a supervisor switchover, such as ISSU, ISSD, or system switchover occurs when the key is
greater than 65535, Fibre Channel Identifiers (FC IDs) can be dropped from the FLOGI table.
The end devices continue to function normally until they are logged out and then attempt to
relogin.
3.
If after both 1 and 2 above have occurred and then an end device is rebooted on the affected
interface, that end device might not be able to log back in.
Workaround: You must first resolve the issue with the device on the interface with the Max flogi
key over 65535, such as FLOGI rejects or port security, to prevent the FLOGI key from
incrementing.
If the Max flogi key value is greater than 65535 before any supervisor switchover, ISSU, or ISSD,
use the shutdown and then no shutdown command on the interface. Consequently, the Max flogi
key value must be checked before any supervisor switchover. However, if the supervisor switchover
has already occurred and logging in are failing, you must follow either of these steps:
– Contact Cisco TAC to implement a nondisruptive recovery. This requires special files not
accessible to customers.
– Suspend the VSAN and wait for 5 minutes and then unsuspend the VSAN of the affected devices
on the switch. This action is disruptive to all devices in that VSAN connected to this switch.
More Information: For detailed information about this issue, see the General Upgrading
Guidelines, page 18.
•
CSCuf64822
Symptom: The DCBX local information shows LLS DCBX registration when the port is in the shut
state as:
Local DCBXP Control information:
Operation version: 00 Max version: 00 Seq no: 1
Type/
Subtype
Version
En/Will/Adv Config
006/001
000
Y/N/Y
80
Ack no: 0
006/001 is the LLS TLV.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
43
Caveats
Note
All the other DCBX features are usually preregistered on a down port and not seen in the DCBX
output. LLS is not deregistered on a shut port, and keeps appearing in the output.
Condition: This situation occurs when the port is in the shut state.
Workaround: None.
•
CSCuf35479
Symptom: While configuring the SNMP server, if you configure a host name instead of an IP
address, the following error appears:
Bad IPv6 host address
Condition: If the domain name and the name server IP are configured, and if you provide the SNMP
host name.
Workaround: Instead of the host name, add the IP address of the host in the SNMP configuration.
•
CSCue31727
Symptom: A user with the priv-14 role does not inherit rules from the priv-0 through priv-13 roles.
Condition: This situation occurs during a normal operation.
Workaround: Create users with roles from priv-0 to priv-13 and log in, or log in to the switch using
AAA authentication where users with certain user levels are identified.
•
CSCuq59148
Symptom: Credit Monitor disabled on 9710 FC ports running NX-OS 6.2(7) when the device
FLOGIs in with less than or equal to 8 credits. This can lead to other ports failing with:
%PORT-5-IF_DOWN_LINK_FAILURE: %$VSAN 1%$ Interface fc1/1 is down (Link failure Link
Reset failed nonempty recv queue) port-channel11.
Condition: Applies to MDS 9710 running NX-OS 6.2(7) only.
Also applies to earlier NX-OS 6.2 releases if there was an In Service Software Downgrade from
NX-OS 6.2(7) to that earlier release. In that case, credit monitoring will remain disabled until the
device re-logs in.
Workaround: There are two known workarounds:
1.
If possible have the attached device increase the number of B2B credits it allows in its FLOGI
to a number that is greater than 8.
2.
A TCL script is available that will non-disruptively modify the port settings on any/all F ports
in the switch to enable credit monitoring.
Please contact the Cisco TAC for this.
Upgrading to Cisco MDS NX-OS Release 6.2(9) or later will completely resolve the issue.
Further Problem Description: The following linecard command will show that credit monitoring
is disabled on ports 19 and 20:
module-1# show process creditmon statistics
******************Credit Monitor Info*******************
Port
Mode
Monitor Cr Loss
Slow-Port-Detection
on?
Detected?
------------- -------------- -----1
F
yes
0
yes
0
2
F
yes
0
yes
0
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
44
OL-29201-03
Caveats
19
20
F
F
no
no
0
0
no
no
0
0
Other symptoms that might occur due to a port stuck at zero Tx credits remaining:
%DIAG_PORT_LB-2-INT_PORT_LOOPBACK_TEST_FAIL: Module:1 Test:Internal PortLoopback
failed 10 consecutive times. Faulty module: affected ports:affected ports:30
Error:Loopback test failed. Packets lost on the SUP in the transmit direction
%DIAG_PORT_LB-2-SNAKE_TEST_LOOPBACK_TEST_FAIL: Module:1 Test:SnakeLoopback failed 10
consecutive times. Faulty module: affected ports:affected ports:1-48 Error:Test
Failed, Could not identify the Faulty Device
•
CSCum30306
Symptom: The security service crashes when configuring an SSH authentication key.
Configuring SSH keys multiple times within 10 minutes results in a HAP reset that resets the active
supervisor.
Condition: This issue intermittently occurs when configuring an SSH authentication key.
Workaround: To avoid the supervisor reset, do not configure more than 2 SSH keys per 10 minutes.
•
CSCuo82450
Symptom: An egress FCoE interface log output discards during congestion even though pause
frames are sent upstream on the ingress interface. Pause frames received on the egress interface do
not prevent the output discards.
Affected ingress interfaces can be identified when the 'ENABLED' field is 1 in the output of the
following module-level command:
show hardware internal qengine inst inst-num table vq_voq_td
where inst-num = quotient of ((the port number - 1) / 4. For example, to verify Ethernet1/1 is affected
using “slot 1” and “inst 0” as arguments to the above command:
switch# slot 1 show hardware internal qengine inst 0 table vq_voq_td | include
"port|ENABLE|^0"
| Inst 0; port(s) 1-4
INDEX QUEUE PKT TYPE VL THRESHOLD ENABLE
0
8q
CRD DE
0
14400
1
Condition: This issue only applies to interfaces with a “no drop” CoS, that is, FCoE interfaces. An
interface will be affected by this issue only after a supervisor switchover (this includes ISSU/ISSD
switchovers) and then the interface flaps for any reason (this includes moving the interface into a
port channel).
For Nexus 7000/7700 switches, the first affected release is Cisco NX-OS Release 6.2(2).
For MDS 9500/9700 switches, the first affected release is Cisco MDS NX-OS release 6.2(7).
Workaround: To nondisruptively restore the “no drop” functionality, set the priority flow control
to “on” and back to “auto” for each affected ingress interface. If the interface is a member of a port
channel then the change should be done at the port channel interface level. For example:
switch(config-if)# interface port-channel 1
switch(config-if)# priority-flow-control mode on
switch(config-if)# priority-flow-control mode auto
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
45
Caveats
The above workaround can only be applied to interfaces which are up. This will restore the potency
of pause frames on the Ethernet interfaces. However, further port flaps will cause the issue to recur
on the interface.
Further Problem Description: By default, FCoE traffic is no-drop class and can be affected by this
issue. Also, congestion is usually found in network designed to be oversubscribed or when slow
drain devices are present in a network. To recover permanently and nondisruptively, follow these
steps:
1.
Apply the priority-flow-control mode on to all affected interfaces
2.
Upgrade the system to a fixed version of NX-OS
Apply the priority-flow-control mode auto to all the previously affected interfaces.
•
CSCur52810
Symptom: FCIP tunnels don't fully utilise the available TCP window size. This leads to
underperforming FCIP tunnels that never achieve their configured bandwidth on higher latency
links.When TCP send queue hits 2MB threshold, the FCIP tunnel is exerting flow control back to
the FC ports utilizing the tunnel. This leads to Rx B2B credit depletion. You can see the current size
of the send queue via the following command:
show ips stats tcp interface gige
Local Address
Remote Address
1.1.1.1:65525
2.2.2.2:3225
State
ESTABLISH
Send-Q
2558928 0
Recv-Q
Condition: This issue applies when:
– NX-OS versions from 6.2(5) to 6.2(9c) inclusive, and
– the platform is an MDS 9500 or MDS 9222i, and
– latency on FCIP tunnel is high enough that a TCP window size greater than 2 MB is required
Workaround: Increase the number of FCIP tunnels.
Further Problem Description: The current TCP window size is displayed in the "Peer receive
window" field of the show interface fcip command:
Peer receive window: Current: 4162 KB, Maximum: 4220 KB, Scale: 11
•
CSCur81171
Symptom: System switchover takes too long a time [around 20 minutes] and standby gets reloaded
before becoming HA-standby. Flogi process will consume 90 - 100% of CPU cycles during PSS
restore and due to this, any end device activity like login and logout will not be processed by Flogi
process and eventually gets timed out.
This may cause the flogi process to crash and if the standby is not in ha-standby status, the switch
will reload.
Condition: The issue will happen if all of the the below conditions are met.
– The end device must have done a continuous Login - Logout [this is not a port flap but the end
device doing a login flap without the port going down] to a switch running NX-OS less than
6.2.7. (or) 5.2.8e
– Max flogi key greater than the flogi bitset (See Further Problem Description below.)
– An ISSU to any version higher than NX-OS 6.2.7 or 5.2.8e from any version less than NX-OS
6.2.7 or 5.2.8e occur
– A Supervisor Switch-over happens.
Workaround: The workaround to recover - is to - identify the affected ports and flap them.
Note: Contact Cisco TAC to efficiently identify affected ports.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
46
OL-29201-03
Caveats
Further Problem Description: When there is repeated Flogi and Logo on an interface, the “Max
Flogi key” count which is 16-bit will increment for every Login - Logout flap and after reaching 64k
will wrap around and start from Zero. On the other hand, the “flogi bitset” count reaches 255 for
every Login - Logout flap and after reaching 255 will stay put. When the “Max Flogi key” count is
less than the “flogi bitset” the PSS recovery takes more time which is a bug. This issue is fixed and
will not occur in Cisco MDS NX-OS Releases 6.2(7), 5.2(8e) and above - Bug CSCub40020.
If the issue has occurred in lower versions and when an ISSU to Cisco MDS Release NX-OS 6.2(7)
or 5.2(8e) is done, it tries to recover the “Max flogi key”. If the recovery step ends up in Max flogi
key < than flogi bitset value, the PSS recovery during further Switchover will take up more time.
The time consumption of PSS recovery is directly proportional to the No. of Instances where the
“Max Flogi key” is less than the “flogi bitset”
That is, in a scaled environment and when more and more ports or vsans are affected the time taken
for PSS recovery is exponential.
The affected interface can be found by the following CLI:
# show flogi internal info |inc fc|port-channel|key|bitset
Interface fc2/5: mode[F] [1084000] Mode: F State: UP Vsan: 1
Vsan no: 1 Max flogi key: 0x1(1) num_fl[0x1]
flogi bitset: 0
-------------------------Interface port-channel3: mode[TF] [4000002] Mode: TF State: UP Vsan: 552
Vsan no: 1 Max flogi key: 0x40(64) num_fl[0x10]
flogi bitset: 0-255
Vsan no: 552 Max flogi key: 0x40(64) num_fl[0x5]
flogi bitset: 0-4
In the above example,
interface fc2/5 in Vsan 1 and interface port-channel3 in Vsan 552 have Max flogi key greater than
the flogi bitset [0x1(1) > 0 and 0x40(64) > 4] but interface port-channel3 in Vsan 1 has Max flogi
key less than the highest flogi bitset value [0x40(64) < 255].
•
CSCue48324
Symptom: Users remotely authenticated by RADIUS or TACACS+ cannot login to the system after
ISSU. Also, the aaa group configuration has a deadtime greater than the maximum of 1440 minutes,
for example:
switch# show running-config tacacs+
aaa group server tacacs+ TACACS_GROUP
deadtime 269688784
Conditions: This issue only occurs for RADIUS or TACACS+ server groups.
Workaround: To recover after this issue has occurred:
1.
Use a local account to login then reestablish a connection to the aaa servers with the one of the
following commands:
test aaa server tacacs+ a.b.c.d
test aaa server radius a.b.c.d
This must be done for all server addresses in the affected group.
2.
Reconfigure the deadtime of the server group to a value within the range of 0 to 1440. After the
deadtime is within range, it can be removed with the no deadtime command.
To prevent this issue before an upgrade, initialise the deadtime and save the config, then remove it
and save the config again. For example, for TACACS+:
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
47
Caveats
switch# conf t
(config)# tacacs-server deadtime 1
(config)# aaa group server tacacs tacacsgroup
(config)# deadtime 1
(config)# end
switch# copy run start
switch# conf t
(config)# no tacacs-server deadtime 1
(config)# aaa group server tacacs tacacsgroup
(config)# no deadtime 1
(config)# end
switch# copy run start
•
CSCuq00007
Symptom: Maximum FCIP throughput on the MDS 9250i is limited to less than line rate for 10
Gbps interfaces.
Condition: This issue only applies to 10 Gbps FCIP interfaces on the MDS 9250i platform.
Workaround: There is no workaround.
•
CSCuq64102
Symptom: The RSCN or ZONE service crashes with the following syslog message:
%SYSMGR-2-SERVICE_CRASHED: Service "rscn" (PID 5405) hasn't caught signal 11 (core
will be saved).
or
%SYSMGR-2-SERVICE_CRASHED: Service "zone" (PID 5430) hasn't caught signal 6 (core will
be saved)
A Cisco MDS 9700 switch can incur a switchover, however in most cases, the crash occurs again
before the standby is available and the dual supervisor switch will reload.
For Example:
show system reset-reason
----- reset reason for Supervisor-module 5 (from Supervisor in slot 5) --1) At 161169 usecs after Thu Dec dd hh:mm:ss 2014
Reason: Reset triggered due to HA policy of Reset
Service: rscn hap reset
...
----- reset reason for Supervisor-module 6 (from Supervisor in slot 6) --1) At 422003 usecs after Thu Dec dd hh:mm:ss 2014
Reason: Reset triggered due to HA policy of Reset
Service: rscn hap reset.
Condition: This issue occurs only when "port" format RSCNs are configured and an RSCN is sent
on the relevant VSAN. RSCNs are sent, for example, after activating zoneset changes or a link
changing state. Further, only the following platforms are affected:
Cisco MDS 9710 Switch
Cisco MDS 9706 Switch
Cisco Nexus 7000 Switch
Cisco Nexus 7710 Switch
This issue does not occur when RSCNs are sent with "fabric" format.
Workaround: Use the default RSCN address format by removing the following lines from the
switch configuration:
no zone rscn address-format port vsan
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
48
OL-29201-03
Caveats
Note that some end devices may not support receiving RSCNs in this format.
Further Problem Description: This wrong data is constructed by the zone server. It can corrupt its
own heap while creating the payload to put into MTS.
The crash can be either in the zone server or RSCN. It is just which module runs into the issue first.
The fix that went in is to prevent both.
•
CSCuq98083
Symptom: An FCSP-ESP enabled (encrypted) port that was working fails to come up after
ISSU/ISSD followed by link flap.
Condition: This issue only affects FCSP encrypted ports on MDS 9700 DS-X9448-768K9 and MDS
9500 DS-X9248-256K9 and DS-X9232-256K9 switching modules after an ISSU or ISSD to an
affected version of NX-OS.
Workaround: Only a switch reload will recover from this situation. The switch must be running a
fixed release of NX-OS (NX-OS 6.2(11) or above) before the reload to prevent the issue from
recurring after recovery.
None of the following steps alone will not recover the port functionality:
– - Shut/no-shut the affected port.
– - Reloading the affected linecard.
– - Removing the FCSP configuration and re-configuring FCSP.
– - Upgrading to NX-OS 6.2(11) or above.
Further Problem Description: The issue arises on affected version of NX-OS since these versions do
not push the FCSP-ESP configuration to hardware. This results in a permanent FCSP-ESP configuration
mismatch with the peer port. Hence the port will not come up.
•
CSCuw82693
Symptom: An ISL connected over a DWDM path does not reach link up state.
Condition: This issue only applies to MDS 9700 DS-X9448-768K9 modules used with some
DWDM vendors.
Workaround: None.
Further Problem Description: show interface shows the link in "Link failure or not-connected"
with OLS/LRR and NOS increasing in both directions.
•
CSCuw06365
Symptom: An ISL does not initialize quickly across a DWDM connection. The link can take
minutes, hours or even days to connect. Once connected, it is stable.
Condition: This issue only applies to DS-X9248-256K9 and DS-X9232-256K9 modules when
connecting an ISL over a Tellabs 7100 DWDM path.
Workaround: None.
Further Problem Description: show interface shows the link in "Link failure or not-connected"
with OLS/LRR and NOS increasing in both directions.
•
CSCus46630
Symptom: Whenever we give the command to max-bandwidth-mbps in m9250i, although the
maximum supported speed is 10Gig, it shows 1Gig as the maximum configurable bandwidth.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
49
Related Documentation
Condition: There is one condition when we have IPS port speed for m9250i speed set as 1Gig, then
as of now, the user has to make sure he doesn't give the speed as 10Gig. Reason being it will show
the 10Gig as max-bandwidth allowed even for 1Gig speed in m9250i. As of now, we don't have the
intelligence in the cli to check for what speed the port speed is set to.
Hence when Port speed = 1Gig, we should give the value of max-bandwidth-mbps = 1Gig and not
as 10Gig.
Workaround: There is no workaround.
Further Problem Description: Reproducible
•
CSCuv42986
Symptom: Callhome stops working and callhome tests fail.
Condition: Only destination profiles of full_txt are configured.
Workaround: To prevent from hitting this defect, configure an additional destination profile that is
either short_txt or XML.
To recover from this defect after it has already been hit, perform a system switchover or reload the
switch.
•
CSCuu76450
Symptom: MDS fabric switch running in NPV mode fails to generate port-monitor alerts.
Condition: Applies to all MDS fabric switches running in NPV mode using port-monitor.
Applies to all versions prior to NX-OS 6.2(13).
Will occur only in the following conditions:
- After one or more upstream NP or TNP ports goes down and then back up.
- For each (T)NP port that flaps, one F port at the end of the range of ports
will no longer be scanned for port-monitor counter events. For example, if the
(T)NP port fc1/1 flaps then the last F port being used(ex. fc1/48) will no
longer be scanned for port-monitor counter events.
Workaround: There are two workarounds, one temporary and one permanent:
1 - Contact the TAC and they can assist with killing the port-monitor process. Once the port-monitor
process restarts, all ports will be once again scanned.
This is only temporary in the sense that if an upstream (T)NP port flaps again the problem will recur.
2 - Move the (T)NP ports to the end of the ports on the switch. For example, if there are four (T)NP
uplinks on a MDS 9148 or MDS 9148S, then move them to fc1/45-fc1/48. Once this has been done
the problem will not recur.
Further Problem Description: The fix is integrated into NX-OS 6.2(13) and later versions.
Related Documentation
The documentation set for the Cisco MDS 9000 Family includes the documents listed in this section. To
find a document online, access the following URL:
http://www.cisco.com/en/US/products/ps5989/tsd_products_support_series_home.html
The documentation set for Cisco Prime Data Center Network Manager is available from the following
URL:
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
50
OL-29201-03
Related Documentation
http://www.cisco.com/en/US/products/ps9369/tsd_products_support_series_home.html
Release Notes
•
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Releases
•
Cisco MDS 9000 Family Release Notes for MDS SAN-OS Releases
•
Cisco MDS 9000 Family Release Notes for Storage Services Interface Images
•
Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images
Regulatory Compliance and Safety Information
•
Regulatory Compliance and Safety Information for the Cisco MDS 9000 Family
Compatibility Information
•
Cisco Data Center Interoperability Support Matrix
•
Cisco MDS 9000 NX-OS Hardware and Software Compatibility Information and Feature Lists
•
Cisco MDS NX-OS Release Compatibility Matrix for Storage Service Interface Images
•
Cisco MDS 9000 Family Switch-to-Switch Interoperability Configuration Guide
Hardware Installation
•
Cisco MDS 9710 Director Hardware Installation Guide
•
Cisco MDS 9500 Series Hardware Installation Guide
•
Cisco MDS 9500 Series Supervisor-2A Tech Note
•
Cisco MDS 9250i Multiservice Switch Installation Guide
•
Cisco MDS 9200 Series Hardware Installation Guide
•
Cisco MDS 9100 Series Hardware Installation Guide
Software Installation and Upgrade
•
Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide
Cisco NX-OS Configuration Guides
•
Cisco MDS 9000 Family NX-OS Licensing Guide
•
Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide
•
Cisco MDS 9000 Family NX-OS System Management Configuration Guide
•
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
OL-29201-03
51
Obtaining Documentation and Submitting a Service Request
•
Cisco MDS 9000 Family NX-OS Fabric Configuration Guide
•
Cisco MDS 9000 Family NX-OS Quality of Service Configuration Guide
•
Cisco MDS 9000 Family NX-OS Security Configuration Guide
•
Cisco MDS 9000 Family NX-OS IP Services Configuration Guide
•
Cisco MDS 9000 Family NX-OS Intelligent Storage Services Configuration Guide
•
Cisco MDS 9000 Family NX-OS High Availability and Redundancy Configuration Guide
•
Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide
Command-Line Interface
•
Cisco MDS 9000 Family Command Reference
Intelligent Storage Networking Services Configuration Guides
•
Cisco MDS 9000 I/O Acceleration Configuration Guide
•
Cisco MDS 9000 Family SANTap Deployment Guide
•
Cisco MDS 9000 Family Data Mobility Manager Configuration Guide
•
Cisco MDS 9000 Family Storage Media Encryption Configuration Guide
Troubleshooting and Reference
•
Cisco NX-OS System Messages Reference
•
Cisco MDS 9000 Family NX-OS Troubleshooting Guide
•
Cisco MDS 9000 Family NX-OS MIB Quick Reference
•
Cisco MDS 9000 Family NX-OS SMI-S Programming Reference
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the “Obtaining Documentation and Submitting a Service Request” section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of
Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The
use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
© 2014 Cisco Systems, Inc. All rights reserved.
MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 6.2(7)
52
OL-29201-03