Guest

Cisco MDS 9000 NX-OS and SAN-OS Software

Cisco MDS 9000 NX-OS Release 5.0(1a) and SAN-OS 3.3(x) Software Upgrade and Downgrade Guide

  • Viewing Options

  • PDF (888.1 KB)
  • Feedback
Cisco MDS 9000 NX-OS Release 5.0(1a) and SAN-OS 3.3(x) Software Upgrade and Downgrade Guide

Table Of Contents

Cisco MDS 9000 NX-OS Release 5.0(1a) and SAN-OS 3.3(x) Software Upgrade and Downgrade Guide

About Software Images

Dependent Factors for Software Installation

NX-OS Release 5.0x Supported Hardware

NX-OS Release 4.x Supported Hardware

Selecting the Correct Software Image for an MDS 9100 Series Switch

Selecting the Correct Software Image for an MDS 9200 Series Switch

Selecting the Correct Software Image for an MDS 9500 Series Switch

Installing NX-OS Release 5.0(1a) Software on a New Cisco MDS Switch

Upgrading to NX-OS Release 5.0(1a) on an Existing Cisco MDS Switch

Upgrading Guidelines for the MDS 9513 Director Switch

Upgrading Guidelines for the MDS 9506 and MDS 9509 Director Switches

Upgrading to NX-OS Release 5.0(x) on an MDS 9500 Series Switch

Upgrading to NX-OS Release 5.0(x) on the MDS 9222i Switch

Downgrading from NX-OS Release 5.0 (1a)

Downgrading from NX-OS Release 5.0(1a) to NX-OS Release 4.2(3)

Downgrading from NX-OS Release 4.2(3) to NX-OS Release 4.2(1b)

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9513 Multilayer Director with Higher Bandwidth Capability

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9513 Multilayer Director Without Higher Bandwidth Capability

Downgrading from NX-OS Release 5.0(x) to SAN-OS 3.3(x) on an MDS 9509 or MDS 9506 Switch with an Installed Generation 3 8-Gbps Fibre Channel Switching Module

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9509 or MDS 9506 Switch Without an Installed Generation 3 8-Gbps Fibre Channel Switching Module

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9222i Switch

Nondisruptive Upgrades on Fabric and Modular Switches

Preparing for a Nondisruptive Upgrade on Fabric and Modular Switches

Performing a Nondisruptive Upgrade on a Fabric Switch

Displaying the Status of a Nondisruptive Upgrade on a Fabric Switch

Troubleshooting a Nondisruptive Upgrade on a Fabric Switch

Migrating From Supervisor-1 Modules to Supervisor-2 Modules

Migration Guidelines

Migrating From a Supervisor 1 Module to a Supervisor-2 Module on a Cisco MDS 9509 or MDS 9506 Director

Migrating from Supervisor-1 to Supervisor-2 Module when SANTap Is Enabled

Related Documentation

Release Notes

Regulatory Compliance and Safety Information

Compatibility Information

Hardware Installation

Software Installation and Upgrade

Cisco NX-OS

Command-Line Interface

Intelligent Storage Networking Services Configuration Guides

Troubleshooting and Reference

Obtaining Documentation and Submitting a Service Request


Cisco MDS 9000 NX-OS Release 5.0(1a) and SAN-OS 3.3(x) Software Upgrade and Downgrade Guide


May 2010

This document provides information on upgrading to NX-OS Release 5.0(1a) and from SAN-OS Release 3.3(x) to NX-OS Release 4.2(x). It provides information on downgrading from NX-OS Release 5.0(1a) to SAN-OS Release 3.3(x), and downgrading from NX-OS Release 4.2(x) to SAN-OS Release 3.3(x).

You will need to do these tasks to upgrade/downgrade:

To upgrade from SAN-OS, you must first upgrade to SAN-OS Release 3.3(x), then upgrade to NX-OS Release 4.2(x), and then upgrade to NX-OS Release 5.0(1a).

To upgrade, you must first upgrade to NX-OS Release 4.2(x), then you can upgrade to NX-OS Release 5.0(1a).

To downgrade, you must first downgrade to SAN-OS Release 3.3(x).

This guide includes the following sections:

About Software Images

Installing NX-OS Release 5.0(1a) Software on a New Cisco MDS Switch

Upgrading to NX-OS Release 5.0(1a) on an Existing Cisco MDS Switch

Downgrading from NX-OS Release 5.0 (1a)

Nondisruptive Upgrades on Fabric and Modular Switches

Migrating From Supervisor-1 Modules to Supervisor-2 Modules

Related Documentation

Obtaining Documentation and Submitting a Service Request


Note All command-line interface (CLI) session examples provided in this document are only intended for reference. The actual switch output differs based on your switch model.



Note For information on upgrading and downgrading Fabric Manager, refer to the Cisco Fabric Manager Fundamentals Guide.


About Software Images

Each switch is shipped with a Cisco MDS NX-OS or SAN-OS operating system for Cisco MDS 9000 Family switches. The Cisco MDS NX-OS and SAN-OS software consists of two images: the kickstart image and the system image.

To select the kickstart image, use the KICKSTART variable.

To select the system image, use the SYSTEM variable.

The images and variables are important factors in any install procedure. You must specify the variable and the respective image to upgrade or downgrade your switch. Both images are not always required for each install.


Note To download new Cisco MDS 9000 Family software including NX-OS and Fabric Manager management software, refer to the Storage Networking Software download site at: http://www.cisco.com/cisco/software/navigator.html


For Storage Services Interface image compatibility information, refer to the Cisco MDS NX-OS Release Compatibility Matrix for Storage Service Interface Images.

For information on Fabric Manager upgrade and downgrade paths, and software images that are supported on your Cisco switches, refer to the Cisco MDS 9000 NX-OS and SAN-OS Release Notes.

Dependent Factors for Software Installation

The software image install procedure is dependent on the following factors:

Software images—The kickstart and system image files reside in directories or folders that can be accessed from the Cisco MDS 9000 Family switch prompt.

Image version—Each image file has a version.

Flash disks on the switch—The bootflash: resides on the supervisor module and the CompactFlash disk is inserted into the slot0: device.

Supervisor modules—There are single or dual supervisor modules.


Note On switches with dual supervisor modules, both supervisor modules must have Ethernet connections on the management interfaces (mgmt 0) to maintain connectivity when switchovers occur during upgrades and downgrades. Refer to the Cisco MDS 9500 Series Hardware Installation Guide.


NX-OS Release 5.0x Supported Hardware

Table 3 lists the MDS hardware chassis supported by Cisco MDS NX-OS Release 5.0(x).

Table 1 Cisco MDS NX-OS Release 5.0(x) Chassis Support Matrix

Switch
NX-OS 5.0(x) Support

MDS 9513

Yes

MDS 9509

Yes

MDS 9506

Yes

MDS 9222i

Yes

MDS 9216i

No

MDS 9216A

No

MDS 9216

No

MDS 9148

Yes

MDS 9134

Yes

MD S 9124

Yes

MDS 9140

No

MDS 9120

No

Cisco Fabric Switch for HP c-Class BladeSystem and Cisco Fabric Switch for IBM BladeCenter

Yes


Table 4 lists the MDS hardware modules supported by Cisco MDS NX-OS Release 5.0(x).

Table 2 Module Support Matrix for Cisco MDS NX-OS Release 5.0(x) 

Module
Description
MDS 9500 Series
MDS 9222i
MDS 9216i

DS-X9530-SF2-K9

MDS 9500 Supervisor-2 Module

Yes

N/A

N/A

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

N/A

N/A

DS-X9224-96K9

24-port 8-Gbps Fibre Channel Switching Module

Yes1

No

No

DS-X9248-96K9

48-port 8-Gbps Fibre Channel Switching Module

Yes1

No

No

DS-X9248-48K9

4/44-port Host Optimized8-Gbps Fibre Channel Switching Module

Yes

Yes

No

DS-X9304-18K9

18/4-Port Multiprotocol Services Module (MSM-18/4)

Yes

Yes

Yes

DS-X9316-SSNK9

16-port Gigabit Ethernet Storage Services Node (SSN-16)

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

No

No

No

DS-X9016

16-port 1-, 2-Gbps Fibre Channel Switching Module

No

No

No

DS-X9032

32-port 1-, 2-Gbps Fibre Channel Switching Module

No

No

No

DS-X9032-SSM

32-port Storage Services Module (SSM)

No

No

No

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 Requires DS-13SLT-FAB2 in the MDS 9513.


For the list of MDS hardware modules supported by Cisco MDS SAN-OS 3.x, refer to the Cisco MDS Release Notes for SAN-OS Release 3.x.

NX-OS Release 4.x Supported Hardware

Table 3 lists the MDS hardware chassis supported by Cisco MDS NX-OS Release 4.x.

Table 3 Cisco MDS NX-OS Release 4.x Chassis Support Matrix

Switch
NX-OS 4.x Support

MDS 9513

Yes

MDS 9509

Yes

MDS 9506

Yes

MDS 9222i

Yes

MDS 9216i

Yes

MDS 9216A

No

MDS 9216

No

MDS 9134

Yes

MD S 9124

Yes

MDS 9140

No

MDS 9120

No

Cisco Fabric Switch for HP c-Class BladeSystem and Cisco Fabric Switch for IBM BladeCenter

Yes


Table 4 lists the MDS hardware modules supported by Cisco MDS NX-OS Release 4.x.

Table 4 Module Support Matrix for Cisco MDS NX-OS Release 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

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

N/A

N/A

DS-X9224-96K9

24-port 8-Gbps Fibre Channel Switching Module

Yes1

No

No

DS-X9248-96K9

48-port 8-Gbps Fibre Channel Switching Module

Yes1

No

No

DS-X9248-48K9

4/44-port Host Optimized8-Gbps Fibre Channel Switching Module

Yes

Yes

No

DS-X9304-18K9

18/4-Port Multiprotocol Services Module (MSM-18/4)

Yes

Yes

Yes

DS-X9316-SSNK9

16-port Gigabit Ethernet Storage Services Node (SSN-16)

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 Requires DS-13SLT-FAB2 in the MDS 9513.


For the list of MDS hardware modules supported by Cisco MDS SAN-OS 3.x, refer to the Cisco MDS Release Notes for SAN-OS Release 3.x.

Selecting the Correct Software Image for an MDS 9100 Series Switch

The system and kickstart image that you use for an MDS 9100 series switch depends on which switch you use, as shown in Table 5.

Table 5 Software Images for MDS 9100 Series Switches

Cisco MDS 9100 Series Switch Type
Supervisor Module Type
Naming Convention

MDS 9124, 9134, Cisco Fabric Switch for HP c-Class BladeSystem, Cisco Fabric Switch for IBM BladeCenter

Supervisor-2 module

Filename begins with m9100-s2ek9

MDS 9148

Supervisor-2 module

Filename begins with m9100-s3ek9


Selecting the Correct Software Image for an MDS 9200 Series Switch

The system and kickstart image that you use for an MDS 9200 series switch depends on the switch you use, as shown in Table 6.

Table 6 Software Images for MDS 9200 Series Switches

Disc MDS 9200 Series Switch Type
Supervisor Module Type
Naming Convention

MDS 9222i

Supervisor-2 module

Filename begins with m9200-s2ek9


Selecting the Correct Software Image for an MDS 9500 Series Switch

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

Table 7 Software Images for MDS 9500 Series Switches

Disc MDS 9500 Series Switch Type
Supervisor Module Type
Naming Convention

MDS 9513

Supervisor-2 module

Filename begins with m9500-sf2ek9

MDS 9506 or 9509

Supervisor-1 module

Filename begins with m9500-sf1ek9

Supervisor-2 module

Filename begins with m9500-sf2ek9


Use the show module command to display the type of supervisor module in the switch. For a Supervisor-1 module, the output might look like this:

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
...
...
5    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    active*
6    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    ha-standby

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

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
...
...
7    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
8    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby

Installing NX-OS Release 5.0(1a) Software on a New Cisco MDS Switch

To install the latest NX-OS Release 5.0(1a) software images a new Cisco MDS 9000 Family switch, follow these steps:


Step 1 Log in to Cisco.com to access the links provided in this document. To log in to Cisco.com, go to the URL http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco Systems user name and password.


Note Unregistered Cisco.com users cannot access the links provided in this document.


Step 2 Verify the following physical connections for the new Cisco MDS 9000 Family switch:

The console port is physically connected to a computer terminal (or terminal server).

The management 10/100 Ethernet port (mgmt0) is connected to an external hub, switch, or router.

Information on physical connections can be found in the Cisco Hardware Installation Guides.


Note On switches with dual Supervisor modules, both Supervisor modules must have Ethernet connections on the management interfaces (mgmt 0) to maintain connectivity when switchovers occur during upgrades and downgrades. Refer to the Cisco MDS 9500 Series Hardware Installation Guide.



Tip Save the host ID information for future use (for example, to enable licensed features). The host ID information is provided in the Proof of Purchase document that accompanies the switch.


Step 3 Verify that the default console port parameters are identical to the parameters of the computer terminal (or terminal server) attached to the switch console port:

9600 baud

8 data bits

1 stop bit

No parity

Refer to the "ConfiguringTerminal Settings and Sessions "chapter in the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.

Step 4 Power up the Cisco MDS 9000 Family switch. The switch boots automatically and the switch prompt appears in your terminal window.

Step 5 Obtain the IP address, subnet mask, and default gateway information that is required for the Cisco MDS 9000 Family switch to communicate over the supervisor module Ethernet interface. This information is required to configure and manage the switch.

Refer to the "Using the Cisco NX-OS Setup Utility" chapter in the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.


Tip You have the option to change the default password during the initial setup process. All Cisco MDS 9000 Family switches have the network administrator as a default user (admin) and a default password (admin). You cannot change the default user at any time.


Step 6 Complete the System Admin Account Setup.


Tip If you create a short, easy-to-decipher password, your password is rejected. Be sure to configure a strong password as shown in the sample configuration. Passwords are case sensitive. You must explicitly create a password that meets the requirements listed in the "Characteristics of Strong Passwords" section in the "Configuring Users and Common Roles" chapter in the Cisco MDS 9000 Family NX-OS Security Configuration Guide.


---- System Admin Account Setup ----

Do you want to enforce secure password standard (yes/no) [y]: y

Enter the password for "admin":
Confirm the password for "admin":

Step 7 Enter yes to enter the setup mode and assign the information obtained in Step 5.

Refer to the "Using the Cisco NX-OS Setup Utility" chapter in the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.


Note Press Ctrl-C at any prompt to skip the remaining configuration options and proceed with what is configured until that point.



Tip If you do not want to answer a previously configured question, or if you want to skip answers to any questions, press Enter. If a default answer is not available (for example, a switch name), the switch uses the previously configured settings and skips to the next question.


The CLI configuration steps (using factory defaults) are as follows:

---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of
the system. Setup configures only enough connectivity for management
of the system.

Press Enter incase you want to skip any dialog. Use ctrl-c at anytime
to skip remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no): yes

By default, two roles exist in all switches:

Network operator (network-operator)—Has permission to view the configuration only. The operator cannot make any configuration changes.

Network administrator (network-admin)—Has permission to execute all commands and make configuration changes. The administrator can also create and customize up to 64 additional roles. One (of these 64 additional roles) can be configured during the initial setup process.


Create another login account (yes/no) [n]: yes

Note While configuring your initial setup, you can create an additional user account (in the network-admin role) besides the administrator's account. The user name must contain non-numeric characters. Refer to the "Configuring User Accounts" section in the "Configuring Users and Common Roles" chapter in the Cisco MDS 9000 Family NX-OS Security Configuration Guide.


Enter the user login ID: test

Enter the password for "test":
Confirm the password for "test":
Enter the user role [network-operator]:


Tip If you use SNMPv3, then do not configure the SNMPv2 community string. Refer to the "Configuring SMNP" chapter in the Cisco MDS 9000 Family NX-OS System Management Configuration Guide.


Configure read-only SNMP community string (yes/no) [n]: yes

SNMP community string: admin


Note The switch name is limited to 32 alphanumeric characters.


Enter the switch name: switch

Continue with Out-of-band (mgmt0) management configuration? [yes/no]: yes

IP version 6 (IPv6) is supported in Cisco MDS SAN-OS Release 4.1(x) and later. However, the setup script only supports IP version 4 (IPv4) for the management interface. For information on configuring IPv6 on the management interface, refer the Cisco MDS 9000 Family NX-OS IP Services Configuration Guide, or the Cisco Fabric Manager IP Services Configuration Guide.

Mgmt0 IPv4 address: ip_address

Mgmt0 IPv4 netmask: subnet_mask

Configure the default gateway? (yes/no) [y]: yes

IPv4 address of the default gateway : 209.165.200.225

Configure advanced IP options? (yes/no) [n]: yes

Continue with In-band (vsan1) management configuration? (yes/no) [n]: n

Enable IP routing? (yes/no) [n]: yes

Configure static route? (yes/no) [n]: n



Note Be sure to configure the IP route, the IP default network address, and the IP default gateway address to enable SNMP access. If IP routing is enabled, the switch uses the IP route and the default network IP address. If IP routing is disabled, the switch uses the default gateway IP address.


Configure the default-network: (yes/no) [y]: yes 


Note The default network address is the Destination prefix: dest_prefix provided above in Mgmt0 IPv4 netmask: subnet_mask.


Default network IPv4 address: dest_prefix 


Configure the DNS IPv4 address? (yes/no) [y]: yes

DNS IP address: name_server_ip_address

Configure the default domain name? (yes/no) [n]: yes

Default domain name: domain_name


Note Refer to the "Configuring Users and Common Roles" chapter in the Cisco MDS 9000 Family NX-OS Security Configuration Guide.


Enable the ssh service? (yes/no) [y]:

Type of ssh key you would like to generate (dsa/rsa) [rsa]:

Number of rsa key bits <768-2048> [1024]:

Enable the telnet service? (yes/no) [n]: y

Enable the http-server? (yes/no) [y]:

Configure clock? (yes/no) [n]: yes

Clock config format [HH:MM:SS Day Mon YYYY] :

Enter clock config :10:10:10 1 July 2008

Configure timezone? (yes/no) [n]: y

Enter timezone config :pst

Configure summertime? (yes/no) [n]: yes

summer-time config :PDT 2 sunday march 02:00 1 sunday november 02:00 59

Configure NTP server? (yes/no) [n]: yes

NTP server IP address: ntp_server_IP_address

Configure default switchport interface state (shut/noshut) [shut]: shut

Note The mgmt0 interface is not shut down at this point - only the Fibre Channel, iSCSI, FCIP, and Gigabit Ethernet interfaces are shut down.



Configure default switchport trunk mode (on/off/auto) [on]: on

Configure default switchport port mode F (yes/no) [n]: yes


Configure default zone policy (permit/deny) [deny]: deny

Enable full zoneset distribution (yes/no) [n]: yes 

Configure default zone mode (basic/enhanced) [basic]: basic 


Note Refer to the "Configuring and Managing Zones" chapter in the Cisco MDS 9000 Family NX-OS Fabric Configuration Guide.


The following configuration will be applied:
username admin password admin_pass role network-admin
  username user_name password user_pass role network-admin
  snmp-server community snmp_community ro
  switchname switch
  interface mgmt0
    ip address ip_address subnet_mask
    no shutdown
  ip routing
  ip route dest_prefix dest_mask dest_address
  ip default-network dest_prefix
  ip default-gateway default_gateway
  ip name-server name_server
  ip domain-name domain_name
  telnet server disable
  ssh key rsa 2048 force
  ssh server enable
  ntp server ipaddr ntp_server
  system default switchport shutdown
  system default switchport trunk mode on
  system default switchport mode F
  system default port-channel auto-create
  zone default-zone permit vsan 1-4093
  zoneset distribute full vsan 1-4093
  system default zone mode enhanced

Would you like to edit the configuration? (yes/no) [n]: no

Would you like to edit the configuration? (yes/no) [n]: no

Use this configuration and save it? (yes/no) [y]: yes


