[c-nsp] l2vpn vpls w/bgp autodiscovery - me3600x to asr9k

[Pete Lumbis]

(assuming I understand your question correctly)

We are breaking VPLS into two pieces:

discovery (who are my VPLS peers)
signaling (what labels do those peers want to use)

For both of these pieces we have two options.

Discovery can be done either manually
l2 vfi blue manual
  vpn id 100
  neighbor 192.168.1.1
  neighbor 192.168.1.2

or automatically
l2 vfi blue autodiscovery
 vpn id 100

If we are using auto discovery we just attach the L2 AFI to our BGP peers.
If they support it we look at their VPN IDs and add them to a list of peers
for that VPN Identifier (VFI).

Once we have a list of interested parties we need to exchange labels. Again
two options:
LDP (think P to P)
BGP (think L3VPN PE to PE)

Why use one over the other is a philosophical argument.

For most Cisco implementations of autodiscovery we will use BGP to build
the list of peers that we will make targeted LDP sessions to.

Hope this helps.

-Pete



On Mon, Jan 7, 2013 at 10:37 AM, Aaron <aaron1 at gvtc.com> wrote:

>
> ...also, the idea for bgp OR ldp for the signaling portion....does the
> targeted ldp neighbor session mean that these devices are using ldp for
> signaling within the vpls w/bgp autodiscovery architecture OR does the ldp
> targeted neighbor session exists *regardless* ?