When you need to use a Control Host
The Control Host is similar to a Standard Agent, except that it also lets you discover the following:
See About the Control Host.
See About the Standard Agent.
You might use a Control Host to discover remote hosts, arrays, switches, or VMware ESX servers for the following reasons:
Network configurations prohibit discovery
Network configurations might prohibit discovery from the Management Server if you need to:
Perform discovery of an object that is behind a firewall. If you do not want to install the Management Server in the firewall, you can:
Install a Control Host in the firewall.
Grant the Management Server access to the Control Host.
Configure discovery from the Control Host.
Run the EMC Solutions Enabler Command Line Interface (SYMCLI) to discover an EMC Symmetrix array, but you cannot run the SYMCLI from the Management Server.
You have a Solaris Management Server
CommandCentral cannot perform agentless discovery of a remote Windows host from a Solaris Management Server or Solaris Control Host. If you have a Solaris Management Server and you want to perform agentless discovery of a Windows host, initiate discovery from a Windows Control Host.
You want to distribute the discovery of hosts, arrays, switches, and VMware ESX servers
The Control Host can discover remote hosts, arrays, switches, and ESX servers and then send the discovery data to the Management Server. As a result, the Control Host can lessen the amount of computing that the Management Server would have to do to discover these objects directly.
Install a Control Host only if you need to use these capabilities. If you do not need these capabilities, use a different method to discover a host.
See How you can discover hosts in CommandCentral.