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.

Layer 2 infrastructures <strong>to</strong> operate multiple discrete Layer 3 segments.<br />

By using VLANs, you can reduce Layer 2 collision domains and <strong>to</strong>ken<br />

contention problems, as well as control <strong>the</strong> extent of Layer 3<br />

broadcast traffic. When it exceeds <strong>the</strong> normal operating percentage of<br />

8 <strong>to</strong> 10 percent of Layer 3 segmen<strong>to</strong>perating bandwidth, this kind of<br />

traffic impacts <strong>network</strong> performance and increases <strong>the</strong> chance of<br />

Layer 3 broadcast s<strong>to</strong>rms. VLANs can also reduce unneeded router<br />

processing overhead by eliminating <strong>the</strong> need <strong>to</strong> have geographically<br />

distant end-stations (with common resource access requirements)<br />

homed on different Layer 3 segments. Instead, dynamic VLANs can be<br />

created <strong>to</strong> have end-stations and servers in different locations<br />

function as if <strong>the</strong>y were on <strong>the</strong> same local segment.<br />

NOTE<br />

Remember, when configuring 802.1q switches, each switch involved<br />

within a VLAN group must be configured using <strong>the</strong> same VID<br />

designation. In o<strong>the</strong>r words, if you want a port on switch B <strong>to</strong> belong<br />

<strong>to</strong> <strong>the</strong> same VLAN as ano<strong>the</strong>r port on switch A, you need <strong>to</strong> make <strong>the</strong><br />

VID for both of those ports identical between <strong>the</strong> two switches.<br />

NOTE<br />

Broadcast s<strong>to</strong>rms occur when <strong>the</strong> <strong>network</strong> is <strong>to</strong>o large or when<br />

defective hardware or <strong>network</strong> configurations exist. Network<br />

broadcasts are essential for any <strong>network</strong> <strong>to</strong> operate, and when <strong>the</strong><br />

<strong>network</strong> is of a reasonable size, broadcasts should not result in any<br />

significant impact on <strong>network</strong> performance. As Layer 3 <strong>network</strong>s<br />

increase in size, however, <strong>the</strong> broadcast domains (<strong>the</strong> possible<br />

number of hosts that can send or receive broadcast traffic) also<br />

increase. This results in higher <strong>network</strong> bandwidth utilization rates for<br />

broadcast traffic and less for "real" <strong>network</strong> traffic. Broadcast<br />

bandwidth utilization rates up <strong>to</strong> 25 percent are <strong>to</strong>lerable, but not<br />

optimal. When Layer 3 <strong>network</strong>s grow <strong>to</strong>o large, broadcast s<strong>to</strong>rms can<br />

be triggered by minor <strong>network</strong> events and cause excessive broadcast<br />

traffic between hosts on <strong>to</strong>p of an already high <strong>network</strong> broadcast rate.<br />

Broadcast s<strong>to</strong>rms will also occur regardless of <strong>the</strong> underlying Layer 3<br />

broadcast when an end-station NIC, switch, or bridge port fails and<br />

randomly generates broadcast traffic, or if two or more bridge ports<br />

exist between two Layer 2 <strong>network</strong> segments and spanning tree is<br />

disabled.

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

Saved successfully!

Ooh no, something went wrong!