Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 2.1(2b) (OL-7411-04, September 2005)

Send documentation comments to [e-mail].
9
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 2.1(2b)
OL-7411-04
Caveats
Symptom: Even though FCIP IVR capability on a Cisco MDS 9216i switch is bundled with
hardware at no extra charge, a switch running Cisco MDS SAN-OS Release 2.1(1a) or later might
disable FCIP IVR functionality after the 120 days of enabling the feature. As a result, the Cisco
MDS 9216i switch will stop routing traffic, such as IVR functionality, over the FCIP links. There
are no issues if FCIP functionality is not enabled on the Cisco MDS 9216i switch.
Workaround: Contact your OSM and/or Cisco TAC to obtain and install SAN-OS version 2.1.2b.
If you are unable to upgrade to SAN-OS 2.1.2b at this time, then work with your OSM's service
organization to obtain and install a software fix.
• CSCei82417
Symptom: When multiple roles are configured on the switch, the SNMP process may consume more
memory if the user logs in using the GUI with some VSAN restrictions.
Workaround: Use the network-admin role only, the CLI only, or two well defined roles,
network-admin and network-operator.
• CSCei88345
Symptom: 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 running
might be disruptive. Some possible scenarios include:
– 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 RDI failure and the flapped lSL could remain in a down state
because of a domain overlap. This is caused by conflicts between the allowed domains list and the
virtual domain requested through RDI.
Workaround: There are four distinct scenarios for which the workarounds are provided.
1. If you are running Cisco MDS SAN-OS Releases 1.3(X) or 2.0(X) with IVR enabled, we
recommend upgrading to Release 2.0(2b). Please contact your OSM for 2.1(2b) availability.
2. If you have already upgraded some or all of your Cisco MDS SAN-OS switches from Cisco MDS
SAN-OS Release 1.3(X) or 2.0(x) to Release SAN-OS 2.1(1a), 2.1(1b), or 2.1(2a), a scheduled
downtime is required to perform the following steps:
a. 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 domainIDs. 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 2a for all switches before moving to Step 2b.
b. b. Issue the no ivr virtual-fcdomain-add vsan-ranges 1-4093 command to disable RDI mode on
all IVR enabled switches. This can cause traffic disruption.
Note Complete Step 2b for all IVR enabled switches before moving to Step 2c.
c. Check the syslogs for any ISL that was brought down.