Brocade Communications Systems CNA 1010 Troubleshooting Manual page 55

1. Possible Cause: If the hcmagent process exited in VMware ESX 3.5 or 4.0, the HCM Agent may
2. Other Possible Causes:
Brocade Adapters Troubleshooting Guide
53-1001582-01
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.
hcmservice start
•
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).
Action: For Linux, Solaris, and VMware systems, perform the following steps to help isolate the
problem:
a. Verify that the agent is running by executing the appropriate status command for your
operating system as described in the "Software Installation" chapter in the Brocade
Adapters Installation and Reference Manual under "HCM Agent Operations."
b. If you receive a message that the hcmagent is stopped, restarting the agent should
resolve the problem. To restart, use the appropriate start command for your operating
system which is also described in the "Software Installation" chapter in the Brocade
Adapters Installation and Reference Manual under "HCM Agent Operations."
c. Note that one command described in the manual restarts the agent, but the agent will not
restart if the system reboots or the agent stops unexpectedly. Another command restarts
the agent, but the agent will restart if the system reboots.
d. Confirm the HCM Agent is responding to requests using the expected user password.
Execute the following command to connect to the HCM Agent and force it to collect the
adapter driver supportsave data.
NOTE
This command is a single line. The localhost can be replaced with a different IP address.
wget --no-check-certificate
https://admin:password@localhost:34568/JSONRPCServiceApp/
SupportSaveController.do
If successful, the file SupportSaveController.do (actually a zip format file) will contain the
data from the HCM Agent.
e. If you are managing a VMware host system through HCM from a remote system, the host's
firewall may be blocking TCP/IP port 34568, which allows agent communication with HCM.
Use the following command to open port 34568:
/usr/sbin/esxcfg-firewall-o 34568,tcp,out,https
Use Windows Firewall and Advanced Service (WFAS) to open port 34568.
HCM and HCM Agent problems
2
35