Integration of AKCP Security Probe x20 IP-Alarmserver into OpenNMS

Seite 1 von 23

OpenNMS Version: 1.6.+ (capsd)Document Version: 1.0

Ronny Trommer, Thursday, January 6, 2011

AKCPFloor 7, WANG DEK Building 2,19/1-2 Vibhavadi Rangsit Road

Jatujak, Bangkok 10900

Thailand

Fon: +66-2-617-8998Web: http://www.akcp.com

The OpenNMS Group, Inc.220 Chatham Business Drive

Pittsboro, NC 27312

United States

Web: http://www.opennms.com

Didactum® Ltd. DeutschlandMarsweg 17

48163 Münster

Deutschland

Fon: +49 - 2501 - 9 71 63 55Web: http://www.didactum.com

NETHINKS GmbHBahnhofstraße 16

36037 Fulda

Deutschland

Fon: +49 - 661 - 2 50 00 0Web: http://www.nethinks.com

Introduction! 3

Requirements ! 4

Grundeinrichtung – AKCP SecurityProbe ! 5

Sensor monitoring with OpenNMS! 11

Long-term Data Collection with OpenNMS! 17

SNMP-Trap MIB Support in OpenNMS! 23

Seite 2 von 23

IntroductionWith AKCP`s securityProbe IP-AlarmServer, a wide range of environmental parameters can be monitored and documented. In larger infrastructures it may make sense to centralize the monitoring to a powerful network monitoring system. In this example we will show you how to interate AKCP`s securityProbe-X20 monitoring devices into OpenNMS.The powerful OpenNMS monitors all connected sensors and records the long-term measurement data. In addition, events of the securityProbe-X20 via SNMP traps are processed by OpenNMS.

For monitoring, two variants are implemented. On the one hand, the active polling of the various sensor status and on the other the direct processing of SNMP traps.

Seite 3 von 23

RequirementsFor the configuration of AKCP securityProbe in OpenNMS, the following four files are needed. The files can be downloaded from the issue tracking system from OpenNMS.

akcp.capsd-configuration.xmlCapsd-Configuration for automatic detection of sensors

akcp.poller-configuration.xml Polling-Configuration for active monitoring of sensors

akcp.securityprobe.snmp.xml SNMP data collection of long term measurement data

akcp.snmp-graph.properties Definition of the graphs for long term data

akcp.spagent.events.xml Converted AKCP SNMP Trap MIB

The configuration is divided into three parts

