Yes :-). This error may happen when you have two switches interconnected with 802.1q trunks, and you are running PVST+ and a wrong VLAN is detected in incoming BPDUs.
The method switches use to detect VLAN inconsistency is by using an extension to the Bridge Priority field in BPDU called Extended System ID (sys-id-ext). If APs don't support sys-id-ext, then the priority they set in BPDUs will be incorrect from switches' perspective. There are several generic workarounds: 1. Make sure native VLANs match on two sides 2. Run MST 3. Turn off STP on your APs (could lead to bad things, with bridging involved) Hope this helps. -- Marko Milivojevic - CCIE #18427 (SP R&S) Senior CCIE Instructor / Managing Partner - IPexpert On Mon, Mar 11, 2013 at 7:49 AM, Jaffar Nassiry <[email protected]> wrote: > Hi All, > > I am have two 3502s setup in a bridge(RAP)/non-bridge(MAP), both APs > connect to switches that are configured as trunks. I have enabled Ethernet > bridging on both AP as well as enable VLAN transparent bridging. I am > running into a spanningtree issue on the switch side of both APs > > %SPANTREE-2-RECV-PVID-ERR: Received PBDU with inconsistent peer vlan id 10 > on Fas... > > Then goes through the STP process of blocking, but cylces back around and > goes to learning...and so forth. Seems like an infinite loop. The correct > VLANs are configured on both side(AP and Switch) > > Has anyone run into this issue before? > > Jaffar Nassiry > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
