Troubleshooting host discovery – Brocade Network Advisor SAN User Manual v12.3.0 User Manual

Page 118

Advertising
background image

66

Brocade Network Advisor SAN User Manual

53-1003154-01

Host discovery

3

HCM Agent unknown failure

WMI authentication failed

WMI connection failed

WMI Unknown Error

Discovery ignored. One or more adapters in the host are already a part of Host group {}

Discovery ignored. One or more adapters in the host are already a part of auto/manual
enclosure {}. Please delete the enclosure and try again.

Discovered

Discovering....

Rediscovering...

Deleting....

Internal Error

No Adapters found

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.

Advertising