HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Re - Page 20

Reconfiguring SSM Ports Before Upgrading to NX-OS Release 4.2(1a

Page 20 highlights

Upgrading Your Cisco MDS NX-OS Software Image Send documentation comments to [email protected] 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(1c). 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. 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. Step 2 Issue the no ivr virtual-fcdomain-add vsan-ranges vsan-range command to disable RDI mode on all IVR enabled switches. The range of values for a VSAN ID is 1 to 4093. This can cause traffic disruption. Note Complete Step 2 for all IVR enabled switches before moving to Step 3. Step 3 Step 4 Step 5 Step 6 Step 7 Check the syslogs for any ISL that was isolated. 2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$ Isolation of interface PortChannel 52 (reason: unknown failure) 2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$ Isolation of interface PortChannel 51 (reason: domain ID assignment failure) Issue the following commands for the isolated switches in Step 3: switch(config)# vsan database switch(config-vsan-db)# vsan vsan-id suspend switch(config-vsan-db)# no vsan vsan-id suspend Issue the ivr refresh command to perform an IVR refresh on all the IVR enabled switches. Issue the copy running-config startup-config command to save the RDI mode in the startup configuration on all of the switches. Follow the normal upgrade guidelines for Release 2.1(2b). If you are adding new switches running Cisco MDS SAN-OS Release 2.1(2b) or later, upgrade all of your existing switches to Cisco SAN-OS Release 2.1(2b) as described in this workaround. Then follow the normal upgrade guidelines for Release 3.3(1c). Note RDI mode should not be disabled for VSANs running in interop mode 2 or interop mode 3. Reconfiguring SSM Ports Before Upgrading to NX-OS Release 4.2(1a) Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode, which is the default for releases prior to Release 3.0(1). Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a) 20 OL-19964-02

  • 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
  • 45
  • 46
  • 47
  • 48

Send documentation comments to [email protected]
20
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a)
OL-19964-02
Upgrading Your Cisco MDS NX-OS Software Image
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(1c). 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. 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.
Step 2
Issue the
no ivr virtual-fcdomain-add vsan-ranges
vsan-range
command to disable RDI mode on all
IVR enabled switches. The range of values for a VSAN ID is 1 to 4093. This can cause traffic disruption.
Note
Complete Step 2 for all IVR enabled switches before moving to Step 3.
Step 3
Check the syslogs for any ISL that was isolated.
2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED:
%$VSAN 2005%$ Isolation of interface
PortChannel 52 (reason: unknown failure)
2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$
Isolation of interface PortChannel 51
(reason: domain ID assignment failure)
Step 4
Issue the following commands for the isolated switches in Step 3:
switch(config)#
vsan database
switch(config-vsan-db)#
vsan
vsan-id
suspend
switch(config-vsan-db)# no
vsan
vsan-id
suspend
Step 5
Issue the
ivr refresh
command to perform an IVR refresh on all the IVR enabled switches.
Step 6
Issue the
copy running-config startup-config
command to save the RDI mode in the startup
configuration on all of the switches.
Step 7
Follow the normal upgrade guidelines for Release 2.1(2b). If you are adding new switches running Cisco
MDS SAN-OS Release 2.1(2b) or later, upgrade all of your existing switches to Cisco SAN-OS Release
2.1(2b) as described in this workaround. Then follow the normal upgrade guidelines for Release 3.3(1c).
Note
RDI mode should not be disabled for VSANs running in interop mode 2 or interop mode 3.
Reconfiguring SSM Ports Before Upgrading to NX-OS Release 4.2(1a)
Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be
configured in auto mode, which is the default for releases prior to Release 3.0(1).