[c-nsp] private/port-based l2vpn service

Pshem Kowalczyk pshem.k at gmail.com
Tue Oct 29 16:11:27 EDT 2013


The easiest way to do that is to use 'encapsulation default':

interface GigabitEthernet0/5
 description Test INT VPLS
 switchport trunk allowed vlan none
 switchport mode trunk
 mtu 9000
 load-interval 30
 media-type rj45
 service-policy output PM-INT-1G-OUT
 service instance 304 ethernet
  encapsulation default
  l2protocol forward
  service-policy input PM-CUST-DEFAULT-100M-BD-IN
  service-policy output PM-CUST-DEFAULT-100M-OUT
  bridge-domain 304

This configuration forwards all frames received on the physical port
into a bridge domain (you can also forward it using a xconnect).

kind regards

On 30 October 2013 08:44, Aaron <aaron1 at gvtc.com> wrote:
> As MEF calls an l2vpn, private/port-based (which carries all, tagged or
> untagged frames) that arrive at an interface.. EPL, EPLAN, EPTREE, I
> understand the asr9k would implement this with.
> Int g0/0/0/0
> L2transport
> With no encap needed.  And then you would simply add that interface to the
> xconnect group:p2p or bg:bd.
> Question, what is the interface config for doing this exact same thing on an
> ME3600X ?
> Aaron
> _______________________________________________
> 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/

More information about the cisco-nsp mailing list