Vm manager discovery, Vm manager discovery requirements, Discovering a vm manager – Brocade Network Advisor SAN + IP User Manual v12.1.0 User Manual

Page 208

Advertising

Brocade Network Advisor SAN + IP User Manual

141

53-1002949-01

VM Manager discovery

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.

VM Manager discovery

The Management application enables you to discover VM managers. VM Manager discovery
requires vCenter Server 4.0 or later.

NOTE

vCenter discovery time is dynamically determined based on the number of hosts being managed by
the vCenter. For every 50 hosts managed, the vCenter collection period increases 30 minutes.
For 0-50 hosts managed, the collection duration is 30 minutes; for 50-100 hosts managed, the
collection duration is one hour, and so on.

VM Manager discovery requirements

•

Discovery of a vCenter server (refer to

“Discovering a VM manager”

on page 141,

step 4

and

step 5

), requires a vCenter user with read-only or read-write privilege on the vCenter server

node and all objects in the inventory below the vCenter server.

•

Enabling the vSphere client plug-in registration (refer to