Community discussions

 
ukzerosniper
Member Candidate
Member Candidate
Topic Author
Posts: 118
Joined: Tue Jul 23, 2013 9:20 pm

MPLS TE 2x 1gbps point to point links

Sun Jan 13, 2019 11:23 pm

Hi Guys,

I borrowed the ascii art idea from another thread to which I have a similar issue, but not the same.

I have two sites linked with a Siklu 2500FX (2gbps radio over 2x 1gbps ethernet at each side).

I have eth1 on R1 connected to Eth1 on the siklu at site one.
I have eth2 on R1 connected to Eth2 on the siklu at site one.

I have eth1 on R2 connected to Eth1 on the siklu at site two.
I have eth2 on R2 connected to Eth2 on the siklu at site two.

Currently, I run OSPF ECMP across the links and everything works great! However, we now want to deploy MPLS on the network.

MikroTik support told me that we can achieve the same or similar results using TE with MPLS. Without TE MPLS only uses 1 of the links. It doesnt use both.

What I think I would like to do is setup TE between R1 and R2 in a way that it will use Eth1 <---> Eth1 up to 900Mbps then start using Eth2 <----> Eth2 up to 900Mbps.

I have spent maybe 20hours or so in GNS3 trying to figure this out with no luck. Is there anyone here that can come and save the day and show me how to create a config along these lines.

Thanks guys.
		Eth1----> Siklu2500FX Eth1 ~~~Wireless link~~~ Siklu2500FX Eth1 <----Eth1
Site1----- R1											R2 ----- Site2
		Eth1----> Siklu2500FX Eth1 ~~~Wireless link~~~ Siklu2500FX Eth1 <----Eth1
			
 
mducharme
Trainer
Trainer
Posts: 716
Joined: Tue Jul 19, 2016 6:45 pm

Re: MPLS TE 2x 1gbps point to point links

Mon Jan 14, 2019 12:53 am

Hi,

This is accomplished by forcing one VPLS tunnel across one TE tunnel and the other VPLS tunnel across the other TE tunnel. The VPLS tunnels can then be used for load balancing.
 
ukzerosniper
Member Candidate
Member Candidate
Topic Author
Posts: 118
Joined: Tue Jul 23, 2013 9:20 pm

Re: MPLS TE 2x 1gbps point to point links

Mon Jan 14, 2019 1:25 am

Hi,

This is accomplished by forcing one VPLS tunnel across one TE tunnel and the other VPLS tunnel across the other TE tunnel. The VPLS tunnels can then be used for load balancing.
Hi @mducharme,

Would you be able to share an example config for me that I could use to understand how this would function?

I want this link to be functional so that it can function as a normal segment in the MPLS core so that my BGP signaled VPLS connections for the end users can pass it without issue.

Thanks for your response, I really do appreciate all the help I can get at the moment as this is totally new to me.

Thanks again.
 
ukzerosniper
Member Candidate
Member Candidate
Topic Author
Posts: 118
Joined: Tue Jul 23, 2013 9:20 pm

Re: MPLS TE 2x 1gbps point to point links

Mon Jan 14, 2019 3:44 pm

Hi Guys,

I managed to get RSVP TE tunnel up and running between the two routers but traffic doesn't pass over it.

I notice that the RSVP TE shows up as an Interface in the router.

Should I configure an OSPF connection between the two routers on the RSVP TE interfaces?

The issue I am currently having is that traffic is not passing over the RSVP TE connection, it is still passing via the normal interfaces.

Any assistance would be great.
 
mducharme
Trainer
Trainer
Posts: 716
Joined: Tue Jul 19, 2016 6:45 pm

Re: MPLS TE 2x 1gbps point to point links

Tue Jan 15, 2019 1:45 am

Hi Guys,

I managed to get RSVP TE tunnel up and running between the two routers but traffic doesn't pass over it.

I notice that the RSVP TE shows up as an Interface in the router.

Should I configure an OSPF connection between the two routers on the RSVP TE interfaces?

The issue I am currently having is that traffic is not passing over the RSVP TE connection, it is still passing via the normal interfaces.

Any assistance would be great.
View the status of your VPLS tunnel - it should show the TE tunnel name in the "transport" field if it is using the TE tunnel. You will not generally see traffic on the TE interface itself, so you can't really use that as a way of determining whether it is working or not.
 
