Overview for Upgrading Software for Intelligent Storage Services

Step 1 Determine the correct Cisco MDS Software release and SSI boot image version. Refer to the Cisco MDS SAN-OS Release Compatibility Matrix for Storage Service Interface Images, the Cisco MDS SAN-OS Software Release Notes, and, if applicable, the third party support matrix to locate the correct image version for your system. Also, refer to the Cisco MDS SAN-OS Software Release Notes for any other SSI boot image upgrading considerations or procedures for the version to which you want to upgrade.

Step 2 Download the kickstart image and system image for the Cisco MDS SAN-OS Release that is appropriate for your installation from the following URL:

Guidelines for Image File Locations

When upgrading your switch, we recommend that you keep on the active supervisor bootflash the Cisco MDS SAN-OS system and kickstart image files for the release that your switch is running along with the new release to which you want to upgrade. Because of the increasing size of the Cisco MDS SAN-OS system image files, kickstart image files, and other binary files, it is difficult to have more than one release of these files located on the active supervisor module bootflash on the Cisco MDS 9500 Series switches. To accommodate the SSI boot image files and any third party binary files, Cisco MDS SAN-OS Release 2.1(2b), and later, allows you to place these images on the SSM modflash. For details on the available space on bootflash refer to the MDS 9000 Family Hardware Installation Guides.

To allow copies of more that one release of the kickstart and system image files on the supervisor module bootflash, we recommend locating images on all Intelligent Storage Services installations as described in Table 2.

Table 2 Image File Locations

Image File Type

Memory Device Location

Kickstart and system

Supervisor module bootflash

SSI

Modflash on SSM, MSM-18/4, or 9222i

Third party binary

Modflash on SSM, MSM-18/4, or 9222i

Upgrading to Cisco MDS SAN-OS Release 2.1(2x)

This section describes the procedure for upgrading to Cisco MDS SAN-OS Release 2.1(2x) from a release prior to Cisco SAN-OS Release 2.1(2) on an MDS switch with SSMs installed, and it includes the following actions:

•Place the previous kickstart and system images for Cisco SAN-OS and for Cisco SAN-OS Release 2.1(2x) on the active supervisor module bootflash.

•Make sure that the standby supervisor module on Cisco MDS 9500 Series switches has the kickstart and system images for your current Cisco SAN-OS release on the bootflash and has enough free space for the Cisco SAN-OS Release 2.1(2x) kickstart and system images. During the upgrade process, the MDS SAN-OS Release 2.1(2x) kickstart and system images are copied to the standby supervisor module bootflash on Cisco MDS 9500 Series switches.

•Delete any unnecessary files on the standby supervisor module bootflash on Cisco MDS 9500 Series switches.

You can have one of three different types of SSM installations on your switch:

•Only one SSM installed.

•Two or more SSMs installed that are running only one type of application, either Fibre Channel switching or the same Intelligent Storage Service, that uses the same SSI boot image version.

•Two or more SSMs installed that run a mixture of Fibre Channel switching and Intelligent Storage Services and that require different SSI boot image versions.

Note Upgrading to Cisco MDS SAN-OS Release 2.1(2x) from Release 2.1(1b), or earlier, disrupts traffic on the SSMs that are installed on the MDS switch.

Table 3 lists the features supported on the Cisco MDS SAN-OS Release 2.x for the SSM.

Note You must obtain an SSI image that is compatible with the Cisco SAN-OS kickstart image and system image for the MDS switch and SSMs to boot successfully.

Step 4 Obtain the kickstart image and system image for Cisco SAN-OS Release 2.1(2x) and the desired SSI boot image from the Cisco.com software download site if your switch is running an earlier release:

Caution The
install all command disrupts traffic on the SSM when you upgrade from a release prior to Cisco SAN-OS 2.1(2) to Cisco SAN-OS Release 2.1(2) or later.

Note The install all command disrupts traffic on the Cisco MDS 9216 Series switches.

Note Every SSM on the switch that is configured with an SSI boot variable is upgraded to the new SSI boot image that is provided with the install all command, along with the Fiber Channel switching firmware. Any SSM that is not configured with an SSI boot variable is nondisruptively upgraded with the new Cisco SAN-OS kickstart and system firmware. The SSI boot variables are set to the SSI boot image on bootflash.

