From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Wed May 04 2005 - 12:53:26 GMT-3
Simon,
The solution is meant to be simply "network 0.0.0.0". It works
for me in 12.2(15)T14, which is the version we wrote the new workbook
on. See the following output:
R1#sh ver | in IOS
IOS (tm) C2600 Software (C2600-J1S3-M), Version 12.2(15)T14, RELEASE
SOFTWARE (fc4)
R1#sh run | b router rip
router rip
version 2
network 0.0.0.0
no auto-summary
R1#debug ip rip
RIP protocol debugging is on
R1#
RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (204.12.1.4)
RIP: build update entries
150.1.4.0/24 via 0.0.0.0, metric 1, tag 0
155.1.146.0/24 via 0.0.0.0, metric 1, tag 0
172.16.12.0/24 via 0.0.0.0, metric 1, tag 0
172.16.12.2/32 via 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via BRI0/0 (172.16.12.1)
RIP: build update entries
30.0.0.0/16 via 0.0.0.0, metric 2, tag 0
30.1.0.0/16 via 0.0.0.0, metric 2, tag 0
30.2.0.0/16 via 0.0.0.0, metric 2, tag 0
30.3.0.0/16 via 0.0.0.0, metric 2, tag 0
31.0.0.0/16 via 0.0.0.0, metric 2, tag 0
31.1.0.0/16 via 0.0.0.0, metric 2, tag 0
31.2.0.0/16 via 0.0.0.0, metric 2, tag 0
31.3.0.0/16 via 0.0.0.0, metric 2, tag 0
150.1.4.0/24 via 0.0.0.0, metric 1, tag 0
155.1.146.0/24 via 0.0.0.0, metric 1, tag 0
204.12.1.0/24 via 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via Ethernet0/1 (155.1.146.4)
RIP: build update entries
30.0.0.0/16 via 0.0.0.0, metric 2, tag 0
30.1.0.0/16 via
R1#0.0.0.0, metric 2, tag 0
30.2.0.0/16 via 0.0.0.0, metric 2, tag 0
30.3.0.0/16 via 0.0.0.0, metric 2, tag 0
31.0.0.0/16 via 0.0.0.0, metric 2, tag 0
31.1.0.0/16 via 0.0.0.0, metric 2, tag 0
31.2.0.0/16 via 0.0.0.0, metric 2, tag 0
31.3.0.0/16 via 0.0.0.0, metric 2, tag 0
150.1.4.0/24 via 0.0.0.0, metric 1, tag 0
172.16.12.0/24 via 0.0.0.0, metric 1, tag 0
172.16.12.2/32 via 0.0.0.0, metric 1, tag 0
204.12.1.0/24 via 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via Loopback0 (150.1.4.4)
RIP: build update entries
30.0.0.0/16 via 0.0.0.0, metric 2, tag 0
30.1.0.0/16 via 0.0.0.0, metric 2, tag 0
30.2.0.0/16 via 0.0.0.0, metric 2, tag 0
30.3.0.0/16 via 0.0.0.0, metric 2, tag 0
31.0.0.0/16 via 0.0.0.0, metric 2, tag 0
31.1.0.0/16 via 0.0.0.0, metric 2, tag 0
31.2.0.0/16 via 0.0.0.0, metric 2, tag 0
31.3.0.0/16 via 0.0.0.0, metric 2, tag 0
155.1.146.0/24 via 0.0.0.0, metric 1, tag 0
172.16.12.0/24 via 0.0.0.0, metric 1, tag 0
172.16.12.2/32 via 0.0.0.0, metric 1, tag 0
204.12.1.0/24 via 0.0.0.0, metric 1, tag 0
RIP: ignored v2 packet from 150.1.4.4 (sourced from one of our
addresses)
Try upgrading to 12.2(15)T14 and see if that has an effect.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: simon hart [mailto:simon.hart@btinternet.com]
> Sent: Wednesday, May 04, 2005 10:46 AM
> To: Brian McGahan; Group Study
> Subject: RE: Advertising RIP all interfaces with one Network Statement
>
> Hi Brian,
>
> Here is the IOS
>
> IOS (tm) 3600 Software (C3620-J1S3-M), Version 12.2(15)T9, RELEASE
> SOFTWARE
> (fc2)
>
> c3620-j1s3-mz.122-15.t9.bin
>
> Thanks
>
> Simon
>
> -----Original Message-----
> From: Brian McGahan [mailto:bmcgahan@internetworkexpert.com]
> Sent: 04 May 2005 16:43
> To: simon hart; Group Study
> Subject: RE: Advertising RIP all interfaces with one Network Statement
>
>
> Simon,
>
> This looks suspiciously like an IOS bug. The "show ip
> protocols" output should only show RIP enabled on interfaces that
> updates will be sent on. What version are you running?
>
> Brian McGahan, CCIE #8593
> bmcgahan@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987 x 705
> Outside US: 775-826-4344 x 705
> 24/7 Support: http://forum.internetworkexpert.com
> Live Chat: http://www.internetworkexpert.com/chat/
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > simon hart
> > Sent: Wednesday, May 04, 2005 10:33 AM
> > To: Group Study
> > Subject: Advertising RIP all interfaces with one Network Statement
> >
> > Hi Group,
> >
> > I have become a little stuck with a question in the recently
released
> IE
> > Vol
> > II workbook. I am interested to hear what the solution maybe.
> >
> > I have a router R5, with 4 interfaces. 3 interfaces are within the
> > 176.1.0.0 major net range and 1 interface within the 192.10.0.0
major
> net
> > range.
> > The requirement is to enable all interfaces for RIP with one Network
> > statement.
> >
> > Now I thought that the solution would be to use the following
> >
> > Network 0.0.0.0
> >
> > No this is met with limited success, in that I can recieve RIP
updates
> on
> > all interfaces, however R5 does not send out RIP on any interface
> >
> > Here is the config for R5
> >
> > router rip
> > version 2
> > redistribute connected
> > network 0.0.0.0
> > no auto-summary
> > !
> >
> > Here is the output from show ip protocols
> >
> > Routing Protocol is "rip"
> > Sending updates every 30 seconds, next due in 13 seconds
> > Invalid after 180 seconds, hold down 180, flushed after 240
> > Outgoing update filter list for all interfaces is not set
> > Incoming update filter list for all interfaces is not set
> > Redistributing: connected, rip
> > Default version control: send version 2, receive version 2
> > Interface Send Recv Triggered RIP Key-chain
> > Ethernet0/0 2 2
> > Interface Send Recv Triggered RIP Key-chain
> > Ethernet0/1 2 2
> > Serial0/0 2 2
> > BRI0/0 2 2
> > Loopback0 2 2
> > Automatic network summarization is not in effect
> > Maximum path: 4
> > Routing for Networks:
> > 0.0.0.0
> > Routing Information Sources:
> > Gateway Distance Last Update
> > 192.10.1.254 120 00:00:18
> > Distance: (default is 120)
> >
> > As can be seen from above, it does look as if RIP is enabled on all
> the
> > interfaces, however no updates are being sent. Is there a solution,
> what
> > am
> > I missing here.
> >
> > Any help greatly received.
> >
> > Incidentally, the subsequent part of the question is that rip
updates
> be
> > only sent out of e0/0. Not got to that part yet, but have tried to
> use
> > passive interface default and no passive interface on the e0/0, but
> still
> > no
> > joy.
> >
> > Thanks
> >
> > Simon
> > --
> > No virus found in this outgoing message.
> > Checked by AVG Anti-Virus.
> > Version: 7.0.308 / Virus Database: 266.11.3 - Release Date:
03/05/2005
> >
> >
>
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:56 GMT-3