Cisco Cisco Fabric Manager Release 4.2

ページ / 24
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   f m - d o c f e e d b a c k @ c i s c o . c o m
17
Release Notes for Cisco Fabric Manager Release 4.2(7a)
OL-20325-08
  Caveats
Caveats
This section lists the open and resolved caveats for this release. 
Resolved Caveats
CSCtc83622
Symptom: Cisco Fabric Manager should not display a 120-day grace period whence CLI does not 
show a 120- day grace period for any feature that is not enabled.
Workaround: This issue is resolved.
CSCtd53603
Symptom: When the Enterprise license is not installed, role creation through SNMP fails.
Workaround: This issue is resolved.
CSCte16034
Symptom: If you create a password with a plus sign (+) for a Cisco Fabric Manager Server local 
user, the Cisco Fabric Manager web client rejects the password with the message: Please enter a 
valid password.
The client control panel of Cisco Fabric Manager allows you to create a password with the plus sign.
Workaround: This issue is resolved.
CSCtf17946
Symptom: Statistics are not shown correctly for a Performance Manager with a large sequence 
number. This symptom can occur when Cisco Fabric Manager Server restarts multiple times. For 
each restart, the sequence number increases.
Workaround: This issue is resolved.
CSCtg25758
Symptom: The following sorting issues occur on the flow page:
When all flows are enabled, you cannot search and identify a flow for a specific server.
The sort function is broken.
The web interface displays only 20 entries; when the entries are exported to Excel, there are 40 
entries and all others are zeros.
Workaround: This issue is resolved.
CSCtg68083
Symptom: ISL charts do not display in the Performance Manager web client GUI, even though the 
they are populated. This symptom may occur when Cisco Fabric Manager Server has been running 
for a long time and is upgraded. 
Workaround: This issue is resolved.
CSCtg73733
Symptom: If you clone a zone set and try to add multiple zones to multiple zone sets, you need to 
refresh the zoning tool so that the cloned zone set will have the correct name. Without the refresh, 
the cloned zone set will have the same name as the original zone set.
Workaround: This issue is resolved.