Polling Active Clients via SNMP.

[Anonymous]

I have a ZD1150 and 23x 7372 APs which im trying to poll active clients via SNMP from.
i can poll the ZoneDirector OK with the following statement

snmpget -v 2c -c public 10.0.0.8 RUCKUS-ZD-SYSTEM-MIB::ruckusZDSystemStatsNumSta.0
this returns the correct value.
RUCKUS-ZD-SYSTEM-MIB::ruckusZDSystemStatsNumSta.0 = Gauge32: 58

but if i try to poll an AP i get an error
snmpget -v 2c -c public 10.0.0.22 RUCKUS-ZD-SYSTEM-MIB::ruckusZDSystemStatsNumSta.0
RUCKUS-ZD-SYSTEM-MIB::ruckusZDSystemStatsNumSta.0 = No Such Object available on this agent at this OID

[keith_redfield]

Right - you can't use ZoneDirector MIBs on the AP's - apples and oranges...

You might want to look at ruckusWLANStatsNumSta or similar in the AP SNMP Reference Guide : https://support.ruckuswireless.com/do...

[Anonymous]

Thats helpful, except i don't see the corresponding - or equivalent check.

I am after the number of currently authorised clients.

i can get stats of recently connected and dropped. but I dont see the correct one for me (needle in a haystack)

can you point me closer to the direction i need?

[keith_redfield]

I see you're working with Support now on this issue. Please do share the result when you have it.

[Anonymous]

Well your guys have come back with one solution. which works, but its also incredibly ugly in practicality terms.

snmpwalk -v 2c -c public 10.1.7.2 RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta

will return

RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...S'.32 = Gauge32: 0
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...^'.0 = Gauge32: 1
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,..._'.32 = Gauge32: 1
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...a'.32 = Gauge32: 0
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...a'.176 = Gauge32: 0
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...j'.112 = Gauge32: 1
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,....'.224 = Gauge32: 0
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,....'.0 = Gauge32: 1
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,....'.32 = Gauge32: 1
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,....'.208 = Gauge32: 11
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,....'.240 = Gauge32: 1
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,....'.96 = Gauge32: 19
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...$'.208 = Gauge32: 0
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...G'.224 = Gauge32: 0
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...L'.160 = Gauge32: 5
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...V'.176 = Gauge32: 0
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...W'.16 = Gauge32: 1
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...]'.144 = Gauge32: 2
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,....'.0 = Gauge32: 7
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...d'.160 = Gauge32: 1
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,...r'.144 = Gauge32: 2
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,....'.112 = Gauge32: 0
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,....'.144 = Gauge32: 0
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'.,..,Y'.224 = Gauge32: 2
RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.'...|..'.160 = Gauge32: 0

performing snmpwalk -v 2c -c public 10.1.7.2 RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta.X
doesnt work so im forced to use OID numbers, which works but performs highly human unreadable results.

snmpwalk -v 2c -c public 10.1.7.2 -On RUCKUS-ZD-WLAN-MIB::ruckusZDWLANAPNumSta

will return

.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.83.32 = Gauge32: 0
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.94.0 = Gauge32: 1
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.95.32 = Gauge32: 1
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.97.32 = Gauge32: 0
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.97.176 = Gauge32: 0
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.106.112 = Gauge32: 1
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.158.224 = Gauge32: 0
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.182.0 = Gauge32: 1
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.185.32 = Gauge32: 1
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.194.208 = Gauge32: 11
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.197.240 = Gauge32: 1
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.13.199.96 = Gauge32: 19
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.14.36.208 = Gauge32: 0
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.14.71.224 = Gauge32: 0
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.14.76.160 = Gauge32: 5
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.14.86.176 = Gauge32: 0
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.14.87.16 = Gauge32: 1
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.14.93.144 = Gauge32: 2
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.14.128.0 = Gauge32: 7
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.15.100.160 = Gauge32: 1
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.16.114.144 = Gauge32: 2
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.16.129.112 = Gauge32: 0
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.16.136.144 = Gauge32: 0
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.44.230.204.44.89.224 = Gauge32: 2
.1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.15.6.196.1.124.2.204.160 = Gauge32: 0

Adding these into a script s very unwieldy so although it does provide the data i need, it returns it in a poor format for usability.

I don't want to sound ungrateful. It is helpful to me. But as i've responded to support, polling the AP's directly makes it much easier to work with the data.