HP StorageWorks B-series Data Center Fabric Manager Professional 10.1.x Release Notes (5697-0804 July 2009 - includes all 10.1.x versions)

SolutionClosed defect summary
Fixed in DCFM 10.1.0
Workaround—If the user wants to generate the graph
for all the types[active and inactive
tunnels], the user will have to select FCIP from the
historical wizard from the "From" drop-down list and
then generate a graph. But for real time the user
cannot select in active tunnels.
Port selection button does not get enabled for inactive
FCIP tunnel in performance port picker
Symptom—Suppose a tunnel is present which was
active some time back and later becomes inactive then
the user will not be able generate graph for inactive
tunnel as the port selector is disabled for inactive FCIP
tunnels in the performance port picker.
Fixed in DCFM 10.1.0Zoning report showing zone name twice when zone
is part of active zone config.
Symptom—When user generates report with active
zone config, the active zone appears twice in the
Report with Active=Yes and Active=No values.
Fixed in DCFM 10.1.0
Workaround—Enter a valid backup directory, even if
backup is disabled.
DCFM Professional, disable backup,
nl
migrate to enterprise, open options-backup, close, in-
valid error message.
Symptom—A confusing error message when using the
options dialog after migration. Even though the backup
is disabled the path is invalid and must contain a valid
path.
Fixed in DCFM 10.1.0
Workaround—Trace Route summary dialog shows
information in Fcping tab and blank Forward and
Reverse Route tabs instead of showing an error
message when McDATA fabric mode is set.
Error message is not displayed when Trace Route
nl
operation fails due to McDATA fabric mode.
Fixed in DCFM 10.1.0Informational message is not appearing when the user
tries to enable notification from the user dialog, when
it is disabled from the main dialog(Monitor >
Event Notification > Email).
Symptom—User will not get warned that the
notification is disabled when he tries to enable an
event notification from the user management dialog.
Fixed in DCFM 10.1.0
Workaround—Close and relaunch the DCFM Client.
The connection between the FOS and EOS switches
is not shown on launching DCFM Client for the first
time after a migration from EFCM to DCFM.
Symptom—On launching DCFM Client for the first time
after a migration from EFCM to DCFM, the connection
between the FOS and the EOS switch is not displayed
in the Connectivity map.
Fixed in DCFM 10.1.0Changing server IP after DCFM installation created
multiple issues.
Symptom—During installation, the option 'any' was
chosen in the ipconfiguration screen. After installing
DCFM, on changing the server machine IP, it is
observed that the DCFM client is not launching. The
Client login window itself was not shown on trying to
launch the DCFM client. The DCFM server services
were still running. The client failed to launch even after
restarting the server.
14