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

bgp inbound and outbound routing issue

Chin
Level 1
Level 1

Dear all, 

 

I encountered an issue about the BGP inbound and outbound routing issue. I have 2 routers connect to a same AS. RT1 is primary router and RT2 is secondary router. When I check on the router's interface that connecting to the WAN, RT1's interface is generating counter in output, whereas RT2's interface is generating counter in input. 

I have set a metric and weight in my routers, but it still show the inbound in RT2 and outbound in RT1. 

Below is my configuration. Appreciate for help. 

 

 

RT1#
router bgp 88088
 bgp log-neighbor-changes
 network 172.2.61.0
 network 10.16.15.0
 timers bgp 15 20
 redistribute connected
 redistribute static
 neighbor 172.2.61.61 remote-as 4477
 neighbor 172.2.61.61 transport path-mtu-discovery
 neighbor 172.2.61.61 weight 100
 neighbor 172.2.61.61 route-map SET-ROUTE-LOCAL-PREF in
 neighbor 172.2.61.61 route-map ADVERTISE-BGP-WAN out
 neighbor 10.16.15.253 remote-as 88088
 neighbor 10.16.15.253 transport path-mtu-discovery
 neighbor 10.16.15.253 next-hop-self

 

route-map SET-ROUTE-LOCAL-PREF permit 10
 set local-preference 500

route-map ADVERTISE-BGP-WAN permit 10
 match ip address prefix-list ADVERTISE-ROUTE-WAN

ip prefix-list ADVERTISE-ROUTE-WAN seq 5 permit 10.16.15.0/24
ip prefix-list ADVERTISE-ROUTE-WAN seq 10 permit 172.2.61.60/30

 

RT2#

router bgp 88088
 bgp log-neighbor-changes
 network 172.2.61.0
 network  10.16.15.0
 timers bgp 15 20
 redistribute connected
 redistribute static
 neighbor 172.2.61.65 remote-as 4477
 neighbor 172.2.61.65 transport path-mtu-discovery
 neighbor 172.2.61.65 route-map ADVERTISE-BGP-WAN out
 neighbor 10.16.15.254 remote-as 88088
 neighbor 10.16.15.254 transport path-mtu-discovery
 neighbor 10.16.15.254 next-hop-self
 neighbor 10.16.15.254 weight 100

route-map ADVERTISE-BGP-WAN permit 10
 match ip address prefix-list ADVERTISE-ROUTE-WAN

ip prefix-list ADVERTISE-ROUTE-WAN seq 5 permit 10.16.15.0/24
ip prefix-list ADVERTISE-ROUTE-WAN seq 10 permit 172.2.61.60/30

 

1 Accepted Solution
3 Replies 3

milan.kulik
Level 10
Level 10
Hi, to influence the inbound traffic you need to play with the attributes of prefixes advertised to your neighbors. So I'd try to configure a worse MED for the prefixes advertised to your neighbor from your secondary router. Or to prepend your AS number several times to that prefixes. That should make your neighbors to prefer your primary router as the entry point to your AS. Best regards, Milan

Hi Milan, 

Do you have any example that I can refer to? Appreciate.