te tunnel path

RouterOS Forwarding Protocols
1

I’ve setup a test lab very similar to the MPLSVPLS example on the wiki page. My problem is with TE tunnels and it not choosing the shortest path when using CSPF and some confusing route paths. When I create a TE tunnel from R1 to R5 the path used is R1,R2,R3,R4,R5. When I create a TE tunnel from R5 to R1 it uses the correct/shortest path of R5,R3,R2,R1. If anyone wants part of the configuration posted let me know. Here is a traceroute from R1 to R5

/tool traceroute 192.168.0.18
     ADDRESS                                    STATUS
   1     192.168.0.2 4ms 3ms 4ms 
   2     192.168.0.6 5ms 5ms 5ms 
   3    192.168.0.18 11ms 13ms 7ms

From R1 to R4 with extra route???

/tool traceroute 192.168.0.17
     ADDRESS                                    STATUS
   1     192.168.0.2 6ms 4ms 3ms 
   2     192.168.0.6 5ms 5ms 4ms 
   3    192.168.0.14 10ms 9ms 6ms 
   4    192.168.0.17 8ms 7ms 8ms

R1 to R5 using loopback

/tool traceroute 10.255.255.5 src-address=10.255.255.1
     ADDRESS                                    STATUS
   1     192.168.0.2 9ms 8ms 9ms 
                      mpls-label=17
   2     192.168.0.6 11ms 9ms 7ms 
                      mpls-label=17
   3    10.255.255.5 6ms 9ms 6ms

R1 to R4 using loopback

/tool traceroute 10.255.255.4 src-address=10.255.255.1 
     ADDRESS                                    STATUS
   1     192.168.0.2 12ms 8ms 8ms 
                      mpls-label=19
   2     192.168.0.6 13ms 8ms 7ms 
                      mpls-label=19
   3    10.255.255.4 8ms 6ms 6ms

TE tunnel on R1

/interface traffic-eng monitor 0 once 

             tunnel-id: 4
    primary-path-state: established
          primary-path: dyn
  secondary-path-state: not-necessary
           active-path: dyn
          active-lspid: 1
          active-label: 22
        explicit-route: "S:192.168.0.2/32,S:192.168.0.5/32,S:192.168.0.6/32,
                        S:192.168.0.9/32,S:192.168.0.10/32,S:192.168.0.17/32,
                        S:192.168.0.18/32"
        recorded-route: "192.168.0.5[22],192.168.0.9[22],192.168.0.17[38],
                        192.168.0.18[0]"
    reserved-bandwidth: 60.0Mbps

If I add a 192.168.0.13:loose to the tunnel path then it will traverse over the shorter route. I’m just trying to understand why this isn’t the default behaviour.

 tunnel-id: 9
    primary-path-state: established
          primary-path: static-test
  secondary-path-state: not-necessary
           active-path: static-test
          active-lspid: 1
          active-label: 26
        explicit-route: "S:192.168.0.2/32,S:192.168.0.5/32,S:192.168.0.6/32,
                        S:192.168.0.13/32,S:192.168.0.14/32"
        recorded-route: "192.168.0.5[26],192.168.0.13[26],192.168.0.14[0]"
    reserved-bandwidth: 60.0Mbps

Here is my ip configuration on the routers with the 10.255.255 addresses being the loopback bridge.

R1
10.255.255.1/32
192.168.0.1/30

R2
10.255.255.2/32
192.168.0.2/30
192.168.0.5/30

R3
10.255.255.3/32
192.168.0.6/30
192.168.0.9/30
192.168.0.13/30

R4
10.255.255.4/32
192.168.0.10/30
192.168.0.17/30

R5
10.255.255.5/32
192.168.0.14/30
192.168.0.18/30

2

bump?

3

Two first traceroutes suggest that regular routing in your setup is somehow going asymmetrically. Please post routing tables of R3,R4 and R5.

4 
[admin@R3] > /ip route print   
Flags: X - disabled, A - active, D - dynamic, 
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, 
B - blackhole, U - unreachable, P - prohibit 
 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADS  0.0.0.0/0                          10.250.1.1         0       
 1 ADC  10.250.1.0/24      10.250.1.148    ether4             0       
 2 ADo  10.255.255.1/32                    192.168.0.5        110     
 3 ADo  10.255.255.2/32                    192.168.0.5        110     
 4 ADC  10.255.255.3/32    10.255.255.3    lobridge           0       
 5 ADo  10.255.255.4/32                    192.168.0.10       110     
 6 ADo  10.255.255.5/32                    192.168.0.14       110     
 7 ADo  192.168.0.0/30                     192.168.0.5        110     
 8 ADC  192.168.0.4/30     192.168.0.6     ether1             0       
 9 ADC  192.168.0.8/30     192.168.0.9     ether2             0       
10 ADC  192.168.0.12/30    192.168.0.13    ether3             0       
11 ADo  192.168.0.16/30                    192.168.0.10       110     
                                           192.168.0.14




[admin@R4] > /ip route print
Flags: X - disabled, A - active, D - dynamic, 
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, 
B - blackhole, U - unreachable, P - prohibit 
 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADS  0.0.0.0/0                          10.250.1.1         0       
 1 ADC  10.250.1.0/24      10.250.1.147    ether3             0       
 2 ADo  10.255.255.1/32                    192.168.0.9        110     
 3 ADo  10.255.255.2/32                    192.168.0.9        110     
 4 ADo  10.255.255.3/32                    192.168.0.9        110     
 5 ADC  10.255.255.4/32    10.255.255.4    lobridge           0       
 6 ADo  10.255.255.5/32                    192.168.0.18       110     
 7 ADo  192.168.0.0/30                     192.168.0.9        110     
 8 ADo  192.168.0.4/30                     192.168.0.9        110     
 9 ADC  192.168.0.8/30     192.168.0.10    ether1             0       
10 ADo  192.168.0.12/30                    192.168.0.18       110     
                                           192.168.0.9       
11 ADC  192.168.0.16/30    192.168.0.17    ether2             0




[admin@R5] > /ip route print
Flags: X - disabled, A - active, D - dynamic, 
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, 
B - blackhole, U - unreachable, P - prohibit 
 #      DST-ADDRESS        PREF-SRC        GATEWAY            DISTANCE
 0 ADS  0.0.0.0/0                          10.250.1.1         0       
 1 ADC  10.250.1.0/24      10.250.1.146    ether3             0       
 2 ADo  10.255.255.1/32                    192.168.0.13       110     
 3 ADo  10.255.255.2/32                    192.168.0.13       110     
 4 ADo  10.255.255.3/32                    192.168.0.13       110     
 5 ADo  10.255.255.4/32                    192.168.0.17       110     
 6 ADC  10.255.255.5/32    10.255.255.5    lobridge           0       
 7 ADo  192.168.0.0/30                     192.168.0.13       110     
 8 ADo  192.168.0.4/30                     192.168.0.13       110     
 9 ADo  192.168.0.8/30                     192.168.0.17       110     
                                           192.168.0.13      
10 ADC  192.168.0.12/30    192.168.0.14    ether1             0       
11 ADC  192.168.0.16/30    192.168.0.18    ether2             0
5

Problem with CSPF has been confirmed and will be fixed in next release. Thanks for pointing out!