Wired

last person joined: 7 hours ago 

Bring performance and reliability to your network with the Aruba Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of the ArubaOS-Switch and ArubaOS-CX devices, and find ways to improve security across your network to bring together a mobile first solution.
Expand all | Collapse all

Mobility Access Switches - Error - Flushing port

Jump to Best Answer
  • 1.  Mobility Access Switches - Error - Flushing port

    Posted Apr 05, 2013 02:31 PM

    Does know what this means?  I am reviewing the logs, and this is something that caught my attention.

     

     <WARN> |l2m|  Flushing port GE3/0/16

     

    Thanks,

     

    Dave Hall



  • 2.  RE: Mobility Access Switches - Error - Flushing port
    Best Answer

    Posted Apr 05, 2013 02:37 PM

    Dave,

    That is log entry indicating that we are clearing the mac-address-table entries for a given port. You typically see it due to ports flapping which may result in STP Topology Change Notifications which is why we recommend enabling "portfast" on access ports.

     

    Best regards,

     

    Madani



  • 3.  RE: Mobility Access Switches - Error - Flushing port

    Posted Jul 22, 2013 04:56 PM

    What if you see it on trunk ports?



  • 4.  RE: Mobility Access Switches - Error - Flushing port

    Posted Jul 22, 2013 06:36 PM

    Its for the same reason. The switch is receiving a TCN and so it is clearing the mac-address-table entries.



  • 5.  RE: Mobility Access Switches - Error - Flushing port

    Posted Jul 25, 2013 12:28 PM
    Is there a way to turn on port fast on a trunk port? I thought I read somewhere it is unavailable. If that's the case do we have to live with the errors?

    Thanks


  • 6.  RE: Mobility Access Switches - Error - Flushing port

    Posted Jul 25, 2013 12:49 PM

    Unfortunately not at this time. I recommened you submit a feature request via the Idea Portal.

     

    https://arubanetworkskb.secure.force.com/cp/ideas/ideaList.apexp

     

    I wouldn't describe these as errors but normal behavior as a result of a spanning-tree topology change. Are these trunks going to user devices as opposed to other switches and as such they may go up and down with great frequency? I'm trying to understand what is generating the STP changes.

     

    Bst regards,

     

    Madani



  • 7.  RE: Mobility Access Switches - Error - Flushing port

    Posted Jul 25, 2013 12:55 PM
    Thank you for your response. These are trunk ports connecting to Cisco 3560 switches and it is mainly just annoying getting these. By enabling the port fast on the access ports we cleared up those, but still see these.

    Thanks


  • 8.  RE: Mobility Access Switches - Error - Flushing port

    Posted Jul 25, 2013 07:21 PM

    Since these are connections to other switches you don't actually want to have portfast enabled. Portfast on trunks is meant to be used with end devices like IP phones that don't participate in STP (e.g. BPDUs) so that the port transitions to forwarding as quickly as possible, trunks to other switches on the other hand should go through the STP process to ensure there isn't a loop in the network.

     

    So if you are seeing "flushing" a lot, that indicates we are receiving a lot of TCNs or seeing trunk links go up/down. You may want to check the interface stats to see how frequently they have flapped or check the other switches to see whether they have portfast enabled or disabled, if disabled they may be generating the TCNs which we are responding to.

     

    Best regards,

     

    Madani