Can't add additional LAN NIC to vswitch in ESX 4.0

Hello Experts;

I'm having an issue with one of my ESX servers boxes.

I have upgraded the NICs on one server and I want to add additional NIC to the LAN Switch for redundancy.

I added the NIC successfully, but as soon as plug the LAN cable to it, I will lose the connection connections and when I ping the server I get request timed out. I have to go and physically unplug the LAN cable out of the second NIC that I added  to make it work.  

I don't have any vlans or subnets so I can say it's conflicting


Any Idea why this is happening???

Thanks

Adam
LVL 2
atigrisAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Creating the NIC team on the ESX Server side is as simple as adding physical NICs to the vSwitch and setting the load balancing policy appropriately, and connecting them to a switch.

This will work for outbound traffic from the ESX server, but how does your unmanaged switch know where to send the inbound traffic?

normally with a managed switch you configure the two ports to create a bond or channel group.

do you want load balancing, failover, double the throughput?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You need to configure the switch if you are adding two physical NICs from the vSwitch to a physical switch.

Take a look at the knowledge base article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004048

It covers etherchannel as well as other network connectivity options for ESX/ESXi

If both of the VM hosts have two nics going to the same vlan on the same switch you need to make both active with load balance based on IP hash on each vm esx host. You need to configure a port channel on the physical switch that spans the two ports for one of the vms, then configure another port channel for the other esx(i) host. If using a single vlan switchport mode can be access, if using vlans you will need mode trunk.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The only supported algorithm for load balancing traffic across multiple NICs between VMware's NIC Teaming is using “Route based on IP hash”

In VMWare, edit the vSwitch Properties, select NIC Teaming and change Load Balancing to Route based on IP hash"

and then you need to make some physical switch configuration changes for etherchannel, or aggreate ports, or channel group, it depends on the switch.
0
Prepare for an Exciting Career in Cybersecurity

Help prevent cyber-threats and provide solutions to safeguard our global digital economy. Earn your MS in Cybersecurity. WGU’s MSCSIA degree program curriculum features two internationally recognized certifications from the EC-Council at no additional time or cost.

 
atigrisAuthor Commented:
okay, Thanks for the quick reply.

in my case, all switches are on the same subnet, we are not using vlans. What configuration I need to do beside assigning the nic to the right vswitch?.

Thanks

Adam
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
its the same, you are connecting two nics to the same physical network.

what is your switch?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
you need to make changes to your virtual switch properties and changes on your switch configuration.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
is it connectef to a managed switch?
0
 
atigrisAuthor Commented:
The switches are unmanaged. I want to add the second NIC and connected to the other switch that I have for redundancy.

What additional configuration I should make?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if they are unmanaged switches you cannot configure them.

you need to create channel groups between two ports on the switch, Cisco, HP managed switches have these features.

you could try changing the virtual switch properties, ip hash and test
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you have an unmanaged switch, you would load balance based on virtual port id.

Check this on the virtual switch.
0
 
atigrisAuthor Commented:
I was going to say you are wrong on this, but yes.  just checked the config on another client and it's set that way.

 NIcs
This is the default setup, why it does not work for me?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You are connecting two NICs, to different unmanaged switches?

Correct?
0
 
atigrisAuthor Commented:
yes, 2 Nics configured one the same vSwitch0 to 2 different unmanaged switches on the same subnet.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
and how are the two unmanaged switches connected?
0
 
atigrisAuthor Commented:
I know they are connected on the same subnet, How they are connected? I don't know. I think they simple made Ethernet chain connection.

I think it should not matter what switch you put it on as long as they are on the same subnet, you can even connect both ESX Nics to the same switch and still should work!.
0
 
atigrisAuthor Commented:
It seems like there was a problem with the unmanaged switch it self, I tried different port and it worked.

0
 
atigrisAuthor Commented:
Thanks, This ticket can be closed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.