11.01.2013 Views

Workshop

Workshop

Workshop

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Down Town<br />

Previous Table of Contents Next<br />

Most Token-Rings chug away pretty well. The most problematic Token-Rings are usually the largest<br />

ones, where error recovery doesn’t work as well. (Although you can theoretically put more than 100<br />

workstations on a single Token-Ring, it’s suicidal to go above 60, and in this day of cheap switching, you<br />

might as well put one or two dozen per segment.) Nonetheless, Token-Rings are known to go down.<br />

A downed ring usually results from one of these two causes:<br />

• Beacons<br />

• Excessive errors<br />

A beacon, most often, is when a signal loss occurs on the wire. That is, a workstation has not exited the<br />

ring gracefully, and the hub thinks the station is still in use. Because the workstation doesn’t respond<br />

anymore (caused by a broken NIC), its downstream neighbor detects a signal loss and tells everyone. (It<br />

can still talk downstream, even though its upstream data has been cut off.)<br />

The active monitor initiates a ring purge (or do over). If this doesn’t work, the downstream neighbor<br />

thinks to itself, “What if it’s me?” and hurries to check this out. It removes itself from the ring, performs<br />

self-diagnostics, and reinserts itself. This cycle keeps happening until the signal loss is corrected. It’s a<br />

pretty bad scene until you come along.<br />

Fortunately, you have your trusty Token-Ring monitor program, and the defective workstation has been<br />

reported to the active monitor as the reporting station’s NAUN. You walk the NAUN list, find the bad<br />

workstation, remove it from the hub, and everything is okay. You can then figure out why the signal loss<br />

was occurring at your leisure (it’s usually a bad card or cable). Most times, this is how a beacon<br />

troubleshooting session goes.<br />

Excessive errors are troubleshot in pretty much the same way. You can look at the NAUN of the<br />

offending machine and remove it from the network. Even though I’ve seen all sorts of errors caused by<br />

bad drivers, your trouble will most often be with a single card, cable, or hub. If you don’t have a Token-<br />

Ring monitor (and again, some vendors provide this for free-it’s part of what Token-Ring offers over<br />

Ethernet) or network analyzer (or if your analyzer provides no clues), the divide-and-conquer method<br />

will usually win over any problem.<br />

Summary

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!