Community discussions

MikroTik App
 
p3rad0x
Long time Member
Long time Member
Topic Author
Posts: 637
Joined: Fri Sep 18, 2015 5:42 pm
Location: South Africa
Contact:

MPLS/VPLS ECMP

Sat Feb 23, 2019 1:08 pm

Good day,

I'm busy experimenting to transport pppoe over mpls/vpls

Now the issue i'm experiencing is we are using at least 2 microwave links to our main towers because the require from 600-1.2bgps.

As soon as MPLS is enabled between the two sites the traffic starts flowing only over 1 link.

Any way to get around this issue.

BGP based signaling maybe?
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7056
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: MPLS/VPLS ECMP

Mon Feb 25, 2019 10:34 am

You can make VPLS tunnel over each link and then add ECMP route to route over both tunnels.
 
p3rad0x
Long time Member
Long time Member
Topic Author
Posts: 637
Joined: Fri Sep 18, 2015 5:42 pm
Location: South Africa
Contact:

Re: MPLS/VPLS ECMP

Mon Feb 25, 2019 12:46 pm

You can make VPLS tunnel over each link and then add ECMP route to route over both tunnels.
Thanks,

I seem to ran into a different issue,

Only the first tunnel will establish.

I also tried manually specifying the transport address in LDP interface.
[admin@R1] /mpls ldp neighbor> print
Flags: X - disabled, D - dynamic, O - operational, T - sending-targeted-hello, 
V - vpls 
 #      TRANSPORT       LOCAL-TRANSPORT PEER                       SEN
 0 D TV 172.16.1.2                                                 yes
 1 D TV 172.16.0.2                                                 yes
 2 DO   1.1.1.2         172.16.0.1      1.1.1.2:0                  no 
[admin@R1] /interface vpls> print
Flags: X - disabled, R - running, D - dynamic, 
B - bgp-signaled, C - cisco-bgp-signaled 
 0 R   name="vpls1" mtu=1500 l2mtu=1500 mac-address=02:B2:24:43:43:72 
       arp=enabled arp-timeout=auto disable-running-check=no 
       remote-peer=172.16.0.2 vpls-id=1:2 cisco-style=no cisco-style-id=0 
       advertised-l2mtu=1500 pw-type=raw-ethernet use-control-word=default 

 1     name="vpls2" mtu=1500 l2mtu=1500 mac-address=02:B2:24:43:43:72 
       arp=enabled arp-timeout=auto disable-running-check=no 
       remote-peer=172.16.1.2 vpls-id=2:2 cisco-style=no cisco-style-id=0 
       advertised-l2mtu=1500 pw-type=raw-ethernet use-control-word=default 
 
sid5632
Long time Member
Long time Member
Posts: 554
Joined: Fri Feb 17, 2017 6:05 pm

Re: MPLS/VPLS ECMP

Mon Feb 25, 2019 1:28 pm

You have the same MAC address on both interfaces.
It is probably not a good idea to use Winbox's Copy facility for this, which is what I assume you did to end up with it like that.
 
p3rad0x
Long time Member
Long time Member
Topic Author
Posts: 637
Joined: Fri Sep 18, 2015 5:42 pm
Location: South Africa
Contact:

Re: MPLS/VPLS ECMP

Mon Feb 25, 2019 7:31 pm

You have the same MAC address on both interfaces.
It is probably not a good idea to use Winbox's Copy facility for this, which is what I assume you did to end up with it like that.
Thanks, did not even realize.

Did create new interfaces now but still the same behavior
 
sid5632
Long time Member
Long time Member
Posts: 554
Joined: Fri Feb 17, 2017 6:05 pm

Re: MPLS/VPLS ECMP

Tue Feb 26, 2019 4:07 am

Let's see the config. then.
Are you sure the problem isn't at the other end of the link?
 
p3rad0x
Long time Member
Long time Member
Topic Author
Posts: 637
Joined: Fri Sep 18, 2015 5:42 pm
Location: South Africa
Contact:

Re: MPLS/VPLS ECMP

Tue Feb 26, 2019 9:11 am

