Advertisement
Connection between the Access Gateway and switches does not appear when
F_Port trunking is enabled on the Access Gateway
If a switch configured with F_Port trunking is connected to the Access Gateway, the F_Port trunk group
icon does not appear in the Product Tree, and the connection between the switch and the Access
Gateway is not displayed in the Topology. HP recommends that you disable F_Port trunking on the
switch before connecting it to the Access Gateway.
Opening the Zoning dialog fails during discovery
If you attempt to open the Zoning dialog before the discovery operation is complete, a Failed to
load Zone DB message appears. HP recommends that you wait until the discovery operation is
complete before you open the Zoning dialog.
Mi10k manageability issue after migration
After migrating to DCFM 10.3.x from DCFM 10.0.x or 10.1.x, an Mi10k is unable to gain
manageability. This is because Configure for Intrepid 10k is disabled and the displayed
user name is (API User | Administrator). HP recommends that you select the Configure for Intrepid
10k check box on the Edit dialog, SNMPv3 tab.
VMware firewall settings may require HCM agent to be restarted
If the firewall settings on port 514 changed in VMware, the HCM Agent must be restarted. VMware
(ESX 3.5 & 4) blocks the Syslog outgoing port 514 by default. If you are using a Syslog Host
configuration or HCM as part of DCFM, the firewall must be configured to allow outgoing port 514
for Syslog.
Use the command esxcfgfirewall -o 514,udp,out,syslog to open port 514 and the
command esxcfgfirewall -c 514,udp,out,syslog to block outgoing traffic through port
514.
HP StorageWorks DC SAN Director support in Professional Plus
DCFM Professional Plus edition can discover, but not manage, the HP DC SAN Backbone chassis.
To manage the device, launch the device Element Manager from the Connectivity Map.
The HP DC SAN Backbone Director cannot be used as a seed switch.
Failover restriction in mixed fabrics
In mixed fabrics, the seed switch must be an FOS switch. If the FOS seed switch becomes unreachable,
and there are no other manageable FOS switches in the fabric, failover to the EOS seed switch cannot
occur. You cannot change the seed switch to EOS manually.
In this situation, to manage the fabric:
1.
Disconnect the ISL between the FOS and EOS switches.
2.
Unmonitor or delete this fabric.
3.
Discover the Pure EOS Fabric by providing the EOS seed switch IP address.
Failover can occur in the following configurations:
FOS to FOS switches
EOS to EOS switches
B-series Data Center Fabric Manager Enterprise, Professional Plus, and Professional
17
Advertisement
