New-NetLbfoTeam

Creates a new NIC team.

Syntax

New-NetLbfoTeam
   [-Name] <String>
   [-TeamMembers] <WildcardPattern[]>
   [[-TeamNicName] <String>]
   [[-TeamingMode] <TeamingModes>]
   [[-LoadBalancingAlgorithm] <LBAlgos>]
   [-AsJob]
   [-CimSession <CimSession[]>]
   [-ThrottleLimit <Int32>]

Description

The New-NetLbfoTeam cmdlet creates a new NIC team that consists of one or more network adapters. Teaming network adapters of different speeds is not supported. You can create a team with network adapters of different speeds, but the network traffic distribution algorithms do not take the speed of each network adapter into consideration when distributing traffic.

When you create a team, you can specify additional properties such as TeamingMode and LoadBalancingAlgorithm.

You need administrator privileges to use New-NetLbfoTeam.

Examples

Example 1: Create a new team

PS C:\>New-NetLbfoTeam -Name Team1 -TeamMembers NIC1,NIC2

This command creates a new team named Team1 with two team members named NIC1 and NIC2.

Example 2: Create a new team with specified properties

PS C:\>New-NetLbfoTeam -Name Team1 -TeamMembers NIC1,NIC2 -TeamingMode LACP 
-LoadBalancingAlgorithm HyperVPorts

This command creates a new team named Team1 that consists of two team members named NIC1 and NIC2. The teaming mode is set to LACP and the load balancing algorithm is set to HyperVPorts.

Example 3: Create a new team in a virtual machine

PS C:\>Set-VMNetworkAdapter -VMName <VMname> -AllowTeaming  




PS C:\>New-NetLbfoTeam -Name Team2 -TeamMembers NIC1,NIC2

This set of commands allows teaming in virtual machines by using the AllowTeaming parameter of the Set-VMNetworkAdapter cmdlet and then creates a team named Team2 in the virtual machine specified by VMName. You must run the following command in the host (parent partition) with administrator permissions.

Required Parameters

-Name

Specifies the name of the new NIC team.

Type:String
Position:1
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
-TeamMembers

Specifies the names of the network adapters that are members of the new team. Specify multiple network adapter names (or wildcard patterns) separated by a comma.

Type:WildcardPattern[]
Position:2
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Optional Parameters

-AsJob

ps_cimcommon_asjob

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
-CimSession

Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSessionhttp://go.microsoft.com/fwlink/p/?LinkId=227967 or Get-CimSessionhttp://go.microsoft.com/fwlink/p/?LinkId=227966 cmdlet. The default is the current session on the local computer.

Type:CimSession[]
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
-LoadBalancingAlgorithm

Specifies the load-balancing algorithm the new team uses to distribute network traffic between the interfaces.

You can specify one of the following four load balancing algorithms:

TransportPorts: Uses the source and destination TCP ports and the IP addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces.

IPAddresses: Uses the source and destination IP addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces.

MacAddresses: Uses the source and destination MAC addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces.

HyperVPort: Distributes network traffic based on the source virtual machine Hyper-V switch port identifier.

Type:LBAlgos
Aliases:lba
Position:6
Default value:TransportPorts
Accept pipeline input:False
Accept wildcard characters:False
-TeamNicName

Specifies the name of the new team interface. This is the name used to reference the teamed network adapters.

Type:String
Position:4
Default value:Same as team name
Accept pipeline input:False
Accept wildcard characters:False
-TeamingMode

Specifies the mode of the NIC teaming. You can specify one of the following three teaming modes:

LACP: Uses the IEEE 802.1ax Link Aggregation Control Protocol (LACP) to dynamically identify links that are connected between the host and a given switch. (This protocol was formerly known as IEEE 802.3ad draft)

Static: Requires configuration on both the switch and the host to identify which links form the team.

SwitchIndependent: Specifies that a network switch configuration is not needed for the NIC team. Because the network switch is not configured to know about the interface teaming, the team interfaces can be connected to different switches.

Type:TeamingModes
Aliases:tm
Position:5
Default value:SwitchIndependent
Accept pipeline input:False
Accept wildcard characters:False
-ThrottleLimit

Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.

Type:Int32
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Inputs

None

This cmdlet takes no input objects.

Outputs

MSFT_NetLbfoTeam

This cmdlet produces an MSFT_NetLbfoTeam object, corresponding to the newly created team.