[c-nsp] L2TPv3 "LNS mode"

[Arie Vayner (avayner)]

Gabor,

Yes, this is the right way to make it work.
You need to take into consideration that you are actually running a L2VPN pseudowire over L2TPv3, but the service is actually based on terminating the attachment circuit locally on the router using a L3 interface.

This can also be done using regular L2VPN over MPLS, and L2TPv3 is just a substitute for the MPLS infrastructure, allowing to run MPLS-like services directly over an IP core.

Arie

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Gabor Ivanszky
Sent: Monday, April 27, 2009 10:16
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] L2TPv3 "LNS mode"

Hi,

I received some kind orientation from Cisco on this matter. This
function is called "Routed Pseudowire Support", and is documented at
http://www.cisco.com/en/US/docs/ios/12_2sr/release/notes/122SRrn.html

regards,
Gabor


On Wed, Mar 18, 2009 at 8:58 PM, Gabor Ivanszky <gaborivanszky at gmail.com> wrote:
> Hello,
>
> is there any possibility to route(L3 process) Ethernet encapsulated IP
> packets arriving at a Cisco router in a L2TPv3 tunnel?
>
> In other words, is it possible to configure a Cisco box in LNS role in
> an Ethernet L2TPv3 setup?
>
> " L2TP Network Server (LNS)
>
>      If a given L2TP session is terminated at the L2TP node and the
>      encapsulated network layer (L3) packet processed on a virtual
>      interface, we refer to this L2TP node as an L2TP Network Server" (RFC3931)
>
> Actually i'd like to implement  "(a) LAC-LNS Reference Model:
>
> On one side, the LAC receives traffic
>   from an L2 circuit, which it forwards via L2TP across an IP or other
>   packet-based network.  On the other side, an LNS logically terminates
>   the L2 circuit locally and routes network traffic to the home
>   network.  The action of session establishment is driven by the LAC
>   (as an incoming call) or the LNS (as an outgoing call).
>
>    +-----+  L2  +-----+                        +-----+
>    |     |------| LAC |.........[ IP ].........| LNS |...[home network]
>    +-----+      +-----+                        +-----+
>    remote
>    system
>                       |<-- emulated service -->|
>          |<----------- L2 service ------------>| "(RFC3931)
>
> Practically an Ethernet interface with an xconnect setting on "LAC"
> side, and something like an IP tunnel interface on the "LNS" side.
>
> The obvious
>
> interface Tunnel1
>  tunnel mode l2tpv3
>
> doesn't exist.
>
>
> cheers,
> Gabor
>
_______________________________________________
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/