headers
Ken Eshelby | 1 Mar 2011 01:30
Picon

Re: Issues with collecting SNMP data from tables with arbitrary indexes

First, you don't need to collect the index as the index config takes care of it.  Second you should have a strings.properties in your index-based directories with any strings collected, so that could be something to look into.


Onto another possibility.

If you know that ONLY those indexes will ever exist for your devices, you can get rid of arbitrary indexes and go back to fixed indexes.  Build a group unique to that sysOID.  Then the graph definition will find your cpu66.jrb, etc files all together and you don't need to do additional work combining them together.

<group name="cisco-cpu" ifType="all">
(normal cisco cpu stuff)

<group name="cisco-cpu-routerY" ifType="all">
<mibObj oid=".1.3.6.1.4.1.9.9.109.1.1.1.1.7"  instance="66" alias="cpmCPUTotal1m66"       type="Gauge32" />
<mibObj oid=".1.3.6.1.4.1.9.9.109.1.1.1.1.7"  instance="82" alias="cpmCPUTotal1m82"       type="Gauge32" />
<mibObj oid=".1.3.6.1.4.1.9.9.109.1.1.1.1.7"  instance="2050" alias="cpmCPUTotal1m2050"       type="Gauge32" />
<mibObj oid=".1.3.6.1.4.1.9.9.109.1.1.1.1.7"  instance="2066" alias="cpmCPUTotal1m2066"       type="Gauge32" />
(string collections if you can rely upon fixed string index values, but really it won't matter with a graph definition built this way unless you want specialized graph labels)

     <systemDef name="Cisco Routers">
       <sysoidMask>.1.3.6.1.4.1.9.1.</sysoidMask>

       <collect>
           <includeGroup>cisco-cpu</includeGroup>
       </collect>
     </systemDef>

     <systemDef name="Cisco RouterY">
       <sysoidMask>(routerY's specific OID)</sysoidMask>
       <collect>
           <includeGroup>cisco-cpu-routerY</includeGroup>
       </collect>
     </systemDef>

Then make two graph defs- the generic Cisco CPU graph and the one for RouterY that has the four variables as columns.
I would only use arbitrary index setups if you absolutely have to because that randomness to indexes makes it near impossible to combine any of the data into graph/reports besides just a single graph.
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 2 comments |
headers
Ken Eshelby | 1 Mar 2011 01:35
Picon

Re: Issues with collecting SNMP data from tables with arbitrary indexes

Ah, I see why you are collecting indexes, to get the names.  If you can rely on repeatable names, you could do away with that.  If they change per box then you are back to arbitrary indexes.  It seems like the names should exist within the Cisco MIB and indexed the same as the CPUs. 

I would almost go to generic naming on a graph definition rather than making that a show stopper to revert to using arbitrary indexing.

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 0 comments |
headers
André Lasiota | 1 Mar 2011 12:26

Re: Provisiond autodiscovery configuration

Hi Patrick!

Thanks for your expression. It was exactly what I thought how provsiond
would work in my understanding. Now I have a configuration setup which
should solve our problem.
I wondered if there is a reason why the ip matching is not allowed in
the "NodeCategorySettingPolicy". A little bit confusing this provsiond
config but it works (I hope) :)

Thanks again, have a nice day

Andre

-- 
IN-telegence GmbH
Oskar-Jäger-Str. 125
D - 50825 Köln

Tel.: +49 221 260-1568
Fax: +49 221 260-1995 oder -1509
Web: www.in-telegence.net

Registergericht Köln - HRB 34038
USt-ID DE210882245
Geschäftsführende Gesellschafter: Christian Plätke und Holger Jansen

On 02/28/2011 06:01 PM, Patrick Tuite wrote:
> Hi Andre
> 
> There's a lot in the new Provisiond so I think it may be a bit confusing 
> at first, but I believe I know what may be happening here.
> 
> If you are using enableDiscovery with provisiond, the nodes discovered 
> are part of the default foreign source group and that is where you 
> should have your IP matching policies. You have created a Provision 
> Group where only nodes that are manually added or provisioned into using 
> the adapters etc. will be part of that group's foreign source.
> 
> Patrick
> 
> On 28/02/11 16:38, André Lasiota wrote:
>> Hey Guys!
>>
>> First time posting on a list, so please be patient and sorry for my bad
>> grammar...
>> I try to activate provsiond autodiscovery and got a few problems. Myabe
>> I understand some part of the new provsioning wrong.
>> I've got a IP ange with some nodes, they all have SNMP,SSH and
>> ICMP. I want to autodiscover the range and add the nodes in a
>> provsioning group automatically. (Because this IP Range is configured
>> with dhcp for phones only and people try to use this with PC's. Result
>> is the phones aren't working anymore. So Opennms with autodiscovery
>> should tell us if a wrong hardware is used )
>>
>> I can't find any Infromation about that in the wiki/lists or the
>> Provsiond.pdf so at this time I don't know if this steps are correct for
>> this case.
>>
>> I changed the org.opennms.provisiond.enableDiscovery in
>> opennms.properties from false to true
>> In the service.configuration I commented out the capsd service
>> Defined a range in the discovery-configuration
>> Defined a IP policy for a provsion group
>>
>> Are these steps correct? The Autodiscovery is working but the policy is
>> not matching or the discovered nodes aren't in the group. I also tried
>> to match only one IP which is in the Range but no success at all.
>>
>> Maybe someone can help me to get some information about provisiond/
>> autodiscovery and its configuration?
>>
>> Thanks in advance,
>>
>> Andre
>>
>>
>>
>> *Opennms version: 1.8.7*
>>
>> *etc/discovery-configuration.xml*
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <discovery-configuration
>>      xmlns="http://xmlns.opennms.org/xsd/config/discovery" threads="2"
>>      packets-per-second="1" initial-sleep-time="30000"
>>      restart-sleep-time="7200000" retries="1">
>>      <include-range>
>>          <begin xmlns="">10.2.50.1</begin>
>>          <end xmlns="">10.2.50.254</end>
>>      </include-range>
>> </discovery-configuration>
>>
>>
>> *etc/foreign-sources/Testdiscovery.xml*
>>
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> <foreign-source date-stamp="2011-02-28T15:15:14.670+01:00"
>> name="Testdiscovery"
>> xmlns="http://xmlns.opennms.org/xsd/config/foreign-source">
>>      <scan-interval>1d</scan-interval>
>>      <detectors>
>>          <detector
>> class="org.opennms.netmgt.provision.detector.simple.HttpDetector"
>> name="HTTP"/>
>>          <detector
>> class="org.opennms.netmgt.provision.detector.simple.HttpsDetector"
>> name="HTTPS"/>
>>          <detector
>> class="org.opennms.netmgt.provision.detector.icmp.IcmpDetector"
>> name="ICMP"/>
>>          <detector
>> class="org.opennms.netmgt.provision.detector.snmp.SnmpDetector"
>> name="SNMP"/>
>>          <detector
>> class="org.opennms.netmgt.provision.detector.ssh.SshDetector" name="SSH"/>
>>      </detectors>
>>      <policies>
>>          <policy
>> class="org.opennms.netmgt.provision.persist.policies.MatchingIpInterfacePolicy"
>> name="Testdiscovery">
>>              <parameter value="MANAGE" key="action"/>
>>              <parameter value="ALL_PARAMETERS" key="matchBehavior"/>
>>              <parameter value="10.2.50.104" key="ipAddress"/>
>>          </policy>
>>      </policies>
>> </foreign-source>
>>
> 

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 0 comments |
headers
Matz | 1 Mar 2011 12:52
Picon

WG: OPENNMS und NSCLient ++

xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">

 

Hallo,

habe folgendes Problem möchte die Prozessor - Auslastung mit NSClient++

von einem Windows XP System ermitteln und Graphisch anzeigen lassen.

NSClient habe ich installiert und kann auch Tests Local ausführen wie auf dem Bild nsclienttest.jpg zu sehen ist.

 

Über die WebUI habe ich ein Scheduled Outage erstellt wie auf outage.jpg zu sehen ist.

 

Wenn ich das Prinzip richtig verstanden habe, dann werden die Daten im Verzeichnis

RRD gespeichert.

In Diesem Verzeichnis gibt es 2 Unterordner 1. Responce und 2. Snmp

 

Leider werden die ermittelten Daten nicht in diesem Verzeichnis angezeigt.

 

Weis jemand warum nicht ?

 

Gruß Sascha Matz

 

 

CAPSD-configuration.xml

 

    <protocol-plugin protocol="WMI-NSClientpp_Run" class-name="org.opennms.netmgt.capsd.plugins.WmiPlugin"

        <property key="timeout" value="2000" />

        <property key="retry" value="1" />

        <property key="matchType" value="all"/>

        <property key="wql" value="Select State From Win32_Service Where Name='NSClientpp'" />

        <property key="wmiObject" value="State" />

        <property key="compareOp" value="EQ" />

        <property key="compareValue" value="Running" />

        <property key="service-name" value="WMI-NSClientpp-Run" />

  </protocol-plugin>

 

    <protocol-plugin protocol="NSClientpp" class-name="org.opennms.netmgt.capsd.plugins.NsclientPlugin"

        <property key="banner" value="*" />

        <property key="port" value="12489" />

        <property key="timeout" value="3000" />

        <property key="retry" value="1" />

    </protocol-plugin>

 

 

Poller-configuration.xml

 

<?xml version="1.0" encoding="UTF-8"?>

<poller-configuration xmlns="http://xmlns.opennms.org/xsd/config/poller"

    threads="30" nextOutageId="SELECT nextval('outageNxtId')"

    serviceUnresponsiveEnabled="false" xmlrpc="false" pathOutageEnabled="false">

    <node-outage status="on" pollAllIfNoCriticalServiceDefined="true">

        <critical-service name="ICMP"/>

    </node-outage>

    <package name="example1">

        <filter>IPADDR != '0.0.0.0'</filter>

        <include-range begin="192.12.146.1" end="192.12.146.254"/>

        <rrd step="300">

            <rra xmlns="">RRA:AVERAGE:0.5:1:2016</rra>

            <rra xmlns="">RRA:AVERAGE:0.5:12:1488</rra>

            <rra xmlns="">RRA:AVERAGE:0.5:288:366</rra>

            <rra xmlns="">RRA:MAX:0.5:288:366</rra>

            <rra xmlns="">RRA:MIN:0.5:288:366</rra>

        </rrd>

 

 

        <service name="WMI-NSClientpp-Run" interval="300000"

            user-defined="false" status="on">

            <parameter key="retry" value="2"/>

            <parameter key="timeout" value="3000"/>

            <parameter key="matchType" value="all"/>

            <parameter key="wql" value="Select State From Win32_Service Where Name='NSClientpp'"/>

            <parameter key="wmiObject" value="State"/>

            <parameter key="compareOp" value="EQ"/>

            <parameter key="compareValue" value="Running"/>

            <parameter key="service-name" value="WMI-NSClientpp-Run"/>

        </service>

                <service name="NSClientpp" interval="300000"

            user-defined="false" status="on">

            <parameter key="retry" value="2"/>

            <parameter key="port" value="12489"/>

            <parameter key="timeout" value="3000"/>

        </service>

 

......

 

......

 

 

   <monitor service="WMI-NSClientpp-Run" class-name="org.opennms.netmgt.poller.monitors.WMIMonitor"/>

   <monitor service="NSClientpp" class-name="org.opennms.netmgt.poller.monitors.NsclientMonitor"/>

 

 

 

 

 

nsclient-config.xml

 

<?xml version="1.0"?>

<nsclient-config port="12489" retry="3" timeout="3000" password=""

</nsclient-config>

 

collectd-configuration

 

<?xml version="1.0" encoding="UTF-8"?>

<collectd-configuration threads="50">

    <package name="example1">

        <filter>IPADDR != '0.0.0.0'</filter>

        <include-range begin="192.12.146.1" end="192.12.146.254"/>

        <storeByIfAlias>true</storeByIfAlias>

        <storeByNodeID>normal</storeByNodeID>

        <service name="SNMP" interval="300000" user-defined="false" status="on">

            <parameter key="collection" value="default"/>

            <parameter key="port" value="161"/>

            <parameter key="retry" value="3"/>

            <parameter key="timeout" value="3000"/>

            <parameter key="thresholding-enabled" value="true"/>

        </service>

        <service name="WMI" interval="300000" user-defined="false" status="on">

            <parameter key="collection" value="default"/>

            <parameter key="thresholding-enabled" value="true"/>

        </service>

        <service name="XMP" interval="300000" user-defined="false" status="on">

            <parameter key="collection" value="default"/>

            <parameter key="thresholding-enabled" value="true"/>

        </service>

        <service name="OpenNMS-JVM" interval="300000"

            user-defined="false" status="on">

            <parameter key="port" value="18980"/>

            <parameter key="retry" value="2"/>

            <parameter key="timeout" value="3000"/>

            <parameter key="protocol" value="rmi"/>

            <parameter key="urlPath" value="/jmxrmi"/>

            <parameter key="rrd-base-name" value="java"/>

            <parameter key="ds-name" value="opennms-jvm"/>

            <parameter key="friendly-name" value="opennms-jvm"/>

            <parameter key="collection" value="jsr160"/>

            <parameter key="thresholding-enabled" value="true"/>

        </service>

    </package>

    <package name="NSClient">

        <filter>IPADDR IPLIKE != '0.0.0.0'</filter>

        <include-range begin="192.12.146.1" end="192.12.146.254"/>

        <service name="NSClientpp" interval="300000"

            user-defined="false" status="on">

            <parameter key="nsclient-collection" value="default"/>

            <parameter key="port" value="12489"/>

            <parameter key="retry" value="3"/>

            <parameter key="timeout" value="5000"/>

        </service>

    </package>

    <collector service="SNMP" class-name="org.opennms.netmgt.collectd.SnmpCollector"/>

    <collector service="WMI" class-name="org.opennms.netmgt.collectd.WmiCollector"/>

    <collector service="XMP" class-name="org.opennms.netmgt.collectd.XmpCollector"/>

    <collector service="OpenNMS-JVM" class-name="org.opennms.netmgt.collectd.Jsr160Collector"/>

    <collector service="NSClientpp" class-name="org.opennms.netmgt.collected.NSClientCollector"/>

</collectd-configuration>

 

 

 

nsclient-datacollection-config.xml

 

<?xml version="1.0"?>

<nsclient-datacollection-config rrdRepository="/var/lib/opennms/rrd/snmp/">

  <nsclient-collection name="default">

    <rrd step="300">

      <rra>RRA:AVERAGE:0.5:1:2016</rra>

      <rra>RRA:AVERAGE:0.5:12:1488</rra>

      <rra>RRA:AVERAGE:0.5:288:366</rra>

      <rra>RRA:MAX:0.5:288:366</rra>

      <rra>RRA:MIN:0.5:288:366</rra>

  </rrd>

 

    <wpms>

        <wpm name="LDCFreeSpace" keyvalue="\LogicalDisk(c:)\% Free Space" recheckInterval="300000">

        <attrib name="\LogicalDisk(c:)\% Free Space" alias="LD_C_FreeSpace" type="Gauge"/>

      </wpm>

      <wpm name="ProzessorProc" keyvalue="\Prozessor(_Total)\Prozessorzeit (%)" recheckInterval="3600000">

        <attrib name="\Prozessor(_Total)\Prozessorzeit (%)" alias="cpuProcTime" type="Gauge"/>

      </wpm>

      <wpm name="ProzessorIntr" keyvalue="\Prozessor(_Total)\Interruptzeit (%)" recheckInterval="3600000">

        <attrib name="\Prozessor(_Total)\Interruptzeit (%)" alias="cpuIntrTime" type="Gauge"/>

      </wpm>

      <wpm name="ProzessorPriv" keyvalue="\Prozessor(_Total)\Privilegierte Zeit (%)" recheckInterval="36000

         <attrib name="\Prozessor(_Total)\Privilegierte Zeit (%)" alias="cpuPrivTime" type="Gauge"/>

      </wpm>

      <wpm name="ProzessorUser" keyvalue="\Prozessor(_Total)\Leerlaufzeit (%)" recheckInterval="3600000">

         <attrib name="\Prozessor(_Total)\Leerlaufzeit (%)" alias="cpuUserTime" type="Gauge"/>

      </wpm>

 

      <wpm name="Processor" keyvalue="\Processor(_Total)\% Processor Time" recheckInterval="86400000">

      <><!--  Collect these attributes.  Name is the name to pass to NSClient..

      <>Alias is the local name for the RRD file.

      <>Type is used to convert values around

      <>maxval/minval are optional-->

      <><attrib name="\Processor(_Total)\% Processor Time" alias="cpuProcTime" type="Gauge"/>

      <><attrib name="\Processor(_Total)\% Interrupt Time" alias="cpuIntrTime" type="Gauge"/>

      <><attrib name="\Processor(_Total)\% Privileged Time" alias="cpuPrivTime" type="Gauge"/>

      <><attrib name="\Processor(_Total)\% User Time" alias="cpuUserTime" type="Gauge"/>

      </wpm>

      <wpm name="System" keyvalue="\System\ProcessorQueueLength" recheckInterval="86400000">

      <><attrib name="\System\ProcessorQueueLength" alias="winProcQueueLength" type="Gauge"/>

      <><attrib name="\System\Processes" alias="winProcesses" type="Gauge"/>

      <><attrib name="\System\Threads" alias="winThreads" type="Gauge"/>

      </wpm>

 

      <!-- IIS stats -->

      <wpm name="IIS" keyvalue="\Web Service(_Total)\Bytes Total/sec" recheckInterval="86400000">

      <><attrib name="\Web Service(_Total)\Total Bytes Transfered" alias="iisbytes" type="Counter"/>

      <><attrib name="\Web Service(_Total)\Total CGI Requests" alias="iiscgireq" type="Counter"/>

      <><attrib name="\Web Service(_Total)\Total Get Requests" alias="iisgetreq" type="Counter"/>

       ><attrib name="\Web Service(_Total)\Total Head Requests" alias="iisheadreq" type="Counter"/>

      <><attrib name="\Web Service(_Total)\Total Post Requests" alias="iispostreq" type="Counter"/>

      <><attrib name="\Web Service(_Total)\Maximum Connections" alias="iismaxconn" type="Gauge"/>

      </wpm>

 

      <wpm name="Exchange" keyvalue="\SMTP Server(_Total)\Message Bytes Sent Total" recheckInterval="864000

<------><attrib name="\SMTP Server(_Total)\Message Bytes Sent Total" alias="exchangebytessent" type="Counte

<------><attrib name="\SMTP Server(_Total)\Message Bytes Received Total" alias="exchangebytesrecv" type="Co

<------><attrib name="\SMTP Server(_Total)\Messages Sent Total" alias="exchangemsgsent" type="Counter"/>

<------><attrib name="\SMTP Server(_Total)\Messages Received Total" alias="exchangemsgrecv" type="Counter"/

<------><attrib name="\SMTP Server(_Total)\Messages Delivered Total" alias="exchangemsgdeliv" type="Counter

<------><attrib name="\SMTP Server(_Total)\% Recipients Local" alias="exchangereciplocal" type="Gauge"/>

<------><attrib name="\SMTP Server(_Total)\% Recipients Remote" alias="exchangerecipremote" type="Gauge"/>

      </wpm>

      <wpm name="DNS" keyvalue="\DNS\Total Query Received" recheckInterval="86400000">

<------><attrib name="\DNS\Total Query Received" alias="dnsqueryrecv" type="Counter"/>

<------><attrib name="\DNS\Total Response Sent" alias="dnsresponsesent" type="Counter"/>

      </wpm>

    </wpms>

  </nsclient-collection>

</nsclient-datacollection-config>

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 4 comments |
headers
Matz | 1 Mar 2011 13:54
Picon

WG: OPENNMS und NSCLient ++ (Matz)

Hallo,

Nachtrag zum Thema NSClient++ und Opennms

 

Woran kann es liegen ?

 

 

Im collectd.log steht:

 

2011-03-01 11:53:37,359 WARN  [Main] Collectd: instantiateCollectors: Failed to load collector org.opennms.netmgt.collected.NSClientCollector for service

NSClientpp: java.lang.ClassNotFoundException: org.opennms.netmgt.collected.NSClientCollector

java.lang.ClassNotFoundException: org.opennms.netmgt.collected.NSClientCollector

        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)

        at java.security.AccessController.doPrivileged(Native Method)

        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)

        at java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:627)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

        at java.lang.Class.forName0(Native Method)

        at java.lang.Class.forName(Class.java:169)

        at org.opennms.netmgt.collectd.Collectd.instantiateCollectors(Collectd.java:1501)

        at org.opennms.netmgt.collectd.Collectd.onInit(Collectd.java:207)

        at org.opennms.netmgt.daemon.AbstractServiceDaemon.init(AbstractServiceDaemon.java:356)

        at org.opennms.netmgt.daemon.AbstractServiceDaemon.afterPropertiesSet(AbstractServiceDaemon.java:58)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)

        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)

        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)

        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)

        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:563)

        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:872)

        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:423)

        at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)

        at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:105)

        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)

        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:107)

        at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:277)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:993)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:897)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)

        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)

        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)

        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)

        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1049)

        at org.springframework.beans.factory.access.SingletonBeanFactoryLocator.useBeanFactory(SingletonBeanFactoryLocator.java:397)

        at org.opennms.core.utils.BeanUtils.getBeanFactory(BeanUtils.java:59)

        at org.opennms.core.utils.BeanUtils.getFactory(BeanUtils.java:101)

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 2 comments |
headers
Jonathan C. Cohn | 1 Mar 2011 13:27
Picon

