Filter
Top Products
Chapter 5. Troubleshooting techniques 165
03/02/12 15:01:56 0 1144 Maximum log size 1 (MB)
03/02/12 15:01:56 3 1144 FSR0001W Gateway Proxy Started
03/02/12 15:01:56 0 1144 gateway port 9494
03/02/12 15:01:56 0 1144 Using 0.0.0.0 for gateway interface
03/02/12 15:01:56 0 1144 TCP/IP timeout 240
03/02/12 15:01:56 0 1144 Gateway Proxy label tic01005-gw.
03/02/12 15:01:56 0 1144 Using default port range of 6000-8000
03/02/12 15:01:56 0 1144 max sessions 256
03/02/12 15:01:56 0 1144 Initializing the communication layer ...
03/02/12 15:01:56 3 1144 initRoutedSessionsManager: no network card specified
for parent-local-host, using random interface
03/02/12 15:02:07 3 1828 routingManager: WHO command received [l=null]
03/02/12 15:02:07 3 1828 routingManager: TELL reply command received
03/02/12 15:02:07 0 1144 Communication layer initialized
03/02/12 15:02:07 3 1144 Run Gateway listener (on Gateway port = 9494)
03/02/12 15:02:07 3 1144 Run UDP listener (on Gateway port = 9494)
03/02/12 15:02:07 0 1144 Gateway Proxy initialization successfully completed
The Gateway Proxy.log file shows that the Gateway Proxy is communicating
with the Endpoint Proxy. So until now, everything seems to be working from
Framework point of view.
3. Now we need to check what happens at Controller and Target Proxy level,
and if the two Proxies have communication problems.
First we look to see if the services are up and running, and we notice that the
RC Target Proxy is down.
Example 5-12, Example 5-13, and Example 5-14, respectively, show the
Target Proxy, Relay, and Controller Proxy log files when there is a session
startup failure caused by the Target Proxy service being down.
Example 5-12 The Target Proxy log file
03/02/12 15:06:53 3 1760 logInit - Message logging initialized (level=3,
logmax=1MB).
03/02/12 15:06:54 1 1760 sendCommandLineRequest: cannot connect to
127.0.0.1:3333
03/02/12 15:06:54 0 1760 Proxy label: none (node is root)
03/02/12 15:06:54 0 1760 Proxy type: target
03/02/12 15:06:54 2 1760 No listen interface specified, defaulting to
INADDY_ANY
03/02/12 15:06:54 0 1760 Proxy listen port: 5020
03/02/12 15:06:54 0 1760 TFST Endpoint Proxy directory: C:\Tivoli\Tivoli
Systems\Tivoli Endpoint Proxy
03/02/12 15:06:54 2 1760 No timeout specified, using default
03/02/12 15:06:54 0 1760 Communication timeout: 240
03/02/12 15:06:54 0 1760 Max sessions: 10
03/02/12 15:06:54 0 1760 Reply to RSM data: no