![]() |
![]() |
|
Newsletter | Forum | Contact Us | News | Products | Downloads | Support | Partners |
|
|
Using Alarm and Event group of Remote Network Monitoring (RMON)Working principle and example of setting Setting RMON Alarm entries with the SetRMONAlarm LUA script application Description of the RMON Event Group Description of the RMON Alarm Group
IntroductionThe goal of this document is to describe how to use LoriotPro software for the management of the alarm group and event group of the remote network monitoring snmp mib. RMON is used to remotely monitor devices with SNMP. Many devices like routers and switches support these two groups, it is also true for the dedicated RMON probes. The support of RMON is generally provided in the SNMP agent or in a sub agent of the device. The RMON mib defines multiple groups but we will focus on the Event and Alarm group. Event Group: The Event group supports the definition of events. An event is triggered by a condition defined in the “Alarm group” or elsewhere in the MIB. When a condition is met, defined action is performed and causes an information to be logged or a SNMP Trap message to be sent, or both of them. Alarm Group: The Alarm group is used to define a set of threshold on the values of objects located in the MIB. If a threshold is crossed either when the mib object value becomes higher or lower a previously defined event is generated. Remark: In any cases, the Alarm Group requires the implementation of the Event group for operation. The Event table should be filled with the event number used by the alarm entries. Working principleBefore configuring the Event table and Alarm table, it is necessary to know what we need to monitor within the hundreds of MIB object. This requires a good knowledge of what and where to find the mib objects. In the example used in this document we will monitor objects of the Ethernet Statistics table of the RMON mib.
But is could be any object of the MIB as soon as these objects are of ASN Integer type (INTEGER, Integer32, Counter32, Counter64,Gauge, or TimeTicks) To achieve the goal of sending a trap to LoriotPro the snmp agent event and alarm group should be configured. The configuration process requires creating at least one entry for an event in the Event table and entries for each mib object to monitor in the Alarm table.
When an Alarm is set in the Alarm table and if the condition is met, for example the value of the monitored object reach the threshold and event is generated. The event has a unique number in the Event table. Here under a list of event configured in an Ethernet Switch from Alcatel (model 6624). The event type defines the type of action that will be triggered (send a trap or generate a log).
Remark: The switch should be configured to send trap to LoriotPro elsewhere in its configuration. As an example of setting, we set alarms on the snmp object etherStatspkts and etherstatsbroadcastpkts. Both of them are available in the etherstats table of the RMON mib. etherStatspkts: The total number of packets (including bad packets, broadcast packets, and multicast packets) received. Etherstatsbroadcastpkts : The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets. After a short baseline analysis of the interface traffic, we decide to set two thresholds, The rising Alarm at 25 pkt/s and the falling alarm at 10 pkts/s. The setting is performed with the RMON Alarm setting application written in LUA and explains in a next chapter of this document If we have a look at the RMON Alarm table in the Loriotpro Mib tree
On the Alcatel switch we can see the same table, this table is not very useful because the snmp object is not displayed, thus better use the MIB table.
Here under an example of trap received from the alarm index 100, the last measured value is 2638 and goes over the threshold of 250 pkts/10s. Be ware that the sampling is done each 10 second and the value is a delta value between to successive collect. The threshold is set on a number of packets for 10 seconds interval too
Setting RMON Alarm entries with the SetRMONAlarm LUA script applicationTo perform the configuration of entries in the RMON Alarm table and in the RMON Event table we do provide the SetRomnAlarm LUA script application. What does this program do ?
WARNING: This LUA script application requires for working LoriotPro Extended Edition of release (-cl) or higher. The RMON mib should be compiled on LoriotPro, check in the MIB tree for the RMON branch. The device that you want to configure should support the RMON Alarm and Event group. InstallationThe SetRMONAlarm application should be located in the /bin/config/script/ directory of LoriotPro. If you do not see it there download it from this location:SetRMONAlarm.zip ConfigurationBefore launching it you should customize the script for your own settings. At the end of the script you should find where the main settings are performed. 1 - You should define a list of event entries Example of Event entry creation: CreateEvent(12,"Event 12",3,"public","loriotpro",deb); This command creates the event number 12, with the description “Event 12". The action of the event is to send a snmp trap. The communauty used will be public and the owner of this entry in the table is LoriotPro. If deb is previously set to 1 a verbose mode is used to debug. 2 - You should define a list of alarm entries. Exemple of Alarm entry creation CreateAlarm(101,10,"etherstatsbroadcastpkts.1009",2,1,250,0,11,0,"LoriotPro",deb);--Rising 250pkts/10s This command creates the alarm number 101, with the sampling interval of 10 seconds. The snmp object collected is etherstatsbroadcastpkts.1009. The alarmSampleType is set to 2 meaning that we use the delta value to compare to threshold. The alarmStartupAlarm is set to 1 meaning that we want to trigger on the rising threshold. The rising threshold is set to 250. The falling threshold is set to 0 (not set) The rising event is the event number 11 defined previously The falling event is not set (value 0) The owner of this entry is “LoriotPro” If deb can be previously set to 1, a verbose mode is used to debug. How to launch the script. If you have modified the script from the Script editor (from the main menu select Tools -> Script Editor (Extended Edition)) Load the script for editing. Select Compiler -> Run Script to launch it. You can also launch a script from the directory and its contextual menu or from the Report Center. Here under screenshots of the execution of the program. (with the default values provided)
Description of the RMON Event GroupThe path to the RMON Event group in the MIB is provided below in numerical and string format. OID LEN (8) : 1.3.6.1.2.1.16.9. iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).rmon(16).event(9) This branch contains the Event Table
Description of the RMON Alarm GroupThe path to the RMON alarm group in the MIB is provided below in numerical and string format. OID LEN (8) : 1.3.6.1.2.1.16.3. iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).rmon(16).alarm(3) The branch contains a single table the Alarm Table:
Each object in the alarm group is explained below.
End of document |
| Newsletter | Forum | Contact Us | News | Products | Downloads | Support | Partners | |||||
|
|||||