Observium device discovery
I have a Cisco 9130axi AP that is running in embedded controller mode.
I am not able to monitor traffic or user statistics on the WLANs like I did with my WLC2504.
I do not see any wireless related MIBS attached to the device.
Is there a way to force discovery for certain features or MIBS? Or do I have to add my own custom OID?
Chris
This is likely because these devices don't match the rules we use to identify WLCs (are they even WLCs?)
If you create a jira ticket and attach a walk we can have a look at how we can detect these and attach the correct polling.
Adam.
From: observium observium-bounces@observium.org On Behalf Of Christopher N Callison via observium Sent: 04 May 2021 00:14 To: observium@observium.org Cc: Christopher N Callison cncallison@hotmail.com Subject: [Observium] Observium device discovery
I have a Cisco 9130axi AP that is running in embedded controller mode.
I am not able to monitor traffic or user statistics on the WLANs like I did with my WLC2504.
I do not see any wireless related MIBS attached to the device.
Is there a way to force discovery for certain features or MIBS? Or do I have to add my own custom OID?
Chris
FWIW, I can confirm that C9130AXI-E WAPs do show up correctly in Observium via a WLC - I haven't tried embedded controller mode.
Darren
On Tue, 4 May 2021 at 00:43, Adam Armstrong via observium < observium@observium.org> wrote:
This is likely because these devices don’t match the rules we use to identify WLCs (are they even WLCs?)
If you create a jira ticket and attach a walk we can have a look at how we can detect these and attach the correct polling.
Adam.
*From:* observium observium-bounces@observium.org *On Behalf Of *Christopher N Callison via observium *Sent:* 04 May 2021 00:14 *To:* observium@observium.org *Cc:* Christopher N Callison cncallison@hotmail.com *Subject:* [Observium] Observium device discovery
I have a Cisco 9130axi AP that is running in embedded controller mode.
I am not able to monitor traffic or user statistics on the WLANs like I did with my WLC2504.
I do not see any wireless related MIBS attached to the device.
Is there a way to force discovery for certain features or MIBS? Or do I have to add my own custom OID?
Chris _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Here is the output of the snmpwalk I performed on the controller.
On a related note, I can’t even find a list of the supported MIBs for this class of devices, so I am opening a Cisco ticket to get that information before I do any more research.
root@mess:~# snmpwalk -v2c -c <XXXXXXXX> <NNN.NNN.NNN.NNN> iso.3.6.1.2.1.1.1.0 = STRING: "Cisco IOS Software [Amsterdam], C9800-AP Software (C9800-AP-K9_IOSXE-UNIVERSALK9-M), Version 17.3.3, RELEASE SOFTWARE (fc7) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2021 by Cisco Systems, Inc. Compiled Thu 04-Mar-21 07:40 " iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.9.1.2878 iso.3.6.1.2.1.1.3.0 = Timeticks: (385152300) 44 days, 13:52:03.00 iso.3.6.1.2.1.1.4.0 = STRING: "XXXXXXXXX" iso.3.6.1.2.1.1.5.0 = STRING: "C9130AXI" iso.3.6.1.2.1.1.6.0 = STRING: "AAAAAAAA” iso.3.6.1.2.1.1.7.0 = INTEGER: 6 iso.3.6.1.2.1.1.8.0 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.2.1.0 = INTEGER: 2 iso.3.6.1.2.1.2.2.1.1.1 = INTEGER: 1 iso.3.6.1.2.1.2.2.1.1.2 = INTEGER: 2 iso.3.6.1.2.1.2.2.1.2.1 = STRING: "GigabitEthernet0" iso.3.6.1.2.1.2.2.1.2.2 = STRING: "Null0" iso.3.6.1.2.1.2.2.1.3.1 = INTEGER: 6 iso.3.6.1.2.1.2.2.1.3.2 = INTEGER: 1 iso.3.6.1.2.1.2.2.1.4.1 = INTEGER: 1500 iso.3.6.1.2.1.2.2.1.4.2 = INTEGER: 1500 iso.3.6.1.2.1.2.2.1.5.1 = Gauge32: 1000000000 iso.3.6.1.2.1.2.2.1.5.2 = Gauge32: 4294967295 iso.3.6.1.2.1.2.2.1.6.1 = Hex-STRING: 00 00 5E 00 01 01 iso.3.6.1.2.1.2.2.1.6.2 = "" iso.3.6.1.2.1.2.2.1.7.1 = INTEGER: 1 iso.3.6.1.2.1.2.2.1.7.2 = INTEGER: 1 iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1 iso.3.6.1.2.1.2.2.1.8.2 = INTEGER: 1 iso.3.6.1.2.1.2.2.1.9.1 = Timeticks: (24762) 0:04:07.62 iso.3.6.1.2.1.2.2.1.9.2 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.2.2.1.10.1 = Counter32: 0 iso.3.6.1.2.1.2.2.1.10.2 = Counter32: 0 iso.3.6.1.2.1.2.2.1.11.1 = Counter32: 0 iso.3.6.1.2.1.2.2.1.11.2 = Counter32: 0 iso.3.6.1.2.1.2.2.1.13.1 = Counter32: 0 iso.3.6.1.2.1.2.2.1.13.2 = Counter32: 0 iso.3.6.1.2.1.2.2.1.14.1 = Counter32: 0 iso.3.6.1.2.1.2.2.1.14.2 = Counter32: 0 iso.3.6.1.2.1.2.2.1.15.1 = Counter32: 0 iso.3.6.1.2.1.2.2.1.15.2 = Counter32: 0 iso.3.6.1.2.1.2.2.1.16.1 = Counter32: 0 iso.3.6.1.2.1.2.2.1.16.2 = Counter32: 0 iso.3.6.1.2.1.2.2.1.17.1 = Counter32: 0 iso.3.6.1.2.1.2.2.1.17.2 = Counter32: 0 iso.3.6.1.2.1.2.2.1.19.1 = Counter32: 0 iso.3.6.1.2.1.2.2.1.19.2 = Counter32: 0 iso.3.6.1.2.1.2.2.1.20.1 = Counter32: 0 iso.3.6.1.2.1.2.2.1.20.2 = Counter32: 0 iso.3.6.1.2.1.11.1.0 = Counter32: 601267 iso.3.6.1.2.1.11.2.0 = Counter32: 601198 iso.3.6.1.2.1.11.3.0 = Counter32: 0 iso.3.6.1.2.1.11.4.0 = Counter32: 69 iso.3.6.1.2.1.11.5.0 = Counter32: 0 iso.3.6.1.2.1.11.6.0 = Counter32: 0 iso.3.6.1.2.1.11.8.0 = Counter32: 0 iso.3.6.1.2.1.11.9.0 = Counter32: 0 iso.3.6.1.2.1.11.10.0 = Counter32: 0 iso.3.6.1.2.1.11.11.0 = Counter32: 0 iso.3.6.1.2.1.11.12.0 = Counter32: 0 iso.3.6.1.2.1.11.13.0 = Counter32: 681861 iso.3.6.1.2.1.11.14.0 = Counter32: 0 iso.3.6.1.2.1.11.15.0 = Counter32: 309388 iso.3.6.1.2.1.11.16.0 = Counter32: 374 iso.3.6.1.2.1.11.17.0 = Counter32: 0 iso.3.6.1.2.1.11.18.0 = Counter32: 0 iso.3.6.1.2.1.11.19.0 = Counter32: 0 iso.3.6.1.2.1.11.20.0 = Counter32: 0 iso.3.6.1.2.1.11.21.0 = Counter32: 0 iso.3.6.1.2.1.11.22.0 = Counter32: 0 iso.3.6.1.2.1.11.24.0 = Counter32: 0 iso.3.6.1.2.1.11.25.0 = Counter32: 0 iso.3.6.1.2.1.11.26.0 = Counter32: 0 iso.3.6.1.2.1.11.27.0 = Counter32: 0 iso.3.6.1.2.1.11.28.0 = Counter32: 404608 iso.3.6.1.2.1.11.29.0 = Counter32: 0 iso.3.6.1.2.1.11.30.0 = INTEGER: 2 iso.3.6.1.2.1.11.31.0 = Counter32: 0 iso.3.6.1.2.1.11.32.0 = Counter32: 0 iso.3.6.1.2.1.31.1.1.1.1.1 = STRING: "Gi0" iso.3.6.1.2.1.31.1.1.1.1.2 = STRING: "Nu0" iso.3.6.1.2.1.31.1.1.1.2.1 = Counter32: 0 iso.3.6.1.2.1.31.1.1.1.2.2 = Counter32: 0 iso.3.6.1.2.1.31.1.1.1.3.1 = Counter32: 0 iso.3.6.1.2.1.31.1.1.1.3.2 = Counter32: 0 iso.3.6.1.2.1.31.1.1.1.4.1 = Counter32: 0 iso.3.6.1.2.1.31.1.1.1.4.2 = Counter32: 0 iso.3.6.1.2.1.31.1.1.1.5.1 = Counter32: 0 iso.3.6.1.2.1.31.1.1.1.5.2 = Counter32: 0 iso.3.6.1.2.1.31.1.1.1.6.1 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.6.2 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.7.1 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.7.2 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.8.1 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.8.2 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.9.1 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.9.2 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.10.1 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.10.2 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.11.1 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.11.2 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.12.1 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.12.2 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.13.1 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.13.2 = Counter64: 0 iso.3.6.1.2.1.31.1.1.1.14.1 = INTEGER: 1 iso.3.6.1.2.1.31.1.1.1.14.2 = INTEGER: 1 iso.3.6.1.2.1.31.1.1.1.15.1 = Gauge32: 1000 iso.3.6.1.2.1.31.1.1.1.15.2 = Gauge32: 10000 iso.3.6.1.2.1.31.1.1.1.16.1 = INTEGER: 2 iso.3.6.1.2.1.31.1.1.1.16.2 = INTEGER: 2 iso.3.6.1.2.1.31.1.1.1.17.1 = INTEGER: 1 iso.3.6.1.2.1.31.1.1.1.17.2 = INTEGER: 2 iso.3.6.1.2.1.31.1.1.1.18.1 = "" iso.3.6.1.2.1.31.1.1.1.18.2 = "" iso.3.6.1.2.1.31.1.1.1.19.1 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.31.1.1.1.19.2 = Timeticks: (0) 0:00:00.00 iso.3.6.1.2.1.31.1.2.1.3.0.1 = INTEGER: 1 iso.3.6.1.2.1.31.1.2.1.3.0.2 = INTEGER: 1 iso.3.6.1.2.1.31.1.2.1.3.1.0 = INTEGER: 1 iso.3.6.1.2.1.31.1.2.1.3.2.0 = INTEGER: 1 iso.3.6.1.2.1.31.1.5.0 = Timeticks: (23300) 0:03:53.00 iso.3.6.1.2.1.31.1.6.0 = Timeticks: (23300) 0:03:53.00 iso.3.6.1.2.1.47.1.1.1.1.2.1 = STRING: "Cisco Embedded Wireless Controller on Catalyst Access Point" iso.3.6.1.2.1.47.1.1.1.1.3.1 = OID: iso.3.6.1.4.1.9.12.3.1.3.1 iso.3.6.1.2.1.47.1.1.1.1.4.1 = INTEGER: 0 iso.3.6.1.2.1.47.1.1.1.1.5.1 = INTEGER: 3 iso.3.6.1.2.1.47.1.1.1.1.6.1 = INTEGER: -1 iso.3.6.1.2.1.47.1.1.1.1.7.1 = STRING: "Chassis" iso.3.6.1.2.1.47.1.1.1.1.8.1 = STRING: "V01" iso.3.6.1.2.1.47.1.1.1.1.9.1 = "" iso.3.6.1.2.1.47.1.1.1.1.10.1 = "" iso.3.6.1.2.1.47.1.1.1.1.11.1 = STRING: "ANANANAN" iso.3.6.1.2.1.47.1.1.1.1.12.1 = STRING: "Cisco Systems Inc" iso.3.6.1.2.1.47.1.1.1.1.13.1 = STRING: "C9130AXI-B" iso.3.6.1.2.1.47.1.1.1.1.14.1 = "" iso.3.6.1.2.1.47.1.1.1.1.15.1 = "" iso.3.6.1.2.1.47.1.1.1.1.16.1 = INTEGER: 1 iso.3.6.1.2.1.47.1.1.1.1.17.1 = Hex-STRING: 00 00 00 00 00 00 00 00 iso.3.6.1.2.1.47.1.1.1.1.18.1 = "" iso.3.6.1.2.1.47.1.4.1.0 = Timeticks: (600) 0:00:06.00 iso.3.6.1.2.1.92.1.1.1.0 = Gauge32: 500 iso.3.6.1.2.1.92.1.1.2.0 = Gauge32: 15 iso.3.6.1.2.1.92.1.2.1.0 = Counter32: 0 iso.3.6.1.2.1.92.1.2.2.0 = Counter32: 0
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Storer, Darren via observium Sent: Wednesday, May 5, 2021 10:15 AM To: Observium observium@observium.org Cc: Storer, Darren darren.storer@gmail.com Subject: Re: [Observium] Observium device discovery
FWIW, I can confirm that C9130AXI-E WAPs do show up correctly in Observium via a WLC - I haven't tried embedded controller mode.
Darren
On Tue, 4 May 2021 at 00:43, Adam Armstrong via observium <observium@observium.orgmailto:observium@observium.org> wrote: This is likely because these devices don’t match the rules we use to identify WLCs (are they even WLCs?)
If you create a jira ticket and attach a walk we can have a look at how we can detect these and attach the correct polling.
Adam.
From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Christopher N Callison via observium Sent: 04 May 2021 00:14 To: observium@observium.orgmailto:observium@observium.org Cc: Christopher N Callison <cncallison@hotmail.commailto:cncallison@hotmail.com> Subject: [Observium] Observium device discovery
I have a Cisco 9130axi AP that is running in embedded controller mode.
I am not able to monitor traffic or user statistics on the WLANs like I did with my WLC2504.
I do not see any wireless related MIBS attached to the device.
Is there a way to force discovery for certain features or MIBS? Or do I have to add my own custom OID?
Chris _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong
-
Christopher N Callison
-
Storer, Darren