Configuration : L2VPN VPLS

L2VPN

VPLS

Syntax

l2vpn {
   vpls <name> {
      endpoint <number>;
      base <number>;
      offset <number>;
      size <number>;
      rd <ip>:<number>|<number>:<number>;
      next-hop <IPv4>;
      origin IGP|EGP|INCOMPLETE;
      as-path [ <number> ...];
      med <number>;
      local-preference <number>;
      originator-id <IPv4>;
      cluster-list [ <IPv4> ... ];
      community [ <number> ... ];
      extended-community [ <extended community> .. ];
      withdraw;
}

---

endpoint

vpls endpoint id

base

vpls label base

offset

vpls block offet

size

vpls block size

rd or route-distinguisher

route-distinguisher

extended community can be one of :

Each entry can be one of :

• route target

    target|origin:<number>:<ipv4> target|origin:<IPv4>:<number>
  

• hex number prepended with 0x

    0x0002FDE800000001
  

• l2info with the number being encapsulation, control, MTU and reserved

    l2info:<number>:<number>:<number:<number>
  

withdraw

The route should not be announced when ExaBGP starts