home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.novell
- Path: sparky!uunet!ukma!eng.ufl.edu!eng.ufl.edu!mjw
- From: mjw@eng.ufl.edu (Mike Wohlgemuth)
- Subject: IPX routing question
- Message-ID: <1992Aug19.153009.12168@eng.ufl.edu>
- Sender: news@eng.ufl.edu (Usenet Diskhog System)
- Organization: College of Engineering, University of Florida
- Distribution: na
- Date: Wed, 19 Aug 92 15:30:09 GMT
- Lines: 30
-
- We have a campus wide network with Wellfleet routers serving as
- IP and IPX routers off the campus backbone. The backbone actually
- consists of two different, redundant segments: an older broadband
- segment and a newer fiber segment. Each Wellfleet has an interface
- connected to each of the backbone segments, as well as several local
- segments, ie:
-
- +-----------+
- | Wellfleet |
- local net-+ +---fiber------+
- | | |
- local net-+ +-broadband-+ |
- | | | |
- +-----------+ IPX net | | IPX net
- 200-->| |<--80e30200
- +-----------+ | |
- | Wellfleet | | |
- local net-+ +-----------+ |
- | | |
- local net-+ +--------------+
- | |
- +-----------+
-
- IPX routing is turned on for both backbone segments in both Wellfleets.
- This has worked fine for a while, but lately we are having baffling
- routing problems. Is it legal to have a redundant IPX route? I seem
- to remember that it isn't, but I can't find any documentation.
-
- Thanks,
- Mike
-