HP Brocade 8/12c HP StorageWorks B-series Data Center Fabric Manager Enterpris - Page 37

Fixed in DCFM 10.1.4, DCFM displays the message

Get HP Brocade 8/12c PDF manuals and user guides View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 37 highlights

Closed defect summary Solution Zones that contain a hyphen in the zone name do not appear in the zone Fixed in DCFM 10.1.4 database table after migrating to DCFM, and a zone configuration mismatch alert occurs. During switch discovery with DCFM, the message Specified seed switch already present in another managed fabric appears, even though the switch was not present in the topology of the discovery dialog. This specified switch was part of an unmonitored fabric when it was discovered. Fixed in DCFM 10.1.4 Occasionally, after creating logical switches and adding ports to each of them, the logical switch change confirmation and status shows one or more of the logical switch configurations failed. Fixed in DCFM 10.1.4 nl Workaround prior to this upgrade: You could avoid this issue by nl using the CLI to create and config- ure logical switches. After the DCFM client accepted changes, the client was not updated and Fixed in DCFM 10.1.4 the discovery dialog was empty because the database connection was not closed. The CLI displays the NPIV device type for the attached node correctly as NPIV target, but the DCFM Product List displays the NPIV device type as NPIV initiator. The DCFM displays the encryption select target dialog host selection screen rather than select target dialog. Fixed in DCFM 10.1.4 When migrating from EFCM to DCFM, Call Home status does not migrate. Fixed in DCFM 10.1.4 This results in Call home being disabled for all M-series switches. If a nickname is set as Non-Unique in the EFCM V9.7.x options dialog, Fixed in DCFM 10.1.4 the nickname entry does not migrate to DCFM. After using DCFM for zeroization of the Encryption Engine on an nl encryption blade, the Encryption Group Link Key tab shows the status as OK. Fixed in DCFM 10.1.4 DCFM displays the message Zone Member or Alias not found Fixed in DCFM 10.1.4 for a B-series slot/port member that exists as a domain and port member in the zone. The DCFM local client is slow and eventually hangs during discovery, preventing new clients from opening. A second local client nl displays the message contacting the server on login attempt and the remote client displays the message Server not available at port xxxxx. Fixed in DCFM 10.1.4 An ISL Offline event policy type action is not triggered when an ISL goes Fixed in DCFM 10.1.4 down. After an authentication failure, all switches in a fabric become unreachable and DCFM discovery does not recover. All switches have a blank or empty password field. Fixed in DCFM 10.1.4 nl Workaround prior to this upgrade: You could recover by entering the password in the discovery setup window for every switch in the nl affected fabric. HP StorageWorks B-series Data Center Fabric Manager Enterprise 37

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
Solution
Closed defect summary
Fixed in DCFM 10.1.4
Zones that contain a hyphen in the zone name do not appear in the zone
database table after migrating to DCFM, and a zone configuration mis-
match alert occurs.
Fixed in DCFM 10.1.4
During switch discovery with DCFM, the message
Specified seed
switch already present in another managed fabric
ap-
pears, even though the switch was not present in the topology of the dis-
covery dialog. This specified switch was part of an unmonitored fabric
when it was discovered.
Fixed in DCFM 10.1.4
nl
Workaround prior to this upgrade:
You could avoid this issue by
nl
using the CLI to create and config-
ure logical switches.
Occasionally, after creating logical switches and adding ports to each of
them, the logical switch change confirmation and status shows one or
more of the logical switch configurations failed.
Fixed in DCFM 10.1.4
After the DCFM client accepted changes, the client was not updated and
the discovery dialog was empty because the database connection was
not closed.
Fixed in DCFM 10.1.4
The CLI displays the NPIV device type for the attached node correctly as
NPIV target
, but the DCFM Product List displays the NPIV device type
as
NPIV initiator
. The DCFM displays the encryption select target
dialog host selection screen rather than select target dialog.
Fixed in DCFM 10.1.4
When migrating from EFCM to DCFM, Call Home status does not migrate.
This results in Call home being disabled for all M-series switches.
Fixed in DCFM 10.1.4
If a nickname is set as
Non-Unique
in the EFCM V9.7.
x
options dialog,
the nickname entry does not migrate to DCFM.
Fixed in DCFM 10.1.4
After using DCFM for zeroization of the Encryption Engine on an
nl
encryption blade, the Encryption Group Link Key tab shows the status as
OK
.
Fixed in DCFM 10.1.4
DCFM displays the message
Zone Member or Alias not found
for a B-series slot/port member that exists as a domain and port member
in the zone.
Fixed in DCFM 10.1.4
The DCFM local client is slow and eventually hangs during discovery,
preventing new clients from opening. A second local client
nl
displays the message
contacting the server
on login attempt and
the remote client displays the message
Server not available at
port
xxxxx
.
Fixed in DCFM 10.1.4
An ISL Offline event policy type action is not triggered when an ISL goes
down.
Fixed in DCFM 10.1.4
nl
Workaround prior to this upgrade:
You could recover by entering the
password in the discovery setup
window for every switch in the
nl
affected fabric.
After an authentication failure, all switches in a fabric become unreachable
and DCFM discovery does not recover. All switches have a blank or empty
password field.
HP StorageWorks B-series Data Center Fabric Manager Enterprise
37