It depends on how you configured the NIC teaming, the normal smart loadbalancing and failover does not require additional setup of a port channel on the switch. There is an option in the teaming setup that you can use LAG and in that case you do need to create a port channel on the switch.
As for stacking and link aggregation, stacking basically creates one big switch out of two switches and you can create a LAG with ports from both switches, which would provide the best redundancy for stack to stack communication.
DELL-Josh Cr
Moderator
•
9.5K Posts
0
April 22nd, 2014 09:00
Hi,
It depends on how you configured the NIC teaming, the normal smart loadbalancing and failover does not require additional setup of a port channel on the switch. There is an option in the teaming setup that you can use LAG and in that case you do need to create a port channel on the switch.
As for stacking and link aggregation, stacking basically creates one big switch out of two switches and you can create a LAG with ports from both switches, which would provide the best redundancy for stack to stack communication.
sekhar4452
7 Posts
0
April 23rd, 2014 03:00
HI,
thanx for your response,
I configured NIC teaming with Switch independence , Address harsh, NIC 2 put on stand by.
so still need to configure Lag...?????
it still provide redundancy????
becz problem i am facing that when i try to ping servers with each other , some times RTO comes some time takes time Reply.????
DELL-Josh Cr
Moderator
•
9.5K Posts
0
April 23rd, 2014 09:00
If it is in switch independent mode there is no need to configure anything on the switch. http://blogs.technet.com/b/privatecloud/archive/2012/06/19/nic-teaming-in-windows-server-2012-brings-simple-affordable-traffic-reliability-and-load-balancing-to-your-cloud-workloads.aspx