Chapter 7. A case study 361
– RDUWWS01: This server hosts a WebSphere server for the IBM Tivoli
Enterprise Console Web Console. It is installed with a gateway to run the
IBM Tivoli Enterprise Console Gateway Process and state correlation.
– RDUATF01: This server hosts another TMR for the use of the lower-level
IBM Tivoli Enterprise Console. IBM Tivoli Monitoring is installed on this
TMR. An instance of DB2 is installed for the lower-level IBM Tivoli
Enterprise Console server’s use.
– RDUATC01: This server hosts the lower-level IBM Tivoli Enterprise
Console. It also has the UI server and RIM host installed.
– RDUANW01: This server hosts Integrated TCP Service Component in
NetView as well as IBM Tivoli Switch Analyzer.
The following servers are used for an endpoint with IBM Tivoli Monitoring
Resource Models and ACF Logfile Adapters running at each site:
– Server starting with MSP for Minneapolis, Minnesota
– Server beginning with SAP located in San Paulo, Brazil
– Servers beginning with PHI located in Philadelphia, Pennsylvania
– Servers beginning with DTM located in Dortmund, Germany
We use a combination of one Cisco 2600 router, one Cisco 3600 router, and
seven switches. Our main router, the Cisco 3600, is named rdur02. The 2600
router is named rdur01. For our purposes, here we refer to our switches by their
IP address. Refer to Figure 7-1 for the general layout.
Our lab has four networks, 126.96.36.199, 188.8.131.52, 184.108.40.206, and
220.127.116.11. The main router rdur02 is connected to the Risk Manager Network
and connects the 18.104.22.168 and 176 networks.
In the 160 network, we have two switches: 22.214.171.124 and 126.96.36.199. The
164 is cascaded off of the 163, and the 163 is connected to rdur02. Both
switches on this network have one server connected to them.
Note: These PHI servers are a Linux cluster.