Chat now with support
Chat with Support

Foglight Agent Manager 6.3.0 - Foglight Agent Manager Guide

Configuring the embedded Agent Manager Installing external Agent Managers
Understanding how the Agent Manager communicates with the Management Server Deploying the Agent Manager cartridge Downloading the Agent Manager installer Installing the Agent Manager Starting or stopping the Agent Manager process Frequently asked questions
Configuring the Agent Manager Advanced system configuration and troubleshooting
Configuring Windows Management Instrumentation (WMI) Configuring Windows Remote Management (WinRM) UNIX- and Linux-specific configuration
Monitoring the Agent Manager performance Deploying the Agent Manager to large-scale environments

Part 3: Add the script parameters

After performing the preliminary steps, you are ready to start configuring the Agent Manager deployment script.

In this part of the example, you will add the list of parameters for the script.

 
* 
NOTE: The default values shown for these parameters are examples only. The steps below describe how to configure these example settings for your environment.
1
Navigate to the fglaminstall working directory.
2
Open remote_install_fglam_example.sh.
3
Add the following lines, which describe the parameters you are about to set for the script:
#!/bin/sh
# Script to download, install, and run the Agent
# Manager
#
# THIS CODE AND INFORMATION ARE PROVIDED "AS IS" WITHOUT
# WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
# INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF
# MERCHANTBILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE.
#
############################################################
# Location of the hostnames file for mass deployment.
HOSTFILE=/fglaminstall/hostnames
# Location of the Management Server.
FMS=[http|https]://<hostname>:<port>
# Operating system user name to run the installation on the
# remote hosts.
FGLAM_USER=foglight
# Installation directory, which should be writable by the
# Agent Manager user.
INSTALL_DIR=/opt/Quest_Software/Foglight_Agent_Manager
# Management Server version (specified without punctuation, for example:
555 for version 5.5.5).
FMS_VER=558
###########################################################
# The following lines do not require configuration.
# URL for downloading installers (requires version 5.2.4+ of
# the Management Server).
FMS_INSTALLERS=\
/console/installer/download-installer.action?downloadId=
if [ $FMS_VER -lt 550 ]; then
FMS_INSTALLERS=/catalyst-glue-service/installers/
fi
4
Change the value of HOSTFILE to the location of the text file hostnames that you created in Part 2: Create a list of hosts .
5
Change the value of FMS to the URL of the Management Server (version 5.2.4 or higher) from which you want to retrieve the Agent Manager installers and to which the Agent Manager instances connect. Use the format
<http|https>://<hostname>:<port>
where <hostname> is the resolvable DNS name or IP address and <port> is the HTTP port specified during installation (the default port is 8080).
If the Management Server has been configured to use HTTPS, then you can specify https as the protocol used by the Foglight Agent Manager to connect to the Management Server.
6
Change the value of FGLAM_USER to the name of the user that your UNIX administrator created for you to use when running the Agent Manager.
7
Change the value of INSTALL_DIR to the directory on each machine where the Agent Manager is being installed.
8
Change the value of FMS_VER to the version number of the Management Server (version 5.2.4 or higher) from which you want to retrieve the Agent Manager installers and to which the Agent Manager instances will connect. Specify the version number without punctuation, for example: 567, for Management Server version 5.6.7.
9
Save remote_install_fglam_example.sh.

Part 4: Specify the script commands

The steps below describe the process of specifying the commands to download and run the installers on the remote hosts and to run the installed Agent Manager instances.

