don't think you can filter BPDUs on the PE if you're using this type of
setup (you might be able to do if you used SVI/Vlan-based eompls, i.e.
with an interface Vlan and bpdu filter/mac-acl), so you need to address
this PVID inconsistency issue on the CE, either by disabling STP for the
Vlan (as you already suggested), or by enabling BPDU fulter on the CE
switches, which looks like a better option.
oli
[EMAIL PROTECTED] <> wrote on Wednesday, May 16, 2007 12:40 PM:
> hello,
>
> did everybody use the same vlan id on both ends of the "vlan based
> eompls tunnel" ? is anyone here that use different vlans, who can
> give me an answer to my question ?
>
> thanks,
> liviu.
>
> On Tuesday 15 May 2007 15:34, [EMAIL PROTECTED] wrote:
>> hello,
>>
>> topology:
>> Host1 --> switches -->PE --eompls--PE <-- switches <- Host2
>>
>> config PE (7604 sup 720 / IOS SRA3):
>> subinterface + encapulation dot1q vlan X + xconnect (MUX-UNI)
>>
>> problem:
>> if vlan X for Host1 is different then vlan X for Host 2, on the first
>> switch connected directly to PE we will have STP bloking state at
>> VlanX.
>>
>> questions:
>> is there a possibility to solve that, except "spann disable on vlan
>> X"
>> or "spann bpdu filter enable" on switches, or the same vlan X on
>> both ends ? can i filter somehow bpdu throught the eompls tunnel ?
>>
>> thank you,
>> liviu.
>> _______________________________________________
>> cisco-nsp mailing list [email protected]
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
> _______________________________________________
> cisco-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
