Wireless Access

 View Only
  • 1.  Flapping ports

    Posted Oct 13, 2023 05:18 AM

    Hello Team,

    we have several cisco switches and  quite a few APs are connected to these switches

    this is the configuration on the ports for all the Aruba APs.

    switchport trunk native vlan 10

    switchport mode trunk

    The issue that we are experiencing is flapping between ports on all switches.

    I am just wondering what would be the issue, could it be because people on their mobiles moving around the building  and jumping between all the APs ?

    thank you.



  • 2.  RE: Flapping ports

    Posted Oct 13, 2023 09:42 AM
    Edited by chulcher Oct 13, 2023 09:43 AM

    Can you give a better explanation of what you mean by "flapping between ports on all switches"?

    Controller or Instant or AOS 10?  What version of firmware?  What mode is the WLAN configured in?



    ------------------------------
    Carson Hulcher, ACEX#110
    ------------------------------



  • 3.  RE: Flapping ports

    Posted Oct 13, 2023 10:06 PM

    Hi, yes, sorry

    so what I mean when I say flapping is

    "host xxxx.xxxx.xxxx in vlan 12 is flapping between port Gi1/0/1 and port Po12"

    "host cccc.cccc.cccc in vlan 12 is flapping between port Gi1/0/2 and port Gi1/0/10"

    "host cc2c.cc1c.c1cc in vlan 20 is flapping between port Gi1/0/12 and port Gi1/0/10"

    in regards of "Controller or Instant or AOS 10?  What version of firmware?  What mode is the WLAN configured in?"

    cannot answer as these APs are just connected to our network, and not managed by us. 

    I could get all of the information, but what is the purpose of it, is there a known issue with some older firmware versions ?

    Thank you




  • 4.  RE: Flapping ports

    Posted Oct 14, 2023 10:39 AM

    Software version and deployment type for the AP determines whether the AP should be on an access or trunk port.

    The MAC addresses that you are seeing as flapping, is that AP or client MAC addresses?



    ------------------------------
    Carson Hulcher, ACEX#110
    ------------------------------



  • 5.  RE: Flapping ports

    Posted Oct 14, 2023 06:22 PM

    The mac addresses look like client Mac addresses.

    Also will find out the version and deployment type, will let you know, thank you




  • 6.  RE: Flapping ports

    Posted Oct 14, 2023 10:24 PM

    Based on what you've shared, this looks like you are running AOS 10, using a tunneled WLAN.  If that is the case, prune the allowed VLANs on the switchports connected to the APs down to only the AP management VLAN and any bridged WLAN client VLANs.

    AOS 10 requires the user VLANs only be learned by the AP from one method, either locally bridged or through the gateway tunnel.  If the a tunneled client VLAN is spanned out to an AP, you'll end up with the client MAC address hopping around.



    ------------------------------
    Carson Hulcher, ACEX#110
    ------------------------------



  • 7.  RE: Flapping ports

    Posted Oct 16, 2023 01:23 AM

    Hi,

    Did you check for STP? It looks like you have STP problem. 




  • 8.  RE: Flapping ports

    Posted Oct 16, 2023 05:13 AM

    If you configured a bridged SSID, this probably are just clients that are roaming. If client xxxx.xxxx.xxxx is roaming between the AP on port Gi1/0/1 and an AP on a different switch, you would see the client MAC xxxx.xxxx.xxxx move between those ports, which may be reported as flapping. Maybe the client also need to roam back for this message to appear. But with moving/roaming clients, it's expected that the client MAC addresses move from AP to AP.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------