home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.sys.cisco
- Path: sparky!uunet!boulder!recnews
- From: Tony Li <tli@cisco.com>
- Subject: Multiple subnet problem
- In-Reply-To: Ivan Pepelnjak's message of 12-Aug-92 20:58:15 <9208130105.AA3d66@GARFY.nil.yu>
- Message-ID: <9208122010.AA15290@cider.cisco.com>
- Sender: news@colorado.edu
- Date: 12 Aug 92 13:10:02 -0700
- Lines: 33
-
-
- According to my experience, secondary addresses on cisco routers work
- only if the other nodes are not aware of the subnetting (so that they
- still think it is one big network), but even in this case, proxy-arp
- would be more appropriate.
-
- However, if You are using (for the sake of example) two class-C networks
- on the same Ethernet (or a class-B and class-C network), they are not
- announced to each other.
-
- +---------+
- | Cisco | primary : 192.1.1.20
- +---------+ secondary : 192.1.2.20
- !
- ===============================================
- ! !
- +---------+ +---------+
- | Node A | 192.1.1.10 | Node B | 192.1.2.15
- +---------+ +---------+
-
- In this example, Cisco would not announce network 192.1.1.0 to node B
- unless split-horizon is disabled (and that only works in 9.0-only
- environment).
-
- "no ip split-horizon" was introduced in 8.3(3). If you do not depend
- on your hosts snooping on RIP, then you wont need this.
-
- I hope there is a better way around this problem, as I am afraid I
- will encounter it in a near future. Any other solutions out there ?
-
- A better solution is to run GDP on your nodes.
-
- Tony
-