| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
TCP/IP Remote Network Monitoring (RMON) (Page 3 of 3) RMON Alarms, Events and Statistics Alarms and events are particularly useful constructs in RMON, as they allow the immediate communication of important information to a network management station. The administrator has full control over what conditions will cause an alarm to be sounded and how an event is generated. This includes specifying what variables or statistics to monitor, how often to check them, and what values will trigger an alarm. A log entry may also be recorded when an event occurs. If an event results in transmission of a trap message, the administrator will thus be notified and can decide how to respond, depending on the severity of the event. Like all MIB modules and groups, a particular manufacturer may decide which RMON groups to implement. However, certain groups are related, such as alarm and event, and some groups such as statistics are pretty much always implemented in all RMON probes. Obviously, when RMON is used, the network management station must be aware of RMON groups and must allow a network management application to be run that will exploit the capabilities of the RMON MIB objects.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||