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].
12
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 2.1(2b)
OL-7411-04
Caveats
Workaround: Remove the QoS attribute from the IVR zone set, both active and configured, before
disabling QoS.
• CSCei18830
Symptom: Removing zones from an active zone set may generate a system message that the zone
activation has failed because of an Accept Change Authorization (ACA) failure.
Workaround: None required. The IVR retries the activation and eventually the zone set activation
succeeds.
• CSCei19822
Symptom: An active IVR zone set on the local switch is not propagated when the commit session
contains any other configuration changes.
Workaround: For Release 2.1(2), perform an implicit commit without any changes. In the case of
a merge failure and the IVR zone set is not active on remote switches but is active on a local switch,
issue an implicit commit from the local switch to propagate the active zone set to the remote
switches.
For releases prior to 2.1(2), the workaround is different. Add either a dummy member to an existing
zone or add a dummy zone with dummy members to the currently active IVR zone set, and then
reactivate the IVR zone set. Then issue the commit command, which will propagate the active zone
set to other switches.
• CSCei40874
Symptom: If port 9001 is in use by another process, the database update for the previous release
tables and data may hang.
Workaround: Edit the server.properties file in the bin directory and use another port. Alternatively,
remove the process that opened port 9001.
• CSCei53783
Symptom: An iSCSI host cannot log in to one IPS port after many supervisor module switchovers.
Workaround: None.
• CSCei55341
Symptom: Undefined objects are found in CISCO-VLAN-MEMBERSHIP-MIB.
Workaround: None.
• CSCec31365
Symptom: When IVR is enabled, the Fabric-Device Management Interface information is not
transferred across VSANs for IVR devices.
Workaround: None.
• CSCed16845
Symptom: Occasionally, the Common Information Model (CIM) server may be automatically
restarted because of an internal error. In this case, the connected CIM client is disconnected.
Workaround: You must explicitly reconnect the CIM client to the CIM server.
• CSCef56229
Symptom: If an iSCSI initiator is configured differently on multiple switches, iSNS might report
more targets to the initiator than the initiator can access. An iSCSI initiator would get a target error
if it attempts to establish a connection.
Workaround: None.