I would think that 'could' be correct depending on the chassis configuration.
If each blade is only communicating with another blade in the chassis, then you
don't need to trunk that vlan up the chain. If you had another blade chassis
or stand alone server that you were vmotion-ing to, you'd have to trunk that
vlan up. Generally the ESX host should have its mgmt address, vmotion
address, and vm network addresses all on different networks.
Someone please correct me if that doesn't sound right
Thanks!
From: Tom Miller [mailto:tmil...@sfgtrust.com]
Sent: Saturday, March 02, 2013 12:06 PM
To: NT System Admin Issues
Subject: Another VMWare question: networking
I'm slowly becoming familiar with VMWare ESX in my new job, assuming management
from the person who preceded me. I think the networking is not configured
optimally for the hosts. This is most noticeable on our Exchange CAS servers
when they are moved to different ESX hosts each and the load balancers have
communication issues with one or more of the CAS servers. I've been through
the on-line VMWare documentation but still have a few questions for you VMWare
experts.
These hosts are IBM blades. The chassis has two Cisco 3012 switch modules.
There are logical ports for the blades, and they share four common physical
ports.
Looking at the VMotion network on each host, it's VLAN 100. Looking at the
Cisco modules, each ethernet port for the blades is defined as trunked, but not
a member of VLAN 100 defined on those modules, instead the command for each of
these ports is switchport trunk native vlan 500. I do not see a VLAN 500
configured on the Cisco modules.
This does not seem correct but I'm still learning VMWare. Can someone clarify
the network requirements for ESX hosts? Once I know and understand I can
configure the switches correctly.
Thanks,
Tom
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to
listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin
This email and any attached files are confidential and intended solely for the
intended recipient(s). If you are not the named recipient you should not read,
distribute, copy or alter this email. Any views or opinions expressed in this
email are those of the author and do not represent those of the company.
Warning: Although precautions have been taken to make sure no viruses are
present in this email, the company cannot accept responsibility for any loss or
damage that arise from the use of this email or attachments.
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin
