On Wed, Nov 18, 2015 at 9:33 AM, Tom Laermans <tom.laermans@powersource.cx> wrote:

Tim,

Looks like you need -M /opt/observium/mibs tacked on to that command line. The error is not coming from the device but from your snmpget tool.

Tom
On 2015-11-17 13:56, Tim Vaughan wrote:
Oops - However, that one fails too:

$ snmpget -v 1 -c public 10.60.0.13 sysDescr.0

sysDescr.0: Unknown Object Identifier (Sub-id not found: (top) -> sysDescr)

$ snmpget -v 1 -c public 10.60.0.13 sysUptime.0

sysUptime.0: Unknown Object Identifier (Sub-id not found: (top) -> sysUptime)
On Tue, Nov 17, 2015 at 12:47 PM, Tom Laermans <tom.laermans@powersource.cx> wrote:
Hi Tim,

it's just sysDescr.0, not system.sysDescr.0 :-)

Tom

On 17/11/2015 13:11, Tim Vaughan wrote:
So this works:

$ snmpget -v 1 -c public 10.60.0.13 1.3.6.1.2.1.7526.2.4

iso.3.6.1.2.1.7526.2.4 = STRING: "snom710-SIP 8.7.3.25.11 1.1.5-IFX-05.01.12"

$ snmpget -v 1 -c public 10.60.0.13 1.3.6.1.2.1.7526.2.8

iso.3.6.1.2.1.7526.2.8 = STRING: "1 days, 1 hours, 52 minutes"

But this doesn't:

$ snmpget -v 1 -c public 10.60.0.13 system.sysDescr.0

system.sysDescr.0: Unknown Object Identifier (Sub-id not found: (top) -> system)

I can set my own OIDs up easily enough but it looks like I can't even get that far if it won't respond to sysDescr queries.

On Tue, Nov 17, 2015 at 11:53 AM, Adam Armstrong <adama@memetic.org> wrote:

snmpget sysDescr.0 sysObjectID.0 and sysUptime.0 from one of them.

adam.

On 17/11/2015 11:47:28, Tim Vaughan <tim@timvaughan.co.uk> wrote:

Thanks for the reply. Mostly I'm interested in alerts if the device goes offline. At the moment I'm not worried about other data, although it would be interesting.

The Snom docs say it requires SNMPv1 (http://wiki.snom.com/Category:HowTo:SNMP) and if I have to I can create custom OIDs (from here, woo: http://www.maartenmoerman.nl/?p=649).

I've checked debug.log as per Tom's suggestion and it doesn't mention anything - do I need to make that happen manually in config.php?

On Tue, Nov 17, 2015 at 11:30 AM, Adam Armstrong <adama@memetic.org> wrote:

In 2006 one of the first devices Observium monitored were SNOM phones, since I worked for a managed services company which provided managed SIP stuff.

This was a long time ago, though, and the support was never migrated to our more modern code structures, so it's likely either been removed or long since stopped working.

Offhand I think you should graph when a phone was in a call and not much else, and it required SNMPv1. Last I checked they still required SNMPv1, so that might be the issue.

adam.

On 17/11/2015 11:26:35, Tim Vaughan <tim@timvaughan.co.uk> wrote:

Hi, I'm trying to add several Snom 710 phones. The documentation says they will accept SNMP requests (http://wiki.snom.com/Category:HowTo:SNMP). However, I can't add it from Observium even if I enter my installation's IP address as trusted in the phone config. Checking the phone logs after trying to add them, I see:

17/11/2015 11:19:53 [NOTICE] TOOLS: SNMP: Received unknown object identifier 06082b06010201010200

17/11/2015 11:19:53 [NOTICE] TOOLS: SNMP: Received unknown object identifier 06082b06010201010300

17/11/2015 11:20:03 [NOTICE] TOOLS: SNMP: Received unknown object identifier 06082b06010201010200

17/11/2015 11:20:03 [NOTICE] TOOLS: SNMP: Received unknown object identifier 06082b06010201010300

Has anyone managed to get their Snom phones talking to Observium?

_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium