Routing
Highlighted
Routing

Tracking next-hop of leaked route??

11.24.11   |  
‎11-24-2011 12:54 AM

Dear friends,

 

Following is my topology . I am using  connectivity between PE-CE router in a virtual-router type routing-instance.

 

 

   PE-Router -------2.2.2.0/30----- CE-Router--X-network (9.9.9.0)

 

Now problem i am facing is that i need to leak X-Network in a global routing table. But i also want that if X-network goes down it should also be removed from inet.0 , but its not happening.  inet.0 route remains UP all the time.

 

can anyone suggest any workaround?? i tried bfd option but session is not comming up.. may b due to the fact that CE is cisco and it doesnt support multihop bfd... 

 

any other work arounds are also appriciate.

----------

 

routing-options {
interface-routes {
rib-group inet customer;
}
static {

route 9.9.9.0/24 {
next-table customer.inet.0;

}

}
rib-groups {
cloud {
import-rib [ inet.0 customer.inet.0 ];
}

}
}

 

 

routing-instances {
customer {
instance-type virtual-router;
interface ge-0/0/1.0;
routing-options {
static {
route 9.9.9.0/24 next-hop 2.2.2.1;
}
}

 

 

1 REPLY
Routing

Re: Tracking next-hop of leaked route??

[ Edited ]
12.01.11   |  
‎12-01-2011 12:44 AM

The route is not invalidated because you've configured it as a static route with next-hop being "next-table customer.inet.0".

What you actually need to do is to use RIB group for this purpose because it will leak the route only if it's alive.

The source RIB will be "customer.inet.0" while destination "inet.0", and you have to apply it under protocol static in routing-instance "customer"

 

rib-groups {
reverse {
import-rib [ customer.inet.0 inet.0];
}
}

 

 

Regards,
Dumitru Papana