You have a server named Server1 that runs Windows Server 2012 R2.
Server1 has three physical network adapters named NIC1, NIC2, and NIC3.
On Server1, you create a NIC team named Team1 by using NIC1 and NIC2.You configure
Team1 to accept network traffic on VLAN 10.
You need to ensure that Server1 can accept network traffic on VLAN 10 and VLAN 11. The
solution must ensure that the network traffic can be received on both VLANs if a network
adapter fails.
What should you do?
A.
From Server Manager, change the load balancing mode of Team1.
B.
Run the New-NetLbfoTeamcmdlet.
C.
From Server Manager, add an interface to Team1.
D.
Run the Add-NetLbfoTeamMembercmdlet.
Lord Business demands this to be tried in the ServerDude lab!
0
0
lord business is in an almighty pickle then
0
0
Lord Business can be sure it was tested and here´s a link to the trick. C is right.
http://blogs.technet.com/b/keithmayer/archive/2012/11/20/vlan-tricks-with-nic-teaming-in-windows-server-2012.aspx
0
0
doesn’t the Add-NetLbfoTeamMember cmdlet add an Interface to a Team as well? So C or D..
0
0
No, you would use Add-NetLbfoTeamNIC not Add-NetLbfoTeamMember so C is right
0
0
Yup JR is right – it seems a bit weird because you tend to think of a team member as a NIC and it is so you think it’s the add team member cmdlet, the cmdlet to add a new VLAN to a team uses the term NIC but it means an interface rather than a real network adapter – almost like a virtual NIC rather than a real one, to accept the traffic from the other VLAN which is in effect a separate network.
0
0
C is the only valid answer
Add-NetLbfoTeamNIC -Team NetTeam01 -VlanID 56
– This is the correct command to add an additional interface to an existing team
0
0
if a network adapter failed that how can Add-NetLbfoTeamNIC will work.I am new, if any body plz clarify it
0
0
Team Name: Team
Team Member: Ethernet0
I Added Ethernet1 using below commandlet and it works
Add-NetLbfoTeamMember -Team “Team” -Name “Ethernet1”
0
0