| 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 |
Why does the spanning tree not work in this example? I have two DECswitch900EFs in two separate DEChub 900s. They are connected via FDDI fiber between port 1 of each switch. There is a Thich wire Ethernet LAN with two H4005 taps. If I connect both transceiver cables to ports 2 and 6 of one of the switches, ClearVISN shows one of the ports switched off via spanning tree. If I move a cable from port 2 to port 6 of the other switch, the network goes to pot. It does not get fixed until I either use ClearVISN to shut one of the ports off or I physically disconect one of the cables. Does the spanning tree not span the FDDI link? Norm
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4342.1 | Yes, it spans the FDDI as well. | NETCAD::GALLAGHER | Thu Apr 10 1997 10:26 | 5 | |
I can't help you with the problem, but I can confirm that the spanning tree protocol *does* span the FDDI link. That is, the spanning tree is maintained on the FDDI port as well as the Ethernet ports. -Shawn | |||||
| 4342.2 | NETCAD::HOPPE | Mon Apr 14 1997 16:07 | 28 | ||
Shawn is correct. Spanning tree should be enabled on all ports by
default. Here are some recommedations for things to check:
1) Are both switches configured to use the same spanning tree
protocol? The DS900EF gives you the option of running either
802.1d spanning tree or LB100 spanning tree. Both switches
must be running the same spanning tree protocol.
2) Have you tested the FDDI link to ensure that traffic is
forwarded across it, there's a link, etc.
3) Check each port in MCM to ensure that spanning tree
is enabled on every port.
4) Check each switch to see who is the root. Does the
root information match?
If you're still having the problem, please post the firmware versions
the switches are running and any information about how the switches
have been recently upgraded or configured. Also, information on which
switch was the root in your first post would be helpful. Also,
could you list the spanning tree info from each switch (priority,
etc.)? Then, as a last resort,
you may want to try resetting the switches to factory defaults
and see if the problem still exists.
Chris
| |||||