Example for Configuring RMON

Owned by Tracy Yang
Nov 28, 2023
4 min read

Networking Requirements

Figure 1. RMON Configuration Example

As shown in Figure 1, to monitor the LAN network connected to PICA8 Switch’s interface ge-1/1/1, RMON is enabled to achieve the following requirement:

  • Real-time and historical statistical information on traffic and the number of various types of packets.
  • Record a log when the flow rate per minute (MIB variable 1.3.6.1.2.1.16.1.1.1.4.1) exceeds the set threshold.
  • Monitor the broadcast and multicast traffic of this LAN subnet and report alarm messages to the NMS when exceeding the set threshold.

Configuration Roadmap

The RMON statistics function can be configured on PICA8 Switch to monitor real-time and history statistics of traffic and the number of various types of packets. Configuring RMON alarm function can record the log and actively report alarm information to NMS when the traffic exceeds the set threshold.

  1. Configure the IP address of the switch interface and route reachability on the network.
  2. Configure to allow Trap messages to be sent to the NMS.
  3. Enable the RMON ethernet statistics and history statistics function.
  4. Configure both RMON event definition function and alarm threshold setting function to achieve RMON alarm function.

Procedure

Step1         Configure the IP address of the switch interface.

admin@Switch# set interface gigabit-ethernet ge-1/1/1 family ethernet-switching port-mode trunk
admin@Switch# set interface gigabit-ethernet ge-1/1/1 family ethernet-switching native-vlan-id 10
admin@Switch# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching port-mode trunk
admin@Switch# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching native-vlan-id 20
admin@Switch# set vlans vlan-id 10 l3-interface vlan10
admin@Switch# set vlans vlan-id 20 l3-interface vlan20
admin@Switch# set l3-interface vlan-interface vlan10 address 192.168.1.10 prefix-length 24
admin@Switch# set l3-interface vlan-interface vlan20 address 192.168.2.1 prefix-length 24

Step2         Configure route reachability on the network.

admin@Switch# set protocols ospf router-id 1.1.1.1
admin@Switch# set protocols ospf area 0
admin@Switch# set protocols ospf network 192.168.1.0/24 area 0
admin@Switch# set protocols ospf network 192.168.2.0/24 area 0
admin@Switch# set ip routing enable true

Step3         Enable SNMP trap.

admin@Switch# set l3-interface loopback lo address 192.168.3.30 prefix-length 32
admin@Switch# set protocols snmp community Pica8-data-center
admin@Switch# set protocols snmp trap-group targets 192.168.3.1 security-name Pica8-data-center
admin@Switch# set protocols snmp trap-group source-interface loopback

Step4         Configure RMON ethernet statistics and history statistics.

admin@Switch# set protocols snmp rmon statistics 1 interface ge-1/1/2
admin@Switch# set protocols snmp rmon statistics 1 owner owner_pica8
admin@Switch# set protocols snmp rmon history 1 interface ge-1/1/2
admin@Switch# set protocols snmp rmon history 1 owner owner_pica8

Step5         Configure RMON event type to log and trap.

admin@Switch# set protocols snmp rmon event 1 type log-trap
admin@Switch# set protocols snmp rmon event 1 community Pica8-data-center
admin@Switch# set protocols snmp rmon event 1 description test
admin@Switch# set protocols snmp rmon event 1 owner public

Step6         Configure RMON alarm to monitor MIB variable 1.3.6.1.2.1.16.1.1.1.4.1, and the rising threshold to 600, falling threshold to 400.

admin@Switch# set protocols snmp rmon alarm 1 variable 1.3.6.1.2.1.16.1.1.1.4.1
admin@Switch# set protocols snmp rmon alarm 1 interval 20
admin@Switch# set protocols snmp rmon alarm 1 sample-type delta
admin@Switch# set protocols snmp rmon alarm 1 rising-threshold 600
admin@Switch# set protocols snmp rmon alarm 1 rising-event-index 1
admin@Switch# set protocols snmp rmon alarm 1 falling-threshold 400
admin@Switch# set protocols snmp rmon alarm 1 falling-event-index 1
admin@Switch# set protocols snmp rmon alarm 1 owner public

Step7         Commit after completing all the above configurations.

admin@Switch# commit

Verifying the Configuration

  • The run show rmon statistics command can be used to view RMON Ethernet statistics information.
admin@Switch# run show rmon statistics
Entry 1 on ge-1/1/2 is active, and owned by owner_pica8,
    Monitors ifIndex.2 which has
    Received 354601 octets, 3643 packets,
    0 broadcast and 0 multicast packets,
    0 undersized and 0 oversized packets,
    0 fragments and 0 jabbers,
    0 CRC alignment errors and 0 collisions.
    dropped packet events (due to lack of resources):0.
    packets received of length (in octets):
        64: 0, 65-127: 3524, 128-255: 119,
        256-511: 0, 512-1023: 0, 1024-1518: 0
  • The run show rmon history command can be used to view RMON history statistics information.
admin@Switch# run show rmon history
Entry 1 on ge-1/1/2 is active, and owned by owner_pica8,
    Monitors ifIndex.2 every 10 seconds, bucket is 50,
        Sample # 1 began measuring at 0:43:22
            Received 576000 octets, 9000 packets,
            0 broadcast and 9000 multicast packets,
            0 undersized and 0 oversized packets,
            0 fragments and 0 jabbers,
            0 CRC alignment errors and 0 collisions.
            network utilization is estimated at 0
        Sample # 2 began measuring at 0:43:32
            Received 0 octets, 0 packets,
            0 broadcast and 0 multicast packets,
            0 undersized and 0 oversized packets,
            0 fragments and 0 jabbers,
            0 CRC alignment errors and 0 collisions.
            network utilization is estimated at 0
        Sample # 3 began measuring at 0:43:42
            Received 0 octets, 0 packets,
            0 broadcast and 0 multicast packets,
            0 undersized and 0 oversized packets,
            0 fragments and 0 jabbers,
            0 CRC alignment errors and 0 collisions.
            network utilization is estimated at 0
  • The run show rmon events command can be used to view RMON event information.
admin@Switch# run show rmon events
Entry 1 is active, and owned by public,
    Description is test,
    Event firing causes trap to community Pica8-data-center,
    Last event fired at 0:01:19,
    Current uptime 1:02:17.
  • The run show rmon eventlog command can be used to view RMON event log information.
admin@Switch# run show rmon eventlog
Entry 1 owned by public is VALID.
    Generates eventLog 1.1 at 2:01:19.
    Description: The 1.3.6.1.2.1.16.1.1.1.4.1 defined in alarmEntry 1, equal or more than 600 with alarm value 369804. Alarm sample type is delta.
  • The run show rmon alarms command can be used to view RMON alarms information.
admin@Switch# run show rmon alarms
Entry 1 is active, and owned by public
    Monitors 1.3.6.1.2.1.16.1.1.1.4.1 every 20 seconds
    Taking delta samples, last value was 369804
    Rising threshold is 600, assigned to event 1
    Falling threshold is 400, assigned to event 1
    On startup enable rising or falling alarm

Copyright © 2024 Pica8 Inc. All Rights Reserved.