Wireless Access

Hello,

I'm having some trouble trying to provision two AP 61 with a 3600 controller (version 3.3). The main problem is that only one of the AP is detected by the controller as unprovisoned, but I can reach both through ping. Futhermore I can reach both of them with the options from the diagnostics tab, such as "Software Status" or "Debug Log".

Can you help me with this issue?

Thank you very much.

Did that access point ever work?  Are you sure it might not have its ip address hardcoded to another controller?

It worked with another controller. What do you mean with ip hardcoded to another controller? (sorry if stupid question, i'm new with this Aruba systems)

Thank you.

You can provision an access point so that it only finds a controller at a specific ip address.

Is the access point in the same subnet as the controller?

If you can SSH into the controller and get in "enable" mode, type "show log system 50" to see if you can see anything about that access point.

Here you can find the output of the "show log system 50". I see a lot of license errs, so I also display below the output of the "show license limits" command.

Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 4096 for feature CIM Users 5
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit CIM Users (5) to 0, platform limit to 4096
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 4096 for feature CIM Users 5
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 128 for feature Ortronics Access Points 6
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit Ortronics Access Points (6) to 0, platform limit to 128
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 128 for feature Ortronics Access Points 6
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 0 for feature Contexts 7
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit Contexts (7) to 0, platform limit to 0
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 0 for feature Contexts 7
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 512 for feature Mesh Access Points 8
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit Outdoor Mesh Access Points (8) to 0, platform limit to 512
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 512 for feature Mesh Access Points 8
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 0 for feature 3rd-party Remote APs 9
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit 3rd-party Remote APs (9) to 0, platform limit to 0
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 0 for feature 3rd-party Remote APs 9
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 128 for feature Wireless Intrusion Protection Module 10
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit Wireless Intrusion Protection Module (10) to 0, platform limit to 128
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 128 for feature Wireless Intrusion Protection Module 10
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 2048 for feature Policy Enforcement Firewall Module 11
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit Policy Enforcement Firewall Module (11) to 0, platform limit to 2048
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 2048 for feature Policy Enforcement Firewall Module 11
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 2048 for feature Voice Service Module 12
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit Voice Service Module (12) to 0, platform limit to 2048
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 2048 for feature Voice Service Module 12
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 2048 for feature VPN Service Module 13
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit VPN Server Module (13) to 0, platform limit to 2048
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 2048 for feature VPN Service Module 13
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 2048 for feature xSec Module 14
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit xSec Module (14) to 0, platform limit to 2048
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 2048 for feature xSec Module 14
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 512 for feature Indoor Mesh Access Points 15
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_update_limits: updating limit Indoor Mesh Access Points (15) to 0, platform limit to 512
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 512 for feature Indoor Mesh Access Points 15
Dec 14 00:19:12 :399816:  <ERRS> |licensemgr|  __license_get_limit_max: returning max limit of 128 for feature Access Points 0
Dec 14 00:19:25 :399816:  <ERRS> |fpapps|  Failed to Delete Route with err_code 1
Dec 14 00:19:25 :313256:  <WARN> |fpapps| Route resolve returned an Error
Dec 14 00:19:27 :399801:  <ERRS> |cfgm|  An internal system error has occurred at file sapi.c function sapi_rsp line 247.
Dec 14 00:19:48 :304001:  <ERRS> |stm|  Unexpected stm (Station managment) runtime error at data_path_handler, 467, data_path_handler: recv - Network is down
Dec 14 00:19:53 :304001:  <ERRS> |stm|  Unexpected stm (Station managment) runtime error at igmp_send, 117, setsockopt failed
Dec 14 00:19:54 :316019:  <ERRS> |wms| da39a3ee5e6b4b0d3255bfef95601890afd80709
Dec 14 00:31:10 :399816:  <ERRS> |fpapps|  Failed to Delete Route with err_code 1
Dec 14 00:31:10 :316019:  <ERRS> |wms| da39a3ee5e6b4b0d3255bfef95601890afd80709
Dec 14 01:16:08 :303022:  <WARN> |AP VIN-AP-01@192.168.2.32 nanny|  Reboot Reason: AP rebooted Thu Dec 13 09:28:09 PST 2012: SAPD: Reboot requested by controller
Dec 14 01:16:10 :305024:  <WARN> |stm|  AP VIN-AP-01: Group "Vinagrande" does not exist.
Dec 14 01:47:06 :303022:  <WARN> |AP VIN-AP-01@192.168.2.32 nanny|  Reboot Reason: No reboot message found.
Dec 14 01:47:08 :305024:  <WARN> |stm|  AP VIN-AP-01: Group "Vinagrande" does not exist.
Dec 14 01:57:10 :303022:  <WARN> |AP VIN-AP-01@192.168.2.32 nanny|  Reboot Reason: No reboot message found.
Dec 14 01:57:12 :305024:  <WARN> |stm|  AP VIN-AP-01: Group "Vinagrande" does not exist.
Dec 14 02:05:48 :303022:  <WARN> |AP VIN-AP-01@192.168.2.32 nanny|  Reboot Reason: No reboot message found.
Dec 14 02:05:50 :305024:  <WARN> |stm|  AP VIN-AP-01: Group "Vinagrande" does not exist.

(Aruba3600) #show license limits

License Limits
--------------
Limit  Value
-----  -----
128    Access Points
0      Remote Access Points
0      MUXes
0      External Servers
0      xSec Users
0      CIM Users
0      Ortronics Access Points
0      Contexts
0      Outdoor Mesh Access Points
0      3rd-party Remote APs
0      Wireless Intrusion Protection Module
0      Policy Enforcement Firewall Module
0      Voice Service Module
0      VPN Server Module
0      xSec Module
0      Indoor Mesh Access Points

Well,

It looks like that access point is looking for the ap-group "Vinagrande" but it does not exist on that controller.  If it does not exist the access point will not come up.  Create an ap-group with that name.

I created it but still the same issue. Futhermore this AP (the one on the 192.168.2.32) is the one that appears to be provisioned on the controller. The other one is in the same subnet with the IP 192.168.2.33.

The ap-group name is case-sensitive..

Yes, is exactly the same name

You should be able to go to Configuration> Wireless> AP Installation and reprovision that AP to another group.

It doesn't appear, so I can't do it. I can only see in the Configuration> Wireless> AP Installation one of them, the one with IP 192.168.2.32, not the one I'm having trouble with (192.168.2.33).

Type "show ap-group" and paste the output into here..

(Aruba3600) #show ap-group

AP group List
-------------
Name              Profile Status
----              --------------
C.C. Vinyagrande
default
Vinagrande

Total:3

Do this:

config t

ap-group Vinagrande

write memory

It is possible that your Vinagrande has a space in it.

I introduced the commands, wait a few minutes... but still have the same problem, I can only see one AP to be provisioned.

Anyway the problem is not with the Vinagrande one (192.168.2.32), the one i cannot see in the web tool is the other one we didn't see on the system log (192.168.2.33).

Thank you for your help

Okay.  On the commandline, run this command to see if any traffic is being sent to the controller from that access point:

show datapath session table 192.168.2.33

run it over and over again to see if there is any traffic,

I tried the command and it appeared like this several times:

(Aruba3600) #show datapath session table 192.168.2.33

Datapath Session Table Entries
------------------------------

Flags: F - fast age, S - src NAT, N - dest NAT
       D - deny, R - redirect, Y - no syn
       H - high prio, P - set prio, T - set ToS
       C - client, M - mirror, V - VOIP

  Source IP     Destination IP  Prot SPort DPort  Cntr Prio ToS Age Destination TAge Flags
--------------  --------------  ---- ----- -----  ---- ---- --- --- ----------- ---- -----

After that I tried a ping from the controller (192.168.2.111) to the AP, and then the command displayed the information below displayed.

(Aruba3600) # ping 192.168.2.33
Press 'q' to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.33, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.588/0.9588/2.369 m                                                                              s

(Aruba3600) #show datapath session table 192.168.2.33

Datapath Session Table Entries
------------------------------

Flags: F - fast age, S - src NAT, N - dest NAT
       D - deny, R - redirect, Y - no syn
       H - high prio, P - set prio, T - set ToS
       C - client, M - mirror, V - VOIP

  Source IP     Destination IP  Prot SPort DPort  Cntr Prio ToS Age Destination                                                                               TAge Flags
--------------  --------------  ---- ----- -----  ---- ---- --- --- -----------                                                                               ---- -----
192.168.2.33    192.168.2.111   1    35    0      0    0    0   1   local                                                                                     1    F
192.168.2.33    192.168.2.111   1    34    0      0    0    0   1   local                                                                                     1    F
192.168.2.33    192.168.2.111   1    33    0      0    0    0   1   local                                                                                     1    F
192.168.2.33    192.168.2.111   1    32    0      0    0    0   1   local                                                                                     1    F
192.168.2.33    192.168.2.111   1    31    0      0    0    0   1   local                                                                                     1    F
192.168.2.111   192.168.2.33    1    31    2048   0    0    0   1   local                                                                                     1    FYC
192.168.2.111   192.168.2.33    1    35    2048   0    0    0   1   local                                                                                     1    FYC
192.168.2.111   192.168.2.33    1    34    2048   0    0    0   1   local                                                                                     1    FYC
192.168.2.111   192.168.2.33    1    33    2048   0    0    0   1   local                                                                                     1    FYC
192.168.2.111   192.168.2.33    1    32    2048   0    0    0   1   local                                                                                     1    FYC

Unfortunately, that means that access point is not even trying to contact the controller.  The data you were seeing is just pings back and forth.  You might want to try connecting it to the old controller and seeing if it is statically configured to connect to that controller.

And what if I'm not able to use the old one? Can I restart the AP to fabrics?

Unfortunately, the AP61 does not have a console port.  You would have to get a "Y" cable to reset it.  Please see information here:  http://community.arubanetworks.com/t5/Access-Points-and-Mesh-Routers/AP-61-Console-to-clear-the-pre-configuration/td-p/19028

Thank you for your help

Do you have an 800 or 2400 controller lying around?