Configure RMON Basic Functions

Network Requirements

• Device is the RMON proxy device and the route with the NMS server is reachable;
• Monitor and manage the event groups, alarm groups, history groups and statistics groups of RMON via NMS.

Network Topology

Figure 9-1 Networking of configuring the RMON basic functions

Configuration Steps

Step 1: Configure VLAN and add the port to the corresponding VLAN. (Omitted)

Step 2: Configure the IP address of the interface. (Omitted)

Step 3: Configure the SNMP proxy.

#Enable the SNMP proxy, and configure the node view node as default and read-only community name as public.

#Enable the SNMP Trap function and configure the destination address and the used community name of the Trap packet.

Step 4: Configure the RMON event group, alarm group, history group and statistics group of Device.

#Enable the RMON proxy.

#Configure the serial number of the event group as 1 and record the ingress packets of port gigabitethernet0/1.

#Configure the alarm event group; the monitor object is ifInOctets.1; configure the sampling of the relative value; the sampling interval is 10s. Configure the increasing and decreasing threshold as 100; configure the triggered event of reaching the threshold value as event1.

#Configure the RMON statistics group.

#Configure the RMON history group.

• ---

  The corresponding port of the instance index ifInOctets.1 is gigabitethernet0/1 on the device. You can use the show interface switchport snmp ifindex command to display the snmp index values of all L2 ports; the show interface snmp ifindex command displays the snmp index value of all L3 ports; the show interface switchport XXXX snmp ifindex command displays the snmp index value of the specified L2 port; the command show interface XXXX snmp ifindex displays the snmp index value of the specified L3 port.
• The remote monitored object instance index needs to be read from the interface table ifEntry of MIB-2.

  ---

Step 5: Configure NMS.

#On NMS using SNMP v1/v2c, we need to set “Read-only community name”, “timeout” and “Retry times”.

Step 6: Check the result.

#View the RMON event group entry configuration of Device.

Device#sh rmon event  
Event 1 is active, owned by config
Description : gigabitethernet_0/1_in_octes 
Event firing causes: log and trap, last fired at 11:38:07   

Current log entries: 
   logIndex     logTime       Description 
 -------------------------------------------------
     1          11:38:07	  gigabitethernet_0/1_in_octes 

#Configure the RMON alarm entry configuration of Device.

Device#show rmon alarm
Alarm 1 is active, owned by 1 
Monitoring variable: ifInOctets.1,	Sample interval: 10 second(s)
Taking samples type: delta,    last value was 4225 
Rising threshold : 100,	assigned to event: 1
Falling threshold : 100,	assigned to event: 1 

#Configure RMON statistics group entry configuration of Device.

Device#sh rmon statistics ethernet  
------------------------------------------
Ethernet statistics table information:  
       Index: 1 
       Data Source: ifIndex.1 
       Owner: config 
       Status: Valid 
 ----------------------------------------- 
 ifIndex.1 statistics information: 
 ----------------------------------------- 
 DropEvents:0 
 Octets: 26962295 
 Pkts:252941 
 BroadcastPkts:156943 
 MulticastPkts:62331 
 CRCAlignErrors:51 
 UndersizePkts:0 
 OversizePkts:0 
 Fragments:0 
 Jabbers:0 
 Collisions:0 
 Pkts64Octets:167737 
 Pkts65to127Octets:47962 
 Pkts128to255Octets:22497 
 Pkts256to511Octets:9967 
 Pkts512to1023Octets:4032 
 Pkts1024to1518Octets:745 

#View the RMON history group entry configuration of Device.

Device#show rmon history control  
---------------------------------------
RMON history control entry index: 1 
 Data source: IfIndex.1 
 Buckets request: 10 
 Buckets granted: 2 
 Interval: 1800 
 Owner: config 
 Entry status: Valid
---------------------------------------

#NMS can query the History, Event and Statistics information in Device via MIB.

NMS can receive the Trap information of the Alarm event from Device. For example, when the ingress traffic change rate of the monitor interface is larger than the increasing threshold or smaller than the decreasing threshold, Device generates the corresponding Trap information and sends to NMS.