362 Event Management and Best Practices
In the 176 network, there are three switches: 184.108.40.206, 220.127.116.11, and
18.104.22.168. The 180 and 181 are cascaded off of the 179, and the 179 is
connected to rdur01. Switch 179 has two servers connected to it. The other two
switches have one server connected to them.
In the 144 network, we have one switch 22.214.171.124. This switch is between
rdur01 and rdur02 and has four servers connected to it.
In the 128 network, we have one switch 126.96.36.199. This switch is connected
to rdur01 and has two servers connected to it.
7.1.3 Reasons for lab layout and best practices
We set up our lab to try to test most situations that customers would configure in
their networks. In this section, we discuss the reasoning behind our lab layout
and the positioning of the IBM Tivoli software.
We are limited to the amount of networking hardware and the type of network
hardware available to the ITSO at the time of running the lab. We acquire and
use two Cisco routers (one 3600 and one 2600) and seven Cisco Catalyst 1900
We position our network to try to create as many situations as possible in this
limited test environment. First we divide our lab into four networks, one for each
location that we specify. Our locations here represent virtual geographical
locations. This assists us with using locations to separate each network event.
Another goal we accomplish is to cascade at least one network switch off of
another network switch. This determines whether IBM Tivoli Switch Analyzer
recognizes a failure on the cascaded switch and forwards the event to NetView.
For this same reason, we locate a switch between our main and secondary
router. In addition, we use our limited network hardware to include at least one
switch in each of our virtual geographic network locations.
In conjunction with our network layout, we locate at least one machine in each of
our four locations. The servers at each location represent servers that run
business critical applications. Again, we use this configuration to assist with
event management and event source location. This type of information is
invaluable when working specifically on correlation and other event management