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.

need. This method not only allocates <strong>the</strong> Layer 2 bandwidth in a more<br />

efficient manner, but also enhances <strong>network</strong> security by allowing<br />

hosts <strong>to</strong> see only <strong>the</strong> Layer 3 traffic <strong>the</strong>y need <strong>to</strong> see.<br />

VLAN Usefulness<br />

Although proprietary (and now standards-based) VLAN capability has<br />

been part of many switch manufacturers'feature sets for years, <strong>the</strong><br />

implementation of VLANs has not become as prevalent as <strong>the</strong><br />

implementing of "plain vanilla" Layer 2 switching. There are three<br />

main reasons for this.<br />

The first reason is <strong>the</strong> complexity of using distributed VLANs.<br />

Deploying VLANs properly requires planning and, in many cases,<br />

major <strong>network</strong> redesign. When switching hit <strong>the</strong> marketplace, many<br />

manufacturers pushed Layer 2 switches as <strong>the</strong> panacea for large,<br />

congested, Layer 3 segmented <strong>network</strong>s. "Get rid of your routers,<br />

flatten your <strong>network</strong>," was <strong>the</strong>ir sales pitch. What most cus<strong>to</strong>mers<br />

missed was that in order <strong>to</strong> correctly implement this idea, <strong>the</strong>y<br />

needed <strong>to</strong> replace <strong>the</strong>ir shared <strong>network</strong>s with switched <strong>network</strong>s. Well,<br />

an entire switched <strong>network</strong> is quite expensive, but <strong>the</strong> idea sounded<br />

good. So, <strong>the</strong>y bought some switches, attached multiport repeaters<br />

and MAUs <strong>to</strong> <strong>the</strong>m, and <strong>the</strong>n flattened <strong>the</strong>ir <strong>network</strong>s. For many, this<br />

resulted in <strong>network</strong>s with excessively large broadcast domains, with<br />

40 percent of <strong>the</strong> <strong>network</strong> traffic being utilized for <strong>network</strong> broadcasts.<br />

So, when <strong>the</strong> same vendors came around a few years later and<br />

started talking about reducing broadcast domains and using multiport<br />

routers <strong>to</strong> manage multiple "virtual" Layer 3 <strong>network</strong>s, <strong>the</strong>y got <strong>the</strong>ir<br />

hats handed <strong>to</strong> <strong>the</strong>m.<br />

The second reason VLANs are not as prevalent is that standards<br />

migration only affected those who really kept up on <strong>the</strong> evolving<br />

technology. Until <strong>the</strong> IEEE 802.1q standard was released, <strong>network</strong><br />

administra<strong>to</strong>rs were forced <strong>to</strong> use only a single vendor's switching<br />

implementation, for compatibility reasons. Large-scale enterprise<br />

<strong>network</strong> administra<strong>to</strong>rs tend <strong>to</strong> keep away from non-standards-based<br />

solutions unless <strong>the</strong>y have no o<strong>the</strong>r choice. Therefore, with no<br />

standards, no cross-vendor compatibility, and no real enhancement<br />

<strong>to</strong> <strong>the</strong> <strong>network</strong> that could not be achieved by o<strong>the</strong>r means, VLANs did<br />

not catch on with <strong>the</strong> individuals who could have really used <strong>the</strong>m.<br />

Now, with standards-based VLANs available, utilization is starting <strong>to</strong><br />

become more common, particularly in high bandwidth/speed data<br />

farms in WWW and database application services.

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

Saved successfully!

Ooh no, something went wrong!