08-31-2012 06:25 AM - edited 03-04-2019 05:26 PM
Hi
I am currently setting up a new VRF on a Cisco 7609 which is advertising (as a RR-Client) an iBGP route to a Juniper MX960. This route is then getting sent back to the default route table on the 7609 but rejected due to the cluster-id loop prevention. Although not ideal I need this route to be visible in both tables.
Is there a way of changing the bgp cluster-id per VRF rather than just globally?
Thanks
09-03-2012 03:03 AM
Hello Paul,
the cluster-id is configured at BGP protocol level in IOS
see
cluster-id is configured at BGP group level in JUNOS
see
I'm afraid you cannot achieve what you want in this way, because you cannot have the same iBGP peer in two different BGP groups in JUNOS (if I correctly remember).
If your objective is to pass a route locally on the C7609 between a VRF and global routing table you should think of using route leakage
Hope to help
Giuseppe
09-03-2012 11:39 AM
Hi
Thanks for your feedback.
I have ended up having to use eBGP between the Cisco box and our LNS to avoid the cluster ID of the Cisco being attached to the route advertisement toward the MX960. Although route leakage would be the best solution normally I need the traffic to go via a set path (DPI Traffic Management).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide