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.

grouped in<strong>to</strong> VLAN groups consisting of two or more ports. All <strong>the</strong><br />

end-stations, multiport repeaters, and router interfaces connected <strong>to</strong><br />

<strong>the</strong> port group are members of <strong>the</strong> same broadcast domain. Figure<br />

6.12 is an example of a switch configured with two port-based VLAN<br />

devices: ports 1 through 6 are VLAN 1, and 7 through 12 are VLAN 2.<br />

End-stations connected <strong>to</strong> <strong>the</strong>se ports only see Layer 3 broadcast<br />

traffic that is specific <strong>to</strong> <strong>the</strong>ir VLAN port group. In order for <strong>the</strong> two<br />

VLANs <strong>to</strong> exchange traffic, a router is needed.<br />

Figure 6.12. A switched backbone <strong>to</strong>pology utilizing<br />

VLANs for Layer 3 segmentation.<br />

The downside <strong>to</strong> port-based VLANs is mostly housekeeping chores.<br />

Port configurations must be manually tracked and labeled. There is<br />

also <strong>the</strong> added hassle of having <strong>to</strong> change <strong>the</strong> port allocations when<br />

<strong>network</strong>s expand and contract, or as end-stations are moved between<br />

VLANs. Special care must also be used when establishing links<br />

between switches. With most implementations, VLANs (by default) do<br />

not span across multiple switches au<strong>to</strong>matically; <strong>the</strong>y need <strong>to</strong> be<br />

configured on each switch accordingly.

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

Saved successfully!

Ooh no, something went wrong!