Filter
Top Products
Chapter 4. Implementation scenario: Tivoli Firewall Security Toolbox 119
For our testing we used the following products and release levels:
Operating systems:
– IBM AIX 5.1
– Microsoft Windows 2000 Advanced Server
– Microsoft Windows 2000 Professional
Tivoli Software:
– IBM Tivoli Management Framework 4.1
– IBM Tivoli Remote Control 3.8
– Tivoli Firewall Security Toolbox 1.3
We interconnected the Hub and Spoke TMR, using a two-way connection, and
exchanged the following Tivoli resources:
Administrator (two-way)
AdministratorCollection (two-way)
ManagedNode (two-way)
Endpoint (two-way)
PolicyRegion (two-way)
ProfileManager (two-way)
EndpointManager (one-way, and only once from the Spoke to the HUB TMR)
For this scenario, we assume that all Administrators are on the more secure side
of our network. Therefore, the Remote Control Server is installed on both of the
TMR Servers; and one of the Endpoints in the more secure zone will be the
Remote Control Controller. The Administrators need to have remote Control
access to the Endpoint located in the less secure zone.
Figure 4-2 shows how we implemented the Remote Control Proxy technology
based on the existing TFST configuration.
Note: We have not exchanged the Remote Control resource because, in our
scenario, there are no controllers connected to the HUB TMR.