[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | FDDI - The Next Generation |
|
| Moderator: | NETCAD::STEFANI |
|
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
2024.0. "Wierd 900TX problem" by MARVIN::RIGBY (No such thing as an alpha beta) Thu Apr 25 1996 11:03
Observed a wierd problem while I was on a customer site visit (for a completely
different purpose) last week.
The customer has a large FDDI network with several rings bridged and switched
together and has a number of DEChub900s connected via DECbridge900EFs (running
the bridge software, not the routing software).
While I was there we spotted that THREE ring nodes thought that they were the
Designated bridge (802.1d spanning tree) for this ring, one (a DECNIS) was
supposed to be (priority 65), the other two were not (priority 128). The DECnis
was reported the correct root bridge in its hellos, the other devices did not,
they reported themselves as root.
Strangely, there was no impact on the forwarding anywhere. The DECNIS just
ignored the hellos, expecting them to go away. We eventually tracked the other
MAC addresses down to PEswitch900TX devices which were forwarding everything OK.
Both devices on either side of them in the ring saw the DECnis hellos OK (the 2
900Txs not adjacent but in two completely different places). Fortunately there
were no physical loops as spanning tree wouldn't have found them.
Any guesses as to how this could happen?
We tried power cycling the 900TXs with no effect but replacing them with spares
sorted everything out!
Who do I report this to in engineering?
John Rigby - DECNIS
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|