1. Active monitoring of connected AKCP sensors with a 5 minutes polling interval2. Processing of AKCP`s SNMP traps into OpenNMS for detailed sensor descriptions3. Settings of OpenNMS for storing the collected sensor data4. Presentation and display of long-term measurement data in the web interface

First the SNMP settings on the securityProbe-X20 have to be checked. The functionality can be verified from the OpenNMS server with the following command:

Note: The query should be set via SNMP version 1. The SNMP community is set in default on public and thus corresponds to the web interface can be set with different passwords to be set.

root@opennms:~# snmpwalk -v 1 -c public <ip-security-probe> .1.3.6.1.2.1.1.1.0SNMPv2-MIB::sysDescr.0 = STRING: securityProbe-X20 SEC-PXAV401f Jul 28 2010 16:37:56

Seite 4 von 23

Grundeinrichtung – AKCP SecurityProbeVia SNMP protocol OpenNMS can read automatically various information. The following figures show you the parameters which could be set reasonable.

The following parameters are read out by OpenNMS and can be used in network management:

• System Description: Firmware and type of securityProbe• System Name: Description of securityProbe in network• System Location: Physical location of securityProbe• System Contact: Contact data of the responsible person or department

In addition to the actual system information also the sensor information can be used in OpenNMS. In the long-term graph. the corresponding sensor name and threshold values can be documented and recorded. Furthermore, the information of SNMP traps can then be used for notification.

First the sensor name and levels are displayed in the long-time graphs and on the other are those sent by the SNMP traps.

Seite 5 von 23

For SNMP traps to be sent directly from the securityProbe to OpenNMS, two configuration steps on the securityProbe are necessary. In the first step the OpenNMS server has to be established as SNMP trap destination. In the second step, a notification by SNMP trap has to be created.

The following figures show the creation of the OpenNMS server as an SNMP trap target.

Seite 6 von 23

Seite 7 von 23

Finally a test trap is sent with the button “Test Action” on the OpenNMS server.

An event should appear in OpenNMS. The SNMP trap is still treated as a generic enterprise default trap by OpenNMS. In the OpenNMS configuration section, we describe how to set up the AKCP SNMP Trap MIB in OpenNMS.

The next figure will show you the setup of the notification for the notification for the corresponding sensor as an SNMP trap.

Seite 8 von 23

Seite 9 von 23

In above figures all sensors and all status changes are transmitted to the OpenNMS server. The configuration of the securityProbe is now completed. The next step the appropriate configuration files are integrated in OpenNMS.

Seite 10 von 23

Sensor monitoring with OpenNMSWith the installation of OpenNMS, three functional areas have to be created. The first describes the active status monitoring of the sensors via SNMP. In the second part the long-term data recording and it’s presentation in web interface has to be configured. In the last step the SNMP trap MIB has to be imported to resolve correctly securityProbe’s SNMP traps.

We begin with the creation of active monitoring of the attached sensors. Following configuration files are needed:

akcp.capsd-configuration.xml Capsd-Configuration for automatic sensor detection

akcp.poller-configuration.xml Polling-Configuration for active sensor monitoring

Important: The configuration files are only exceprts. The relevant sections must be inserted in the existing OpenNMS configuration. The following figures show you the corresponding points.

In the first step, the file capsd-configuration.xml will be enhanced with the contents of akcp.capsd-configuration.xml.

Seite 11 von 23

Seite 12 von 23

With the configuration of the Capsd, the connected sensors are automatically recognized by OpenNMS. To monitor the status of the sensors, the file poller-configuration.xml must be enhanced with the content of akcp.poller-configuration.xml.

Seite 13 von 23

Seite 14 von 23

Seite 15 von 23

Seite 16 von 23

Long-term Data Collection with OpenNMSAfter successful configuration, OpenNMS has to be restarted. After restart, the AKCP sensors are automatically detected and monitored via SNMP. the sensors are checked in the default configuration in the 5 minute interval.The next step, the lon-term monitoring in OpenNMS has to established. In OpenNMS you have to edit the two configuration files called datacollection-configuration.xml and snmp-graph.properties.

akcp.securityprobe.snmp.xml SNMP datacollection für Langzeitdaten

akcp.snmp-graph.properties Graphendefinition für Langzeitdaten

First the collectd for the storage of long-term data has to be configured. The corresponding configuration sections have to be inserted into the existing file datacollection-configuration.xml.

Seite 17 von 23

Seite 18 von 23

In this configuration the data is collected intervals of 5 minutes and stored into RRD-files. In order to display the RRD-data in web interface, the file snmp-graph.properties has to be edited. First you have to insert the corresponding reports, then you have to insert the definitions of the graphs.

Seite 19 von 23

Seite 20 von 23

Seite 21 von 23

Seite 22 von 23

SNMP-Trap MIB Support in OpenNMSFor the correct display of the SNMP-Traps you have to import the manufacturerers SNMP Trap-MIB. The conversion of AKCP Trap-MIB was already done and needs only to be downloaded in OpenNMS. For this, you have to copy the file akcp.spagent.eents.xml into the directory $OPENNMS_HOME/etc/events.

akcp.spagent.events.xml Converted AKCP SNMP Trap MIB

To integrate the trap-events, you have to specify in eventconf.xml file the copied file in include area. Please see below figure:

You can edit the file without restart of OpenNMS. A configuration reload could be initiated by following command:

All new incoming traps are then resolved correctly according to the MIB description.

/opt/opennms/bin/send-event.pl uei.opennms.org/internal/reloadDaemonConfig --parm 'daemonName Eventd'

Seite 23 von 23