ukzerosniper
Member Candidate
Member Candidate
Topic Author
Posts: 118
Joined: Tue Jul 23, 2013 9:20 pm

Re: MPLS TE 2x 1gbps point to point links

Sun Feb 03, 2019 8:45 pm

Hi Guys.

I am still having no luck with this.

Could you take a quick look at the configuration below and let me know what im missing? This is from a GNS3 lab I have created to simulate some of these configurations and to try and learn about TE Tunnels.

Thanks guys.

First Router

[admin@R5_ISP_CORE1] > ip address print 
Flags: X - disabled, I - invalid, D - dynamic 
 #   ADDRESS            NETWORK         INTERFACE                                  
 0   192.168.100.1/30   192.168.100.0   ether2 - ISP CORE1 --> ISP CORE2_OSPF (Link
 1   10.0.0.1/32        10.0.0.1        LOOPBACK                                   
 2   192.168.100.5/30   192.168.100.4   ether3 - ISP CORE1 --> ISP CORE2_OSPF (Link
 3   192.168.100.21/30  192.168.100.20  ether4 - ISP CORE1 --> ISP CORE5_OSPF      
 4   192.168.50.2/30    192.168.50.0    ether1 - ISP CORE1 --> ISP_WAN_Connection_O
 5   192.168.100.29/30  192.168.100.28  ether1 - ISP CORE1 --> ISP_WAN_Connection_O
[admin@R5_ISP_CORE1] > 


[admin@R5_ISP_CORE1] > /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   10.0.0.5        10.0.0.1        10.0.0.5:0                 no            10.0.0.5       
                                                                                 192.168.100.18 
                                                                                 192.168.100.22 
                                                                                 192.168.100.69 
 1 DO   10.0.0.2        10.0.0.1        10.0.0.2:0                 no            10.0.0.2       
                                                                                 172.16.1.2     
                                                                                 192.168.100.2  
                                                                                 192.168.100.6  
                                                                                 192.168.100.9  
                                                                                 192.168.100.33 
 2 DO   10.0.0.100      10.0.0.1        10.0.0.100:0               no            10.0.0.100     
                                                                                 192.168.100.30 
                                                                                 192.168.123.2  
                                                                                 192.168.184.131



[admin@R5_ISP_CORE1] > mpls traffic-eng export verbose          
# feb/03/2019 18:33:01 by RouterOS 6.43.8
# software id = 
#
#
#
/mpls traffic-eng interface
add bandwidth=0bps blockade-k-factor=2 disabled=no down-flood-thresholds=\
    15,30,45,60,75,80,85,90,95,97,98,99,100 igp-flood-period=3m interface=\
    "ether2 - ISP CORE1 --> ISP CORE2_OSPF (Link1)" k-factor=2 refresh-time=10s resource-class=0 te-metric=1 \
    up-flood-thresholds=15,30,45,60,75,80,85,90,95,97,98,99,100 use-udp=no
add bandwidth=0bps blockade-k-factor=2 disabled=no down-flood-thresholds=\
    15,30,45,60,75,80,85,90,95,97,98,99,100 igp-flood-period=3m interface=\
    "ether3 - ISP CORE1 --> ISP CORE2_OSPF (Link2)" k-factor=2 refresh-time=10s res
    up-flood-thresholds=15,30,45,60,75,80,85,90,95,97,98,99,100 use-udp=no
/mpls traffic-eng tunnel-path
add !affinity-exclude !affinity-include-all !affinity-include-any disabled=no !hold
    192.168.100.2:strict name="ISP CORE1 --> CORE2 (Link1)" !record-route !reoptimi
    use-cspf=no
add !affinity-exclude !affinity-include-all !affinity-include-any disabled=no !hold
    192.168.100.6:strict name="ISP CORE1 --> CORE2 (Link2)" !record-route !reoptimi
    use-cspf=no




[admin@R5_ISP_CORE1] > interface traffic-eng export verbose 
# feb/03/2019 18:33:40 by RouterOS 6.43.8
# software id = 
#
#
#
/interface traffic-eng
add !affinity-exclude !affinity-include-all !affinity-include-any auto-bandwidth-av
    auto-bandwidth-range=0bps auto-bandwidth-reserve=0% auto-bandwidth-update-inter
    bandwidth-limit=disabled disable-running-check=no disabled=no from-address=10.0
    1500 name="ISP CORE1 --> CORE2" primary-path="ISP CORE1 --> CORE2 (Link1)" prim
    !record-route !reoptimize-interval secondary-paths="ISP CORE1 --> CORE2 (Link2)
    to-address=10.0.0.2

Second Router
[admin@R6_ISP_CORE2] > ip address print
Flags: X - disabled, I - invalid, D - dynamic 
 #   ADDRESS            NETWORK         INTERFACE                                  
 0   192.168.100.2/30   192.168.100.0   ether2 - ISP CORE2 --> ISP CORE1_OSPF (Link
 1   10.0.0.2/32        10.0.0.2        LOOPBACK                                   
 2   192.168.100.6/30   192.168.100.4   ether3 - ISP CORE2 --> ISP CORE1_OSPF (Link
 3   192.168.100.9/30   192.168.100.8   ether4 - ISP CORE2 --> ISP CORE3_OSPF      
 4   192.168.100.33/30  192.168.100.32  ether5 - ISP CORE2 --> ISP CORE7_(DNS2)    
 5 D 172.16.1.2/32      172.16.22.1     <pppoe-Customer1>                          


[admin@R6_ISP_CORE2] > 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   10.0.0.3        10.0.0.2        10.0.0.3:0                 no            10.0.0.3       
                                                                                 192.168.100.10 
                                                                                 192.168.100.13 
                                                                                 192.168.100.25 
                                                                                 192.168.100.37 
 1 DO   10.0.0.7        10.0.0.2        10.0.0.7:0                 no            10.0.0.7       
                                                                                 192.168.100.34 
 2 DO   10.0.0.1        10.0.0.2        10.0.0.1:0                 no            10.0.0.1       
                                                                                 192.168.50.2   
                                                                                 192.168.100.1  
                                                                                 192.168.100.5  
                                                                                 192.168.100.21 
                                                                                 192.168.100.29 


[admin@R6_ISP_CORE2] > mpls traffic-eng export verbose                               
# feb/03/2019 18:33:06 by RouterOS 6.43.8
# software id = 
#
#
#
/mpls traffic-eng interface
add bandwidth=0bps blockade-k-factor=2 disabled=no down-flood-thresholds=\
    15,30,45,60,75,80,85,90,95,97,98,99,100 igp-flood-period=3m interface=\
    "ether3 - ISP CORE2 --> ISP CORE1_OSPF (Link2)" k-factor=2 refresh-time=10s res
    up-flood-thresholds=15,30,45,60,75,80,85,90,95,97,98,99,100 use-udp=no
add bandwidth=0bps blockade-k-factor=2 disabled=no down-flood-thresholds=\
    15,30,45,60,75,80,85,90,95,97,98,99,100 igp-flood-period=3m interface=\
    "ether2 - ISP CORE2 --> ISP CORE1_OSPF (Link1)" k-factor=2 refresh-time=10s res
    up-flood-thresholds=15,30,45,60,75,80,85,90,95,97,98,99,100 use-udp=no
/mpls traffic-eng tunnel-path
add !affinity-exclude !affinity-include-all !affinity-include-any disabled=no !hold
    192.168.100.1:strict name="ISP CORE2 --> CORE1 (Link1)" !record-route !reoptimi
    use-cspf=no
add !affinity-exclude !affinity-include-all !affinity-include-any disabled=no !hold
    192.168.100.5:strict name="ISP CORE2 --> CORE1 (Link2)" !record-route !reoptimi
    use-cspf=no


[admin@R6_ISP_CORE2] > interface traffic-eng export verbose 
# feb/03/2019 18:33:28 by RouterOS 6.43.8
# software id = 
#
#
#
/interface traffic-eng
add !affinity-exclude !affinity-include-all !affinity-include-any auto-bandwidth-av
    auto-bandwidth-range=0bps auto-bandwidth-reserve=0% auto-bandwidth-update-inter
    bandwidth-limit=disabled disable-running-check=no disabled=no from-address=10.0
    1500 name="ISP CORE2 --> CORE1 " primary-path="ISP CORE2 --> CORE1 (Link1)" pri
    !record-route !reoptimize-interval secondary-paths="ISP CORE2 --> CORE1 (Link2)
    to-address=10.0.0.1

Who is online

Users browsing this forum: No registered users and 4 guests