About Control Hosts in Veritas Operations Manager 5.0

Article:HOWTO78446  |  Created: 2012-08-24  |  Updated: 2012-08-24  |  Article URL http://www.symantec.com/docs/HOWTO78446
Article Type
How To

Product(s)

Subject


About Control Hosts in Veritas Operations Manager 5.0

Veritas Operations Manager uses Control Hosts as a discovery mechanism. In Veritas Operations Manager, the Control Hosts discovers the following:

  • Information on VMware Virtualization Infrastructure. To configure this Control Host on a managed host, you need to install the Control Host Add-on on the managed host.

  • Agentless discovery of a host. The Control Host Add-on enables a managed host to perform agentless discovery of remote hosts. Platform support for a host that can act as a Control Host is the same as that of Management Server.

Note:

The following sections provide detailed information about the above-mentioned features.

Information on VMware Virtualization Infrastructure

In Veritas Operations Manager, you can configure Veritas Operations Manager Management Server or a managed host that reports to Management Server as Control Host for discovering the information on the VMware virtualization infrastructure. For this configuration, you must install the Control Host Add-on on the traditional hosts that you want to designate as Control Host. In Veritas Operations Manager, you must download the Control Host Add-on from the Symantec Web site, upload to the Deployment Management Repository, and install it on the relevant traditional hosts.

In your datacenter, Control Hosts help Management Server in discovering the following information on VMware virtualization infrastructure:

  • VMware VirtualCenter servers that are configured in your datacenter.

  • VMware ESX servers that Virtual Centers manage.

  • VMware Virtual machines that are configured on the VMware ESX servers.

  • VMware HA Clusters

In Veritas Operations Manager, you can install the Control Host Add-on on the managed hosts with the following platforms:

  • Solaris 10 (SPARC)

  • Linux (64-bit)

  • Solaris x86 (64-bit)

  • Windows Server 2003/2008 (64-bit)

    Note:

    To administer a Control Host on the Windows platform, Veritas Operations Manager creates a user named 'vomuser' with the administrative privileges.

Ensure that the Control Hosts can ping the VirtualCenter servers from which they can discover the information on VMware Infrastructure.

The Control Host discovers the VMware Infrastructure from the traditional hosts other than Management Server. After the discovery of VMware Infrastructure, the Control Host reports the discovered data to Management Server. Management Server coalesces the data that it receives from the Control Host and populates the relevant views.

You can designate a managed host that reports to Management Server as Control Host to address the following situations:

  • To discover the VirtualCenter server that is behind a firewall and you do not want to install Management Server inside the firewall.

  • To except Management Server from the discovery of VMware infrastructure to reduce the load on Management Server.

Agentless discovery of a remote host

To perform agentless discovery of hosts, you must install the Control Host Add-on on one of the managed hosts. You can install the Control Host Add-on on Management Server, however it is not recommended as it puts extra load on Management Server.

A UNIX Control Host can only discover UNIX agentless hosts using SSH. A Windows Control Host can discover Windows agentless hosts using WMI or UNIX agentless hosts using SSH. Ensure that you install one or more Control Hosts on the appropriate platform depending on the operating system of the remote hosts you want to discover agentlessly.

See How Veritas Operations Manager 5.0 discovers VirtualCenter and ESX servers

See Information that Veritas Operations Manager 5.0 discovers on the VMware Infrastructure components

See About agentless discovery using the Control Host in Veritas Operations Manager 5.0.


Legacy ID



v55387189_v71172234


Article URL http://www.symantec.com/docs/HOWTO78446


Terms of use for this information are found in Legal Notices