A data center networking standard that's not so TRILLing

A data center networking standard that's not so TRILLing

Rivka Gewirtz Little, Senior Site Editor

This was the year we were supposed to bid farewell to the spanning tree protocol and say hello to the flat data center network. To do that, some said we should use the Transparent Interconnection of Lots of Links (TRILL) protocol, a data center networking protocol that allows Layer 3 routing among Layer 2 devices. This would replace spanning tree and free up more Layer 2 paths, creating a friendlier environment for massive VM migration.

But Juniper Networks engineer and Fast Packet blogger, Anjan Venkatramani takes issue with this theory. In his blog “Why TRILL

    Requires Free Membership to View

    By submitting your registration information to SearchNetworking.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchNetworking.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

won't work for data center network architecture,” Venkatramani says TRILL “ignores important trends, including the need for varying types of VLANs for segmentation in cloud networks.”

In fact, Venkatramani goes so far as to say that TRILL offers no answer for Layer 3 multi-pathing and actually fails at the multi-tenancy necessary for cloud networking.

Read Venkatramani's Fast Packet blog on TRILL’s lacklustre capabilities.

Next up, everybody loves a network fabric, right? Maybe not.


This was first published in December 2011

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.