Hi,
I am looking for a way of removing local /32 routes whenever a irb interface goes down. I have the setup in the picture. R3 runs LDP VPLS towards a primary Edge router (R1) and has a backup-neighbor to a secondary Edge router (R2). Irb interface on the secondary router remains down until the primary VPLS circuit fails. However the local /32 route (1.1.1.1/32) of the irb interface is still present in the routing table with next hop type "reject" even when the irb interface is down. At the same time R2 receives the bigger block (/29) from R1 via BGP which I want to be preferred. Is there anyway to remove the local route from the routing-table on R2 whenever the irb interface is down so that the BGP route from R1 will be used?
***** R2 show route *****
1.1.1.1/32 *[Local/0] 05:28:06
Reject
BGP route from R1:
***** R2 show route*****
1.1.1.0/29 *[BGP/170] 05:29:04, localpref 100, from x.x.x.x
AS path: I, validation-state: unverified
> to x.x.x.x via lt-1/1/0.4000
************ R1 CONFIGURATION ************
R1> show configuration routing-instances CUSTOMER_ACME
apply-groups INTERNET_VPLS_BACKHAUL_ER;
protocols {
vpls {
vpls-id 100;
neighbor 10.10.10.3 {
pseudowire-status-tlv;
}
}
}
bridge-domains {
CUSTOMER_ACME {
domain-type bridge;
vlan-id 100;
routing-interface irb.100;
}
}
}
}
R1> show configuration interfaces irb.100
description CUSTOMER_ACME;
family inet {
address 1.1.1.1/29;
}
mac 44:f4:77:12:d3:58;
************ R2 CONFIGURATION (same as R1) ************
R2> show configuration routing-instances CUSTOMER_ACME
apply-groups INTERNET_VPLS_BACKHAUL_ER;
protocols {
vpls {
vpls-id 100;
neighbor 10.10.10.3 {
pseudowire-status-tlv;
}
}
}
bridge-domains {
CUSTOMER_ACME {
domain-type bridge;
vlan-id 100;
routing-interface irb.100;
}
}
}
}
R2> show configuration interfaces irb.100
description CUSTOMER_ACME;
family inet {
address 1.1.1.1/29;
}
mac 44:f4:77:12:d3:58;
************ R2 CONFIGURATION ************
R3> show configuration routing-instances CUSTOMER_ACME
apply-groups INTERNET_VPLS_BACKHAUL_PE;
interface ge-0/0/0.100;
protocols {
vpls {
vpls-id 100;
neighbor 10.10.10.1 {
pseudowire-status-tlv;
revert-time 20;
backup-neighbor 10.10.10.2;
}
}
}
}
}