Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
nic-teaming [2022/01/11 19:29] warmachine |
nic-teaming [2022/01/20 14:08] (current) warmachine |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | on the windows server side:\\ | + | ====== NIC Teaming/ |
| + | |||
| + | **on the windows server side:**\\ | ||
| < | < | ||
| Line 9: | Line 11: | ||
| once applied, you will lose internet connect and gain a new IP. if you are doing this via RDP, use angry IP scanner or similar tools to find your server, RDP back in, and assign a static IP\\ | once applied, you will lose internet connect and gain a new IP. if you are doing this via RDP, use angry IP scanner or similar tools to find your server, RDP back in, and assign a static IP\\ | ||
| - | if you have a linux server instead: | + | After you complete the switch configuration, |
| + | |||
| + | ** | ||
| + | if you ware not running a server edition of windows**, I've found this powershell script works as well: | ||
| + | |||
| + | < | ||
| + | |||
| + | 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:// | ||
| + | |||
| + | install the intel pro set drivers, and make sure to check ' | ||
| + | |||
| + | **if you have a linux server instead:** | ||
| reference: [[https:// | reference: [[https:// | ||
| Line 138: | Line 155: | ||
| </ | </ | ||
| - | 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. | + | **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 and vlan, and designate trunk. | ||
| < | < | ||
Last modified: le 2022/01/11 19:29
