References

Books

Leinwand, Allan and Karen Fang Conroy. Network Management: A Practical Perspective . Reading, MA: Addison-Wesley, 1996.

Stallings, William. SNMP, SNMPv2, and RMON , Second Edition. Reading, MA: Addison-Wesley, 1996.

Terplan, Kornel. Benchmarking for Effective Network Management . New York, NY: McGraw-Hill, 1995.

Terplan, Kornel. Communication Networks Management . Upper Saddle River, NJ: Prentice Hall, 1992.

Internet Resources

http://www.cisco.com/public/mibs/v1/CISCO-RTTMON-MIB-V1SMI.my

ftp://ftp.isi.edu/in-notes/rfc1757.txt (RMON) (page 16)

ftp://ftp.isi.edu/in-notes/rfc2021.txt (RMON)

ftp://ftp.isi.edu/in-notes/rfc2233.txt (Interfaces group )

Cisco IOS documentation

RFC 2275 http:// info .internet.isi.edu:80/in-notes/rfc/files/rfc2275.txt

Chapter 5. Configuring Events

As network administrators, we all want our network to be as reliable as possible. If the network develops a problem or is reaching capacity in some area, we want to know about it as soon as possible—preferably before users begin complaining.

Your network devices will report symptoms of problems by generating events. An event in this context is a message indicating that a device or application in your network has discovered something of note. Your network devices will generate many types of events automatically. In addition, you can use triggers to define or modify the conditions under which events are generated. Triggers are points of interest in specific data objects that generate events when these points are satisfied. A threshold is a type of trigger set on continuous data streams.

Now that you've baselined your network and started collecting performance data on that network, you have enough information to make sure that your network alerts you when things become abnormal. The steps you'll need to do this include the following:

• Determine what information is interesting and what states or levels are normal for your network.

• Evaluate the events your devices will automatically generate and make sure that the desired events are turned on and the undesired ones are turned off or filtered out.

• Define and configure methods to generate events that are not built-in.

The events generated need to be analyzed to determine whether they represent a fault condition or diagnosis of a problem in your network. This analysis is done by an event management system. This system then takes action on faults, such as notifying network operators about the fault, paging you, or just logging the fault to a file for later analysis. The process of analyzing events and processing faults is the subject of the next chapter, "Event and Fault Management."

This chapter covers the following topics:

• Types of generated events

• Controlling event generation

• Using built-in events

• Determining when you want events to be triggered

• Generating events using RMON by programming devices and collecting and analyzing data.