Controller Based WLANs

Why is a RAP not stable when it is connected to a remote location, but it works when it is connected to an internet connection?

by on ‎07-04-2014 03:15 PM

Product and Software: This article applies to all ArubaOS versions.

When a remote access point (RAP) is connected to the internal network, the RAP is stable. However, when the RAP is connected from a remote location, the RAP comes up, but it goes down again after 3 or 4 minutes. It seems that the RAP is aging out and resetting the tunnel. When the RAP is in this state, the inner IP address cannot be reached by a ping.


When the AP is connected to internal network it is stable. However, the same AP connected from a remote location works for few minutes and then goes down. If you check the logs, you see that the PAPI keepalives are missing.

If you check the AP system profile, you see that it was configured with inner IP address. When you remove the inner IP address, then this AP comes up and works correctly.

The following logs are from that specific RAP.

(ARUBA-MASTER) #show log ap-debug all | include RAP-Faycal

Sep 28 11:45:32 :400161: <NOTI> |stm| AP RAP-Faycal: Registering AP: IP 192.168.200.19, BSS 00:24:6c:83:8d:42, G band, AP mode, max clients 64, 1 virtual APs

Sep 28 11:45:32 :400162: <DBUG> |stm| AP RAP-Faycal: Registering AP, new virtual ap for ESSID CSCV-LIBRE, deny broadcast 0

Sep 28 11:45:32 :400100: <DBUG> |stm| AP RAP-Faycal: LED state 0x5

Sep 28 11:45:32 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_program_bw: programmed rap uplink bw: 0 0 $ 0 0 0

Sep 28 11:45:32 :305026: <DBUG> |stm| sapm_vap_reg_cb: AP RAP-Faycal: result 1 btime 1285692331 slot 65534 port 1

Sep 28 11:45:32 :305026: <DBUG> |stm| sapm_start_ap_msg: AP RAP-Faycal message type CONFIG

Sep 28 11:45:32 :305026: <DBUG> |stm| sapm_start_ap_msg: AP RAP-Faycal message type FW_CONFIG

Sep 28 11:45:32 :305026: <DBUG> |stm| sapm_start_ap_msg: AP RAP-Faycal message type ALG_CONFIG

Sep 28 11:45:32 :305026: <DBUG> |stm| sapm_start_ap_msg: AP RAP-Faycal message type ACL_CONFIG

Sep 28 11:45:32 :305026: <DBUG> |stm| sapm_start_ap_msg: AP RAP-Faycal message type ROLE_CONFIG

Sep 28 11:45:32 :305026: <DBUG> |stm| sapm_start_ap_msg: AP RAP-Faycal message type NAT_POOL_CONFIG

Sep 28 11:45:32 :305026: <DBUG> |stm| sapm_start_ap_msg: AP RAP-Faycal message type IDLE_USER_TIMEOUT

Sep 28 11:45:32 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_program_bw: programmed rap uplink bw: 1 0 $ 1 0 0

Sep 28 11:45:32 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_program_bw: programmed rap uplink bw: 1 1 $ 1 0 0

Sep 28 11:45:32 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_program_bw: programmed rap uplink bw: 1 2 $ 1 0 0

Sep 28 11:45:32 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_set_global_led_mode: global LED mode is 0

Sep 28 11:45:32 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_set_native_vlan: native vlan is 1

Sep 28 11:45:32 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_set_dbl_encr: single-encryption optimisation: ON (!sysprof:dbl_encr)

Sep 28 11:45:35 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_set_bw_report_intvl: radio 0: setting intvl to 0 at /proc/sys/net/aruba_asap/wifi0/bw_stats_period

Sep 28 11:45:35 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_set_bw_shaping_policy: radio 0: setting intvl to 0 at /proc/sys/net/aruba_asap/wifi0/shaping-policy

Sep 28 11:45:35 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_set_bw_report_intvl: radio 1: setting intvl to 0 at /proc/sys/net/aruba_asap/wifi1/bw_stats_period

Sep 28 11:45:35 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_set_bw_shaping_policy: radio 1: setting intvl to 0 at /proc/sys/net/aruba_asap/wifi1/shaping-policy

Sep 28 11:45:35 :326001: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| AM: Master a020e0c lms a020e0c num_ifs 2

Sep 28 11:45:35 :326148: <NOTI> |AP RAP-Faycal@192.168.200.19 sapd| AM: set_mode called for 00:24:6c:83:8d:48 type 0 active 0

Sep 28 11:45:35 :326148: <NOTI> |AP RAP-Faycal@192.168.200.19 sapd| AM: set_mode called for 00:24:6c:83:8d:40 type 0 active 0

Sep 28 11:45:35 :326001: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| AM: am_update: set_mode processing complete

Sep 28 11:45:35 :311009: <DBUG> |AP RAP-Faycal@192.168.200.19 sapd| sapd_sysctl_set_led_action_mode: LED action mode is 1

Sep 28 11:49:11 :305026: <DBUG> |stm| sapm_ap_ageout: AP RAP-Faycal: Aging out using ageout time 180 (now 1285692551 last 1285692332)

Sep 28 11:49:11 :305003: <INFO> |stm| AP RAP-Faycal is down

Sep 28 11:49:11 :400110: <DBUG> |stm| AP RAP-Faycal: Delete AP state for bssid 00:24:6c:83:8d:40; Deauth 0 Clear 1

Sep 28 11:49:11 :400110: <DBUG> |stm| AP RAP-Faycal: Delete AP state for bssid 00:24:6c:83:8d:41; Deauth 0 Clear 1

Sep 28 11:49:11 :400110: <DBUG> |stm| AP RAP-Faycal: Delete AP state for bssid 00:24:6c:83:8d:42; Deauth 0 Clear 1

Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.