Re: [propagating default-networks - RIP V2 and IGRP - ]

From: Curtis Phillips (phillipscurtis@xxxxxxxxxxxx)
Date: Tue Jan 16 2001 - 15:14:10 GMT-3


   
One thing you did not mention, and perhaps the reason for your difficulty is
that the network that it references has to be in it's routing table.

"Connary, Julie Ann" <jconnary@cisco.com> wrote:
Hi All,

I know there have been many discussions on this - but what I don't
understand is how to get IGRP to propagate a default-network. I understand
the defualt-network has to point to a network that is not in the same
address space as IGRP and it must be classfull.
But why does it not propagate to downstream neighbors?

Here is the scenario - R5 is redistributing from IGRP into OSPF and RIP V2
into OSPF. I do not want
to redistribute OSPF into IGRP or RIP V2 - but use a default-network instead.

R7---Rip V2
|
|E 0 - 170.100.42.241/28
|
R5 -------- S0.2 ------------R3 -----s0
------------------r6-------205.0.5.0 AND non 24 bit 170.100 networks off of
R6
  | 170.100.65.0/24 170.100.68.0/24
| OSPF
|
|
S0.1 - igrp - 170.100.1.0/24
|
R4

So, I put in R5 the following command:

ip default-network 205.0.5.0

and I got a gateway of last resort in R5. (I also tried setting the ip
default-network to 170.100.65.0, but that just installed a static route and
no gateway of last resort). However IGRP is not propagating this default to
R4. Is this because 205.0.5.0 is an OSPF learned
route? R4 has no knowledge of the 210.0.5.0 network - however, I thought
that R5 would source down
to R4 that it had a default and R4 would have a gateway of last resort to
R5. R7, the Rip V2 router does receive the default network and it points it
toward R5. Am I missing something here?

Here is my routing table:

Gateway of last resort is 170.100.65.3 to network 210.0.5.0

      170.100.0.0/16 is variably sub
01netted, 13 subnets, 3 masks
I 170.100.200.0/24 [100/8576] via 170.100.1.4, 00:00:50, Serial0.1
C 170.100.42.240/28 is directly connected, Ethernet0
O IA 170.100.233.1/32 [110/75] via 170.100.65.2, 00:25:04, Serial0.2
O IA 170.100.233.0/24 [110/65] via 170.100.65.3, 00:25:04, Serial0.2
O E2 170.100.129.0/24 [110/20] via 170.100.65.2, 00:25:04, Serial0.2
O E2 170.100.150.0/24 [110/20] via 170.100.65.3, 00:25:04, Serial0.2
O IA 170.100.68.0/24 [110/128] via 170.100.65.3, 00:25:04, Serial0.2
O IA 170.100.67.6/32 [110/129] via 17:05:06: %SYS-5-CONFIG_I: Configured
from
  console by console0.100.65.3, 00:25:04, Serial0.2
C 170.100.66.0/28 is directly connected, BRI0
O IA 170.100.64.0/24 [110/74] via 170.100.65.2, 00:25:04, Serial0.2
                         [110/74] via 170.100.65.3, 00:25:04, Serial0.2
C 170.100.65.0/24 is directly connected, Serial0.2
C 170.100.1.0/24 is directly connected, Serial0.1
O 170.100.42.0/24 is a summary, 00:25:01, Null0
R 1.0.0.0/8 [120/1] via 170.100.42.242, 00:00:10, Ethernet0
R 20.0.0.0/8 [120/1] via 170.100.42.242, 00:00:10, Ethernet0
O*E2 210.0.5.0/24 [110/20] via 170.100.65.3, 00:25:07, Serial0.2
I 205.15.150.0/24 [100/14000] via 170.100.1.4, 00:00:54, Serial0.1

Here is the routing table on R4

Gateway of last resort is not set

      170.100.0.0/24 is subnetted, 3 subnets
C 170.100.200.0 is directly connected, Ethernet0
I 170.100.65.0 [100/10476] via 170.100.1.5, 00:01:13, Serial0
C 170.100.1.0 is directly connected, Serial0
      1.0.0.0/24 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, Loopback0
B 205.15.150.0/24 [20/0] via 170.100.200.7, 00:36:34

Also - does anyone understand how to use the defualt-information command
under igrp?
It says it requires an access-list - but the examples in the docs do not
use access-lists.

Thanks,

Julie Ann
------------------------------------------------------------------------
                                         Julie Ann Connary
           | | Network Consulting Engineer
          ||| ||| Federal Support Program
        .|||||. .|||||. 13635 Dulles Technology Drive,
Herndon VA 20171
      .:|||||||||:.:|||||||||:. Pager: 1-888-642-0551
     c i s c o S y s t e m s Email: jconnary@cisco.com

------------------------------------------------------------------------



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:31 GMT-3