From: Nick Shah (nshah@connect.com.au)
Date: Thu Sep 19 2002 - 06:12:05 GMT-3
John
I recreated your exact scenario, and the only way to get the RIP routes into
IGRP & vice versa is to mutually redistribute between them (which is what it
should be , theoritically speaking)
I HAD TO redistribute on R5 between everybody2everybody to get it all going.
Here are the configs, sich while ISDN is down, sich after ISDN kicks in
(ethernet dies)
R2 ---- eth ---- R4
| |
| |
R5 -------------------------R6
|
|
R7
If my 'creative artistry' doesnt come good then basically this is it :
R2 -ether-R4, R2-isdn-R5, R5-fr-R4, R5-fr-R6 & R5 - eth-R7 . R2 has backup
interface E0 to dialer0 (basically dialer 0 is backup interface for e0)
R2 : (nothing special in R2 config, its running IGRP)
150.50.0.0/24 is subnetted, 11 subnets
I 150.50.177.0 [100/10576] via 150.50.42.4, 00:00:01, Ethernet0
C 150.50.42.0 is directly connected, Ethernet0
I 150.50.4.0 [100/1600] via 150.50.42.4, 00:00:01, Ethernet0
I 150.50.5.0 [100/7100] via 150.50.42.4, 00:00:01, Ethernet0
I 150.50.6.0 [100/7100] via 150.50.42.4, 00:00:01, Ethernet0
I 150.50.7.0 [100/7100] via 150.50.42.4, 00:00:01, Ethernet0
C 150.50.2.0 is directly connected, Loopback0
I 150.50.9.0 [100/160350] via 150.50.42.4, 00:00:02, Ethernet0
I 150.50.17.0 [100/7100] via 150.50.42.4, 00:00:02, Ethernet0
I 150.50.100.0 [100/8576] via 150.50.42.4, 00:00:02, Ethernet0
I 150.50.77.0 [100/7100] via 150.50.42.4, 00:00:02, Ethernet0
R4 : (redistributing IGRP2OSPF & vice versa)
router ospf 1
router-id 200.0.0.4
redistribute igrp 1 subnets
network 150.50.4.4 0.0.0.0 area 0
network 150.50.100.4 0.0.0.0 area 0
distribute-list IGRP out igrp 1
!
router igrp 1
timers basic 5 15 20 20
redistribute ospf 1
passive-interface default
no passive-interface Ethernet0
no passive-interface Loopback1
network 150.50.0.0
default-metric 2000 2000 255 1 1500
distance 130 ----> I am paranoid & igrp is a bi***
150.50.0.0/24 is subnetted, 11 subnets
I 150.50.177.0 [130/10476] via 150.50.100.5, 00:00:02, Serial0
C 150.50.42.0 is directly connected, Ethernet0
C 150.50.4.0 is directly connected, Loopback0
O 150.50.5.0 [110/65] via 150.50.100.5, 00:24:27, Serial0
O 150.50.6.0 [110/65] via 150.50.100.6, 00:24:27, Serial0
O E2 150.50.7.0 [110/20] via 150.50.100.5, 00:22:57, Serial0
I 150.50.2.0 [130/1600] via 150.50.42.2, 00:00:05, Ethernet0
I 150.50.9.0 [130/160250] via 150.50.100.5, 00:00:03, Serial0
O E2 150.50.17.0 [110/20] via 150.50.100.5, 00:24:28, Serial0
C 150.50.100.0 is directly connected, Serial0
O E2 150.50.77.0 [
R5 : (redistributing everybody)
router ospf 1
router-id 200.0.0.5
log-adjacency-changes
summary-address 150.50.17.0 255.255.255.0
summary-address 150.50.7.0 255.255.255.0
redistribute rip subnets
redistribute igrp 1 subnets
network 150.50.5.5 0.0.0.0 area 0
network 150.50.100.5 0.0.0.0 area 0
network 200.0.0.5 0.0.0.0 area 0
distribute-list FROMRIP out rip
distribute-list IGRP out igrp 1
distribute-list FROMOSPF in
!
router rip
version 2
redistribute ospf 1 metric 3
redistribute igrp 1 metric 2
passive-interface default
no passive-interface Ethernet0
network 150.50.0.0
!
router igrp 1
timers basic 5 15 20 20
redistribute rip
redistribute ospf 1
network 150.50.0.0
default-metric 2000 2000 255 1 1500
distance 130
!!!! Note that while ISDN is down, IGRP is not active and so R5 doesnt learn
anything via IGRP (fairly obvious)
150.50.0.0/16 is variably subnetted, 11 subnets, 3 masks
R 150.50.177.0/24 [120/1] via 150.50.7.7, 00:00:21, Ethernet0
O E2 150.50.42.0/24 [110/20] via 150.50.100.4, 00:24:01, Serial0
O 150.50.4.0/24 [110/65] via 150.50.100.4, 00:24:01, Serial0
C 150.50.5.0/24 is directly connected, Loopback0
O 150.50.6.0/24 [110/65] via 150.50.100.6, 00:24:01, Serial0
O 150.50.7.0/24 is a summary, 00:07:04, Null0
C 150.50.7.0/25 is directly connected, Ethernet0
C 150.50.9.0/24 is directly connected, Dialer0
C 150.50.100.0/24 is directly connected, Serial0
R 150.50.77.0/24 [120/1] via 150.50.7.7, 00:00:22, Ethernet0
R 150.50.17.64/27 [120/1] via 150.50.7.7, 00:00:22, Ethernet0
R6 : straightforward, running on ly OSPF
150.50.0.0/24 is subnetted, 9 subnets
O E2 150.50.42.0 [110/20] via 150.50.100.4, 00:26:45, Serial0
O 150.50.4.0 [110/65] via 150.50.100.4, 00:26:45, Serial0
O 150.50.5.0 [110/65] via 150.50.100.5, 00:26:45, Serial0
C 150.50.6.0 is directly connected, Loopback0
O E2 150.50.7.0 [110/20] via 150.50.100.5, 00:25:09, Serial0
O E2 150.50.9.0 [110/20] via 150.50.100.4, 00:18:02, Serial0
O E2 150.50.17.0 [110/20] via 150.50.100.5, 00:26:46, Serial0
C 150.50.100.0 is directly connected, Serial0
O E2 150.50.77.0 [110/20] via 150.50.100.5, 00:26:46, Serial0
TermServ#
R7 : (straightforward, running RIP)
150.50.0.0/16 is variably subnetted, 11 subnets, 3 masks
C 150.50.177.0/24 is directly connected, Loopback0
R 150.50.42.0/24 [120/3] via 150.50.7.5, 00:00:18, FastEthernet0
R 150.50.4.0/24 [120/3] via 150.50.7.5, 00:00:18, FastEthernet0
R 150.50.5.0/24 [120/1] via 150.50.7.5, 00:00:18, FastEthernet0
R 150.50.6.0/24 [120/3] via 150.50.7.5, 00:00:18, FastEthernet0
R 150.50.7.0/24 [120/3] via 150.50.7.5, 00:00:18, FastEthernet0
C 150.50.7.0/25 is directly connected, FastEthernet0
R 150.50.9.0/24 [120/1] via 150.50.7.5, 00:00:19, FastEthernet0
R 150.50.100.0/24 [120/1] via 150.50.7.5, 00:00:19, FastEthernet0
C 150.50.77.0/24 is directly connected, Loopback1
C 150.50.17.64/27 is directly connected, Serial0
R7#
Then the FUN begins... ETHERNET port shut down from the switch (going to R2)
R2 :
150.50.0.0/24 is subnetted, 10 subnets
I 150.50.177.0 [100/160250] via 150.50.9.5, 00:00:01, Dialer0
I 150.50.42.0 [100/160250] via 150.50.9.5, 00:00:01, Dialer0
I 150.50.4.0 [100/160250] via 150.50.9.5, 00:00:01, Dialer0
I 150.50.5.0 [100/158750] via 150.50.9.5, 00:00:01, Dialer0
I 150.50.6.0 [100/160250] via 150.50.9.5, 00:00:01, Dialer0
I 150.50.7.0 [100/160250] via 150.50.9.5, 00:00:01, Dialer0
C 150.50.2.0 is directly connected, Loopback0
C 150.50.9.0 is directly connected, Dialer0
I 150.50.100.0 [100/160250] via 150.50.9.5, 00:00:02, Dialer0
I 150.50.77.0 [100/160250] via 150.50.9.5, 00:00:02, Dialer0
R2#ping 150.50.7.7 (pinging R7 loopback)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 150.50.7.7, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 244/344/744 ms
R2
R7 :
150.50.0.0/16 is variably subnetted, 12 subnets, 3 masks
C 150.50.177.0/24 is directly connected, Loopback0
R 150.50.42.0/24 [120/3] via 150.50.7.5, 00:00:18, FastEthernet0
R 150.50.4.0/24 [120/3] via 150.50.7.5, 00:00:18, FastEthernet0
R 150.50.5.0/24 [120/1] via 150.50.7.5, 00:00:18, FastEthernet0
R 150.50.6.0/24 [120/3] via 150.50.7.5, 00:00:18, FastEthernet0
R 150.50.7.0/24 [120/3] via 150.50.7.5, 00:00:18, FastEthernet0
C 150.50.7.0/25 is directly connected, FastEthernet0
R 150.50.2.0/24 [120/2] via 150.50.7.5, 00:00:19, FastEthernet0
R 150.50.9.0/24 [120/1] via 150.50.7.5, 00:00:19, FastEthernet0
R 150.50.100.0/24 [120/1] via 150.50.7.5, 00:00:19, FastEthernet0
C 150.50.77.0/24 is directly connected, Loopback1
C 150.50.17.64/27 is directly connected, Serial0
R7#ping 150.50.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 150.50.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 240/343/528 ms
R7#
R5 :
150.50.0.0/16 is variably subnetted, 12 subnets, 3 masks
R 150.50.177.0/24 [120/1] via 150.50.7.7, 00:00:14, Ethernet0
O E2 150.50.42.0/24 [110/20] via 150.50.100.4, 00:28:32, Serial0
O 150.50.4.0/24 [110/65] via 150.50.100.4, 00:28:32, Serial0
C 150.50.5.0/24 is directly connected, Loopback0
O 150.50.6.0/24 [110/65] via 150.50.100.6, 00:28:32, Serial0
O 150.50.7.0/24 is a summary, 00:11:36, Null0
C 150.50.7.0/25 is directly connected, Ethernet0
I 150.50.2.0/24 [130/158750] via 150.50.9.2, 00:00:03, Dialer0
C 150.50.9.0/24 is directly connected, Dialer0
C 150.50.100.0/24 is directly connected, Serial0
R 150.50.77.0/24 [120/1] via 150.50.7.7, 00:00:15, Ethernet0
R 150.50.17.64/27 [120/1] via 150.50.7.7, 00:00:15, Ethernet0
R5#
R4 :
150.50.0.0/24 is subnetted, 11 subnets
I 150.50.177.0 [130/10476] via 150.50.100.5, 00:00:02, Serial0
C 150.50.42.0 is directly connected, Ethernet0
C 150.50.4.0 is directly connected, Loopback0
O 150.50.5.0 [110/65] via 150.50.100.5, 00:30:08, Serial0
O 150.50.6.0 [110/65] via 150.50.100.6, 00:30:08, Serial0
O E2 150.50.7.0 [110/20] via 150.50.100.5, 00:28:37, Serial0
I 150.50.2.0 [130/160750] via 150.50.100.5, 00:00:02, Serial0
I 150.50.9.0 [130/160250] via 150.50.100.5, 00:00:03, Serial0
O E2 150.50.17.0 [110/20] via 150.50.100.5, 00:30:09, Serial0
C 150.50.100.0 is directly connected, Serial0
O E2 150.50.77.0 [110/20] via 150.50.100.5, 00:30:09, Serial0
R4#
Let me know in case of any other issues . I will be up for another 3 hrs.
Nick
----- Original Message -----
From: Paglia, John (USPC.PCT.Hopewell) <JPaglia@NA2.US.ML.com>
To: 'Guoqi Cui' <guoqicui@yahoo.com>; Paglia, John (USPC.PCT.Hopewell)
<JPaglia@NA2.US.ML.com>; 'Nick Shah' <nshah@connect.com.au>;
<ccielab@groupstudy.com>
Sent: Thursday, September 19, 2002 5:50 AM
Subject: RE: IGRP Disaster
> Actually, I did insert a distance into IGRP to make it higher than RIP,
and
> many of the issues were resolved (thanks so much for kicking that into my
> head, Nick!!!). However, there is one lingering problem which has me
> baffled:
>
> Here's a 'closeup' of the router doing the redistributing:
>
> IGRP to r5
> BRI0
> \
> \
> >SO
> / OSPF
> /
> S1
> RIP to r1 and BB
>
> In my route-maps I'm (10) permitting rip into ospf and (20) denying any,
and
> (10) permitting igrp and (20) denying any. What's happening now is that
when
> the ISDN is up, a route for the loopback on r1 does not get to r5, and a
> route for the loopback on r5 does not get to r1. All of the other RIP and
> IGRP nets DO SHOW UP ON ALL OTHER ROUTERS in the network including r1 and
> r5.....only these 2 loopbacks do not transfer.
>
> This kind of spooks me out the most about this...I put a secondary address
> on the bri of r5 in the same subnet as the loopback on r5, and that did
> indeed transfer to the other respective router! Thus I I have to think my
> ACL's and redist procedures are OK, and also that a possible loop is not
the
> problem. After all, is there a difference of redistrbuting a .5.x/24
subnet
> whether it be on a physical interface or a logical interface? .5.5/24
redist
> as 'acl 10 perm 148.3.5.0 0.0.0.255' did not go, but without changing the
> acl and adding 'ip add 148.3.5.1 255.255.255.0 backup' to the bri int, a
> route to 5.0 showed up on r1. BTW, I also "invented" a new loopback on r5
> and tried to send that through but it met the same fate as the original
> loopb's...it made it out to ospf, but not to the opposing RIP area.
>
> During all of this, every route is making it out to OSPF under both ISDN
> up/down situations. Is there something I'm missing concerning the
> advertisement of loopbacks over ISDN w/ IGRP? Am I nuts? I'm starting to
> think it's the latter.
>
> Any help would be very appreciated!
>
> Pags
>
>
>
> > -----Original Message-----
> > From: Guoqi Cui [SMTP:guoqicui@yahoo.com]
> > Sent: Tuesday, September 17, 2002 11:25 PM
> > To: Paglia, John (USPC.PCT.Hopewell); 'Nick Shah';
> > ccielab@groupstudy.com
> > Subject: RE: IGRP Disaster
> >
> >
> > when you redistribute igrp into ospf and
> > and you filter the rip interface, you will not see
> > the rip interface in ospf. this only affect the
> > directed interfaces.
> >
> > To make it clearer, try redistribute connected, and
> > filter all the connected routes, then even you
> > redistribute igrp into ospf, the igrp interface will
> > not show.
> >
> > It seems the distance takes effect.
> >
> > Guoqi
> >
> >
> >
> >
> >
> > --- "Paglia, John (USPC.PCT.Hopewell)"
> > <JPaglia@NA2.US.ML.com> wrote:
> > > Mr. Shah, I couldn't agree more. In fact, when I
> > > first did this situation,
> > > that is EXACTLY what I did. However, following my
> > > config presentation, my
> > > Sensei said "I did not say you could redist. btwn.
> > > RIP and IGRP, so please
> > > attempt without it" (I don't think he's being
> > > 'realistic', but rather trying
> > > to prove a point).
> > >
> > > Thanks for the corroboration of my original thought
> > > process!
> > >
> > > John
> > >
> > > > -----Original Message-----
> > > > From: Nick Shah [SMTP:nshah@connect.com.au]
> > > > Sent: Tuesday, September 17, 2002 9:32 PM
> > > > To: Paglia, John (USPC.PCT.Hopewell);
> > > ccielab@groupstudy.com
> > > > Subject: Re: IGRP Disaster
> > > >
> > > > John
> > > >
> > > > > -ISDN is indeed being used as a backup..a backup
> > > intf. situation on r5.
> > > >
> > > > Yes, thats ok.
> > > >
> > > > > -I am not redistributing from RIP to IGRP...the
> > > redist is btwn. RIP and
> > > > > OSPF, and btwn. OSPF and IGRP.
> > > > > -Basically, since RIP and IGRP have the lower #
> > > of routes (and I'm not a
> > > > > strong typist), I have redists that look kinda
> > > like this:
> > > >
> > > > This looks ok, albeit prima facie, I think if
> > > IGRP is used on the backup
> > > > link, then in case of the failure of frame relay,
> > > you should still be able
> > > > to see RIP routes on R2, so you will need to
> > > redistribute between IGRP &
> > > > RIP
> > > > (dont you think ?)
> > > >
> > > > rgds
> > > > Nick
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! News - Today's headlines
> > http://news.yahoo.com
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:56 GMT-3