Welcome, Guest. Please login or register.

Author Topic: Feasible for NeDi to track HP printer information?  (Read 14393 times)

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Re: Feasible for NeDi to track HP printer information?
« Reply #15 on: March 02, 2009, 11:11:25 PM »
Well I replaced the temp OID with the OID for connections (1.3.6.1.4.1.9.9.147.1.2.2.2.1.5.40.6) in my ASA sysobj but I see a number way lower than what it should be and not what the snmpget value is for that OID.  Isn't that all I'm supposed to have to do?  I want to do what you did in your "temperature as "number of users connected" graph" example.

rufer

  • Guest
Re: Feasible for NeDi to track HP printer information?
« Reply #16 on: March 03, 2009, 09:08:52 AM »
OK, here are some examples

bluegw.conn.png
Bluesocket. Number of connections in temperature graph.
The device supports maximum 400 connections at a time, so yesterday we were in trouble.
DEF entry:
Temp    1.3.6.1.4.1.9967.1.13.1.1.0

unidreg.voltage.png
APC AP7721 rack automatic transfer switch (2 power sources, 1 common power output). Voltage graph in CPU graphs.
As you can see one voltage is stable 230V, thus from USV, the other fluctuates a bit, thus non-USV.
DEF entry:
MemCPU  1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.1.1.1
MemIO   1.3.6.1.4.1.318.1.1.8.5.3.3.1.3.2.1.1


unidsensor.humidity.png
AKCP SP2 temperature/humidity sensor. Ambient humidity% in CPU graph.
DEF entry:
CPUutl  1.3.6.1.4.1.3854.1.2.2.1.17.1.3.0

One important thing: You always have to keep in mind how RRD treats these values. Read the RRD FAQ. It always depends on RRDstep and in which frequency RRD runs! I have a RRDstep of 3600 and nedi (and thus RRD) runs every 1h, so the values are right.
If you have a big rrdstep and run RRD manually every 5min for testing, the values will probably be wrong.

Greetings
Rufer

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Re: Feasible for NeDi to track HP printer information?
« Reply #17 on: March 03, 2009, 07:57:23 PM »
Cool thanks.  Well I'm getting no joy with using temp for my ASA (firewall) connections.  Here is my graphing section:

# RRD Graphing
CPUutl  1.3.6.1.4.1.9.9.109.1.1.1.1.5.1
Temp    1.3.6.1.4.1.9.9.147.1.2.2.2.1.5.40.6
MemCPU  1.3.6.1.4.1.9.9.48.1.1.1.6.1
MemIO

The connections run between 15,000 to 40,000.  I see messages like this in the messages list "Temperature of 15665 degrees Celsius detected!" but my graph is blank.  I would think auto-scaling would mean large numbers would not be a problem for rrdtool, but maybe nedi.pl chokes on a high value for temperature.


rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2695
    • View Profile
    • NeDi
Re: Feasible for NeDi to track HP printer information?
« Reply #18 on: March 03, 2009, 09:42:10 PM »
I'm halfway through migrating the IO Memory graph into it's own one and make it custom "lablable"...is that even a word? Anyway I'm aware it's only one value for now, but we'll see further once I get some feedback...

As for the Temp GAUGE, you're just a bit too eager :) Thinking a fith of the sun's surface temperature would be enough I limited it to +/- 1000 degrees (I know, the - is even more difficult): "DS:temp:GAUGE:$ds:-1000:1000"

Try the existing IO Memory instead, as it's from 0 to unlimited "DS:memio:GAUGE:$ds:0:U"
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Re: Feasible for NeDi to track HP printer information?
« Reply #19 on: March 04, 2009, 10:54:05 PM »
Using MemIO did it, thanks!  And thanks for your work on the change for added flexibility.

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Re: Feasible for NeDi to track HP printer information?
« Reply #20 on: March 05, 2009, 01:22:52 AM »
On my ASA tracking connections is so nice in nedi along with CPU because you can see the effect on the CPU of the connection load.  I think this would be a natural addition to the ASA sysobj definition.

I think I already contributed an ASA 5520 (1.3.6.1.4.1.9.1.670.def) sysobj file.  So how would that file need to be for the update you have planned to track connections (1.3.6.1.4.1.9.9.147.1.2.2.2.1.5.40.6)?  It would be cool if an updated sysobj file could be included in the next update.


rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2695
    • View Profile
    • NeDi
Re: Feasible for NeDi to track HP printer information?
« Reply #21 on: March 05, 2009, 07:07:23 PM »
I'm afraid I don't have that .def (669 and 674 are there). Mail it to me and I'll include it...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Re: Feasible for NeDi to track HP printer information?
« Reply #22 on: March 05, 2009, 08:38:42 PM »
Did you get 875 & 877?  http://forum.nedi.ch/index.php?topic=333.0

Well here is what I have for 670.  The icon may not be correct but the interfaces and modules works well.


# Definition for 1.3.6.1.4.1.9.1.670 created by Defgen 1.4 on 2.Dec 15:45:09 (admin)

# General
SNMPv   2HC
Type    ASA5520
OS      IOS-fw
Icon    vpbn
Bridge
Dispro
Serial  1.3.6.1.2.1.47.1.1.1.1.11.1
Bimage  1.3.6.1.2.1.47.1.1.1.1.10.1

# Vlan Specific
VLnams
VTPdom
VTPmod

# Interfaces
IFalia
IFalix
IFvlan
IFvlix
IFdupl
IFduix
Halfdp
Fulldp

# Modules
Modesc  1.3.6.1.2.1.47.1.1.1.1.2
Moclas  1.3.6.1.2.1.47.1.1.1.1.5
Movalu  9
Moslot  1.3.6.1.2.1.47.1.1.1.1.7
Modhw   1.3.6.1.2.1.47.1.1.1.1.8
Modsw   1.3.6.1.2.1.47.1.1.1.1.9
Modfw   1.3.6.1.2.1.47.1.1.1.1.10
Modser  1.3.6.1.2.1.47.1.1.1.1.11
Momodl  1.3.6.1.2.1.47.1.1.1.1.13

# RRD Graphing
CPUutl  1.3.6.1.4.1.9.9.109.1.1.1.1.5.1
Temp    1.3.6.1.4.1.9.9.392.1.3.1.0
#Workaround to get Current Connections in the graph labelled MemIO
#MemCPU 1.3.6.1.4.1.9.9.48.1.1.1.6.1
MemIO   1.3.6.1.4.1.9.9.147.1.2.2.2.1.5.40.6


mduling

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Re: Feasible for NeDi to track HP printer information?
« Reply #23 on: March 05, 2009, 08:53:01 PM »
BTW, how do you tell which def file a device is using?  I think I had to copy this

1.3.6.1.4.1.3854.1.2.2.1.1.def

to this

1.3.6.1.4.1.3854.1.def

to get my ACKP sensorProbe2 to work.  I would like to confirm which def file it is using, but since I left the original file in place, I want to be sure since I am going from memory.  I also don't understand why the one def file for AKCP has "Type  akcp-HHMSS".

rufer

  • Guest
Re: Feasible for NeDi to track HP printer information?
« Reply #24 on: March 06, 2009, 09:54:45 AM »
The DEF file is chosen upon the SNMP sysOID of a device.
AKCP decided to change those between software versions. That's why there are multiple DEF files for them.

Greetings
Rufer