After installation, you can change several options for the AppManager for UNIX components on the agent computer and the management server.
NOTE:If you use the AMAdminUNIX_SetPrimaryMS Knowledge Script to set a primary and secondary management server, this information is added to the NqmComms.xml file underneath $AM_HOME/netiq/AM/data/Config_X, where X is an integer.
When you install the UNIX agent, you identify a user account for the UNIX agent to use. This account effectively owns all of the AppManager files on the computer and handles your monitoring jobs. Depending on the permissions associated with the account, there might be a few limitations on the Knowledge Script jobs you can run. Most Knowledge Script functionality is enabled by the sudoers configuration file that extends non-root account access, but in rare cases, the root user or an admin group account might be able to access certain statistics that are not available to a normal user account.
You can change the account you use to run the UNIX agent using UNIX Agent Manager. Select the computer you want and click Configure > AppManager Options > Configure AM, then change the account in the Owner field.
By default, the computer you designate as a management server for UNIX listens on port number 9001. You have an opportunity to change that port number automatically, during agent installation. However, you can also change it manually after the agent has been installed.
To change the port number where the management server listens:
Click Start > Run, then type regedt32.exe to start the Registry Editor on the management server computer.
Open the HKLM\Software\NetIQ\AppManager\4.0\NetIQms registry key.
Click the UNIX Port value entry, then click Edit > DWORD.
Select the Decimal option to display the current value in decimal format.
Enter the new port number to use.
Click OK.
Restart the computer for this change to take effect.
After you change the registry entry for the Windows computer where the management server is installed, you also need to update the UNIX agent with this information. To do this, you need to edit the UNIX agent’s communications file, NqmComms.xml.
You can use UNIX Agent Manager to change the management server that a UNIX agent communicates with or the port number the management server listens on. Using UNIX Agent Manager, select the computer you want and click Configure > AppManager Options > Configure AM, then change the port in the Server Management area.
You can also use the AMAdminUNIX_SetPrimaryMS Knowledge Script to change the management server that a UNIX agent communicates with or the port number the management server listens on. This Knowledge Script allows you to specify a primary management server or a secondary management server by hostname and change the port number the management server listens on.
The heartbeat interval controls how frequently the UNIX agent communicates with the management server. In most environments, you do not need to modify the heartbeat interval. However, if you need to modify the heartbeat interval, modify the <HEARTBEAT>, <SCHEDULE>, and <INTERVAL> tags in the uaconf.xml configuration file in $AM_HOME/etc.
<HEARTBEAT>
<SCHEDULE>
<INTERVAL>30</INTERVAL>
</SCHEDULE>
</HEARTBEAT>
Set the interval to the number of seconds between agent heartbeat signals. Changing the UNIX agent heartbeat interval might require you to also adjust the UNIX Machine Check and UNIX Machine Timeout intervals on the management server. For example, if you set a longer heartbeat interval to conserve network bandwidth, you should lengthen the UNIX Machine Check and UNIX Machine Timeout intervals to prevent the UNIX agent from appearing to be unavailable between heartbeat signals. For information about changing the intervals on the management server, see the Administrator Guide for NetIQ AppManager.
By default, the management server records information about its operations in a log file on the computer designated as the management server.The log file, ms.log, is located in the NetIQ\Temp\NetIQ_debug\computer directory, where NetIQ is the AppManager installation path and computer is the name of the computer where the management server is installed. The directory for the log file is specified in the HKEY_LOCAL_MACHINE\Software\NetIQ\Generic\Tracing\TraceLogPath registry key.
Typically, the information in the log is not detailed. However, you can change the amount of information recorded in the log file by modifying a registry key.
To change the level of logging for the management server:
In the Registry Editor on the computer you are using as the management server., find the HKEY_LOCAL_MACHINE\Software\NetIQ\NetIQms\Tracing registry key. This key contains several entries for tracing management server activity. By default, all trace logs are enabled and set to record error and warning messages (values set to 1). Two of the entries, TraceSockets and TraceXml, trace communication between the management server and NetIQ UNIX agents.
|
Registry Entry |
Purpose |
|---|---|
|
TraceSockets |
Tracing of communication activity between the management server and AppManager UNIX agents. |
|
TraceXml |
Tracing of all the XML messages transferred to and from the UNIX agents. |
Click the Trace value entry that you want to change, then click Edit > DWORD.
Select the Decimal option to display the current value in decimal format.
Set the logging level to one of the following values:
|
Logging Level |
Description |
|---|---|
|
0 |
Disables trace logging for the selected type of activity. |
|
1 |
Minimal tracing. Errors and warnings are logged, but there are no informational messages. |
|
2 |
Minimal tracing with only limited informational messages. |
|
3 |
Medium level of tracing with more informative messages, including tracing of the communication with the UNIX agent. This is the default. |
|
4 |
More verbose informative messages. |
|
5 |
Most verbose tracing. |
Click OK.
The change does not require you to restart the computer or the NetIQms service.
Each line in the log file includes a time stamp in UTC format, a message type indicator, and the message body. For example:
987220342: info 1: computer name = MERCURY 987220342: info 1: host name = MERCURY 987220342: info 1: ip = 10.5.102.152 987220342: info 2: SocketServerThread, 2920 987220342: info 2: UnixAgentsThread, 3052 987220342: info 2: QUnixaConfigureThread, 2620
Two registry keys control how the management server determines the status of the NetIQ UNIX agents. The registry keys are under the HKEY_LOCAL_MACHINE\Software\NetIQ\AppManager\4.0\NetIQms\Config registry key on the management server computer.
Click the value entry for the queue you want to modify, then click Edit > DWORD.
|
Registry Key Entry |
Description |
|---|---|
|
UNIX Machine Check Interval |
Set the interval, in seconds, to control how often the management server checks the time of the last heartbeat signal from each of its UNIX agents. This registry key is used in conjunction with the UNIX Machine Timeout value to determine whether a UNIX server is available. If the management server has not received a heartbeat signal in the period specified as the UNIX Machine Timeout value, the UNIX agent is deemed unavailable. The default is 300 seconds. |
|
UNIX Machine Timeout |
Set the interval, in seconds, that identifies a UNIX agent as unavailable. If the UNIX agent does not send a heartbeat signal in this period of time, it is deemed unavailable. The default is 1200 seconds. |
Select the Decimal option to display the current value in decimal format.
Set the key value as appropriate for your environment.
Click OK.
This change requires you to restart the NetIQms service to take effect. To restart the NetIQms service, use the Services Control Panel.