Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
after this log: %IOSXE_SPA-6-UPDOWN: Interface TenGigabitEthernet0/0/1, link down due to local fault the interface TenGigabitEthernet0/0/1 never goes down, however that interface is deleted as best path, for all prefix. With FRR enabled, after that event, all prefix start to use the repair path. there is no changes from control and data plane, but the traffic is not forwarded on the correct interface. ASR1K#show ip route 172.31.17.252 Routing entry for 172.31.17.252/32 Known via "ospf 65000", distance 110, metric 10, type intra area Redistributing via ospf 64617 Advertised by ospf 64617 subnets tag 532249010 route-map LOOPBACK_ONLY Last update from 172.31.17.52 on TenGigabitEthernet0/0/1.4082, 6d11h ago Routing Descriptor Blocks: * 172.31.17.52, from 172.31.17.252, 6d11h ago, via TenGigabitEthernet0/0/1.4082 Route metric is 10, traffic share count is 1 Repair Path: 172.31.17.54, via TenGigabitEthernet1/0/1.4082 ASR1K#show ip cef 172.31.17.252 172.31.17.252/32 nexthop 172.31.17.52 TenGigabitEthernet0/0/1.4082 label [implicit-null|350448](elc)-(local:9876) repair: attached-nexthop 172.31.17.54 TenGigabitEthernet1/0/1.4082 ASR1K#show ip cef exact-route 172.31.17.220 172.31.17.252 172.31.17.220 -> 172.31.17.252 => label [implicit-null|350448](elc)-(local:9876)TAG adj out of TenGigabitEthernet1/0/1.4082, addr 172.31.17.54 <---------------------------- ASR1K#traceroute 172.31.17.252 Type escape sequence to abort. Tracing the route to 172.31.17.252 VRF info: (vrf in name/id, vrf out name/id) 1 172.31.17.54 [MPLS: Label 350448 Exp 0] 17 msec 17 msec 16 msec <------------------------------- 2 172.31.16.8 [MPLS: Label 18060 Exp 0] 19 msec 17 msec 19 msec 3 172.31.17.252 16 msec 17 msec 17 msec ASR1K#show mpls forwarding-table 172.31.17.252 Local Outgoing Prefix Bytes Label Outgoing Next Hop Label Label or Tunnel Id Switched interface 9876 350448 172.31.17.252/32 0 Te1/0/1.4082 172.31.17.54 <------------------------------- PA-CATAITCR-R001#
We observed the evidence of this problem if we enable the FRR feature. Without FRR feature we don't have the same result.
We found two WA, confirmed in LAB and Production environment - shut/no shut of the interface related to local fault - clear ip route *
tested in the lab by using two different release: - 16.12.8 problem confirmed - 17.6.3a problem solved