After upgrading to 7.13, I encountered the same OSPF issue. Even though the interface was shut down, the routing entries still existed, and the same entry was added multiple times in the routing table and marked as DAo+(ecmp). My total number of routing table entries was only 700, and over time, the total number would accumulate to over 10000 (those same entries would be added infinitely). Moreover, when there were multiple paths, I set different costs for different paths, but this did not work. All of them were still activated and marked as DAo+
L2TP-client was disabled,but the routing entries still existed , The same entry has been added multiple times
Code:
[admin@R6] > int pr where name~"l2tp"Flags: X - DISABLEDColumns: NAME, TYPE# NAME TYPE 0 X to-bb-cloud-1111-l2tp l2tp-out1 X to-bb-cloud-1112-l2tp l2tp-out2 X to-bb-cloud-1113-l2tp l2tp-out3 X to-bb-cloud-1114-l2tp l2tp-out4 X to-bb-cloud-1115-l2tp l2tp-out[admin@R6] > ip rou pr where dst-address in 10.199.0.0/16 Flags: D - DYNAMIC; I - INACTIVE, A - ACTIVE; o - OSPF; H - HW-OFFLOADED; + - ECMP Columns: DST-ADDRESS, GATEWAY, DISTANCE DST-ADDRESS GATEWAY DISTANCEDAo + 10.199.0.0/16 172.21.192.254%vlan2600 110DIoH 10.199.0.0/16 100.64.133.1%to-bb-cloud-1112-l2tp 110DAo + 10.199.0.0/16 172.21.192.254%vlan2600 110DIoH 10.199.0.0/16 100.64.129.1%to-bb-cloud-1111-l2tp 110DAo + 10.199.0.0/16 172.21.192.254%vlan2600 110DAo + 10.199.127.0/30 172.21.192.254%vlan2600 110DIoH 10.199.127.0/30 100.64.133.1%to-bb-cloud-1112-l2tp 110DAo + 10.199.127.0/30 172.21.192.254%vlan2600 110DIoH 10.199.127.0/30 100.64.129.1%to-bb-cloud-1111-l2tp 110DAo + 10.199.127.0/30 172.21.192.254%vlan2600 110DAo + 10.199.127.8/30 172.21.192.254%vlan2600 110DIoH 10.199.127.8/30 100.64.133.1%to-bb-cloud-1112-l2tp 110DAo + 10.199.127.8/30 172.21.192.254%vlan2600 110DIoH 10.199.127.8/30 100.64.129.1%to-bb-cloud-1111-l2tp 110DAo + 10.199.127.8/30 172.21.192.254%vlan2600 110Statistics: Posted by wwj — Wed Feb 07, 2024 8:20 am