From: Nitro Drops (nitrodrops@hotmail.com)
Date: Sun Aug 31 2008 - 06:20:27 ART
BTW, it is Lab7.
Thanks mate, i will take note of this behaviour of RIP.
Cheers
Nit
Date: Sun, 31 Aug 2008 13:09:33 +0500From: fahad.khan@gmail.comTo:
nitrodrops@hotmail.comSubject: Re: IEWB Vol2 Task4.1 - RIP domain on R1, R3
and SW1CC: ccielab@groupstudy.com
I have not seen the topology, but as far as my perception is concerned, Yes,
163.1.0.0/16 covers all the prefixes of /24, although the interfaces that have
/24 networks are passive, but the interface that is connected to the switch
SW1 is not passive, and you have advertised 163.1.0.0, therefore leaked all of
the /24 prefixes towards SW1.Normal behaviour!
HTH
On 8/31/08, Nitro Drops <nitrodrops@hotmail.com> wrote:
When configuring RIP process on R1, R3 and SW1. "Passive-interfacedefault"
have been used on both R3 and R1. "No passive interfaces" havebeen used on R1
F0/0 and R3 E0/0.Rack1R3#sh run | begin router riprouter ripversion
2passive-interface defaultno passive-interface Ethernet0/0network 163.1.0.0no
auto-summaryRack1R1#sh run | begin router riprouter ripversion
2passive-interface defaultno passive-interface FastEthernet0/0network
163.1.0.0no auto-summaryQns : How come SW2 still can learn the routes for
163.1.13.0/24 viaboth R1 and R3? Even though this subnet 163.1.13.0/24 is
notadvertised by both R1 and R3 into RIP domain, as 'passive-interfacedefault'
command is used on both R1 and R3? Understand that this subnetfalls into the
major network 163.1.0.0/16. Does it means major networktakes precedence over
'passive-interface default' command?Rack1SW2#Rack1SW2#sh ip route rip
163.1.0.0/16 is variably subnetted, 6 subnets, 2 masksR 163.1.35.0/24
[120/1] via 163.1.38.3, 00:00:21, FastEthernet1/14R 163.1.13.3/32
[120/1] via 163.1.18.1, 00:00:08, FastEthernet1/15R 163.1.12.0/24
[120/1] via 163.1.18.1, 00:00:08, FastEthernet1/15R 163.1.13.0/24
[120/1] via 163.1.38.3, 00:00:21, FastEthernet1/14 [120/1]
via 163.1.18.1, 00:00:08, FastEthernet1/15Rack1SW2#sh ip route
163.1.13.0Routing entry for 163.1.13.0/24Known via "rip", distance 120, metric
1Redistributing via ripLast update from 163.1.18.1 on FastEthernet1/15,
00:00:00 agoRouting Descriptor Blocks:* 163.1.38.3, from 163.1.38.3, 00:00:13
ago, via FastEthernet1/14 Route metric is 1, traffic share count is 1
163.1.18.1, from 163.1.18.1, 00:00:00 ago, via FastEthernet1/15 Route
metric is 1, traffic share count is
1Rack1SW2#CheersNit__________________________________________________________
_______Meet singles near you. Try ninemsn dating
now!http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fdating%2Eninemsn%2Ecom%2E
au%2Fchannel%2Findex%2Easpx%3Ftrackingid%3D1046247&_t=773166080&_r=WL_TAGLINE
&_m=EXTBlogs and organic groups at
http://www.ccie.net__________________________________________________________
_____________Subscription information may be found
at:http://www.groupstudy.com/list/CCIELab.html-- Fahad Khan
This archive was generated by hypermail 2.1.4 : Mon Sep 01 2008 - 08:15:33 ART