Wireless Access

last person joined: 2 days ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

AP BSSIDs keep going up and down

This thread has been viewed 18 times

  • 1.  AP BSSIDs keep going up and down

    MVP
    Posted Aug 10, 2017 01:10 PM

    Good afternoon,

     

    I have an Aruba 7220 controller and AP-335 configured for bridged mode. We have a wired profile setup for bridging to make ENET0 a trunk and allow VLAN 210,211, with 210 being native - That's where we want the AP to get it's IP from. The AP worked fine when it came up initially, and was then provisioned into the AP group that has this wired profile. I was told the switchport was configured to match, but haven't confirmed that. We notice the BSS-Table shows the SSIDs for about 17 seconds and then it drops for 1-2 seconds and then back up same thing. The AP never reboots, just the radios. I confirmed the VLANs are configured on the controllers.

     

    Any idea what could be causing this? I'm still thinking it's switchport related, but need some other input if anyone else has had similar issue.

     

    Thanks.



  • 2.  RE: AP BSSIDs keep going up and down

    EMPLOYEE
    Posted Aug 10, 2017 01:13 PM
    Type "show log system all" on the controller to get a clue.


  • 3.  RE: AP BSSIDs keep going up and down

    MVP
    Posted Aug 10, 2017 01:19 PM

    KERNEL(AP-447_100-TEST@172.20.211.104): [130458.639682] VAP device aruba000 created osifp: (c5939620) os_if: (daf88000)
    Aug 10 07:13:06  KERNEL(AP-447_100-TEST@172.20.211.104): [130458.695362] VAP device aruba001 created osifp: (c593e940) os_if: (c6b68000)
    Aug 10 07:13:06  KERNEL(AP-447_100-TEST@172.20.211.104): [130458.789186] copy prefab machdr
    Aug 10 07:13:06  KERNEL(AP-447_100-TEST@172.20.211.104): [130458.791847] VAP device aruba002 created osifp: (c593b760) os_if: (c4478000)
    Aug 10 07:13:06  KERNEL(AP-447_100-TEST@172.20.211.104): [130458.886796] VAP device aruba100 created osifp: (c5948580) os_if: (dab20000)
    Aug 10 07:13:06  KERNEL(AP-447_100-TEST@172.20.211.104): [130458.945730] VAP device aruba101 created osifp: (c594d8a0) os_if: (c5818000)
    Aug 10 07:13:06  KERNEL(AP-447_100-TEST@172.20.211.104): [130459.037208] copy prefab machdr
    Aug 10 07:13:06  KERNEL(AP-447_100-TEST@172.20.211.104): [130459.039612] VAP device aruba102 created osifp: (c594b760) os_if: (db750000)
    Aug 10 07:13:09  KERNEL(AP-447_100-TEST@172.20.211.104): [130461.547530] asap_mod: asap_dpa.c:3673:asap_dpa_rem_lms() tun is unset
    Aug 10 07:13:09  KERNEL(AP-447_100-TEST@172.20.211.104): [130461.547562] copy standby prefab machdr
    Aug 10 07:13:15 :311004:  <WARN> |AP AP-447_100-TEST@172.20.211.104 sapd|  Missed 8 heartbeats; rebootstrapping
    Aug 10 07:13:27  KERNEL(AP-447_100-TEST@172.20.211.104): [130479.513391] asap_mod: asap_dpa.c:2882:remove_out_flow() Outbound flow 0x9000 is not inserted yet
    Aug 10 07:13:27  KERNEL(AP-447_100-TEST@172.20.211.104): [130479.513694] copy standby prefab machdr
    Aug 10 07:13:33 :311004:  <WARN> |AP AP-447_100-TEST@172.20.211.104 sapd|  Missed 8 heartbeats; rebootstrapping
    Aug 10 07:13:45  KERNEL(AP-447_100-TEST@172.20.211.104): [130497.645344] asap_mod: asap_dpa.c:2882:remove_out_flow() Outbound flow 0x9000 is not inserted yet
    Aug 10 07:13:45  KERNEL(AP-447_100-TEST@172.20.211.104): [130497.645635] copy standby prefab machdr
    Aug 10 07:13:51 :311004:  <WARN> |AP AP-447_100-TEST@172.20.211.104 sapd|  Missed 8 heartbeats; rebootstrapping
    Aug 10 07:14:28 :311004:  <WARN> |AP AP-447_100-TEST@172.20.211.104 sapd|  Missed 8 heartbeats; rebootstrapping
    Aug 10 07:15:09  KERNEL(AP-447_100-TEST@172.20.211.104): [130581.877522] ASAP_FIREWALL_REM_MCAST "211 0 0 1"
    Aug 10 07:15:09  KERNEL(AP-447_100-TEST@172.20.211.104): [130581.882458] wlan_mlme_app_ie_delete: appie is NULL. Do nothing.
    Aug 10 07:15:09  KERNEL(AP-447_100-TEST@172.20.211.104): [130581.882466] wlan_mlme_app_ie_delete: appie is NULL. Do nothing.
    Aug 10 07:15:10  KERNEL(AP-447_100-TEST@172.20.211.104): [130582.932555] wlan_mlme_app_ie_delete: appie is NULL. Do nothing.
    Aug 10 07:15:10  KERNEL(AP-447_100-TEST@172.20.211.104): [130582.932562] wlan_mlme_app_ie_delete: appie is NULL. Do nothing.
    Aug 10 07:15:12  KERNEL(AP-447_100-TEST@172.20.211.104): [130584.166168] ASAP_FIREWALL_REM_MCAST "1 0 2 1"
    Aug 10 07:15:12  KERNEL(AP-447_100-TEST@172.20.211.104): [130584.171424] wlan_mlme_app_ie_delete: appie is NULL. Do nothing.



  • 4.  RE: AP BSSIDs keep going up and down

    MVP
    Posted Aug 10, 2017 01:20 PM

    Missing heartbeats is the only thing I really understand there



  • 5.  RE: AP BSSIDs keep going up and down
    Best Answer

    EMPLOYEE
    Posted Aug 10, 2017 05:33 PM

    Missing heartbeats is enough for an AP to bring the BSSID down.  Did the APS negotiate the proper duplex/speed on their physical connection?  Could there be another physical issue in the path?



  • 6.  RE: AP BSSIDs keep going up and down

    MVP
    Posted Aug 10, 2017 05:38 PM

    Got it, could be, waiting to speak to their network guy and find out. We have another remote site with the same config, different VLANs on the bridge and wired port though and all works fine.

    I'll follow up on this next week and hopefully post the fix. Thanks.



  • 7.  RE: AP BSSIDs keep going up and down

    MVP
    Posted Aug 16, 2017 03:38 PM

    Turned out the issue was the GRE connection to the controller. The firewall at the remote site (where AP is) and main site (where controller is) was doing deep packet inspection, which for some reason was breaking the GRE tunnel. After bypassing inspection, the tunnel came up and the SSIDs stayed on.

     

    Thanks for the help.