02-26-2006 06:33 PM - edited 03-03-2019 11:52 AM
Please look at my configuration:
R7#sh run
Building configuration...
Current configuration:
!
! Last configuration change at 17:52:58 UTC Tue Apr 13 1993
! NVRAM config last updated at 17:50:34 UTC Tue Apr 13 1993
!
version 12.1
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname R7
class-map chris
match none
class-map COS2_TRAFFIC
match none
!
!
!
ip subnet-zero
no ip domain-lookup
!
tag-switching tdp router-id Loopback7
cns event-service server
interface Loopback0
ip address 7.x.x.x.x.255.255
!
interface Loopback1
ip address 6.x.x.x.x.255.255
!
interface Loopback2
ip address 8.x.x.x.x.255.255
!
interface Loopback5
no ip address
!
interface Loopback7
no ip address
!
interface Ethernet0/0
ip address 20.x.x.x.255.255.0
ip directed-broadcast
ip policy route-map vfilter
half-duplex
max-reserved-bandwidth 76
!
interface Serial0/0
ip address 137.x.x.x.x.255.0
traffic-shape group 101 64000 8000 8000 1000
!
interface Serial0/1
no ip address
shutdown
clockrate 64000
!
router bgp 700
redistribute connected route-map t1
neighbor 20.20.20.5 remote-as 500
neighbor 20.20.20.5 send-community
no auto-summary
!
ip classless
no ip http server
ip pim rp-address 10.1.23.3
!
access-list 1 permit 6.6.6.6
access-list 2 permit 7.7.7.7
access-list 3 permit 8.8.8.8
access-list 12 permit 30.1.1.5
access-list 33 permit any
access-list 101 deny udp any any range 16348 32767
access-list 101 permit ip any any
route-map t1 permit 10
match ip address 1
set community no-export
!
route-map t1 permit 20
match ip address 2
set community no-advertise
!
route-map t1 permit 30
match ip address 3
set community local-AS
!
route-map t1 permit 1000
end
I noticed some subnets not being advertised to other BGP neighbor such as 6.6.6.6, 7.7.7.7 and 8.8.8.8:
R7#sh ip bgp 7.7.7.7
BGP routing table entry for 7.7.7.7/32, version 5
Paths: (1 available, best #1, table Default-IP-Routing-Table, not advertised to any peer)
Not advertised to any peer
Local
0.0.0.0 from 0.0.0.0 (8.8.8.8)
Origin incomplete, metric 0, localpref 100, weight 32768, valid, sourced, best
Community: no-advertise
R7#sh ip bgp 8.8.8.8
BGP routing table entry for 8.8.8.8/32, version 6
Paths: (1 available, best #1, table Default-IP-Routing-Table, not advertised outside local AS)
Not advertised to any peer
Local
0.0.0.0 from 0.0.0.0 (8.8.8.8)
Origin incomplete, metric 0, localpref 100, weight 32768, valid, sourced, best
Community: local-AS
R7#sh ip bgp 6.6.6.6
BGP routing table entry for 6.6.6.6/32, version 4
Paths: (1 available, best #1, table Default-IP-Routing-Table, not advertised to EBGP peer)
Not advertised to any peer
Local
0.0.0.0 from 0.0.0.0 (8.8.8.8)
Origin incomplete, metric 0, localpref 100, weight 32768, valid, sourced, best
Community: no-export
R7#sh ip bgp 137.20.25.0
BGP routing table entry for 137.20.25.0/24, version 2
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Advertised to non peer-group peers:
20.20.20.5
Local
0.0.0.0 from 0.0.0.0 (8.8.8.8)
Origin incomplete, metric 0, localpref 100, weight 32768, valid, sourced, best
some one tell me why?
02-26-2006 07:11 PM
I'm glad to see you fixed the community issue you had in your previous posting.
To answer this question, the reason these prefixes are not advertised to your eBGP neighbor is a direct effect of these special communities being attached to them.
For more information on the effect of these special communities, please refer to the following URL:
http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_6-2/bgp_communities.html
Hope this helps,
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide