Mike Fratto

Network Computing Editor


Upcoming Events

Where the Cloud Touches Down: Simplifying Data Center Infrastructure Management

Thursday, July 25, 2013
10:00 AM PT/1:00 PM ET

In most data centers, DCIM rests on a shaky foundation of manual record keeping and scattered documentation. OpManager replaces data center documentation with a single repository for data, QRCodes for asset tracking, accurate 3D mapping of asset locations, and a configuration management database (CMDB). In this webcast, sponsored by ManageEngine, you will see how a real-world datacenter mapping stored in racktables gets imported into OpManager, which then provides a 3D visualization of where assets actually are. You'll also see how the QR Code generator helps you make the link between real assets and the monitoring world, and how the layered CMDB provides a single point of view for all your configuration data.

Register Now!

A Network Computing Webinar:
SDN First Steps

Thursday, August 8, 2013
11:00 AM PT / 2:00 PM ET

This webinar will help attendees understand the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging. It will also help users decide whether SDN makes sense in their environment, and outline the first steps IT can take for testing SDN technologies.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

See more from this blogger

Shortest Path Bridging Will Rock Your World

Whether you're planning to deploy FCoE in the data center or voice and video on your LAN, chances are you will have to redesign your network to be more efficient and robust than it is today. The way we design LANs today means we often over-provision because we build choke points through which all traffic has to pass even when the traffic is going to a neighbor. The distribution and core layers have to be over built just to overcome the choke points. It's wasteful and only addresses a symptom of a tree like design, such as inefficient paths. Short path bridging is going to change all that.

typicalnetwork.pngTake a look at your LAN architecture. It's a tree with a single path from one node to another. Ethernet is a dumb protocol. The switching logic goes something like this: Step 1: Determine which port has the destination MAC, Step 2: Spit the frame out that port.

Ethernet forwarding's benefit is that it's simple. The drawback is that you are limited in what you can do. If you have two 48Gb switches that can forward a full 96Gb between all ports on the switch, and host A on switch A wants to talk to host B on switch B, the frames have to pass through--you guessed it-- a 1Gbps uplink port. To get more inter-switch capacity, you need either a fatter uplink like a 10Gb port or you can aggregate multiple 1Gb ports together. Switch-to-switch isn't interesting but highlights the uplink problem.

If you have three or more Ethernet switches, you can't link them together in a mesh. Remember, Ethernet forwarding is dumb. Putting three or more switches into a mesh creates a loop, which means the switches keep tossing frames to each other like a hot potato. What you have to do is ensure that there is one path and only one path between switches. Anyone who has run cable will tell you that is easier said than done. I don't know any IT person who hasn't mistakenly created a network loop. The spanning tree protocol addresses that issue by ensuring that when there is a loop in the network, the network devices discover the loop and disable one link to remove the loop. Problem solved. A nice side effect is that we can now have redundant links between switches--intentional loops--for fail-over and spanning tree will fix it. The downside is you're paying for uplinks that aren't being used.

But we have only eliminated loops, and we haven't changed network design much. We still have to contend with choke points in a multi-tier architecture. Whether you have an access tier, distribution tier, core tier or some other number of tiers, the basic design is a tree with one path from any node to any other node. As you go up the network, you need to add capacity to handle the aggregation of all traffic.


Page:  1 | 23  | Next Page »


Related Reading


More Insights


Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.
 
Vendor Comparisons
Network Computing’s Vendor Comparisons provide extensive details on products and services, including downloadable feature matrices. Our categories include:

Next Gen Network Reports

Research and Reports

Network Computing: April 2013



TechWeb Careers