Advertisement
Closed defect summary
M-EOS-based switches can be managed only by one DCFM server at
a time. If two DCFM servers attempt to manage the same M-EOS fabric,
and the fabric is then unmonitored in one of the DCFM servers to allow
the other DCFM server can manage the fabric, a too many ses-
sions error message appears, and that server still cannot gain man-
ageability of the M-EOS fabric.
If a CLI supportsave is in progress, an attempt to use DCFM to collect
supportsave data to the same switch fails.
DCFM allows you to add a switch with a domain ID greater than 31
in interopmode 2 to the zone, but zone activation fails with a Bad
Zone configuration error.
The Add FCIP Tunnel dialog online help is missing information about
the Select Switch Two button.
After a host is discovered, Auto enclosure is not created in the Fabric
view, and the wrong fabric WWN is shown on the host view.
When activating a zone with report generation enabled for an M-EOS-
only fabric, an error message is displayed and a report is not gener-
ated.
After a switch name is changed, the Master Log event count increments
with the old source name.
After a host name is changed, the DCFM client does not reflect the
new name until the client is relaunched.
After adding a single side tunnel to a DC SAN or 4/256 Director with
Multiprotocol Router Blade, the VE_Port number does not display with
the Tunnel ID.
nl
After adding a second side tunnel, the FCIP Tunnel/Circuit Configura-
tion Report returns an error.
The HTML image on the DVD displays Professional Edition
and must be replaced with the latest image.
When the TI zone is modified, the Zoning dialog displays an Alert
message before activating, and the change does not take place in the
zone configuration.
After creating a third circuit, the horizontal scroll bar does not appear
in the FCIP Tunnel dialog, Circuit tab.
44
Solution
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
Fixed in DCFM 10.3.2
nl
Workaround prior to this version:
nl
Close and reopen the FCIP Tunnel
dialog.
Advertisement
