OSPF/MPLS route not work
Posted: Sat Feb 04, 2023 2:07 pm
Hi folks!
i pass a problem in the last days, my network have a backbone with MPLS/LDP/OSPF and signalizing VPLS with LDP.
In fews POPs i have two redundant links, but my problem is, when a redundant link port that is advertising the network goes down, it seems that OSPF/MPLS does not understand that the port has gone down and the other side does not start to announce the route.
My topology can be illustrated like this...
Announcing the route 10.100.100.0/30 with a lower cost in R1, the preference would be for him, however when the ether2 in R1 drops, R2 should continue receiving traffic at least until the ip in the ether2 port of it, which does not happen. The strange thing is that in the forwarding table of mpls, after the port falls on R1, an out label is added that did not exist before.
Tests were done on at least 3 different versions (6.47.X, 6.48.6 and 6.43.4)
Would that be a bug?
i pass a problem in the last days, my network have a backbone with MPLS/LDP/OSPF and signalizing VPLS with LDP.
In fews POPs i have two redundant links, but my problem is, when a redundant link port that is advertising the network goes down, it seems that OSPF/MPLS does not understand that the port has gone down and the other side does not start to announce the route.
My topology can be illustrated like this...
Announcing the route 10.100.100.0/30 with a lower cost in R1, the preference would be for him, however when the ether2 in R1 drops, R2 should continue receiving traffic at least until the ip in the ether2 port of it, which does not happen. The strange thing is that in the forwarding table of mpls, after the port falls on R1, an out label is added that did not exist before.
Tests were done on at least 3 different versions (6.47.X, 6.48.6 and 6.43.4)
Would that be a bug?