Re: Creating a single graph showing multiple CPUs

Hmm,  a significant number of health monitors on the Cisco devices created in the last 10 years use the entity
MIB to describe where on the device the monitor is and to also give a human readable name to the monitor.

Since the entity MIB contains card serial numbers and such does that get loaded into the asset database?  And
if so, could there be a way to reference the asset database to  determine this information?

Jon

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 0 comments |
headers
Jason Lixfeld | 1 Mar 2011 14:35
Picon

mapsadapter/linkadapter: provisiond discovered nodes too?

I know that the mapsadapter works with nodes manually created via provisiond, but I've yet been able to have
the mapsadapter or linkadapter work on nodes that have been autodiscovered via provisiond.

Is mapsadapter/linkadapter via provisiond autodiscovery supported?
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 0 comments |
headers
Matz | 1 Mar 2011 14:25
Picon

Re: WE: OPENNMS und NSCLient ++ (Matz)

Hallo,

Nachtrag zum Thema NSClient++ und Opennms

 

Woran kann es liegen ?

Es werden auch keine RRD Dateien für das Node  erstellt.

 

Im collectd.log steht:

 

2011-03-01 11:53:37,359 WARN  [Main] Collectd: instantiateCollectors: Failed to load collector org.opennms.netmgt.collected.NSClientCollector for service

