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/18 22:56]
warmachine
nic-teaming [2022/01/20 14:08] (current)
warmachine
Line 20: Line 20:
 run it from an elevated powershell prompt and replace the team name with your desired one, and ethernet 1-4 with your NIC names. 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. +**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]]//+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 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
Line 157: 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/18 22:56