Filter
Top Products
Chapter 4. Implementation scenario: Tivoli Firewall Security Toolbox 133
The wgetpolm and wputpolm commands are used to modify the rc_def_proxy
policy method settings. The procedure is similar to the process shown for the
Standalone case study scenario in Example 3-10 on page 107.
4.3.3 Remote Control Proxy startup
The process for starting the Remote Control Proxies was described in 3.3.4,
“Remote Control Proxy startup” on page 109 and is similar when installed on a
Non-Standalone environment. In this section we just provide the content of the
rcproxy.log file for both the RC Target and Controller Proxies. Since there is a
new instance of the Relay exclusive for the Remote Control communications, we
also provide the content of the Relay.log file. The highlighted lines on the
following examples show that the connections between the components
separated by a firewall have been established.
Example 4-7 shows the RC Target Proxy log file.
Example 4-7 The rcproxy.log: RC Target Proxy log file
03/02/13 10:49:24 3 2200 logInit - Message logging initialized (level=3,
logmax=1MB).
03/02/13 10:49:25 1 2200 sendCommandLineRequest: cannot connect to
127.0.0.1:3333
03/02/13 10:49:25 0 2200 Proxy label: none (node is root)
03/02/13 10:49:25 0 2200 Proxy type: Target
03/02/13 10:49:25 2 2200 No listen interface specified, defaulting to
INADDY_ANY
03/02/13 10:49:25 0 2200 Proxy listen port: 5020
03/02/13 10:49:25 0 2200 TFST Endpoint Proxy directory: C:\Tivoli\Tivoli
Systems\Tivoli Endpoint Proxy
03/02/13 10:49:25 2 2200 No timeout specified, using default
03/02/13 10:49:25 0 2200 Communication timeout: 240
03/02/13 10:49:25 0 2200 Max sessions: 10
03/02/13 10:49:25 0 2200 Reply to RSM data: no
03/02/13 10:49:25 3 2200 initRoutedSessionsManager: no network card specified
for Children-local-host, using random interface
03/02/13 10:49:25 2 2200 initRoutedSessionsManager: Children-remote-file
parameter not specified
03/02/13 10:49:25 3 2168 routingManager: TELL command received
[l=tic01005-gw]
03/02/13 10:49:25 3 2168 routingManager: WHO reply command received
[l=tic01005-gw]
03/02/13 10:49:25 3 2168 routingManager: TELL command received
[l=tic01005-gw]