vSwitch Not Behaving Properly

jdff
jdff used Ask the Experts™
on
I'm recently facing a situation with a ESXi vSwitch and I'm not sure on how to start to troubleshoot this, we have a host with 4 NICS and 2 vSwitchs; vSwitch1(NIC1) and vSwitch2(NIC2-4), I have the WAN configured on vSwitch1 and vSwitch2 is just for LAN usage, however I have another blade Server connected directly on the vSwitch2 and it is working just fine, but once I plug a NAS drive on vSwitch2 it knocks off the blade server meaning that I can not ping it anymore and if I unplug the blade server then the NAS starts to work just fine, so it is one of the other, my intent is to use vSwitch2 for lan devices but as you can see I'm having a bit of problem. Any ideas?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
however I have another blade Server connected directly on the vSwitch2 and it is working just fine,

can you explain the above.

what is the current host, another blade in the enclosure ?

Author

Commented:
Its another lan device, in this case a Dell blade server running windows.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
so you have a ethernet cable connected directly between them ?
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Yes, ethernet cable to another server and ethernet cable to the NAS.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Connect all the physical network interfaces to a physical network switch, and do this properly, cross over cable or ethernet cable connected between servers and NAS, whatever next!

it's probably due to route table/arp table switching between nics

But to be honest with you I've never read any so ridiculous.

Author

Commented:
Andrew, just a couple of things to consider here;

1. When working as a self employed and relying on different clients in order to make a living you have to also be subject to dealing with different individuals as well different mentalities, back in the days when working for Siemens I had access to the IT departments budget and buying equipment or services would not be an issue but when working with Small Businesses you have to be flexible and yet not compromise the integrity/quality of the project.

2. This is for a datacenter and adding an additional switch will cost money for the part and rack rental, besides when I took over the account, there were 2 other servers using the vSwitch on this host just as a normal Lan switch.

3. I've asked if someone had any ideas or had experienced the same problem before or perhaps had a direct fix for my question, but beyond that, I would like to learn the technical side of it, if it does not work, why it does not work. Swapping parts is an easy job, understanding why the part needs to be replaced is another thing.

4. I don't think it is ridiculous at all, in fact suggesting to use a real switch is what I had in mind too but I'm sure there is someone out there who knows the technicality of how vSwitch works and are using the same technique to save resources and money.

5. Thank you once again for your time and effort.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
We would never complete any implementation like this. VMware vSphere/Servers are not designed with this mind. Anyway,,,

it's probably due to route table/arp table switching between nics.

It's not a vSwitch issue, it's ethernet, and routes/arp, the same would happen on a physical server.

and devices are not designed to be connected directly to one another.

What you could try is different IP Addresses Subnets per ethernet port.

192.168.x.x on nic1
172.168.x.x on nic2
Commented:
The problem was with the NAS drive, once replaced this feature worked as a charm. Thank you all.

Author

Commented:
Problem solved.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial