This topic contains 3 replies, has 3 voices, and was last updated by
January 22, 2015 at 9:32 pm #22075ParticipantTopics: 7Replies: 7Points: 0Rank: Member
I need to clarify difference between following two cmdlets difference between switch teaming and NIC teaming & scenarios we can use this
January 23, 2015 at 4:20 am #22077KeymasterTopics: 2Replies: 234Points: 188Rank: Participant
Hey there Kasun,
Get-Help or TechNet would be a good place to start. It'll give you a synopsis of what the cmdlet does, and even some examples in which you would use the cmdlet.
Hope this helps!
January 23, 2015 at 5:23 am #22080ParticipantTopics: 9Replies: 387Points: 500Rank: Contributor
Kasun, can you tell us what are you trying to do? or is this just academic interest?
New-NetLbfoTeam creates a NIC team. This is something you can do separate and apart from the Hyper-V role. So, a physical or virtual computer can have a NIC team (or more) that provide features like bandwidth aggregation, network load balancing, and network fault tolerance. This is much more commonly used than New-NetSwitchTeam
New-NetSwitchTeam creates a switch team. This is something you can create on a physical computer (only) that has the Hyper-V role installed. It is controlled by a Hyper-V extensible switch forwarding extension. This is rarely used.
So, if you're trying to do NIC teaming you should use New-NetLbfoTeam
January 26, 2015 at 12:36 am #22127
The topic ‘NIC Teaming & Switch Team’ is closed to new replies.