[c-nsp] VPLS to multiple end points

aaron1 at gvtc.com aaron1 at gvtc.com
Fri May 28 13:05:41 EDT 2021

Option 1 - VPLS can be manual (using only LDP and you *typing in the
neighbor ip addresses* to land the pw's on)

Option 2 - VPLS can be auto-neighbor discovered...
- BGP does the AD (auto discovery, that is, for the PE's participating in
the vpls)
- PW/LSP set up - can be signaled via BGP or LDP (RFC 4761 or 4762

Of course with option 2 you need to fire up bgp on those pe's, I use a
private AS (64512-65535, pick one)... immediately consider RR, and dual RR
hub at that....

I thought I had some config from when I tested vpls on 920's a few years
ago, but I do have asr903 configs, which might be similar, just verify
before you go using these configs... sharing some stuff I had from my
previous lab tests...

This appears to be an RFC 4762 config...

lab-903-1 - 03.16.00.S

interface GigabitEthernet0/5/3
 no ip address
 negotiation auto
 service instance 1 ethernet
  encapsulation untagged

l2vpn vfi context v100
 vpn id 10100
 autodiscovery bgp signaling ldp
  vpls-id 65535:10100
  route-target export 65535:10100
  route-target import 65535:10100
  no auto-route-target

bridge-domain 100
 member GigabitEthernet0/5/3 service-instance 1
 member vfi v100

interface BDI100
 ip address

router bgp 64512
 bgp router-id
 no bgp default ipv4-unicast
 neighbor remote-as 64512
 neighbor update-source Loopback0

 address-family l2vpn vpls
  neighbor activate
  neighbor send-community extended
  neighbor prefix-length-size 2

NOTES.. Just like ME3600, ASR903 cannot change 4761 to 4762 within the vfi
on-the-fly.. Must delete and recreate.

eng-lab-903-1(config)#l2vpn vfi context v100
eng-lab-903-1(config-vfi)#autodiscovery bgp signaling ldp
% VFI auto-discovery signaling protocol changes are not allowed. Delete the
VFI and reconfigure.

eng-lab-903-1(config-vfi)#no l2vpn vfi context v100
% VFI removal failed. Please remove references to VFI before removal.

eng-lab-903-1(config)#do sh run | sec bridge-domain 100
bridge-domain 100
 member GigabitEthernet0/5/3 service-instance 1
no member vfi v100

Also, again, I didn't like all PE's having same RD (auto) so I did
this.again, it worked without this, I mean it worked in auto RD mode, but I
did this anyway.  Not sure what is best practice.

conf t
l2vpn vfi context v100
autodiscovery bgp signaling ldp
-> rd

More information about the cisco-nsp mailing list