IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual page 209

be myhost1.acme.north.prod.com. Inclusion of the network domain name causes
the agent name in the example above to expand to
SERVER1:myhost1.acme.north.prod.com:KXX. This resulting name is 39 characters
long. It is truncated to 32 characters resulting in the name
SERVER1:myhost1.acme.north.prod.
The agent name truncation is only a problem if there is more than one monitoring
agent on the same system. In this case, the agent name truncation can result in
collisions between agent products attempting to register using the same truncated
name value. When truncated agent names collide on the same system, this can lead
to Tivoli Enterprise Monitoring Server problems with corrupted EIB tables. The
agent name collision in the Tivoli Enterprise Monitoring Server might cause a
registered name to be associated with the wrong product.
In general, create names that are short but meaningful within your environment.
Use the following guidelines:
v Each name must be unique. One name cannot match another monitoring agent
name exactly.
v Each name must begin with an alpha character.
v Do not use blanks or special characters, including $, #, and @.
v Each name must be between 2 and 32 characters in length.
v Monitoring agent naming is case-sensitive on all operating systems.
Create the names by completing the following steps:
1. Open the configuration file for the monitoring agent, which is located in the
following path:
v On Windows: &install_dir;\tmaitm6\Kproduct_codeCMA.INI. For example,
the product code for the Monitoring Agent for Windows OS is NT and the
file name is KNTCMA.INI.
v On UNIX and Linux: /config/product_code.ini and product_code.config.
For example, the file names for the Monitoring Agent for UNIX OS are
ux.ini and ux.config.
2. Find the line the begins with CTIRA_HOSTNAME=.
3. Type a new name for host name that is a unique, shorter name for the host
computer. The final concatenated name including the subsystem name, new
host name, and agent code, cannot be longer than 32 characters.
Note: You must ensure that the resulting name is unique with respect to any
existing monitoring component that was previously registered with the
monitoring server.
4. Save the file.
5. Restart the agent.
6. If you do not find the files mentioned in Step 1, perform the workarounds
listed in the next paragraph.
If you do not find the files mentioned in the preceding steps, perform the
following workarounds:
1. Change CTIRA_HOSTNAME environment variable in the configuration file of the
monitoring agent.
v Find the KAGENT_CODEKENV file in the same path mentioned in the preceding
row.
v For z/OS agents, find the RKANPAR library.
Chapter 10. Monitoring agent troubleshooting
191