NSClientpp: java.lang.ClassNotFoundException: org.opennms.netmgt.collected.NSClientCollector

java.lang.ClassNotFoundException: org.opennms.netmgt.collected.NSClientCollector

        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)

        at java.security.AccessController.doPrivileged(Native Method)

        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)

        at java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:627)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

        at java.lang.Class.forName0(Native Method)

        at java.lang.Class.forName(Class.java:169)

        at org.opennms.netmgt.collectd.Collectd.instantiateCollectors(Collectd.java:1501)

        at org.opennms.netmgt.collectd.Collectd.onInit(Collectd.java:207)

        at org.opennms.netmgt.daemon.AbstractServiceDaemon.init(AbstractServiceDaemon.java:356)

        at org.opennms.netmgt.daemon.AbstractServiceDaemon.afterPropertiesSet(AbstractServiceDaemon.java:58)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)

        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)

        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)

        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)

        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:563)

        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:872)

        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:423)

        at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)

        at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:105)

        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)

        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:107)

        at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:277)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:993)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:897)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)

        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)

        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)

        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)

        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1049)

        at org.springframework.beans.factory.access.SingletonBeanFactoryLocator.useBeanFactory(SingletonBeanFactoryLocator.java:397)

        at org.opennms.core.utils.BeanUtils.getBeanFactory(BeanUtils.java:59)

        at org.opennms.core.utils.BeanUtils.getFactory(BeanUtils.java:101)

 

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 0 comments |
headers
Jason Lixfeld | 1 Mar 2011 15:02
Picon

mapsadapter: nodes not being removed from map after deletion

I have a bunch of manually provisioned nodes that nicely appear in the mapsadapter, but when I delete those
nodes from either admin > delete nodes or admin > manage provisioning groups > edit requisition, the nodes
are still present in the map.  all of the links have been deleted but the nodes are still there with a severity
of "indeterminate".

anyone know what's going on here?  Expected behavior?  Do I have to get nodes out of the dynamic map by some
other means?  The map type still reads automatic.
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 0 comments |
headers
mritorto | 1 Mar 2011 16:17
Picon

Re: Custom graph not displaying innode resource graphs

all I see are response time graphs for smtp, snmp and icmp

these are my snmp-config.xml settings

<?xml version="1.0" encoding="UTF-8"?>
<snmp-config xmlns="http://xmlns.opennms.org/xsd/config/snmp" retry="1"
    timeout="2800" read-community="stbpub" version="v2c">
    <definition read-community="stbpub" version="v1">
        <ns1:range xmlns:ns1="http://xmlns.opennms.org/xsd/types"
            begin="192.168.100.1" end="192.168.100.13"/>
        <ns2:range xmlns:ns2="http://xmlns.opennms.org/xsd/types"
            begin="192.168.100.15" end="192.168.100.64"/>
        <ns3:range xmlns:ns3="http://xmlns.opennms.org/xsd/types"
            begin="10.10.2.10" end="10.10.2.254"/>
        <ns4:range xmlns:ns4="http://xmlns.opennms.org/xsd/types"
            begin="10.30.150.1" end="10.30.150.254"/>
    </definition>
    <definition read-community="Stbpub" version="v1">
        <specific xmlns="">192.168.100.14</specific>

    </definition>
</snmp-config>

-- 
View this message in context: http://opennms.530661.n2.nabble.com/Custom-graph-not-displaying-in-node-resource-graphs-tp6067133p6077585.html
Sent from the OpenNMS - discuss mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Permalink | Reply | 0 comments |

Gmane