Let's see the config. then.
Are you sure the problem isn't at the other end of the link?
Here we go
R1
[admin@R1] > export 
/interface bridge
add name=bridge1
add name=bridge2
/interface ethernet
set [ find default-name=ether1 ] disable-running-check=no mtu=1580
set [ find default-name=ether2 ] disable-running-check=no mtu=1580
set [ find default-name=ether3 ] disable-running-check=no
set [ find default-name=ether4 ] disable-running-check=no
/interface vpls
add disabled=no l2mtu=1500 mac-address=02:24:C1:6D:20:B1 name=vpls1 \
    remote-peer=172.16.0.2 vpls-id=1:2
add disabled=no l2mtu=1500 mac-address=02:B2:24:43:43:72 name=vpls2 \
    remote-peer=172.16.1.2 vpls-id=2:2
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/routing ospf instance
set [ find default=yes ] router-id=1.1.1.1
/ip address
add address=172.16.0.1/30 interface=ether1 network=172.16.0.0
add address=172.16.1.1/30 interface=ether2 network=172.16.1.0
add address=1.1.1.1 interface=bridge1 network=1.1.1.1
add address=2.2.2.1 interface=bridge2 network=2.2.2.1
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=ether1
/mpls ldp
set enabled=yes lsr-id=1.1.1.1 transport-address=1.1.1.1
/mpls ldp interface
add interface=ether1 transport-address=172.16.0.1
add interface=ether2 transport-address=172.16.1.1
/routing ospf network
add area=backbone network=1.1.1.1/32
add area=backbone network=172.16.0.0/30
add area=backbone network=172.16.1.0/30
add area=backbone network=2.2.2.1/32
/system identity
set name=R1
R2
/interface bridge
add name=bridge1
add name=bridge2
/interface ethernet
set [ find default-name=ether1 ] disable-running-check=no mtu=1580
set [ find default-name=ether2 ] disable-running-check=no mtu=1580
set [ find default-name=ether3 ] disable-running-check=no mtu=1580
set [ find default-name=ether4 ] disable-running-check=no
/interface vpls
add disabled=no l2mtu=1500 mac-address=02:93:47:97:D4:C9 name=vpls1 \
    remote-peer=172.16.0.1 vpls-id=1:2
add disabled=no l2mtu=1500 mac-address=02:E9:50:DF:D5:BA name=vpls2 \
    remote-peer=172.16.1.1 vpls-id=2:2
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/routing ospf instance
set [ find default=yes ] router-id=1.1.1.2
/ip address
add address=172.16.0.2/30 interface=ether1 network=172.16.0.0
add address=172.16.1.2/30 interface=ether2 network=172.16.1.0
add address=172.16.2.1/30 interface=ether3 network=172.16.2.0
add address=1.1.1.2 interface=bridge1 network=1.1.1.2
add address=2.2.2.2 interface=bridge2 network=2.2.2.2
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=ether1
/mpls ldp
set enabled=yes lsr-id=1.1.1.2 transport-address=1.1.1.2
/mpls ldp interface
add interface=ether1 transport-address=172.16.0.2
add interface=ether2 transport-address=172.16.1.2
add disabled=yes interface=ether3
/routing ospf network
add area=backbone network=172.16.0.0/30
add area=backbone network=172.16.1.0/30
add area=backbone network=172.16.2.0/30
add area=backbone network=1.1.1.2/32
add area=backbone network=2.2.2.2/32
/system identity
set name=R2
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7056
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: MPLS/VPLS ECMP

Tue Feb 26, 2019 10:12 am

You cannot do this setup with LDP signaled VPLS (only one VPLS will be active), here is the example with BGP signaled VPLS:
https://wiki.mikrotik.com/wiki/Transpar ... S_extended
 
p3rad0x
Long time Member
Long time Member
Topic Author
Posts: 637
Joined: Fri Sep 18, 2015 5:42 pm
Location: South Africa
Contact:

Re: MPLS/VPLS ECMP

Thu Feb 28, 2019 8:22 am

You cannot do this setup with LDP signaled VPLS (only one VPLS will be active), here is the example with BGP signaled VPLS:
https://wiki.mikrotik.com/wiki/Transpar ... S_extended
Thanks that seems to work

Only issue now is it creates dynamic interface, if one BGP drops and reconnects the interface name changes, but i will try and figure it out
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7056
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: MPLS/VPLS ECMP

Thu Feb 28, 2019 10:13 am

Two options,
* script that checks if dynamic interface was changed;
* use bridge per dynamic interface and in static configuration work with bridge interface.

Who is online

Users browsing this forum: saahil and 60 guests