09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

frame or <strong>to</strong>ken, and are commonly attributed <strong>to</strong> ring reconfiguration or a<br />

possibly a faulty NIC.<br />

• Type 3—Type 3 soft errors require <strong>the</strong> election of a new active moni<strong>to</strong>r and<br />

a ring-purge procedure. They are ei<strong>the</strong>r a result of <strong>the</strong> loss of <strong>the</strong> ring's<br />

active moni<strong>to</strong>r, or result in loss of <strong>the</strong> active moni<strong>to</strong>r.<br />

The level of ring recovery associated with each soft error must also be distinguished.<br />

In addition <strong>to</strong> being categorized as ei<strong>the</strong>r an ISE or a NSE Token Ring soft error,<br />

each Token Ring soft error is fur<strong>the</strong>r classified as a Type 1, Type 2, or Type 3 error.<br />

The following is a list describing <strong>the</strong> most common Token Ring soft errors (including<br />

<strong>the</strong>ir classification and recovery type):<br />

• Line error—An isolating, Type 1 error. It indicates that <strong>the</strong> frame has a CRC<br />

error.<br />

• Frame copy error—A non-isolating, Type 1 error. It indicates that a station<br />

copied a frame with its source address.<br />

• Multiple moni<strong>to</strong>rs—An isolating, Type 1 error. It indicates that <strong>the</strong> active<br />

moni<strong>to</strong>r received a ring-purge frame that it had not sent.<br />

• Receiver congestion error—A non-isolating, Type 1 error. It indicates that a<br />

station was unable <strong>to</strong> receive a frame that was addressed <strong>to</strong> its address.<br />

• Burst error—An isolating, Type 2 error. It indicates that a signaling error<br />

occurred. Burst errors are a common result of a station being added or<br />

removed <strong>to</strong> <strong>the</strong> ring. Occurrences of burst errors when no reconfigurations<br />

are occurring are often an indication of a cabling problem.<br />

• Abort delimiter transmitted error—An isolating, Type 2 error. It indicates<br />

that <strong>the</strong> ring station detected a corrupted <strong>to</strong>ken or some type of<br />

unrecoverable internal error, which requires it <strong>to</strong> abort its transmission.<br />

• Lost <strong>to</strong>ken error—An isolating, Type 2 error. It indicates that <strong>the</strong> active<br />

moni<strong>to</strong>r's "Any_Token" time expired. If <strong>the</strong> active moni<strong>to</strong>r fails <strong>to</strong> detect a<br />

<strong>to</strong>ken or frame once every 10usec, it purges <strong>the</strong> ring.<br />

• Lost frame error—A non-isolating, Type 3 error. A lost frame error indicates<br />

that a station has sent a frame and has not received it back. The error is<br />

generated if <strong>the</strong> ring station (functioning as a standby moni<strong>to</strong>r) fails <strong>to</strong><br />

receive a <strong>to</strong>ken once every 2.6 seconds. This is tracked locally by <strong>the</strong> station<br />

with <strong>the</strong> Good_Token timer. An error is also genterated if <strong>the</strong> station is not<br />

polled once every 15 seconds by <strong>the</strong> ring's active moni<strong>to</strong>r (also tracked<br />

locally with <strong>the</strong> Receive_Notfication timer).<br />

• Frequency error—A non-isolating, Type 3 error. It indicates that a station<br />

received a frame that is out of clock frequency with <strong>the</strong> rest of <strong>the</strong> ring. As<br />

mentioned in Chapter 5, one of <strong>the</strong> functions of <strong>the</strong> active moni<strong>to</strong>r is <strong>to</strong><br />

provide <strong>the</strong> ring's master clock for transmission timing. Token Ring uses a<br />

line clock rate of 8MHz (for 4Mbps Token Ring) and 32MHz (for 16Mbps<br />

Token Ring). Although <strong>the</strong> ring signal (maintained by <strong>the</strong> frame/<strong>to</strong>ken) is<br />

retimed as <strong>the</strong> <strong>to</strong>ken is passed from station <strong>to</strong> station, due <strong>to</strong> signal<br />

attenuation from <strong>the</strong> transmission medium and varying component

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

Saved successfully!

Ooh no, something went wrong!