Step 11 Move the SSI image to the modflash on each SSM in the switch by performing a. through d. for each SSM. On a Cisco MDS 9500 Series switch, if an SSM requires a different SSI boot image version than that referenced in the install all command, you can copy the correct SSI boot image to the modflash of each such SSM. For example, one SSM on the switch might require SSI version 2.1(2l) for SANTap and another SSM might require SSI version 2.1(2i) for EMC Invista).

a. Copy the desired SSI boot image to the SSM modflash.

The following example copies the same SSI boot image as referenced in the install all command:

Caution The SSI boot variable must reference the correct SSI boot image, otherwise the SSM fails to initialize. If you do not correctly set the SSI boot variable, the SSM remains in the power-down state after attempting to initialize three times.

c. Verify the boot variables to verify the location of the boot images for each SSM.

For Cisco MDS 9500 Series switches:

switch# show boot

sup-1

kickstart variable = bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin

system variable = bootflash:/m9500-sf1ek9-mz.2.1.2b.bin

sup-2

kickstart variable = bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin

system variable = bootflash:/m9500-sf1ek9-mz.2.1.2b.bin

Module 2

ssi variable = modflash://2-1/m9000-ek9-ssi-mz.2.1.2i.bin

Module 3

ssi variable = modflash://3-1/m9000-ek9-ssi-mz.2.1.2l.bin

For Cisco MDS 9200 Series switches:

switch# show boot

kickstart variable = bootflash:/m9200-sf1ek9-kickstart-mz.2.1.2b.bin

system variable = bootflash:/m9200-sf1ek9-mz.2.1.2b.bin

Module 2

ssi variable = modflash://2-1/m9000-ek9-ssi-mz.2.1.2i.bin

d. Reload the SSM with the different SSI image if you are upgrading on a Cisco MDS 9500 Series switch.

Upgrading to Cisco MDS SAN-OS Release 3.0(1) and Later

This section describes the procedure to upgrade your MDS switch from Cisco MDS SAN-OS Release 2.1(2b), or later, to Release 3.0(1), or later, and it includes the following actions:

•Place the kickstart and system images for both Cisco SAN-OS Release 2.1(2b), or later, and Release 3.0(1), or later, on the active supervisor module bootflash.

•Make sure that the standby supervisor module on Cisco MDS 9500 Series switches has at least the kickstart and system images for Cisco SAN-OS Release 2.1(2b), or later, on the bootflash and has enough free space for the Cisco SAN-OS Release 3.0(1), or later, kickstart and system images.

•Delete any unnecessary files on the standby supervisor module bootflash on a Cisco MDS 9500 Series switches.

Note You must upgrade to Cisco SAN-OS Release 2.1(2b), or later, before upgrading to Cisco SAN-OS Release 3.0(1).

Note During the process of upgrading, the Cisco SAN-OS Release 3.0(1) or later, kickstart image and system images are copied to the standby supervisor module bootflash on Cisco MDS 9500 Series switches.

Note You must obtain an SSI image that is compatible with the Cisco SAN-OS kickstart image and system image for the MDS switch and SSMs to boot successfully.

Step 2 Obtain the kickstart image and system image for Cisco SAN-OS Release 3.0(1), or later, and the appropriate SSI boot image from the Cisco.com software download site. This site also shows the size of the image files in byte:

b. Change the configuration for the first interface of the port groups when the admin mode is auto. These are the interfaces 1, 5, 9, 13, 17, 21, 25, and 29. Do not leave the port mode for these interfaces set to auto.

–If the current operating port mode is F or FL, set the admin mode to Fx.

switch# config t

switch(config)# interface fc 2/1

switch(config-if)# switchport mode fx

switch(config-if)# exit

switch(config)#

–If the current operating port mode is E or TE, set the admin mode to E .

switch# config t

switch(config)# interface fc 2/5

switch(config-if)# switchport mode e

switch(config-if)# exit

switch(config)#

c. Change the configuration for the remaining three ports in each port group (2-4, 6-8, 10-12, 14-16, 18-20, 22-24, 26-28, and 30-32). Do not leave the port mode for these interfaces set to autoor E.

–If the admin mode of these ports is auto or E and the first interface in the port group does not have admin mode of E, change the admin port mode to Fx.

switch# config t

switch(config)# interface fc 2/2

switch(config-if)# switchport mode fx

switch(config-if)# exit

switch(config)#

–If the first interface in the port group has admin mode E or is operating in E port mode, change the admin state of remaining ports to shutdown .

Note Only the first port in a port group is available for traffic in E port mode. Shutting down the other three interfaces in the port group disrupts the traffic on those interfaces.

Caution The
install all command with the
ssi option can be disruptive for SSM traffic, as described in
Table 1.

Note The install all command disrupts traffic on the Cisco MDS 9216 Series switches.

Note The install all command automatically copies the SSI boot image referenced in the ssi option to the modflash of SSMs that already have SSI images installed and SSI boot variables set. The SSI boot variables are updated to point to the correct SSI boot image.

Step 12 Perform a. through b. if an SSM on a Cisco MDS 9500 Series switch requires a different SSI boot image version than the one referenced in the install all command. You can copy the correct SSI boot image to the modflash of each such SSM and install it for that SSM. For example, one SSM on the switch might require one SSI boot image version for SANTap while another SSM on the switch requires a different SSI boot image version for EMC Invista.

a. Copy the desired SSI boot image to the SSM modflash.

Note Before copying the SSI boot image to the SSM modflash, verify that the SSM is online using the show module command and that the modflash is available using the dir modflash://slot-1/ command.

switch# copy ftp://ftpserver.cisco.com/MDS/m9000-ek9-ssi-mz.3.0.2.bin

modflash://3-1/m9000-ek9-ssi-mz.3.0.2.bin

b. Install the SSI boot image.

The following example installs the SSI boot image for Cisco SAN-OS Release 3.0(1):

Caution The SSI boot variable must reference the correct SSI boot image, otherwise the SSM fails to initialize. If you do not correctly set the SSI boot variable, the SSM remains in the power-down state after attempting to initialize three times.

The following example installs the SSI boot image for Cisco SAN-OS Release 3.0(2) and later:

•To upgrade to Cisco MDS NX-OS SSI image Release 4.1(1b), an SSM must be running SAN-OS SSI image Release 3.3(1a) or 3.3(1c), or should not be running on an SSI image.

Note As of Cisco MDS NX-OS Release 4.1(1b), when there are multiple SSM or MSM-18/4 modules in the same chassis, you can set the amount of time to delay between SSM or MSM-18/4 modules in a rolling SSI upgrade. For more information, refer to the Cisco MDS 9000 Family Configuration Guides for Release 4.x.

•If the module was running an SSI image, clear the SSI bootvar on the MSM-18/4, and MDS 9222i module 1 modules before you upgrade to Cisco MDS NX-OS Release 4.1(1b) or later.

•If you have an SSM module running on an SSI image, then perform the following operations to upgrade the MDS NX-OS and the SSI image on the SSM module:

switch# install all system bootflash:m9500-sf1ek9-mz.4.1.1a.bin kickstart

Caution The
install all command with the
ssi option will upgrade the SSI image on an SSM not running the specified SSI image.
The
install all command with the
ssi option will not upgrade the SSI image on an MSM-18/4 for a system running on MDS SAN-OS release earlier than 3.3(1c).
The
install all command does not disrupt traffic on the Cisco MDS 9222i switches.

•If you do not have an SSM module running SSI image, or have only MSM-18/4 modules, or have an SSM running SAN-OS Release 3.3(1c) compatible SSI image and you do not want to upgrade the SSI image but upgrade only the NX-OS image, then perform the following operations:

switch# install all system bootflash:m9500-sf1ek9-mz.4.1.1a.bin kickstart

bootflash:m9500-sf1ek9-kickstart-mz.4.1.1a.bin

•To install an SSI image on an SSM, MSM-18/4, or MDS 9222i module 1 on a switch running MDS NX-OS Release 4.1(1b), perform the following operations:

–Use the install ssi command to install a new MDS NX-OS Release 4.1(1b) compatible SSI image on an SSM module.

