Re: Node sysObjectID

Trevor Dunstan <[email protected]>
Newsgroups gmane.network.opennms.general
Message-ID <[email protected]> 
Hey Jonathon,

Thanks for the info, and I think you may be onto something about the device responding with the incorrect OID. That's exactly what it seems like, but I didn't understand the underlying process of how the OID was identified. If OpenNMS queries the device via snmpget then it would appear that the tape library is responding with the incorrect OID.

I did an snmpget on the device and it came back with the below:

[user@server etc]# snmpget -Os -c public -v 2c 10.20.5.28 .1.3.6.1.2.1.1.2.0

sysObjectID.0 = OID: netSnmpAgentOIDs.10

So not entirely sure what that translates to. Anyway, at the end of the day this is not a show stopper and looking through code at your end really isnt neccesary, I am sure you have more important things to do. The information I have got so far has been very helpful and understanding what is happening under the hood.

Thanks

Trev

 [Description: St_John_Logo_Portrait_RGB]

Trevor Dunstan
Infrastructure Engineer
St John Ambulance Western Australia Ltd.
209 Great Eastern Highway | PO Box 183 | Belmont Western Australia 6104
Tel 08 9373 3875 |
[email protected]<mailto:[email protected]>
www.stjohnambulance.com.au<http://www.stjohnambulance.com.au/>



From: Jonathan Heard [mailto:[email protected]]
Sent: Saturday, October 21, 2017 12:35 AM
To: [email protected]
Subject: Re: [opennms-discuss] Node sysObjectID


Hi Trev
   The SnmpMonitor class looks up the sysObjectID by doing an SNMP Get of .1.3.6.1.2.1.1.2.0 (MIB-II System Object ID)... Your Quantum device should respond with the OID which represented its System Object OID. I think it would be worth checking a manual snmpget of the above OID to see what its responding with. If it doesn't actually support Net-SNMP but gives that as the OID then may be part of the issue.

I've been having a poke around in the SnmpCollector code but it's fairly complicated so I'm not entirely certain as to how important the sysObjectID is when it comes to collecting data.

I'm off for the weekend now, but I'll see if I can find any other info next week

Regards
Jonathan
On 20/10/17 01:27, Trevor Dunstan wrote:
Hey Jonathan,

Thanks for the info, it has been very helpful in finding my way around. Ill provide some details of my findings so it may help someone else having a similar issue or identify something I have missed. Ill try and keep it brief:


1.       Quantum Tape Library MIBS have been successfully uploaded / compiled and data collection generated. No errors and I have added the MIBS to the default SNMP collection via the GUI and the tape library has a SNMP interface.


2.       When I check /etc/opennms/datacollection-config.xml there is an include-collection with the required MIBS as per below:



<include-collection dataCollectionGroup="UPS-MIB"/>

      <include-collection dataCollectionGroup="LIEBERT-GP-CONTROLLER-MIB"/>

      <include-collection dataCollectionGroup="EATON-EPDU-MIB"/>

      <include-collection dataCollectionGroup="QUANTUM-SMALL-TAPE-LIBRARY-MIB"/>

      <include-collection dataCollectionGroup="EATON-EMP-MIB"/>

      <include-collection dataCollectionGroup="QUANTUM-SNMP-MIB"/>

      <include-collection dataCollectionGroup="XUPS-MIB"/>



3.       The SNMP collection name is <snmp-collection name="default" snmpStorageFlag="select">


4.       When I check collectd-config.xml, I see the SNMP collector and its applied to the default collection and the filter is not excluding anything as per below:


<package name="example1">
        <filter>IPADDR != '0.0.0.0'</filter>
        <include-range begin="1.1.1.1" end="254.254.254.254"/>
        <include-range begin="::1" end="ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff"/>

        <service name="SNMP" interval="300000" user-defined="false" status="on">
            <parameter key="collection" value="default"/>
            <parameter key="thresholding-enabled" value="true"/>
        </service>


5.       When I check the /etc/opennms/datacollection directory, I can see the required XML files which contain the OID's as required


QUANTUM-SMALL-TAPE-LIBRARY-MIB.xml
akcp.xml            f5.xml                                     LIEBERT-GP-PDU-MIB.xml            QUANTUM-SNMP-MIB.xml

<group name="logicalLibraryTable" ifType="all">
            <mibObj oid=".1.3.6.1.4.1.3697.1.10.10.1.16.2.1.11" instance="logicalLibraryEntry" alias="logicLibrarNumSlots" type="integer32"/>
      <mibObj oid=".1.3.6.1.4.1.3697.1.10.10.1.16.2.1.12" instance="logicalLibraryEntry" alias="logicalLibraryNumIE" type="integer32"/>
      <mibObj oid=".1.3.6.1.4.1.3697.1.10.10.1.16.2.1.13" instance="logicalLibraryEntry" alias="logiLibrNumTapeDriv" type="integer32"/>
      <mibObj oid=".1.3.6.1.4.1.3697.1.10.10.1.16.2.1.14" instance="logicalLibraryEntry" alias="logLibrStorElemAddr" type="integer32"/>
      <mibObj oid=".1.3.6.1.4.1.3697.1.10.10.1.16.2.1.15" instance="logicalLibraryEntry" alias="logiLibraIEElemAddr" type="integer32"/>
      <mibObj oid=".1.3.6.1.4.1.3697.1.10.10.1.16.2.1.16" instance="logicalLibraryEntry" alias="logLibTapDriEleAddr" type="integer32"/>
      <mibObj oid=".1.3.6.1.4.1.3697.1.10.10.1.16.2.1.17" instance="logicalLibraryEntry" alias="logLibrChanDeviAddr" type="integer32"/>
   </group>


