shankshank
asked on
NIC Teaming
I'm currently managing a infrastructure with DELL PowerEdge servers. I do alot of virtualization using virtual server 2005 and hyper V. Some of these servers have Broadcom and some have Intel NICs. I'd like to implement teaming, mainly for failover/fault tolerance.
I've been reading upon the different teaming modes but I am not completely sure which one I want to implement.
Adapter fault tolerance seems the simplest. My understanding is that 2 nics, one is active other is standby. the IP address is assigned to the active and if it fails it gets passed to the standby.
Then there is switch fault tolerance, which seems to do the same thing. But, what's the difference amongst the 2?
And the main question is, why not do adaptive load balancing to increase traffic throughput on 2 nics, but if one fails everything will still function?
I am going to use 2 Procurve 2810 switches connected to a Cisco ASA5505. Do I need to configure anything special on any of the devices?
I've been reading upon the different teaming modes but I am not completely sure which one I want to implement.
Adapter fault tolerance seems the simplest. My understanding is that 2 nics, one is active other is standby. the IP address is assigned to the active and if it fails it gets passed to the standby.
Then there is switch fault tolerance, which seems to do the same thing. But, what's the difference amongst the 2?
And the main question is, why not do adaptive load balancing to increase traffic throughput on 2 nics, but if one fails everything will still function?
I am going to use 2 Procurve 2810 switches connected to a Cisco ASA5505. Do I need to configure anything special on any of the devices?
ASKER
Yeah right now on my dual port one nic is for host only and the other nic has all tcp ip properties removed so it's dedicated to the virtual network.
in the past if i didn't do this i noticed sometimes i lose connectivity to the host.
"Add nics and configure the same as the second nic and load balance as a trunk over the virtual switch."
i'm not understanding what you mean here..
in the past if i didn't do this i noticed sometimes i lose connectivity to the host.
"Add nics and configure the same as the second nic and load balance as a trunk over the virtual switch."
i'm not understanding what you mean here..
The current configuration should not be teamed.
If network cards are added then teaming or trunking or load balancing the VM traffic could be considered.
Were you wanting team the host nic?
If network cards are added then teaming or trunking or load balancing the VM traffic could be considered.
Were you wanting team the host nic?
ASKER
I don't need trunking since all servers on the physical server are part of the same VLAN.
I do have 4 ports, dual broadcom and dual intel.
I was thinking dual broadcom set up as a team for the virtual servers.
I do have 4 ports, dual broadcom and dual intel.
I was thinking dual broadcom set up as a team for the virtual servers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The remaining nic set with just virtual networking and all other clients and service unchecked.
Add nics and configure the same as the second nic and load balance as a trunk over the virtual switch.