Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring RMON Alarms and Events

To configure RMON alarms and events using the CLI, perform these tasks:

1. Configuring SNMP
2. Configuring an Event
3. Configuring an Alarm

Configuring SNMP

1. Grant read-only access to all SNMP clients:
   [edit snmp]
user@switch# set community community-name authorization authorization

   For example:

   [edit snmp]
user@switch# set community public authorization read-only
2. Grant read-write access to the RMON and jnx-rmon MIBs:
   [edit snmp]
user@switch# set view view-name oid object-identifier include
user@switch# set view view-name oid object-identifier include
user@switch# set community community-name authorization authorization view view-name

   For example:

   [edit snmp]
user@switch# set view rmon-mib-view oid .1.3.6.1.2.1.16 include
user@switch# set view rmon-mib-view oid .1.3.6.1.4.1.2636.13 include
user@switch# set community private authorization read-write view rmon-mib-view

   OIDs 1.3.6.1.2.1.16 and 1.3.6.1.4.1.2636.13 correspond to the RMON and jnxRmon MIBs.

3. Configure an SNMP trap group:
   [edit snmp]
user@switch# set trap-group group-name categories category
user@switch# set trap-group group-name targets address

   For example:

   [edit snmp]
user@switch# set trap-group rmon-trap-group categories rmon-alarm
user@switch# set trap-group rmon-trap-group targets 192.168.5.5

   The trap group rmon-trap-group is configured to send RMON traps to 192.168.5.5.

Configuring an Event

1. Configure an event index, community name, and type:
   [edit snmp rmon]
user@switch# set event index community community-name typetype

   For example:

   [edit snmp rmon]
user@switch# set event 1 community rmon-trap-group type log-and-trap

   The event community corresponds to the SNMP trap group and is not the same as an SNMP community. This event generates an SNMP trap and adds an entry to the logTable in the RMON MIB.

2. Configure a description for the event:
   [edit snmp rmon]
user@switch# set event index description description

   For example:

   [edit snmp rmon]
user@switch# set event 1 description “rmon event”

Configuring an Alarm

1. Configure an alarm index, the variable to monitor, the rising and falling thresholds, and the corresponding rising and falling events:
   [edit snmp rmon]
user@switch# set alarm index variable oid-variable falling-threshold integer rising-threshold integer rising-event-index index falling-event-index index

   For example:

   [edit snmp rmon]
user@switch# set alarm 5 variable .1.3.6.1.4.1.2636.3.1.13.1.8.9.1.0.0 falling-threshold 75 rising-threshold 90 rising-event-index 1 falling-event-index 1

   The variable .1.3.6.1.4.1.2636.3.1.13.1.8.9.1.0.0 corresponds to the jnxRmon MIB object jnxOperatingCPU, which represents the CPU utilization of the Routing Engine. The falling and rising threshold integers are 75 and 90. The rising and falling events both generate the same event (event index 1).

2. Configure the sample interval and type and the alarm type:
   [edit snmp rmon]
user@switch# set alarm index interval seconds sample-type (absolute-value | delta-value) startup-alarm (falling-alarm | rising-alarm | rising-or-falling-alarm)

   For example:

   [edit snmp rmon]
user@switch# set alarm 5 interval 30 sample-type absolute-value startup-alarm rising-or-falling-alarm

   The absolute value of the monitored variable is sampled every 30 seconds. The initial alarm can occur because of rising above the rising threshold or falling below the falling threshold.