[c-nsp] H-VPLS/P2MP style functionality with L2TPv3 inside VFI

[Spyros Kakaroukas]

Hey,

My info could be slightly outdated but, IIRC , the me3600 can't do l2tpv3.

On 2 Oct 2014 17:32, James Bensley <jwbensley at gmail.com> wrote:
Hi All,

For reasons way beyond the scope of this mailing list (crazy sales
people, insane customers, ridiculous marketing, promises of gold, the
usual techies nightmare) I'm trying to lab up a hub and spoke L2 VPN
scenario using L2TPv3.

CPEs are ISR G2s such as 1941 and the PE/Hub is an ME3600. I'm not
having much luck so I wondered if I'm chasing a ghost; Has anyone used
L2TPv3 xconnects (due to lack of MPLS) into a VFI on an ME3600 to get
this scenario to work?

Perhaps you used something else that worked? Or do you think this
simply can't be done?

When mixing L2TPv3 with VFIs, is the logic present to do things like
MAC learning, I've never tried this without MPLS and/or BGP.


Something like;


pseudowire-class l2tpv3-class
 encapsulation l2tpv3
 interworking ethernet
 ip local interface looopback 0

l2 vfi TEST manual
 vpn id 100
  bridge-domain 200
  neighbor 1.1.1.1 pw-class l2tpv3-class
  neighbor 2.2.2.2 pw-class l2tpv3-class

int gi0/2
 switchport mode trunk
 switchport trunk allow vlan none
  service instance 200 ethernet
  uncapsulation untagged
  bridge-domain 200

int vlan200
 no ip address


Cheers,
James.
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


This e-mail and any attachment(s) contained within are confidential and are intended only for the use of the individual to whom they are addressed. The information contained in this communication may be privileged, or exempt from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and delete the communication without retaining any copies. Rolaware Hellas SA is not responsible for, nor endorses, any opinion, recommendation, conclusion, solicitation, offer or agreement or any information contained in this communication.