From: Mahesh Shivaswamy (maheshs.cisco@gmail.com)
Date: Tue Feb 17 2009 - 20:23:23 ARST
Hi,
I am not sure why is R2 advertising prefix 136.1.29.0/24 when the
route 136.1.23.0/24 exist in the routing table ???
I have the following configs on R2
R2#sh run | be router bgp
router bgp 300
no synchronization
bgp router-id 150.1.2.2
bgp log-neighbor-changes
network 136.1.29.0 mask 255.255.255.0
neighbor 136.1.23.3 remote-as 100
neighbor 136.1.29.9 remote-as 100
neighbor 136.1.245.5 remote-as 200
neighbor 136.1.245.5 advertise-map ADVERTISE non-exist-map NON-EXIST
no auto-summary
!
ip prefix-list HDLC seq 5 permit 136.1.23.0/24
!
ip prefix-list VLAN29 seq 5 permit 136.1.29.0/24
!
route-map NON-EXIST permit 10
match ip address prefix-list HDLC
!
route-map ADVERTISE permit 10
match ip address prefix-list VLAN29
R2#sh ip bgp ne 136.1.245.5 advertised-routes
BGP table version is 9, local router ID is 150.1.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 136.1.3.0/24 136.1.23.3 0 0 100 i
*> 136.1.29.0/24 0.0.0.0 0 32768 i
Total number of prefixes 2
R2#sh ip bgp ne 136.1.245.5 | in Condition
Condition-map NON-EXIST, Advertise-map ADVERTISE, status: Advertise
R2#sh ip route 136.1.23.0
Routing entry for 136.1.23.0/24
Known via "connected", distance 0, metric 0 (connected, via interface)
Redistributing via ospf 1, eigrp 100
Advertised by ospf 1
Routing Descriptor Blocks:
* directly connected, via Serial0/1
Route metric is 0, traffic share count is 1
rgds
Mahesh
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:11 ARST