Introduction to Hybrid-VPLS and Basic Configuration
Today I am going to talk about the basic configuration of H-VPLS. The IP addresses in the topology are the loopbacks of the U-PE/N-PE devices. The IP addresses of the Clients are what we expect to look direct connected via the H-VPLS core.
Under normal circumstances I would expect the N-PEs to all be a part of the same ISP BGP AS, and the U-PE boxes to be in different BGP AS’s. This would require some type of BGP Inter-AS option to extend the LSP between providers. To keep it simple I just configured a single core and enabled MPLS for the label switched path.
Below is the topology for the reference
 |
| Fig 1.1- H-VPLS Design |
N-PE7 Router:
NPE peer config:
!
l2vpn vfi context VPLS-10
vpn id 10
member 8.8.8.8 encapsulation mpls
!
U-PE peer config:
!
bridge-domain 10
member vfi VPLS-10
member 2.2.2.2 10 encapsulation mpls
member 1.1.1.1 10 encapsulation mpls
!
N-PE8 Router:
!
l2vpn vfi context VPLS-10
vpn id 10
member 7.7.7.7 encapsulation mpls
!
U-PE peer config:
!
bridge-domain 10
member vfi VPLS-10
member 2.2.2.2 10 encapsulation mpls
member 1.1.1.1 10 encapsulation mpls
!
U-PE1 Router:
Attachment Circuit:
!
interface GigabitEthernet4
service instance 10 ethernet
encapsulation dot1q 10
!
Xconnect config:
!
l2vpn xconnect context XC-10
member GigabitEthernet4 service-instance 10
member 8.8.8.8 10 encapsulation mpls group RED priority 9
member 7.7.7.7 10 encapsulation mpls group RED priority 10
!
U-PE-2 Router:
Attachment Circuit:
!
interface GigabitEthernet4
service instance 10 ethernet
encapsulation dot1q 10
!
Xconnect config:
!
l2vpn xconnect context XC-10
member GigabitEthernet4 service-instance 10
member 7.7.7.7 10 encapsulation mpls group RED priority 9
member 8.8.8.8 10 encapsulation mpls group RED priority 10
!
N-PE Output:
NPE-7#sh vfi name VPLS-10
Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No
VFI name: VPLS-10, state: up, type: multipoint, signaling: LDP
VPN ID: 10
Bridge-Domain 10 attachment circuits:
Neighbors connected via pseudowires:
Peer Address VC ID S
2.2.2.2 10 N <<<< Split horizon from N-PE to U-PE is disabled
1.1.1.1 10 N
8.8.8.8 10 Y <<<< Split horizon from N-PE to N-PE is enabled
NPE-7#sh xconn all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri vfi VPLS-10 UP mpls 2.2.2.2:10 UP
SB pri vfi VPLS-10 UP mpls 1.1.1.1:10 SB <<<<< This Xconnect is in Standby Mode
UP pri vfi VPLS-10 UP mpls 8.8.8.8:10 UP
UP pri bd 10 UP vfi VPLS-10 UP
We see the above output becaue the prioity on U-PE1 is configured as follows:
member 8.8.8.8 10 encapsulation mpls group RED priority 9
member 7.7.7.7 10 encapsulation mpls group RED priority 10
From U-PE1 we will prefer 8.8.8.8 (NPE-8) based on lower priority, so the Xconnect from U-PE1 to N-PE7 is in standby.
U-PE Output:
Here is the output from the U-PE which shows the same behavior as above:
UPE-1#sh xconn all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Gi4:10(Eth VLAN) UP mpls 8.8.8.8:10 UP
IA pri ac Gi4:10(Eth VLAN) UP mpls 7.7.7.7:10 SB
