Cisco AJ732A - MDS 9134 Fabric Switch Release Note page 35

S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
CSCsk95241
•
Symptom: If you use JDK instead of JRE on Solaris, you might encounter a problem trying to install
Device Manager from a web browser. This can happen because the installer heap limit of 256 MB
is not sufficient.
Workaround: This issue is resolved.
• CSCsl15511
Symptom: On the MDS 12-port, 24-port, and 48-port 4-Gbps Fibre Channel switching modules, and
on the 4-port 10-Gbps Fibre Channel switching module for downgrades from 3.2(2c) to lower
versions, if fcdomain persistency is disabled, F ports may not come up after a shutdown or no
shutdown or a link flap.
Workaround: This issue is resolved.
CSCsl17944
•
Symptom: During an MDS 9222i switch reload, the connection from the management port (mgmt0) to
the Gigabit Ethernet interface goes down. When the connection comes back up, the Gigabit Ethernet
interface doesn't go into forwarding mode until 30 seconds later. The Fabric Manager server is not able
to communicate to the MDS 9222i switch through SNMP during this 30 second window.
Workaround: This issue is resolved.
CSCsl31087
•
Symptom: In DMM, if a server I/O to a LUN fails during data migration, that session is marked as failed.
The DMM migration job is then moved to a Failed state when the remaining sessions are complete. Such
a failed migration job can be scheduled for a restart. If such a failed migration job is scheduled to start in
less than 5 minutes from the time of scheduling, and another server I/O to a session LUN fails in that 5
minute window, the migration job will move from a Scheduled state to a Failed state. An administrator
has the option to start the job immediately or schedule it again. This problem does not happen if an
administrator schedules the migration job to start more than 5 minutes from the time of scheduling.
Workaround: This issue is resolved.
CSCsl34922
•
Symptom: Dual-fabric DMM migration jobs can not have one fabric running Release 3.2(1a) and a peer
fabric running Release 3.2(2c) due to a signal message change. This may cause unexpected results during
a DMM migration job validation, creation, start, and so on.
Workaround: This issue is resolved.
CSCsl42571
•
Symptom: SNMP timeouts occur when a AAA user ages out.
By design, a AAA user is aged out every hour on a switch for security reasons. If a large fabric is
discovered using a AAA user and a Performance Monitoring (PM) collection is added for such a
fabric, a number of SNMP requests (related to the discovery or PM statistics collection) could time
out. When a user views the PM statistics charts (in the Performance tab in the web client), the charts
are not seen as continuous.
Workaround: This issue is resolved.
OL-14116-11
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3)
Caveats
35