07-23-2007 09:10 AM - edited 03-05-2019 05:26 PM
I am have asymmetric routing issue in a multi-homed environment due to redistributing floating into OSPF. We have a client with dual feed, 10MB primary and ADSL as backup. The primary is running BGP advertising the client ip space. HSRP with route tracking feature is used for fail over. The fail over seems to work fine but inbound traffic to client network seems to be taking the ADSL and the primary is used for outbound traffic from client network. I can see why i am having asymmetric routing as the bgp route is not installed into routing table because the floating static is redistributed into OSPF and inheriting AD for OSPF even though floating static has higher AD then BGP route. I would really appreciate if someone can advise me on possible resolution.
07-23-2007 11:26 AM
Nav
Perhaps I am not understanding something in your post. But it seems to me that there are 2 solutions that should work. You could try setting the administrative distance of the floating static to be higher than both BGP and OSPF. Or you could try modifying the redistribute statement to use a route map or a distribute list and deny redistribution of the floating static.
If those do not solve the problem then perhaps you can clarify the environment and the problem.
HTH
Rick
08-03-2007 06:35 AM
Thanks for your reply Rick. We have now changed our routing architecture. OSPF is used for loopback and infrastructure and BGP is used to carry the customer routes. I will be testing the failover for the client in two weeks.
08-28-2007 06:58 AM
Hi Rick
Am still having asymmetic routing problem even after introducing the new BGP and OSPF infrastructure. BGP is used to carry customer routes via redistributing connected and static. The problem i am having currently for some clients is that there primary link is being used for outbound traffic and ADSL is used for inbound traffic. If you take a look at the network diagram i have attach i have two static routes pointing to the customer network. On Access1 router the static route has a default AD and on the Aggr1 the static route has AD of 250. The routing decision on the Core seems to be preparing ADSL route for some reason. I believe this may be due to bgp is assigning AD for static route when redistributed into BGP. Rick can you please help me resolve this problem without having to introduce BGP on customer primary router.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: