| Same general answer as for Ethernet (see Ethernet conference).
In FDDI the situation is, if anything, better yet. If your station were
to fail in such a way that it "babbles" continuously and allows nothing
at all from others to get through, that will trigger a recovery mechanism
("Trace" -- see the FDDI primer for an outline) that removes your station
from the network. The kinds of failures that do this will also prevent
the station from reconnecting, so the station will stay off until fixed.
Failures that simply send lots of traffic (which is the worst that any
software failure can do) don't matter a whole lot; other stations will
still be able to send data. Among other things, that will allow network
management to talk to the concentrator to turn off your port!
paul
|
| Paul,
Thanks for the info, much more positive than with an Ethernet card.
I understand your point(s) about heavy loads from one controller not
stopping the network. In the case I am working with the network would
not sustain too much of this type of thing and still allow response
times to be met - but that's another story.
Thanks again,
Gary.
|
| Re response time: keep in mind that there's a strict bound on how long it
takes to transmit. Given N stations each offering an "infinite" load,
the worst case delay for your first message to get out is N * TTRT.
That's with async service, and ignoring errors such as loss of token.
For more detail on this, look at the paper on this topic by Raj Jain.
paul
|