2.4 Alternative Installation Methods for the Cloud Manager Monitoring Agent

The Cloud Manager Monitoring Agent can be installed on a server where any other Orchestration pattern is installed or independently on a SLES or Windows server. The agent installation lays down the Ganglia Agent on each monitored node to collect performance metrics and send the data to the Cloud Manager Monitoring Server.

If you need to install Cloud Manager Monitoring Agent files without using the standard SLES installation script, the information in this section can help you identify the installation source files and give you some direction on how to install them to Linux or Windows machines.

For more information about agent installation, see Section A.0, Advanced Agent Installation Methods.

2.4.1 Installing the Cloud Manager Monitoring Agent on Linux Servers

This section can help you identify the correct installation files for the Cloud Manager Monitoring Agent on the Cloud Manager product ISO and provide you with some installation instructions for installing those files on SLES or RHEL servers.

Cloud Manager Monitoring Agent Installation Files for Linux Servers

The Cloud Manager Monitoring Agent uses both the agent program files

Table 2-2 Monitoring Agent Installation Pattern Files for Linux

Operating System

Installation File

  • SLES 11 SP2 (64-bit)

  • <cd>/suse/setup/descr/zw_mon_agent-3.1.3-0.x86_64.pat

  • RHEL 6 (latest update, 64-bit)

  • <cd>/RHEL6/novell-zenworks-monitor-gmond-3.0.4-67.1.x86_64.rpm

  • RHEL 5 (latest update, 64-bit)

  • <cd>/RHEL5/novell-zenworks-monitor-gmond-3.0.4-67.1.x86_64.rpm

2.4.2 Installing the Cloud Manager Monitoring Agent On Windows Machines

Installing the Cloud Manager Orchestration Agent on Microsoft Windows Server 2003 or Windows Server 2008 (see Section 2.2.2, Installing the Agent on Windows Machines) does not automatically install the Cloud Manager Monitoring Agent.

A separate installation package is available for installing the Monitoring Agent on Windows platforms where you have installed the Orchestration Agent.

This section includes the following information:

Installing the Cloud Manager Monitoring Agent for Windows

Hardware and Software Requirements

The Cloud Manager Monitoring Agent (gmond) can be installed only on Windows Server 2003 or Windows Server 2008 machines where the Orchestration Agent is also installed. Only a 32-bit version of gmond is provided, but it will run normally on 64-bit systems. It requires the same minimum hardware configuration as the Orchestration Agent. Port 8649 must be available for gmond to communicate with the agent.

Installing the Monitoring Agent

Use these steps to install the Monitoring Agent as a service on a local Windows Server 2003 or Windows Server 2008 machine.

  1. Download the pertinent Add-On ISO from the product DVD.

  2. Create a CD from the ISO or use ISOBuster (or a similar tool) to mount the ISO.

  3. Browse to the Windows/ folder and search for the Cloud Manager Monitoring Agent.

  4. Double-click the Monitoring Agent icon (gmondsetup.exe) and follow the wizard through the setup:

    NOTE:You must be logged on as Administrator to run the installation program. If you are installing on Windows Server 2008, click Accept in the User Account Control dialog box to allow the installation to proceed as system administrator.

Starting and Stopping the Monitoring Agent

If you are logged on as the Windows administrator, you can start and stop the gmond service by using the Windows Services Control Panel.

  1. From the desktop, click My Computer, select Manage, expand Services and Applications, expand Services, then right-click the gmond service object and choose the Start or Stop option as needed.

Uninstalling the Monitoring Agent

You can uninstall gmond by using the Add/Remove Programs utility in the Windows Control Panel. Uninstalling gmond automatically shuts down the gmond service prior to uninstalling.

Configuring the Monitoring Agent for Windows

This version of the Monitoring Agent uses the open source gmond 3.1.7 code. It is preconfigured to run only on a Windows local machine. It does not support multicasting. The installation includes a preconfigured gmond.conf that works only on the local host. You can manually edit gmond.conf for a different configuration, but your changes are not supported by Novell.

If you choose to customize an unsupported configuration for your needs, you can test the configuration by stopping the gmond service and then restarting gmond from the Windows command line prompt. Use the -d (debug) and -f (foreground) options to capture any error messages generated by the new configuration.