Dell Brocade Adapters - Manual (Page 70)

46 Brocade Adapters Troubleshooting Guide
53-1002145-01
HCM and HCM Agent problems
2
Action: Check FCoE switch configuration using the appropriate Fabric OS command on the
attached switch. Refer to the Fabric OS Command Reference Manual for information. Change
configuration as necessary using appropriate Fabric OS command on the attached switch.
Refer to the Fabric OS Command Reference Manual for information.
3. Possible Cause: The front-end Ethernet port on the FCoE switch is not configured as
“switchport” or is not set to converged mode.
Action: Use the appropriate Fabric OS command on the attached switch to display information
about the VLAN interface. Refer to the Fabric OS Command Reference Manual for information.
Action: Configure the FCoE port as a “switchport” using the appropriate Fabric OS command on
the attached switch. Refer to the Fabric OS Command Reference Manual for information.
Action: Configure the FCoE port to converged mode using the appropriate Fabric OS command
on the attached switch.
HCM and HCM Agent problems
This section provides information to help resolve problems with HCM installation and operation.
Failed to connect to agent on host... error when using HCM
An “Adapter failed to connect to agent on host...” message indicates that the client application
cannot connect to the HCM agent listening on the configured port (normally TCP port 34568). Refer
to the following descriptions of possible causes and recommended actions to help resolve the
problem.
1. Possible Cause: If the hcmagent process exited in VMware ESX 3.5 or 4.x, the HCM Agent may
be configured to forward events to a remote Syslog host, but the outgoing UDP port 514 is
blocked by the ESX firewall.
Action: Perform the following steps.
a. Run the following command to open port 514.
esxcfg-firewall -o 514,udp,out,syslog
b. Start the agent using the following command.
hcmagentservice start
2. Other Possible Causes:
• The HCM Agent is not running.
• The HCM Agent is not accepting connections on the expected port.
• The HCM Agent is not listening on the expected port.
• Communication between the client and agent is blocked by a firewall preventing access to
the port (usually only a consideration for remote HCM management).