| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
A large FDDI network of DEC concentrator 500's, DEC switch 900EF's,
and DECbrigdge 900's are seeing the DECbridges stop forwarding
IP and IPX traffic. This was happening in the April May time frame
and its has started again.
The DECswitch 900EF's are not seeing the problem. They are
running 1.4.0 on the DECbridges now and will upgrade to 1.5.0
tonite. I checked the 1.5.0 release notes and did not see any
documentation addressing this issue.
The FE will fax me the some error logs from the decbridges.
he did:
Error Data sr=2700 pc=0302A782 Error Code=00002008 ProcCsr=4F69
next
Error Data sr=2700 pc=00757A8 Error Code=0002010 ProcCrs=4769
They are also seeing their DECrepeater 900TM's reset with V1.1.0
I suggested a fix for this is on its way.
any ideas ?
Larry Morse
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2515.1 | Is the Router OK? | ANGLIN::BERNDT | Thu Jul 13 1995 22:42 | 9 | |
I don't know too much about the IP problem in the Switch...but be aware
that the network topology at Caterpillar is such that multiple subnets
are entering and exiting via one port on a Proteon Router (with
multiple secondary addresses). Generally users are on a separate (IP)
subnet in each building with the servers in yet another building. Is it
possible that there is a problem with the router/config? It is
potentially both a bottleneck and potentially a single point of
failure....Ron
| |||||
| 2515.2 | Be aware of NTAS environment | KAOFS::R_RYAN | I used to be a coyote but Im ok nowoooo! | Thu Aug 03 1995 13:20 | 16 |
The error code of 2008 should be resolved by version 1.5 of the DEFBA
firmware. This problem was fixed in version 1.4.4. As to the forwarding
of IP and IPX stopping....there are a number of issues with the
DECbridge and corruption of some internal data structures such as ARP
tables. There are as well, issues with some of the FDDI adapters such as
the PCI based FDDI adapter which will cause the problems you are seeing.
This is very evident in the NT environment. In fact it's the only
environment I've seen it in; NTAS based servers on the FDDI and
ethernet based clients. V1.57 of the DEFPA driver resolves this
problem.
For best results I would look into getting the customer defba155 and if
you have NT servers that use PCI bus FDDI cards provide them with
NTKIT157. This resolves, as far as I know all of these issues.
Regards,
Ron
| |||||