From: dhuskey (dhuskey@xxxxxxxx)
Date: Mon Nov 12 2001 - 00:29:05 GMT-3
could you use policy routing?
kind of a static.
is policy based routing considered the same as a static?
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Albert Lu
> Sent: Sunday, November 11, 2001 8:09 PM
> To: ccielab@groupstudy.com
> Cc: 'Erick B.'
> Subject: RE: I'm STUMPED!! EIGRP & IGRP Redistribution (STUMPED BUT MORE
> INFO)
>
>
> Erick,
>
> None of these options would be acceptable in the lab. There must be a way
> for the two routers to have a 200.0.0.0/24 route pointing to each other. I
> think this is a common problem that you could see in a lab. Since each
> router is bound to have a loopback interface with a /32 address
> but part of
> the same /24 network. When you add IGRP into the picture and you have this
> scenario, how are you going to reach that lonely loopback in that IGRP
> network?? I guess the obvious solution is to use a /32 static
> route pointing
> to that loopback, but static routes are often frowned upon in lab exams
> eventhough they are often used in real world scenarios.
>
> Thanks
>
> Albert
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Erick B.
> Sent: Monday, November 12, 2001 12:52 PM
> To: Albert Lu; ccielab@groupstudy.com
> Cc: 'Erick B.'
> Subject: RE: I'm STUMPED!! EIGRP & IGRP Redistribution (STUMPED BUT MORE
> INFO)
>
>
> Albert,
>
> You could use a routing protocol that understands VLSM
> like EIGRP, OSPF, etc. With the addressing you're
> using for the loopbacks on both routers that causes a
> problem with a classful routing protocol. Both
> loopbacks 200.x.x.x/32 will be summarized down to a
> /24 when advertised across the 150.x.x.x/24 serial
> link between the routers.
>
> Another solution short of changing the addressing,
> would be not to advertise the loopbacks and use static
> host routes on both sides.
>
> You could also get creative with NAT.
>
> HTH, Erick
>
> --- Albert Lu <albert_ccie@yahoo.com> wrote:
> > Erick,
> >
> > So how would R4 be able to advertise to R2 it's
> > loopback address and R2
> > advertise it's loopback address to R4 if they are
> > going to advertise it as a
> > 200.0.0.0/24 route to each other?
> >
> > Thanks
> >
> > Albert
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com
> > [mailto:nobody@groupstudy.com]On Behalf Of
> > Erick B.
> > Sent: Monday, November 12, 2001 9:15 AM
> > To: Albert Lu; ccielab@groupstudy.com
> > Subject: RE: I'm STUMPED!! EIGRP & IGRP
> > Redistribution (STUMPED BUT MORE
> > INFO)
> >
> >
> > Hi,
> >
> > Looking at this closer, you're running into the same
> > issue you're having with the other question you
> > posed.
> >
> >
> > In this case, both routers have a 200.x.x.x/32
> > loopback that is getting summarized down to a
> > natural
> > class boundary of /24 for IGRP. Both routers are
> > sending/receiving this route which is causing a
> > conflict.
> >
> > Erick
> >
> > --- Albert Lu <albert_ccie@yahoo.com> wrote:
> > > Hello All,
> > >
> > > Ok, now I've shut down all the other interfaces so
> > > that only R2 and R4 are
> > > talking to each other. This will cut down on the
> > > amount of routes being in
> > > the routing table. I'm sure some of you will
> > notice
> > > that I changed the
> > > timers for IGRP, this was so that I can see the
> > > results faster of this weird
> > > behaviour rather faster. I've now taken that out,
> > > and here is the new
> > > output:
> > >
> > > Just a few comments. R4 seems to send the
> > > 200.0.0.0/24 route out once and
> > > doesn't want to send again, this flushes out the
> > > route in R2 because it
> > > hasn't received any updates. Afterwards, it goes
> > > nuts!! and sends the
> > > 200.0.0.0/24 route to R2 as though it owns it,
> > > creating a routing loop!!!
> > >
> > >
> >
> ------------------------------------------------------------------
> ----------
> > > ---
> > > R2#sir
> > > Codes: C - connected, S - static, I - IGRP, R -
> > RIP,
> > > M - mobile, B - BGP
> > > D - EIGRP, EX - EIGRP external, O - OSPF,
> > IA
> > > - OSPF inter area
> > > N1 - OSPF NSSA external type 1, N2 - OSPF
> > > NSSA external type 2
> > > E1 - OSPF external type 1, E2 - OSPF
> > external
> > > type 2, E - EGP
> > > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS
> > > level-2, ia - IS-IS inter
> > > area
> > > * - candidate default, U - per-user static
> > > route, o - ODR
> > > P - periodic downloaded static route
> > >
> > > Gateway of last resort is not set
> > >
> > > 200.0.0.0/24 is variably subnetted, 2
> > subnets,
> > > 2 masks
> > > I 200.0.0.0/24 [100/8976] via 150.50.24.4,
> > > 00:04:32, Serial0/0.1
> > > C 200.0.0.2/32 is directly connected,
> > > Loopback0
> > > I 10.0.0.0/8 [100/8976] via 150.50.24.4,
> > > 00:00:37, Serial0/0.1
> > > 150.50.0.0/24 is subnetted, 1 subnets
> > > C 150.50.24.0 is directly connected,
> > > Serial0/0.1
> > > R2#
> > > 09:54:17: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.4 (Serial0/0.1)
> > > <----------******** WHY?!?!?!
> > > 09:54:17: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > 09:54:17: IGRP: edition is now 255
> > > 09:54:17: IGRP: sending update to 255.255.255.255
> > > via Serial0/0.1
> > > (150.50.24.2)
> > > 09:54:17: network 200.0.0.0, metric=501
> > > 09:54:17: IGRP: received update from 150.50.24.4
> > on
> > > Serial0/0.1
> > > 09:54:17: network 200.0.0.0, metric 8976
> > > (neighbor 501)
> > > 09:54:17: network 10.0.0.0, metric 8976
> > > (neighbor 501)
> > > R2#
> > > 09:54:26: IGRP: received update from 150.50.24.4
> > on
> > > Serial0/0.1
> > > 09:54:26: network 200.0.0.0, metric 8976
> > > (neighbor 501)
> > > 09:54:26: network 10.0.0.0, metric 8976
> > > (neighbor 501)
> > > R2#sir
> > > Codes: C - connected, S - static, I - IGRP, R -
> > RIP,
> > > M - mobile, B - BGP
> > > D - EIGRP, EX - EIGRP external, O - OSPF,
> > IA
> > > - OSPF inter area
> > > N1 - OSPF NSSA external type 1, N2 - OSPF
> > > NSSA external type 2
> > > E1 - OSPF external type 1, E2 - OSPF
> > external
> > > type 2, E - EGP
> > > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS
> > > level-2, ia - IS-IS inter
> > > area
> > > * - candidate default, U - per-user static
> > > route, o - ODR
> > > P - periodic downloaded static route
> > >
> > > Gateway of last resort is not set
> > >
> > > 200.0.0.0/24 is variably subnetted, 2
> > subnets,
> > > 2 masks
> > > I 200.0.0.0/24 is possibly down,
> > > routing via 150.50.24.4, Serial0/0.1
> > > C 200.0.0.2/32 is directly connected,
> > > Loopback0
> > > I 10.0.0.0/8 [100/8976] via 150.50.24.4,
> > > 00:00:25, Serial0/0.1
> > > 150.50.0.0/24 is subnetted, 1 subnets
> > > C 150.50.24.0 is directly connected,
> > > Serial0/0.1
> > > R2#
> > > 09:55:39: IGRP: received update from 150.50.24.4
> > on
> > > Serial0/0.1
> > > 09:55:39: network 200.0.0.0, metric 8976
> > > (neighbor 501)
> > > 09:55:39: network 10.0.0.0, metric 8976
> > > (neighbor 501)
> > > R2#
> > > 09:55:42: IGRP: sending update to 255.255.255.255
> > > via Serial0/0.1
> > > (150.50.24.2)
> > > 09:55:42: network 200.0.0.0, metric=501
> > > R2#
> > > 09:56:59: IGRP: received update from 150.50.24.4
> > on
> > > Serial0/0.1
> > > 09:56:59: network 200.0.0.0, metric 8976
> > > (neighbor 501)
> > > 09:56:59: network 10.0.0.0, metric 8976
> > > (neighbor 501)
> > > R2#
> > > 09:57:03: IGRP: sending update to 255.255.255.255
> > > via Serial0/0.1
> > > (150.50.24.2)
> > > 09:57:03: network 200.0.0.0, metric=501
> > > R2#
> > > 09:58:15: IGRP: received update from 150.50.24.4
> > on
> > > Serial0/0.1
> > > 09:58:15: network 200.0.0.0, metric 8976
> > > (neighbor 501)
> > > 09:58:15: network 10.0.0.0, metric 8976
> > > (neighbor 501)
> > > R2#
> > >
> > >
> > >
> >
> ------------------------------------------------------------------
> ----------
> > > ---
> > > R4#
> > > 09:52:07: IGRP: sending update to 255.255.255.255
> > > via Serial0/0
> > > (150.50.24.4)
> > > 09:52:07: network 200.0.0.0, metric=501
> > > 09:52:07: network 10.0.0.0, metric=501
> > > R4#
> > > 09:53:28: IGRP: sending update to 255.255.255.255
> > > via Serial0/0
> > > (150.50.24.4)
> > > 09:53:28: network 200.0.0.0, metric=501
> > > 09:53:28: network 10.0.0.0, metric=501
> > > R4#
> > > 09:54:45: IGRP: received update from 150.50.24.2
> > on
> > > Serial0/0
> > > 09:54:45: network 200.0.0.0, metric 8976
> > > (neighbor 501)
> > > <----------************************** I'm suppose
> > to
> > > get this!!
> > > 09:54:45: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:54:45: RT: add 200.0.0.0/24 via 150.50.24.2,
> > igrp
> > > metric [100/8976]
> > > 09:54:45: IGRP: edition is now 19
> > > 09:54:45: IGRP: sending update to 255.255.255.255
> > > via Serial0/0
> > > (150.50.24.4)
> > > 09:54:45: network 200.0.0.0, metric=501
> > > 09:54:45: network 10.0.0.0, metric=501
> > > R4#
> > > 09:54:54: IGRP: sending update to 255.255.255.255
> > > via Serial0/0
> > > (150.50.24.4)
> > > 09:54:54: network 200.0.0.0, metric=501
> > > 09:54:54: network 10.0.0.0, metric=501
> > > R4#sir
> > > Codes: C - connected, S - static, I - IGRP, R -
> > RIP,
> > > M - mobile, B - BGP
> > > D - EIGRP, EX - EIGRP external, O - OSPF,
> > IA
> > > - OSPF inter area
> > > N1 - OSPF NSSA external type 1, N2 - OSPF
> > > NSSA external type 2
> > > E1 - OSPF external type 1, E2 - OSPF
> > external
> > > type 2, E - EGP
> > > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS
> > > level-2, ia - IS-IS inter
> > > area
> > > * - candidate default, U - per-user static
> > > route, o - ODR
> > > P - periodic downloaded static route
> > >
> > > Gateway of last resort is not set
> > >
> > > 200.0.0.0/24 is variably subnetted, 2
> > subnets,
> > > 2 masks
> > > I 200.0.0.0/24 [100/8976] via 150.50.24.2,
> > > 00:00:29, Serial0/0
> > > C 200.0.0.4/32 is directly connected,
> > > Loopback0
> > > 10.0.0.0/24 is subnetted, 1 subnets
> > > C 10.1.1.0 is directly connected, Loopback1
> > > 150.50.0.0/24 is subnetted, 1 subnets
> > > C 150.50.24.0 is directly connected,
> > Serial0/0
> > > R4#
> > > 09:56:07: IGRP: sending update to 255.255.255.255
> > > via Serial0/0
> > > (150.50.24.4)
> > > 09:56:07: network 200.0.0.0, metric=501
> > > 09:56:07: network 10.0.0.0, metric=501
> > > R4#
> > > 09:56:10: IGRP: received update from 150.50.24.2
> > on
> > > Serial0/0
> > > 09:56:11: network 200.0.0.0, metric 8976
> > > (neighbor 501)
> > > R4#
> > > 09:57:28: IGRP: sending update to 255.255.255.255
> > > via Serial0/0
> > > (150.50.24.4)
> > > 09:57:28: network 200.0.0.0, metric=501
> > > 09:57:28: network 10.0.0.0, metric=501
> > > R4#
> > > 09:57:32: IGRP: received update from 150.50.24.2
> > on
> > > Serial0/0
> > > 09:57:32: network 200.0.0.0, metric 8976
> > > (neighbor 501)
> > > R4#
> > > 09:58:43: IGRP: sending update to 255.255.255.255
> > > via Serial0/0
> > > (150.50.24.4)
> > > 09:58:43: network 200.0.0.0, metric=501
> > > 09:58:43: network 10.0.0.0, metric=501
> > > R4#
> > > 09:58:53: IGRP: received update from 150.50.24.2
> > on
> > > Serial0/0
> > > 09:58:53: network 200.0.0.0, metric 8976
> > > (neighbor 501)
> > > R4#
> > >
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com
> > > [mailto:nobody@groupstudy.com]On Behalf Of
> > > Albert Lu
> > > Sent: Monday, November 12, 2001 8:30 AM
> > > To: ccielab@groupstudy.com
> > > Subject: I'm STUMPED!! EIGRP & IGRP Redistribution
> > >
> > >
> > > Hello All,
> > >
> > > What can I say?? I give up!! Could someone please
> > > take a look at my configs
> > > and tell me why my 200.0.0.0/24 route is going
> > into
> > > hold down?
> > >
> > > Basically, the 2 routers that are involved in this
> > > are R2 and R4 with R2
> > > running EIGRP and IGRP, and R4 running IGRP only.
> > R2
> > > has a 200.0.0.2/32
> > > loopback being redistributed from EIGRP into IGRP
> > > and towards R4. R4 has a
> > > 200.0.0.4/32 loopback being redistributed
> > connected
> > > into IGRP on R4.
> > >
> > > I've filtered out the propagation of the
> > > 200.0.0.4/32 route into IGRP as can
> > > be seen in the deny_200 route-map on R2, so the
> > only
> > > router that should be
> > > getting any 200.0.0.0 routes should be R2 seeing
> > > R4's loopback of
> > > 200.0.0.4/32 (seen as a 200.0.0.0/24 on R4).
> > > However, this 200.0.0.0/24 is
> > > being sent back to R4 after R2 goes into hold down
> > > for the 200.0.0.0/24
> > > route.
> > >
> > > I've been working on this problem for too long.
> > > Please help!!
> > >
> > > Thanks in advance
> > >
> > > Albert
> > >
> > >
> > >
> > > R2 Config
> > > --------------
> > > !
> > > version 12.1
> > > service timestamps debug uptime
> > > service timestamps log uptime
> > > no service password-encryption
> > > !
> > > hostname R2
> > > !
> > > logging buffered 55000 debugging
> > > enable password cisco
> > > !
> > > !
> > > !
> > > !
> > > !
> > > ip subnet-zero
> > > ip tcp synwait-time 5
> > > no ip domain-lookup
> > > !
> > > cns event-service server
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > interface Loopback0
> > > ip address 200.0.0.2 255.255.255.255
> > > !
> > > interface Ethernet0/0
> > > ip address 150.50.17.2 255.255.255.0
> > > half-duplex
> > > !
> > > interface Serial0/0
> > > no ip address
> > > encapsulation frame-relay
> > > no fair-queue
> > > !
> > > interface Serial0/0.1 point-to-point
> > > ip address 150.50.24.2 255.255.255.0
> > > ip summary-address eigrp 1 150.50.100.0
> > > 255.255.255.0 5
> > > ip summary-address eigrp 1 150.50.7.0
> > 255.255.255.0
> > > 5
> > > ip summary-address eigrp 1 150.50.5.0
> > 255.255.255.0
> > > 5
> > > no arp frame-relay
> > > frame-relay interface-dlci 104
> > > !
> > > interface Serial0/0.2 multipoint
> > > ip address 150.50.100.2 255.255.255.224
> > > ip hello-interval eigrp 1 20
> > > ip hold-time eigrp 1 60
> > > frame-relay interface-dlci 105
> > > frame-relay interface-dlci 106
> > > !
> > > interface TokenRing0/0
> > > no ip address
> > > shutdown
> > > ring-speed 16
> > > !
> > > interface ATM1/0
> > > no ip address
> > > shutdown
> > > atm vc-per-vp 4096
> > > no atm ilmi-keepalive
> > > !
> > > router eigrp 1
> > > redistribute igrp 2 metric 1000 100 255 1 1500
> > > passive-interface Serial0/0.1
> > > passive-interface Loopback0
> > > network 150.50.0.0
> > > network 200.0.0.2 0.0.0.0
> > > no auto-summary
> > > no eigrp log-neighbor-changes
> > > !
> > > router igrp 2
> > > timers basic 5 15 20 30
> > > redistribute eigrp 1 metric 1000 100 255 1 1500
> > > route-map deny_200
> > > passive-interface Ethernet0/0
> > > passive-interface Serial0/0.2
> > > network 150.50.0.0
> > > !
> > > ip classless
> > > ip http server
> > > !
> > > access-list 1 deny 200.0.0.0 0.0.0.255
> > > access-list 1 permit any
> > > route-map deny_200 permit 10
> > > match ip address 1
> > > !
> > > !
> > >
> > > R4 Config
> > > ---------
> > >
> > > !
> > > version 12.1
> > > service timestamps debug uptime
> > > service timestamps log uptime
> > > no service password-encryption
> > > !
> > > hostname R4
> > > !
> > > logging buffered 55000 debugging
> > > enable secret 5 $1$a4Gk$e21ITX3LOKrRnMlIeVILY1
> > > enable password cisco
> > > !
> > > !
> > > !
> > > !
> > > !
> > > ip subnet-zero
> > > ip tcp synwait-time 5
> > > no ip domain-lookup
> > > !
> > > cns event-service server
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > interface Loopback0
> > > ip address 200.0.0.4 255.255.255.255
> > > !
> > > interface Loopback1
> > > ip address 10.1.1.4 255.255.255.0
> > > !
> > > interface FastEthernet0/0
> > > no ip address
> > > shutdown
> > > duplex auto
> > > speed auto
> > > !
> > > interface Serial0/0
> > > ip address 150.50.24.4 255.255.255.0
> > > encapsulation frame-relay
> > > ip split-horizon
> > > no fair-queue
> > > frame-relay map ip 150.50.24.2 401 broadcast
> > > no frame-relay inverse-arp
> > > !
> > > interface Serial0/1
> > > no ip address
> > > shutdown
> > > !
> > > router igrp 2
> > > timers basic 5 15 20 30
> > > redistribute connected
> > > network 150.50.0.0
> > > !
> > > ip classless
> > > no ip http server
> > > !
> > >
> > >
> > > R2#sh ip ro
> > > Codes: C - connected, S - static, I - IGRP, R -
> > RIP,
> > > M - mobile, B - BGP
> > > D - EIGRP, EX - EIGRP external, O - OSPF,
> > IA
> > > - OSPF inter area
> > > N1 - OSPF NSSA external type 1, N2 - OSPF
> > > NSSA external type 2
> > > E1 - OSPF external type 1, E2 - OSPF
> > external
> > > type 2, E - EGP
> > > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS
> > > level-2, ia - IS-IS inter
> > > area
> > > * - candidate default, U - per-user static
> > > route, o - ODR
> > > P - periodic downloaded static route
> > >
> > > Gateway of last resort is not set
> > >
> > > 200.0.0.0/32 is subnetted, 6 subnets
> > > D EX 200.0.0.8 [170/297784576] via
> > 150.50.100.5,
> > > 00:03:19, Serial0/0.2
> > > [170/297784576] via
> > 150.50.100.6,
> > > 00:03:19, Serial0/0.2
> > > D EX 200.0.0.1 [170/2611200] via 150.50.17.1,
> > > 00:03:19, Ethernet0/0
> > > C 200.0.0.2 is directly connected, Loopback0
> > > D EX 200.0.0.5 [170/3097600] via 150.50.100.5,
> > > 00:03:19, Serial0/0.2
> > > D EX 200.0.0.6 [170/3097600] via 150.50.100.6,
> > > 00:03:19, Serial0/0.2
> > > D EX 200.0.0.7 [170/3100160] via 150.50.100.5,
> > > 00:03:19, Serial0/0.2
> > > [170/3100160] via 150.50.100.6,
> > > 00:03:20, Serial0/0.2
> > > 173.16.0.0/22 is subnetted, 1 subnets
> > > D 173.16.0.0 [90/2300416] via 150.50.100.5,
> > > 00:03:20, Serial0/0.2
> > > [90/2300416] via 150.50.100.6,
> > > 00:03:20, Serial0/0.2
> > > 150.50.0.0/16 is variably subnetted, 12
> > > subnets, 3 masks
> > > D 150.50.200.0/24 [90/409600] via
> > 150.50.17.1,
> > > 00:03:22, Ethernet0/0
> > > D 150.50.4.0/24 [90/297886976] via
> > > 150.50.100.5, 00:03:22, Serial0/0.2
> > > [90/297886976] via
> > > 150.50.100.6, 00:03:22, Serial0/0.2
> > > D 150.50.5.0/25 [90/297758976] via
> > > 150.50.100.5, 00:03:22, Serial0/0.2
> > > [90/297758976] via
> > > 150.50.100.6, 00:03:22, Serial0/0.2
> > > D 150.50.5.0/24 is a summary, 00:03:22,
> > Null0
> > > D 150.50.7.0/25 [90/2172416] via
> > 150.50.100.5,
> > > 00:03:22, Serial0/0.2
> > > [90/2172416] via
> > 150.50.100.6,
> > > 00:03:22, Serial0/0.2
> > > D 150.50.7.0/24 is a summary, 00:03:22,
> > Null0
> > > D 150.50.3.0/24 [90/297886976] via
> > > 150.50.100.5, 00:03:22, Serial0/0.2
> > > [90/297886976] via
> > > 150.50.100.6, 00:03:22, Serial0/0.2
> > > C 150.50.17.0/24 is directly connected,
> > > Ethernet0/0
> > > D 150.50.18.0/24 [90/409600] via
> > 150.50.17.1,
> > > 00:03:22, Ethernet0/0
> > > C 150.50.24.0/24 is directly connected,
> > > Serial0/0.1
> > > D 150.50.100.0/24 is a summary, 00:03:24,
> > > Null0
> > > C 150.50.100.0/27 is directly connected,
> > > Serial0/0.2
> > > R2#
> > > 09:31:16: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:31:16: RT: add 200.0.0.0/24 via 150.50.24.4,
> > igrp
> > > metric [100/8976]
> > > 09:31:16: RT: add 10.0.0.0/8 via 150.50.24.4, igrp
> > > metric [100/8976]
> > > R2#
> > > 09:31:31: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.4 (Serial0/0.1)
> > > 09:31:31: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R2#
> > > 09:31:49: RT: garbage collecting entry for
> > 200.0.0.0
> > > R2#
> > > 09:31:51: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:31:51: RT: add 200.0.0.0/24 via 150.50.24.4,
> > igrp
> > > metric [100/8976]
> > > R2#
> > > 09:32:08: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.4 (Serial0/0.1)
> > > 09:32:08: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R2#
> > > 09:32:25: RT: garbage collecting entry for
> > 200.0.0.0
> > > R2#
> > > 09:32:26: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:32:26: RT: add 200.0.0.0/24 via 150.50.24.4,
> > igrp
> > > metric [100/8976]
> > > R2#
> > > 09:32:43: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.4 (Serial0/0.1)
> > > 09:32:43: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R2#
> > > 09:32:57: RT: garbage collecting entry for
> > 200.0.0.0
> > > 09:32:57: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:32:57: RT: add 200.0.0.0/24 via 150.50.24.4,
> > igrp
> > > metric [100/8976]
> > > R2#
> > > 09:33:15: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.4 (Serial0/0.1)
> > > 09:33:15: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R2#
> > > 09:33:29: RT: garbage collecting entry for
> > 200.0.0.0
> > > 09:33:29: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:33:29: RT: add 200.0.0.0/24 via 150.50.24.4,
> > igrp
> > > metric [100/8976]
> > > R2#
> > > 09:33:46: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.4 (Serial0/0.1)
> > > 09:33:46: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R2#
> > > 09:34:00: RT: garbage collecting entry for
> > 200.0.0.0
> > > R2#
> > > 09:34:01: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:34:01: RT: add 200.0.0.0/24 via 150.50.24.4,
> > igrp
> > > metric [100/8976]
> > > R2#
> > > 09:34:18: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.4 (Serial0/0.1)
> > > 09:34:18: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R2#
> > > 09:34:33: RT: garbage collecting entry for
> > 200.0.0.0
> > > 09:34:33: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:34:33: RT: add 200.0.0.0/24 via 150.50.24.4,
> > igrp
> > > metric [100/8976]
> > > R2#
> > >
> > > R4#sh ip ro
> > > Codes: C - connected, S - static, I - IGRP, R -
> > RIP,
> > > M - mobile, B - BGP
> > > D - EIGRP, EX - EIGRP external, O - OSPF,
> > IA
> > > - OSPF inter area
> > > N1 - OSPF NSSA external type 1, N2 - OSPF
> > > NSSA external type 2
> > > E1 - OSPF external type 1, E2 - OSPF
> > external
> > > type 2, E - EGP
> > > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS
> > > level-2, ia - IS-IS inter
> > > area
> > > * - candidate default, U - per-user static
> > > route, o - ODR
> > > P - periodic downloaded static route
> > >
> > > Gateway of last resort is not set
> > >
> > > 200.0.0.0/32 is subnetted, 1 subnets
> > > C 200.0.0.4 is directly connected, Loopback0
> > > I 173.16.0.0/16 [100/10986] via 150.50.24.2,
> > > 00:00:02, Serial0/0
> > > 10.0.0.0/24 is subnetted, 1 subnets
> > > C 10.1.1.0 is directly connected, Loopback1
> > > 150.50.0.0/24 is subnetted, 9 subnets
> > > I 150.50.200.0 [100/9076] via 150.50.24.2,
> > > 00:00:02, Serial0/0
> > > I 150.50.4.0 [100/1165621] via 150.50.24.2,
> > > 00:00:02, Serial0/0
> > > I 150.50.5.0 [100/1165121] via 150.50.24.2,
> > > 00:00:02, Serial0/0
> > > I 150.50.7.0 [100/10486] via 150.50.24.2,
> > > 00:00:03, Serial0/0
> > > I 150.50.3.0 [100/1165621] via 150.50.24.2,
> > > 00:00:03, Serial0/0
> > > I 150.50.17.0 [100/8576] via 150.50.24.2,
> > > 00:00:03, Serial0/0
> > > I 150.50.18.0 [100/9076] via 150.50.24.2,
> > > 00:00:03, Serial0/0
> > >
> > > R4#
> > > 09:32:00: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:32:00: RT: add 200.0.0.0/24 via 150.50.24.2,
> > igrp
> > > metric [100/8976]
> > > R4#
> > > 09:32:19: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.2 (Serial0/0)
> > > 09:32:19: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R4#
> > > 09:32:33: RT: garbage collecting entry for
> > 200.0.0.0
> > > R4#
> > > 09:32:36: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:32:36: RT: add 200.0.0.0/24 via 150.50.24.2,
> > igrp
> > > metric [100/8976]
> > > R4#
> > > 09:32:54: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.2 (Serial0/0)
> > > 09:32:54: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R4#
> > > 09:33:08: RT: garbage collecting entry for
> > 200.0.0.0
> > > R4#
> > > 09:33:11: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:33:11: RT: add 200.0.0.0/24 via 150.50.24.2,
> > igrp
> > > metric [100/8976]
> > > R4#
> > > 09:33:30: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.2 (Serial0/0)
> > > 09:33:30: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R4#
> > > 09:33:43: RT: garbage collecting entry for
> > 200.0.0.0
> > > 09:33:43: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:33:43: RT: add 200.0.0.0/24 via 150.50.24.2,
> > igrp
> > > metric [100/8976]
> > > R4#
> > > 09:34:02: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.2 (Serial0/0)
> > > 09:34:02: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R4#
> > > 09:34:16: RT: garbage collecting entry for
> > 200.0.0.0
> > > R4#
> > > 09:34:19: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:34:19: RT: add 200.0.0.0/24 via 150.50.24.2,
> > igrp
> > > metric [100/8976]
> > > R4#
> > > 09:34:35: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.2 (Serial0/0)
> > > 09:34:35: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R4#
> > > 09:34:53: RT: garbage collecting entry for
> > 200.0.0.0
> > > R4#
> > > 09:34:57: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:34:57: RT: add 200.0.0.0/24 via 150.50.24.2,
> > igrp
> > > metric [100/8976]
> > > R4#
> > > 09:35:16: RT: flushed route to 200.0.0.0 via
> > > 150.50.24.2 (Serial0/0)
> > > 09:35:16: RT: no routes to 200.0.0.0, entering
> > > holddown
> > > R4#
> > > 09:35:29: RT: garbage collecting entry for
> > 200.0.0.0
> > > R4#
> > > 09:35:50: RT: network 200.0.0.0 is now variably
> > > masked
> > > 09:35:50: RT: add 200.0.0.0/24 via 150.50.24.2,
> > igrp
> > > metric [100/8976]
> > > R4#
>
>
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:13 GMT-3