HP Cisco MDS 9140 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Rel - Page 37

Restart the Fabric Manager Server., Fabric Manager Server.

Page 37 highlights

Caveats Send documentation comments to [email protected] Workaround: Cancel the DMM job and then recreate it. • CSCsk26424 Symptom: Removing a fabric and then adding the same fabric in Fabric Manager causes a session fabric ID mismatch. As a result, hosts to not appear in the Step 1 window of the the Fabric Manager DMM job creation wizard. Workaround: Restart the Fabric Manager Server. • CSCsk35725 Symptom: Fabric Manager takes 2 to 3 minutes to bring up the DMM job creation wizard in a setup with 25 switches, 400 enclosures, and 2400 entries in the name server. Workaround: None. • CSCsk35951 Symptom: In a configuration with a PortChannel with FCIP members and Write Acceleration in use, if IVR NAT is enabled on one end of the PortChannel and not enabled on the other end, then traffic over the FCIP tunnel might fail. Workaround: Enable IVR NAT on both ends of the PortChannel or disable it on both ends. • CSCsk39341 Symptom: Although the FCIP compression ratio is set to Auto, it does not display correctly in Fabric Manager Server. Workaround: None. • CSCsk49309 Symptom: IPv6 duplicate address detection (DAD) may not always works for the management port. Workaround: None. • CSCsk63929 Symptom: If DMM is provisioned on the SSM and you downgrade to a Cisco MDS SAN-OS release that does not support DMM, the configuration persists and the GUI and CLI show DMM as a provisioned application. Workaround: Manually remove the DMM configuration from the switch before downgrading to a Cisco MDS SAN-OS release that does not support DMM, such as downgrading from SAN-OS Release 3.2(1) to SAN-OS Release 3.1(3). If you forget to remove the configuration before the downgrade, power off the module and purge the configuration on the SSM module by entering the following commands: switch(config)# poweroff module slot switch# purge module slot running-config • CSCsi56167 Symptom: The response time shown in the output of a ping ip-address command may not be accurate if there is an MDS MSM -8/4 in the path. Workaround: Use the ips measure-rtt command to measure the round trip time. • CSCsk43927 Symptom: The following Fabric Manager client components that use SSH and Telnet do not work well with NAT: • DMM storage job creation • Cisco SAN-OS software upgrade OL-14116-02 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1a) 37

  • 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]
37
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1a)
OL-14116-02
Caveats
Workaround
: Cancel the DMM job and then recreate it.
CSCsk26424
Symptom
: Removing a fabric and then adding the same fabric in Fabric Manager causes a session
fabric ID mismatch. As a result, hosts to not appear in the Step 1 window of the the Fabric Manager
DMM job creation wizard.
Workaround
: Restart the Fabric Manager Server.
CSCsk35725
Symptom
: Fabric Manager takes 2 to 3 minutes to bring up the DMM job creation wizard in a setup
with 25 switches, 400 enclosures, and 2400 entries in the name server.
Workaround
: None.
CSCsk35951
Symptom
: In a configuration with a PortChannel with FCIP members and Write Acceleration in
use, if IVR NAT is enabled on one end of the PortChannel and not enabled on the other end, then
traffic over the FCIP tunnel might fail.
Workaround
: Enable IVR NAT on both ends of the PortChannel or disable it on both ends.
CSCsk39341
Symptom
: Although the FCIP compression ratio is set to Auto, it does not display correctly in
Fabric Manager Server.
Workaround: None.
CSCsk49309
Symptom
: IPv6 duplicate address detection (DAD) may not always works for the management port.
Workaround
: None.
CSCsk63929
Symptom
: If DMM is provisioned on the SSM and you downgrade to a Cisco MDS SAN-OS release
that does not support DMM, the configuration persists and the GUI and CLI show DMM as a
provisioned application.
Workaround
: Manually remove the DMM configuration from the switch before downgrading to a
Cisco MDS SAN-OS release that does not support DMM, such as downgrading from SAN-OS
Release 3.2(1) to SAN-OS Release 3.1(3). If you forget to remove the configuration before the
downgrade, power off the module and purge the configuration on the SSM module by entering the
following commands:
switch(config)#
poweroff module
slot
switch#
purge module
slot
running-config
CSCsi56167
Symptom
: The response time shown in the output of a
ping
ip-address
command may not be accurate if
there is an MDS MSM -8/4 in the path.
Workaround
: Use the
ips measure-rtt
command to measure the round trip time.
CSCsk43927
Symptom
: The following Fabric Manager client components that use SSH and Telnet do not work
well with NAT:
DMM storage job creation
Cisco SAN-OS software upgrade