Too much data in SNMP query, so object won't graph

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

Post Reply
svetter78
Posts: 4
Joined: Tue Feb 05, 2013 11:35 am

Too much data in SNMP query, so object won't graph

Post by svetter78 »

I am polling for current temperature statistics on a Blade Network Technologies switch running Nortel Alteon OS 1.0.21.

When I do a Verbose Query in cacti the following is displayed:

......
+Located input field 'tempSensor1' [walk]
+Executing SNMP walk for data @ '.1.3.6.1.4.1.26543.2.5.1.3.1.22'
+Found item [tempSensor1='45.0 C (Warn at 85.0 C/Recover at 79.0 C)'] index: 0 [from value]
......

This query won't graph. I think it is because of all the extra information returned in parenthesis.

Is there a way to strip off everything after the "C" within the data query XML file or do I have to figure this out with a script.

Thanks,
Scott
User avatar
Linegod
Developer
Posts: 1626
Joined: Thu Feb 20, 2003 10:16 am
Location: Canada
Contact:

Re: Too much data in SNMP query, so object won't graph

Post by Linegod »

Just a wild guess, but did you install the MIB on your system, and you're calling the MIB name, not the OID?
--
Live fast, die young
You're sucking up my bandwidth.

J.P. Pasnak,CD
CCNA, LPIC-1
http://www.warpedsystems.sk.ca
svetter78
Posts: 4
Joined: Tue Feb 05, 2013 11:35 am

Re: Too much data in SNMP query, so object won't graph

Post by svetter78 »

I didn't load the MIB. I'm calling the OID. Here is what my XML file looks like.

Code: Select all

<temperature>
    <name>Get 10GbESM Temp</name>
    <oid_index>.1.3.6.1.4.1.26543.2.5.1.3.1</oid_index>
    <fields>
        <tempSensor1>
            <name>Sensor1</name>
            <method>walk</method>
            <source>value</source>
            <direction>input</direction>
            <oid>.1.3.6.1.4.1.26543.2.5.1.3.1.22</oid>
        </tempSensor1>
-----<snip>-----
        <tempSensor4>
            <name>Sensor4</name>
            <method>walk</method>
            <source>value</source>
            <direction>input</direction>
            <oid>.1.3.6.1.4.1.26543.2.5.1.3.1.27</oid>
        </tempSensor4>
    </fields>
</temperature>
My issue is that temp sensor1 and 2 both return values like I listed in my original post. Sensor3 and 4 are graphing just fine, here is what I get on the verbose query for those.

......
+Located input field 'tempSensor4' [walk]
+Executing SNMP walk for data @ '.1.3.6.1.4.1.26543.2.5.1.3.1.27'
+Found item [tempSensor4='37.0 C'] index: 0 [from value]
......

So I think my syntax is correct, it just seems to be a flaw with the way the switch returns the OID query. I would like to format the output of the snmpwalk with REGEX like we can do with the OID.

I appreciate the help!

Scott
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Re: Too much data in SNMP query, so object won't graph

Post by gandalf »

svetter78 wrote:I would like to format the output of the snmpwalk with REGEX like we can do with the OID.
You can do that. See 4th link of my sig, see disk usage template/query.
R.
svetter78
Posts: 4
Joined: Tue Feb 05, 2013 11:35 am

Re: Too much data in SNMP query, so object won't graph

Post by svetter78 »

gandalf-

Thank you! That is exactly what I was looking for. I should have been smart enough to realize that if you could do OID/REGEXP that you could also do VALUE/REGEXP. Much appreciated!

Scott
svetter78
Posts: 4
Joined: Tue Feb 05, 2013 11:35 am

Re: Too much data in SNMP query, so object won't graph

Post by svetter78 »

I think I spoke too soon.

This works great for input (I was using verbose query to quickly verify syntax) but it doesn't seem to work the same way for output (graphed items). After searching through these forums I found that this may not be possible and that I will have to put in some extra time and create a scripted query.

I wish IBM/BNT didn't have unique OIDs, :x

If I'm wrong, and this can be done via snmp/xml data query please let me know what I might be doing wrong.

Thanks,
Scott
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Re: Too much data in SNMP query, so object won't graph

Post by gandalf »

A scripted query will do that, yes.
We have put some effort into stripping any numbers out of any output. But this is known to fail for specific conditions.
I'm not sure, that a feature request for VALUE/REGEXP on output exists already. As output processing is partly performed by cmd.php AND spine, we will have issues implementing a REXEXP with our C code. But nevertheless, a feature request might be valid. But please check, if it already exists.
R.
jmnielsen
Posts: 9
Joined: Mon Mar 19, 2012 3:09 pm

Re: Too much data in SNMP query, so object won't graph

Post by jmnielsen »

*Sorry if this is hijacking - please let me know if this should go in another thread [this is the only thread in Cacti forum history with "BNT" or "Blade Network Technologies" mentioned in it according to search]*

I have a BNT switch as well and I'm simply trying to graph the In/Out in Bytes of each port but am experiencing issues graphing. I selected the "Cisco Router" template (which obviously BNT is not Cisco - but the data query source for that template is simply the "SNMP - Get Network Interface Statistics" query) and it even found the interfaces for each port, but when it comes to graphing they are all NaN. I am not an RRD Tool power user and have never understood NaNs.

Any idea why this would not work for a BNT (G8000 & G8100) switch? How can I dig into the problem further to see the discrepancy between the snmpwalk and the rrdtool graph?

P.S. I am successfully using the same template for a Cisco 4500 to graph In/Out in Bytes per port.


Edit: Nevermind... There were NaNs for about 15-30 minutes as far as I can tell (and the ping & SNMP check were positive that whole time) but it seems to have eventually started graphing. Why the time lapse? This restores my confidence in the power of the generic SNMP query "SNMP - Get Network Interface Statistics" though. Yay. I still don't understand NaNs though. Any details/explanations on that for future reference?
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests