VMware ESXi 5.5 distributed switch/VLAN issue

Hi all,

We are running into a strange issue with setting up a private VLAN for Exchange.  Running in a VMware ESXi 5.5 environment with a distributed switch, we have 3 Mailbox servers that each have a "public" virtual NIC on the LAN and a "private" virtual NIC, which is currently still on the same VLAN as the public, but with a "private" IP address.

I created another port group in the distributed switch with a separate VLAN ID (300).  I did not change the private IP addresses, but as soon as I placed the private VM NICs into the separate port group, the 3 Mailbox servers' private IPs could no longer ping each other.  And when I ran a tracert from any of those VMs to one of the other private IPs, the machines were trying to route through the public LAN interface.  That's what is stumping me.  The private IP addresses are on the same network segment, so why would Windows suddenly try to route traffic through the public interfaces?  I looked at the routing table, and the routes looked correct.  I've done this before on another ESXi cluster that doesn't have Enterprise Plus, hence no distributed switch, so I had to configure the port groups individually on each host, but it works fine there.  

Any thoughts?

Thanks!
acanalystsSystems AnalystAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gheistCommented:
Because public IPs are on same subnet too?
acanalystsSystems AnalystAuthor Commented:
Hello,

Thanks for your response!

The problem has been solved.  The public IPs are on a different subnet, so that wasn't the problem.  As it turns out, I did everything right in VMware.  However, what I neglected to remember is that our VMware blades are all in an HP C7000 Blade System enclosure, which has two VirtualConnect switch modules.  Since the VirtualConnects are "smart" switches, all of the VLANs assigned to a particular port are configured within the VirtualConnect.  I did not add the new VLAN to the VirtualConnect, because I had forgotten about it.  In addition to the message here, I had also e-mail our integrator, and they pointed me in the right direction.  So everything is working now.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
acanalystsSystems AnalystAuthor Commented:
Problem was resolved through outside help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.