HP Cisco MDS 9124 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Rel - Page 13

Upgrading with IVR Enabled, Current Release with, FICON Enabled, Upgrade Path

Page 13 highlights

Upgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] Table 5 FICON Nondisruptive Upgrade Path to SAN-OS 3.1(2a) Current Release with FICON Enabled SAN-OS 3.0(2) SAN-OS 2.0(2b) SAN-OS 1.x Upgrade Path You can nondisruptively upgrade directly to SAN-OS Release 3.1(2a). Use the interface shutdown command to administratively shut any Fibre Channel ports on Generation 1 modules that are in an operationally down state before nondisruptively upgrading from SAN-OS Release 2.0(2b) to SAN-OS Release 3.0(2), and then upgrade to Release 3.1(2a). An operationally down state includes Link failure or not-connected, SFP not present, or Error Disabled status in the output of a show interface command. When an interface is administratively shut it will then show as Administratively down. Interfaces that are currently up or trunking do not need to be shut down. Upgrade to SAN-OS Release 3.0(2). Use the interface shutdown command to shut all the ports operationally down and administratively up on all the Generation 1 modules before nondisruptively upgrading to Release 2.0(2b) and then upgrade to 1.3(4a). Upgrading with IVR Enabled An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is enabled might be disruptive. Some possible scenarios include the following: • FCIP connection flapping during the upgrade process resulting in fabric segmentation or merge. • ISL flap results in fabric segmentation or merge because of hardware issues or a software bug. • ISL port becomes part of PCP results in fabric segmentation or merge because of a port flap. If this problem occurs, syslogs indicate a failure and the flapped ISL could remain in a down state because of a domain overlap. This issue was resolved in Cisco SAN-OS Release 2.1(2b); therefore, you must upgrade to Release 2.1(2b) before upgrading to Release 3.1(2a). An upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.1(2b) when IVR is enabled requires that you follow the procedure below, and then follow the upgrade guidelines listed in the "Upgrading Your Version of Cisco Fabric Manager" section on page 10. If you have VSANs in interop mode 2 or 3, you must issue an IVR refresh for those VSANs. To upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.1(2b) for all other VSANs with IVR enabled, follow these steps: Step 1 Configure static domains for all switches in all VSANs where IVR is enabled. Configure the static domain the same as the running domain so that there is no change in domain IDs. Make sure that all domains are unique across all of the IVR VSANs. We recommend this step as a best practice for IVR-non-NAT mode. Issue the fcdomain domain id static vsan vsan id command to configure the static domains. Note Complete Step 1 for all switches before moving to Step 2. OL-12208-03 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(2a) 13

  • 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

Send documentation comments to [email protected]
13
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(2a)
OL-12208-03
Upgrading Your Cisco MDS SAN-OS Software Image
Upgrading with IVR Enabled
An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade
from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is enabled might be disruptive.
Some possible scenarios include the following:
FCIP connection flapping during the upgrade process resulting in fabric segmentation or merge.
ISL flap results in fabric segmentation or merge because of hardware issues or a software bug.
ISL port becomes part of PCP results in fabric segmentation or merge because of a port flap.
If this problem occurs, syslogs indicate a failure and the flapped ISL could remain in a down state
because of a domain overlap.
This issue was resolved in Cisco SAN-OS Release 2.1(2b); therefore, you must upgrade to Release
2.1(2b) before upgrading to Release 3.1(2a). An upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b),
or 2.1(2a) to Release 2.1(2b) when IVR is enabled requires that you follow the procedure below, and
then follow the upgrade guidelines listed in the
“Upgrading Your Version of Cisco Fabric Manager”
section on page 10
. If you have VSANs in interop mode 2 or 3, you must issue an IVR refresh for those
VSANs.
To upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.1(2b) for all other
VSANs with IVR enabled, follow these steps:
Step 1
Configure static domains for all switches in all VSANs where IVR is enabled. Configure the static
domain the same as the running domain so that there is no change in domain IDs. Make sure that all
domains are unique across all of the IVR VSANs. We recommend this step as a best practice for
IVR-non-NAT mode. Issue the
fcdomain domain
id
static vsan
vsan id
command to configure the static
domains.
Note
Complete Step 1 for all switches before moving to Step 2.
Table 5
FICON Nondisruptive Upgrade Path to SAN-OS 3.1(2a)
Current Release with
FICON Enabled
Upgrade Path
SAN-OS 3.0(2)
You can nondisruptively upgrade directly to SAN-OS Release 3.1(2a).
SAN-OS 2.0(2b)
Use the
interface shutdown
command to administratively shut any Fibre
Channel ports on Generation 1 modules that are in an operationally down
state before nondisruptively upgrading from SAN-OS Release 2.0(2b) to
SAN-OS Release 3.0(2), and then upgrade to Release 3.1(2a). An
operationally down state includes
Link failure or not-connected, SFP
not present
, or
Error Disabled
status in the output of a
show interface
command. When an interface is administratively shut it will then show as
Administratively down
. Interfaces that are currently up or trunking do
not need to be shut down.
SAN-OS 1.x
Upgrade to SAN-OS Release 3.0(2). Use the
interface shutdown
command to shut all the ports operationally down and administratively up
on all the Generation 1 modules before nondisruptively upgrading to
Release 2.0(2b) and then upgrade to 1.3(4a).