From: Atif Awan (atifawan@xxxxxxxxxxx)
Date: Mon Sep 25 2000 - 07:42:28 GMT-3
Yup the difference in IOS must have something to do with it.
Thanks for the input.
Regards
Atif Awan
>From: Kristian Bjoernskov <krbj-ccie@novo.dk>
>To: Atif Awan <atifawan@hotmail.com>
>CC: krbj-ccie@novo.dk, ccielab@groupstudy.com
>Subject: Re: RIP details
>Date: Mon, 25 Sep 2000 12:26:34 +0200 (CEST)
>
>On Mon, 25 Sep 2000, Atif Awan wrote:
>
> > but normally RIP does not advertise the directly connected network. I
>have
> > seen it advertise the directly connected network only in case of a
>neighbor
> > statement being configured ..
>
>This reply suppriced me! I have tried this severel times, and never seen
>this happenes. I just tried in my lab, and this seems to be different in
>different versions of IOS!
>
>On an old C4000 running c4000-js-mz.113-11a.bin I get:
>
>router rip
> network 10.0.0.0
> neighbor 10.1.1.10
>
>1w5d: RIP: sending v1 update to 255.255.255.255 via TokenRing0 (10.1.1.1)
>1w5d: subnet 10.1.2.0, metric 1
>1w5d: RIP: sending v1 update to 10.1.1.10 via TokenRing0 (10.1.1.1)
>1w5d: subnet 10.1.2.0, metric 1
>1w5d: subnet 10.1.1.0, metric 1
>
>but with c4500-js56i-mz.121-4.bin and the same config I get:
>
>1w5d: RIP: sending v1 update to 255.255.255.255 via TokenRing0 (10.1.1.2)
>1w5d: RIP: build update entries
>1w5d: subnet 10.1.3.0 metric 1
>1w5d: RIP: sending v1 update to 10.1.1.10 via TokenRing0 (10.1.1.2)
>1w5d: RIP: build update entries
>1w5d: subnet 10.1.3.0 metric 1
>
>Now I think the answer is, hmmmm. I will still refer to section 3 of the
>RFC, where it is quite clear you will have to send your entire route
>table!
>
>Most kind regards,
>Kristian Bjoernskov, <mailto:krbj@novo.dk>
>Novo Nordisk IT, Network - internet.
>Phone: +45 4442 3299. Fax: +45 4442 6061
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:01 GMT-3