Caution If you do not save the configuration at this point, your changes will not be updated the next time that the switch is rebooted. Type yes in order to save the new configuration. This process ensures that the kickstart and system boot images are also automatically configured.

Tip Up to this point, you can only configure the switch using the CLI. After this step, you can continue configuring the switch using the CLI or switch over to using the Cisco MDS 9000 Family Fabric Manager application. Refer to the Cisco Fabric Manager Fundamentals Configuration Guide.


If you continue to use the CLI, the login prompt automatically appears in your terminal window.

Step 8 Log in to the switch using the new user name and password.

Step 9 Verify that the required licenses are installed in the switch using the show license command.


Note The switch is initially shipped with the required licenses installed in the system; however, the initial license file will not cover unlicensed features that may be used during the grace period. Refer to the Cisco MDS 9000 Family NX-OS Licensing Guide.


The example CLI output for a valid license follows:

switch# show license 
license.lic:
SERVER this_host ANY
VENDOR cisco
INCREMENT ENTERPRISE_PKG cisco 1.0 permanent uncounted \
        VENDOR_STRING=MDS HOSTID=VDH=REG070201 \
        NOTICE="<LicFileID>ent_ips_main_fm.lic</LicFileID><LicLineID>0</LicLineI
D> \
        <PAK>dummyPak</PAK>" SIGN=FB454F0A0D40
INCREMENT MAINFRAME_PKG cisco 1.0 permanent uncounted \
        VENDOR_STRING=MDS HOSTID=VDH=REG070201 \
        NOTICE="<LicFileID>ent_ips_main_fm.lic</LicFileID><LicLineID>1</LicLineI
D> \
        <PAK>dummyPak</PAK>" SIGN=0DAE1B086D9E
INCREMENT SAN_EXTN_OVER_IP cisco 1.0 permanent 7 VENDOR_STRING=MDS \
        HOSTID=VDH=REG070201 \
        NOTICE="<LicFileID>ent_ips_main_fm.lic</LicFileID><LicLineID>2</LicLineI
D> \
        <PAK>dummyPak</PAK>" SIGN=D336330C76A6
INCREMENT FM_SERVER_PKG cisco 1.0 permanent uncounted \
        VENDOR_STRING=MDS HOSTID=VDH=REG070201 \
        NOTICE="<LicFileID>ent_ips_main_fm.lic</LicFileID><LicLineID>3</LicLineI
D> \
        <PAK>dummyPak</PAK>" SIGN=AEAEA04629E8

Step 10 Verify that the switch is running the latest NX-OS 5.0(1a) software, depending on which you installed, by issuing the show version command.

switch# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
  BIOS:      version 1.0.6
  loader:    version N/A
  kickstart: version 5.0(x)
  system:    version 5.0(x)
  BIOS compile time:       06/14/07
  kickstart image file is: bootflash:/m9500-sf2ek9-kickstart-mz.5.0.x.bin.S4
  kickstart compile time:  10/12/2020 25:00:00 [08/26/2008 10:41:37]
  system image file is:    bootflash:/m9500-sf2ek9-mz.5.0.x.bin.S4
  system compile time:     8/22/2008 0:00:00 [08/26/2008 12:15:27]


Hardware
  cisco MDS 9509 (9 Slot) Chassis ("Supervisor/Fabric-2")
  Motorola, 7447A, altivec  with 1032472 kB of memory.
  Processor Board ID JAE1211B6LB

  Device name: 209.165.200.226
  bootflash:    1000440 kB
  slot0:          64065 kB (expansion flash)

Kernel uptime is 0 day(s), 0 hour(s), 20 minute(s), 3 second(s)
...

If the latest NX-OS 5.0(x) software version is displayed, you can continue configuring the switch using one of the following options:

Refer to the Cisco MDS 9000 NX-OS and SAN-OS Configuration Guides for information on configuring further Cisco NX-OS features using the CLI.

Refer to the Cisco Fabric Manager Configuration Guides for more information on using the Cisco MDS 9000 Family Fabric Manager to configure your switch.

If the latest NX-OS 5.0(1a) software is not displayed, continue with upgrading or downgrading the switch as required to install the correct version. Refer to the appropriate section in this guide for upgrading or downgrading to specific versions.


Step 11 Verify the status of the modules on the switch using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    48     1/2/4/8 Gbps 48-Port FC Module   DS-X9248-96K9      ok
2    24     1/2/4/8 Gbps 24-Port FC Module   DS-X9224-96K9      ok
3    48     1/2/4/8 Gbps 48-Port FC Module   DS-X9248-96        ok
4    48     1/2/4/8 Gbps 4/44-Port FC Module DS-X9248-48K9      ok
5    48     1/2/4 Gbps FC Module             DS-X9148           ok
7    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
8    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
11   4      10 Gbps FC Module                DS-X9704           ok
12   22     4x1GE IPS, 18x1/2/4Gbps FC Modul DS-X9304-18K9      ok

Mod  Sw              Hw      World-Wide-Name(s) (WWN)
---  --------------  ------  --------------------------------------------------
1 	5.0(x) 				1.0     20:01:00:0d:ec:24:e8:40 to 20:30:00:0d:ec:24:e8:40
2 	5.0(x) 				0.6     20:41:00:0d:ec:24:e8:40 to 20:58:00:0d:ec:24:e8:40
3 	5.0(x) 				0.55    20:81:00:0d:ec:24:e8:40 to 20:b0:00:0d:ec:24:e8:40
4 	5.0(x) 				0.65    20:c1:00:0d:ec:24:e8:40 to 20:f0:00:0d:ec:24:e8:40
5 	5.0(x) 				1.5     21:01:00:0d:ec:24:e8:40 to 21:30:00:0d:ec:24:e8:40
7 	5.0(x) 				0.3     --
8 	5.0(x) 				1.6     --
11 	5.0(x) 				0.522   22:81:00:0d:ec:24:e8:40 to 22:84:00:0d:ec:24:e8:40
12 	5.0(x) 				1.1     22:c1:00:0d:ec:24:e8:40 to 22:d2:00:0d:ec:24:e8:40


Mod  MAC-Address(es)                         Serial-Num
---  --------------------------------------  ----------
1    00-0d-ec-75-3c-d8 to 00-0d-ec-75-3c-dc  XXXXXXXXXXX
2    00-0d-ec-75-3c-d0 to 00-0d-ec-75-3c-d4  XXXXXXXXXXX
3    00-50-30-02-19-7e to 00-50-30-02-19-82  XXXXXXXXXXX
4    00-0d-ec-75-33-dc to 00-0d-ec-75-33-e0  XXXXXXXXXXX
5    00-19-56-3e-76-5c to 00-19-56-3e-76-60  XXXXXXXXXXX
7    00-05-30-01-d5-e2 to 00-05-30-01-d5-e6  XXXXXXXXXXX
8    00-23-5e-99-9f-e8 to 00-23-5e-99-9f-ec  XXXXXXXXXXX
11   00-13-1a-e5-f5-66 to 00-13-1a-e5-f5-6a  XXXXXXXXXXX
12   00-1b-54-02-e5-08 to 00-1b-54-02-e5-10  XXXXXXXXXXX

Xbar Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    0      Fabric Module 2                  DS-13SLT-FAB2      ok
2    0      Fabric Module 2                  DS-13SLT-FAB2      ok

Xbar Sw              Hw      World-Wide-Name(s) (WWN)
---  --------------  ------  --------------------------------------------------
1    NA              2.0     --
2    NA              2.0     --


Xbar MAC-Address(es)                         Serial-Num
---  --------------------------------------  ----------
1    NA                                      XXXXXXXXXXX
2    NA                                      XXXXXXXXXXX

* this terminal session
switch# 

Upgrading to NX-OS Release 5.0(1a) on an Existing Cisco MDS Switch

This section provides information on upgrading your SAN-OS software to NX-OS Release 5.0(1a). It includes the following sections:

Upgrading Guidelines for the MDS 9513 Director Switch

Upgrading Guidelines for the MDS 9506 and MDS 9509 Director Switches

Upgrading to NX-OS Release 5.0(x) on an MDS 9500 Series Switch

Upgrading to NX-OS Release 5.0(x) on the MDS 9222i Switch

To upgrade to NX-OS Release 5.0(1a) from SAN-OS Release 3.2(3a) or earlier, first upgrade to SAN-OS Release 3.3(x), then upgrade to NX-OS Release 4.1(x) or 4.2(x), and then upgrade to NX-OS Release 5.0(1a).


Note For a nondisruptive upgrade, the switch must be running SAN-OS Release 3.3(x) or later. A disruptive upgrade requires a switch reload.


Upgrading Guidelines for the MDS 9513 Director Switch

On the MDS 9513 switch, the high-level process to upgrade to NX-OS Release 5.0(x) is as follows:


Step 1 Upgrade to MDS NX-OS Release 5.0(1a) as described in Upgrading to NX-OS Release 5.0(x) on an MDS 9500 Series Switch.


Note If you are installing 8-Gbps Fibre Channel modules, refer to the fabric module installation information in the Cisco MDS 9500 Series Switch Hardware Installation Guide, otherwise, follow Step 1.


Step 2 (Optional) Install the MDS 9000 4/44-port 8-Gbps Fibre Channel module.

Step 3 (Optional) Upgrade the MDS 9513 Fabric 1 modules to MDS 9513 Fabric 2 modules.

Step 4 (Optional) Install the MDS 9000 48-port 8-Gbps Fibre Channel module or MDS 9000 24-port 8-Gbps Fibre Channel module.

Step 5 If you installed an MDS 9000 48-port 8-Gbps Fibre Channel module or MDS 9000 24-port 8-Gbps Fibre Channel module, then reload the switch. If you did not install an 8-Gbps module in Step 5, then issue the install all command.

Cisco MDS NX-OS 5.0(x) and Release 4.2(x) support the following Generation 3 8-Gbps modules:

MDS 9000 4/44-port 8-Gbps Host-Optimized Fibre Channel module (DS-X9248-48K9)

MDS 9000 24-port 8-Gbps Fibre Channel module (DS-X9224-96K9)

MDS 9000 48-port 8-Gbps Fibre Channel module (DS-X9248-96K9)

In addition, Cisco MDS NX-OS 4.1(1b) and later supports two fabric modules, which are also known as crossbar modules, for the MDS 9513 Director:

MDS 9513 Fabric 2 module, DS-13SLT-FAB2

MDS 9513 Fabric 1 module, DS-13SLT-FAB1


Note The MDS 9513 Director supports the 8-Gbps Fibre Channel module after the switch upgrade.


If you have a Storage Services Module or other modules, refer to the Cisco MDS 9000 Family Storage Services Interface Image Installation and Upgrade Guide for the list of supported and unsupported modules.


Upgrading Guidelines for the MDS 9506 and MDS 9509 Director Switches

On the MDS 9506 and 9509 Director switches, the high-level process to upgrade to NX-OS Release 5.0(x) is as follows:


Step 1 Upgrade all Supervisor-1 modules to Supervisor-2 modules.

For detailed steps, see the "Migrating From Supervisor-1 Modules to Supervisor-2 Modules" section.

Step 2 Upgrade to MDS NX-OS Release 4.2(x) as described in Upgrading to NX-OS Release 5.0(x) on an MDS 9500 Series Switch.

Step 3 Install the 8-Gbps Fibre Channel modules.


Upgrading to NX-OS Release 5.0(x) on an MDS 9500 Series Switch

To upgrade your switch to use the latest Cisco MDS NX-OS software on your Cisco MDS 9500 Series switch, follow these steps:


Step 1 Log in to Cisco.com to access the links provided in this document. To log in to Cisco.com, go to the URL http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco Systems user name and password.


Note Unregistered Cisco.com users cannot access the links provided in this document.


Step 2 Verify the following physical connections for the new Cisco MDS 9500 Family switch:

The console port is physically connected to a computer terminal (or terminal server).

The management 10/100 Ethernet port (mgmt0) is connected to an external hub, switch, or router.

These procedures are specified in the hardware installation guide for the required product. Refer to the Cisco Hardware Installation Guides to obtain more information:

Step 3 Log in to the switch.

Step 4 Issue the copy running-config startup-config command to store your current running configuration. You can also create a backup of your existing configuration to a file by issuing the copy running-config bootflash:backup_config.txt command. Refer to the "Using the Cisco NX-OS Setup Utility" chapter in the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.

Step 5 Verify that the requested license files installed in the switch are displayed in response to the show license usage command.


Note The switch is initially shipped with the required licenses installed in the system; however, the initial license file will not cover unlicensed features that may be used during the grace period. Refer to the Cisco MDS 9000 Family NX-OS Licensing Guide. If no license is displayed at this point, perform Step 6 and Step 7 to install the required licenses. If the required licenses are displayed at this point, skip Step 6 and Step 7 and move to Step 8.


The example CLI output for a valid license follows:

switch# show license usage
Feature               Insta License Status Expiry Date Comments
                      lled  Count
--------------------------------------------------------------------------------
FM_SERVER_PKG          Yes      -   Unused never       -
MAINFRAME_PKG          Yes      -   Unused never       -
ENTERPRISE_PKG         Yes      -   In use never       -
SAN_EXTN_OVER_IP       Yes      1   Unused never       -
--------------------------------------------------------------------------------

The example CLI output for licenses with expiring grace periods follows:

switch# show license usage
Feature               Insta License Status Expiry Date Comments
                      lled  Count
--------------------------------------------------------------------------------
FM_SERVER_PKG          No       -   In use             Grace Period 78days 5hrs
MAINFRAME_PKG          No       -   Unused             -
ENTERPRISE_PKG         No       -   In use             Grace Period 88days 5hrs
SAN_EXTN_OVER_IP       No       0   Unused             -
--------------------------------------------------------------------------------

Step 6 Install licenses (if necessary) to ensure that the required features are available on the switch. Perform the following steps:

a. Use the show license host-id command to obtain the serial number for your switch. The host ID is also referred to as the switch serial number.

switch# show license host-id
License hostid: VDH=FOX064317SQ


Tip Use the entire ID that appears after the colon (:) sign. In this example, the host ID is VDH=FOX064317SQ


b. Obtain your Claim Certificate or the Proof of Purchase document. This document accompanies every Cisco MDS switch.

c. Locate the Product Authorization Key (PAK) from the Claim Certificate or Proof of Purchase document.

d. Locate the website URL from the Claim Certificate or Proof of Purchase document.

e. Access the specified URL that applies to your switch and enter the switch serial number and the PAK. The license key file is sent to you by e-mail. The license key file is digitally signed to only authorize use on the switch for which it was requested. The requested features are also enabled once the NX-OS software on the specified switch accesses the license key file.


Caution Install the license file in the specified Cisco MDS 9000 Family switch without making any modifications.

Refer to the Cisco MDS 9000 Family NX-OS Licensing Guide.

Step 7 Install the license key file when you receive it by e-mail. Perform the following steps:

a. Copy the license file to bootflash using tftp or scp.

b. Perform the installation by issuing the install license command on the active supervisor module from the switch console.

switch# install license bootflash:license_file.lic 
Installing license ..done 

Note If you provide a target name for the license key file, the file is installed with the specified name. Otherwise, the file name specified in the license key file is used to install the license.


c. Exit the switch console.

Refer to the Cisco MDS 9000 Family NX-OS Licensing Guide.

Step 8 Ensure that the required space is available in the bootflash: directory for the image file(s) to be copied using the dir bootflash: command. Use the delete bootflash:filename command to remove unnecessary files.


Note Before downloading and installing Cisco NX-OS software, verify that the release is supported by your Cisco System MDS reseller. If you purchased support through a Cisco Systems reseller, contact them directly for more information. Otherwise, contact Cisco Technical support at this URL: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.


switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   16206848     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.3.1.3.bin
   16604160     Jul 01 10:20:07 2008  m9500-sf2ek9-kickstart-mz.3.3.1c.bin
   78337129     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.3.1.3.bin
   78718938     Jul 01 10:18:09 2008  m9500-sf2ek9-mz.3.3.1c.bin

Usage for bootflash://sup-local
  122811392 bytes used
   61748224 bytes free
  184559616 bytes total

Step 9 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.

switch# del bootflash:m9500-sf2ek9-kickstart-mz.3.1.3.bin
switch# del bootflash:m9500-sf2ek9-mz.3.1.3.bin

Step 10 Verify that there is space available on the standby supervisor module bootflash on a Cisco MDS 9500 Series switch.

switch(standby)s# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   16206848     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.3.1.3.bin
   16604160     Jul 01 10:20:07 2008  m9500-sf2ek9-kickstart-mz.3.3.1c.bin
   78337129     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.3.1.3.bin
   78718938     Jul 01 10:18:09 2008  m9500-sf2ek9-mz.3.3.1c.bin

Usage for bootflash://sup-local
  122811392 bytes used
   61748224 bytes free
  184559616 bytes total

Step 11 If you need more space on the standby supervisor module bootflash on a Cisco MDS 9500 Series switch, delete unnecessary files to make space available.

switch(standby)# del bootflash:m9500-sf2ek9-kickstart-mz.3.1.3.bin
switch(standby)# del bootflash:m9500-sf2ek9-mz.3.1.3.bin

Step 12 Access the Software Download Center using this URL:

http://www.cisco.com/cisco/software/navigator.html

If prompted to log in, use your Cisco system user ID and password.

Step 13 Click the required Cisco MDS NX-OS Release 5.0(x) image file, depending on which you are installing.

You see the Technical Support Encryption Software Export Distribution Authorization form.

Step 14 Complete the required forms to obtain authorization.

Step 15 Download the files to an FTP or TFTP server.

Step 16 Copy the MDS NX-OS kickstart and system images to the active supervisor module bootflash using FTP or TFTP.


Note When you download an image file, change to your FTP environment IP address or DNS name and the path where the files are located.


switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-kickstart-mz.5.0.x.bin 
bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin
switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-mz.5.0.x.bin 
bootflash:m9500-sf2ek9-mz.5.0.x.bin 

Step 17 Verify that the switch is running the required software version by issuing the show version command. You might need to downgrade to the latest certified original storage manufacturer (OSM) release.

switch# show version
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software may be covered under the GNU Public
License or the GNU Lesser General Public License. A copy of
each such license is available at
http://www.gnu.org/licenses/gpl.html and
http://www.gnu.org/licenses/lgpl.html

Software
  BIOS:      version 1.0.6
  kickstart: version 3.3(1c)
  system:    version 3.3(1c)

  BIOS compile time:       06/14/07
  kickstart image file is: bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin
  kickstart compile time:  5/23/2008 19:00:00 [06/20/2008 07:15:58]
  system image file is:    bootflash:/m9500-sf2ek9-mz.3.3.1c.bin
  system compile time:     5/23/2008 19:00:00 [06/20/2008 07:50:40]
 ......

Step 18 Verify that your switch is running compatible hardware. Refer to the specific version of the Cisco MDS 9000 NX-OS and SAN-OS release notes.

Step 19 Perform the upgrade by issuing the install all command.

The following example displays the result of the install all command if the system and kickstart files are specified locally. The example shows the command issued on an MDS 9500 Series switch.

switch# install all kickstart bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin sys 
bootflash:m9500-sf2ek9-mz.4.2.x.bin

