I am a little confused and looking for suggestions on what I can do to troubleshoot this issue.
On the machine that I am running Observium on I can use snmpwalk to view the device’s system information.
ubuntu@mgh-netmon:/opt/observium$ snmpwalk -Os -v 2c -c communitystring mx-hospital system sysDescr.0 = STRING: Meraki MX80 Cloud Managed Security Appliance sysObjectID.0 = OID: enterprises.29671.2.103 sysName.0 = STRING: MX-HOSPITAL sysORID.1 = OID: snmpMIB sysORID.2 = OID: vacmBasicGroup sysORID.3 = OID: ifMIB sysORDescr.1 = STRING: The MIB module for SNMPv2 entities sysORDescr.2 = STRING: View-based Access Control Model for SNMP. sysORDescr.3 = STRING: The MIB module to describe generic objects for network interface sub-layers sysORUpTime.1 = Timeticks: (1) 0:00:00.01 sysORUpTime.2 = Timeticks: (1) 0:00:00.01 sysORUpTime.3 = Timeticks: (16) 0:00:00.16
However when I use add_device it tells me that it cannot add the device.
ubuntu@mgh-netmon:/opt/observium$ ./add_device.php mx-hospital communitystring v2c 161 udp Observium v0.14.4.5229 Add Device(s)
Try to add mx-hospital: Trying v2c community communitystring ... No reply on community communitystring using v2c. Could not reach mx-hospital with given SNMP community using v2c. Devices skipped: 1.
Any ideas? I know it Is not a network/firewall related issue since SNMPWALK can access the device. I know it is not an SNMP string issue because both SNMPWALK and another monitoring system is able to access this device using the provided SNMP string.
Hi Richard,
Some fixes went in very recently (in the Subscription edition) for Meraki devices. They don't provide sysUptime so our SNMP check fails.
Tom
On 08/18/2014 07:19 AM, Richard Berndt wrote:
I am a little confused and looking for suggestions on what I can do to troubleshoot this issue.
On the machine that I am running Observium on I can use snmpwalk to view the device’s system information.
ubuntu@mgh-netmon:/opt/observium$ snmpwalk -Os -v 2c -c communitystring mx-hospital system sysDescr.0 = STRING: Meraki MX80 Cloud Managed Security Appliance sysObjectID.0 = OID: enterprises.29671.2.103 sysName.0 = STRING: MX-HOSPITAL sysORID.1 = OID: snmpMIB sysORID.2 = OID: vacmBasicGroup sysORID.3 = OID: ifMIB sysORDescr.1 = STRING: The MIB module for SNMPv2 entities sysORDescr.2 = STRING: View-based Access Control Model for SNMP. sysORDescr.3 = STRING: The MIB module to describe generic objects for network interface sub-layers sysORUpTime.1 = Timeticks: (1) 0:00:00.01 sysORUpTime.2 = Timeticks: (1) 0:00:00.01 sysORUpTime.3 = Timeticks: (16) 0:00:00.16
However when I use add_device it tells me that it cannot add the device.
ubuntu@mgh-netmon:/opt/observium$ ./add_device.php mx-hospital communitystring v2c 161 udp Observium v0.14.4.5229 Add Device(s)
Try to add mx-hospital: Trying v2c community communitystring ... No reply on community communitystring using v2c. Could not reach mx-hospital with given SNMP community using v2c. Devices skipped: 1.
Any ideas? I know it Is not a network/firewall related issue since SNMPWALK can access the device. I know it is not an SNMP string issue because both SNMPWALK and another monitoring system is able to access this device using the provided SNMP string.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 18/08/2014 13:52, Adam Armstrong wrote:
On 2014-08-18 10:25, Tom Laermans wrote:
Hi Richard,
Some fixes went in very recently (in the Subscription edition) for Meraki devices. They don't provide sysUptime so our SNMP check fails.
BECAUSE MERAKI ARE FUCKING STUPID
</rant>
Well, hey, who cares about uptime, right?
I'm somewhat curious if the rest of Observium handles the lack of uptime data (ie will it hide the line/graph or just display 0, and what will a device rebooted alert do if there is no meraki exception).
Tom
On 08/18/2014 02:00 PM, Administrator wrote:
The following email message was blocked, as it may contain unacceptable language, or inappropriate material.
Message details: Sender: tom.laermans@powersource.cx; Recipient: observium@observium.org; Subject: Re: [Observium] Add_device fails at SNMP
FNZ is the trading name of FNZ (UK) Ltd which is registered in England and Wales (05435760) 20-22 Bedford Row, London, WC1R 4JS.
FNZ (UK) Ltd is authorised and regulated by the Financial Conduct Authority (438687).
The contents of this e-mail are confidential and are intended for the attention of the addressee only. If this e-mail has been sent to you in error, kindly notify us immediately by telephone or return e- mail and delete your copy. You should not copy the e-mail or use it for any purpose to disclose its content to any other person.
Please unsubscribe.
Tom
participants (3)
-
Adam Armstrong -
Richard Berndt -
Tom Laermans