| |
|
|
This chapter describes the configuration of remote monitoring on the Avici router.
The Remote Monitor
Remote monitor (RMON) on the Avici router provides for the sampling of MIB objects defined in alarm entries against rising and falling thresholds generating outputs defined in the associated event entries. This chapter provides an introductory overview RMON, followed by the details for creating, deleting, and displaying alarms and events.
Introduction
The remote monitor implements the alarm and event groups specified in RFC-1757. When a threshold is crossed, RMON generates an alarm that is optionally logged to the log table, or sends a trap to a specified SNMP community. The sampling threshold type can either be delta or absolute. Type delta samples the change in object value between the beginning and end of the sample period; type absolute samples the actual value of the object at the end of the sample period.
You can enable or disable RMON on any platform: module, server, and bay. RMON is enabled on all platforms by default. Disabling RMON does not cause the deletion of alarm or event entries.
There are two parts to configuring the remote monitor to monitor a MIB object: the creation of an alarm and the events associated with the rising and falling thresholds.
An event defines the action taken when a threshold is crossed. An event contains the following fields: an event index number identifying the event, a description field that allows you to specify the nature of the event, and an owner field that allows you to define the resource ownership and contact information associated with the event. When creating an event you can optionally specify whether RMON should log events to the log file, trap events to a specified SNMP community, both, or none. If you configure events for no action, a log message is sent to the log subsystem.
An alarm defines the MIB object to monitor and the criteria that will cause an alarm. An alarm contains the following fields: a number ID identifying the alarm, an object ID that specifies the system object to sample, the period between samples, the sample type, the rising and falling threshold values along with the event number associated with each threshold type, and an owner description that specifies the resource owner or contact information associated with the alarm.
You optionally create an event first and then associate it with an alarm. The event ID provides for the association between the alarm threshold defined in the alarm entry and the event generated as a result of the threshold crossing. If an event is not defined for an alarm threshold, the default behavior logs the alarm information to the logging system. Show commands are available that list all alarms and events in the Avici router.
Enabling and Disabling Remote Monitor
Remote monitor can be enabled or disabled per platform: module, server, or bay. You use the rmon enable command to enable RMON. Use of this command without any options enables RMON on all platforms. Using the module, server, or bay option with this command allows remote monitor enabling on all platforms of the specified type or to a particular specified platform.
Use the no option along with any variant of this command to disable remote monitor for the specified platform(s).
IPriori enables RMON on all platforms by default.
Creating and deleting remote monitor events
To create an event that can be associated with one or more alarms use the rmon event command.
You must specify an ID number for the event. Use the show rmon events command to display all active remote monitor events. Specify the next available number for the number variable. Use the log parameter to log this event to the log file. The trap parameter provides for sending a trap to the specified community. Insert a description of the event for the des-string variable. You can specify an owner and contact information using the owner-string variable. The description and ownership strings can be composed of any alpha-numeric characters.
The following example creates event 2, specifies that the event should be logged, contains a description "interface speed rising-threshold," indicating that the sampled object is the interface speed and that the rising threshold value for this object was either equaled or exceeded, and specifies that the resources are owned by tsrMgr1.
router#config terminal
Enter configuration commands, one per line. End with CNTL/Z
router(config)#rmon event 2 log description "interface speed rising-threshold" owner tsrMgr1
- The no rmon event command deletes the specified event.
The following example deletes event 2:
router#config terminal
Enter configuration commands, one per line. End with CNTL/Z
router(config)#no rmon event 2
Creating and deleting remote monitor alarms
A remote monitor alarm provides for the periodic sampling of a MIB object, by an ASN.1 formatted object ID or name, and the generation of an alarm and associated event if either the specified rising or falling threshold is crossed.
The alarm and its associated event is only generated the first time the threshold is crossed in the activating direction and will not activate again until the threshold has equaled or crossed the opposite threshold. For example, an alarm and its associated event is generated for a rising threshold when the sampled MIB object's value first equals or exceeds the configured threshold value. Another alarm associated with that threshold will not be generated until the sampled object's value equals or falls below the falling threshold configured for that alarm. Once this happens, a rising threshold alarm will generate the next time the object's value equals or exceeds the configured rising threshold value. The same is true for the alarm and event associated with the sampled object's falling threshold value. RFC-1757 details this hysteresis algorithm.
You use the rmon alarm command to configure remote monitor alarms.
You must specify an ID number for the alarm. Use the show rmon alarm command to display all active remote monitor alarms. Specify the next available number for the number variable. The variable field identifies the MIB object you want the alarm to monitor. This object must be an ASN.1 primitive type of INTEGER (INTEGER, Counter, Gauge, or TimeTicks). The variable field supports the identification of the MIB object by either object ID or name. The interval variable specifies the sample period in seconds. Use the show rmon value command to verify support for a given object.
There are two sample types. The delta sample type calculates the change in the object value between the beginning and end of the sample period based upon two sample readings per period, to provide for higher precision. The remote monitor task generates an alarm if the change is lower than or equal to the falling threshold specified for this command, or the change is higher than or equal to the rising threshold. Use the delta sample type when you want to monitor an object for the change in value over a specific period of time. The delta sample type is invalid for gauges. The absolute sample type compares the actual value of the sampled object at the end of the sample period against the configured rising and falling thresholds. If the value of the object is less than or equal to the falling threshold value, an alarm is generated. If the value of the object is greater than or equal to the rising threshold value, an alarm is generated.
The rising-threshold and falling-threshold parameters set the values that generate an alarm. You can associate an event with each of these parameters. An event provides a description field that allows you to more fully identify the circumstances that generated the alarm.
The owner parameter provides for up to 128 alpha-numeric characters for you to identify the owner of the object resources associated with this alarm.
The following example creates alarm 2, which is owned by the tsrMgr1 and monitors the MIB variable ifSpeed absolute samples every 15 seconds. The rising threshold is 1200 and generates event 1 if the object value exceeds 1200. The falling threshold is 800 and generates event 2 if crossed:
router#config terminal
Enter configuration commands, one per line. End with CNTL/Z
router(config)#rmon alarm 2 ifSpeed.1/1/1/phy 15 absolute rising-threshold 1200 1 falling-threshold 0 2 owner tsrMgr1
- The no rmon alarm command deletes the specified alarm.
The following example deletes alarm 2:
router#config terminal
Enter configuration commands, one per line. End with CNTL/Z
router(config)#no rmon alarm 2
Configuring Log Size
The maximum number of entries per event in the remote monitor log can be configured using the rmon log size command. Log entries are numbered from 1 to the maximum log size. Once the maximum log size is reached the oldest entry is deleted. The amount of system memory the log uses is a primary consideration in configuring the log size. The maximum number of entries in the log defaults to 200 entries per event.
Displaying remote monitor alarms and events
The following display commands are available for the remote monitor:
| |
|
|
Source
File Name: RemMonconfig.fm
HTML File Name: RemMonconfig.html
Last Updated: 05/30/02 at 13:54:40
Please email suggestions and comments to: doc@avici.com