Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(2c) (OL14116-03, November 2007)

Send documentation comments to [e-mail]
27
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(2c)
OL-14116-03
Limitations and Restrictions
CWDM SFPs
The 2-Gbps CWDM SFPs do not have have a maximum speed set in memory and they negotiate to
4-Gbps on modules that support the higher speed. As a result, the link comes up and appears to work,
but then becomes disabled and connectivity problems occur. To correct this problem, both sides of the
connection must have their speed hard coded to 2-Gbps.
Fabric Manager
Observe the following limitations or restrictions for the Cisco SAN-OS Release 3.2(2c) for Fabric
Manager:
• By default, the database and aaa passwords are stored in plain text. You can encrypt them by using
the encrypter.bat/.sh script and pasting the output into the appropriate file, either server.properties
or aaa.properties.
• The Microsoft Security Patch MS06-040 is known to break applications with a large heap memory.
If you increase any Java application's heap (including Fabric Manager) beyond 64 M, we
recommend you do not apply this patch.
• If port 80 on the switch is blocked and you are using VPN, Fabric Manager cannot detect NAT
addresses. The timeout for URL connections is set for 500ms.
MTU Size Limitation
The Cisco MDS 9216i switch and MPS-14/2 module do not support an MTU size greater than 8000
bytes. An attempt to set the MTU size greater than 8000 bytes will result in an error. As a workaround,
reset the value of the MTU size (576 to 8000 bytes) and issue the no shutdown command on the interface
for normal operation.
Reconfiguring SSM Ports
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.1(1). For instructions about how to
modify the configuration of the ports before upgrading to SAN-OS Release 3.1(3a), see the
“Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.2(2c)” section on page 17.
Virtual Router Redundancy Protocol (VRRP) Interfaces
When a switchover occurs on a switch that is the master for Virtual Router Redundancy Protocol (VRRP)
interfaces, the switchover may cause a minor delay. As a result, the VRRP backup (occurring elsewhere)
may assume the role of the VRRP master. As a workaround, increase the VRRP advertisement interval
for these interfaces.