Controllerless Networks

last person joined: yesterday 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Back to discussions
Expand all | Collapse all

Spanning tree issues with IAP Mesh

This thread has been viewed 2 times

  • 1.  Spanning tree issues with IAP Mesh

    Posted Mar 22, 2013 01:36 PM

    I have a strange issue where spanning-tree is blocking vlans through the mesh.

     

    Here is my set up.

     

    2-Cisco 3560's that have two trunk ports set with do1q and a native vlan of 2. I'm allowing a client vlan (2) and a voice vlan (103) to come over the trunk. They have a native vlan of 2 so the mesh APs can get an address through DHCP.

     

    2-134 IAP's. The point and portal both have an uplink mang. vlan of 1. The Point IAP has bridging enabled. The wired profile is up and is set as a trunk, allowing all vlans, and with a native vlan of 2.

     

    My problem is getting any Vlan besides the native vlan to not get blocked by spanning-tree. I get the following erros:

     

    000129: *Feb 28 19:24:58.289 EST: %SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port FastEthernet0/1 on VLAN0103.
    000130: *Feb 28 19:24:58.448 EST: %SPANTREE-2-LOOPGUARD_UNBLOCK: Loop guard unblocking port FastEthernet0/1 on VLAN0103.

     

    Eventually the loop is cleared and the port is set back to a forwarding state from a blocking state. Spanning-tree is not set on the trunk ports.

     

    As a test I disconnected the APs from their trunk ports. I then used a cross over cable to connect the switches and no spanning tree loops occured. This tells me that the switch config is fine. Is there something I'm missing or overlooking on the mesh config?


    #AP103


  • 2.  RE: Spanning tree issues with IAP Mesh

    Posted Mar 25, 2013 10:21 AM

    I know STP loopguard is blocking the vlan. The simple solution would be to disable loopguard but clearly isn't desireable. How can the mesh network create a vlan loop but a cross over cable doesn't? Is there something in the IAP configuration I should take a look at?