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

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

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

A <strong>network</strong> node continuously listens <strong>to</strong> <strong>the</strong> <strong>network</strong> cable segment. The cable<br />

segment shared by all of <strong>the</strong> nodes when CSMA/CD is employed is called a collision<br />

domain. When <strong>the</strong> node is ready <strong>to</strong> send data, it checks <strong>to</strong> see if <strong>the</strong>re is any activity.<br />

If <strong>the</strong> cable is clear, it sends its data. If two stations do this at <strong>the</strong> same time, a<br />

"collision" occurs. When this happens, <strong>the</strong> participating stations begin <strong>the</strong> Collision<br />

Consensus Enforcement Procedure (CCEP), under which a "jam" pattern is<br />

broadcast <strong>to</strong> all of <strong>the</strong> workstations on <strong>the</strong> <strong>network</strong>. This period lasts as long as it<br />

takes <strong>to</strong> reach <strong>the</strong> ends of <strong>the</strong> <strong>network</strong>. If <strong>the</strong> collision domain is quite large, it may<br />

take some time. After <strong>the</strong> CCEP is over, one of <strong>the</strong> affected nodes retransmits its<br />

frame. If it's successful and needs <strong>to</strong> transmit more data, <strong>the</strong> "listening" process<br />

starts over again.<br />

However, if a collection of nodes collide, <strong>the</strong>y s<strong>to</strong>p transmitting and try again after<br />

a retransmission delay. Each node computes its own delay time using <strong>the</strong> truncated<br />

binary exponential backoff algorithm. This algorithm basically takes <strong>the</strong> duration of<br />

<strong>the</strong> collision event, doubles its value, and uses it as a wait time. This time is usually<br />

longer <strong>the</strong>n <strong>the</strong> collision domain's round trip delay, which should be no more than<br />

51.2 microseconds and varies depending on <strong>the</strong> transmission pro<strong>to</strong>col medium used.<br />

For example, according <strong>to</strong> <strong>the</strong> IEEE 10-BaseT specification, <strong>the</strong> round-trip delay<br />

should be no more than 5.76 microseconds. The <strong>the</strong>ory is that if all <strong>the</strong> stations are<br />

transmitting at random intervals (with random delay periods after collisions),<br />

collisions will be minimized.<br />

The major problem with CSMA/CD is that all transmissions are half-duplex (<strong>the</strong><br />

node can ei<strong>the</strong>r send or receive at one time), and it only allows one source-<strong>to</strong>destination<br />

transmission at a time because <strong>the</strong> bandwidth is shared. That means as<br />

<strong>the</strong> domain adds more nodes or <strong>the</strong> collision domain becomes larger, <strong>the</strong> chance of<br />

a collision increases. As a result, overall performance decreases because more time<br />

is spent detecting collisions and performing collision recovery than actually<br />

transmitting data. To maximize <strong>the</strong> efficiency of a CSMA/CD collision domain, it is<br />

normal <strong>to</strong> engineer <strong>the</strong> domain <strong>to</strong> operate under a sustained load of no more <strong>the</strong>n<br />

30 percent of available capacity.<br />

Non-Contention-Based Access<br />

Token passing is <strong>the</strong> non-contention-based access method used with transmission<br />

pro<strong>to</strong>cols that utilize ring and bus <strong>to</strong>pologies. Token passing works by having <strong>the</strong><br />

connected nodes pass a "<strong>to</strong>ken" from one station <strong>to</strong> ano<strong>the</strong>r. When a station needs<br />

<strong>to</strong> send data, it takes <strong>the</strong> <strong>to</strong>ken and transmits its data. Only <strong>the</strong> station that has<br />

possession of <strong>the</strong> <strong>to</strong>ken can send data. The station that has <strong>the</strong> <strong>to</strong>ken can only<br />

transmit one packet; <strong>the</strong>n, it must release <strong>the</strong> <strong>to</strong>ken. The <strong>to</strong>ken handling process is<br />

different depending upon <strong>the</strong> transmission medium.

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

Saved successfully!

Ooh no, something went wrong!