Wireless Access

Hello,

I am fairly new to Aruba., We are trying to get our AP's to pick up across the MPLS network.
We have several networks with several IP's such as 10.10.20.10 at one location and 10.10.30.10 at another location.

We have configured the controller and set up the AP's/

The issue is the AP's show as our Router IP and fail to load the .ari file.
we are getting cert_cap=0 which I believe tells us the AP is not pulling data from the controller.

The AP will show up as our primary location router ip (ie 10.10.20.1) 

When the AP's restart the controller briefly sees them and then they drop and restart again attempting to pull from the controller. 

Any ideas or suggestions from someone that might know a little more on this topic?

Thanks

Stacy

Do you have your network configured for discovery via "aruba-master" DNS discovery or dhcp options 43 and 60? What provides dhcp to that access point? If it gets the IP address of your router, it will not work.

Cert_cap just means that it is not configured for control plane security. It is not a bad thing in itself.

Discovery is set for Aruba-Master ( I believe ) - and we are using DHCP for all AP's - We have also tried static to no avail.
DHCP Is provided by the local router at each site. 

It is actually showing (not getting) the IP Address of the Main location Router on the controller.

Location A

Router - IP - 10.10.100.1
Switch
Controller - IP - 10.10.100.5
3 AP's - All working pulling DHCP 

Location B
Router IP - 10.10.200.1
Switch
1 AP - Pulling DHCP local IP 10.10.200.110

Looking at the controller I can see the AP at Location B show up as it is rebooting - Then it will drop again. 
The controller shows the AP as having an IP address of Location A Router IP.

So this is where my confusion is. 

Sorry if I am not explaining this well.
Let me know if you have any other questions. 

Thanks

Stacy

On the controller, when the access point is booting up, type "show log system 50" to see if you can see any messages.

 

Here is a sample of what I got when I did that.  This seems to be the location B trying to work.

 

Nov 5 09:45:29 :311020: <ERRS> |AP Atoka - 203@10.100.20.72 sapd| An internal system error has occurred at file sapd_redun.c function sapd_proc_redun_msg line 4313 error Error: Received RC_OPCODE_ERROR lms 10.100.20.5 tunnel 0.0.0.0 RC_ERROR_ISAKMP_N_VERSION2_SUPPORTED.
Nov 5 09:45:30 :311020: <ERRS> |AP 00:24:6c:cb:0f:f5@10.100.20.74 sapd| An internal system error has occurred at file sapd_redun.c function sapd_proc_redun_msg line 4313 error Error: Received RC_OPCODE_ERROR lms 10.100.20.5 tunnel 0.0.0.0 RC_ERROR_ISAKMP_N_VERSION2_SUPPORTED.
Nov 5 09:45:31 :311020: <ERRS> |AP Atoka - 202@10.100.20.71 sapd| An internal system error has occurred at file sapd_redun.c function sapd_proc_redun_msg line 4313 error Error: Received RC_OPCODE_ERROR lms 10.100.20.5 tunnel 0.0.0.0 RC_ERROR_ISAKMP_N_VERSION2_SUPPORTED.
Nov 5 09:45:34 :311020: <ERRS> |AP Atoka - 201@10.100.20.68 sapd| An internal system error has occurred at file sapd_redun.c function sapd_proc_redun_msg line 4336 error Error: Received RC_OPCODE_ERROR lms 10.100.20.5 tunnel 0.0.0.0 RC_ERROR_IKEP1.
Nov 5 09:45:36 :311020: <ERRS> |AP Atoka - 201@10.100.20.68 sapd| An internal system error has occurred at file sapd_redun.c function sapd_proc_redun_msg line 4313 error Error: Received RC_OPCODE_ERROR lms 10.100.20.5 tunnel 0.0.0.0 RC_ERROR_ISAKMP_N_VERSION2_SUPPORTED.
Nov 5 09:49:38 :303022: <WARN> |AP Wapanucka@10.100.20.74 nanny| Reboot Reason: AP rebooted Mon Nov 5 03:48:39 CST 2012; SAPD: Rebooting after provisioning
Nov 5 09:51:49 :303022: <WARN> |AP 00:24:6c:cb:10:14@10.10.31.116 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:24 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4. Last Ctrl message: HELLO len=859 dest=10.100.20.5 tries=10 seq=0
Nov 5 09:55:58 :311002: <WARN> |AP 00:24:6c:cb:10:14@10.10.31.116 sapd| Rebooting: SAPD: Unable to contact switch. Called by sapd_hello_cb:4. Last Ctrl message: HELLO len=859 dest=10.100.20.5 tries=10 seq=0
Nov 5 09:55:58 :303086: <ERRS> |AP 00:24:6c:cb:10:14@10.10.31.116 nanny| Process Manager (nanny) shutting down - AP will reboot!
Nov 5 10:09:41 :303022: <WARN> |AP 00:24:6c:cb:10:14@10.10.31.116 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:24 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4. Last Ctrl message: HELLO len=859 dest=10.100.20.5 tries=10 seq=0
Nov 5 10:13:49 :311002: <WARN> |AP 00:24:6c:cb:10:14@10.10.31.116 sapd| Rebooting: SAPD: Unable to contact switch. Called by sapd_hello_cb:4. Last Ctrl message: HELLO len=859 dest=10.100.20.5 tries=10 seq=0
Nov 5 10:13:49 :303086: <ERRS> |AP 00:24:6c:cb:10:14@10.10.31.116 nanny| Process Manager (nanny) shutting down - AP will reboot!
Nov 5 10:20:58 :303022: <WARN> |AP 00:24:6c:cb:10:14@10.10.31.116 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:04:30 PST 1999; SAPD: Unable to contact switch. Called by sapd_hello_cb:4. Last Ctrl message: HELLO len=859 dest=10.100.20.5 tries=10 seq=0
Nov 5 10:25:06 :311002: <WARN> |AP 00:24:6c:cb:10:14@10.10.31.116 sapd| Rebooting: SAPD: Unable to contact switch. Called by sapd_hello_cb:4. Last Ctrl message: HELLO len=859 dest=10.100.20.5 tries=10 seq=0
Nov 5 10:25:06 :303086: <ERRS> |AP 00:24:6c:cb:10:14@10.10.31.116 nanny| Process Manager (nanny) shutting down - AP will reboot!

OK We have found the way around this. 

We are technicaly using two types of AP set ups 

1- Being Campus for all local AP's
2- RAP for all of those on different IP schemes.

Bring them to the main location - "Prime" and Provision the AP's

Once it has made initial connection and you will need to configure the AP's to be remote ap's 

Deliver them to the proper destination - Add the IP into the RAP white list and good to go.

Thanks for your suggestions they helped point us in the right direction.

Thanks

Stacy