From: Steve Krantz (Steve.Krantz@inacom.com)
Date: Tue Dec 06 2005 - 09:28:27 GMT-3
Ivan
Unfortunately the show commands don't offer much help. The R7Exist map
and ROUTE7 prefix-list work and
the 0/0 route is getting sent to 140.2.6.6, even though the show
route-map R7Exist doesn't show any hits. Why does the exact same config
not work using an acl?
Maybe it's just a bug, acl 146 looks correct, doesn't it?
neighbor 140.2.6.6 default-originate route-map R7Exist
neighbor 140.2.7.7 default-originate route-map R6Exist
!
ip prefix-list ROUTE seq 5 permit 140.2.6.0/24
!
ip prefix-list ROUTE7 seq 5 permit 140.2.7.0/24
!
access-list 146 permit ip host 140.2.6.0 host 255.255.255.0
!
route-map R7Exist permit 10
match ip address prefix-list ROUTE7
!
route-map R6Exist permit 10
match ip address 146
R9#sh route-map R6Exist
route-map R6Exist, permit, sequence 10
Match clauses:
ip address (access-lists): 146
Set clauses:
Policy routing matches: 0 packets, 0 bytes
R9#sh access-list 146
Extended IP access list 146
10 permit ip host 140.2.6.0 host 255.255.255.0
R9#sh ip prefix-list ROUTE
ip prefix-list ROUTE: 1 entries
seq 5 permit 140.2.6.0/24
R9#sh route-map R7Exist
route-map R7Exist, permit, sequence 10
Match clauses:
ip address prefix-lists: ROUTE7
Set clauses:
Policy routing matches: 0 packets, 0 bytes
R9#sh ip prefix-list ROUTE7
ip prefix-list ROUTE7: 1 entries
seq 5 permit 140.2.7.0/24
R9#
R9#sh ip bgp 140.2.6.6
% Network not in table
R9#sh ip bgp neigh 140.2.6.6 adv
BGP table version is 16, local router ID is 140.2.9.9
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Originating default network 0.0.0.0
Network Next Hop Metric LocPrf Weight Path
*> 160.2.40.0/22 0.0.0.0 32768 i
R9#sh ip bgp neigh 140.2.7.7 adv
BGP table version is 16, local router ID is 140.2.9.9
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
*> 160.2.40.0/22 0.0.0.0 32768 i
Dave,
I had started down that path, but according to this wording it seems the
0.0.0.0/0 would have to exist in the routing table to be advertised.
Obviously the intent of the default-originate command is the
functionality I am looking for, especially since no default route exists
in the routing table.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/
iprrp_r/ip2_n1g.htm#wp1036743
All routes that may be dynamically advertised or not advertised need to
exist in the BGP routing table for conditional advertisement to occur.
This is really interesting, from the non-neighbor version of the
advertise-map command. The example they use looks for 10.1.1.0/24 and
advertises the more specific /25's
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft
/122t/122t4/ftbgpri.htm
Enabling this feature will allow you to improve the accuracy of common
route aggregation by conditionally injecting or replacing less specific
prefixes with more specific prefixes. Only prefixes that are equal to or
more specific than the original prefix may be injected.
Their example:
router bgp 109
bgp inject-map ORIGINATE exist-map LEARNED_PATH
!
route-map LEARNED_PATH permit 10
match ip address prefix-list ROUTE
match ip route-source prefix-list ROUTE_SOURCE
!
route-map ORIGINATE permit 10
set ip address prefix-list ORIGINATED_ROUTES
set community 14616:555 additive
!
ip prefix-list ROUTE permit 10.1.1.0/24
!
ip prefix-list ORIGINATED_ROUTES permit 10.1.1.0/25
ip prefix-list ORIGINATED_ROUTES permit 10.1.1.128/25
!
ip prefix-list ROUTE_SOURCE permit 10.2.1.1/32
Steve
Steve Krantz
Consulting Engineer
Inacom Information Systems
Phone: 608.661.7777
steve.krantz@inacom.com
http://www.inacom.com/
-----Original Message-----
From: Ivan [mailto:ivan@iip.net]
Sent: Tuesday, December 06, 2005 4:23 AM
To: Steve Krantz; ccielab@groupstudy.com
Subject: Re: neighbor default-originate route-map - am I missing
something obvious?
pease send output of command
sh ip route-map R6Exist
sh access-list 146
sh ip prefix-list ROUTE
On Tuesday 06 December 2005 05:39, Steve Krantz wrote:
> I know this subject has been covered before, but I can't see what I'm
> doing wrong?
>
>
>
> Trying to generate a default route for neighbor 140.2.7.7 based on the
> presence of the 140.2.6.0/24 route.
>
>
>
> I was able to do this successfully with the prefix list (ROUTE -
below)
> instead of an acl, but I'm wondering what's wrong with this config.
>
>
>
> !
>
> router bgp 10342
>
> neighbor 140.2.7.7 remote-as 8302
>
> neighbor 140.2.7.7 ebgp-multihop 255
>
> neighbor 140.2.7.7 update-source Loopback0
>
> neighbor 140.2.7.7 default-originate route-map R6Exist
>
> no auto-summary
>
> !
>
> ip prefix-list ROUTE seq 5 permit 140.2.6.0/24
>
> !
>
> access-list 146 permit ip host 140.2.6.0 host 255.255.255.0
>
> !
>
> route-map R6Exist permit 10
>
> match ip address 146
>
>
>
> R9(config-router)#do sh ip bgp neigh 140.2.7.7 adv
>
> BGP table version is 10, local router ID is 140.2.9.9
>
> 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
>
> *> 160.2.40.0/22 0.0.0.0 32768 i
>
> R9(config-router)#
>
>
>
>
>
> Gateway of last resort is not set
>
>
>
> R 222.222.222.0/24 [120/1] via 150.2.1.102, 00:00:12,
FastEthernet0/0
>
> R 192.168.25.0/24 [120/5] via 150.2.12.6, 00:00:29, FastEthernet0/1
>
> 140.2.0.0/16 is variably subnetted, 14 subnets, 5 masks
>
> R 140.2.8.0/24 [120/1] via 150.2.1.8, 00:00:11, FastEthernet0/0
>
> C 140.2.9.0/24 is directly connected, Loopback0
>
> R 140.2.6.0/24 [120/5] via 150.2.12.6, 00:00:29, FastEthernet0/1
>
> R 140.2.7.0/24 [120/2] via 150.2.1.8, 00:00:11, FastEthernet0/0
>
> R 140.2.5.5/32 [120/5] via 150.2.12.6, 00:00:00, FastEthernet0/1
>
> R 140.2.4.4/32 [120/5] via 150.2.12.6, 00:00:00, FastEthernet0/1
>
> R 140.2.1.1/32 [120/5] via 150.2.12.6, 00:00:00, FastEthernet0/1
>
> R 140.2.36.0/24 [120/5] via 150.2.12.6, 00:00:00,
FastEthernet0/1
>
> R 140.2.35.0/24 [120/5] via 150.2.12.6, 00:00:00,
FastEthernet0/1
>
> R 140.2.56.0/29 [120/5] via 150.2.12.6, 00:00:00,
FastEthernet0/1
>
> R 140.2.78.8/29 [120/1] via 150.2.1.8, 00:00:12, FastEthernet0/0
>
> R 140.2.68.0/28 [120/2] via 150.2.1.8, 00:00:12, FastEthernet0/0
>
> R 140.2.100.0/28 [120/5] via 150.2.12.6, 00:00:00,
FastEthernet0/1
>
> R 140.2.112.0/22 [120/5] via 150.2.12.6, 00:00:00,
FastEthernet0/1
>
> 111.0.0.0/32 is subnetted, 1 subnets
>
> R 111.111.111.111 [120/5] via 150.2.12.6, 00:00:00,
> FastEthernet0/1
>
> 160.2.0.0/16 is variably subnetted, 5 subnets, 2 masks
>
> C 160.2.42.0/24 is directly connected, Loopback42
>
> C 160.2.43.0/24 is directly connected, Loopback43
>
> C 160.2.40.0/24 is directly connected, Loopback40
>
> B 160.2.40.0/22 [200/0] via 0.0.0.0, 03:43:31, Null0
>
> C 160.2.41.0/24 is directly connected, Loopback41
>
> 150.2.0.0/16 is variably subnetted, 3 subnets, 2 masks
>
> R 150.2.2.2/32 [120/5] via 150.2.12.6, 00:00:01, FastEthernet0/1
>
> C 150.2.1.0/24 is directly connected, FastEthernet0/0
>
> C 150.2.12.0/24 is directly connected, FastEthernet0/1
>
>
>
> Cisco's example - Notice typo, I'm pretty sure they mean "match ip
> address 100" not "1"
>
> In the following example, the last line of the configuration has been
> changed to show the use of an extended access list. The local router
> injects route 0.0.0.0 to the neighbor 172.16.2.3 only if there is a
> route to 198.92.68.0 with a mask of 255.255.0.0:
>
> router bgp 109
> network 172.16.0.0
> neighbor 172.16.2.3 remote-as 200
> neighbor 172.16.2.3 default-originate route-map default-map
> !
> route-map default-map 10 permit
> match ip address 1
> !
> access-list 100 permit ip host 198.92.68.0 host 255.255.255.0
>
>
>
>
>
> Thanks,
>
> Steve Krantz
>
> Consulting Engineer
>
> Inacom Information Systems
>
> steve.krantz@inacom.com
>
> http://www.inacom.com/
>
>
This archive was generated by hypermail 2.1.4 : Mon Jan 09 2006 - 07:07:50 GMT-3