Advertisement
Closed defect summary
Repeated Failed to send Call Home error messages appear in
the Master log of DCFM 10.1.3 when Call Home is disabled.
You cannot use RADIUS Authentication using Password Authentication
Protocol (PAP).
Migrating from EFCM to DCFM does not include migration of config-
uration information such as nicknames, user names, passwords, and
banner.
DCFM 10.3.1 fixes
Table 5
lists the defects that were closed for this release.
Table 5 DCFM 10.3.1 fixes
Closed defect summary
Activated LSAN zone is not shown in the LSAN zoning dialog after
reopening the dialog.
Unable to unblock an automatically disabled port from the Port Auto
Disable (PAD) dialog.
Duplicate tunnels are shown in the FCIP tunnel dialog. After creating
4 tunnels, 4 more duplicate tunnels are shown, and then unable to
create a 5th tunnel.
Tunnel links are not being displayed in Topology. Switches in the
fabric appear isolated without any link between them, and the user
does not have the option to launch the connection properties dialog.
Client logouts observed in the Scalability server when the port count
is much greater than 9000.
Local client connectivity lost to Linux and Solaris servers, requiring
logging in again.
Due to HCM agent connection failure, the host and storage connected
to a fabric are shown isolated in the host view when the host is redis-
covered.
Duplicate virtual NPIV ports are shown in the device tree for the M-
series switch after migrating from EFCM to DCFM.
A gray icon is displayed for 2408 FCoE switches and the device tree
does not show attached ports for those switches.
DCFM cannot be used to set or change a CNA node or port name.
HCM must be used.
40
Solution
Fixed in DCFM 10.3.0
Fixed in DCFM 10.3.0
Fixed in DCFM 10.3.0
Solution
Fixed in DCFM 10.3.1
nl
Workaround prior to this version:
nl
Wait for up to 30 minutes and activ-
ated LSAN zone will be shown.
Fixed in DCFM 10.3.1
nl
Workaround prior to this version:
nl
Use CLI to unblock the port.
Fixed in DCFM 10.3.1
Fixed in DCFM 10.3.1
Fixed in DCFM 10.3.1
Fixed in DCFM 10.3.1
Fixed in DCFM 10.3.1
nl
Workaround prior to this version:
nl
Delete the newly discovered host,
monitor the old fabric, delete and re-
discover the host
Fixed in DCFM 10.3.1
Fixed in DCFM 10.3.1
Fixed in DCFM 10.3.1
Advertisement
