I have an intel-dual port NIC in one of my servers and I cannot remember how to configure it for teaming and load balancing. I have gone to intel's website and all I can see is technical documentation. All I am wondering is what are the settings for a VLAN on a switch and for the computer itself. No place on the web seems to have information on setting this up. Last time I did it was about 3 years ago, but like I said, I can't remember what I did. Does anyone know how to get this to work?
-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Intel Dual-Port NIC Teaming...
- Thread starter Moonark
- Start date
JustinLerner
Senior member
You ask two different questions:
NIC teaming for load balancing and about VLAN's.
If you have Intel 10/100/1000 NIC's with any chipset newer than the 82557, you are probably in good shape. To properly setup both NIC's for load balancing, both NIC's will be forced to 'acquire' the same IP address. I assume you are using 2000/XP and possibly NT 4.0. Before attempting to enable teamining and then load balancing without using Advanced Server, you must install the Intel PROSet II software, available on their website for your NIC if it's the appropriate type. After ensuring the software is properly installed (Check the installation by opening ProSet II and right clicking on a NIC icon. You should be presented with options to Add Team or Add VLAN.)
The first step is to enable this to work properly, you must set each NIC to adjacent, but different networks. IF each NIC is set to the same network and subnet, the load balancing and/or fault tolerance will not work properly. There will also be other IP based problems.
Set them to the following networks, for example:
192.168.1.0 mask 255.255.255.0
192.168.2.0 mask 255.255.255.0
Once they are in separate networks, then you can create a team. After you create the team, you can reassign a new IP address to the team. Etherchannel link aggregation is best if you have the appropriate Cisco or Intel switches supporting Etherchannel link aggregation, otherwise the 802.3ad is better if you have switches with 802.3ad capability. Both of these standards incorporate load balancing and fault tolerance in their particular implementations, so they are both better than single load balancing or fault tolerance implementations.
After NIC's are teamed together I don't know if you can add them to a VLAN, but I don't see why not. Just try to add the team to a VLAN.
Hope this helps.
NIC teaming for load balancing and about VLAN's.
If you have Intel 10/100/1000 NIC's with any chipset newer than the 82557, you are probably in good shape. To properly setup both NIC's for load balancing, both NIC's will be forced to 'acquire' the same IP address. I assume you are using 2000/XP and possibly NT 4.0. Before attempting to enable teamining and then load balancing without using Advanced Server, you must install the Intel PROSet II software, available on their website for your NIC if it's the appropriate type. After ensuring the software is properly installed (Check the installation by opening ProSet II and right clicking on a NIC icon. You should be presented with options to Add Team or Add VLAN.)
The first step is to enable this to work properly, you must set each NIC to adjacent, but different networks. IF each NIC is set to the same network and subnet, the load balancing and/or fault tolerance will not work properly. There will also be other IP based problems.
Set them to the following networks, for example:
192.168.1.0 mask 255.255.255.0
192.168.2.0 mask 255.255.255.0
Once they are in separate networks, then you can create a team. After you create the team, you can reassign a new IP address to the team. Etherchannel link aggregation is best if you have the appropriate Cisco or Intel switches supporting Etherchannel link aggregation, otherwise the 802.3ad is better if you have switches with 802.3ad capability. Both of these standards incorporate load balancing and fault tolerance in their particular implementations, so they are both better than single load balancing or fault tolerance implementations.
After NIC's are teamed together I don't know if you can add them to a VLAN, but I don't see why not. Just try to add the team to a VLAN.
Hope this helps.
JustinLerner
Senior member
Teaming is different from VLANS. Teaming includes any of the following:
Load balancing (works with any switch)
Fault tolerance (works with any switch)
Etherchannel Link aggregations (requires Etherchannel switch, like Cisco/Intel)
802.3ad (requires 802.3ad compliant switch)
VLAN is a spec (hardware isolated subnetting) that requires specific NIC's and switches with VLAN capability.
Load balancing (works with any switch)
Fault tolerance (works with any switch)
Etherchannel Link aggregations (requires Etherchannel switch, like Cisco/Intel)
802.3ad (requires 802.3ad compliant switch)
VLAN is a spec (hardware isolated subnetting) that requires specific NIC's and switches with VLAN capability.
JustinLerner
Senior member
Yes, teaming can be used by itself (with switch).
JustinLerner wrote:
The first step is to enable this to work properly, you must set each NIC to adjacent, but different networks. IF each NIC is set to the same network and subnet, the load balancing and/or fault tolerance will not work properly. There will also be other IP based problems.
Set them to the following networks, for example:
192.168.1.0 mask 255.255.255.0
192.168.2.0 mask 255.255.255.0
So does this still stand if I am not using VLANs?
The first step is to enable this to work properly, you must set each NIC to adjacent, but different networks. IF each NIC is set to the same network and subnet, the load balancing and/or fault tolerance will not work properly. There will also be other IP based problems.
Set them to the following networks, for example:
192.168.1.0 mask 255.255.255.0
192.168.2.0 mask 255.255.255.0
So does this still stand if I am not using VLANs?
vlans and teaming are completely unrelated topics.
You take both NIC ports, plug them into a switch and do the teaming with the intel application.
These nics also can do trunking and use separate vlans on the same nic. Don't even worry about that, it is bad practice and pretty messy.
You take both NIC ports, plug them into a switch and do the teaming with the intel application.
These nics also can do trunking and use separate vlans on the same nic. Don't even worry about that, it is bad practice and pretty messy.