NOTE:This Knowledge Script is obsolete as of AppManager version 7.0. You can still run this Knowledge Script on a proxy computer where the Windows agent is running to install the UNIX agent, version 6.x, on remote UNIX and Linux computers in your AppManager site.
The proxy computer where you run this script must configured with the following:
AppManager, version 6.0.2 or later
UNIX proxy components, version 6.5 or later
See the NetIQ Web site for information about downloading the latest AppManager components.
This script can use either the Secure Shell (SSH) program with root password authentication or Telnet to make a secure connection to the remote UNIX or Linux computer. By default, Telnet is used, but you can select SSH/SFTP from the Connection Transport parameter to use Secure Shell instead. If you use Telnet, supply a non-root user account name and password.
This script uses a silent installation file to specify how to install the UNIX agent and application monitoring support. You must manually create this file. For more information, see the AMAdminUNIX_AgentInstallProxy Knowledge Script. To update the AppManagerUNIX agent, currently installed managed objects, and the managed client’s local repository, use the AMAdminUNIX_AgentUpdate Knowledge Script.
You should use this script if you want to:
Install the agent for the first time on a remote UNIX or Linux computer.
Perform a fresh installation of the UNIX agent on an existing managed client, for example, if you do not want to preserve existing events, data, and jobs or if you want to use new information.
Install application monitoring support on the UNIX agent, version 6.5 or later.
For the job to succeed, the remote UNIX computer must be accessible through the network from the management server computer. All of the computers where you want to install the UNIX agent must be accessible using the same root user account information.
To enable this script, you must run the AppManager installation program (the AM602_UNIX_setup.exe file) on the proxy computer. An extra “helper” file will be installed (UnixAgentInstallProxy.exe).
NOTE:If you ran this script to remotely install the UNIX agent and want to run it again—to install additional application-monitoring support, for example—you must restart the UNIX agent on the remote computer. This script cannot be run on the same remote UNIX computer more than once without first restarting the UNIX agent.
If you attempt to install the UNIX agent on more than one computer, this script attempts to install the agent on the first computer in the list. If an error occurs, or when the installation completes, the script attempts to install the agent on the next computer in the list.
The failure messages associated with a scenario in which you inadvertently tried to run with an invalid root user account password may not clearly state this fact. If you see a failure that states, for example, “Cannot switch to root user on [X computer],” “Permission denied at UnixAgentInstallProxy.pl line X,” “unable to get a session to start the Installation,” or “Unable to get a session to start the Installation for [X computer],” first ensure you are using a valid root password.
If the .tar file or .ini file that you specified for the Installation Source Configuration parameter (that is, the file that you intend to use for the installation on a remote computer) already exists in the directory you listed for the Temporary directory on the remote computer parameter, you will see a failure. The event states, “Can't FTP File <File Name>: permission denied.” If this occurs, run the job again. After the initial failure, the .tar or .ini files will have been removed from the directory.
When you run this script using a hosts file, the hosts file should list any file locations of .ini files before it lists locations of .tar files. The job will fail and the script will transfer the .tar file and never transfer the .ini file unless you make sure to list the .ini files first.
To successfully run the UnixAgentInstallProxy Knowledge Script, provide the paths and filenames of the .tar, .ini, and hosts files with no blank spaces.
The following are examples of file paths containing blank spaces that will cause the script job to fail:
c:\Remote Install\ClientInstall.txt c:\RemoteInstall\Client Install.txt c:\Remote Install\UnixClient-solaris.tar c:\RemoteInstall\Unix Client-solaris.tar c:\Remote Install\UnixClient-solaris.ini c:\RemoteInstall\Unix Client-solaris.ini
The following are examples of file paths that will allow for a successful installation using this script. They contain no blank spaces in paths or filenames:
c:\RemoteInstall\ClientInstall.txt c:\RemoteInstall\UnixClient-solaris.tar c:\RemoteInstall\UnixClient-solaris.ini
AppManager, version 6.0.2 or later, with version 6.5 (or later) UNIX proxy components. You should not run this script on the management server.
The default interval for this script is Run once.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Event Notification |
|
|
Raise event if installation fails? |
Set to y to raise an event indicating that the installation has failed. The default is y. |
|
Event severity when installation fails |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 10 (red event indicator). |
|
Raise event if installation succeeds? |
Set to y to raise an event indicating that the installation is complete and has succeeded.The default is y. |
|
Event severity when installation succeeds |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 25 (blue event indicator). |
|
Remote Host Connection Configure access to the remote managed computers by specifying their root password. All of the remote computers must use the same root password. This script can use SSH with root password authentication or Telnet to communicate with the remote managed computer. |
|
|
Password for root user account |
To use Secure Shell (SSH) for the connection to the remote computers, ensure SSH with root authentication is enabled on the remote UNIX computers where you want to install the UNIX agent. For this parameter, you must specify the password for the root user to securely access the remote UNIX computers. This script does not support SSH root authentication with an RSA key. |
|
Connection Transport |
This script can use SSH with root password authentication or Telnet to communicate with the remote managed computer. If you select the Telnet/FTP option (the default), the Telnet prompt on the remote computer must end with a space or one of the following characters: % > # $ Here is an example of a supported Telnet prompt: user@hostname> Here is an example of an unsupported Telnet prompt: <user@hostname:/tmp - 2005-Mar-09> -> In the example above, the last character in the first line of the 2-line prompt is a line feed character, which is not supported. |
|
Telnet non-root user account |
If you selected Telnet to connect to the remote UNIX computers, specify a non-root user account to use for the connection. When connecting to a remote UNIX computer using Telnet and FTP, this script switches from the non-root user to the root user. |
|
Telnet non-root user account password |
If you selected Telnet as the connection transport medium, specify the password for the non-root user account to connect to the remote UNIX computers. |
|
Installation Source Configuration Set parameters to specify the remote computers where you want to install the UNIX agent, and the location of installation tar package and the silent installation file. The simplest way to configure and run this script is to store the installation tar packages and the silent installation files in the same directory using the standard naming convention. If these files are in the same directory and use the standard naming convention, you can configure this script to simply specify the remote UNIX computers where you want to install the UNIX agent, and the directory where the installation files are located. For installation tar packages, the following naming convention applies: - UnixClient-aix.tar for IBM AIX 5.1, 5.2, or 5.3 on IBM Power (32-bit agent) - UnixClient-hpux.tar for HP-UX 11.0, 11.1x, or 11.23 on PA-RISC (32-bit agent) - UnixClient-hpux_ia64.tar for HP-UX 11iv2 (11.23) on Intel Itanium (64-bit agent) - UnixClient-linux.tar for Red Hat AS 2.1, 3.0, or 4 and SuSe 8 or 9 on x86 and AMD Opteron (32-bit agent) - UnixClient-linux64.tar for Red Hat AS 3.0 on Intel Itanium (64-bit agent) - UnixClient-solaris.tar for Sun Solaris 8, 9, or 10 on SPARC (32-bit agent) For silent installation files, the following naming convention applies: - UnixClient-aix.ini for IBM AIX 5.1, 5.2, or 5.3 on IBM Power (32-bit agent) - UnixClient-hpux.ini for HP-UX 11.0, 11.1x, or 11.23 on PA-RISC (32-bit agent) - UnixClient-hpux_ia64.ini for HP-UX 11iv2 (11.23) on Intel Itanium (64-bit agent) - UnixClient-linux.ini for Red Hat AS 2.1, 3.0, or 4 and SuSe 8 or 9 on x86 and AMD Opteron (32-bit agent) - UnixClient-linux64.ini for Red Hat AS 3.0 on Intel Itanium (64-bit agent) - UnixClient-solaris.ini for Sun Solaris 8, 9, or 10 on SPARC (32-bit agent) If you do not use these standard names, you must specify the file path and filename. |
|
|
Full path to hosts file or list of computers where agent should be installed |
Specify the computers you want by doing one of the following: Entering the path and name of the hosts file that contains a list of the remote managed UNIX computers you want. For example, type d:\appmgr\agtinstalltarget. This option enables you to configure different installation .tar packages and silent installation files for each computer. In the hosts file, list each hostname on a new line, for example: labuws202::d:\agt\ua-usr.ini::d:\agt\UnixClient-linux.tar where: labuws202 is the name of computer where you want to install the UNIX agent d:\agt\ua-usr.ini is the file path to the silent installation file d:\agt\UnixClient-linux.tar is the file path to the agent installation package. The following .tar files are available: - UnixClient-aix.tar for IBM AIX 5.1, 5.2, or 5.3 on IBM Power (32-bit agent) - UnixClient-hpux.tar for HP-UX 11.0, 11.1x, or 11.23 on PA-RISC (32-bit agent) - UnixClient-hpux_ia64.tar for HP-UX 11iv2 (11.23) on Intel Itanium (64-bit agent) - UnixClient-linux.tar for Red Hat AS 2.1, 3.0, or 4 and SuSe 8 or 9 on x86 and AMD Opteron (32-bit agent) - UnixClient-linux64.tar for Red Hat AS 3.0 on Intel Itanium (64-bit agent) - UnixClient-solaris.tar for Sun Solaris 8, 9, or 10 on SPARC (32-bit agent) Tips To comment out a line in the hosts file, use a # character. The hosts file should list any file locations of .tar files before it lists locations of .ini files. Specifying a comma-separated list of UNIX computers. If you specify the list of computers in this script (instead of using a hosts file), you must also configure this script to specify the name and location of the silent installation file and the installation tar package. Note that all the computers in the list must be installed using the same installation .tar package and silent installation file. |
|
Installation without Hosts File |
If you do not configure this script to use a hosts file, you must specify where the agent installation .tar package and the silent installation file are located. |
|
Directory path to agent installation .tar package(s) |
If you configured this script to use a hosts file, you do not need to configure this parameter. Provide the full path from the remote UNIX computer to the directory where the installation .tar package is located. For example: d:\tarball_location You do not need to specify the name of the installation tar package if the name of the installation tar package follows the naming convention. If the name of the file does not follow the naming convention, you must specify the path and filename. |
|
Name of silent installation file |
If you configured this script to use a hosts file, you do not need to set this parameter. You do not need to configure this parameter if the name of the silent installation file follows the naming convention and the silent installation file is located in the same directory as the agent installation .tar package. If the name of the silent installation file does not follow the convention (but it is in the same directory as the installation package), provide the name of the silent installation file. If the silent installation file is not in the same directory as the installation .tar package, provide the directory path and name of the silent installation file. For example: d:\agent_cfg\Linux.ini. |
|
Installation Destination Specify a temporary directory on the remote computer to store a copy of installation files. Note that if UNIX agent communication is authenticated and encrypted (security level 2), this script does not copy the security key with the installation files. Make sure that the remote UNIX computer can access the key file according to the location specified in the silent installation file. |
|
|
Temporary directory on the remote computer |
Specify a temporary directory on the remote computer where you want to install the UNIX agent. The script copies the installation .tar package and related files, such as the hosts file and the silent installation file to the temporary directory. NOTE:Some operating systems have small /tmp directories, which can prevent this script from successfully copying the installation files and untarring the installation .tar package. For this reason, you can specify another directory. If the .tar file already exists in this directory, you will see a failure the first time you run this script. |
|
Installation command to run on the remote computer |
Specify the command you want to run. The default command, netiq_agent_install, installs the agent and any managed objects as specified in the silent installation file. Note that you do not need to specify the -s option to run the silent installation. You can also use this script to configure another command, for example, netiq_component_install, to install monitoring support for a particular application on an existing UNIX agent. |