[c-nsp] L2PT over VPLS/VPWS between ME3600X and ASR920 (one for Warris?)

James Bensley jwbensley at gmail.com
Wed Aug 24 12:49:45 EDT 2016


On 24 August 2016 at 17:21, Lukas Tribus <luky-37 at hotmail.com> wrote:
>> ASR920 is 03.16.01a.S
>
> Don't use this image, it will bite you.
> Upgrade to 03.16.02a or even better: 03.16.03a.
>
> Really do this *before* losing any more time on this.

Hi Lukas,

We are settling on 03.16.03a, however the 2nd DC is still in build so
I haven't bumped this up yet. Concentrating on getting the config
working for now.

> Which transport do you want, VPLS or VPWS? Doesn't make sense to troubleshoot both.

Well neither seem to be woorking. Happy to use either that will work.
The documentation seems incorrect, so I don't think I have much choise
but to go through trial and error.

> Also, exactly which l2protocol do you expect to forward? Other than per-vlan spanning-tree I'm don't know any protocols that dot1q tag.

Yeah we are running rapid per-VLAN spanning-tree here.

> I have successfully forwarded cdp, stp, vtp, lacp and udld between a ASR920 and ME3600 in a EPL ("encapsulation default") configuration, and rapid-pvst in a EVPL configuration (since the other protocols don't dot1q tag).

I have had various combinations working between pairs of
ME3600s/ME3800s and obviously port based with ASR920s, but this mix of
ASR920 to ME3600 is giving me stick! EPL and EVPL are metro/carrier
ethernet improvements on port-based pseudowires using EVCs and EFPs on
a specific port. I am simply trying to create pseudowires between a
bridge-domain on each PE, not a specific port or EFP, that will carry
the rapid PVST frames.


Cheers,
James.


More information about the cisco-nsp mailing list