Incredibly Bad Network Designs That Still Work

Share on TwitterSubmit to StumbleUponDigg This

Kudos to IT giants such as Cisco, Juniper and Microsoft. Despite some horrible network designs out in the field their equipment continues to work. In many cases, so well that the designer isn't aware of the abomination that is the network architecture. Here are our top 4 picks for network designs that can make your eyes water.

1. Dodgy Net – This design consists of many IP subnets all residing on one single VLAN. For the uninitiated the general rule is 1 IP subnet per VLAN. This helps to segment layer 2 and layer 3 traffic consistently across the network.

Technically, but, it is possible to run all IP subnets on a single VLAN. Of course, you get the worst of both worlds with this approach. IP broadcasts are encapsulated by layer 2 frames that have no boundaries and are in turn seen by every IP device on the network. Those devices outside the IP subnet of the originating host promptly discard the packet but by that stage both performance and security have been compromised.

Correcting dodgy net designs does require a lot of plotting and management because every access port vlan and trunk port has to be identified, marked and configured.

Configuring Dodgy Net is akin to slipping on a warm sweater in winter then jumping into a cold pool. It just doesn't make sense.

2. Static City – Most network engineers first learn about routing using static routes. Learning to propagate routes via routing protocols comes later but for some lost souls the penny never drops and their network designs inevitably become static cities.

Consider that modern networks can host thousands of subnets and hundred/thousands of routing devices. Imagine now having to write down each subnet from the perspective of each device and manually tell it which direction to send the packet. That is a lot of work and it becomes an administrative nightmare in large networks where changes occur on a daily basis.

google_ad_channel = "7940249670, " + AB_cat_channel + AB_unit_channel; google_language = "en"; google_ad_region = 'test';
Andres Villalva - About the Author:

IT-Pathways is a fantastic source of technical and career information for entry level and experienced IT professionals alike.  Find a sample network architect job description here.

Share on TwitterSubmit to StumbleUponDigg This
In: network, NewsAuthor: Editor