Re: default-information originate route-map

Hmmmmm could this be a case for ip default-route ???

"He not busy being born is busy dying" -- Dylan

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.7 (MingW32) - WinPT 1.2.0

mQGiBEY2qu8RBAD0E7Ydspmpn9/rRfd614pvDaqj4GKAUeWpc8NNJ3xNU9C5TAKg
Ta/52f2DvxgPlw6m7W66AJP0HZODw2ameQ9tNMrz3upKRA+ISFaqkJa99UOTdLGC
W/HtHWZNUJDopBHm3j/TBAAhI0EWvcNIudbHx5zYY4osfDNMaIXYaySwIwCg61Db
RuST/K0PlSUFK9o6AqTmrcsD/ReQLYK/OEzZBQsPBqMD68ADtdYyIA3VZ7nhWCzc
YODiBl36XIskcwyVAnU9YXs/Hf96MfI1R2fvYGW8jJ4WHb3wT1JxgiUG4rUbA2L3
doxNseggGrKC31njFynVuOpdd/TRfsqzV3Yv5MGFPkNG3w/AoiRtwoMZFUtAox3j
EWbBA/4mYkTKS/Rfgpv7QQHj4ajCHsTL/JNSN8LARwbBomUFdJ+0xdNdr7Ax1zC4
FEUfP0plRMLMypKPSNYzlIF8dKGwW2I8hUMfQpmIBA4BXBE0/mbv21lU2AzTkvb1
FssbIzhCkx3mMzESgYIwnnNkJBatTfFqKOxGm//G7s2y1eFPsrQnSm9lIEFzdG9y
aW5vIDxqb2VfYXN0b3Jpbm9AY29tY2FzdC5uZXQ+iGAEExECACAFAkY2qu8CGwMG
CwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRAb4dzwEzSi9chbAKCTz89zl4etDIdD
Hewo7LNEmfT8uQCgmbneQqTT5VyIEx75nG5KzJh2K2m5Ag0ERjaq7xAIALgM2fwR
tuhRNrwvkYFXTA5grAnnhGqFXPfLt5YlU86QLdu3Z9WJcAAHck1HMCUxdm0gZyNu
q5XQnmr76dbWjftQ+mxYAdhZGjjGV1OQyjfyUoLbxyR0jvaLUTFvMmtxFsHpJvEc
VLscWZUvjPbpcg/BH8EWbDUSCJc70EZMW6TpjyL+1Eq6+n4KB+IWDnn603U3vYFj
ExVfg2CqTIzC/mxAGQ/lg1ujKBnL/VemGpjZzL8jyYVLhAtASTWnwuaL1Sf2kCYh
fApP+06YxkQ39BrJmi7Dg6s5zeRu4le57kPLVAGK0ZYRbaq5asAi9Ni5j/ZLdh/b
F3oUgAOTPQtqbi8AAwUH/1n9jpOXRX7LsfsI5K4gVhHYPUYuy5WuRRxJZ6Y1JbOq
UfePLg+cutaxE8RAvEY1VZvNTvEt7UYPoA3qR3lb4IzLqJimbbKGhhVdHIOYLGnz
nxiwfo4S+my9GEYKLb3iHIR1DCfihhDryVlFYGAMCPNh0w2sNSSenP4cZBuD6V1J
QLitW9aZoURMvtFYU8aO/BlZ7hVlRVNU5juwwAM5t2n2gBeRhMthaAR7OApDypvB
1TM+BeSDchieEAFNkX4leSMbFgP3CJmAXMJXKj8MQmsR8gdccUHGplGFI6IzNklm
L/eWLdhAZsM+LsAo4MpoJzPoQyFIH7wmIPm4b/z7YZmISQQYEQIACQUCRjaq7wIb
DAAKCRAb4dzwEzSi9XiWAKCdDtdnTW9X/6rHxQL/obNiZsEtEwCgrlmYisNacJyf
74k/eLaYWYqu7YI=
=8HMA
-----END PGP PUBLIC KEY BLOCK-----

-----Original Message-----
From: "Gavin Schokman" <g_schokman_at_yahoo.com.au>

Date: Sat, 18 Apr 2009 23:34:29
To: <ccielab_at_groupstudy.com>
Subject: default-information originate route-map

Evening brain-bank,
 
I'm working through some IEWB lab stuff and come across an unexpected
behaviour (unexpected to me at least).
 
I'm trying to conditionally originate a default route via RIP. The condition
I'm using is "does 0.0.0.0/0 appear in local route table?".
If yes -> originate default, if not -> don't originate
 
The problem is that when I use 0.0.0.0/0 in the condition, it doesn't work.
If I use another (random) route as the condition, it works.
See config below:
 
condition_route = 0.0.0.0/0 => doesn't work
 
router rip
 version 2
 default-information originate route-map DEFAULT_MONITOR
 no auto-summary
 
ip route 0.0.0.0 0.0.0.0 Null0
 
ip prefix-list DEFAULT seq 5 permit 0.0.0.0/0
 
route-map DEFAULT_MONITOR permit 10
 match ip address prefix-list DEFAULT
 
! static route exists on Rack1R6
 
Rack1R6#sh ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
  Known via "static", distance 1, metric 0 (connected), candidate default
path
  Routing Descriptor Blocks:
  * directly connected, via Null0
      Route metric is 0, traffic share count is 1
 
! default is not originated and pushed via RIP to Rack1R4
 
Rack1R4#sh ip route 0.0.0.0
% Network not in table
 
condition_route = 1.1.1.1/32 => doesn't work
 
router rip
 version 2
 default-information originate route-map ROUTE_WATCH
 no auto-summary
 
ip route 1.1.1.1 255.255.255.255 Null0
 
ip prefix-list ROUTE_WATCH seq 5 permit 1.1.1.1/32
 
route-map ROUTE_WATCH permit 10
 match ip address prefix-list ROUTE_WATCH
 
! static route exists on Rack1R6

Rack1R6#sh ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
  Known via "static", distance 1, metric 0 (connected), candidate default
path
  Routing Descriptor Blocks:
  * directly connected, via Null0
      Route metric is 0, traffic share count is 1
 
! default IS originated and pushed via RIP to Rack1R4
 
Rack1R4#sh ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
  Known via "rip", distance 120, metric 1, candidate default path
  Redistributing via rip
  Last update from 155.1.146.6 on Ethernet0/1, 00:00:03 ago
  Routing Descriptor Blocks:
  * 155.1.146.6, from 155.1.146.6, 00:00:03 ago, via Ethernet0/1
      Route metric is 1, traffic share count is 1
 
 
Seems to be something strange with 0.0.0.0/0. I know it is matching, see
below
 
Rack1R6#sh ip prefix-list detail
ip prefix-list DEFAULT:
   count: 1, range entries: 0, sequences: 5 - 5, refcount: 2
   seq 5 permit 0.0.0.0/0 (hit count: 20, refcount: 1)
 
 
Any thoughts?
 
Cheers,
Gavin

Blogs and organic groups at http://www.ccie.net
Received on Sat Apr 18 2009 - 23:08:25 ART