Configuration : vpls

vpls

This document present the NEW, not yet complete process API which is due to be used after the 3.4.x releases.

This statement can be found under the following group:

• BGP/l2vpn
• BGP/group/l2vpn
• BGP/neighbor/l2vpn
• BGP/group/neigbor/l2vpn

with every more specific setting adding to the previous more generic one.

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

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