Use this Knowledge Script on a version 8.0 proxy AppManager UNIX agent to install a version 8.0.11 agent on remote UNIX and Linux computers in your AppManager site.
You cannot use this Knowledge Script to install a version 7.5 or higher NetIQ UNIX agent.
To install the AppManager UNIX agent on a remote UNIX or Linux computer, the remote computer must be accessible through the network from the computer where the proxy AppManager UNIX agent is installed. This Knowledge 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 list to use Secure Shell instead. If you choose to use Telnet, you must supply a non-root user account name and password.
This Knowledge Script uses a version 8.1.0.11 AppManager UNIX agent as the proxy to install the version 8.1.0.11 AppManager UNIX agent on remote UNIX and Linux computers.
The proxy AppManager UNIX agent where you run this Knowledge Script must be configured to run as the root user account.
All of the computers where you want to install the AppManager UNIX agent using this Knowledge Script must be accessible using the same root user account information.
The failure messages associated with a scenario where you inadvertently tried to run with an invalid root user account password might 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 check to make sure you are using a valid root password.
If the .tar file or .ini file that you have 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 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 are removed from the directory.
When you run this Knowledge 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 fails and the Knowledge Script transfers the .tar file and never transfer the .ini file unless you make sure to list the .ini files first.
This Knowledge Script supports all platforms supported by the AppManager UNIX agent 7.0.1, with the following exceptions:
HP-UX in 32-bit and 64-bit mode is supported. Most AMAdminUNIX and UNIX Knowledge Scripts can run on HP-UX in 64-bit mode (because you can install and run the AppManager UNIX agent there). However, a computer running HP-UX in 64-bit mode cannot serve as a proxy.
Red Hat Advanced Server (AS) 3.0 on Opteron with 64-bit operating system is supported with the AppManager UNIX agent running in 32-bit mode.
Red Hat AS 3.0 on Itanium in 64-bit mode is supported.
A managed UNIX computer where the AppManager UNIX Agent 7.0.1 is installed. The AppManager UNIX agent must be configured to run as the root user account.
By default, this Knowledge Script is only run once on each proxy UNIX computer.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Event Notification Set parameters for event notification. |
|
|
Raise event if installation fails? |
Set to y to raise an event indicating that the installation has failed. By default, events are enabled. |
|
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. |
|
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. |
|
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 Knowledge Script can use SSH with root password authentication or Telnet to communicate with the remote managed computer. |
|
|
Password for root user account |
If you want to use Secure Shell (SSH) for the connection to the remote computers, make sure SSH with root authentication is enabled on the remote UNIX computers where you want to install the AppManager UNIX agent. For this parameter, you must specify the password for the root user to securely access the remote UNIX computers. This Knowledge Script does not support SSH root authentication with an RSA key. |
|
Connection Transport |
This Knowledge 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 Knowledge Script switches from the non-root user to the root user. |
|
Telnet non-root user 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 AppManager UNIX agent, and the location of installation tar package and the silent installation file. The simplest way to configure and run this Knowledge 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 simply specify the remote UNIX computers where you want to install the AppManager UNIX agent and the directory where the installation files are located. For installation .tar packages, the following naming convention applies:
For silent installation files, the following naming convention applies:
If you do not use these standard names, you must specify the directory path and filename. |
|
|
Full path to hosts file or comma-separated list of computers where agent should be installed |
Specify the computers you want by either:
This Knowledge Script attempts to install the AppManager UNIX agent on the first computer in the list. If an error occurs, or when the installation completes, the Knowledge Script attempts to install the AppManager UNIX agent on the next computer in the list. Tip To use this Knowledge Script to install the AppManager UNIX agent on multiple remote UNIX or Linux computers, all of the target computers must be using the same root password. |
|
Installation without Hosts File |
If you do not configure this Knowledge Script to use a hosts file, you must specify where the AppManager UNIX agent installation tar package and the silent installation file are located. |
|
Directory path to agent installation .tar package(s) |
If you have configured this Knowledge Script to use a hosts file, you do not need to configure this parameter. Enter the full path from the remote UNIX or Linux computer to the directory where the installation .tar package is located. For example: /usr/local/agt 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 have configured this Knowledge Script to use a hosts file, you do not need to configure 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 AppManager UNIX 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), enter the name of the silent installation file. If the silent installation file is not in the same directory as the installation .tar package, enter the directory path and name of the silent installation file. For example: /usr/local/agt/UnixClient-Linux.ini. |
|
Installation Destination Specify a temporary directory on the remote computer to store a copy of installation files. Note that if AppManager UNIX agent communication is authenticated and encrypted (security level 2), this Knowledge 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 the name of a temporary directory on the remote computer where you want to install the AppManager UNIX agent. This Knowledge Script copies the installation tar package and related files, such as the hosts file and the silent installation file to the temporary directory. Note that some operating systems have small /tmp directories, which can prevent this Knowledge Script from successfully copying the installation files and untarring the installation .tar package. For this reason, you can specify a directory other than /tmp. If the .tar file already exists in this directory, you see a failure the first time you run this Knowledge Script. See Section 6.2.1, Running this Knowledge Script, above, for more information. |
|
Installation command to run on the remote computer |
Type the full command to use to install the AppManager UNIX agent on the target computer. The default is UnixClient/netiq_agent_install. |
|
Event severity for internal failure |
Set the event severity level, from 1 to 40, to indicate the importance of an event if the maximum pool threshold is exceeded. The default is 5. |