| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1904.1 | Wonder why customer felt he had to disable spanning tree? | NETCAD::BATTERSBY | | Wed Jan 18 1995 12:22 | 21 |
| I would find out the following if I were you....
1. Which of the 4 units the customer referred to as the "failing
unit" (IE: which one wasn't "working" after the customer reset
the whole system. Were there any error log entries noted when
viewing the "broken unit" console after it was working again?
2. Find out from the customer when exactly he disabled spanning
tree, before connecting Ethernets 1 & 2 or afterwards. Also
find out which of the EF's he disabled spanning tree on.
If he disabled spanning tree *before* inadvertantly connecting
Ethernets 1 & 2 together, this might explain why one of the links
didn't go into backup. You can't detect loops if spanning tree is
disabled.
Sounds like he disabled spanning tree on a bridge, then inadvertantly
connected two LANs together. Why the rest didn't continue to work
has me a little baffled.
Bob
|
| 1904.2 | | NETCAD::SLAWRENCE | | Wed Jan 18 1995 13:31 | 4 |
|
If he disabled spanning tree and then made a loop it would be amazing
if it _did_ continue to work.
|
| 1904.3 | ANother way to Kill a Hub... | MSDOA::REED | John Reed @CBO, (803) 781-9571 NIS Networker | Thu Jan 19 1995 09:39 | 16 |
| I also have had HUBs stop working when I inadvertently plug the
DECconcentrator FDDI UTP PMD modules into DECrepeater 10BaseT ports....
That causes the Entire Ethernet portion of the hub to stop working, and
all users to time out on all ports of all repeaters on a DEChub90,
until you unplug the offending FDDI UTP source. We found that the
DECrepeater90 didn't segment this faulty port, but sent the signal into
the HUB90 to propogate to the other modules.
That might have been what he plugged into a DECbridge on his site?
Keep the Spanning Tree running, and color code your jumper cables.
That is the only way that I can keep them straight.
JR
|