Chapter 7. A case study 359
Applications
We use the following applications:
WebSphere Application Server Version 5.0 Base Edition
Peregrine ServiceCenter Version 4.0.4
WebSphere MQ 5.2 or 5.3 (IBM Tivoli Monitoring)
Java Runtime Environment (JRE) 1.3.1
7.1.2 Lab setup and diagram
This section looks at the layout of our lab environment. It includes a description of
the software that we install on each individual box. It discuses the network setup
and naming conventions.
Naming conventions
We use the following naming conventions:
The first three letters correspond to the location of the machine.
The next letter is either an A for AIX or W for a Windows operating system.
The next two characters correspond to that machine’s purpose. For Tivoli
machines, we use an abbreviation of the Tivoli software installed on the
machine. For endpoints, we specify whether they are an application server or
file server. The majority are application servers to host DB2, WebSphere MQ,
and WebSphere Application Server.
For the machines installed with Tivoli software, TC corresponds to IBM Tivoli
Enterprise Console, NW corresponds to Integrated TCP Service Component
in NetView, WS corresponds with WebSphere Application Server, and TF
corresponds to Tivoli Management Region (TMR) (Tivoli Framework).
The last two characters are a unique two-digit number for that machine.
For example, the first machine located in Raleigh, North Carolina, has Windows
2000 as its operating system and is used as a file server. It has the name
RDUWFS01.
Lab layout
Figure 7-1 shows the layout that we create in the ITSO lab for our case study and
testing purposes.
Note: Having a standard naming convention for your endpoints greatly
increases the ease of correlating events.
360 Event Management and Best Practices
Figure 7-1 Lab layout
Servers
We use a total of six AIX-based and six Intel-based servers. The following list
includes the names of these servers and their purpose. Refer to Figure 7-1 for
their location in the network.
The servers beginning with RDU located in Raleigh are:
– RDUARM01: This server hosts RemedyHelp Desk for trouble ticketing. A
DB2 database is also installed for Remedy’s use.
– RDUATC01: This server hosts the Focal Point IBM Tivoli Enterprise
Console. It has the UI server, RIM host, and a TMR installed. This server
also hosts an instance of DB2 for the use of the Focal Point IBM Tivoli
Enterprise Console.
Tier 2
Remedy
DB2
rs6000
AIX
m1097502
RDUARM01
TEC
TMR
UI_Server
RIM host
DB2
rs6000
AIX
m10df58f
RDUATC01
9.24.106.136 9.24.106.135
Tier 1
Entry Tier
Event Sources
Risk Manager Network
WebSphere
State Correlation
GW
xSeries 230
Windows 2000
m23vnx64
RDUWWS01
TMR
ITM
DB2
rs6000
AIX
m106244
RDUATF01
Endpoint w/
ITM
ACF
NetFinity 5100
Linux
m23x3078
MSPWAS01
Endpoint w/
ITM
ACF
300pl
Windows 2000
m23caaxy
SAPWAS02
Endpoint w/
ITM
ACF
rs6000
AIX
Venus
DTMAAS01
9.24.106.151 9.24.106.153
9.24.106.154
9.24.106.167
9.24.106.183
9.24.106.184
9.24.106.185
9.24.106.186
9.24.106.152
CISCO
S
YSTE M S
CISCO
S
YSTEMS
CIS CO SYSTEMS
9.24.106.164
9.24.106.168
9.24.106.180 9.24.106.181
9.24.106.130
9.24.106.145
CISCOSYSTEMS
9.24.106.131
CISCO
S
YSTEMS
Cisco 2600 Router
CISCOSYSTEMS
9.24.106.147
TEC
UI_Server
RIM host
rs6000
AIX
m10df5bf
RDUATC01
ITSC/NetView
ITSA
rs6000
AIX
m1083a6f
RDUANW01
9.24.106.161
9.24.106.161
CISCOSYSTEMS
Cisco 2600 Router
Endpoint w/
ITM
ACF
300pl
Windows 2000
m23caaac
PHIWAS01
9.24.106.177
9.24.106.146
CISC OSYSTEMS
9.24.106.179
Endpoint w/
ITM
ACF
300pl
Windows 2000
m23caaxp
DTMWAS01
Endpoint w/
ITM
ACF
NetFinity 5100
Linux
m23x2636
PHIWAS02
CIS CO
S
YSTEMS
9.24.106.163
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
• MSPWAS01
– Server beginning with SAP located in San Paulo, Brazil
•SAPWAS01
– Servers beginning with PHI located in Philadelphia, Pennsylvania
•PHIWAS01
•PHIWAS02
– Servers beginning with DTM located in Dortmund, Germany
• DTMAAS01
•DTMWAS01
Network components
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, 9.24.106.160, 9.24.106.176, 9.24.106.144, and
9.24.106.128. The main router rdur02 is connected to the Risk Manager Network
and connects the 9.24.106.160 and 176 networks.
In the 160 network, we have two switches: 9.24.106.163 and 9.24.106.164. 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.
Get Event Management and Best Practices now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
