How to configure RMON in MAS.

Remote Monitoring (RMON) is a standard monitoring specification that enables various network monitors and clients to exchange network-monitoring data with features that meet their particular networking needs. RMON provides network administrators with more freedom in selecting network-monitoring probes and consoles with features that meet their particular networking needs. An RMON implementation typically operates in a client/server model. Monitoring devices (commonly called "probes" in this context) contain RMON software agents that collect information and analyze packets. These probes act as servers and the Network Management applications that communicate with them act as clients. While both agent configuration and data collection use SNMP, RMON is designed to operate differently than other SNMP-based systems:

 

  • Probes have more responsibility for data collection and processing, which reduces SNMP traffic and the processing load of the clients.
  • Information is only transmitted to the management application when required, instead of continuous polling.

The following groups are supported in this release :

 

  • Ethernet statistics
  • History control
  • Ethernet history
  • Alarm
  • Event

Configuration Steps :

 

To enable the RMON service

(ArubaS3500)(config)# service rmon

 

Configuring RMON etherstat entry

(ArubaS3500)(config)#rmon etherstat 1 
(ArubaS3500) (Etherstat index "1") #monitor gigabitethernet 0/0/3 
(ArubaS3500) (Etherstat index "1") #owner Admin

Or

(ArubaS3500) (config) #rmon etherstat 2 
(ArubaS3500) (Etherstat index "2") #monitor ifIndex.4
(ArubaS3500) (Etherstat index “2") #owner Admin

== Configuring RMON history entry ==

(ArubaS3500) (config) #rmon history 1 
(ArubaS3500) (History index "1") #monitor port-channel 1
(ArubaS3500) (History index "1") #samples 10 
(ArubaS3500) (History index "1") #sampling-interval 8 
(ArubaS3500) (History index "1") #owner Admin

 

Configuring RMON event

(ArubaS3500) (config) #rmon event 1 
(ArubaS3500) (Event index "1") #owner Admin
(ArubaS3500) (Event index "1") #type log-and-trap

Configuring RMON Alarm-profile

(ArubaS3500) (config) #rmon alarm-profile alarm_profile1
(ArubaS3500) (alarm profile "alarm_profile1") #rising-threshold-value 2000
(ArubaS3500) (alarm profile "alarm_profile1") #falling-threshold-value 200
(ArubaS3500) (alarm profile "alarm_profile1") #rising-event 1
(ArubaS3500) (alarm profile "alarm_profile1") #falling-event 2
(ArubaS3500) (alarm profile "alarm_profile1") #sample-type absolute
(ArubaS3500) (alarm profile "alarm_profile1") #startup-alarm rising

 

Configure RMON Alarm

(ArubaS3500) (config) #rmon alarm 1
(ArubaS3500) (alarm "1") #alarm-profile alarm_profile1
(ArubaS3500) (alarm "1") #monitor gigabitethernet 0/0/4 oid-type in-mcast-pkts-64
(ArubaS3500) (alarm "1") #owner Admin

 

show rmon etherstat entry <index>

(ArubaS3500) #show rmon etherstat entry 1 
RMON etherstat Entry 1 is Active, and owned by Admin 
Monitors gigabitethernet0/0/3 from 2-22-2012@03-59-01 
Statistics: 
Received 0 octets, 0 packets 
0 broadcast, 0 multicast packets 
0 oversized packets, 0 fragments, 0 jabbers 
0 CRC alignment errors, 0 collisions 
Number of dropped packet events is 0

 

show rmon history entry <index>

(ArubaS3500) #show rmon history entry 1 
Entry 1 is active, and owned by Admin
Monitors  port-channel1 every 8 seconds
Buckets requested 2, Buckets granted 2
2 sample(s) created
Sample 2:
	Began measuring at 2-22-2012@05-06-52
	Received 1447269 octets, 21438 packets
	0 broadcast, 21398 multicast packets
	0 oversized packets, 0 fragments, 0 jabbers
	0 CRC alignment errors, 0 collisions
	Number of dropped packet events is 0
	Network utilization is estimated at 0 (0%)

 

 

Version history
Revision #:
1 of 1
Last update:
‎07-04-2014 02:33 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.