42 IBM Tivoli Remote Control Across Firewalls
In order to implement the Remote Control session to us e Remote Control
Proxies, the rc_def_proxy default policy method needs to be configured as
shown in Example 1-14 on page 38. This has t o be done in the Spoke TMR
where the Remote Control Object is located.
Tra cin g for RC Proxy StandaloneThe Tivoli methods used to start a session in a Remote Control Proxy
Standalone architecture are the same used to start a session in a non-secure
environment. Refer to Example 1-1 on page 16 for a subset of an IBM Tivoli
Management Framework odstat output trace file for a single-TMR architecture
and to the Example 1-6 on page 25 and Example 1-7 on page 25 for multi-TMR
architecture.
Sections “Tracing for single-TMR session” on page 16 and “Tracing for a
multi-TMR session” on page 24 provided the details of the most important
methods used to start a Remote Control ses sion both in a single-TMR and
multi-TMR architecture. As mentioned, the methods are almost the same to start
a Remote Control session in a secure environment. Thus, we only provide in this
section the main differences for the most important methods.
The Target request, managed by the remote_control method, remains the same
in a secure environment. For more information about this method, refer to
Example 1-2 on page 19 for a single-TMR architecture an d to Example 1-8 on
page 28 for a multi-TMR architecture.
Example 1-15 details the is_proxied_ep method started from either the TMR
Server in a single-TMR architecture or from the Spoke TMR Ser ver in a
multi-TMR architecture. It refers to the following line in Example1-7 on page 25:
1519322503.29.522+#TMF_Endpoint::Endpoint# is_proxied_ep
This method checks if the Target is behind an Endpoint Proxy/Gateway Proxy
architecture. If the result is true, Remote Control knows that an Endpoint Proxy
must be used to contact the Target. We see that the result of this method is
false; this means that the Target is not an Endpoint connected to a Gateway
Proxy.
As a reference, the following information is important to understand the content
of the examples:
The Target IP address is 10.10.10.7
The RC Target Proxy IP address is 9.3.4.169 and it is defined in the
rc_def_proxy policy file
The Controller IP address is 9.3.4.244