opennms配置文件介绍

 

配置文件介绍

1.      自身管理

1.1service-configuration.xml

这个档案定义opennms本身要启动的服务. 它和VM有关,并且控制哪个服务在哪个VM中开启.

1.2jmx-datacollection-config.xml

2.      发现：

2.1discovery-configuration.xml （daemon）

这个档案定义要发掘的网络地址范围，(ping sweep)以及逾时，重试次数，以及用来做发掘的执行绪(thread)数目。这个档案也提供 初次发掘间隔时间(initial-sleep-time)和重新发掘间隔时间(restart-sleep-time)。这些数值以毫秒(miliseconds)为单位，用来决定 OpenNMS执行后，间隔多久要开始针对网络地址清单作发掘；以及每次发掘之间的间隔时间。

Let's look at that file:

<discovery-configuration threads="1" packets-per-second="1"

                         initial-sleep-time="300000"

                         restart-sleep-time="86400000"

                         retries="3" timeout="800">

 <include-range retries="2" timeout="3000">

    <begin>192.168.0.1</begin>

    <end>192.168.0.254</end>

 </include-range>

 <include-url>file:/opt/OpenNMS/etc/include</include-url>

</discovery-configuration>

 

3.      配置性能采集

3.1snmp-config.xml

定义snmp采集的节点、版本、read-community、超时、重试次数等

The parameters used to connect with SNMP agents are defined in the snmp-config.xml file. Here is an example:

<snmp-config retry="3" timeout="800" read-community="public" write-community="private">

     <definition version="v2c">

          <specific>192.168.0.5</specific>

     </definition>

     <definition retry="4" timeout="2000">

          <range begin="192.168.1.1" end="192.168.1.254"/>

          <range begin="192.168.3.1" end="192.168.3.254"/>

     </definition>

     <definition read-community="bubba" write-community="zeke">

          <range begin="192.168.2.1" end="192.168.2.254"/>

     </definition>

     <definition port="1161">

          <specific>192.168.5.50</specific>

     </definition>

</snmp-config>

 

3.2collectd-configuration.xml

Data collection is handled via the collectd process. collectd listens for NodeGainedService events for the SNMP "service". When this happens, it checks to see if the primary SNMP interface for that node exists in a collection package (which it should by definition). If so, the SNMP collector is instantiated for that IP address.

Unless forced toward one version or another via the snmp-config.xml file, when the collection is initialized it will check to see if SNMPv2 is supported by attempting a GET-BULK on system.sysObjectID. If that fails it will revert to version 1.

This is a change from earlier versions of OpenNMS. capsd is no longer responsible for determining the SNMP version. Whether or not SNMPv2 is supported on a node will no longer show up on the node page.

Let's look at the collectd-configuration.xml file:

<collectd-configuration

        threads="5">

        <package name="example1">

                <filter>IPADDR IPLIKE *.*.*.*</filter>

                <specific>0.0.0.0</specific>

                <include-range begin=