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.

Figure 14.4 How two stations talk via a switch.<br />

Always remember that there’s a segment on each switch port (whether it’s shown or not). In other words,<br />

when you see a diagram showing a point-to-point link between a PC and a switch, or a server and a<br />

switch, it’s unlikely that someone will show the segment in between the node and the switch; instead, just<br />

one line between the switch and the node will be shown. However, the segment is there!<br />

Wait and Switch<br />

There are two kinds of switching methods:<br />

• Cut through Like it sounds, cut through switching starts transmitting the packet as it comes<br />

through, and it’s very fast. Of course, if the packet ends up being an error packet, the switch has<br />

just introduced an error on the other end.<br />

• Store and forward With store and forward switching, the switch receives the entire packet and<br />

then forwards it on to the destination segment. When errors occur here, the switch has the option<br />

of dropping the packet rather than propagating the error. Of course, because the switch waits for<br />

the entire packet to be received before forwarding it to the destination, there’s delay involved.<br />

Store and forward versus cut through involves a tradeoff of reliability versus speed; if you’re<br />

experiencing problems with your switched network, this is something to keep in mind. The price of speed<br />

can sometimes be more than you’re willing to pay.<br />

Broadcast News<br />

If you have large numbers of programs, servers, or print servers that rely on data link–level broadcasts<br />

(that is, data link traffic destined to all stations on a network), remember that each broadcast no longer<br />

goes to one segment. When switching segments together, a broadcast on one propagates to all segments.<br />

This can result in large amounts of traffic and can cause unwanted problems.<br />

You’ll want to think about when to switch and when to route. Two networks with different protocol<br />

addresses do not share data link–level broadcasts.<br />

Again, a switch is really dumb. It doesn’t know anything about the conversation on the phone—it merely<br />

knows who’s doing the talking. Can the switch be configured to divide two different segments based on<br />

protocols? Sure, but then the switch is basically acting as a router.<br />

Trees Save You

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

Saved successfully!

Ooh no, something went wrong!