Newsgroups: bit.listserv.novell
Date:         Wed, 6 Jan 1993 14:55:00 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Don Kazem <DKAZEM@NAS.BITNET>
Subject:      Re: Routing Bug - cisco or Novell or 3com ?

This is in reference to the problem that Richard Letts reported.
While I still do not have any solid answers, I have the following
observations.

1.  In your router configurations for Lans B and C,  you have used the Arpa
numbers instead of the Novell numbers.  If the servers know the networks as
100007 and 100008, then the Cisco claiming 100FF8 and 100FF7 could be
a problem.

2. A bug that I have seen in Cisco, and it was also confirmed in the 9.1
release
notes is that if you configure a port with an existing  Novell network number,
and
shutdown the adapter (or not  connect it  to the network) , the router will
cause
router errors  on IPX routers. The reason is that when the updates sent by IPX
routers get to the internal backbone of the Cisco, they cause a conflict.
Although the adapter is  shutdown  or not connected, the Cisco box  considers
that port assigned to that  network number, but it does not see the same
updates coming in from that port.

So the question becomes: do you have a another port  in the Cisco that
is configured with an existing  novell network number and shutdown or not
connected. If so, activating it will  eradicate the errors.  Alternatively, use
the No Novell Network command for that port.

Hope this helps.

dkazem@nas.edu

--------------




We have the following setup on part of our network :

CWB-A    CWB-B   WHITWORTH-1
LANA                   | | |       |       |
|----------------------------------(-(-+-------+-------+---
|  Arpa:100000                     | |
|                                  | |     Faith
|           LANB                   | |       |[Arpa Framing]
cisco ------------------------------(-+-------+------------
| Arpa:  100FF8   novell:100008    |
|                                  |      NEWTON-1
|           LANC                   |         |[novell framing]
|----------------------------------+---------+--------
Arpa:100FF7                  novell:100007

!
novell routing 0000.0c01.282a
!
! LANA
interface Ethernet 0
ip address 146.87.0.129 255.255.255.128
novell network 100000
novell encapsulation ARPA
novell helper-address -1.ffff.ffff.ffff
bridge-group 1
!
! LANB
interface Ethernet 2
ip address 146.87.1.1 255.255.255.128
novell network 100FF8
novell encapsulation ARPA
novell helper-address -1.ffff.ffff.ffff
bridge-group 1
!
! LANC
interface Ethernet 3
ip address 146.87.1.129 255.255.255.128
novell network 100FF7
novell encapsulation ARPA
novell helper-address -1.ffff.ffff.ffff
bridge-group 1
!

What I've found so far:

Turning off bridging on ethernet0 [LANA] of the cisco does not stop the problem.
I cannot turn bridging off on the other interfaces because this prevents the
ISO CONS from staff offices being bridged.

If it is a problem in the 3c527 driver - Why doesn't it affect the CWB-B
server. Upgrading from v3.11 to v3.12 of the driver hasn't changed the
problem.

If it is a problem in the cisco software - Why doesn't it affect any of the
other servers ?

Any Ideas on what I should try now ?

Richard
--
Richard Letts
Network Manager
University of Salford               Email: R.J.Letts@salford.ac.uk
United Kingdom                      Phone : +44 61 745 5252
United States of Europe
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU