Cisco Cisco Workload Automation 6.3 Installation Guide

Page of 194
135
 
Installing Agents
Troubleshooting Agent Issues
INCLUDE - only the specified Masters with optionally specified IP addresses will be connected to by the Agent.
EXCLUDE - the specified Masters will be specifically excluded from being connected to by the Agent.
Master entries of the form:
MasterAlias
The MasterAlias typically has the form 'ES_<hostname of master>_1' and is case-insensitive. If specified alone on 
the line, then only the MasterAlias will be verified that it matches what was presented by the Master in its registration 
message.
MasterAlias:IPaddress1
For connections that are 'local', i.e. their Master host machine IP addresses are directly accessible by the Agent, 
then only IPaddress1 needs to be specified. This address will be verified against the IP address presented by the 
Master in its registration message and the IP address obtained from the network as the origination of the connection 
that provided the registration message.
MasterAlias:IPaddress1;IPaddress2
For connections that must traverse a firewall, then IPaddress2 must be specified.  IPaddress2 will be the externally 
known address of the firewall.  The externally known address of the firewall is what will be obtained by the Agent 
when it retrieves the IP address of the origination of the connection through which the registration message was 
delivered .
For situations where a Master could have multiple IPs, Failover scenarios, or disaster recovery situations, the same 
MasterAlias can be specified with different IPaddress parameters.
Here is an example of a Masters.cfg file:
INCLUDE                                      
hou-testvm-531:192.168.48.111;172.19.25.125 
hou-testvm-531:192.168.55.211;172.19.25.125
zostest:192.168.95.92          
zostest:192.168.42.92           
catest
Troubleshooting Agent Issues
When the Agent for Windows or Unix generates errors and doesn’t operate properly, you need to contact Technical 
Services to help you resolve the technical issues. However, Technical Services requires specific information on how the 
Agent is operating before they can track down the source of the problem. Before contacting Technical Services about 
an agent issue, you should verify the agent version and turn on diagnostic logging to collect information about the way 
the agent is functioning. These are the first steps that Technical Services will have you do, if you have not done it before 
contacting them. 
Troubleshooting a Unix Agent that Fails to Start
If your Unix agent fails to start or hangs on the following message:
TIDAL Agent for UNIX
Starting agent testagent on port 5912
Opening Connection......
...there might be no logs to troubleshoot. Typically, this problem is caused by an IP address mismatch. Follow the 
procedure below to check the IP address definitions.