HP Cisco MDS 8/24c Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Rel - Page 15

Upgrading Your Cisco MDS NX-OS Software Image, Upgrading Guidelines Specific to NX-OS Release 5.2(2)

Page 15 highlights

Upgrading Your Cisco MDS NX-OS Software Image Send documentation comments to [email protected] Upgrading Your Cisco MDS NX-OS Software Image This section lists the guidelines recommended for upgrading your Cisco MDS NX-OS software image and includes the following topics: • Upgrading Guidelines Specific to NX-OS Release 5.2(2), page 15 • General Upgrading Guidelines, page 16 • Nondisruptive Upgrade Paths, page 17 • FICON Supported Releases and Upgrade Paths, page 18 Note Before you begin the upgrade process, review the list of chassis and modules that Cisco MDS NX-OS Release 5.2(2) supports. See the "MDS 9000 Chassis and Module Support" section on page 8. For detailed instructions for performing a software upgrade using Cisco DCNM, see the Cisco DCNM Release Notes, Release 5.2, which is available from the following website: http://www.cisco.com/en/US/products/ps10495/prod_release_notes_list.html Upgrading Guidelines Specific to NX-OS Release 5.2(2) Follow these guidelines when upgrading to Cisco MDS NX-OS Release 5.2(2): • Follow the upgrade path to NX-OS Release 5.2(2) that is specified in Table 11. • Upgrade to NX-OS Release 5.2(x) before you install any Generation 4 module in an MDS 9500 Series switch. Generation 4 modules include the FCoE module and the 32-port and 48-port 8-Gbps Advanced Fibre Channel modules. NX-OS Release 5.2(x) is needed for the switch to recognize the new hardware. • Perform a full switch reload on an MDS 9509 or MDS 9506 switch after you install NX-OS Release 5.2(1) and install any Generation 4 module, including the FCoE module. The switch reload is required for the new hardware to come up. Once you perform the switch reload, the fabric mode changes to support the Generation 4 hardware. Because of the changed fabric mode, you cannot subsequently perform a nondisruptive software downgrade from NX-OS Release 5.2(1). For additional information, see the "Downgrading Guidelines Specific to NX-OS Release 5.2(2)" section on page 19 • Ensure that you have a Supervisor-2A module (DS-X9530-SF2A-K9) installed in a MDS 9500 Series switch if you plan to use the Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) (DS-X9708-K9). • We recommend that you delete any SPAN configuration, Fibre Channel tunnel, or tunnel-ID map configuration from your switch before you start the upgrade to NX-OS Release 5.2(1). You can save the SPAN destination and SPAN target configuration and then reconfigure the SPAN session following the upgrade. All SPAN destination and SPAN target ports are reinitialized after the upgrade. To gather information about SPAN sessions and delete them, use the following commands in this order: - show incompatibility systems bootflash:image_name to display any incompatible configurations - show span session to check the current configuration for a SPAN session - no span session session-number to delete a SPAN session OL-25090-02 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(2) 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44

Send documentation comments to [email protected]
15
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(2)
OL-25090-02
Upgrading Your Cisco MDS NX-OS Software Image
Upgrading Your Cisco MDS NX-OS Software Image
This section lists the guidelines recommended for upgrading your Cisco MDS NX-OS software image
and includes the following topics:
Upgrading Guidelines Specific to NX-OS Release 5.2(2), page 15
General Upgrading Guidelines, page 16
Nondisruptive Upgrade Paths, page 17
FICON Supported Releases and Upgrade Paths, page 18
Note
Before you begin the upgrade process, review the list of chassis and modules that Cisco MDS NX-OS
Release 5.2(2) supports. See the
“MDS 9000 Chassis and Module Support” section on page 8
.
For detailed instructions for performing a software upgrade using Cisco DCNM, see the
Cisco DCNM
Release Notes, Release 5.2
, which is available from the following website:
Upgrading Guidelines Specific to NX-OS Release 5.2(2)
Follow these guidelines when upgrading to Cisco MDS NX-OS Release 5.2(2):
Follow the upgrade path to NX-OS Release 5.2(2) that is specified in
Table 11
.
Upgrade to NX-OS Release 5.2(x) before you install any Generation 4 module in an MDS 9500
Series switch. Generation 4 modules include the FCoE module and the 32-port and 48-port 8-Gbps
Advanced Fibre Channel modules. NX-OS Release 5.2(x) is needed for the switch to recognize the
new hardware.
Perform a full switch reload on an MDS 9509 or MDS 9506 switch after you install NX-OS Release
5.2(1) and install any Generation 4 module, including the FCoE module. The switch reload is
required for the new hardware to come up. Once you perform the switch reload, the fabric mode
changes to support the Generation 4 hardware. Because of the changed fabric mode, you cannot
subsequently perform a nondisruptive software downgrade from NX-OS Release 5.2(1). For
additional information, see the
“Downgrading Guidelines Specific to NX-OS Release 5.2(2)”
section on page 19
Ensure that you have a Supervisor-2A module (DS-X9530-SF2A-K9) installed in a MDS 9500
Series switch if you plan to use the Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet
(FCoE) (DS-X9708-K9).
We recommend that you delete any SPAN configuration, Fibre Channel tunnel, or tunnel-ID map
configuration from your switch before you start the upgrade to NX-OS Release 5.2(1). You can save
the SPAN destination and SPAN target configuration and then reconfigure the SPAN session
following the upgrade. All SPAN destination and SPAN target ports are reinitialized after the
upgrade. To gather information about SPAN sessions and delete them, use the following commands
in this order:
show incompatibility systems bootflash:
image_name
to display any incompatible
configurations
show span session
to check the current configuration for a SPAN session
no span session
session-number
to delete a SPAN session