Question & Answer
Question
How can you troubleshoot a linking issue between a Tivoli Workload Scheduler (TWS) master and a Fault Tolerant Agent (FTA)?
Answer
To troubleshoot linking issues, check the following from the Unix prompt:
1. telnet [node] 31111 (if 31111 is the port being used)
2. ping [node]
3. nslookup for the FTA and the master (look for both on FTA and on the master), paying particular attention if the systems resolve the information the same way.
IMPORTANT NOTE: There must be two-way communication between the FTA and the master (or domain manager, if applicable).
4. netstat -a |grep 31111 (if 31111 is the port being used)
paying particular attention if any FIN_WAIT_2 states exist.
NOTE: On some operating systems, a connection in the FIN_WAIT_2 state will persist until the system is rebooted. If the system does not have a time-out and too many FIN_WAIT_2 connections build up, it can fill up the space allocated for storing information about the connections and crash the kernel. Consult your Unix administrator for assistance as this is an operating system issue.
5. verify that the port number of the master in the TWS database (CPU definition) matches the entry for "nm port" in the ~twshome/localopts file of the master. Use "cpuinfo master_workstation_name" from the Unix command prompt or from within conman to see port numbers defined in the database.
6. verify that the port number of the FTA (CPU definition) in the TWS database matches the entry for "nm port" in the ~twshome/localopts file of the FTA. Use "cpuinfo fta_workstation_name" from the Unix command prompt or from within conman to see port numbers defined in the database.
7. look over the netman and TWSMerge logs on both the master and FTA for errors. These are located under the ~twshome/stdlist/logs/ directory.
If this information does not provide the answers to the linking issue, call IBM Support for further assistance. Have the information gathered while troubleshooting available for the engineer working the PMR
NOTE: Any issues found performing steps 1-4 suggests that there are issues with the network or with DNS.
NOTE: Any issues found performing steps 5-7 suggests that there are issues with the TWS configuration or installation. If any changes are made in the TWS database to the CPU definitions, Jnextday (pre-v8.3) or JnextPlan (Final schedule) will need to run for the change to become effective.
Also, see Technote # 1156106 in the "Related information" section below for more network troubleshooting hints.
Related Information
Product Synonym
Maestro;TWS;TWA
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21193396