Verifying image bootflash:/m9500-sf2ek9-kickstart-mz.5.0.x.bin for boot variable 
"kickstart".
[####################] 100% -- SUCCESS

Verifying image bootflash:/m9500-sf2ek9-mz.5.0.x.bin for boot variable "system".
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.5.0.x.bin.
[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.5.0.x.bin.
[####################] 100% -- SUCCESS

Extracting "slc" version from image bootflash:/m9500-sf2ek9-mz.5.0.x.bin.
[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/m9500-sf2ek9-mz.5.0.x.bin.
[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/m9500-sf2ek9-kickstart-mz.5.0.x.bin.
[####################] 100% -- SUCCESS

Performing Compact Flash and TCAM sanity test.
[####################] 100% -- SUCCESS


Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     1       yes  non-disruptive       rolling
     3       yes  non-disruptive       rolling
     4       yes  non-disruptive       rolling
     5       yes  non-disruptive         reset
     6       yes  non-disruptive         reset
     7       yes  non-disruptive       rolling
     8       yes  non-disruptive       rolling
     9       yes  non-disruptive       rolling

Images will be upgraded according to following table:
Module       Image                  Running-Version(pri:alt)           New-Version  Upg-Required
------  ----------  ----------------------------------------  --------------------  ------------
     1        slc2                                   3.3(1c)                5.0(x)           yes
     1        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.15(07/16/08)            no
     3         slc                                   3.3(1c)                5.0(x)           yes
     3        bios                          v1.1.0(10/24/03)      v1.1.0(10/24/03)            no
     4        slc2                                   3.3(1c)                5.0(x)           yes
     4        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.15(07/16/08)            no
     5      system                                   3.3(1c)                5.0(x)           yes
     5   kickstart                                   3.3(1c)                5.0(x)           yes
     5        bios       v1.0.6(06/14/07):  v1.0.6(06/14/07)      v1.0.6(06/14/07)            no
     6      system                                   3.3(1c)                5.0(x)           yes
     6   kickstart                                   3.3(1c)                5.0(x)           yes
     6        bios       v1.0.6(06/14/07):  v1.0.6(06/14/07)      v1.0.6(06/14/07)            no
     7        slc2                                   3.3(1c)                5.0(x)           yes
     7        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.15(07/16/08)            no
     8         slc                                   3.3(1c)                5.0(x)           yes
     8        bios                          v1.1.0(10/24/03)      v1.1.0(10/24/03)            no
     9        slc2                                   3.3(1c)                5.0(x)           yes
     9        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.15(07/16/08)            no

Do you want to continue with the installation (y/n)?  [n] y

Install is in progress, please wait.

Syncing image bootflash:/m9500-sf2ek9-kickstart-mz.5.0.x.bin to standby.
[####################] 100% -- SUCCESS

Syncing image bootflash:/m9500-sf2ek9-mz.5.0.x.bin to standby.
[####################] 100% -- SUCCESS

Setting boot variables.
[####################] 100% -- SUCCESS

Performing configuration copy.
[####################] 100% -- SUCCESS

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 3: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 4: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 5: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 6: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 7: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 8: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 9: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 6: Waiting for module online.
 -- SUCCESS

Note At this point, the standby supervisor module reboots. Refer to the Cisco MDS 9000 Family High Availability Configuration Guide.



Automatic boot of image at addr 0x00000000 ...
Starting kernel...
INIT: version 2.85 booting
Checking all filesystems...... done.
Setting the System Clock using the Hardware Clock as reference...System Clock set. Local 
time: Tue Jul  112:13:57 UTC 2008
Loading system software
Uncompressing system image: bootflash:/m9500-sf2ek9-mz.5.0.x.bin
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
INIT: Entering runlevel: 3

If the configuration meets all guidelines when the install all command is issued, all modules (supervisor and switching) are upgraded.

Open a new terminal session to view the upgraded supervisor module using the show module command. Refer to the "Managing Modules" chapter in the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    12     1/2/4 Gbps FC Module             DS-X9112           ok
3    16     1/2 Gbps FC Module               DS-X9016           ok
4    48     1/2/4 Gbps FC Module             DS-X9148           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
6    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
7    24     1/2/4 Gbps FC Module             DS-X9124           ok
8    16     1/2 Gbps FC Module               DS-X9016           ok
9    4      10 Gbps FC Module                DS-X9704           ok

Mod  Sw              Hw      World-Wide-Name(s) (WWN)
---  --------------  ------  --------------------------------------------------
1    5.0(x)          1.0     20:01:00:0d:ec:1f:bd:00 to 20:0c:00:0d:ec:1f:bd:00
3    5.0(x)          0.509   20:81:00:0d:ec:1f:bd:00 to 20:90:00:0d:ec:1f:bd:00
4    5.0(x)          0.302   20:c1:00:0d:ec:1f:bd:00 to 20:f0:00:0d:ec:1f:bd:00
5    5.0(x)          0.3     --
6    5.0(x)          0.4     --
7    5.0(x)          0.222   21:81:00:0d:ec:1f:bd:00 to 21:98:00:0d:ec:1f:bd:00
8    5.0(x)          5.1     21:c1:00:0d:ec:1f:bd:00 to 21:d0:00:0d:ec:1f:bd:00
9    5.0(x)          1.0     22:01:00:0d:ec:1f:bd:00 to 22:04:00:0d:ec:1f:bd:00
...

You have now upgraded the Cisco MDS NX-OS software in your existing switch.


Upgrading to NX-OS Release 5.0(x) on the MDS 9222i Switch

On the MDS 9222i switch, the high-level process to upgrade to NX-OS Release 5.0(x) is as follows:

Upgrade to MDS NX-OS Release 5.0(1a) as described in this section and then if you want to install the 4/44-port 8-Gbps Fibre Channel module, perform the installation after the upgrade.

To upgrade from SAN-OS, you must first upgrade to SAN-OS Release 3.3(x), then upgrade to NX-OS Release 4.2(x), and then upgrade to Release 5.0(1a). To upgrade to NX-OS Release 5.0(1a) on an MDS 9222i switch, follow these steps:


Step 1 Verify that the system image files for the upgrade are present on the active supervisor module bootflash:.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   18939904     Jul 01 10:54:49 2008  m9200-sf2ek9-kickstart-mz.5.0.x.bin
   16858624     Jul 01 10:20:07 2008  m9200-sf2ek9-kickstart-mz.3.3.1c.bin
  101756072     Jul 01 10:33:52 2008  m9200-sf2ek9-mz.5.0.x.bin
   95771404     Jul 01 10:18:09 2008  m9200-sf2ek9-mz.3.3.1c.bin

Usage for bootflash://sup-local
  236338292 bytes used
  142984076 bytes free
  379322368 bytes total

Step 2 If the software image file is not present, download it from an FTP or TFTP server to the active supervisor module bootflash:. You can obtain the software image file from the Cisco.com software download center at the following URL:

http://www.cisco.com/cisco/software/navigator.html


Note If you need more space on the active supervisor module bootflash:, use the delete command to remove unnecessary files and follow Step 3 and Step 4.


switch# copy tftp://tftpserver.cisco.com/MDS/m9200-sf2ek9-kickstart-mz.5.0.x.bin 
bootflash:m9200-sf2ek9-kickstart-mz.5.0.x.bin
switch# copy tftp://tftpserver.cisco.com/MDS/m9200-sf2ek9-mz.5.0.x.bin 
bootflash:m9200-sf2ek9-mz.5.0.x.bin


Step 3 Ensure that the required space is available on the active supervisor.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   18939904     Jul 01 10:54:49 2008  m9200-sf2ek9-kickstart-mz.3.3.1c.bin
  101756072     Jul 01 10:33:52 2008  m9200-sf2ek9-mz.3.3.1c.bin

Usage for bootflash://sup-local
  120695976 bytes used
   63863640 bytes free
  184559616 bytes total

Step 4 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.

switch# del bootflash:m9200-sf2ek9-kickstart-mz.3.3.1c.bin
switch# del bootflash:m9200-sf2ek9-mz.3.3.1c.bin

Step 5 Save the configuration using the copy running-config startup-config command.

switch# copy running-config startup-config

You can also create a backup of your existing configuration to a file by issuing the copy running-config bootflash:backup_config.txt command. You might want to add a date reference to the .txt file name to identify the file at a later date.

Step 6 Perform the upgrade by issuing the install all command.

switch# install all kickstart bootflash:m9200-s2ek9-kickstart-mz.5.0.x.bin sys 
bootflash:m9200-s2ek9-mz.5.0.x.bin

Verifying image bootflash:/m9200-s2ek9-kickstart-mz.5.0.x.bin for boot variable 


"kickstart".
[####################] 100% -- SUCCESS

Verifying image bootflash:/m9200-s2ek9-mz.5.0.x.bin for boot variable "system".
[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/m9200-s2ek9-mz.5.0.x.bin.
[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/m9200-s2ek9-kickstart-mz.5.0.x.bin.
[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/m9200-s2ek9-mz.5.0.x.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9200-s2ek9-mz.5.0.x.bin.
[####################] 100% -- SUCCESS

Performing Compact Flash and TCAM sanity test.
[####################] 100% -- SUCCESS


Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     1       yes  non-disruptive         reset
     2       yes  non-disruptive       rolling

Images will be upgraded according to following table:
Module Image                Running-Version(pri:alt)        New-Version     Upg-Required
------ ----------  ---------------------------------- -----------------     ------------ 
1     system                                 3.3(1c)              5.0(x)             yes
1     kickstart                              3.3(1c)              5.0(x)             yes
1     bios      v1.0.15(07/16/08): v1.0.15(07/16/08)    v1.0.15(07/16/08)              no
2     slc2                                   3.3(1c)              5.0(x)             yes
2     bios      v1.0.15(07/16/08): v1.0.15(07/16/08)    v1.0.15(07/16/08)              no

Do you want to continue with the installation (y/n)?  [n] y

Install is in progress, please wait.

Notifying services about the upgrade.
[####################] 100% -- SUCCESS

Setting boot variables.
[####################] 100% -- SUCCESS

Performing configuration copy.
[####################] 100% -- SUCCESS

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 2: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Upgrade can no longer be aborted, any failure will result in a disruptive upgrade.

Freeing memory in the file system.
[####################] 100% -- SUCCESS

Loading images into memory.
[####################] 100% -- SUCCESS

Saving external linecard runtime state.
2008 Aug 27 21:08:39 209.165.200.226 %IMAGE_DNLD-SLOT2-2-IMG_DNLD_STARTED:  Module 


image download process.Please wait until completion...
2008 Aug 27 21:09:03 209.165.200.226 %IMAGE_DNLD-SLOT2-2-IMG_DNLD_COMPLETE:  Module 


image download process. Download successful.
[####################] 100% -- SUCCESS

Saving linecard runtime state.
[####################] 100% -- SUCCESS

Saving supervisor runtime state.
[####################] 100% -- SUCCESS

Saving mts state.
[####################] 100% -- SUCCESS

Rebooting the switch to proceed with the upgrade.
Telnet will now be disabled.
Starting new kernel
arch: exit
openpic: enter
openpic: timer
openpic: external
openpic: spurious
openpic: exit
Starting kernel...
 Entered kgdb_console_init:1960

INIT: version 2.85 booting
Checking all filesystems..... done.

directory
Setting the System Clock using the Hardware Clock as reference...System Clock set. 


Local time: Wed Aug 2721:09:37 UTC 2008
Loading system software
Uncompressing system image: bootflash:///m9200-s2ek9-mz.5.0.x.bin
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Uncompressing linecard components
INIT: Entering runlevel: 3
Starting NFS servers: nfsd mountd.

2008 Aug 27 21:10:07 209.165.200.226 %KERN-2-SYSTEM_MSG: Starting kernel... - kernel
2008 Aug 27 21:10:07 209.165.200.226 %KERN-1-SYSTEM_MSG: Entered kgdb_console_init:1960 - 
kernel

Continuing with installation process, please wait.
The login will be disabled until the installation is completed.
2008 Aug 27 21:11:08 switch %PROC_MGR-2-MESG: Entity : (dnld_image) has exited 
successfully
2008 Aug 27 21:11:16 switch %PLATFORM-2-PS_OK: Power supply 2 ok (Serial number 
QCS104811YP)
2008 Aug 27 21:11:16 switch %PLATFORM-2-PS_FANOK: Fan in Power supply 2 ok
2008 Aug 27 21:11:16 switch %PLATFORM-2-FAN_OK: Fan module ok
2008 Aug 27 21:11:16 switch %PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module A ok
2008 Aug 27 21:11:16 switch %PLATFORM-2-CHASSIS_CLKSRC: Current chassis clock source is 
clock-A

Status for linecard upgrade.
[####################] 100% -- SUCCESS

Status for external linecard upgrade.
[####################] 100% -- SUCCESS

Performing supervisor state verification.
[####################] 100% -- SUCCESS

Install has been successful.

MDS Switch
209.165.200.226 login: admin
Password:
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php

Step 7 Issue the show version command.

switch# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
  BIOS:      version 1.0.15
  loader:    version N/A
  kickstart: version 5.0(x)
  system:    version 5.0(x)
  BIOS compile time:       07/16/08
  kickstart image file is: bootflash:///m9200-s2ek9-kickstart-mz.5.0.x.bin
  kickstart compile time:  8/22/2008 25:00:00 [08/25/2008 10:00:03]
  system image file is:    bootflash:///m9200-s2ek9-mz.5.0.x.bin
  system compile time:     8/22/2008 0:00:00 [08/25/2008 11:20:26]


Hardware
  cisco MDS 9222i ("4x1GE IPS, 18x1/2/4Gbps FC/Sup2")
  Motorola, e500v2  with 1036340 kB of memory.
  Processor Board ID JAE11430NJM

  Device name: 209.165.200.226 
  bootflash:    1000440 kB
Kernel uptime is 0 day(s), 0 hour(s), 4 minute(s), 15 second(s)

Last reset at 913177 usecs after  Wed Aug 27 21:09:20 2008

  Reason: Reset due to upgrade
  System version: 3.3(1c)
  Service:

Step 8 Verify the status of the modules on the switch using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    22     4x1GE IPS, 18x1/2/4Gbps FC/Sup2  DS-C9222I-K9       active *
2    48     1/2/4 Gbps FC Module             DS-X9148           ok

Mod  Sw              Hw      World-Wide-Name(s) (WWN)
---  --------------  ------  --------------------------------------------------
1    5.0(x)          1.0     20:01:00:0d:ec:34:82:00 to 20:12:00:0d:ec:34:82:00
2    5.0(x)          0.322   20:41:00:0d:ec:34:82:00 to 20:70:00:0d:ec:34:82:00


Mod  MAC-Address(es)                         Serial-Num
---  --------------------------------------  ----------
1    00-17-94-ee-1b-54 to 00-17-94-ee-1b-5c  JAE11430NJM
2    00-14-a9-74-e0-e8 to 00-14-a9-74-e0-ec  JAB093902HZ

* this terminal session

Downgrading from NX-OS Release 5.0 (1a)

The following section describes how to downgrade from NX-OS Release 5.0(1a) to NX-OS Release 4.2(3).

Downgrading from NX-OS Release 5.0(1a) to NX-OS Release 4.2(3)

The following sections describe how to perform downgrades on an MDS 9513 switch:

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9513 Multilayer Director with Higher Bandwidth Capability

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9513 Multilayer Director Without Higher Bandwidth Capability

To determine whether high bandwidth capability is enabled, issue the show hardware fabric-mode command. The following example shows that the higher bandwidth capability has not been activated:

switch# show hardware fabric-mode
Fabric mode supports only one configuration of 8G FC modules - 4/44 Host-Optimized 8G FC 
module.
switch#

The following example shows that the higher bandwidth capability has been activated:

switch# show hardware fabric-mode
Fabric mode supports 8G FC and above modules.
switch#

The following sections describe how to perform downgrades on an MDS 9509 and MDS 9506 switch:

Downgrading from NX-OS Release 5.0(x) to SAN-OS 3.3(x) on an MDS 9509 or MDS 9506 Switch with an Installed Generation 3 8-Gbps Fibre Channel Switching Module

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9509 or MDS 9506 Switch Without an Installed Generation 3 8-Gbps Fibre Channel Switching Module

The following section describes how to perform a downgrade on an MDS 9222i switch:

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9222i Switch

For information on supported chassis and modules, refer to "NX-OS Release 4.x Supported Hardware" section. For information on the procedures for installing and upgrading software for Intelligent Storage Services on the Cisco MDS 9000 Family Storage Services Module (SSM), refer to the Cisco MDS 9000 Family Storage Services Module Software Installation and Upgrade Guide.


Note If you are running NX-OS Release 4.2(x) in combination with an SSI Release 4.2(x) image and you want to downgrade to SAN-OS Release 3.3(2) with the SSI Release 3.2(3s) image, you must delete all SANTap configurations prior to the downgrade. Downgrading without completely deleting the SANTap configurations is not supported.


Downgrading from NX-OS Release 4.2(3) to NX-OS Release 4.2(1b)

This procedure describes how to downgrade from NX-OS Release 4.2(3) to NX-OS Release 4.2(1b) on a switch with the SSN-16 module installed.

switch# show module

Mod  Ports  Module-Type                      Model              Status

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

2    16     16x1GE, Storage Services Node    DS-X9316-SSNK9     ok

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

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

 

Mod  Sw              Hw      World-Wide-Name(s) (WWN)

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

2    5.0(1a)          3.6     --

5    5.0(1a)          1.4     --

6    5.0(1a)          1.6     --

........

 

switch# install all kickstart bootflash:m9500-sf2ek9-kickstart-mz.5.0.1a.bin sys 
bootflash:m9500-sf2ek9-mz.5.0.1a.bin

 

Verifying image bootflash:/m9500-sf2ek9-kickstart-mz.5.0.1a.bin for boot variable 
"kickstart".

[####################] 100% -- SUCCESS

 

Verifying image bootflash:/m9500-sf2ek9-mz.5.0.1a.bin for boot variable "system".

[####################] 100% -- SUCCESS

 

Verifying image type.

[####################] 100% -- SUCCESS

 

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.5.0.1a.bin.

[####################] 100% -- SUCCESS

 

Extracting "ips16" version from image bootflash:/m9500-sf2ek9-mz.5.0.1a.bin.

[####################] 100% -- SUCCESS

 

Extracting "ssi" version from image bootflash:/m9500-sf2ek9-mz.5.0.1a.bin.

[####################] 100% -- SUCCESS

 

Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.5.0.1a.bin.

[####################] 100% -- SUCCESS

 

Extracting "system" version from image bootflash:/m9500-sf2ek9-mz.5.0.1a.bin.

[####################] 100% -- SUCCESS

 

Extracting "kickstart" version from image bootflash:/m9500-sf2ek9-kickstart-mz.5.0.1a.bin.

[####################] 100% -- SUCCESS

 

Performing Compact Flash and TCAM sanity test.

[####################] 100% -- SUCCESS

 

Notifying services about system upgrade.

[####################] 100% -- SUCCESS

 

 

 

Compatibility check is done:

Module  bootable          Impact  Install-type  Reason

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

     2       yes      disruptive       rolling  Hitless upgrade is not supported

     5       yes  non-disruptive         reset

     6       yes  non-disruptive         reset

 

 

Other miscellaneous information for installation:

Module  info

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

     2  Hitless upgrade is not supported

 

 

Images will be upgraded according to following table:

Module       Image                Running-Version(pri:alt) 	New-Version 		Upg-Required

------  ----------  -------------------------------------- ---------------- ------------
     2        slc2                                  5.0(1a)             4.2(3) yes
     2       ips16                                  5.0(1a)             4.2(3) yes
     2         ssi                                  5.0(1a)             4.2(3) yes
     2        bios   v1.0.16(10/23/08):  v1.0.16(10/23/08)   v1.0.16(10/23/08) no
     5      system                                  5.0(1a)             4.2(3) yes
     5   kickstart                                  5.0(1a)             4.2(3) yes
     5        bios   v1.0.10(01/08/09):  v1.0.10(01/08/09)   v1.0.10(01/08/09) no
     6      system                                  5.0(1a)             4.2(3) yes
     6   kickstart                                  5.0(1a)             4.2(3) yes
     6        bios   v1.0.10(01/08/09):  v1.0.10(01/08/09)   v1.0.10(01/08/09) no


Do you want to continue with the installation (y/n)?  [n] y

 

Install is in progress, please wait.

 

Syncing image bootflash:/m9500-sf2ek9-kickstart-mz.5.0.1a.bin to standby.

[####################] 100% -- SUCCESS

 

Syncing image bootflash:/m9500-sf2ek9-mz.5.0.1a.bin to standby.

[####################] 100% -- SUCCESS

 

Setting boot variables.

[####################] 100% -- SUCCESS

 

Performing configuration copy.

[####################] 100% -- SUCCESS

 

Module 2: Refreshing compact flash and upgrading bios/loader/bootrom.

Warning: please do not remove or power off the module at this time.

[####################] 100% -- SUCCESS

 

Module 5: Refreshing compact flash and upgrading bios/loader/bootrom.

Warning: please do not remove or power off the module at this time.

[####################] 100% -- SUCCESS

 

Module 6: Refreshing compact flash and upgrading bios/loader/bootrom.

Warning: please do not remove or power off the module at this time.

[####################] 100% -- SUCCESS

2009 Dec 10 18:55:46 switch %PLATFORM-2-MOD_REMOVE: Module 6 removed (Serial number 
JAE1241X10O)

2009 Dec 10 18:58:04 switch %IDEHSD-STANDBY-2-MOUNT: slot0: online

 

Module 6: Waiting for module online.

 -- SUCCESS

 

Notifying services about the switchover.

[####################] 100% -- SUCCESS

 

 

"Switching over onto standby".

 

----------

Note

----------

>> MDS-Bootloader-01.00.10 (Jan  8 2009 - 14:53:42) (MPC7447A), Build: 01.00.10

 

INFO: Booting off primary flash.

CPU:   MPC7447A v1.1 @ 1411 MHz

DRAM: SPD Checksum ok!

SPD Checksum ok!

-- DIMM1 (unbuffered) has 1 banks

-- DIMM2 (unbuffered) has 1 banks

ECC Initialization of Bank 0: Done

ECC Initialization of Bank 1: Done

CAS Latency = 2.5 tRP = 3 tRAS = 7 tRCD=3

Total SDRAM memory is 1024 MB

40000000

INFO: SDRAM tests PASSED.

done.

PCI 0 bus mode: Conventional PCI

PCI 1 bus mode: Conventional PCI

L2 Cache Initialization.

 

Internal SRAM ECC Initialization: Done

IDE:   Bus 0: OK Bus 1: OK

  Device 0: Model: SILICONSYSTEMS INC 1GB Firm: 841-023 Ser#: 506VTP69Sn605DC0008

            Type: Hard Disk

            Capacity: 999.1 MB = 0.9 GB (2046240 x 512)

  Device 3: Model: SMART CF Firm: 2006081 Ser#: 0000101152000001263

            Type: Hard Disk

            Capacity: 991.2 MB = 0.9 GB (2030112 x 512)

 

Booting bootflash:/m9500-sf2ek9-kickstart-mz.4.2.1b.bin ...

......................

Automatic boot of image at addr 0x00000000 ...

Starting kernel...

INIT: version 2.85 booting

Checking all filesystems..r.r.r.r.r done.

no matching password file entry

 

delete line `adminbackup:$1$Oip/C5Ci$oOdx7oJSlBCFpNRmQK4na.:13419:0:99999:7:::'? No

pwck: no changes

Setting the System Clock using the Hardware Clock as reference...System Clock set. Local 
time: Thu Dec 10 18:56:59 UTC 2009

Loading system software

Uncompressing system image: bootflash:/m9500-sf2ek9-mz.4.2.1b.bin

CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC

INIT: Entering runlevel: 3

 

 

is_module_netboot returned 0

Continuing with installation, please wait

2009 Dec 10 18:58:04 172.25.229.221 %IDEHSD-2-MOUNT: slot0: online

 

Module 6: Waiting for module online.

 -- SUCCESS

2009 Dec 10 18:58:41 172.25.229.221 %SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is 
becoming active (pre-start phase).

2009 Dec 10 18:58:41 172.25.229.221 %SYSMGR-2-HASWITCHOVER_START: This supervisor is 
becoming active.

2009 Dec 10 18:58:41 172.25.229.221 %SYSMGR-2-SWITCHOVER_OVER: Switchover completed.

 

Module 2: Disruptive upgrading.

[#                   ]   0%2009 Dec 10 19:01:59 switch %PLATFORM-2-MOD_DETECT: Module 2 
detected (Serial number JAE1227NULE) Module-Type 16x1GE, Storage Services Node Model 
DS-X9316-SSNK9

2009 Dec 10 19:01:59 switch %PLATFORM-2-MOD_PWRUP: Module 2 powered up (Serial number 
JAE1227NULE)

2009 Dec 10 19:02:41 switch %IMAGE_DNLD-SLOT2-2-IMG_DNLD_STARTED:  Module image download 
process. Please wait until completion...

2009 Dec 10 19:02:59 switch %IMAGE_DNLD-SLOT2-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.

[####################] 100% -- SUCCESS

 

Install has been successful.

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9513 Multilayer Director with Higher Bandwidth Capability

This procedure describes how to downgrade from NX-OS Release 5.0(x) on an MDS 9513 Multilayer Director with higher bandwidth capability. To downgrade on an MDS 9513 Multilayer Director that does not have higher bandwidth capability, see "Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9513 Multilayer Director Without Higher Bandwidth Capability" section.

To verify that higher bandwidth capabilities are activated, issue the show hardware fabric-mode command. The following example shows that the higher bandwidth capability has been activated:

switch# show hardware fabric-mode
Fabric mode supports 8G FC and above modules.
switch#

The following example shows that the higher bandwidth capability has not been activated:

switch# show hardware fabric-mode
Fabric mode supports only one configuration of 8G FC modules - 4/44 Host-Optimized 8G FC 
module.
switch#

Use the install all command to downgrade the switch and handle configuration conversions. When downgrading any switch in the Cisco MDS 9000 Family, avoid using the reload command.


Note When downgrading to a release earlier than NX-OS Release 5.0(x) and if you have a Generation 3 8-Gbps Fibre Channel Switching Modules and the Fabric 2 module (DS-13SLT-FAB2) installed, the installation will fail. It is recommended that you power down these modules and then downgrade again.



Note A downgrade from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) with higher bandwidth capability enabled is disruptive.


To downgrade to Cisco MDS SAN-OS Release 3.3(x) from NX-OS Release 5.0(x), follow these steps:


Step 1 Verify that the system image files for the downgrade are present on the active supervisor module bootflash:.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   16604160     Jul 01 10:20:07 2008  m9500-sf2ek9-kickstart-mz.3.3.1c.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin
   78718938     Jul 01 10:18:09 2008  m9500-sf2ek9-mz.3.3.1c.bin

Usage for bootflash://sup-local
  211411892 bytes used
  167810476 bytes free
  379322368 bytes total

Step 2 If the software image file is not present, download it from an FTP or TFTP server to the active supervisor module bootflash:. You can obtain the software image file from the Cisco.com software download center at the following URL:

http://www.cisco.com/cisco/software/navigator.html


Note If you need more space on the active supervisor module bootflash:, use the delete command to remove unnecessary files and follow Step 3 through Step 6.


switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-kickstart-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin
switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-mz.3.3.1c.bin

Step 3 Ensure that the required space is available on the active supervisor.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin

Usage for bootflash://sup-local
  116188794 bytes used
   68370822 bytes free
  184559616 bytes total

Step 4 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.

switch# del bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin
switch# del bootflash:m9500-sf2ek9-mz.5.0.x.bin

Step 5 Verify that there is enough space available for the standby supervisor.

switch(standby)# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin

Usage for bootflash://sup-local
  116188794 bytes used
   68370822 bytes free
  184559616 bytes total

Step 6 If you need more space on the standby supervisor module bootflash, delete unnecessary files to make space available.

switch(standby)# del bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin
switch(standby)# del bootflash:m9500-sf2ek9-mz.5.0.x.bin

Step 7 Issue the show incompatibility system image-filename command to determine if you need to disable any features not supported in the earlier release.

switch# show incompatibility system bootflash:m9500-sf2ek9-mz.3.3.1c.bin
The following configurations on active are incompatible with the system image
1) Service : port-channel , Capability : CAP_FEATURE_AUTO_CREATED_41_PORT_CHANNEL
Description : auto create enabled ports or auto created port-channels are present
Capability requirement : STRICT 
Disable command : 
1.Disable autocreate on interfaces (no channel-group auto).
2.Convert autocreated port channels to be persistent (port-channel 1 persistent)
... 

Step 8 Disable any features that are incompatible with the downgrade system image.

switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# interface fcip 31
switch(config-if)# no channel-group auto
switch(config-if)# end
switch# port-channel 127 persistent
switch# 

Step 9 Save the configuration using the copy running-config startup-config command.

switch# copy running-config startup-config

Step 10 Verify if a Generation 3 8-Gbps module is installed on the switch using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    22     4x1GE IPS, 18x1/2/4Gbps FC Modul DS-X9304-18K9      ok
2    12     1/2/4 Gbps FC Module             DS-X9112           ok
3    12     1/2/4 Gbps FC Module             DS-X9112           ok
4    24     1/2/4 Gbps FC Module             DS-X9124           ok
5    48     1/2/4 Gbps FC Module             DS-X9148           ok
6    4      10 Gbps FC Module                DS-X9704           ok
7    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
8    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
9    22     4x1GE IPS, 18x1/2/4Gbps FC Modul DS-X9304-18K9      ok
10   24     1/2/4 Gbps FC Module             DS-X9124           ok
11   48     1/2/4 Gbps FC Module             DS-X9148           ok
12   48     1/2/4/8 Gbps 48-Port FC Module   DS-X9248-96        ok
13   48     1/2/4/8 Gbps 4/44-Port FC Module DS-X9248-48K9      ok
...

Step 11 If there is a Generation 3 8-Gbps module installed, then do Steps a through c. Otherwise, go to Step 12.

a. Power off the Generation 3 8-Gbps module.

switch# configure terminal
switch(config)# poweroff module 12
switch(config)# 2009 Jan 7 18:40:05 switch %PLATFORM-2-PFM_MODULE_POWER_OFF: Manual 
power-off of Module 12 from Command Line Interface
switch(config)# 2009 Jan 7 18:40:10 switch %PLATFORM-2-MOD_PWRDN: Module 12 powered 
down (Serial number JAE1234SOWO)
switch(config)# poweroff module 13
switch(config)# 2009 Jan 7 18:40:40 switch %PLATFORM-2-PFM_MODULE_POWER_OFF: Manual 
power-off of Module 13 from Command Line Interface
switch(config)# 2009 Jan 7 18:40:45 switch %PLATFORM-2-MOD_PWRDN: Module 13 powered 
down (Serial number JAE1234SOWO)

b. Verify that the Generation 3 8-Gbps modules have been powered off.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    22     4x1GE IPS, 18x1/2/4Gbps FC Modul DS-X9304-18K9      ok
2    12     1/2/4 Gbps FC Module             DS-X9112           ok
3    12     1/2/4 Gbps FC Module             DS-X9112           ok
4    24     1/2/4 Gbps FC Module             DS-X9124           ok
5    48     1/2/4 Gbps FC Module             DS-X9148           ok
6    4      10 Gbps FC Module                DS-X9704           ok
7    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
8    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
9    22     4x1GE IPS, 18x1/2/4Gbps FC Modul DS-X9304-18K9      ok
10   24     1/2/4 Gbps FC Module             DS-X9124           ok
11   48     1/2/4 Gbps FC Module             DS-X9148           ok
12   48     1/2/4/8 Gbps 48-Port FC Module   DS-X9248-96        powered-dn
13   48     1/2/4/8 Gbps 4/44-Port FC Module DS-X9248-48K9      powered-dn
...

c. Remove the Generation 3 8-Gbps modules.

Step 12 Issue the install all command to downgrade the software.


Note When downgrading on an MDS 9513 Director, (running in high bandwidth mode with 8-Gbps Fibre Channel modules) consider the following:

Downgrading to MDS SAN-OS Release 3.x is disruptive.

Downgrading to MDS SAN-OS Release 3.x requires a switch reload.

The Fabric 2 module features are not available after a downgrade to SAN-OS Release 3.x or earlier.


switch# install all kickstart bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin system 
bootflash:m9500-sf2ek9-mz.3.3.1c.bin

Verifying image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin for boot variable 
"kickstart".
[####################] 100% -- SUCCESS

Verifying image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin for boot variable "system".
[####################] 100% -- SUCCESS

Verifying image type.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "18_4" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "ssi" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "18_4" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "ssi" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Performing Compact Flash and TCAM sanity test.
[####################] 100% -- SUCCESS

Notifying services about system upgrade.
[####################] 100% -- SUCCESS

Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     1       yes      disruptive         reset  Incompatible fabric switching mode
     2       yes      disruptive         reset  Incompatible fabric switching mode
     3       yes      disruptive         reset  Incompatible fabric switching mode
     4       yes      disruptive         reset  Incompatible fabric switching mode
     5       yes      disruptive         reset  Incompatible fabric switching mode
     6       yes      disruptive         reset  Incompatible fabric switching mode 
     7       yes      disruptive         reset  Incompatible fabric switching mode 
     8       yes      disruptive         reset  Incompatible fabric switching mode 
     9       yes      disruptive         reset  Incompatible fabric switching mode 
    10       yes      disruptive         reset  Incompatible fabric switching mode 
    11       yes      disruptive         reset  Incompatible fabric switching mode 


Other miscellaneous information for installation:
Module  info
------  ----------------------------------
     1  FC ports 1-18 are hitless, GigE 1-4 are Hitful, and Intelligent Applications running are Hitful
     9  FC ports 1-18 are hitless, GigE 1-4 are Hitful, and Intelligent Applications running are Hitful


Images will be upgraded according to following table:
Module       Image                  Running-Version(pri:alt)           New-Version  Upg-Required
------  ----------  ----------------------------------------  --------------------  ------------
     1        slc2                                    4.2(x)               3.3(1c)           yes
     1        18_4                                    4.2(x)               3.3(1c)           yes
     1         ssi                                    4.2(x)               3.3(1c)           yes
     1        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     2        slc2                                    4.2(x)               3.3(1c)           yes
     2        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     3        slc2                                    4.2(x)               3.3(1c)           yes
     3        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     4        slc2                                    4.2(x)               3.3(1c)           yes
     4        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     5        slc2                                    4.2(x)               3.3(1c)           yes
     5        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     6        slc2                                    4.2(x)               3.3(1c)           yes
     6        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     7      system                                    4.2(x)               3.3(1c)           yes
     7   kickstart                                    4.2(x)               3.3(1c)           yes
     7        bios       v1.0.6(06/14/07):  v1.0.6(06/14/07)      v1.0.6(06/14/07)            no
     8      system                                    4.2(x)               3.3(1c)           yes
     8   kickstart                                    4.2(x)               3.3(1c)           yes
     8        bios       v1.0.6(06/14/07):  v1.0.6(06/14/07)      v1.0.6(06/14/07)            no
     9        slc2                                    4.2(x)               3.3(1c)           yes
     9        18_4                                    4.2(x)               3.3(1c)           yes
     9         ssi                                    4.2(x)               3.3(1c)           yes
     9        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
    10        slc2                                    4.2(x)               3.3(1c)           yes
    10        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
    11        slc2                                    4.2(x)               3.3(1c)           yes
    11        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no

ISSU can not be performed due to an incompatible fabric switching mode. Switch will go through a 
disruptive upgrade.

Switch will be reloaded for disruptive upgrade.
Do you want to continue with the installation (y/n)?  [n] y

Install is in progress, please wait.

Syncing image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin to standby.
[####################] 100% -- SUCCESS

Syncing image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin to standby.
[####################] 100% -- SUCCESS

Setting boot variables.
[####################] 100% -- SUCCESS

Performing configuration copy.
[####################] 100% -- SUCCESS

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 2: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 3: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 4: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 5: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 6: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 7: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 8: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 9: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 10: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 11: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Converting startup config.
[####################] 100% -- SUCCESS

Finishing the upgrade, switch will reboot in 10 seconds.
switch#

>> MDS-Bootloader-01.00.06 (Jun 14 2007 - 15:04:07) (MPC7447A)

INFO: Booting off primary flash.
CPU:   MPC7447A v1.1 @ 1411 MHz
DRAM: SPD Checksum ok!
SPD Checksum ok!
-- DIMM1 has 1 banks
-- DIMM2 has 1 banks
ECC Initialization of Bank 0: Done
ECC Initialization of Bank 1: Done
CAS Latency = 2.5 tRP = 3 tRAS = 7 tRCD=3
Total SDRAM memory is 1024 MB
40000000
INFO: SDRAM tests PASSED.
PCI 0 bus mode: Conventional PCI
PCI 1 bus mode: Conventional PCI
L2 Cache Initialization.

Internal SRAM ECC Initialization: Done
IDE:   Bus 0: OK
  Device 0: Model: TOSHIBA THNCF1G02DG Firm:  Ser#: TSBC1G0206301T63902A
            Type: Hard Disk
            Capacity: 976.9 MB = 0.9 GB (2000880 x 512)

Booting bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin ...
...............
Automatic boot of image at addr 0x00000000 ...
Starting kernel...
INIT: version 2.78 booting
Checking all filesystems..r.r.r.. done.
Loading system software
Uncompressing system image: bootflash:/m9500-sf2ek9-mz.3.3.1c.bin
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
INIT: Entering runlevel: 3

2008 Aug 27 20:23:54 209.165.200.226 %KERN-1-SYSTEM_MSG:  calling inter_module_register for mgmt
2008 Aug 27 20:23:56 209.165.200.226 %PLATFORM-2-PS_OK: Power supply 1 ok (Serial number DCH0935005K)
2008 Aug 27 20:23:56 209.165.200.226 %PLATFORM-2-PS_FANOK: Fan in Power supply 1 ok
2008 Aug 27 20:23:56 209.165.200.226 %PLATFORM-2-PS_OK: Power supply 2 ok (Serial number DCH09350060)
2008 Aug 27 20:23:56 209.165.200.226 %PLATFORM-2-PS_FANOK: Fan in Power supply 2 ok
2008 Aug 27 20:23:56 209.165.200.226 %PLATFORM-2-FANMOD_FAN_OK: Fan module 1 (Front fan) ok
2008 Aug 27 20:23:56 209.165.200.226 %PLATFORM-2-FANMOD_FAN_OK: Fan module 2 (Rear fan) ok
2008 Aug 27 20:23:56 209.165.200.226 %PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module A ok
2008 Aug 27 20:23:56 209.165.200.226 %PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module B ok
2008 Aug 27 20:23:56 209.165.200.226 %PLATFORM-2-CHASSIS_CLKSRC: Current chassis clock source is 
clock-A


MDS Switch
209.165.200.226 login: 2008 Aug 27 20:24:27 209.165.200.226 %PLATFORM-2-MOD_PWRIDPROMFAIL: Module 12 
failedto power up due to IDPROM read error
2008 Aug 27 20:24:29 209.165.200.226 %PLATFORM-2-MOD_PWRIDPROMFAIL: Module 13 failed to power up due to 
IDPROM read error
2008 Aug 27 20:24:50 209.165.200.226 %IMAGE_DNLD-SLOT1-2-IMG_DNLD_STARTED:  Module image download 
process.Please wait until completion...
2008 Aug 27 20:25:02 209.165.200.226 %IMAGE_DNLD-SLOT9-2-IMG_DNLD_STARTED:  Module image download 
process.Please wait until completion...
2008 Aug 27 20:25:09 209.165.200.226 %IMAGE_DNLD-SLOT4-2-IMG_DNLD_STARTED:  Module image download 
process.Please wait until completion...
2008 Aug 27 20:25:09 209.165.200.226 %IMAGE_DNLD-SLOT1-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.
2008 Aug 27 20:25:21 209.165.200.226 %IMAGE_DNLD-SLOT9-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.
2008 Aug 27 20:25:27 209.165.200.226 %IMAGE_DNLD-SLOT4-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.
2008 Aug 27 20:25:28 209.165.200.226 %IMAGE_DNLD-SLOT2-2-IMG_DNLD_STARTED:  Module image download 
process.Please wait until completion...
2008 Aug 27 20:25:33 209.165.200.226 %IMAGE_DNLD-SLOT3-2-IMG_DNLD_STARTED:  Module image download 
process.Please wait until completion...
2008 Aug 27 20:25:36 209.165.200.226 %IMAGE_DNLD-SLOT5-2-IMG_DNLD_STARTED:  Module image download 
process.Please wait until completion...
2008 Aug 27 20:25:37 209.165.200.226 %IMAGE_DNLD-SLOT6-2-IMG_DNLD_STARTED:  Module image download 
process.Please wait until completion...
2008 Aug 27 20:25:41 209.165.200.226 %IMAGE_DNLD-SLOT10-2-IMG_DNLD_STARTED:  Module image download 
process. Please wait until completion...
2008 Aug 27 20:25:43 209.165.200.226 %IMAGE_DNLD-SLOT11-2-IMG_DNLD_STARTED:  Module image download 
process. Please wait until completion...
2008 Aug 27 20:25:48 209.165.200.226 %IMAGE_DNLD-SLOT2-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.
2008 Aug 27 20:25:49 209.165.200.226 %IMAGE_DNLD-SLOT3-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.
2008 Aug 27 20:25:56 209.165.200.226 %IMAGE_DNLD-SLOT5-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.
2008 Aug 27 20:25:58 209.165.200.226 %IMAGE_DNLD-SLOT6-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.
2008 Aug 27 20:26:01 209.165.200.226 %IMAGE_DNLD-SLOT10-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.
2008 Aug 27 20:26:04 209.165.200.226 %IMAGE_DNLD-SLOT11-2-IMG_DNLD_COMPLETE:  Module image download 
process. Download successful.

MDS Switch
209.165.200.226 login: admin
Password:
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software may be covered under the GNU Public
License or the GNU Lesser General Public License. A copy of
each such license is available at
http://www.gnu.org/licenses/gpl.html and
http://www.gnu.org/licenses/lgpl.html

Step 13 Verify the status of the modules on the switch using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    22     4x1GE IPS, 18x1/2/4Gbps FC Modu  DS-X9304-18K9      ok
2    12     1/2/4 Gbps FC Module             DS-X9112           ok
3    12     1/2/4 Gbps FC Module             DS-X9112           ok
4    24     1/2/4 Gbps FC Module             DS-X9124           ok
5    48     1/2/4 Gbps FC Module             DS-X9148           ok
6    4      10 Gbps FC Module                DS-X9704           ok
7    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
8    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
9    22     4x1GE IPS, 18x1/2/4Gbps FC Modu  DS-X9304-18K9      ok
10   24     1/2/4 Gbps FC Module             DS-X9124           ok
11   48     1/2/4 Gbps FC Module             DS-X9148           ok

Mod  Sw              Hw      World-Wide-Name(s) (WWN)
---  --------------  ------  --------------------------------------------------
1    3.3(1c)         0.0     20:01:00:05:30:01:ca:32 to 20:12:00:05:30:01:ca:32
2    3.3(1c)         0.196   20:41:00:05:30:01:ca:32 to 20:4c:00:05:30:01:ca:32
3    3.3(1c)         0.196   20:81:00:05:30:01:ca:32 to 20:8c:00:05:30:01:ca:32
4    3.3(1c)         1.3     20:c1:00:05:30:01:ca:32 to 20:d8:00:05:30:01:ca:32
5    3.3(1c)         0.306   21:01:00:05:30:01:ca:32 to 21:30:00:05:30:01:ca:32
6    3.3(1c)         0.522   21:41:00:05:30:01:ca:32 to 21:44:00:05:30:01:ca:32
7    3.3(1c)         0.3     --
8    3.3(1c)         0.3     --
9    3.3(1c)         1.0     22:01:00:05:30:01:ca:32 to 22:12:00:05:30:01:ca:32
10   3.3(1c)         0.196   22:41:00:05:30:01:ca:32 to 22:58:00:05:30:01:ca:32
11   3.3(1c)         0.302   22:81:00:05:30:01:ca:32 to 22:b0:00:05:30:01:ca:32
...

Step 14 Verify that the switch is running the required software version by issuing the show version command.

switch# show version
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software may be covered under the GNU Public
License or the GNU Lesser General Public License. A copy of
each such license is available at
http://www.gnu.org/licenses/gpl.html and
http://www.gnu.org/licenses/lgpl.html

Software
  BIOS:      version 1.0.6
  kickstart: version 3.3(1c)
  system:    version 3.3(1c)

  BIOS compile time:       06/14/07
  kickstart image file is: bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin
  kickstart compile time:  5/23/2008 19:00:00 [06/20/2008 07:15:58]
  system image file is:    bootflash:/m9500-sf2ek9-mz.3.3.1c.bin
  system compile time:     5/23/2008 19:00:00 [06/20/2008 07:50:40]

Hardware
  cisco MDS 9513 ("Supervisor/Fabric-2")
  Motorola, 7447a, altivec with 1029868 kB of memory.
  Processor Board ID JAB09230102

  bootflash:  1000440 kB
  slot0:            0 kB

209.165.200.226   kernel uptime is 0 days 0 hour 5 minute(s) 55 second(s)

  Last reset at 176977 usecs after Wed Aug 27 20:21:39 2008
    Reason: Reset by installer
    System version: 4.2(x)
    Service:

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9513 Multilayer Director Without Higher Bandwidth Capability

To verify that higher bandwidth capabilities are not activated, issue the show hardware fabric-mode command. The following example shows that the higher bandwidth capability has not been activated:

switch# show hardware fabric-mode
Fabric mode supports only one configuration of 8G FC modules - 4/44 Host-Optimized 8G FC 
module.
switch#

The following example shows that the higher bandwidth capability has been activated:

switch# show hardware fabric-mode
Fabric mode supports 8G FC and above modules.
switch#

Use the install all command to downgrade the switch and handle configuration conversions. When downgrading any switch in the Cisco MDS 9000 Family, avoid using the reload command.

To downgrade to Cisco MDS SAN-OS Release 3.3(x) from NX-OS Release 5.0(x), follow these steps:


Step 1 Verify that the system image files for the downgrade are present on the active supervisor module bootflash:.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   16604160     Jul 01 10:20:07 2008  m9500-sf2ek9-kickstart-mz.3.3.1c.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin
   78718938     Jul 01 10:18:09 2008  m9500-sf2ek9-mz.3.3.1c.bin

Usage for bootflash://sup-local
  211411892 bytes used
  167810476 bytes free
  379322368 bytes total

Step 2 If the software image file is not present, download it from an FTP or TFTP server to the active supervisor module bootflash:. You can obtain the software image file from the Cisco.com software download center at the following URL:

http://www.cisco.com/cisco/software/navigator.html


Note If you need more space on the active supervisor module bootflash:, use the delete command to remove unnecessary files and follow Step 3 through Step 6.


switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-kickstart-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin
switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-mz.3.3.1c.bin

Step 3 Ensure that the required space is available on the active supervisor.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin

Usage for bootflash://sup-local
  116188794 bytes used
   68370822 bytes free
  184559616 bytes total

Step 4 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.

switch# del bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin
switch# del bootflash:m9500-sf2ek9-mz.5.0.x.bin

Step 5 Verify that there is enough space available for the standby supervisor.

switch(standby)# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin

Usage for bootflash://sup-local
  116188794 bytes used
   68370822 bytes free
  184559616 bytes total

Step 6 If you need more space on the standby supervisor module bootflash, delete unnecessary files to make space available.

switch(standby)# del bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin
switch(standby)# del bootflash:m9500-sf2ek9-mz.5.0.x.bin

Step 7 Issue the show incompatibility system image-filename command to determine if you need to disable any features not supported by the earlier release.

switch# show incompatibility system bootflash:m9500-sf2ek9-mz.3.3.1c.bin
The following configurations on active are incompatible with the system image
1) Service : port-channel , Capability : CAP_FEATURE_AUTO_CREATED_41_PORT_CHANNEL
Description : auto create enabled ports or auto created port-channels are present
Capability requirement : STRICT 
Disable command : 
1.Disable autocreate on interfaces (no channel-group auto).
2.Convert autocreated port channels to be persistent (port-channel 1 persistent)
...

Step 8 Disable any features that are incompatible with the downgrade system image.

switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# interface fcip 31
switch(config-if)# no channel-group auto
switch(config-if)# end
switch# port-channel 127 persistent
switch# 

Step 9 Save the configuration using the copy running-config startup-config command.

switch# copy running-config startup-config

Step 10 Issue the install all command to downgrade the software.

switch# install all kickstart bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin system 
bootflash:m9500-sf2ek9-mz.3.3.1c.bin

Verifying image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin for boot variable 
"kickstart".
[####################] 100% -- SUCCESS

Verifying image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin for boot variable "system".
[####################] 100% -- SUCCESS

Verifying image type.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Performing Compact Flash and TCAM sanity test.
[####################] 100% -- SUCCESS

Notifying services about system upgrade.
[####################] 100% -- SUCCESS


Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     1       yes  non-disruptive       rolling
     3       yes  non-disruptive       rolling
     4       yes  non-disruptive       rolling
     7       yes  non-disruptive         reset
     8       yes  non-disruptive         reset
     9       yes  non-disruptive       rolling
    10       yes  non-disruptive       rolling
    11       yes  non-disruptive       rolling


Images will be upgraded according to following table:
Module       Image                  Running-Version(pri:alt)           New-Version  Upg-Required
------  ----------  ----------------------------------------  --------------------  ------------
     1        slc2                                    5.0(x)               3.3(1c)           yes
     1        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     3         slc                                    5.0(x)               3.3(1c)           yes
     3        bios                          v1.1.0(10/24/03)      v1.1.0(10/24/03)            no
     4        slc2                                    5.0(x)               3.3(1c)           yes
     4        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     7      system                                    5.0(x)               3.3(1c)           yes
     7   kickstart                                    5.0(x)               3.3(1c)           yes
     8        bios      v1.0.6(06/14/07):   v1.0.6(06/14/07)      v1.0.6(06/14/07)            no
     8      system                                    5.0(x)               3.3(1c)           yes
     8   kickstart                                    5.0(x)               3.3(1c)           yes
     8        bios      v1.0.6(06/14/07):   v1.0.6(06/14/07)      v1.0.6(06/14/07)            no
     9        slc2                                    5.0(x)               3.3(1c)           yes
     9        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
    10         slc                                    5.0(x)               3.3(1c)           yes
    10        bios                          v1.1.0(10/24/03)      v1.1.0(10/24/03)            no
    11        slc2                                    5.0(x)               3.3(1c)           yes
    11        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no


Do you want to continue with the installation (y/n)?  [n] Y

Install is in progress, please wait.

Syncing image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin to standby.
[####################] 100% -- SUCCESS

Syncing image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin to standby.
[####################] 100% -- SUCCESS

Setting boot variables.
[####################] 100% -- SUCCESS

Performing configuration copy.
[####################] 100% -- SUCCESS

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 3: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 4: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 7: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 8: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 9: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 10: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 11: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS
2008 Jul  2 06:35:55 switch %PLATFORM-2-MOD_REMOVE: Module 5 removed (Serial number 
JAB0923010G)

Module 7: Waiting for module online.
 -- SUCCESS

Notifying services about the switchover.
[####################] 100% -- SUCCESS


"Switching over onto standby".


Note At this point, the previously active supervisor module is rebooting after a nondisruptive switchover has taken place. For more information, refer to the "Configuring High Availability" chapter in the Cisco MDS 9000 Family NX-OS High Availability and Redundancy Configuration Guide.



>> MDS-Bootloader-01.00.06 (Jun 14 2007 - 15:04:07) (MPC7447A)

INFO: Booting off primary flash.
CPU:   MPC7447A v1.1 @ 1411 MHz
DRAM: SPD Checksum ok!
SPD Checksum ok!
-- DIMM1 has 1 banks
-- DIMM2 has 1 banks
ECC Initialization of Bank 0: Done
ECC Initialization of Bank 1: Done
CAS Latency = 2.5 tRP = 3 tRAS = 7 tRCD=3
Total SDRAM memory is 1024 MB
40000000
INFO: SDRAM tests PASSED.
PCI 0 bus mode: Conventional PCI
PCI 1 bus mode: Conventional PCI
L2 Cache Initialization.

Internal SRAM ECC Initialization: Done
IDE:   Bus 0: OK
  Device 0: Model: TOSHIBA THNCF1G02DG Firm:  Ser#: TSBC1G0206301W51019A
            Type: Hard Disk
            Capacity: 976.9 MB = 0.9 GB (2000880 x 512)

Booting bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin ...
...............
Automatic boot of image at addr 0x00000000 ...
Starting kernel...
INIT: version 2.78 booting
Checking all filesystems..r.r.r.r. done.
Loading system software
Uncompressing system image: bootflash:/m9500-sf2ek9-mz.3.3.1c.bin
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCC
INIT: Entering runlevel: 3

Step 11 Verify the status of the modules on the switch using the show module command

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    12     1/2/4 Gbps FC Module             DS-X9112           ok
3    16     1/2 Gbps FC Module               DS-X9016           ok
4    48     1/2/4 Gbps FC Module             DS-X9148           ok
7    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
8    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
9    24     1/2/4 Gbps FC Module             DS-X9124           ok
10   16     1/2 Gbps FC Module               DS-X9016           ok
11   4      10 Gbps FC Module                DS-X9704           ok
...

Downgrading from NX-OS Release 5.0(x) to SAN-OS 3.3(x) on an MDS 9509 or MDS 9506 Switch with an Installed Generation 3 8-Gbps Fibre Channel Switching Module

To downgrade to Cisco MDS SAN-OS Release 3.3(x) from NX-OS Release 5.0(x), on an MDS 9509 or MDS 9506 switch with a Generation 3 8-Gbps Fibre Channel Switching module installed, follow these steps:


Step 1 Verify that the system image files for the downgrade are present on the active supervisor module bootflash:.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   16604160     Jul 01 10:20:07 2008  m9500-sf2ek9-kickstart-mz.3.3.1c.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin
   78718938     Jul 01 10:18:09 2008  m9500-sf2ek9-mz.3.3.1c.bin

Usage for bootflash://sup-local
  211411892 bytes used
  167810476 bytes free
  379322368 bytes total

Step 2 If the software image file is not present, download it from an FTP or TFTP server to the active supervisor module bootflash:. You can obtain the software image file from the Cisco.com software download center at the following URL:

http://www.cisco.com/cisco/software/navigator.html


Note If you need more space on the active supervisor module bootflash:, use the delete command to remove unnecessary files and follow Step 3 through Step 6.


switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-kickstart-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin
switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-mz.3.3.1c.bin

Step 3 Ensure that the required space is available on the active supervisor.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin

Usage for bootflash://sup-local
  116188794 bytes used
   68370822 bytes free
  184559616 bytes total

Step 4 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.

switch# del bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin
switch# del bootflash:m9500-sf2ek9-mz.5.0.x.bin

Step 5 Verify that there is enough space available for the standby supervisor.

switch(standby)# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin

Usage for bootflash://sup-local
  116188794 bytes used
   68370822 bytes free
  184559616 bytes total

Step 6 If you need more space on the standby supervisor module bootflash, delete unnecessary files to make space available.

switch(standby)# del bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin
switch(standby)# del bootflash:m9500-sf2ek9-mz.5.0.x.bin

Step 7 Issue the show incompatibility system image-filename command to determine if you need to disable any features not supported by the earlier release.

switch# show incompatibility system bootflash:m9500-sf2ek9-mz.3.3.1c.bin
The following configurations on active are incompatible with the system image
1) Service : port-channel , Capability : CAP_FEATURE_AUTO_CREATED_41_PORT_CHANNEL
Description : auto create enabled ports or auto created port-channels are present
Capability requirement : STRICT 
Disable command : 
1.Disable autocreate on interfaces (no channel-group auto).
2.Convert autocreated port channels to be persistent (port-channel 1 persistent)
...

Step 8 Disable any features that are incompatible with the downgrade system image.

switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# interface fcip 31
switch(config-if)# no channel-group auto
switch(config-if)# end
switch# port-channel 127 persistent
switch# 

Step 9 Save the configuration using the copy running-config startup-config command.

switch# copy running-config startup-config

Step 10 Verify the status of the modules on the switch using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
2    4      10 Gbps FC Module                DS-X9704           ok
3    48     1/2/4 Gbps FC Module             DS-X9148           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
6    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
8    48     1/2/4/8 Gbps 48-Port FC Module   DS-X9248-96        ok
...

Step 11 Verify that the switch is running the required software version by issuing the show version command.

switch# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
  BIOS:      version 1.0.6
  loader:    version N/A
  kickstart: version 5.0(x)
  system:    version 5.0(x)
  BIOS compile time:       06/14/07
  kickstart image file is: bootflash:/m9500-sf2ek9-kickstart-mz.5.0.x.bin.S4
  kickstart compile time:  10/12/2020 25:00:00 [08/26/2008 10:41:37]
  system image file is:    bootflash:/m9500-sf2ek9-mz.5.0.x.bin.S4
  system compile time:     8/22/2008 0:00:00 [08/26/2008 12:15:27]


Hardware
  cisco MDS 9509 (9 Slot) Chassis ("Supervisor/Fabric-2")
  Motorola, 7447A, altivec  with 1032472 kB of memory.
  Processor Board ID JAE1211B6LB

  Device name: 209.165.200.226
  bootflash:    1000440 kB
  slot0:          64065 kB (expansion flash)

Kernel uptime is 0 day(s), 0 hour(s), 20 minute(s), 3 second(s)

Last reset at 128576 usecs after  Wed Aug 27 21:06:24 2008

  Reason: Reset Requested by CLI command reload
  System version: 5.0(x)
  Service:

Step 12 Power down the Generation 3 8-Gbps Fibre Channel switching module.

switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
switch(config)# poweroff module 8
switch(config)# 2008 Aug 27 21:30:59 switch %PLATFORM-2-PFM_MODULE_POWER_OFF: Manual 
power-off of Module 8 from Command Line Interface
2008 Aug 27 21:30:59 switch %PLATFORM-2-MOD_PWRDN: Module 8 powered down (Serial number 
JAE1217FRLR)

Step 13 Verify that the Generation 3 8-Gbps module on the switch is powered down using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
2    4      10 Gbps FC Module                DS-X9704           ok
3    48     1/2/4 Gbps FC Module             DS-X9148           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
6    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
8    48     1/2/4/8 Gbps 48-Port FC Module   DS-X9248-96        powered-dn
...

Step 14 Remove the Generation 3 8-Gbps module.

Step 15 Issue the install all command to downgrade the software.

switch# install all kickstart bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin system 
bootflash:m9500-sf2ek9-mz.3.3.1c.bin

Verifying image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin for boot variable 
"kickstart".
[####################] 100% -- SUCCESS

Verifying image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin for boot variable "system".
[####################] 100% -- SUCCESS

Verifying image type.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Performing Compact Flash and TCAM sanity test.
[####################] 100% -- SUCCESS

Notifying services about system upgrade.
[####################] 100% -- SUCCESS

Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     2       yes  non-disruptive       rolling
     3       yes  non-disruptive       rolling
     5       yes  non-disruptive         reset
     6       yes  non-disruptive         reset

Images will be upgraded according to following table:
Module       Image                  Running-Version(pri:alt)           New-Version  Upg-Required
------  ----------  ----------------------------------------  --------------------  ------------
     2        slc2                                    5.0(x)               3.3(1c)           yes
     2        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     3        slc2                                    5.0(x)               3.3(1c)           yes
     3        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     5      system                                    5.0(x)               3.3(1c)           yes
     5   kickstart                                    5.0(x)               3.3(1c)           yes
     5        bios       v1.0.6(06/14/07):  v1.0.6(06/14/07)      v1.0.6(06/14/07)            no
     6      system                                    5.0(x)               3.3(1c)           yes
     6   kickstart                                    5.0(x)               3.3(1c)           yes
     6        bios       v1.0.6(06/14/07):  v1.0.6(06/14/07)      v1.0.6(06/14/07)            no

Do you want to continue with the installation (y/n)?  [n] y

Install is in progress, please wait.

Syncing image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin to standby.
[####################] 100% -- SUCCESS

Syncing image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin to standby.
[####################] 100% -- SUCCESS

Setting boot variables.
[####################] 100% -- SUCCESS

Performing configuration copy.
[####################] 100% -- SUCCESS

Module 2: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 3: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 5: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 6: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS
2008 Aug 27 21:38:05 switch %PLATFORM-2-MOD_REMOVE: Module 6 removed (Serial number 
JAE1211B6KR)

Module 6: Waiting for module online.
 -- SUCCESS

Notifying services about the switchover.
[####################] 100% -- SUCCESS


"Switching over onto standby".


Note At this point, the previously active supervisor module is rebooting after a nondisruptive switchover has taken place. Refer to the Cisco MDS 9000 Family NX-OS High Availability Configuration Guide.



>> MDS-Bootloader-01.00.06 (Jun 14 2007 - 15:04:07) (MPC7447A)

INFO: Booting off primary flash.
CPU:   MPC7447A v1.1 @ 1411 MHz
DRAM: SPD Checksum ok!
SPD Checksum ok!
-- DIMM1 has 1 banks
-- DIMM2 has 1 banks
ECC Initialization of Bank 0: Done
ECC Initialization of Bank 1: Done
CAS Latency = 2.5 tRP = 3 tRAS = 7 tRCD=3
Total SDRAM memory is 1024 MB
40000000
INFO: SDRAM tests PASSED.
PCI 0 bus mode: Conventional PCI
PCI 1 bus mode: Conventional PCI
L2 Cache Initialization.

Internal SRAM ECC Initialization: Done
IDE:   Bus 0: OK Bus 1: OK
  Device 0: Model: TOSHIBA THNCF1G02DG Firm:  Ser#: TSBC1G0207627A79490A
            Type: Hard Disk
            Capacity: 976.9 MB = 0.9 GB (2000880 x 512)
  Device 3: Model: SanDisk SDCFB-64 Firm: Vdg 1.21 Ser#: 02220224946
            Type: Removable Hard Disk
            Capacity: 61.2 MB = 0.0 GB (125440 x 512)

Booting bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin ...
...............
Automatic boot of image at addr 0x00000000 ...
Starting kernel...
INIT: version 2.78 booting
Checking all filesystems..r.r.r.r. done.
no matching password file entry

delete line `adminbackup:$1$Oip/C5Ci$oOdx7oJSlBCFpNRmQK4na.:13419:0:99999:7:::'? No
pwck: no changes
Loading system software
Uncompressing system image: bootflash:/m9500-sf2ek9-mz.3.3.1c.bin
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCC
INIT: Entering runlevel: 3

Switch Over to new active sup
...
Install has been successful.

User Access Verification
209.165.200.226 login: 2008 Aug 27 21:46:08 209.165.200.226 %PLATFORM-2-MOD_PWRIDPROMFAIL: 
Module 4 failed to power up due to IDPROM read error
2008 Aug 27 21:46:10 209.165.200.226 %PLATFORM-2-MOD_PWRIDPROMFAIL: Module 8 failed to 
power up due to IDPROM read error

User Access Verification

209.165.200.226 login: admin
Password:
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software may be covered under the GNU Public
License or the GNU Lesser General Public License. A copy of
each such license is available at
http://www.gnu.org/licenses/gpl.html and
http://www.gnu.org/licenses/lgpl.html

Step 16 Verify the status of the modules on the switch using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
2    4      10 Gbps FC Module                DS-X9704           ok
3    48     1/2/4 Gbps FC Module             DS-X9148           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
6    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *

Mod  Sw              Hw      World-Wide-Name(s) (WWN)
---  --------------  ------  --------------------------------------------------
2    3.3(1c)         1.0     20:41:00:0b:fd:2c:90:c0 to 20:44:00:0b:fd:2c:90:c0
3    3.3(1c)         0.302   20:81:00:0b:fd:2c:90:c0 to 20:b0:00:0b:fd:2c:90:c0
5    3.3(1c)         1.4     --
6    3.3(1c)         1.6     --
...


Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9509 or MDS 9506 Switch Without an Installed Generation 3 8-Gbps Fibre Channel Switching Module

To downgrade to Cisco MDS SAN-OS Release 3.3(x) from NX-OS Release 5.0(x), on an MDS 9509 or MDS 9506 switch without a Generation 3 8-Gbps Fibre Channel Switching module installed, follow these steps:


Step 1 Verify that the system image files for the downgrade are present on the active supervisor module bootflash:.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   16604160     Jul 01 10:20:07 2008  m9500-sf2ek9-kickstart-mz.3.3.1c.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin
   78718938     Jul 01 10:18:09 2008  m9500-sf2ek9-mz.3.3.1c.bin

Usage for bootflash://sup-local
  211411892 bytes used
  167810476 bytes free
  379322368 bytes total

Step 2 If the software image file is not present, download it from an FTP or TFTP server to the active supervisor module bootflash:. You can obtain the software image file from the Cisco.com software download center at the following URL:

http://www.cisco.com/cisco/software/navigator.html


Note If you need more space on the active supervisor module bootflash:, use the delete command to remove unnecessary files and follow Step 3 through Step 6.


switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-kickstart-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin
switch# copy tftp://tftpserver.cisco.com/MDS/m9500-sf2ek9-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-mz.3.3.1c.bin

Step 3 Ensure that the required space is available on the active supervisor.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin

Usage for bootflash://sup-local
  116188794 bytes used
   68370822 bytes free
  184559616 bytes total

Step 4 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.

switch# del bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin
switch# del bootflash:m9500-sf2ek9-mz.5.0.x.bin

Step 5 Verify that there is enough space available for the standby supervisor.

switch(standby)# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   22001152     Jul 01 10:54:49 2008  m9500-sf2ek9-kickstart-mz.5.0.x.bin
   94175354     Jul 01 10:33:52 2008  m9500-sf2ek9-mz.5.0.x.bin

Usage for bootflash://sup-local
  116188794 bytes used
   68370822 bytes free
  184559616 bytes total

Step 6 If you need more space on the standby supervisor module bootflash, delete unnecessary files to make space available.

switch(standby)# del bootflash:m9500-sf2ek9-kickstart-mz.5.0.x.bin
switch(standby)# del bootflash:m9500-sf2ek9-mz.5.0.x.bin

Step 7 Issue the show incompatibility system image-filename command to determine if you need to disable any features not supported by the earlier release.

switch# show incompatibility system bootflash:m9500-sf2ek9-mz.3.3.1c.bin
The following configurations on active are incompatible with the system image
1) Service : port-channel , Capability : CAP_FEATURE_AUTO_CREATED_41_PORT_CHANNEL
Description : auto create enabled ports or auto created port-channels are present
Capability requirement : STRICT 
Disable command : 
1.Disable autocreate on interfaces (no channel-group auto).
2.Convert autocreated port channels to be persistent (port-channel 1 persistent)
...

Step 8 Disable any features that are incompatible with the downgrade system image.

switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# interface fcip 31
switch(config-if)# no channel-group auto
switch(config-if)# end
switch# port-channel 127 persistent
switch# 

Step 9 Save the configuration using the copy running-config startup-config command.

switch# copy running-config startup-config

Step 10 Verify the status of the modules on the switch using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
2    4      10 Gbps FC Module                DS-X9704           ok
3    48     1/2/4 Gbps FC Module             DS-X9148           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
6    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
...

Step 11 Verify that the switch is running the required software version by issuing the show version command.


switch# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
  BIOS:      version 1.0.6
  loader:    version N/A
  kickstart: version 5.0(x)
  system:    version 5.0(x)
  BIOS compile time:       06/14/07
  kickstart image file is: bootflash:/m9500-sf2ek9-kickstart-mz.5.0.x.bin.S4
  kickstart compile time:  10/12/2020 25:00:00 [08/26/2008 10:41:37]
  system image file is:    bootflash:/m9500-sf2ek9-mz.5.0.x.bin.S4
  system compile time:     8/22/2008 0:00:00 [08/26/2008 12:15:27]


Hardware
  cisco MDS 9509 (9 Slot) Chassis ("Supervisor/Fabric-2")
  Motorola, 7447A, altivec  with 1032472 kB of memory.
  Processor Board ID JAE1211B6LB

  Device name: 209.165.200.226
  bootflash:    1000440 kB
  slot0:          64065 kB (expansion flash)

Kernel uptime is 0 day(s), 0 hour(s), 20 minute(s), 3 second(s)

Last reset at 128576 usecs after  Wed Aug 27 21:06:24 2008

  Reason: Reset Requested by CLI command reload
  System version: 5.0(x)
  Service:

Step 12 Issue the install all command to downgrade the software.

switch# install all kickstart bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin sys 
bootflash:m9500-sf2ek9-mz.3.3.1c.bin

Verifying image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin for boot variable 
"kickstart".
[####################] 100% -- SUCCESS

Verifying image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin for boot variable "system".
[####################] 100% -- SUCCESS

Verifying image type.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Performing Compact Flash and TCAM sanity test.
[####################] 100% -- SUCCESS

Notifying services about system upgrade.
[####################] 100% -- SUCCESS

Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     2       yes  non-disruptive       rolling
     3       yes  non-disruptive       rolling
     5       yes  non-disruptive         reset
     6       yes  non-disruptive         reset

Images will be upgraded according to following table:
Module       Image                  Running-Version(pri:alt)           New-Version  Upg-Required
------  ----------  ----------------------------------------  --------------------  ------------
     2        slc2                                    5.0(x)               3.3(1c)           yes
     2        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     3        slc2                                    5.0(x)               3.3(1c)           yes
     3        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)            no
     5      system                                    5.0(x)               3.3(1c)           yes
     5   kickstart                                    5.0(x)               3.3(1c)           yes
     5        bios       v1.0.6(06/14/07):  v1.0.6(06/14/07)      v1.0.6(06/14/07)            no
     6      system                                    5.0(x)               3.3(1c)           yes
     6   kickstart                                    5.0(x)               3.3(1c)           yes
     6        bios       v1.0.6(06/14/07):  v1.0.6(06/14/07)      v1.0.6(06/14/07)            no

Do you want to continue with the installation (y/n)?  [n] y

Install is in progress, please wait.

Syncing image bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin to standby.
[####################] 100% -- SUCCESS

Syncing image bootflash:/m9500-sf2ek9-mz.3.3.1c.bin to standby.
[####################] 100% -- SUCCESS

Setting boot variables.
[####################] 100% -- SUCCESS

Performing configuration copy.
[####################] 100% -- SUCCESS

Module 2: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 3: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 5: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 6: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS
2008 Aug 27 21:38:05 switch %PLATFORM-2-MOD_REMOVE: Module 6 removed (Serial number 
JAE1211B6KR)

Module 6: Waiting for module online.
 -- SUCCESS

Notifying services about the switchover.
[####################] 100% -- SUCCESS

"Switching over onto standby".


Note At this point, the previously active supervisor module is rebooting after a nondisruptive switchover has taken place. Refer to the Cisco MDS 9000 Family NX-OS High Availability Configuration Guide.



>> MDS-Bootloader-01.00.06 (Jun 14 2007 - 15:04:07) (MPC7447A)

INFO: Booting off primary flash.
CPU:   MPC7447A v1.1 @ 1411 MHz
DRAM: SPD Checksum ok!
SPD Checksum ok!
-- DIMM1 has 1 banks
-- DIMM2 has 1 banks
ECC Initialization of Bank 0: Done
ECC Initialization of Bank 1: Done
CAS Latency = 2.5 tRP = 3 tRAS = 7 tRCD=3
Total SDRAM memory is 1024 MB
40000000
INFO: SDRAM tests PASSED.
PCI 0 bus mode: Conventional PCI
PCI 1 bus mode: Conventional PCI
L2 Cache Initialization.

Internal SRAM ECC Initialization: Done
IDE:   Bus 0: OK Bus 1: OK
  Device 0: Model: TOSHIBA THNCF1G02DG Firm:  Ser#: TSBC1G0207627A79490A
            Type: Hard Disk
            Capacity: 976.9 MB = 0.9 GB (2000880 x 512)
  Device 3: Model: SanDisk SDCFB-64 Firm: Vdg 1.21 Ser#: 02220224946
            Type: Removable Hard Disk
            Capacity: 61.2 MB = 0.0 GB (125440 x 512)

Booting bootflash:/m9500-sf2ek9-kickstart-mz.3.3.1c.bin ...
...............
Automatic boot of image at addr 0x00000000 ...
Starting kernel...
INIT: version 2.78 booting
Checking all filesystems..r.r.r.r. done.
no matching password file entry

delete line `adminbackup:$1$Oip/C5Ci$oOdx7oJSlBCFpNRmQK4na.:13419:0:99999:7:::'? No
pwck: no changes
Loading system software
Uncompressing system image: bootflash:/m9500-sf2ek9-mz.3.3.1c.bin
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCC
INIT: Entering runlevel: 3

Switch Over to new active sup
...
Install has been successful.

User Access Verification
209.165.200.226 login: 2008 Aug 27 21:46:08 209.165.200.226 %PLATFORM-2-MOD_PWRIDPROMFAIL: 
Module 4 failed to power up due to IDPROM read error
2008 Aug 27 21:46:10 209.165.200.226 %PLATFORM-2-MOD_PWRIDPROMFAIL: Module 8 failed to 
power up due to IDPROM read error

User Access Verification

209.165.200.226 login: admin
Password:
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software may be covered under the GNU Public
License or the GNU Lesser General Public License. A copy of
each such license is available at
http://www.gnu.org/licenses/gpl.html and
http://www.gnu.org/licenses/lgpl.html

Step 13 Verify the status of the modules on the switch using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
2    4      10 Gbps FC Module                DS-X9704           ok
3    48     1/2/4 Gbps FC Module             DS-X9148           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby
6    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *

Mod  Sw              Hw      World-Wide-Name(s) (WWN)
---  --------------  ------  --------------------------------------------------
2    3.3(1c)         1.0     20:41:00:0b:fd:2c:90:c0 to 20:44:00:0b:fd:2c:90:c0
3    3.3(1c)         0.302   20:81:00:0b:fd:2c:90:c0 to 20:b0:00:0b:fd:2c:90:c0
5    3.3(1c)         1.4     --
6    3.3(1c)         1.6     --
...

Downgrading from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9222i Switch

To downgrade from NX-OS Release 5.0(x) to SAN-OS Release 3.3(x) on an MDS 9222i switch, follow these steps:


Step 1 Verify that the system image files for the downgrade are present on the active supervisor module bootflash:.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   18939904     Jul 01 10:54:49 2008  m9200-sf2ek9-kickstart-mz.5.0.x.bin
   16858624     Jul 01 10:20:07 2008  m9200-sf2ek9-kickstart-mz.3.3.1c.bin
  101756072     Jul 01 10:33:52 2008  m9200-sf2ek9-mz.5.0.x.bin
   95771404     Jul 01 10:18:09 2008  m9200-sf2ek9-mz.3.3.1c.bin

Usage for bootflash://sup-local
  236338292 bytes used
  142984076 bytes free
  379322368 bytes total

Step 2 If the software image file is not present, download it from an FTP or TFTP server to the active supervisor module bootflash:. You can obtain the software image file from the Cisco.com software download center at the following URL:

http://www.cisco.com/cisco/software/navigator.html


Note If you need more space on the active supervisor module bootflash:, use the delete command to remove unnecessary files and follow Step 3 and Step 4.


switch# copy tftp://tftpserver.cisco.com/MDS/m9200-sf2ek9-kickstart-mz.3.3.1c.bin 
bootflash:m9200-sf2ek9-kickstart-mz.3.3.1c.bin
switch# copy tftp://tftpserver.cisco.com/MDS/m9200-sf2ek9-mz.3.3.1c.bin 
bootflash:m9200-sf2ek9-mz.3.3.1c.bin

Step 3 Ensure that the required space is available on the active supervisor.

switch# dir bootflash:
      12288     Aug 26 19:06:14 2008  lost+found/
   18939904     Jul 01 10:54:49 2008  m9200-sf2ek9-kickstart-mz.5.0.x.bin
  101756072     Jul 01 10:33:52 2008  m9200-sf2ek9-mz.5.0.x.bin

Usage for bootflash://sup-local
  120695976 bytes used
   63863640 bytes free
  184559616 bytes total

Step 4 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.

switch# del bootflash:m9200-sf2ek9-kickstart-mz.5.0.x.bin
switch# del bootflash:m9200-sf2ek9-mz.5.0.x.bin

Step 5 Issue the show incompatibility system image-filename command to determine if you need to disable any features not supported by the earlier release.

switch# show incompatibility system bootflash:m9200-sf2ek9-mz.3.3.1c.bin
The following configurations on active are incompatible with the system image
1) Service : port-channel , Capability : CAP_FEATURE_AUTO_CREATED_41_PORT_CHANNEL
Description : auto create enabled ports or auto created port-channels are present
Capability requirement : STRICT 
Disable command : 
1.Disable autocreate on interfaces (no channel-group auto).
2.Convert autocreated port channels to be persistent (port-channel 1 persistent)
...

Step 6 Disable any features that are incompatible with the downgrade system image.

switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# interface fcip 31
switch(config-if)# no channel-group auto
switch(config-if)# end
switch# port-channel 127 persistent
switch# 

Step 7 Save the configuration using the copy running-config startup-config command.

switch# copy running-config startup-config

Step 8 Issue the install all command to downgrade the software.

switch# install all kickstart bootflash:m9200-s2ek9-kickstart-mz.3.3.1c.bin system 
bootflash:m9200-s2ek9-mz.3.3.1c.bin

Verifying image bootflash:/m9200-s2ek9-kickstart-mz.3.3.1c.bin for boot variable 

"kickstart".
[####################] 100% -- SUCCESS

Verifying image bootflash:/m9200-s2ek9-mz.3.3.1c.bin for boot variable "system".
[####################] 100% -- SUCCESS

Verifying image type.
[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/m9200-s2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "kickstart" version from image 

bootflash:/m9200-s2ek9-kickstart-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/m9200-s2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9200-s2ek9-mz.3.3.1c.bin.
[####################] 100% -- SUCCESS

Performing Compact Flash and TCAM sanity test.
[####################] 100% -- SUCCESS

Notifying services about system upgrade.
[####################] 100% -- SUCCESS

Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     1       yes  non-disruptive         reset
     2       yes  non-disruptive       rolling

Images will be upgraded according to following table:
Module Image                     Running-Version(pri:alt)           New-Version    Upg-Required
------  ----------  ----------------------------------------  -------------------- 
1      system                                    5.0(x)               3.3(1c)      yes
1   kickstart                                    5.0(x)               3.3(1c)      yes
1        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)      no
2        slc2                                    5.0(x)               3.3(1c)      yes
2        bios     v1.0.15(07/16/08):  v1.0.15(07/16/08)     v1.0.12(09/10/07)      no


Do you want to continue with the installation (y/n)?  [n] y

Install is in progress, please wait.

Notifying services about the upgrade.
[####################] 100% -- SUCCESS

Setting boot variables.
[####################] 100% -- SUCCESS

Performing configuration copy.
[####################] 100% -- SUCCESS

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Module 2: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS

Converting startup config.
[####################] 100% -- SUCCESS

Upgrade can no longer be aborted, any failure will result in a disruptive upgrade.

Freeing memory in the file system.
[####################] 100% -- SUCCESS

Loading images into memory.
[####################] 100% -- SUCCESS

Saving external linecard runtime state.
2008 Aug 27 21:18:16 switch %IMAGE_DNLD-SLOT2-2-IMG_DNLD_STARTED:  Module image 

download process. Please wait until completion...
2008 Aug 27 21:18:36 switch %IMAGE_DNLD-SLOT2-2-IMG_DNLD_COMPLETE:  Module image 

download process. Download successful.
[####################] 100% -- SUCCESS

Saving linecard runtime state.
[####################] 100% -- SUCCESS

Saving supervisor runtime state.
[####################] 100% -- SUCCESS

Saving mts state.
[####################] 100% -- SUCCESS

Rebooting the switch to proceed with the upgrade.
Telnet and Ssh will now be disabled.
Starting new kernel
Starting kernel...
INIT: version 2.78 booting
Checking all filesystems..... done.
Loading system software
Uncompressing system image: bootflash:///m9200-s2ek9-mz.3.3.1c.bin
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCC
Uncompressing linecard components
INIT: Entering runlevel: 3
Starting NFS servers: nfsd mountd.

2008 Sep 20 17:45:40 switch %KERN-2-SYSTEM_MSG: Starting kernel... - kernel
2008 Sep 20 17:45:40 switch %KERN-1-SYSTEM_MSG: Entered kgdb_console_init:1960 - kernel

Continuing with installation process, please wait.
The login will be disabled until the installation is completed.
2008 Sep 20 17:46:32 switch %NTP-2-NTP_SYSLOG_NO_RESP_FROM_LC: from LC1 for Timestamp 
Disable
2008 Sep 20 17:46:52 switch %PROC_MGR-2-MESG: Entity : (dnld_image) has exited 
successfully
2008 Sep 20 17:47:00 switch %PLATFORM-2-PS_OK: Power supply 2 ok (Serial number 
QCS104811YP)
2008 Sep 20 17:47:00 switch %PLATFORM-2-PS_FANOK: Fan in Power supply 2 ok
2008 Sep 20 17:47:00 switch %PLATFORM-2-FAN_OK: Fan module ok
2008 Sep 20 17:47:00 switch %PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module A ok
2008 Sep 20 17:47:00 switch %PLATFORM-2-CHASSIS_CLKSRC: Current chassis clock source is 
clock-A

Status for linecard upgrade.
[####################] 100% -- SUCCESS

Status for external linecard upgrade.
[####################] 100% -- SUCCESS

Performing supervisor state verification.
[####################] 100% -- SUCCESS

Install has been successful.

MDS Switch
209.165.200.226 login: admin
Password:
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software may be covered under the GNU Public
License or the GNU Lesser General Public License. A copy of
each such license is available at
http://www.gnu.org/licenses/gpl.html and
http://www.gnu.org/licenses/lgpl.html

Step 9 Issue the show version command to verify the successful downgrade.

switch# show version
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software may be covered under the GNU Public
License or the GNU Lesser General Public License. A copy of
each such license is available at
http://www.gnu.org/licenses/gpl.html and
http://www.gnu.org/licenses/lgpl.html

Software
  BIOS:      version 1.0.15
  kickstart: version 3.3(1c)
  system:    version 3.3(1c)

  BIOS compile time:       07/16/08
  kickstart image file is: bootflash:///m9200-s2ek9-kickstart-mz.3.3.1c.bin
  kickstart compile time:  5/23/2008 19:00:00 [06/20/2008 09:40:24]
  system image file is:    bootflash:///m9200-s2ek9-mz.3.3.1c.bin
  system compile time:     5/23/2008 19:00:00 [06/20/2008 10:28:59]


Hardware
  cisco MDS 9222i ("4x1GE IPS, 18x1/2/4Gbps FC/Sup2")
  Motorola, ppc8548 (e500) with 1032396 kB of memory.
  Processor Board ID JAE1123KANK

  bootflash: 1000440 kB

209.165.200.226   kernel uptime is 0 days 0 hour 5 minute(s) 28 second(s)

  Last reset at 985799 usecs after Wed Aug 27 21:23:53 2008
    Reason: Reset due to upgrade
    System version: 5.0(x)
    Service:

Step 10 Verify the status of the modules on the switch using the show module command.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    22     4x1GE IPS, 18x1/2/4Gbps FC/Sup2  DS-C9222I-K9       active *
2    48     1/2/4 Gbps FC Module             DS-X9148           ok

Mod  Sw              Hw      World-Wide-Name(s) (WWN)
---  --------------  ------  --------------------------------------------------
1    3.3(1c)         0.610   20:01:00:05:30:00:00:00 to 20:12:00:05:30:00:00:00
2    3.3(1c)         0.302   20:41:00:05:30:00:00:00 to 20:70:00:05:30:00:00:00

Mod      Application Image Description       Application Image Version
-------- -----------------------------       -------------------------
1        SSI linecard image (Packaged in SAN-OS) 3.3(1c)


Mod  MAC-Address(es)                         Serial-Num
---  --------------------------------------  ----------
1    00-17-5a-b5-72-80 to 00-17-5a-b5-72-88  JAE1123KANK
2    00-14-a9-74-db-30 to 00-14-a9-74-db-34  JAB093301JZ

* this terminal session
switch#            

Nondisruptive Upgrades on Fabric and Modular Switches

This section describes how to perform nondisruptive upgrades on the following Cisco fabric switches:

Cisco MDS 9124 Multilayer Fabric Switch

Cisco MDS 9134 Multilayer Fabric Switch

Cisco MDS 9148 Multilayer Fabric Switch

Cisco MDS 9222i Multiservice Modular Switch

Cisco Fabric Switch for HP c-Class BladeSystem

Cisco Fabric Switch for IBM BladeCenter

This section includes the following topics:

Preparing for a Nondisruptive Upgrade on Fabric and Modular Switches

Performing a Nondisruptive Upgrade on a Fabric Switch

Displaying the Status of a Nondisruptive Upgrade on a Fabric Switch

Troubleshooting a Nondisruptive Upgrade on a Fabric Switch

Preparing for a Nondisruptive Upgrade on Fabric and Modular Switches

You can upgrade software on the following switches without any disruptions by using the install all command for the system software images:

Cisco MDS 9124 Multilayer Fabric Switch

Cisco MDS 9134 Multlayer Fabric Switch

Cisco MDS 9148 Multilayer Fabric Switch

Cisco MDS 9222i Multiservice Modular Switch

Cisco Fabric Switch for HP c-Class BladeSystem

Cisco Fabric Switch for IBM BladeCenter

When the installation is completed, the supervisor kickstart image, supervisor system image, line card image, and the system BIOS are all updated.

Nondisruptive upgrades on these fabric switches disrupts the control plane for not more than 80 seconds. The software upgrade might be disruptive if the upgrade progresses beyond when it can be stopped gracefully or if a failure occurs.


Note During the upgrade the control plane is down, but the data plane remains up. New devices are not able to log in to the fabric through the control plane, but existing devices do not experience any disruption of traffic through the data plane.


Before attempting to upgrade any software images on the fabric switches, follow these guidelines:

During the upgrade, the fabric must be stable. Do not perform these configuration activies during the upgrade:

Zoning changes

Telnet sessions

Schedule changes

Switch cabling

Addition or removal of physical devices

Configure the FSPF timers to the default value of 20 seconds.

If any CFS commits are pending in the fabric, the upgrade is aborted.

If a zone server merge is in progress, the upgrade is aborted.

If the upgrade is aborted due to a service not being ready for the upgrade, you are prompted to enter the show install all failure-reason command to identify the reason.

If the system has insufficient space to load the new images, then you will be notified through the compatibility table. At this point, you need to either abort the upgrade or proceed with a disruptive upgrade.

Check whether sufficient space is available in the system to load the new images by using the Software Install Wizard. Depending on the available space, you need to either abort the upgrade or proceed with a disruptive upgrade.

Enter the no logging level all command before beginning the upgrade. If you do not enter this command, a failure might occur due to the debug system log messages being printed, which potentially can result in the control plane downtime to exceed 80 seconds.

If VRRP is running on the mgmt0 interface, and the switch being upgraded is the master, then a new master is selected. This situation cannot be avoided because the mgmt0 interface goes down when the control plane goes down.

On the Cisco MDS 18/4-port multiservice module, upgrades of the 4-Gigabit Ethernet ports for the hybrid Supervisor 18/4 line card will be disruptive.

To ensure that you can view the entire upgrade process, you should perform the upgrade by using the console port. By performing the upgrade this way, you can log your session to a file (in case you need it later for troubleshooting). Telnet sessions are lost when the switch is rebooted, so if you want to view the process in its entirety, be sure to use the console port.

The following section shows an example of the failed nondisruptive upgrade due to insuffient resources.

Example 1-1  Failed Nondisruptive Upgrade Due to Insufficient Resources

switch# install all kickstart bootflash:boot-fs9124 system bootflash:isan-164
 
Verifying image bootflash:/boot-fs9124 for boot variable "kickstart".
[####################] 100% -- SUCCESS
 
Verifying image bootflash:/isan-164 for boot variable "system".
[####################] 100% -- SUCCESS
 
Extracting "system" version from image bootflash:/isan-164.
[####################] 100% -- SUCCESS
 
Extracting "kickstart" version from image bootflash:/boot-fs9124.
[####################] 100% -- SUCCESS
 
Extracting "bios" version from image bootflash:/isan-164.
[####################] 100% -- SUCCESS
 
Compatibility check is done:
Module  bootable   Impact         Install-type  Reason
------  --------  --------------  ------------  ------
     1       yes   disruptive     reset  insufficient resources<----Reason for failure
 
 
Images will be upgraded according to following table:
Module  Image       Running-Version(pri:alt)          New-Version  Upg-Required
------  ----------  -----------------------           -----------  -------------------- 
     1      system  3.1(1u)                           3.1(1)           yes
     1   kickstart  3.1(1u)                           3.1(1)           yes
     1        bios  v1.0.0(10/04/06):v1.0.0(10/04/06) v1.0.0(10/04/06) no
 
Do you want to continue with the installation (y/n)?  [n] 

Before performing an upgrade, you may wish to use the show install all impact command to view the effect of updating the system from the running image to another specified image.

switch# show install all impact kickstart bootflash:boot-fs9124 system bootflash:isan-164
 
Verifying image bootflash:/boot-fs9124 for boot variable "kickstart".
[####################] 100% -- SUCCESS
 
Verifying image bootflash:/isan-164 for boot variable "system".
[####################] 100% -- SUCCESS
 
Extracting "system" version from image bootflash:/isan-164.
[####################] 100% -- SUCCESS
 
Extracting "kickstart" version from image bootflash:/boot-fs9124.
[####################] 100% -- SUCCESS
 
Extracting "bios" version from image bootflash:/isan-164.
[####################] 100% -- SUCCESS
 
 
 
Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     1       yes  non-disruptive         reset  
 
 
 
Images will be upgraded according to following table:
Module       Image   Running-Version(pri:alt)           New-Version      Upg-Required
------  ----------   ------------------------           -----------      -------------
     1      system   3.1(1u)                            3.1(1)           yes
     1   kickstart   3.1(1u)                            3.1(1)           yes
     1        bios   v1.0.0(10/04/06): v1.0.0(10/04/06) v1.0.0(10/04/06) no
 
switch# 

Performing a Nondisruptive Upgrade on a Fabric Switch

You can perform a nondisruptive software upgrade on any of the following switches by entering the install all kickstart command using the console port:

Cisco MDS 9124 Multilayer Fabric Switch

Cisco MDS 9134 Multlayer Fabric Switch

Cisco MDS 9148 Multilayer Fabric Switch

Cisco MDS 9222i Multiservice Modular Switch

Cisco Fabric Switch for HP c-Class BladeSystem

Cisco Fabric Switch for IBM BladeCenter


The following section shows an example of the nondisruptive upgrade on a fabric switch.

 
switch# install all kickstart bootflash:boot-fs9124 system bootflash:isan-164u
 
Verifying image bootflash:/boot-fs9124 for boot variable "kickstart".
[####################] 100% -- SUCCESS
 
Verifying image bootflash:/isan-164u for boot variable "system".
[####################] 100% -- SUCCESS
 
Extracting "system" version from image bootflash:/isan-164u.
[####################] 100% -- SUCCESS
 
Extracting "kickstart" version from image bootflash:/boot-fs9124.
[####################] 100% -- SUCCESS
 
Extracting "bios" version from image bootflash:/isan-164u.
[####################] 100% -- SUCCESS
 
Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     1       yes  non-disruptive         reset  
 
Images will be upgraded according to following table:
Module       Image  Running-Version(pri:alt)          New-Version           Upg-Required
------  ----------  --------------------------        --------------------  ------------
     1      system  3.1(1)                            3.1(1u)                yes
     1   kickstart  3.1(1)                            3.1(1u)                yes
     1        bios  v1.0.0(10/04/06): v1.0.0(10/04/06) v1.0.0(10/04/06)       no
 
Do you want to continue with the installation (y/n)?  [n] 
 
Install is in progress, please wait.
 
Notifying services about the upgrade. 
[####################] 100% -- SUCCESS
 
Setting boot variables.
[####################] 100% -- SUCCESS
 
Performing configuration copy.
[####################] 100% -- SUCCESS
 
Converting startup config.
[####################] 100% -- SUCCESS
 
Upgrade can no longer be aborted, any failure will result in a disruptive upgrade. 
<---Note that after this point you cannot abort the upgrade.
 
Freeing memory in the file system.
[####################] 100% -- SUCCESS
 
Loading images into memory.
[####################] 100% -- SUCCESS
 
Saving linecard runtime state.
[####################] 100% -- SUCCESS
 
Saving supervisor runtime state.
[####################] 100% -- SUCCESS
 
Saving mts state.
[####################] 100% -- SUCCESS
 
Rebooting the switch to proceed with the upgrade.
 
 
Continuing with installation process, please wait.
The login will be disabled until the installation is completed.
 
Status for linecard upgrade. 
[####################] 100% -- SUCCESS
 
Performing supervisor state verification. 
[####################] 100% -- SUCCESS
 
Install has been successful.

You can use the Software Install Wizard to perform nondisruptive upgrades on Cisco MDS 9124 Fabric Switches.


Caution We recommend that you enable PortFast on the Ethernet interface of the Catalyst switch to which the management interface of the fabric switch is connected. This step action avoids spanning tree convergence time on the Catalyst switch, and immediately forwards packets from the fabric switch during the nondisruptive upgrade.


Note ASM-SFN and SSI images are not supported for upgrades on the Cisco MDS 9124 Switch, Cisco MDS 9134 Multilayer Fabric Switch, and the Cisco MDS 9148 Multilayer Fabric Switch.


Displaying the Status of a Nondisruptive Upgrade on a Fabric Switch

You can display the status of a nondisruptive upgrade by using the show install all status command. The output displays the status only after the switch has rebooted with the new image. All actions preceding the reboot are not captured in this output because when you enter the install all command using a Telnet session, the session is disconnected when the switch reboots. When you can reconnect to the switch through a Telnet session, the upgrade might already be complete, in which case, the output will display the status of the upgrade.

switch# show install all status 
This is the log of last installation.
 
Continuing with installation process, please wait.
The login will be disabled until the installation is completed.
 
Status for linecard upgrade. 
 -- SUCCESS
 
Performing supervisor state verification. 
 -- SUCCESS
 
Install has been successful.

Troubleshooting a Nondisruptive Upgrade on a Fabric Switch

When a nondisruptive upgrade begins, the system notifies all services that an upgrade is about to start, and finds out whether or not the upgrade can proceed. If a service cannot allow the upgrade to proceed at this time (for example, FSPF timers are not configured to the default value, or a CFS operation is in progress), then the service aborts the upgrade. If this situation occurs, you are prompted to enter the show install all failure-reason command to determine the reason why the upgrade cannot proceed.

...
Do you want to continue with the installation (y/n)?  [n] y
 
Install is in progress, please wait.
 
Notifying services about the upgrade. 
[#                   ]   0% -- FAIL. Return code 0x401E0066 (request timed out).
 
Please issue "show install all failure-reason" to find the cause of the failure.<---system 
prompt to enter the show all failure-reason command.
 
Install has failed. Return code 0x401E0066 (request timed out).
Please identify the cause of the failure, and try 'install all' again.

switch# show install all failure-reason 
Service: "cfs" failed to respond within the given time period.
switch# 

Once the upgrade is already in progress if any failures occur for whatever reason (for example, a save runtime state failure or line card upgrade failure), then the switch is rebooted disruptively because the changes cannot be rolled back. In this case, the upgrade fails, but you are not prompted to enter the show install all failure-reason command; entering it will not yield any useful information.

If you need additional information to determine why an upgrade is unsuccessful, you can obtain the details from the show tech-support command output and from the console output from the installation, if available.

Migrating From Supervisor-1 Modules to Supervisor-2 Modules

As of Cisco MDS SAN-OS Release 3.0(1), the Cisco MDS 9509 and 9506 Directors support both Supervisor-1 and Supervisor-2 modules. For Cisco MDS 9513 Directors, both supervisor modules must be Supervisor-2 modules.

This section includes the following:

Migration Guidelines

Migrating From a Supervisor 1 Module to a Supervisor-2 Module on a Cisco MDS 9509 or MDS 9506 Director


Note The license files will not be copied during the migration process of Supervisor-1 to Supervisor-2 modules. The license files have to be copied manually to the Supervisor-2 modules.


Migration Guidelines

Before performing the migration procedure, consider the following guidelines:

Both Supervisor-1 and Supervisor-2 modules must be running the same SAN-OS release during migration.

Supervisor-1 and Supervisor-2 modules cannot be installed in the same switch, except during migration. Both the active and standby supervisor modules must be of the same type, either Supervisor-1 or Supervisor-2 modules.

If you intend to upgrade your SAN-OS software, you must perform the migration and then perform the upgrade.

To ensure high availability, you must connect the Ethernet port for both active and standby supervisors to the same network or virtual LAN. The active supervisor owns the IP address used by these Ethernet connections. On a switchover, the newly activated supervisor takes over this IP address.

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

The procedure described in this section ensures that your configuration is correctly synchronized after completing the migration.


Caution Migrating your supervisor modules is a disruptive operation. The disruption occurs at the time of the switchover. When the Supervisor-2 module is plugged into the chassis and it comes up as the standby, it is in a warm standby mode (only the ASCII configuration is synchronized; global synchronization is not performed). When the switchover is initiated from the active Supervisor-1 module, the Supervisor-2 module takes over as the active supervisor and applies the ASCII configuration on the switch. At this time, all modules in the chassis are powered down and brought back up as if a fresh boot occurred. The Supervisor-1 module gets powered down.

Migrating From a Supervisor 1 Module to a Supervisor-2 Module on a Cisco MDS 9509 or MDS 9506 Director

To migrate from a Supervisor-1 module to a Supervisor-2 module on a Cisco MDS 9509 or 9506 Director, follow these steps:


Step 1 Ensure that the configured domain ID is the same as the current domain ID for every VSAN on the switch by following these steps:

a. Issue a show vsan command to display all the VSANs on the switch.

switch# show vsan
vsan 1 information
name:VSAN0001  state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down

vsan 2 information
name:VSAN0002  state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down

vsan 10 information
name:VSAN0010  state:active
interoperability mode:default
loadbalancing:src-id/dst-id
operational state:down

vsan 4094:isolated_vsan

b. Display the current and configured domain IDs for a VSAN.

switch# show fcdomain vsan 1
The local switch is the Principal Switch.

Local switch run time information:
State: Stable
Local switch WWN:    20:01:00:05:30:00:35:df
Running fabric name: 20:01:00:05:30:00:35:df
Running priority: 128
Current domain ID: 0x6a(106)

Local switch configuration information:
State: Enabled
FCID persistence: Enabled
Auto-reconfiguration: Disabled
Contiguous-allocation: Disabled
Configured fabric name: 20:01:00:05:30:00:28:df
Configured priority: 128
Configured domain ID: 0x00(0) (preferred)

Principal switch run time information:
Running priority: 128

c. Change the configured domain ID if it differs from the current domain ID.

switch# config terminal
switch(config)# fcdomain domain 106 static vsan 1
switch(config)# exit
switch#

d. Repeat b. and c. for each VSAN on the switch.

Step 2 Save the configuration.

switch# copy running-config startup-config

Step 3 Verify that the switch is running Cisco SAN-OS Release 3.0(1) or later. You must upgrade the switch if necessary.

switch# show version 
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2005, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
  BIOS:      version 1.1.0
  kickstart: version 3.3(1c)
  system:    version 3.3(1c)
...

Step 4 Issue a show module command to determine which Supervisor-1 module is the standby.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    16     1/2 Gbps FC Module               DS-X9016           ok
2    32     Storage Services Module          DS-X9032-SSM       ok
3    8      IP Storage Services Module       DS-X9308-SMIP      ok
4    12     1/2/4 Gbps FC Module             DS-X9112           ok
5    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    ha-standby
6    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    active *
...

Step 5 To set the standby module to manual boot mode, use the system standby manual-boot command.

switch# system standby manual-boot

Step 6 Take the standby Supervisor-1 module out of service.

switch# out-of-service module 5

Step 7 Verify that the standby Supervisor-1 module is powered down.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    16     1/2 Gbps FC Module               DS-X9016           ok
2    32     Storage Services Module          DS-X9032-SSM       ok
3    8      IP Storage Services Module       DS-X9308-SMIP      ok
4    12     1/2/4 Gbps FC Module             DS-X9112           ok
5    0      Supervisor/Fabric-1                                 powered-dn
6    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    active *
...

Step 8 Remove the standby Supervisor-1 module from the chassis. Shut down the management interface on the active Supervisor-1 module. This ensures that the Supervisor-2 can copy the image from TFTP using the same IP address.

switch# config terminal
switch(config)# interface mgmt 0
switch(config-if)# shut
Shutting down this interface will drop all telnet sessions.
Do you wish to continue(y/n)? [n] y
switch(config-if)# end
switch#

Step 9 Install the Supervisor-2 module in the chassis.

Step 10 Establish a console session on the standby Supervisor-2 module console port. For information on establishing a console session, refer to the Cisco MDS hardware installation guide for your switch.

Step 11 If the loader> prompt appears on the standby Supervisor-2 module console session, perform the following steps. Otherwise press Ctrl-C to break the boot sequence.

a. Verify that the Cisco SAN-OS kickstart image is on the Supervisor-2 module bootflash.


Note In rare instances, if the Supervisor-2 module does not include a kickstart image, we recommend that you replace the module with a Supervisor-2 module that has a kickstart image.


loader> dir 
bootflash: 

14458880 m9500-sf2ek9-kickstart-mz.3.0.1.bin
12288    lost+found/ 
48522513 m9500-sf2ek9-mz.3.0.1.bin


Note The kickstart image can be any version of SAN-OS Release 3.x or later, or NX-OS Release 4.x.


b. Boot the kickstart image file from the bootflash.

loader> boot m9500-sf2ek9-kickstart-mz.3.0.1.bin

Booting bootflash:m9500-sf2ek9-kickstart-mz.3.0.1.bin ...
...............
Automatic boot of image at addr 0x00000000 ...
Starting kernel...
INIT: version 2.78 booting
Checking all filesystems...... done.
Loading system software
No system image is specified
INIT: Sending processes the TERM signal
Stopping kernel log daemon: klogd.
Sending all processes the TERM signal... done.
Sending all processes the KILL signal... done.
Entering single-user mode...
INIT: Going single user
INIT: Sending processes the TERM signal
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2007, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software may be covered under the GNU Public
License or the GNU Lesser General Public License. A copy of
each such license is available at
http://www.gnu.org/licenses/gpl.html and
http://www.gnu.org/licenses/lgpl.html
switch(boot)#          

c. Configure the IPv4 address, IPv4 subnet mask, and IPv4 address for the default gateway for the switch.

switch(boot)# config terminal
Enter configuration commands, one per line.  End with CNTL/Z.
switch(boot)(config)# interface mgmt 0
switch(boot)(config-if)# ip address A.B.C.D E.F.G.H
switch(boot)(config-if)# no shut
switch(boot)(config-if)# exit
switch(boot)(config)# ip default-gateway A.B.C.D
switch(boot)(config)# exit
switch(boot)#


Note The IP address can be any valid IP address but we recommend that you configure the Supervisor-2 module with the same IP address as the management interface of the Supervisor-1 module.


d. Download a Cisco SAN-OS system image to the Supervisor-2 module from a TFTP server.

switch(boot)# copy tftp://10.16.10.100/m9500-sf2ek9-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-mz.3.3.1c.bin
Trying to connect to tftp server......


Note Download the Supervisor-2 module image. Ensure that you download the same version as shown in Step 3.


e. Download a kickstart image to the Supervisor-2 module from a TFTP server.

switch(boot)# copy tftp://10.16.10.100/m9500-sf2ek9-kickstart-mz.3.3.1c.bin 
bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin
Trying to connect to tftp server......

f. Reload the Supervisor-2 module on active the Supervisor-1 module console session.

switch# reload module 5

g. Press Ctrl-C to break the boot sequence on the standby Supervisor-2 module console session

switch(boot)#

>> MDS-Bootloader-01.00.10 (Jan  8 2009 - 14:53:42) (MPC7447A), Build: 01.00.10

INFO: Booting off primary flash.
CPU:   MPC7447A v1.1 @ 1411 MHz
DRAM: SPD Checksum ok!
SPD Checksum ok!
-- DIMM1 (unbuffered) has 1 banks
-- DIMM2 (unbuffered) has 1 banks
ECC Initialization of Bank 0: Done
ECC Initialization of Bank 1: Done
CAS Latency = 2.5 tRP = 3 tRAS = 7 tRCD=3
Total SDRAM memory is 1024 MB
40000000
INFO: SDRAM tests PASSED.
done.
PCI 0 bus mode: Conventional PCI
PCI 1 bus mode: Conventional PCI
L2 Cache Initialization.

Internal SRAM ECC Initialization: Done
IDE:   Bus 0: OK
Device 0: Model: SILICONSYSTEMS INC 1GB Firm: 841-023 Ser#: 506VTP69Sn605DC0008
     Type: Hard Disk
     Capacity: 999.1 MB = 0.9 GB (2046240 x 512)
loader> <INTERRUPT>
loader>

h. Verify that the Cisco SAN-OS system image version and the kickstart image version are the same on the standby Supervisor-2 module:

loader> dir

bootflash:

16384       lost+found/
14458880    m9500-sf2ek9-kickstart-mz.3.0.1.bin
16177664    m9500-sf2ek9-kickstart-mz.3.3.1c.bin
69924857    m9500-sf2ek9-mz.3.3.1c.bin
48522513    m9500-sf2ek9-mz.3.0.1.bin

i. Boot the standby Supervisor-2 module using the boot command.

loader> boot m9500-sf2ek9-kickstart-mz.3.3.1c.bin m9500-sf2ek9-mz.3.3.1c.bin

Step 12 Verify that the standby Supervisor-2 module is in the warm standby state by using a show system redundancy status command on the active Supervisor-1 module session.

switch# show system redundancy status
Redundancy mode
---------------
administrative:   HA
   operational:   Warm

This supervisor (sup-2)
-----------------------
Redundancy state:   Active
Supervisor state:   Active
  Internal state:   Active with warm standby

Other supervisor (sup-1)
------------------------
Redundancy state:   Standby
Supervisor state:   Warm standby
  Internal state:   Warm standby


Note In the above switch output, (sup-1) refers to the Supervisor module in slot 5 and (sup-2) refers to the Supervisor module in slot 6. Depending on the slot number from which the original standby Supervisor-1 module was brought out-of-service and removed in Steps 6 and 8, (sup-1) or (sup-2) can be either the Supervisor-1 module or Supervisor-2 module, and vice versa.


Step 13 Enable the management interface.

switch# config terminal
switch(config)# interface mgmt 0
switch(config-if)# no shutdown
switch(config-if)# end
switch#

Step 14 Copy the running configuration to the startup configuration on the active Supervisor-1 module to ensure that any running configuration changes are saved to the startup configuration and that the ASCII configuration is synchronized and current on the warm standby Supervisor-2 module.

switch# copy running-config start-config

Step 15 If your switch has SSMs installed and intelligent services are configured, perform a. through c.. Otherwise, continue to Step 16.

a. Power down all SSMs on the switch.

switch# config terminal
switch(config)# poweroff module 2
switch(config)# exit
switch#


Caution Do not copy the running configuration to the startup configuration after powering down the SSMs. If you do, you will lose the configuration on the SSM interfaces.

b. Verify that the SSMs are powered down.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    16     1/2 Gbps FC Module               DS-X9016           ok
2    32     Storage Services Module                             powered-dn
3    8      IP Storage Services Module       DS-X9308-SMIP      ok
4    12     1/2/4 Gbps FC Module             DS-X9112           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    powered-up
6    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    active *
...

c. Copy the contents of the SSM NVRAM to the standby Supervisor-2 module.

switch# copy ssm-nvram standby-sup


Step 16 Initiate a switchover on the active Supervisor-1 module to power it down and cause the standby Supervisor-2 module to become the active supervisor module.

switch:system switchover
......
CFG-2-ACFG_CONFIGURATION_APPLY_ERROR>>Error encountered while Ascii configuration was 
being applied. Please use "show startup-config log" to view details


Note This message may be shown if a different version (other than that on the Supervisor-1 module) of kickstart and system images are used on the newly installed Supervisor-2 module.


Step 17 Verify that the Supervisor-1 module is powered down.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    16     1/2 Gbps FC Module               DS-X9016           ok
2    32     Storage Services Module          DS-X9032-SSM       powered-dn
3    8      IP Storage Services Module       DS-X9308-SMIP      ok
4    12     1/2/4 Gbps FC Module             DS-X9112           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
6    0      Supervisor/Fabric-1                                 powered-dn
...


Note When the switchover is initiated from the active Supervisor-1 module, the Supervisor-2 module takes over as the active supervisor and applies the ASCII configuration on the switch. At this time, all modules in the chassis are powered down and brought back up as if a fresh boot occurred. The Supervisor-1 module gets powered down.


Step 18 Remove the Supervisor-1 module from the chassis.

Step 19 Verify the current console speed of the active Supervisor-2 module by issuing the show line console command.

switch# show line console
line Console:
    Speed:        9600 baud
    Databits:     8 bits per byte
    Stopbits:     1 bit(s)
    Parity:       none
    Modem In: Disable
    Modem Init-String -
        default : ATE0Q1&D2&C1S0=1\015

Note Make sure that the computer terminal speed or the terminal server speed (that is connected to the newly installed Supervisor-2 module) is the same as the speed on the active Supervisor-2 module. To set up the computer terminal, refer to the "Connecting the Console Port" section in the Cisco MDS 9500 Series Hardware Installation Guide.


Step 20 Configure the boot for the Supervisor-2 module.

switch# config terminal
switch(config)# boot kickstart bootflash:m9500-sf2ek9-kickstart-mz.3.3.1c.bin
switch(config)# boot system bootflash:m9500-sf2ek9-mz.3.3.1c.bin
switch(config)# end
switch#

Step 21 To set the standby module to auto boot mode, use the system no standby manual-boot command.

switch#system no standby manual-boot

Step 22 Install the other Supervisor-2 module in the chassis.


Tip Because the standby autoboot may take up to 5 minutes to start, you may have to wait a few minutes for the standby supervisor module to boot up. To avoid waiting, you can issue the reload module 6 force-dnld command (if the second Supervisor-2 module is in slot 6). The second Supervisor-2 module reloads and boots up immediately without waiting a few minutes for the image synchronization and standby autoboot to take place.


Step 23 Verify that the standby Supervisor-2 module is powered up.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    16     1/2 Gbps FC Module               DS-X9016           ok
2    32     Storage Services Module          DS-X9032-SSM       powered-dn
3    8      IP Storage Services Module       DS-X9308-SMIP      ok
4    12     1/2/4 Gbps FC Module             DS-X9112           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
6    0      Supervisor/Fabric-2                                 powered-up
...

Step 24 Bring up the newly installed Supervisor-2 module using the reload module 6 force-dnld command.

switch# reload module 6 force-dnld

Step 25 Verify that the standby Supervisor-2 module is in the HA standby state.

switch# show system redundancy status
Redundancy mode
---------------
administrative:   HA
   operational:   HA

This supervisor (sup-1)
-----------------------
Redundancy state:   Active
Supervisor state:   Active
  Internal state:   Active with HA standby

Other supervisor (sup-2)
------------------------
Redundancy state:   Standby
Supervisor state:   HA standby
  Internal state:   HA standby

Step 26 If your switch has Storage Services Modules installed and intelligent services are configured, perform Step a and Step b. Otherwise, continue to Step 27.

a. Power up all SSMs on the switch.

switch# config terminal
switch(config)# no poweroff module 2
switch(config)# 

b. Verify that the SSMs have powered up.

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    16     1/2 Gbps FC Module               DS-X9016           ok
2    32     Storage Services Module          DS-X9032-SSM       ok
3    8      IP Storage Services Module       DS-X9308-SMIP      ok
4    12     1/2/4 Gbps FC Module             DS-X9112           ok
5    0      Supervisor/Fabric-2              DS-X9530-SF1-K9    active
6    0      Supervisor/Fabric-2              DS-X9530-SF1-K9    ha-standby *
...

Step 27 Save the configuration.

switch# copy running-config startup-config

Step 28 If the Cisco MDS SAN-OS system image on the supervisor modules is the desired release, enter the install all command.

switch# install all

If you want a different release of the Cisco SAN-OS system image running on the switch, refer to the appropriate sections of this guide.


Migrating from Supervisor-1 to Supervisor-2 Module when SANTap Is Enabled

The SANTap application uses virtual pWWNs that are dependent on the pWWNs and serial numbers of the supervisor modules. When you migrate from Supervisor-1 to Supervisor-2 modules, or change the position of an SSM or MSM-18/4 module in the chassis, SANTap must be reconfigured.

The following procedure describes how to recreate the SANTap configuration with new CVTs, AVTs, and DVTs, and update zoning following a migration from Supervisor-1 to Supervisor-2.

This procedure assumes that you have completed the following preliminary steps:


Step 1 Upgrade kickstart and system on the new switch to match the old switch.

Step 2 Upgrade SSI on the new switch to match the old switch.

Step 3 Load the configuration file from the old switch to the new switch.

Step 4 Log in to RecoverPoint GUI.

Step 5 Detach all volumes from the to-be-replaced SANTap splitter.

Step 6 Remove the splitter from the system.


Once the switch is up and the configuration has been copied over, follow these steps to recreate the SANTap configuration:


Step 1 config

no SSM enable feature SANtap module x

This turns off the SANtap feature and clears the SANtap module x appl-vsan 2 cvt-name cvtname command from the running configuration.

Step 2 SSM enable feature SANtap module x

This enables SANtap for the SSM module specified.

Step 3 Recreate CVT.

config t 
SANtap module x appl-vsan x cvt-name cvtname 

Step 4 View the new CVT details.

do show SANtap module x cvt 
do attach module ssm-module-no 
show isapi virtual-nport database vsan cvt-vsan

to get the CPP and DPP VI port WWNs.

Step 5 Compare the new CVT pWWNs to the old ones in the CVT zone (should be 10). Replace the pWWNs in the CVT zone if necessary. Locate the CVT zone by entering the show zoneset active command.

To remove the old CVT information from the original zone:

config 
zone name cvtzonename vsan x 
no member pwwn xx:xx:xx:xx:xx:xx:xx:xx 

To add new cvt pWWNs (should be 10) from Step 4 to the existing CVT zone, enter the following:

config 
zone name cvtzonename vsan x 
member pwwn new cvt pwwn 


Step 6 Activate the zone set.

config
zoneset activate name backendzonesetname vsan x

Check to see if the CVT zones are active by entering the show zoneset active command.

Step 7 Recreate the DVTs. Locate the DVTs by entering the following command.

show santap module x dvt

To recreate each DVT, enter these commands:

config 
santap module x dvt target-pwwn backend storage pwwn 
target-VSAN backend VSAN dvt-name name for the dvt dvt-vsan Front end VSAN for this DVT 
LUN-size-handling 1 


Step 8 Host-to-target zones are already configured in front end and back end VSANs so the paths should be up now. Rescan the hosts for disks.

Step 9 Rescan SAN on the RPAs. Log in to the RPA1 CLI using the ssh or telnet command and login as the admin user.

rescan_San 

Enter site name, or press Enter for both sites.

rpa1
Rescan SAN volumes? 

A 'full' rescan can take several minutes (default is basic) 
1) full 
2) basic 
3) none 
Select, or press 'ENTER': 1

Rescan SAN splitters? (default is yes) 
1) yes 
2) no 

Select, or press 'ENTER': 1 

If you are rescanning the splitters, enter the splitter name. Also rescan the splitter volume connections. The default is set to all.

Step 10 Rescan the splitters in the RP GUI and add a new splitter.

Step 11 Remove the original AVT zones from the zone set.


Note Generation 3 RPAs only have a single AVT zone instead of separate init and target AVT zones.


config 
zoneset name backendzonesetname vsan x 
no member avt-init zone name 
no member avt-target zone name 
exit 

Activate the zone set to remove the members.

Step 12 On RPA, configure the new AVT zones:

config_SANtap_avt_zones 
Enter SANtap switch username
xxx
Enter SANtap switch password
xxx 
Enter switchname 


Note Do not choose all the switches. Choose only the switch that you want to replace.


Enter the switch name in the form, Cisco - cvt_remote- 258d000f30406ce0.

There are spaces before and after the dash between Cisco and the switch name.

The cvt_remote is a splitter name. You must add the splitter name of the one replaced. Remove the colons when entering the WWN of the splitter CVT.

This step will automatically create the two AVT zones.

Step 13 Verify the AVT zones by entering the following commands:

zone name avt-init zone vsan x 
zone name avt-target zone name vsan x 

Zones may not be named as shown above. You can also check for the AVT zones by entering the show zone vsan 2 command.

Step 14 Add RPA ports from the original AVT zones to the new AVT zones.


Note Generation 3 RPAs only have a single AVT zone instead of separate init and target AVT zones, and should add the RPA ports automatically.


config
zone name avt-init zone vsan x 
member pwwn RPA initiator1 pwwn
member pwwn RPA initiator2 pwwn
exit 
zone name avt-target zone name vsan x 
member pwwn RPA target1 pwwn
member pwwn RPA target2 pwwn

Step 15 Verify the AVT zones again to make sure that the RPA pWWNs are included. (See Step 13.)

Step 16 Add the new AVT zones to the zone set.

config 
zoneset name backendzonesetname vsan x 
member name avt-init zone name 
member name avt-target zone name 
exit 

Step 17 Activate the zone set.

config 
zoneset activate name backendzonesetname vsan x 
exit

Check the active zone set for new zoning. Check to see if the zones are active by entering the show zoneset active command. You should see the new AVT zones and CVT zones with the adjusted information.

Step 18 Back up the configuration.

copy run start 

Attach the volumes to the new splitter through the RecoverPoint GUI.


Related Documentation

The documentation set for NX-OS for the Cisco MDS 9000 Family includes the following documents. To find a document online, access the following web site:

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

The documentation set for Cisco Fabric Manager appears in the Cisco Fabric Manager Release Notes for Release 5.0(1), which is available from the following website:

http://www.cisco.com/en/US/products/ps10495/prod_release_notes_list.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

Cisco MDS NX-OS Release Compatibility Matrix for IBM SAN Volume Controller Software for Cisco MDS 9000

Cisco MDS SAN-OS Release Compatibility Matrix for VERITAS Storage Foundation for Networks Software

Hardware Installation

Cisco MDS 9500 Series Hardware Installation Guide

Cisco MDS 9200 Series Hardware Installation Guide

Cisco MDS 9100 Series Hardware Installation Guide

Cisco MDS 9124 and Cisco MDS 9134 Multilayer Fabric Switch Quick Start Guide

Software Installation and Upgrade

Cisco MDS 9000 NX-OS Release 4.1(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide

Cisco MDS 9000 Family Storage Services Interface Image Install and Upgrade Guide

Cisco MDS 9000 Family Storage Services Module Software Installation and Upgrade Guide

Cisco NX-OS

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

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

Cisco MDS 9000 Family Secure Erase Configuration Guide

Cisco MDS 9000 Family Cookbook for Cisco MDS SAN-OS

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.