Open ccollicutt opened 6 years ago
Tunnels seem OK:
[admin@mpls-r1.novalocal] > interface traffic-eng monitor 0
tunnel-id: 3
primary-path-state: established
primary-path: dyn
secondary-path-state: not-necessary
active-path: dyn
active-lspid: 1
active-label: 26
explicit-route: S:172.16.1.2/32,S:172.16.2.2/32,S:172.16.2.3/32
recorded-route: 172.16.2.2[26],172.16.2.3[0]
reserved-bandwidth: 5.0Mbps
[admin@mpls-r3.novalocal] > interface traffic-eng monitor 0
tunnel-id: 3
primary-path-state: established
primary-path: dyn
secondary-path-state: not-necessary
active-path: dyn
active-lspid: 1
active-label: 27
explicit-route: S:172.16.2.2/32,S:172.16.1.2/32,S:172.16.1.1/32
recorded-route: 172.16.1.2[27],172.16.1.1[0]
reserved-bandwidth: 5.0Mbps
MicroTik forum post as well: https://forum.mikrotik.com/viewtopic.php?f=14&p=636498#p636498
[admin@mpls-r1.novalocal] > mpls forwarding-table print
Flags: L - ldp, V - vpls, T - traffic-eng
# IN-LABEL OUT-LABELS DESTINATION INTERFACE NEXTHOP
0 expl-null
1 L 16 172.16.3.0/24 ether4 172.16.4.4
2 L 17 172.16.2.0/24 ether3 172.16.1.2
3 L 18 24 10.255.0.3/32 ether3 172.16.1.2
4 L 19 10.255.0.4/32 ether4 172.16.4.4
5 L 20 10.255.0.2/32 ether3 172.16.1.2
6 L 21 169.254.169.254/32 ether1 192.168.0.250
[admin@mpls-r1.novalocal] >
Interestingly when I traceroute 10.55.0.3 I see MPLS information.
[admin@mpls-r1.novalocal] > tool traceroute 10.255.0.3
# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS
1 172.16.1.2 0% 11 1ms 1.2 0.9 1.5 0.2 <MPLS:L=24,E=0>
2 10.255.0.3 0% 11 0.7ms 0.9 0.6 1.2 0.2
With the lan routes in place, there is a red *0 in the forwarding table:
[admin@mpls-r3.novalocal] > mpls forwarding-table print
Flags: L - ldp, V - vpls, T - traffic-eng
# IN-LABEL OUT-LABELS DESTINATION INTERFACE NEXTHOP
0 expl-null
1 L 16 10.255.0.4/32 ether4 172.16.3.4
2 L 17 22 10.255.0.1/32 ether3 172.16.2.2
3 L 18 172.16.4.0/24 ether4 172.16.3.4
4 L 19 192.168.10.0/24 *0 10.99.99.1
5 L 20 172.16.1.0/24 ether3 172.16.2.2
6 L 21 10.255.0.2/32 ether3 172.16.2.2
7 L 22 169.254.169.254/32 ether1 192.168.0.250
[admin@mpls-r3.novalocal] >
On R1 is seems OK:
[admin@mpls-r1.novalocal] > mpls forwarding-table print
Flags: L - ldp, V - vpls, T - traffic-eng
# IN-LABEL OUT-LABELS DESTINATION INTERFACE NEXTHOP
0 expl-null
1 L 16 172.16.3.0/24 ether4 172.16.4.4
2 L 17 172.16.2.0/24 ether3 172.16.1.2
3 L 18 24 10.255.0.3/32 ether3 172.16.1.2
4 L 19 10.255.0.4/32 ether4 172.16.4.4
5 L 20 10.255.0.2/32 ether3 172.16.1.2
6 L 21 169.254.169.254/32 ether1 192.168.0.250
7 L 22 192.168.20.0/24 TE-to-R3 10.99.99.2
[admin@mpls-r1.novalocal] >
I can't ping the other end of the tunnel:
R1 is 10.99.99.1:
R3 is 10.99.99.2:
I can ping the R3 loopback from R1:
I'm wondering if I'm having MTU issues? The openstack cloud has an MTU of 1500 everywhere and it can't be raised. Technically the links between the virtual routers are running on top of VXLAN but the OS in the VM doesn't know anything about that.
I have tried changing the MPLS MTU to 1450 but that doesn't seem to have helped.