cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2998
Views
0
Helpful
3
Replies

BGP Default route failover, fallback, whatever you call it, not working

tahequivoice
Level 2
Level 2

We have a remote 1760 with a T1 and DSL backup. It uses BGP for routing. It has route maps for the default route and backup path,

router bgp 65000

no synchronization

bgp log-neighbor-changes

network 10.0.7.0 mask 255.255.255.0

neighbor 10.254.1.129 remote-as 33000

neighbor 10.254.1.129 soft-reconfiguration inbound

neighbor 10.254.1.129 distribute-list 2 out

neighbor 10.254.1.129 route-map default in

neighbor 10.254.1.129 route-map bk out

neighbor 10.20.30.3 remote-as 44000

neighbor 10.20.30.3 allowas-in

neighbor 10.20.30.3 soft-reconfiguration inbound

neighbor 10.20.30.3 distribute-list default in

neighbor 10.20.30.3 distribute-list 2 out

no auto-summary

ip access-list standard default

permit 0.0.0.0

!

access-list 2 permit 10.0.7.0 0.0.0.255

!

route-map bk permit 10

set as-path prepend 65000 65000 65000 65000

!

route-map default permit 10

match ip address default

set as-path prepend 33000 33000

This setup is used by multiple clients and works just fine. However for this one client, it works, but it does not revert the default route. If the T1 drops, which is primary, 10.20.30.3, then the routing all swings to the DSL, this part works fine. When the T1 comes back up, and the neighbor reestablishes, all but the default route swings back to the primary. We have to either shut the DSL down, or shut the neighbor down for the route to go back.  Could this be revision of the 1760 or IOS issue?

3 Replies 3

Edison Ortiz
Hall of Fame
Hall of Fame

Please post the output from typing 'show ip bgp 0.0.0.0'

milan.kulik
Level 10
Level 10

Hi,

if I understand correctly, you are receiving (only) default route from both BGP neighbors?

I guess, you problem might be caused by the same BGP attributes received with the default prefix from both neighbors.

And Step 10. of the BGP best path algorithm then is chosing the older path.

See

http://www.cisco.com/image/gif/paws/13753/25.pdf

What about trying to force the primary neighbor preferred by

Sorry the massage was corrupted somehow.