Design Guide

Chapter 7 VPLS using BGP auto discovery
VPLS CLI and implementational differences
There is a distinct difference as how the split horizon groups are implemented in ME/CISCO ASR 903
platforms and CISCO ASR 9000. This is important to understand while configuring HVPLS or E-TREE based
deployment scenario.
CISCO ME3600X/3800X and CISCO ASR 903
CISCO ASR 9000
1. To disable split-horizon on a psuedowire, the
configuration is straight forward as mentioned
below, where you use a “no-split-horizon”
option with the neighbor command under VFI :
l2 vfi VPLS manual
vpn id 455
neighbor 1.1.1.1 encapsulation mpls no-split-
horizon
2. To enable split-horizon on an EFP or service
instance. The command used to configure it is :
inteface GigabitEthernet0/4
service instance 1 ethernet
encapsulation default
bridge-domain 100 split-horizon-group 0
In ME/CISCO ASR 903 platforms the EFPs that
are in the same bridge domain and split-horizon
group cannot forward data between each other.
EFPs can be configured in 3 split-horizon groups
1. On CISCO ASR 9000 to disable split-
horizon for psuedowire/neighbor. The
neighbor statement has to be configured
under the bridge-domain and outside the vfi
CLI. Below is the configuration :
l2vpn
bridge group VPLS
bridge-domain VPLS
neighbor 1.1.1.1 pw-id 100
!
vfi vpls
neighbor 2.2.2.2 pw-id 200
!
!
In a H-VPLS based deployment all the
CORE psedowires are configured under VFI
and the SPOKE psuedowires outside VFI
under bridge-domain.
2. To enable split-horizon on an EFP. The
commands are as below on CISCO ASR
9000.
l2vpn
bridge group VPLS
bridge-domain VPLS
interface GigabitEthernet0/2/0/0.100
split-horizon group
!