Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
nic-teaming [2022/01/12 22:24]
warmachine 		nic-teaming [2022/01/20 14:08] (current)
warmachine
Line 12: Line 12:
  
 After you complete the switch configuration, if the ports on the switch go amber, you lose connection to the server, and you see suspended ports in the logs or interface status of the switch, it is likely that windows has set the LACP bond back to "switch dependent".  Windows be dumb yo. Change it back to LACP under the server config, local, nic teaming, team1 properties.  After you complete the switch configuration, if the ports on the switch go amber, you lose connection to the server, and you see suspended ports in the logs or interface status of the switch, it is likely that windows has set the LACP bond back to "switch dependent".  Windows be dumb yo. Change it back to LACP under the server config, local, nic teaming, team1 properties. 
 +
 +**
 +if you ware not running a server edition of windows**, I've found this powershell script works as well:
 +
 +<code> New-NetSwitchTeam -Name "SwitchTeam01" -TeamMembers "Ethernet","Ethernet 2", "Ethernet 3", "Ethernet 4" </code>
 +
 +run it from an elevated powershell prompt and replace the team name with your desired one, and ethernet 1-4 with your NIC names.
 +
 +**If you have at least one intel NIC** , there is yet, another way LACP/nic teaming can be done. 
 +
 +ref: [[https://www.intel.com/content/www/us/en/support/articles/000005667/ethernet-products.html]]\\
 +
 +install the intel pro set drivers, and make sure to check 'advanced network services'. once installed, open the intel pro set advanced configuration utility, and nic teaming should be available via GUI
  
 **if you have a linux server instead:** **if you have a linux server instead:**
Line 144: Line 157:
 **on the switch side:** **on the switch side:**
  
-cisco configurations for port channel. change your channel number, interface range, vlan, and description to suit your deployment. if you are instead using a trunk port, remove the spanning tree line.+cisco configurations for port channel. change your channel number, interface range, vlan, and description to suit your deployment. if you are instead using a trunk port, remove the spanning tree line and vlan, and designate trunk.
  
 <code> <code>
Last modified: le 2022/01/12 22:24

Page Tools