Virtualization Pro

Jan 28 2008   5:21PM GMT

VLAN tagging for ESX virtual machines: Making the case

Rick Vanover Rick Vanover Profile: Rick Vanover

VLAN trunking, or tagging, is a powerful feature that allows ESX virtual machines to connect to multiple networks. However, your network team may not want to enable that. In fact, I have come across many situations where trunking is not done to servers, but only to switches for VLAN availability. To break that mold, we have to start with education on the VMware networking technologies.

Most of us are not network admins as well as virtualization admins, so we have to start with some good resources to “get what we want.” Without VLAN trunking, each VLAN you would want to connect to would require its own physical interface. That clearly is a growth and agility inhibitor as well as incredibly expensive for additional cable runs and interfaces on your ESX servers. Quoting Andrew Kutz, “that makes ESX practically worthless.” So I am on a mission to turn the tide. There is a good resource online from VMworld 2006 that explains the ESX networking so that we can inform ourselves, and better integrate with our network staff to ensure all standards are met.

With networking, configuration consistency among ESX servers becomes absolutely critical (as is with other areas of VI3). It is important to deliver the ESX configuration as planned, as if there is a variation and an outage or other networking issue, there may be a swift change of heart from your networking staff.

Readers, I invite you to share your experiences with making the case for trunking below with a comment.

2  Comments on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Akutz
    Without 802.1q deploying ESX in a large enterprise is next to impossible. Network administrators afraid of forwarding tagged frames are simply acting out of fear. The best response is to have your manager talk to their manager. Research the subject so that you know what you are talking about with regards to ESX's implementation of switches (most important point - no STP - no need - no bridging loops possible) and VLAN tagging so that you come off as knowledgeable and the network administrators come off as what they are - ignorant of the matter and scared of change.
    640 pointsBadges:
    report
  • CANewell
    I agree completly. Those that don't want to implement 802.1q VLAN tagging typically don't understand it. In a consolidated environment with VMs or blade servers, the technology provides for an incredible amount of flexibility, and eases any ESX implementation.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: