Page 1 of 1

BGP based L2vpls

Posted: Wed Dec 02, 2020 7:51 pm
by nunum
Configured BGP based VPLS on 2 Mikrotik RCS328 routers and put 2 PCs on either end of the tunnel

Tried to ping PC1 from PC2 connected to either but ping failed. how do I make this setup work?

I used "Bridging ethernet segments with VPLS" in http://wiki.mikrotik.com/wiki/Manual:MPLSVPLS and I created a bridge with interface for costumer and VPLS, but I don't got connectivity between two LANs

I tried to connect PC to Ethernet ports of PE routers, interfaces of PE routers do not have addresses.I think connectivity is established, but I cant ping. My configs are as below


[megastart@cbd] > /mpls ldp neighbor print
Flags: X - disabled, D - dynamic, O - operational, T - sending-targeted-hello, V - vpls
# TRANSPORT LOCAL-TRANSPORT PEER SEND-TARGETED ADDRESSES
0 DO 172.16.12.4 172.16.12.1 172.16.12.4:0 no 172.16.10.6
172.16.10.37
172.16.12.4
1 DO 172.16.12.2 172.16.12.1 172.16.12.2:0 no 172.16.10.2
172.16.10.38
172.16.12.2



[megastart@cbd] > /mpls ldp interface print
Flags: X - disabled, I - invalid
# INTERFACE HELLO-INTERVAL HOLD-TIME
0 sfp-sfpplus1 5s 15s
1 sfp-sfpplus3 5s 15s
[megastart@cbd] >


[megastart@cbd] > mpls forwarding-table print
Flags: H - hw-offload, L - ldp, V - vpls, T - traffic-eng
# IN-LABEL OUT-LABELS DESTINATION INTERFACE NEXTHOP
0 expl-null
1 L 42 172.16.10.36/30 sfp-sfpplus3 172.16.10.6
2 L 44 41.57.66.132/30 ether8 172.16.10.62
3 L 45 172.16.12.4/32 sfp-sfpplus3 172.16.10.6
4 L 46 172.16.12.2/32 sfp-sfpplus1 172.16.10.2
5 L 47 172.16.12.14/32 ether8 172.16.10.62
6 L 49 10.70.85.0/24 Loopback 10.255.20.1
7 L 50 172.16.10.57/32 Loopback 10.255.20.1
8 V 55 vpls3
[megastart@cbd] >



[megastart@cbd] > mpls remote-binding print
Flags: X - disabled, A - active, D - dynamic
# DST-ADDRESS NEXTHOP LABEL PEER
0 AD 172.16.12.2/32 172.16.10.2 impl-null 172.16.12.2:0
1 D 41.57.66.132/30 125 172.16.12.2:0
2 D 172.16.12.4/32 127 172.16.12.2:0
3 D 172.16.12.1/32 120 172.16.12.2:0
4 D 172.16.10.60/30 121 172.16.12.2:0
5 D 172.16.12.14/32 124 172.16.12.2:0
6 D 172.16.10.36/30 impl-null 172.16.12.2:0
7 D 172.16.10.4/30 128 172.16.12.2:0
8 D 172.16.10.48/30 122 172.16.12.2:0
9 D 172.16.10.0/30 impl-null 172.16.12.2:0
10 D 41.57.66.132/30 48 172.16.12.4:0
11 D 172.16.12.1/32 49 172.16.12.4:0
12 D 172.16.12.2/32 50 172.16.12.4:0
13 D 172.16.10.60/30 51 172.16.12.4:0
14 AD 172.16.12.4/32 172.16.10.6 impl-null 172.16.12.4:0
15 D 172.16.12.14/32 53 172.16.12.4:0
16 AD 172.16.10.36/30 172.16.10.6 impl-null 172.16.12.4:0
17 D 172.16.10.4/30 i.mpl-null 172.16.12.4:0
18 D 172.16.10.48/30 54 172.16.12.4:0
19 D 172.16.10.0/30 55 172.16.12.4:0
20 D 10.255.20.0/24 131 172.16.12.2:0
21 D 10.255.20.0/24 58 172.16.12.4:0
[megastart@cbd] >

[megastart@cbd] > interface vpls print

Flags: X - disabled, R - running, D - dynamic, B - bgp-signaled, C - cisco-bgp-signaled
0 RDB name="vpls3" mtu=1500 l2mtu=1522 mac-address=02:92:E6:27:2D:5E arp=enabled arp-timeout=auto disable-running-check=no remote-peer=172.16.12.4 cisco-style=no cisco-style-id=0 advertised-l2mtu=1522
pw-type=raw-ethernet use-control-word=no vpls=Bgp_vpls

[megastart@cbd] >