cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
443
Views
0
Helpful
1
Replies

BGP, route-map questions

wilson_1234_2
Level 3
Level 3

I have the route map show below and have these general question:

1. Is it considered an ok design practice to use the same access-list "OSPF" in both the distribution and advertise rout maps?

I am thinking that I can control exactly what routes are distributed, and have those same routes advertised.

In addition, if I need to add a route, I only need to change one access-list.

2. This could be related to question one,  the "Advertised" route map is implemented on a hub site router. The branches are getting the routes as they should, but there are also a couple of routes advertised from the hub site to the branches, and I don't see how they are getting into the BGP process.

There are two routes that are in the OSPF database, as they should be, but they are not in the OSPF access-list, and should not be getting advertised.

The 16 bit mask of 10.2.0.0/16 is there as it should be,

but also 10.2.30.1/32 and 10.2.30.2/32

There is no network statement in the Hub router for those two more specific routes, or a line in the access-list.

I am sure the routes are coming from the hub site router.

Am I missing something in the route map, or BGP in general?

The 16 bit line in the access-list should not be allowing the 32 bit host addresses should it?

!
route-map OSPF_BGP permit 10
match ip address OSPF
!
route-map Advertised permit 10
match ip address prefix-list Default
!
route-map Advertised permit 20
match ip address OSPF
!
route-map Advertised permit 30
match ip address prefix-list Prepend
!
!
!
!
ip prefix-list Default seq 5 permit 0.0.0.0/0
!
ip access-list standard OSPF
permit 10.1.0.0 0.0.255.255
permit 10.2.0.0 0.0.255.255
permit 10.3.0.0 0.0.255.255
permit 192.168.1.0 0.0.0.255
permit 192.168.2.0 0.0.0.255
permit 192.168.3.0 0.0.0.255
!
ip prefix-list DR seq 5 permit 10.20.30.1/32
ip prefix-list DR seq 10 permit 10.20.30.2/32
!
!

!
router bgp 65001
bgp log-neighbor-changes
network 0.0.0.0
network 10.1.0.0
mask 255.255.0.0
redistribute ospf 1 metric 1000 route-map OSPF_BGP
neighbor 15.77.2.1 remote-as 65000
neighbor 15.77.2.1 route-map Advertised out
no auto-summary

1 Reply 1

Edison Ortiz
Hall of Fame
Hall of Fame

There are two routes that are in the OSPF database, as they should be, but they are not in the OSPF access-list, and should not be getting advertised.

The 16 bit mask of 10.2.0.0/16 is there as it should be,



but also 10.2.30.1/32 and 10.2.30.2/32

10.2.30.1 and 10.2.30.2 are part of the 10.2.0.0/16 permit. You can leave your config as is with a small modification.

route-map OSPF_BGP permit 10
match ip address OSPF
!
route-map Advertised permit 10
match ip address prefix-list Default

!

route-map Advertised deny 15

match ip address prefix-list DR
!
route-map Advertised permit 20
match ip address OSPF
!
route-map Advertised permit 30
match ip address prefix-list Prepend
!