Understanding RMON Alarms and Events Configuration

[Contents] [Prev] [Next] [Index] [Report an Error]

The JUNOS software supports monitoring routers from remote devices. These values are measured against thresholds and trigger events when the thresholds are crossed. You configure remote monitoring (RMON) alarm and event entries to monitor the value of a Management Information Base (MIB) object.

For more information on configuring RMON alarm and event entries, see Configuring RMON Alarms and Events and Summary of RMON Alarm and Event Configuration Statements.

For more information on monitoring integer-valued MIB objects, see Monitoring RMON Alarms and Events.

To configure RMON alarm and event entries, you include statements at the [edit snmp] hierarchy level of the configuration:



[edit snmp]

rmon {



alarm index {

description text-description;

falling-event-index index;

falling-threshold integer;

falling-threshold-interval seconds;

interval seconds;

rising-event-index index;

rising-threshold integer;

request-type (get-next-request | get-request
| walk-request);

sample-type (absolute-value | delta-value);

startup-alarm (falling-alarm | rising-alarm
| rising-or-falling-alarm);

syslog-subtag syslog-subtag;

variable oid-variable;



event index {

community community-name;

description description;

type type;
}


}


}

This topic also describes the minimum required RMON alarm and event configuration:

Minimum RMON Alarm and Event Entry Configuration

Minimum RMON Alarm and Event Entry Configuration

To enable RMON on the router, you must configure an alarm entry and an event entry. To do this, include the following statements at the [edit snmp rmon] hierarchy level:



[edit snmp rmon]
alarm index {

rising-event-index index;

rising-threshold integer;

sample-type type;

variable oid-variable;
}

event index;

[Contents] [Prev] [Next] [Index] [Report an Error]