HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS R - Page 17

FICON Supported Releases and Upgrade Paths, Upgrading with IVR Enabled, FICON Supported Releases

Page 17 highlights

Upgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] FICON Supported Releases and Upgrade Paths Cisco MDS SAN-OS Release 3.3(4) does not support FICON. Table 7 lists the SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes for FICON upgrade path information. Table 7 FICON Supported Releases FICON Supported Releases NX-OS Release 4.1(1c) SAN-OS Release 3.3(1c) Release 3.2(2c) Release 3.0(3b) Release 3.0(3) Release 3.0(2) Release 2.0(2b) 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); you must upgrade to Release 2.1(2b) before upgrading to Release 3.3(4). 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-14116-12 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4) 17

  • 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

Send documentation comments to [email protected]
17
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4)
OL-14116-12
Upgrading Your Cisco MDS SAN-OS Software Image
FICON Supported Releases and Upgrade Paths
Cisco MDS SAN-OS Release 3.3(4) does not support FICON.
Table 7
lists the SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes
for FICON upgrade path information.
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); you must upgrade to Release 2.1(2b) before
upgrading to Release 3.3(4). 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 7
FICON Supported Releases
FICON Supported Releases
NX-OS
Release 4.1(1c)
SAN-OS
Release 3.3(1c)
Release 3.2(2c)
Release 3.0(3b)
Release 3.0(3)
Release 3.0(2)
Release 2.0(2b)