Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Filtering the static routes advertised to BGP Peer

 

 Hi All ,

 

   I have BGP running in my network . I have configured redistribute static . Due to this all the static routes are getting redistributed and advertised to  BGP peer . Now if in case I do not want to advertised any particular static route to BGP peer . Is it possible to achieve this .

 

 Below is the configuration :

 


router bgp 64508
 bgp log-neighbor-changes
 neighbor 10.0.47.22 remote-as 65000
 neighbor 10.0.47.22 description " Connect  to TATA 4 MB Link ID - 22064093"
 neighbor 10.227.19.6 remote-as 18101
 neighbor 10.227.19.6 description "RELIANCE 6MB LINK"
 neighbor 172.22.8.230 remote-as 9829
 neighbor 172.22.8.230 description "Connected to BSNL MPLS"
 neighbor 192.168.200.34 remote-as 64505
 neighbor 192.168.200.130 remote-as 64505
 neighbor 192.168.200.210 remote-as 64505
 neighbor 192.168.200.210 description ## FSS_ROUTER ##
 neighbor 192.168.201.82 remote-as 64505
 neighbor 192.168.201.82 description ## KAUSA_MUMBRA ##
 neighbor 192.168.252.58 remote-as 64505
 neighbor 192.168.252.58 description "Connected Kurla-1 Router"
 !
 address-family ipv4
  redistribute connected
  redistribute static
  neighbor 10.0.47.22 activate
  neighbor 10.0.47.22 allowas-in
  neighbor 10.0.47.22 soft-reconfiguration inbound
  neighbor 10.0.47.22 route-map TATA_IN_BLOCK in
  neighbor 10.0.47.22 route-map TATA_block out
  neighbor 10.227.19.6 activate
  neighbor 10.227.19.6 soft-reconfiguration inbound
  neighbor 10.227.19.6 route-map RCOM_block in
  neighbor 172.22.8.230 activate
  neighbor 172.22.8.230 allowas-in
  neighbor 172.22.8.230 soft-reconfiguration inbound
  neighbor 172.22.8.230 route-map SIFY_LOOPBACK out
  neighbor 192.168.200.34 activate
  neighbor 192.168.200.34 allowas-in
  neighbor 192.168.200.34 soft-reconfiguration inbound
  neighbor 192.168.200.130 activate
  neighbor 192.168.200.130 allowas-in
  neighbor 192.168.200.130 soft-reconfiguration inbound
  neighbor 192.168.200.210 activate
  neighbor 192.168.200.210 allowas-in
  neighbor 192.168.200.210 soft-reconfiguration inbound
  neighbor 192.168.201.82 activate
  neighbor 192.168.201.82 allowas-in
  neighbor 192.168.201.82 soft-reconfiguration inbound
  neighbor 192.168.252.58 activate
  neighbor 192.168.252.58 allowas-in
  neighbor 192.168.252.58 soft-reconfiguration inbound
  no auto-summary
  no synchronization
  network 192.168.100.0 mask 255.255.255.128
  network 192.168.130.0
 exit-address-family
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 192.168.252.33
ip route 10.120.35.0 255.255.255.192 172.22.8.230
ip route 10.150.101.0 255.255.255.0 192.168.200.210
ip route 10.254.254.0 255.255.255.0 192.168.200.210
ip route 172.22.11.144 255.255.255.252 172.22.8.230
ip route 172.22.101.16 255.255.255.252 172.22.8.230
ip route 172.23.97.36 255.255.255.252 172.22.8.230
ip route 172.23.97.44 255.255.255.252 172.22.8.230
ip route 172.25.1.64 255.255.255.252 172.22.8.230
ip route 172.25.33.68 255.255.255.252 172.22.8.230
ip route 172.25.48.132 255.255.255.252 172.22.8.230
ip route 172.25.66.0 255.255.255.252 172.22.8.230
ip route 172.25.96.64 255.255.255.252 172.22.8.230
ip route 172.25.96.252 255.255.255.252 172.22.8.230
ip route 172.25.97.44 255.255.255.252 172.22.8.230
ip route 172.25.97.100 255.255.255.252 172.22.8.230
ip route 172.25.97.232 255.255.255.252 172.22.8.230
ip route 172.31.200.0 255.255.255.0 10.0.47.22
ip route 192.168.8.0 255.255.255.0 10.0.47.22
ip route 192.168.20.0 255.255.255.0 10.0.47.22
ip route 192.168.48.0 255.255.255.224 10.227.19.6

=================================================

ip route 192.168.101.1 255.255.255.255 192.168.250.2    <=== This route I do not want to advertise to BGP peer

================================================
ip route 192.168.76.0 255.255.255.0 172.22.8.230
ip route 192.168.81.232 255.255.255.248 192.168.252.33
ip route 192.168.82.0 255.255.255.0 172.22.8.230
ip route 192.168.87.0 255.255.255.0 10.227.19.6
ip route 192.168.88.0 255.255.255.224 10.227.19.6
ip route 192.168.96.160 255.255.255.224 172.22.8.230
ip route 192.168.97.160 255.255.255.224 10.227.19.6
ip route 192.168.98.128 255.255.255.224 172.22.8.230
ip route 192.186.46.0 255.255.255.0 172.22.8.230

 

 Kindly revert .

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hi Tusharp,It can be done by

Hi Tusharp,

It can be done by using route map with route tagging

 address-family ipv4
  redistribute connected
  redistribute static route-map NO_DISTRIBUTE
 !         
ip route 192.168.101.1 255.255.255.255 192.168.250.2 tag 2
!         
!         
route-map NO_DISTRIBUTE deny 10
 match tag 2
!         
route-map NO_DISTRIBUTE permit 20

 

Regards,

kazim

"If post helpful  don't forget to select correct answer and rating"

1 REPLY

Hi Tusharp,It can be done by

Hi Tusharp,

It can be done by using route map with route tagging

 address-family ipv4
  redistribute connected
  redistribute static route-map NO_DISTRIBUTE
 !         
ip route 192.168.101.1 255.255.255.255 192.168.250.2 tag 2
!         
!         
route-map NO_DISTRIBUTE deny 10
 match tag 2
!         
route-map NO_DISTRIBUTE permit 20

 

Regards,

kazim

"If post helpful  don't forget to select correct answer and rating"

53
Views
0
Helpful
1
Replies