Page 2 of 4
Re: Wireless Clients
Posted: Sun Jun 19, 2016 11:30 pm
by Box293
Perhaps these plugins aren't specifically designed for your access points.
If you look at the plugin code you can see what SNMP OID's are being targeted. You can do an SNMP walk against your devices to see if they have these OID's. There might be different OID's returned in the SNMP walk which may work.
Code: Select all
snmpwalk -v 2c -c 0@5@_P@bl1c 192.168.110.1 -O f -m all 1.3.6.1.4.1.8744
Code: Select all
snmpwalk -v 2c -c 0@5@_P@bl1c 192.168.110.1 -O f -m all 1.3.6.1.4.1
Re: Wireless Clients
Posted: Mon Jun 20, 2016 5:52 am
by nozlaf
Code: Select all
./check_msm_ap.sh -H 172.17.1.1 -C public -A 1
OK AP Name: BigApNameSerial: CN20D332V5 Location: MyAPLocation Uptime: Timeticks: (437081400) 50 days, 14:06:54.00 Contact: IP: 172.17.1.33 MAC: B4:A1:2E:4B:EA:2B Status: running
the -A is for the AP number, not sure where you got the idea it was for the name
Re: Wireless Clients
Posted: Mon Jun 20, 2016 5:57 am
by nozlaf
orani wrote:
Code: Select all
Timeout: No Response from 192.168.110.4
Timeout: No Response from 192.168.110.4
OK AP: 0
but i got 6 AP working fine
I noticed that you have a different IP here to the IP you used in the other commands 192.168.110.1
the IP here needs to be the IP of the MSM controller, not the AP
if you run it against an MSM controller you will get the following output (I have two down AP's)
Code: Select all
./check_msm_controller.sh -H 172.17.1.1 -C public
CRITICAL AP: CN3271D0B2 CN1451D325
Re: Wireless Clients
Posted: Mon Jun 20, 2016 9:59 am
by rkennedy
Thanks @nozlaf!
@orani - let us know if you have any further questions.
Re: Wireless Clients
Posted: Mon Jun 20, 2016 12:21 pm
by orani
I am not at office now. I will be tomorrow for more tests.
For that you said I have tow controllers (teaming) and 6 APs.
Controllers ips: 192.168.110.1 and 192.168.110.2 and the teaming ip 192.168.110.4
And
My APs ips are 192.168.110.31-36
When I use the controller script which ip should I use? .1(team manager) or .4(teaming)
As you said for the AP script -A "APnumber".... What is the number of an AP? How can I find it?
Do you mean I have to run the command 6 times (-A 1 to -A 6)???
Re: Wireless Clients
Posted: Mon Jun 20, 2016 3:24 pm
by orani
i ran both scripts again using your advices.
Code: Select all
./check_msm_ap.sh -H 192.168.110.1 -A 1 -C 0@5@_P@bl1c
Timeout: No Response from 192.168.110.1
Timeout: No Response from 192.168.110.1
Timeout: No Response from 192.168.110.1
Timeout: No Response from 192.168.110.1
Timeout: No Response from 192.168.110.1
Timeout: No Response from 192.168.110.1
Timeout: No Response from 192.168.110.1
CRITICAL AP Name: Serial: Location: Uptime: Contact: IP: MAC: Status: unknown
Nothing new happened
Code: Select all
./check_msm_controller.sh -H 192.168.110.1 -C 0@5@_P@bl1c
Timeout: No Response from 192.168.110.1
Timeout: No Response from 192.168.110.1
OK AP: 0
This means that APs are ok and AP:0 means that no AP has problem?
Re: Wireless Clients
Posted: Mon Jun 20, 2016 4:37 pm
by rhassing
I have created a script which checks if all Access points are still in sync.
And I created some sFlow tools you might use in Nagios, but this was not especially for MSM.
Re: Wireless Clients
Posted: Mon Jun 20, 2016 4:44 pm
by ssax
Please run the snmpwalk commands that Box293 listed, it doesn't look like SNMP is enabled/allowed.
Also, try putting single quotes around your community as well:
Code: Select all
./check_msm_ap.sh -H 192.168.110.1 -A 1 -C '0@5@_P@bl1c'
Let us know the results.
Thank you
Re: Wireless Clients
Posted: Tue Jun 21, 2016 7:24 am
by orani
Both of snmpwalk gives me timeout: no response from 192.168.110.1
Re: Wireless Clients
Posted: Tue Jun 21, 2016 7:27 am
by rhassing
Is snmp enabled on the controller?