On this submit we are going to configure a primary L2VPN setup utilizing the topology diagram as proven under –
Within the above topology R1 and R4 signify the CE routers on the two completely different websites of a single buyer. R2 & R3 signify the supplier spine router which will likely be offering the L2 connectivity to the CE routers of the shopper.
R1 & R2 are linked by way of serial hyperlink with the encapsulation sort of default which is HDLC. R3 & R4 are linked by way of serial hyperlink with the encapsulation sort of default which is HDLC.
We will have varied kinds of encapsulation between CE and PE routers i.e. HDLC, PPP. Body-relay, ATM and Metro-Ethernet however to maintain it easy we’ve got used the default of HDLC. The encapsulation is stored as HDLC on each the edges however we could have completely different encapsulation as effectively on each the edges.
For instance R1 & R2 will be linked over HDLC encapsulation and R3 & R4 will be linked over every other encapsulation FR, ATM or PPP and many others. On this case we require a bit additional configuration which we are going to talk about within the upcoming posts.
Routers R1 and R2 doesn’t straight peer over L3 as supplier will solely present L2 connectivity and wont peer over L3 and equally between R3 and R4.We are going to type a VC between R1 & R4 after which they are going to peer utilizing OSPF with one another and can be capable to see the prefixes from one another.
Configurations: L2VPN
R1:
ip handle 1.1.1.1 255.255.255.255
ip ospf 1 space 0
!
interface Serial5/0
ip handle 9.9.14.1 255.255.255.0
ip ospf 1 space 0
serial restart-delay 0
R2:
ip handle 9.9.0.2 255.255.255.255
ip ospf 1 space 0
!
interface FastEthernet0/0
ip handle 9.9.23.2 255.255.255.0
ip ospf 1 space 0
mpls ip
!
interface Serial5/0
no ip handle
serial restart-delay 0
xconnect 9.9.0.3 100 encapsulation mpls ##(On this command 9.9.0.3 is peer PE admin Loopack IP and 100 is the VCID)
R3:
ip handle 9.9.0.3 255.255.255.255
ip ospf 1 space 0
!
interface FastEthernet0/0
ip handle 9.9.23.3 255.255.255.0
ip ospf 1 space 0
mpls ip
!
interface Serial5/0
no ip handle
serial restart-delay 0
xconnect 9.9.0.2 100 encapsulation mpls
Be aware: The VCID must be similar on each the ends
R4:
ip handle 4.4.4.4 255.255.255.255
ip ospf 1 space 0
!
interface Serial5/0
ip handle 9.9.14.4 255.255.255.0
ip ospf 1 space 0
serial restart-delay 0
Verification
We see R2 and R3 now type a focused LDP session by utilizing the xconnect command:
R2# sh xconnect all
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Scorching Standby RV=Recovering NH=No {Hardware}
XC ST Section 1 S1 Section 2 S2
——+———————————+–+———————————+–
UP pri ac Se5/0(HDLC) UP mpls 9.9.0.3:100 UP
Above command exhibits the VC 100 is up with encapsulation sort as HDLC.
R2#sh mpls ldp neighbor
TCP connection: 9.9.23.3.40491 – 9.9.0.2.646
State: Oper; Msgs despatched/rcvd: 14/14; Downstream
Up time: 00:06:19
LDP discovery sources:
FastEthernet0/0, Src IP addr: 9.9.23.3
Focused Whats up 9.9.0.2 -> 9.9.0.3, lively
Addresses certain to see LDP Ident:
9.9.23.3 9.9.0.3
On R1 we see the OSPF neighbor ship is up with R4:
R1#sh ip ospf neighbor
4.4.4.4 0 FULL/ – 00:00:33 9.9.14.4 Serial5/0
Additional we see route from R4 on R1 for 4.4.4.4.
R1#sh ip route 4.4.4.4
Identified by way of “ospf 1”, distance 110, metric 65, sort intra space
Final replace from 9.9.14.4 on Serial5/0, 00:07:40 in the past
Routing Descriptor Blocks:
* 9.9.14.4, from 4.4.4.4, 00:07:40 in the past, by way of Serial5/0
Route metric is 65, site visitors share rely is 1
Lastly we see we’re in a position to ping from R1 to R4:
R1#ping 4.4.4.4 supply 1.1.1.1
Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
Packet despatched with a supply handle of 1.1.1.1
!!!!!
Success charge is 100% (5/5), round-trip min/avg/max = 112/132/140 ms
Proceed Studying:
Layer 2 vs Layer 3 VPN – Know the Distinction
Varieties of Digital Personal Community (VPN) & its Protocol
