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.

• Beacon (BCN)—Two classifications for Token Ring erroblrs exist: soft errors<br />

and hard errors. Soft errors affect <strong>the</strong> transmission of data, but do not<br />

represent a condition that alters <strong>the</strong> configuration or disables <strong>the</strong> ring.<br />

Depending on <strong>the</strong> severity of <strong>the</strong> soft error, different ring recovery<br />

procedures are initiated so that <strong>the</strong> ring can return <strong>to</strong> a normal state as<br />

quickly as possible. A Token Ring hard error represents failure that halts <strong>the</strong><br />

ability for <strong>the</strong> ring <strong>to</strong> transmit data. When hard errors occur, <strong>the</strong> ring<br />

attempts <strong>to</strong> reconfigure itself by removing <strong>the</strong> faulty elements from <strong>the</strong> ring.<br />

This process, known as beaconing, is initiated by having <strong>the</strong> station that has<br />

detected <strong>the</strong> hard error transmit beacon frames. When a station enters a<br />

beaconing state, <strong>the</strong> beacon frames notify <strong>the</strong> o<strong>the</strong>r stations of <strong>the</strong> ring error<br />

and <strong>the</strong> status of <strong>the</strong> recovery process.<br />

• Claim Token (CTK)—When a standby moni<strong>to</strong>r has reason <strong>to</strong> believe <strong>the</strong><br />

active moni<strong>to</strong>r has failed or has been removed from <strong>the</strong> ring, it generates a<br />

Claim Token in order <strong>to</strong> initiate <strong>the</strong> <strong>to</strong>ken claiming process.<br />

• Ring Purge (PRG)—When <strong>the</strong> active moni<strong>to</strong>r needs <strong>to</strong> reset <strong>the</strong> ring due <strong>to</strong> an<br />

error, it transmits a ring purge frame. The "ring purge" resets <strong>the</strong> ring back<br />

<strong>to</strong> <strong>the</strong> ring's normal operational state.<br />

• Active Moni<strong>to</strong>r Present (AMP)—The AMP frame is transmitted by <strong>the</strong> active<br />

moni<strong>to</strong>r <strong>to</strong> all <strong>the</strong> standby moni<strong>to</strong>rs as part of <strong>the</strong> active moni<strong>to</strong>r's neighbor<br />

notification moni<strong>to</strong>ring process. If a standby moni<strong>to</strong>r fails <strong>to</strong> get an AMP once<br />

every 15 seconds, <strong>the</strong> standby moni<strong>to</strong>r generates an error and a claim <strong>to</strong>ken,<br />

initiated <strong>the</strong> <strong>to</strong>ken claiming process.<br />

• Standby Moni<strong>to</strong>r Present (SMP)—The SMP is sent as part of <strong>the</strong> neighbor<br />

notification process when <strong>the</strong> station joins <strong>the</strong> ring. It is used <strong>to</strong> notify its<br />

nearest active downstream neighbor (NADN) of its MAC address.<br />

• Duplicate Address Test (DAT)—The DAT is used by a ring station <strong>to</strong> verify<br />

that no o<strong>the</strong>r station on <strong>the</strong> ring has <strong>the</strong> same address. In addition <strong>to</strong> <strong>the</strong> ring<br />

insertion process, DAT frames are also transmitted when a ring station is<br />

involved in a hard error condition.<br />

Of <strong>the</strong> 25 IBM MAC frame types, <strong>the</strong> majority of <strong>the</strong>m are used <strong>to</strong> notify <strong>the</strong><br />

configuration report server of changes (and, in some cases, failures) in <strong>the</strong> ring's<br />

operation. Here are descriptions of <strong>the</strong> IBM MAC frames that pertain <strong>to</strong> error<br />

reporting in conjunction with IBM's LAN Manager product or equivalent product that<br />

can function as an REM and <strong>the</strong> Ring Parameter server:<br />

• Report Soft Error (RSE)—When a station detects a soft error, its first action<br />

is <strong>to</strong> collect data on <strong>the</strong> nature of <strong>the</strong> error. The error collection process is a<br />

timed event. When <strong>the</strong> soft error timer has expired, it generates a report and<br />

sends it <strong>to</strong> <strong>the</strong> REM (provided one exists).<br />

• Report Neighbor Notification Incomplete (RNNI)—The neighbor notification<br />

process is a timed event. If <strong>the</strong> notifying station fails <strong>to</strong> receive a response<br />

from its NAUN in <strong>the</strong> allotted time, an RNNI is generated and sent <strong>to</strong> <strong>the</strong><br />

REM.

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

Saved successfully!

Ooh no, something went wrong!