Troubleshooting host discovery – Brocade Network Advisor IP User Manual v12.1.0 User Manual
Page 166
112
Brocade Network Advisor IP User Manual
53-1002947-01
Host discovery
4
The Discovery Status field details the actual status message text, which varies depending on
the situation. The following are samples of actual status messages:
•
Discovered
•
New Discovery Pending
•
Created host structure differs from discovered host; Discovery ignored
•
Brocade HBA Discovery Failed: HCM Agent connection failed
•
HCM Agent collection failed
•
CIM Server Authentication failed
•
CIM Server connection failed
Troubleshooting host discovery
If you encounter discovery problems, complete the following checklist to ensure that discovery was
set up correctly. For more complete information about troubleshooting adapters, refer to the
Adapters Troubleshooting Guide.
1. Verify IP connectivity by issuing a ping command to the host.
a. Open the command prompt.
b. From the Server, type
ping
Host_IP_Address
.
2. If the host is responding to ping, but discovery still fails, verify that HCM agent is up or not by
browsing to the following URL:
https://Host_IP_Address:34568/JSONRPCServiceApp/JSON-RPC
If HCM agent is running and reachable, you should receive a prompt of credentials and then
show an Error 500 (No Reason) result page.
3. Verify that firewall port 34568 is open.
There are firewall issues with the HCM Agent on Windows 2008 and VMware systems. When
installing the driver package on these systems, open TCP/IP port 34568 to allow agent
communication with the Management application.
•
For VMware, use the following commands to open port 34568:
esxcfg-firewall –o 34568,tcp,in,https
esxcfg-firewall –o 34568,udp,out,https
•
For Windows, use Windows Firewall and Advanced Service (WFAS) to open port 34568.
TABLE 19
Discovery Status Icons
Icon
Description
Displays when the fabric or host is managed and the management status is okay.
Displays when the fabric or host is not managed.