switch# install ssi bootflash:m9000-ek9-ssi-mz.4.1.1a.bin module 2

–Use the install all command with the ssi option to install a new MDS NX-OS Release 4.1(1b) compatible SSI image on an SSM, MSM-18/4, and MDS 9222i module 1 modules.

switch# install all ssi bootflash:m9000-ek9-ssi-mz.4.1.1a.bin

Guidelines for SSM, MSM-18/4, and MDS 9222i Module 1

The NX-OS Release 4.1(1b) and later releases support SSI bootvar for MDS-18/4 and MDS 9222i module 1 with some restrictions. Before you install the SSI image on MDS-18/4 and MDS 9222i module 1, check and modify the ssi bootvar configuration and use the install all or the install ssi command based on these guidelines.

In a NX-OS release lower than 4.1(1b), the SSI bootvar was not supported for the MSM-18/4 and MDS 9222i module 1 and the installer would not update the SSI bootvars for these modules while upgrading to 4.1(1b). Before upgrading to NX-OS Release 4.1(1b), be sure that the SSI bootvar is not set for MSM-18/4 or MDS 9222i module 1 modules.

•In a SAN-OS Release earlier than 4.1(1b), the SSI bootvar is not supported for MSM-18/4 modules. The installer will not update the SSI bootvar for these modules while upgrading to NX-OS Release 4.1(1b) from a lower version. If the SSI bootvar is set for these modules pointing to an image not compatible with NX-OS Release 4.1(1b), and the upgrade to NX-OS Release 4.1(1b) is done using the install all command, the module will be brought into power down state.

Caution The
boot ssi image-uri command will set the SSI bootvar for all the modules in the switch. Though the SSI bootvar was not supported for MSM-18/4 in a SAN-OS release earlier than 4.1(1b), the bootvar might have been set.

•While running a SAN-OS release earlier than 4.1(1b), if there is no SSI bootvar set for the SSM, MSM-18/4, and MDS 9222i module 1, and the install all command without ssi option is used, then the installer does not update the SSI bootvar and does a rolling upgrade of the modules: SSM is upgraded in nondisruptive mode, MSM-18/4 and MDS 9222i module 1 18FC ports are upgraded in a nondisruptive mode, but the 4-Gigabit Ethernet ports are upgraded in disruptive mode.

•While upgrading the SSI image on MDS 9222i or any MDS switch with MSM-18/4 module running NX-OS Release 4.1(1b) by using the install all command with the ssi option, the installer will set the SSI bootvar for MDS 9222i module 1 and MSM-18/4. Unless there is a requirement for the MSM-18/4 or MDS 9222i have a new SSI image, we recommend that you do not use the ssi option in the install all command.

•While running NX-OS Release 4.1(1b), if the SSI boot variable was configured to an SSI image not compatible with NX-OS Release 4.1(1b) for the SSM, MSM-18/4, or 9222i module 1 modules, and then the module is reloaded, or if the bootvar set SSI image does not exist, the SSM, MSM-18/4, or 9222i module will be brought online without the SSI image.

•While running NX-OS Release 4.1(1b), if there is no SSI bootvar set for SSM, MSM-18/4, and MDS 9222i module 1, and the install all ssi command is used, the installer sets the SSI bootvar for MSM-18/4 and MDS 9222i module 1, and does rolling upgrade of the modules: SSM is upgraded in nondisruptive mode, MSM-18/4 and 9222i 18FC ports are upgraded in nondisruptive mode but the 4-Gigabit Ethernet ports are upgraded in disruptive mode.

•While running NX-OS Release 4.1(1b), if the SSI bootvar is set for the SSM, MSM-18/4, and MDS 9222i module 1, and the install all command without ssi option is used, then the installer upgrades the kickstart and system images and does a rolling upgrade of the modules: SSM is upgraded in disruptive mode, MSM-18/4 and MDS 9222i module 1 18FC ports are upgraded in nondisruptive mode, and the 4-Gigabit Ethernet ports are upgraded in disruptive mode. SSM, MSM-18/4, and MDS 9222i module 1 load the SSI images newly set in the SSI bootvars. If the ssi option was not used, then the modules load the SSI images previously set in the SSI bootvars. The SSI bootvar image has to be compatible with the supervisor; if not, the modules will go into power down state.

