| |
|
|
rmon alarm
Creates/deletes an RMON alarm on the current server.
Syntax: rmon alarm number variable interval {delta | absolute} rising-threshold rthreshold-value [event-number] falling-threshold fthreshold-value [event-number] [owner string]
no rmon alarm number
number
The number of the alarm you wish to create or delete.
variable
An object ID, by number or name, of the variable to be compared to the rising or falling threshold values during the period set by interval.
interval
The interval in seconds over which the data is sampled. Default: 15 seconds.
rthreshold-value
The setting for the rising threshold value.
fthreshold-value
The setting for the falling threshold value.
event-number
The number of the event generated by the cross of the rising or falling threshold value. Default: none.
string
A string that identifies the entity using the resources assigned to this alarm. Default: none.
Description: The remote monitor alarm task monitors system variables periodically to see if rising or falling thresholds have been crossed and outputs a user defined event when they do. The monitored variable is specified in the alarm. This command allows you to create or delete a remote monitor alarm that specifies the variable to be monitored, the monitoring period, the rising and falling thresholds that trigger a reporting event, and the event to output if a threshold is crossed. Remote Monitoring generates one event as a threshold is crossed in a given direction. No more events are generated for that threshold until the opposite threshold is crossed.
Each alarm is identified by a number. Use the next available alarm number when creating a new alarm. The show rmon alarms command displays all alarms in the host alarm table for this server and can be used to identify the next available number.
The variable can be any system object ID number or name you wish to monitor that resolves to an ASN.1 primitive type of INTEGER (INTEGER, Counter, Gauge, or TimeTicks). Each alarm can monitor a single system object. The alarm variable has both a prefix and suffix. The prefix specifies the object and the suffix specifies an instance of the object. Object descriptors are strings defined in the MIB for each OID. Instance descriptors are strings that identify a specific instance of an object. For example, 1/1/1/phy is the instance descriptor for the physical layer of an ifEntry whose interface is on bay 1, slot 1, port 1 of the Avici router. An alarm variable representing ifSpeed at the physical layer of an interface on bay 1, slot 1, port 1 can be specified as an OID 1.3.6.1.2.1.2.2.1.5.65537 or by object and instance descriptors ifSpeed.1/1/1/phy.
Table 12-1 enumerates instance descriptors used in the Avici router:
The interval is the period in seconds between samplings of the monitored variable.
You must specify whether the sample type is delta or absolute. The delta sample type subtracts the value from the beginning of the sample period from the value at the end of the period based upon two sample readings per period to provide for higher precision. In other words, only the delta between samples is given and an event is generated if that delta crosses the specified thresholds. The absolute sample type checks the absolute value at the end of the sample period and checks to see if the specified thesholds have been crossed. The sample type default value is delta.
The rising-threshold is a threshold for the sampled variable. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event, corresponding to the event-number specified in this alarm, is generated. After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the falling-threshold value.
The falling-threshold is a threshold for the sampled variable. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event, corresponding to the event-number specified in this alarm, is generated. After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the rising-threshold value.
Associate an event-number with one or both of this command's thresholds if you wish to generate an event when a threshold is crossed.
Use the owner string to identify the entity that owns the resources associated with this alarm.
Factory Default: None.
Command Mode: Configuration.
Example 1: The following example creates alarm 2, which is owned by the tsrMgr1 and monitors the variable ifSpeed absolute samples every 15 seconds. The rising threshold is 1200 and generates event 1 if crossed. 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-theshold 0 2
owner tsrMgr1
Example 2: 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
Related Commands: rmon event
show rmon alarms
show rmon events
| |
|
|
Copyright © 2005
Avici Systems Inc.
Avici® and TSR®
is a registered trademark of Avici Systems Inc.
IPriori™, Composite Links™, SSR™, QSR, and NSR® are
trademarks of Avici Systems Inc.
Source
File Name: RemMonCmds.fm
HTML File Name: RemMonCmds2.html
Last Updated: 02/25/05 at 14:31:31