Ubiquity not detecting correct os or version
Hi All,
I’m having an issue here with a few of our UniFi Access Points and Observium
Observium detects most of our AP’s as UniFi but for seem reason two of them as being detected as AirOS ?
I have no idea why it is doing this!
They all have same Firmware and OS installed so why is it detecting it as AirOS instead of UniFi ?
I have even compared snmpwalks and they are both identical (oversally data is different, but names, models, etc all the same!)
Also ive noticed the correct ones for UniFi, aren’t detecting the firmware version correctly either ?
its showing one point as 3.1.12 when infact I’m on 3.2.10
Any help where I should start looking or even ideas for me, would be very helpful
Regards
Simon
On 16.02.2015 18:38, Simon Smith wrote:
Hi All,
I’m having an issue here with a few of our UniFi Access Points and Observium
Observium detects most of our AP’s as UniFi but for seem reason two of them as being detected as AirOS ?
I have no idea why it is doing this!
They all have same Firmware and OS installed so why is it detecting it as AirOS instead of UniFi ?
I have even compared snmpwalks and they are both identical (oversally data is different, but names, models, etc all the same!)
Also ive noticed the correct ones for UniFi, aren’t detecting the firmware version correctly either ?
its showing one point as 3.1.12 when infact I’m on 3.2.10
Any help where I should start looking or even ideas for me, would be very helpful
Send me (or pastebin) debug output:
./poller.php -d -m os -h your_incorrect_unifi
Regards
Simon
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Mike,
http://pastebin.com/LpGhMgSZ http://pastebin.com/LpGhMgSZ - home wifi keeps being detected as AirOS ???
http://pastebin.com/5UGJeLNN http://pastebin.com/5UGJeLNN - office wifi, detects as UniFi, but wrong Version detected ?
Simon
On 16 Feb 2015, at 3:42 pm, Mike Stupalov mike@observium.org wrote:
On 16.02.2015 18:38, Simon Smith wrote:
Hi All,
I’m having an issue here with a few of our UniFi Access Points and Observium
Observium detects most of our AP’s as UniFi but for seem reason two of them as being detected as AirOS ?
I have no idea why it is doing this!
They all have same Firmware and OS installed so why is it detecting it as AirOS instead of UniFi ?
I have even compared snmpwalks and they are both identical (oversally data is different, but names, models, etc all the same!)
Also ive noticed the correct ones for UniFi, aren’t detecting the firmware version correctly either ?
its showing one point as 3.1.12 when infact I’m on 3.2.10
Any help where I should start looking or even ideas for me, would be very helpful
Send me (or pastebin) debug output:
./poller.php -d -m os -h your_incorrect_unifi
Regards
Simon
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Mike Stupalov http://observium.org
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi,
On 16.02.2015 18:47, Simon Smith wrote:
Hi Mike,
http://pastebin.com/LpGhMgSZ - home wifi keeps being detected as AirOS ???
Here you have trouble with permissions to mib dirs: CMD[/usr/bin/snmpget -v1 -c *** -Pu -Ovq -m IEEE802dot11-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'homewifi.hestor':'1992' dot11manufacturerProductName.5] STDERR[ Error in packet Reason: (noSuchName) There is no such variable name in this MIB. Failed object: IEEE802dot11-MIB::dot11manufacturerProductName.5 ]
Run this simple test from server console: snmptranslate -On -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp IEEE802dot11-MIB::dot11manufacturerProductName.5
To all files and folders in /opt/observium/mibs, the poller process (which user run observium cron tasks) must have read rights!
http://pastebin.com/5UGJeLNN - office wifi, detects as UniFi, but wrong Version detected ?
Here I think same problem.
Simon
On 16 Feb 2015, at 3:42 pm, Mike Stupalov <mike@observium.org mailto:mike@observium.org> wrote:
On 16.02.2015 18:38, Simon Smith wrote:
Hi All,
I’m having an issue here with a few of our UniFi Access Points and Observium
Observium detects most of our AP’s as UniFi but for seem reason two of them as being detected as AirOS ?
I have no idea why it is doing this!
They all have same Firmware and OS installed so why is it detecting it as AirOS instead of UniFi ?
I have even compared snmpwalks and they are both identical (oversally data is different, but names, models, etc all the same!)
Also ive noticed the correct ones for UniFi, aren’t detecting the firmware version correctly either ?
its showing one point as 3.1.12 when infact I’m on 3.2.10
Any help where I should start looking or even ideas for me, would be very helpful
Send me (or pastebin) debug output:
./poller.php -d -m os -h your_incorrect_unifi
Regards
Simon
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Mike Stupalov http://observium.org
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
Hi Mike
outputs below:
root@observium:/opt/observium/mibs/net-snmp# snmptranslate -On -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp IEEE802dot11-MIB::dot11manufacturerProductName.5 .1.2.840.10036.3.1.2.1.3.5
root@observium:/opt/observium/mibs/net-snmp# /usr/bin/snmpget -v1 -c *** -Pu -Ovq -m IEEE802dot11-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'homewifi.hestor':'1992' dot11manufacturerProductName.5 Error in packet Reason: (noSuchName) There is no such variable name in this MIB. Failed object: IEEE802dot11-MIB::dot11manufacturerProductName.5
any other ideas, because if i didn’t have permissions correctly, surely the first command would of failed and not returned a string?
Simon
On 16 Feb 2015, at 4:19 pm, Mike Stupalov mike@observium.org wrote:
Hi,
On 16.02.2015 18:47, Simon Smith wrote:
Hi Mike,
http://pastebin.com/LpGhMgSZ http://pastebin.com/LpGhMgSZ - home wifi keeps being detected as AirOS ???
Here you have trouble with permissions to mib dirs: CMD[/usr/bin/snmpget -v1 -c *** -Pu -Ovq -m IEEE802dot11-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'homewifi.hestor':'1992' dot11manufacturerProductName.5] STDERR[ Error in packet Reason: (noSuchName) There is no such variable name in this MIB. Failed object: IEEE802dot11-MIB::dot11manufacturerProductName.5 ]
Run this simple test from server console: snmptranslate -On -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp IEEE802dot11-MIB::dot11manufacturerProductName.5
To all files and folders in /opt/observium/mibs, the poller process (which user run observium cron tasks) must have read rights!
http://pastebin.com/5UGJeLNN http://pastebin.com/5UGJeLNN - office wifi, detects as UniFi, but wrong Version detected ?
Here I think same problem.
Simon
On 16 Feb 2015, at 3:42 pm, Mike Stupalov <mike@observium.org mailto:mike@observium.org> wrote:
On 16.02.2015 18:38, Simon Smith wrote:
Hi All,
I’m having an issue here with a few of our UniFi Access Points and Observium
Observium detects most of our AP’s as UniFi but for seem reason two of them as being detected as AirOS ?
I have no idea why it is doing this!
They all have same Firmware and OS installed so why is it detecting it as AirOS instead of UniFi ?
I have even compared snmpwalks and they are both identical (oversally data is different, but names, models, etc all the same!)
Also ive noticed the correct ones for UniFi, aren’t detecting the firmware version correctly either ?
its showing one point as 3.1.12 when infact I’m on 3.2.10
Any help where I should start looking or even ideas for me, would be very helpful
Send me (or pastebin) debug output:
./poller.php -d -m os -h your_incorrect_unifi
Regards
Simon
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Mike Stupalov http://observium.org http://observium.org/
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Mike Stupalov http://observium.org http://observium.org/_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 16 February, 2015 - Mike Stupalov wrote:
On 16.02.2015 18:38, Simon Smith wrote:
Hi All,
I’m having an issue here with a few of our UniFi Access Points and Observium
Observium detects most of our AP’s as UniFi but for seem reason two of them as being detected as AirOS ?
I have no idea why it is doing this!
They all have same Firmware and OS installed so why is it detecting it as AirOS instead of UniFi ?
I have even compared snmpwalks and they are both identical (oversally data is different, but names, models, etc all the same!)
Also ive noticed the correct ones for UniFi, aren’t detecting the firmware version correctly either ?
its showing one point as 3.1.12 when infact I’m on 3.2.10
Any help where I should start looking or even ideas for me, would be very helpful
Send me (or pastebin) debug output:
./poller.php -d -m os -h your_incorrect_unifi
A tad OT but anyhow.
All of my UAP-AC running 3.2.10 firmware gets detected correctly:
Hardware Unifi UAP-AC Operating System Ubiquiti UniFi 3.2.10.2886.150119.1407
I patched my CE-edition to correctly detect the verision strings from my Unifi AP's:
diff -Nur -x mibs ../observium.orig/includes/polling/os/unifi.inc.php ./includes/polling/os/unifi.inc.php --- ../observium.orig/includes/polling/os/unifi.inc.php 2014-03-31 15:32:19.000000000 +0200 +++ ./includes/polling/os/unifi.inc.php 2015-02-11 11:54:11.608907455 +0100 @@ -19,6 +19,7 @@ $hardware = "Unifi ".$hardware;
$version = trim(snmp_get($device, "dot11manufacturerProductVersion.5", "-Ovq", "IEEE802dot11-MIB", mib_dirs())); +if (!$version) { $version = trim(snmp_get($device, "dot11manufacturerProductVersion.2", "-Ovq", "IEEE802dot11-MIB", mib_dirs())); } list(,$version) = preg_split('/.v/',$version);
// EOF
It's basically the same hack thats done for the dot11manufacturerProductName
//Anton
Hi All,
i did a little more digging into this issue,
root@observium:~# snmpget -v1 -c public wifi.rbs:1992 .1.2.840.10036.3.1.2.1.3.2 Error in packet Reason: (noSuchName) There is no such variable name in this MIB. Failed object: iso.2.840.10036.3.1.2.1.3.2
SiMacbookPro:~ Simon$ snmpget -v 1 -c public 10.0.0.254 .1.2.840.10036.3.1.2.1.3.2 iso.2.840.10036.3.1.2.1.3.2 = STRING: "UAP"
it appears, my port forwarding isn’t letting the variable through our firewall!? very strange? (stupid mikoritk firewalls)
but as pointed out by Anton Lundin before,
I can not get any reply from .1.2.840.10036.3.1.2.1.3.5
however i get reply using .1.2.840.10036.3.1.2.1.3.2
regards
Simon
On 16 Feb 2015, at 3:52 pm, Anton Lundin anton@dohi.se wrote:
On 16 February, 2015 - Mike Stupalov wrote:
On 16.02.2015 18:38, Simon Smith wrote:
Hi All,
I’m having an issue here with a few of our UniFi Access Points and Observium
Observium detects most of our AP’s as UniFi but for seem reason two of them as being detected as AirOS ?
I have no idea why it is doing this!
They all have same Firmware and OS installed so why is it detecting it as AirOS instead of UniFi ?
I have even compared snmpwalks and they are both identical (oversally data is different, but names, models, etc all the same!)
Also ive noticed the correct ones for UniFi, aren’t detecting the firmware version correctly either ?
its showing one point as 3.1.12 when infact I’m on 3.2.10
Any help where I should start looking or even ideas for me, would be very helpful
Send me (or pastebin) debug output:
./poller.php -d -m os -h your_incorrect_unifi
A tad OT but anyhow.
All of my UAP-AC running 3.2.10 firmware gets detected correctly:
Hardware Unifi UAP-AC Operating System Ubiquiti UniFi 3.2.10.2886.150119.1407
I patched my CE-edition to correctly detect the verision strings from my Unifi AP's:
diff -Nur -x mibs ../observium.orig/includes/polling/os/unifi.inc.php ./includes/polling/os/unifi.inc.php --- ../observium.orig/includes/polling/os/unifi.inc.php 2014-03-31 15:32:19.000000000 +0200 +++ ./includes/polling/os/unifi.inc.php 2015-02-11 11:54:11.608907455 +0100 @@ -19,6 +19,7 @@ $hardware = "Unifi ".$hardware;
$version = trim(snmp_get($device, "dot11manufacturerProductVersion.5", "-Ovq", "IEEE802dot11-MIB", mib_dirs())); +if (!$version) { $version = trim(snmp_get($device, "dot11manufacturerProductVersion.2", "-Ovq", "IEEE802dot11-MIB", mib_dirs())); } list(,$version) = preg_split('/.v/',$version);
// EOF
It's basically the same hack thats done for the dot11manufacturerProductName
//Anton
-- Anton Lundin
anton@dohi.se +46702-161604
http://www.dohi.se/ _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Current (latest) revision already corrent detect any UniFi device and its version (as I have multiple unifi in production and dev). You should fix the error at your server with "MIB variable name" and all be fine.
On Mon, Feb 16, 2015 at 8:11 PM, Simon Smith simonsmith5521@gmail.com wrote:
Hi All,
i did a little more digging into this issue,
root@observium:~# snmpget -v1 -c public wifi.rbs:1992 .1.2.840.10036.3.1.2.1.3.2 Error in packet Reason: (noSuchName) There is no such variable name in this MIB. Failed object: iso.2.840.10036.3.1.2.1.3.2
SiMacbookPro:~ Simon$ snmpget -v 1 -c public 10.0.0.254 .1.2.840.10036.3.1.2.1.3.2 iso.2.840.10036.3.1.2.1.3.2 = STRING: "UAP"
it appears, my port forwarding isn’t letting the variable through our firewall!? very strange? (stupid mikoritk firewalls)
but as pointed out by Anton Lundin before,
I can not get any reply from .1.2.840.10036.3.1.2.1.3.5
however i get reply using .1.2.840.10036.3.1.2.1.3.2
regards
Simon
On 16 Feb 2015, at 3:52 pm, Anton Lundin anton@dohi.se wrote:
On 16 February, 2015 - Mike Stupalov wrote:
On 16.02.2015 18:38, Simon Smith wrote:
Hi All,
I’m having an issue here with a few of our UniFi Access Points and
Observium
Observium detects most of our AP’s as UniFi but for seem reason two of
them as being detected as AirOS ?
I have no idea why it is doing this!
They all have same Firmware and OS installed so why is it detecting it
as AirOS instead of UniFi ?
I have even compared snmpwalks and they are both identical (oversally
data is different, but names, models, etc all the same!)
Also ive noticed the correct ones for UniFi, aren’t detecting the
firmware version correctly either ?
its showing one point as 3.1.12 when infact I’m on 3.2.10
Any help where I should start looking or even ideas for me, would be
very helpful
Send me (or pastebin) debug output:
./poller.php -d -m os -h your_incorrect_unifi
A tad OT but anyhow.
All of my UAP-AC running 3.2.10 firmware gets detected correctly:
Hardware Unifi UAP-AC Operating System Ubiquiti UniFi 3.2.10.2886.150119.1407
I patched my CE-edition to correctly detect the verision strings from my Unifi AP's:
diff -Nur -x mibs ../observium.orig/includes/polling/os/unifi.inc.php
./includes/polling/os/unifi.inc.php
--- ../observium.orig/includes/polling/os/unifi.inc.php 2014-03-31
15:32:19.000000000 +0200
+++ ./includes/polling/os/unifi.inc.php 2015-02-11
11:54:11.608907455 +0100
@@ -19,6 +19,7 @@ $hardware = "Unifi ".$hardware;
$version = trim(snmp_get($device, "dot11manufacturerProductVersion.5",
"-Ovq", "IEEE802dot11-MIB", mib_dirs()));
+if (!$version) { $version = trim(snmp_get($device,
"dot11manufacturerProductVersion.2", "-Ovq", "IEEE802dot11-MIB", mib_dirs())); }
list(,$version) = preg_split('/.v/',$version);
// EOF
It's basically the same hack thats done for the
dot11manufacturerProductName
//Anton
-- Anton Lundin
anton@dohi.se +46702-161604
http://www.dohi.se/ _______________________________________________ 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
Hi All,
ive done more digging again (should of waited and put it all in one email)
snmpwalking my home wifi shows these values I found
iso.2.840.10036.3.1.2.1.1.3 = STRING: "24:A4:3C" iso.2.840.10036.3.1.2.1.1.4 = STRING: "2A:A4:3C" iso.2.840.10036.3.1.2.1.2.3 = STRING: "Ubiquiti Networks, Inc." iso.2.840.10036.3.1.2.1.2.4 = STRING: "Ubiquiti Networks, Inc." iso.2.840.10036.3.1.2.1.3.3 = STRING: "UAP" iso.2.840.10036.3.1.2.1.3.4 = STRING: "UAP" iso.2.840.10036.3.1.2.1.4.3 = STRING: "BZ.ar7240.v3.2.10.2886.150119.1358" iso.2.840.10036.3.1.2.1.4.4 = STRING: "BZ.ar7240.v3.2.10.2886.150119.1358”
reason for double values for may ask?
because the UniFi has 2 Wireless names being broadcasting!
so need some code to check for using multiple ssids and get correct version and AP models :-)
Regards
Simon
On 16 Feb 2015, at 3:52 pm, Anton Lundin anton@dohi.se wrote:
On 16 February, 2015 - Mike Stupalov wrote:
On 16.02.2015 18:38, Simon Smith wrote:
Hi All,
I’m having an issue here with a few of our UniFi Access Points and Observium
Observium detects most of our AP’s as UniFi but for seem reason two of them as being detected as AirOS ?
I have no idea why it is doing this!
They all have same Firmware and OS installed so why is it detecting it as AirOS instead of UniFi ?
I have even compared snmpwalks and they are both identical (oversally data is different, but names, models, etc all the same!)
Also ive noticed the correct ones for UniFi, aren’t detecting the firmware version correctly either ?
its showing one point as 3.1.12 when infact I’m on 3.2.10
Any help where I should start looking or even ideas for me, would be very helpful
Send me (or pastebin) debug output:
./poller.php -d -m os -h your_incorrect_unifi
A tad OT but anyhow.
All of my UAP-AC running 3.2.10 firmware gets detected correctly:
Hardware Unifi UAP-AC Operating System Ubiquiti UniFi 3.2.10.2886.150119.1407
I patched my CE-edition to correctly detect the verision strings from my Unifi AP's:
diff -Nur -x mibs ../observium.orig/includes/polling/os/unifi.inc.php ./includes/polling/os/unifi.inc.php --- ../observium.orig/includes/polling/os/unifi.inc.php 2014-03-31 15:32:19.000000000 +0200 +++ ./includes/polling/os/unifi.inc.php 2015-02-11 11:54:11.608907455 +0100 @@ -19,6 +19,7 @@ $hardware = "Unifi ".$hardware;
$version = trim(snmp_get($device, "dot11manufacturerProductVersion.5", "-Ovq", "IEEE802dot11-MIB", mib_dirs())); +if (!$version) { $version = trim(snmp_get($device, "dot11manufacturerProductVersion.2", "-Ovq", "IEEE802dot11-MIB", mib_dirs())); } list(,$version) = preg_split('/.v/',$version);
// EOF
It's basically the same hack thats done for the dot11manufacturerProductName
//Anton
-- Anton Lundin
anton@dohi.se +46702-161604
http://www.dohi.se/ _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Anton Lundin -
Mike Stupalov -
Simon Smith