•While running NX-OS Release 4.1(1b), if the SSI bootvar is set for SSM but not for MSM-18/4 and MDS 9222i module 1, and the install all ssi command is used, then the installer sets the SSI bootvar for MSM-18/4 and MDS 9222i module 1, and does a rolling upgrade of the modules: SSM is upgraded in disruptive mode, MSM-18/4 and MDS 9222i module 1 18FC ports are upgraded in nondisruptive mode, and the 4-Gigabit Ethernet ports are upgraded in disruptive mode. SSM, MSM-18/4, and 9222i load the SSI images newly set in the SSI bootvar. The SSI bootvar image has to be compatible with the supervisor.

•While running NX-OS Release 4.1(1b) on a chassis with multiple SSM and MSM-18/4 modules, to install different SSI images on each, use the install ssi command separately for each module. Use the install ssi command to install different SSI images only on the SSM modules.

•While downgrading from NX-OS Release 4.1(1b) to any release earlier than 4.1(1b), if the SSI bootvar is set for MSM-18/4 and MDS 9222i module 1, it will be removed if you use the install all command with the SSI image because it is not supported in the releases earlier than NX-OS Release 4.1(1b).

Note As of Cisco MDS NX-OS Release 4.1(1b), when there are multiple SSM or MSM-18/4 modules in the same chassis, you can set the amount of time to delay between SSM or MSM-18/4 modules in a rolling SSI upgrade. For more information, refer to the Cisco MDS 9000 Family Configuration Guides for Release 4.x.

•If you have an SSM, MSM-18/4, or MDS 9222i module 1 running an SSI image, then perform the following operations to upgrade the MDS NX-OS software and the SSI image on all modules in the chassis:

switch# install all system bootflash:m9500-sf1ek9-mz.4.1.3a.bin kickstart

•To install an SSI image on an SSM, MSM-18/4, or MDS 9222i module 1 on a switch running MDS NX-OS Release 4.1(3a), use the appropriate command for the module. See Table 4 for the commands that you can use on each module.

–Use the install ssi command to install a new MDS NX-OS Release 4.1(3a) compatible SSI image on an SSM module.

switch# install ssi bootflash:m9000-ek9-ssi-mz.4.1.3a.bin module 2

–Use the install all command with the ssioption to install a new MDS NX-OS Release 4.1(3a) compatible SSI image on the SSM and MSM-18/4 modules in a switch.

switch# install all ssi bootflash:m9000-ek9-ssi-mz.4.1.3a.bin

–Use the install module ssi command to install a new MDS NX-OS Release 4.1(3a) compatible SSI image on a SSM or MSM-18/4 module.

switch# install module ssi bootflash:m9000-ek9-ssi-mz.4.1.3a.bin

Note The install module ssi command is not supported on the MDS 9222i module 1.

Table 4 lists the commands that you should use to upgrade an SSI image from Cisco MDS NX-OS 4.1(1b) to MDS NX-OS 4.1(3a), and the modules that support these commands.

1As Table 4 shows, you cannot upgrade an MDS 9222i module 1separately. You must upgrade it as a part of entire switch upgrade, using the install all system image-name kickstart image-name ssi image-name command, which will reload the switch. Traffic on Fibre Channel ports is not disrupted during this upgrade procedure.

1Table 5 lists the impact of the SSI upgrade procedure. The procedure is disruptive or nondisruptive depending on the module being upgraded and if an SSI image was previously installed.

Note You must obtain an SSI image that is compatible with the Cisco SAN-OS kickstart image and system image for the MDS switch and SSMs to boot successfully.

Step 2 Obtain the kickstart image and system image for Cisco SAN-OS to which you want to downgrade and the appropriate SSI boot image from the Cisco.com software download site. This site also shows the size of the image files in bytes:

Step 9 Issue the show incompatibility systemimage-filename command to determine if you need to disable any features not supported by the older release. Disable any features that are incompatible with the downgrade system image.

Caution The
install all command with the
ssi option can be disruptive for SSM traffic, as described in
Table 1.

Note The install all command disrupts traffic on the Cisco MDS 9216 Series switches.

Note The install all command automatically copies the SSI boot image referenced in the ssi option to the modflash of SSMs that already have SSI images installed and SSI boot variables set. The SSI boot variables are updated to point to the correct SSI boot image.

Step 12 Perform a. through b. if an SSM on a Cisco MDS 9500 Series switch requires a different SSI boot image version than the one referenced in the install all command. You can copy the correct SSI boot image to the modflash of each such SSM and install it for that SSM. For example, one SSM on the switch might require one SSI boot image version for SANTap while another SSM on the switch requires a different SSI boot image version for EMC Invista.

a. Copy the desired SSI boot image to the SSM modflash.

Note Before copying the SSI boot image to the SSM modflash, verify that the SSM is online using the show module command and that the modflash is available using the dir modflash://slot-1/ command.

Caution The SSI boot variable must reference the correct SSI boot image, otherwise the SSM fails to initialize. If you do not correctly set the SSI boot variable, the SSM remains in the power-down state after attempting to initialize three times.

Step 13 Verify that the boot variables are configured correctly. These variables are needed if a system reboot is necessary.

For Cisco MDS 9500 Series switches downgraded to Cisco SAN-OS 3.0(1):

switch# show boot

sup-1

kickstart variable = bootflash:/m9500-sf1ek9-kickstart-mz.3.0.1.bin

system variable = bootflash:/m9500-sf1ek9-mz.3.0.1.bin

sup-2

kickstart variable = bootflash:/m9500-sf1ek9-kickstart-mz.3.0.1.bin

system variable = bootflash:/m9500-sf1ek9-mz.3.0.1.bin

Module 2

ssi variable = modflash://2-1/m9000-ek9-ssi-mz.3.0.1.bin

Module 3

ssi variable = modflash://3-1/m9000-ek9-ssi-mz.3.0.2.bin

For Cisco MDS 9200 Series switches downgraded to Cisco SAN-OS 3.0(1):

switch# show boot

kickstart variable = bootflash:/m9200-sf1ek9-kickstart-mz.3.0.1.bin

system variable = bootflash:/m9200-sf1ek9-mz.3.0.1.bin

Module 2

ssi variable = modflash://2-1/m9000-ek9-ssi-mz.3.0.1.bin

Caution Make sure that the SSI boot variable is pointing to the correct location. If the variable points to an incorrect location for the SSI image, the SSM does not boot correctly.

Step 14 Save the configuration.

switch# copy running-config startup-config

Moving SSI Boot Image Files to SSM Modflash

For installation that are running Cisco MDS SAN-OS Release 2.1(2b) and later, we recommend that you locate the SSI boot image files on the SSM modflash. In most installations, all of the MDS SAN-OS image files are located on the supervisor module bootflash (both active and standby). This section describes how to move the appropriate files to the new location.

To move the SSI boot image files from bootflash to SSM modflash, follow these steps:

Caution The SSI boot variable must reference the correct SSI boot image, otherwise the SSM fails to initialize. If you do not correctly set the SSI boot variable, the SSM remains in the power-down state after attempting to initialize three times.

d. Verify the updated configuration of the boot variables.

For Cisco MDS 9500 Series switches:

switch# show boot

sup-1

kickstart variable = bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin

system variable = bootflash:/m9500-sf1ek9-mz.2.1.2b.bin

sup-2

kickstart variable = bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin

system variable = bootflash:/m9500-sf1ek9-mz.2.1.2b.bin

Module 2

ssi variable = modflash://2-1/m9000-ek9-ssi-mz.2.1.2i.bin

For Cisco MDS 9200 Series switches:

switch# show boot

kickstart variable = bootflash:/m9200-sf1ek9-kickstart-mz.2.1.2b.bin

system variable = bootflash:/m9200-sf1ek9-mz.2.1.2b.bin

Module 2

ssi variable = modflash://2-1/m9000-ek9-ssi-mz.2.1.2i.bin

Step 3 Save the configuration.

switch# copy running-config startup-config

Step 4 Delete the files copied to the SSM modflash from the active supervisor module bootflash and standby supervisor module bootflash (on Cisco MDS 9500 Series switches). The SSI boot image files are no longer needed on those devices.

Troubleshooting and 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:

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.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0903R)