I am currently running an ESX 3.5u3 on a cluster of HP DL580G5 servers. Each server has 2 on board NICs (used for the service console and VMotion) and 2 Quad NIC cards used for the Virtual Machine port groups. We use Nortel 5520 ERS switches and we are currently doing MLT NIC teaming on the 2 Quad NIC cards in each server.
I have started the process of moving these servers to ESX 4.0 (rebuilding the servers rather than doing an upgrade - got to love scripted builds). The first server that I rebuilt in the cluster to ESX 4.0 seemed to build and be configured perfectly. When I put it in the cluster and VMotioned some guests on to it, not of the guests would respond on the network. I have had my COMMS guys look at the configuration of the Nortel switches and the assure me that nothing has changed with the configuration. We have removed the MLT NIC teaming and the guests will them respond on the network.
The only thing I can find in the Communities regarding Nortel switches and MLT NIC teaming is the following link, but it only refers to ESX 3 and we had/have the working great with ESX 3:
My question is, does anyone know why ESX 4.0 does not respond to MLT NIC teaming the same way as ESX 3.5, or has any suggestions in how to get MLT NIC teaming working with ESX 4.0.
what is the nic teaming policy of the portgroup to which VM's are connected? thanks
Could you not just set the Nortel switches up to trunk the ports for the NICs and handle the NIC teaming through your ESX host settings?
That's the way I'd go . . gives me control . . rather than the networks guys
The NIC Teaming was set to route based on IP hash. To get around the problem we have gone back to using route based on originating virtual port id and turning back spanning tree back and not using 802.3ad. This is working for us, but is not our preference.