6.       When I look in /opennms/etc/snmp-graph.properties.d I can see the generated graphs

QUANTUM-SMALL-TAPE-LIBRARY-MIB-graph.properties
QUANTUM-SNMP-MIB-graph.properties


7.       And when I look in the /var/opennms/rrd/snmp/ directory there are only jrb files related to the eth interfaces and no other relevant data. So data is being collected, just not all of it.


[root@dc1prdmgt022 37]# ls
eth0-00308c396d1c  eth1-00308c396d1d  lo  sit0
[root@dc1prdmgt022 37]# cd eth0-00308c396d1c/
[root@dc1prdmgt022 eth0-00308c396d1c]# ls
ifInDiscards.jrb   ifInErrors.meta      ifInOctets.jrb     ifInUcastpkts.meta  ifOutErrors.jrb      ifOutNUcastPkts.meta  ifOutUcastPkts.jrb
ifInDiscards.meta  ifInNUcastpkts.jrb   ifInOctets.meta    ifOutDiscards.jrb   ifOutErrors.meta     ifOutOctets.jrb       ifOutUcastPkts.meta
ifInErrors.jrb     ifInNUcastpkts.meta  ifInUcastpkts.jrb  ifOutDiscards.meta  ifOutNUcastPkts.jrb  ifOutOctets.meta      strings.properties
[root@dc1prdmgt022 eth0-00308c396d1c]#

So it looks like ill be digging through the collectd log to try and find out why the full data set is not being collected, but from the information above is there anything that stands out that could preventing the datas being collected ?? So from my understatding the device is being identified as a Net-SNMP device
and so the Net-SNMP MIB is being used to collect the data, so openNMS is not querying the device for the full set of data. Is there any config change that I can do to change the device sysObjectID ?


sysObjectID

.1.3.6.1.4.1.8072.3.2.10






Thanks

Trev

 [Description: St_John_Logo_Portrait_RGB]

Trevor Dunstan
Infrastructure Engineer
St John Ambulance Western Australia Ltd.
209 Great Eastern Highway | PO Box 183 | Belmont Western Australia 6104
Tel 08 9373 3875 |
[email protected]<mailto:[email protected]>
www.stjohnambulance.com.au<http://www.stjohnambulance.com.au/>



From: Jonathan Heard [mailto:[email protected]]
Sent: Thursday, October 19, 2017 4:45 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [opennms-discuss] Node sysObjectID


Hi Trev,

  OpenNMS doesn't have any MIB data built-in for this OID, therefore it won't collect any data unless you install a MIB, which I presume you are doing? (I looked back at your email about the Liebert Aircon and you were talking about installing MIBs there - incidentally, YES - you do need to generate snmp graph properties templates as well - I'm not sure if that question got answered)...

So in order to handle your tape library you first need to take the Quantum MIB files and compile them using the MIB Compiler in the OpenNMS GUI.. You need to generate datacollection, graphs and events, and restart OpenNMS to be sure it's actually loaded them. The node in question also needs to have at least one primary SNMP interface.

Next, check your /etc/opennms/datacollection-config.xml file and make sure that there's an <include-collection> tag which includes the generated Quantum MIB data. Take note of the name attribute of the 'snmp-collection' which includes your events.
Check your /etc/opennms/collectd-config.xml file - and locate the package which contains your SNMP collector with a parameter of 'collection' which matches the name of you noted above, and then pay close attention to the 'filter' tag to be sure that it's not excluding your device for any reason.

Then have a look through the generated datacollection file in /etc/opennms/datacollection - be certain that there are OID definitions which match what you're seeing in snmpwalk.

Once this is all in place, aside from checking the graphs you can poke around in the /var/lib/opennms/rrd/<node_id>/ directory and see if it's actually collecting any data.

If it's still not working then I think you'll need to take a closer look at the debug log output from instrumentation and collectd.

HTH

Jonathan





On 19/10/17 02:57, Trevor Dunstan wrote:
Hi there guys,

I have raised a previous post about not getting detailed resource graphs for some nodes like Liebert Aircon and now another vendor, Quantum Tape Library i40. The replies in my previous post have been helpful and I getting closer to the issue. What I have noticed with the Quantum tape Library is that the node is using a sysObjectID of  .1.3.6.1.4.1.8072.3.2.10 which appears to be incorrect. When I SNMP walk the IP with .1.3.6.1.4.1.8072.3.2.10 I get "No Such Object available on this agent at this OID"

When I walk the tape library with the sysObjectID of .1.3.6.1.4.1.3697 (The MIB from the Quantum Tape Library), I get the data that I have been looking for, so it appears that the tape library is being incorrectly identified and having the incorrect sysObjectID associated with it. Or maybe the Quantum MIB is not being imported correctly into OpenNMS.

So my question is, how do I force OpenNMS to use the sysObjectID of .1.3.6.1.4.1.3697 for the tape library and NOT .1.3.6.1.4.1.8072.3.2.10.


Thanks

Trev




 [Description: St_John_Logo_Portrait_RGB]

Trevor Dunstan
Infrastructure Engineer
St John Ambulance Western Australia Ltd.
209 Great Eastern Highway | PO Box 183 | Belmont Western Australia 6104
Tel 08 9373 3875 |
[email protected]<mailto:[email protected]>
www.stjohnambulance.com.au<http://www.stjohnambulance.com.au/>








------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot





_______________________________________________

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





------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot




_______________________________________________

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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
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
image001.png (image/png, 12.2 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.