Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!asuvax!ncar!boulder!daemon
From: C.Chaundy@its.unimelb.EDU.AU
Newsgroups: comp.dcom.sys.cisco
Subject: RIP advertising secondary IP addresses
Message-ID: <25608@boulder.Colorado.EDU>
Date: 4 Sep 90 10:00:23 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 24

We are just beginning to install cisco routers to raplace a level 2 bridged
network on our campus and want to use the secondary IP address feature to
ease the transition to a fully subnetted network.  We were intending to add
a secondary address in the subnet to which we wish to migrate a group of hosts
to the ethernet interface that is connected to the current bridged backbone,
change the IP numbers of the hosts, and finally delete the secondary address
and configure a different interface with this address (and move the physical
cable).  Does this sound like the right approach?

We are also connected to the wider world by a cisco unit connected to our
backbone and most systems simply point their default route at its address.
When we added the secondary IP address to the 'local' cisco, our 'gateway'
cisco did not learn about the new subnet and I had to configure an explicit
ip route into the unit (both units are configured for RIP).  Is this to be
expected, i.e., the secondary network number is not advertised by RIP?

Regards, Chris Chaundy

Technical Manager, Networks,
Information Technology Services, The University of Melbourne
Internet: C.Chaundy@its.unimelb.EDU.AU	(DTE 505233430003)
Phone:    +61 3 344 7045  Cables Unimelb
Fax:      +61 3 347 4803  Telex AA35185
Post:     Parkville, Victoria 3052 Australia