1
Add the lines below after those that you added in Part 3: Add the script parameters . These lines verify the existence of the hostnames file and then process it.
############################################################
# Check that the HOSTFILE exists.
if [ -r $HOSTFILE ]; then
# Start the For loop to process each host in the HOSTFILE.
for i in $(cat $HOSTFILE);
do
# Parse the HOSTFILE to get the host name and then the
# installer type.
HOSTNAME=`echo $i | awk -F , '{print $1}'`
OSTYPE=`echo $i | awk -F , '{print $2}'`
if [ $FMS_VER -ge 550 ]; then
FMS_VER_MAJOR=`echo $FMS_VER | cut -c1`
FMS_VER_MINOR=`echo $FMS_VER | cut -c2`
FMS_VER_MICRO=`echo $FMS_VER | cut -c3`
INSTALLER_PREFIX=fglam-\
${FMS_VER_MAJOR}_${FMS_VER_MINOR}_${FMS_VER_MICRO}-
else
INSTALLER_PREFIX=fglam-
fi
# Match the operating system to the installer.
case $OSTYPE in
aix)
INSTALLER=${INSTALLER_PREFIX}aix-powerpc.bin
;;
linux64)
INSTALLER=${INSTALLER_PREFIX}linux-x86_64.bin
;;
linux32)
INSTALLER=${INSTALLER_PREFIX}linux-ia32.bin
;;
solaris)
INSTALLER=${INSTALLER_PREFIX}solaris-sparc.bin
;;
solarisx86)
INSTALLER=${INSTALLER_PREFIX}solaris-x86_64.bin
;;
hpux)
INSTALLER=${INSTALLER_PREFIX}hpux-parisc.bin
;;
hpuxia64)
INSTALLER=${INSTALLER_PREFIX}hpux-ia64.bin
;;
*)
echo "Cannot match the operating system type ($OSTYPE) for \
$HOSTNAME, skipping the deployment of the Agent \
Manager to that host."
continue;
;;
esac
2
Add the lines below to the end of the file. These lines run the ssh command that:
•
Retrieves the installers using Wget.
•
Uses the silent installer to install the Agent Manager on each remote UNIX host specified in the hostnames file. The Agent Manager silent installer is invoked in this example with the command /tmp/${INSTALLER} --silent --fms url=${FMS} --installdir ${INSTALL_DIR}.
•
Runs the Agent Manager on the specified hosts.
############################################################
# Run the SSH command to install the Agent Manager.
ssh $FGLAM_USER@$HOSTNAME "cd /tmp; wget -q \
--tries=10 \"${FMS}${FMS_INSTALLERS}${INSTALLER}\" \
-O ${INSTALLER}; chmod a+x /tmp/${INSTALLER}; \
/tmp/${INSTALLER} --silent --fms url=${FMS} --installdir \
${INSTALL_DIR}; sleep 3; ${INSTALL_DIR}/bin/fglam \
--daemon; sleep 3; rm /tmp/${INSTALLER};"
echo "Installation complete on $HOSTNAME."
echo "Connect to $HOSTNAME and use tail -f \
${INSTALL_DIR}/state/default/logs/FglAM*.log to validate \
the installation."
done
else
echo "$HOSTFILE does not exist, exiting..."
exit 1
fi
exit 0
3
Save remote_install_fglam_example.sh.

Part 5: Run the script

Once you have finished editing the deployment script, it is ready to run to deploy the Agent Manager to the remote UNIX hosts.

 
* 
NOTE: This part of the example describes using one type of login method (passwords) for connecting to remote machines using SSH. However, if you have private keys configured in your environment, then you might encounter one of the following scenarios when establishing an SSH connection:
•
You do not need to provide a password because the host to which you are connecting is a trusted host.
•
You are prompted for a passphrase instead of a password.
1
Ensure that remote_install_fglam_example.sh is executable.
2
Execute the remote_install_fglam_example.sh script.
If Wget is not found on a host or if the operating system listed for a host in the hostnames file does not match the operating system types listed in the script, the script continues deploying the Agent Manager to the rest of the hosts that you specified in the hostnames file.
3
Provide a password for each host when you are prompted to do so.
The Agent Manager is installed and running on the specified hosts.

Example: Deploying the Agent Manager to multiple Windows hosts

The recommended method of deploying the Agent Manager to a large number of Windows hosts is to use a software deployment tool such as Microsoft® Systems Management Center.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating