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.

with a specific VLAN. A ULP-based VLAN is an example of using<br />

implicit tagging for VLAN identification. Although implicit frame<br />

tagging is easy <strong>to</strong> implement on a standalone switch <strong>to</strong> establish VLAN<br />

port membership, <strong>the</strong>re is no easy way <strong>to</strong> ensure that an implicitly<br />

tagged frame will be forwarded correctly when it needs <strong>to</strong> leave <strong>the</strong><br />

switch for delivery. To ensure proper delivery of implicitly tagged<br />

frame <strong>to</strong> <strong>the</strong> correct VLAN when it reaches a remote switch, some type<br />

of centralized configuration data must be used <strong>to</strong> determine a frame's<br />

VLAN assignment. For this reason, VLAN mechanisms utilize implicit<br />

tagging operate in conjunction with a VLAN configuration server.<br />

Switches installed on <strong>the</strong> <strong>network</strong> exchange configuration and VLAN<br />

mapping information. Although using a central server makes<br />

configuration easier, a server failure can have a severe impact on <strong>the</strong><br />

<strong>network</strong>'s operation.<br />

With explicit packet tagging, an extension <strong>to</strong> <strong>the</strong> Layer 2 frame a tag<br />

is added <strong>to</strong> a packet as it enters <strong>the</strong> switch. The tags are used by <strong>the</strong><br />

switches in <strong>the</strong> LAN <strong>to</strong> indicate VLAN membership. However, use of<br />

tagging adds <strong>to</strong> <strong>the</strong> length of <strong>the</strong> packet, so tagged packets will be<br />

seen as deformed packets by switches that do not support tagging<br />

and will be discarded.<br />

With a marketplace full of incompatible solutions, a community effort<br />

was taken up in cooperation with <strong>the</strong> IEEE <strong>to</strong> develop a standard for<br />

"Virtual Bridged Local Area Networks," or standards-based VLANs.<br />

The effort began in 1996 between <strong>the</strong> major LAN switch<br />

manufacturers. Two solutions were considered. One was <strong>the</strong><br />

exchange of VLAN information between switches, a process similar <strong>to</strong><br />

<strong>the</strong> exchanging of dynamic routing tables between routers. The o<strong>the</strong>r,<br />

based on Cisco Systems' ISL solution, was <strong>the</strong> use of packet tagging.<br />

The tagging solution was selected by <strong>the</strong> IEEE <strong>to</strong> be <strong>the</strong> basis of <strong>the</strong><br />

IEEE 802.1q standard. This method, incidentally, is also <strong>the</strong> more<br />

efficient of <strong>the</strong> two, because <strong>the</strong> exchange of VLAN information<br />

between switches would only increase <strong>the</strong> amount of traffic on <strong>the</strong><br />

<strong>network</strong>.<br />

IEEE 802.1q Standards-Based VLANs<br />

The IEEE 802.1q standard provides an architectural model for <strong>the</strong><br />

configuration, distribution, and operation of VLANs. It is a three-layer<br />

model consisting of a configuration layer, a distribution/resolution<br />

layer, and a mapping layer.

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

Saved successfully!

Ooh no, something went wrong!