Intel(R) Advanced Network Services (ANS) for Linux* Operating Systems
=====================================================================
October 10, 2002
Contents
========
- Overview
- Installing and Configuring ANS
- Available Commands
- Structure of the ANS Build Tree
- Example Setup
- Troubleshooting
- Support
Overview
========
This file describes the Intel(R) Advanced Network Services (ANS) package,
version 2.0.x, for Linux* systems. Intel ANS provides both teaming
(including Multi-Vendor Teaming), and IEEE VLAN capabilities. For ANS
support, this package version must be used with the Linux base driver
version 2.1.x for PRO/100 adapters and/or driver version 4.4.x for PRO/1000
adapters.
This package is intended for 2.4.x kernels; it was tested primarily on the
Red Hat* 7.3 Linux 2.4.18 kernel on SMP Intel processor-based systems. This
package includes support for Itanium(TM)-based systems.
Installation assumes all necessary build tools, kernel sources, and headers
are in place and properly configured and that you are using the latest Intel
base drivers found at http://support.intel.com. Base drivers provided in
some distributions do not contain the necessary hooks for ANS.
Intel ANS may now be configured with a new command-line utility called
PROCfg. This reporting and configuration tool reduces the command-line input
required with the manual configuration method described in this document. At
this time, PROCfg is only available for 32-bit architectures. For more
information on using the PROCfg utility refer to procfg.htm. PROCfg is
available on the Intel Customer Support website, http://support.intel.com.
Teaming
-------
This package supports the following teaming modes:
- Adapter Fault Tolerance ("AFT"). Default mode when a team is created and
the mode is not specified. A secondary adapter in the team automatically
takes over on any failure of the primary connection (cable, adapter or
port). Only one network adapter is active at a time. After a failover, if
the connection to the primary adapter is restored, control passes
automatically back to that primary adapter. May mix speed and duplex
capabilities and settings. May use a hub or switch.
- Adaptive Load Balancing ("ALB"). A team of 2-8 adapters. The primary
adapter receives and transmits, and the transmission load is shared among
all adapters in the team. Supports mixed speed/duplex settings among team
members. Includes fault tolerance.
- Intel Link Aggregation, Cisco*'s Fast EtherChannel* Technology or static
802.3ad ("FEC" or "FEC/LA/802.3ad: static"). A team of 2-8 10/100
adapters which simultaneously receive and transmit data. Includes fault
tolerance and load balancing. Requires a switch that supports Intel Link
Aggregation, Cisco*'s FEC or static 802.3ad. Must match speed/duplex
settings on all team members. Spanning Tree Protocol must be turned off.
Must match switch aggregation requirements.
- Gigabit equivalent of FEC ("GEC" or "GEC/LA/802.3ad: static"). Requires
PRO/1000 or equivalent adapters and a switch that supports Intel Link
Aggregation, Cisco*'s GEC or static 802.3ad. Other requirements are
similar to FEC.
- IEEE 802.3ad: dynamic ("802.3ad"). This mode is the IEEE standard for the
technology incorporated into Cisco's FEC method. ANS support for dynamic
802.3ad teaming is similar to that for FEC and GEC teaming. In addition
to the benefits of Link Aggregation, IEEE 802.3ad Dynamic Link
Aggregation generally offers the following advantages: Automatic
Configuration, Rapid Configuration and Reconfiguration, and Deterministic
Behavior. It consists of a team of 2-8 adapters that simultaneously
receive and transmit data. Aggregation groups include only members with
the same speed and full duplex. Includes fault tolerance and load
balancing. Requires a switch that supports the IEEE 802.3ad dynamic
standard, or at least Intel Link Aggregation or Cisco's FEC. In case one
of the latter is used, the team will perform in 802.3ad static mode.
Spanning Tree Protocol must be turned off. Must match switch aggregation
requirements.
- NONE. A team of one Intel adapter that adds VLAN support on top of one
existing interface. Does not require an Intel server adapter. VLAN-
enabled must be set.
NOTES: You must have at least one Intel PRO/100 or PRO/1000 server adapter
to form a team.
For AFT and ALB, you may specify which adapters in a team you want
to use as the primary and secondary adapters. The primary one is the
main adapter used in a team. For AFT, the primary one is the only
adapter used until a failure occurs. For ALB, the primary one is the
adapter that both transmits and receives. In a team of more than two
adapters, the secondary adapter fill's the primary's role if the
primary adapter fails. Also, fail back will not occur unless the
primary has been specified. If Priority is not specified, the
adapter with the highest supported speed is chosen. If all adapters
support the same speed, the last one added is the primary adapter.
Multi-Vendor Teaming
--------------------
Multi-Vendor Teaming (MVT) adds the capability to include adapters from
selected vendors in a team (AFT, ALB, FEC, GEC, 802.3ad). MVT cannot be
used with VLANs.
In order to activate MVT, you must have at least one Intel server adapter
in the team that is designated as the primary adapter. Adapters from other
vendors must be properly loaded. Use the same command line parameters for
building the team as with all Intel adapters. All members in an MVT operate
on a common feature set.
NOTE: Use the manual installation method when installing and configuring
MVT adapters. Use any network configuration tool to select the base
driver for each adapter you wish to include in an ANS team. Make sure
each driver is included as a loadable module and can be found in the
appropriate location. Mark each adapter as "not active on boot" and
remove any IP address assigned to it. This ensures that the driver is
loaded and the adapter properly configured for use under ANS across
reboots.
VLANs
-----
IEEE 802.3ac Virtual LANs (VLANs) are based on the addition of a tag to the
packet header. All equipment on the network that passes this traffic must
be capable of handling the extra length. Settings on the adapter must match
the VLAN settings on the switch. VLANs also add to load time and require
additional memory resources. There is a limit of 64 VLANs per server;
however, VLANs may be numbered from 1 to 4096.
When working with VLAN tagging, all the ports on the switch connected to
the server should be configured to be tagged. In some Cisco switches it is
possible to configure ports to be both tagged and untagged at the same time;
although, this configuration will result in communication loss.
When adding new VLAN IDs to an active team the switch ports attached to the
team's members must be configured with the new VLAN IDs prior to adding
them to the ANS team. Otherwise, ANS might disable members that are not
sensing probes on the new VLAN IDs because the switch is not configured
accordingly.
NOTE: On stock Red Hat* 7.3 and 8.0 distributions, or on any 2.4.19 or
later kernel, Jumbo Frames (MTU > 1500) cannot be used simultaneously
with VLANs. Trying to do so will disconnect the team, and the team
must be rebuilt with standard MTU settings to restore connectivity.
Installing and Configuring ANS
==============================
To install and compile the base driver package(s), see the readme included
with those drivers. Make sure no other base drivers are loaded or compiled
into the kernel for any of the Intel adapters (e.g., eepro, eepro100,
eexpress, e100, e1000). Be sure the configuration files have been edited to
alias the new driver(s). See the Example Setup section for an example file.
NOTE: Not for use with eepro100 (module removal may be necessary).
Verify that all interfaces are working and that you have the base driver
file(s), e100.o and/or e1000.o, located in:
/lib/modules/<kernel_version>/kernel/drivers/net/
The locations listed above may vary for certain Linux distributions. For
exceptions, refer to the ldistrib.txt file included with this package.
1. Login as root.
2. Copy the iANS-x.x.x.tar.gz package file to a directory of your choice.
"x.x.x" specifies the iANS version number.
3. Open the package file by running 'tar xzf iANS-x.x.x.tar.gz'. This
creates a subdirectory for iANS-x.x.x under the current directory.
4. Enter the iANS-x.x.x directory. Choose one of these three methods for
installation:
a. PROCfg Utility. This command-line interface provides a simplified
configuration tool that reduces the amount of command-line input. At
this time, it is only available for 32-bit architectures. For more
information on using the PROCfg utility refer to the readme in the
PROCfg package. PROCfg is available on the Intel Customer Support
website, http://support.intel.com.
b. Scripted. Suggested only for the following distributions:
Red Hat (7.1, 7.2, 7.3)
SuSE* (7.3)
Caldera OpenLinux* (3.1)
TurboLinux* (7.0 server)
c. Manual (suggested for users with command-line experience)
Modifying ANS
-------------
ANS configuration and topology may be changed, with a few limitations.
After commit, you may change member priorities, add or remove team members,
add or remove virtual adapters, or remove a team entirely. You may not:
- Change the team mode.
- Remove or add VLAN support.
- Remove a team's last virtual adapter.
- Remove the last member of a team with open virtual adapters.
If a team is left with no server adapter or with no members at all, it goes
into an idle state until members are added. During such an idle period,
resources used by the team are not freed.
For instructions on modifying ANS, see the instructions in either the
scripted or manual configuration methods.
Removing ANS
------------
Removal of the ANS package includes:
- Bringing down all virtual adapter interfaces.
- Removing the ANS configuration from future reboots.
- Removing the ANS module.
- Removing the files from the system.
For instructions on removing ANS, see the instructions in either the
scripted or manual configuration methods.
Scripted Configuration
======================
If ANS is already installed on your system and you wish to either modify or
remove the package, refer to one of the following subsections under this
heading:
- Modifying ANS
- Removing ANS
For ease of configuration Intel supplies interactive scripts for the Linux
distributions listed above. ANS sets up four directories named Red Hat, SuSE,
Caldera, and Turbo to match each of these distributions under
'iANS-x.x.x/install_scripts/'.
To use the install script, first follow the instructions in Installing and
Configuring ANS. Then, enter:
iANS-x.x.x/install_scripts/[dist_name]
./INSTALL
SMP/UP and MODVERSIONS are determined by 'INSTALL'. If there is a mismatch
between the configuration for the kernel source tree and the running kernel,
a warning is displayed. Run 'INSTALL options' to see extra compilation
switches that allow overriding the kernel source tree settings.
Follow the instructions displayed on the console. You must answer the
following questions during the process:
1. "Would you like the configuration utility to remove all network
interfaces automatically?" The installation process must bring down the
network interfaces related to Intel adapters in order to unload the old
Intel drivers and replace them with the new ones.
Select 'Yes' (default) to remove all network interfaces, including other
brands. Select 'No' to choose each interface.
2. "Enter team name,(Enter) to end." You must enter either a team name (no
longer than 15 characters, often ends in an instance number) or press
<Enter> to quit adding teams. If you choose to quit, skip to Step 6.
"Would you like to have VLANs in team (name)?" Select 'Yes' to create a
VLAN-based team.
"Select members for team (name)" lists all applicable interfaces. Type
the number of the adapter to add to the team. Select the role (none,
primary or secondary). Repeat this for each adapter. Enter 0 when done.
3. "Enter virtual adapter name for team (name)." The virtual adapter name
can be anything, except 'ethx', as long as it ends with an instance
suffix and does not exceed 15 characters in length.
"Enter VLAN id for virtual adapter (name)." The VLAN id is for VLAN-based
teams only. Enter a number from 1 to 4096 to specify the VLAN.
"Enter boot protocol (none, bootp, dhcp, or other)." Choose 'none' to
manually enter the IP address and netmask. Choose 'bootp' or 'DHCP' to
enter the IP address and netmask from another machine. Or, choose 'other'
to enter the protocol name (such as IP).
NOTE: This information is NOT saved until you completely configure the
team and confirm your selection.
4. "Select Teaming Mode for Team (name) - AFT | ALB | FEC | GEC | 802.3ad |
NONE."
For descriptions, see the Overview section of this file. For Intel Link
Aggregation, use FEC or GEC.
WARNING: Choosing NONE still creates a team!
5. "Are you sure?" Choose 'Yes' to commit to the chosen team. Choose 'No' to
return to step 3.
After committing to the team, you may make another team or press <Enter>
to proceed.
6. "Would you like to save this configuration and load it on boot?" Choose
'Yes' (default) to merge the ans initialization script into the boot time
sequence. Choose the run levels that should automatically load the ANS
module. It is recommended that you select the same level as the network
boot, usually 2,3,4, or 5. If you do not want to save the configuration
for boot, select 'No'.
7. "Would you like to start the network now?" Select 'Yes' to activate the
team. Choosing 'No' should still show that installation and configuration
completed successfully. ANS starts at reboot if the settings were saved
in step 6.
Modifying ANS
-------------
To modify the ANS configuration, follow these instructions:
1. Manually modify the ANS topology description file:
/etc/ians/ians.conf
2. Call the ANS initialization script with the restart parameter:
/etc/rc.d/init.d/ans restart
3. To reactivate, run the network service initialization script with the
restart parameter:
/etc/rc.d/init.d/network restart
Removing ANS
------------
Follow these instructions to remove ANS:
1. Make sure you are logged in as root.
2. Enter the iANS-x.x.x/install_scripts/[distribution_name] directory.
3. Run 'UNINSTALL'.
4. The rest of the process is interactive. Follow the instructions
displayed on the console.
Prompts:
"Restore member adapters to original role (stand alone)." Answer 'Yes'
for each adapter you wish to continue using stand alone mode. This
configuration is made using Intel's e100(0).o driver; although, you
may restore other drivers.
Removal of the ANS module from memory does not down the adapters
running in stand alone mode. The script removes all files, scripts,
and links created except '/etc/ians/ians.conf'.
5. For the new settings to take effect, you must restart the network
service by either rebooting the system or running the network init
script with the restart parameter:
/etc/rc.d/init.d/network restart
NOTE: If you used the automatic INSTALL method for configuring ANS
note that lines were added to the '/etc/modules.conf' file. The
UNINSTALL script does not remove these lines. If you want to
remove them, you must do so manually.
Manual Configuration
====================
If ANS is already installed on your system and you wish to either modify or
remove the package, refer to one of the following subsections under this
heading:
- Modifying ANS
- Removing ANS
- Saving ANS Across Reboots
To install and configure ANS, first complete the instructions in Installing
and Configuring ANS. Then, follow these steps:
1. Enter the iANS-x.x.x/src directory, where "x.x.x" is the iANS version
number. Run 'make' to compile the module.
NOTE: SMP/UP and MODVERSIONS are determined by 'make'. If there is a
mismatch between the configuration for the kernel source tree and
the running kernel, a warning is displayed. Run 'make options' to
list the options available for overriding the source tree settings.
Options include SMP, MODVERSIONS, and DEBUG (not listed). DEBUG
values are 0 (debugging is off) and 1 (debugging is on). The
default is 0.
2. Run 'make install'.
NOTE: The default file locations are determined by 'make'. If there is a
mismatch between the configuration for the kernel source tree and
the running kernel, a warning is displayed. Either reboot to a
kernel that matches the kernel source tree or set the symbolic
link, usr/src/linux, to point to the kernel source tree that
matches the running kernel.
For a list of files and their default locations, see the Structure of
the ANS Build Tree section in this file.
3. After the required base drivers are loaded, down any Intel adapters
that are to be added to a team. If they already have an IP address,
remove the address by running 'ifconfig ethx 0.0.0.0'.
ifconfig - a - lists all current network devices
ifconfig ethx down - downs adapters so ANS may use them
NOTE: If you are not using Multi-Vendor Teaming, leave other vendor's
Ethernet adapters configured, as well as any Intel adapters that
are not added to teams. This ensures that the network device name
assignment remains consistent after rebooting.
4. Load the ANS module by running 'insmod ians'. In the following command
lines, optional items are placed in [ ]. All VLAN settings are shown as
optional.
5. To create teams and VLANs use the command line parameters listed in
Available Commands, General Configuration section.
6. Check the team status:
ianscfg -s
At this point the team is now active. You should be able to send and
receive packets via the virtual adapter.
7. If you want the new configurations to take affect after each reboot,
follow the instructions in Saving ANS Across Reboots.
Modifying ANS
-------------
To modify the ANS configuration, follow these instructions:
1. Take down the virtual adapter:
ifconfig <vadapter_name> down
2. Remove the ANS module:
rmmod ians
3. Create or modify the ANS topology file to match the new desired
topology. Default location: /etc/ians/ians.conf. Or, create a script
containing a set of calls to ianscfg that generates the desired
topology.
4. Load the ANS module:
insmod ians
5. Run the script created in step 3, or run the command:
ianscfg -r [-f <filename>]
where <filename> is the new topology file.
6. Reset each created virtual adapter:
ifconfig <vadapter_name> <IPaddr> [netmask <NETMASK>]
[broadcast <BROADCAST>]
7. Save the new configuration:
ianscfg -w [-f <filename>]
Create an interface configuration file for each new virtual adapter:
- The files would normally reside in '/etc/sysconfig/network-scripts/'.
- The name format should be 'ifcfg-<vadapter_name>'.
- Sample file content:
DEVICE="<vadapter_name>"
BOOTPROTO="none"
ONBOOT="yes"
IPADDR="<IP_address>"
NETMASK="<netmask>"
8. If any unnecessary virtual adapter configuration file is left,
remove it or modify it.
9. For any adapter that is desired as stand alone connection, you may
continue to use the Intel base driver.
Removing ANS
------------
Follow these instructions to remove ANS:
1. Login as root.
2. Run 'ifconfig -a' to see every virtual adapter configured in the
system.
3. For each virtual adapter, run 'ifconfig <vadapter_name> down'.
4. Remove the ANS module by running 'rmmod ians'.
5. In each virtual adapter config file, under
/etc/sysconfig/network-scripts/, either modify the
ifcfg-<vadapter_name> to contain the line 'ONBOOT="no"' instead of
'ONBOOT="yes"' or remove the file completely.
6. For each config file for stand alone adapters, under
/etc/sysconfig/network-scripts/, modify the file ifcfg-ethx to contain
the line 'ONBOOT="yes"' instead of 'ONBOOT="no"'.
7. You may leave the Intel base driver or you may edit the modules
configuration file, '/etc/modules.conf', to restore its original form.
To do this, remove the lines containing e100 or e1000 as the drivers
that were added and restore every line that was commented out.
8. Remove the ANS initialization script and all the links to it (e.g.,
'/etc/rc.d/init.d/ans' and '/etc/rc.d/rc.3/S09ans').
9. From the iANS-x.x.x/src directory, run 'make uninstall' to remove all
the files.
Saving ANS Configuration Across Reboots
---------------------------------------
The manual configuration method requires that you perform additional
steps in order to save the new ANS configuration across reboots. After
configuring the Ethernet and ANS drivers, follow these steps:
NOTE: The examples provided might vary for different Linux distributions.
1. Save the ANS configuration to a file by running:
ianscfg -w [-f <file_name>]
The default is '/etc/ians/ians.conf'.
2. Make sure that the adapters that were selected as members of the
team(s) are NOT configured on boot. To do so, change "ONBOOT=yes" to
"ONBOOT=no" in every matching
'/etc/sysconfig/network-scripts/ifcfg-ethx' file.
3. Set each virtual adapter to configure on boot by creating a config
file, '/etc/sysconfig/network-scripts/ifcfg-<vadapter_name>'. The file
must look something like this:
DEVICE="<vadapter_name>"
BOOTPROTO="none"
ONBOOT="yes"
IPADDR="<IP_address>"
NETMASK="<netmask>"
4. Create an init script that loads the e100.o, e1000.o (if needed) and
ians.o modules and configures the ANS topology. You may use the sample
script file by copying 'iANS-x.x.x/install/Red Hat/ans' to
'/etc/rc.d/init.d/ans'. Configuration is read from
'/etc/ians/ians.conf' by default. If you wish to use any other file,
modify the script.
5. Add the ANS script to the init process for the appropriate run levels.
Run 'chkconfig --add ans'.
Available Commands
==================
The following options describe common ANS commands:
- General Configuration
- Removing ANS
- Other Options
NOTE: If you are using Multi-Vendor Teaming, do not use the "-V" or "-i"
options. These flags are specific to VLANs, which are not supported
with Multi-Vendor Teaming.
========================================================================
OPTION COMMAND
========================================================================
General Configuration:
------------------------------------------------------------------------
Create a team ianscfg -a -t <team_name> [-M <mode>] [-V]
Use the -M to specify the teaming mode. The default is AFT. Other
options include ALB, FEC, GEC, 802.3ad, NONE.
Use -V to set a VLAN.
Use -M NONE to set a VLAN with no teaming mode.
------------------------------------------------------------------------
Set/change team mode ianscfg -C -t <team_name> -M <mode>
(only before commit)
------------------------------------------------------------------------
Add team members ianscfg -a -t <team_name> -m <ethx>
[-p <priority_role>]
<priority_role> can be none, primary or secondary. Only existing Intel
Ethernet devices may be added to a team.
------------------------------------------------------------------------
Add virtual adapter ianscfg -a -t <team_name> -v <vadapter_name>
[-i <vlan_id>]
On non-VLAN teams, define ONLY one virtual adapter per team.
The name of the virtual adapter may be anything except 'ethx', as long
as it ends with an instance suffix and does not exceed 15 characters in
length.
Specify the -i option (vlan_id) only on VLAN-based teams or adapters.
------------------------------------------------------------------------
Activate (commit) the ianscfg -c <team_name>
team
After a team has been activated, members may still be added or removed.
At this point the virtual adapter appears (ifconfig -a) in the adapters
list, but it is in the down state.
------------------------------------------------------------------------
Activate the virtual ifconfig <vadapter_name> <IP_address> netmask
adapter <netmask> broadcast <broadcast>
========================================================================
Removing ANS:
------------------------------------------------------------------------
Disable the virtual ifconfig <vadapter_name> down
adapter
------------------------------------------------------------------------
Remove a member ianscfg -d -m <ethx>
Do not specify the team here.
------------------------------------------------------------------------
Remove a virtual adapter ianscfg -d -v <vadapter_name>
(except the last one)
------------------------------------------------------------------------
Remove a team (without ianscfg -d -t <team_name>
members/virtual adapters)
------------------------------------------------------------------------
Remove a team ianscfg -d -t <team_name> -r
(recursively, with all
associated members and
virtual adapters)
------------------------------------------------------------------------
Remove the ANS module rmmod ians
(down all virtual adapters
first)
------------------------------------------------------------------------
Remove ANS files from make uninstall
your system (after
bringing down virtual
adapters and resetting the
configuration), from the
iANS-x.x.x/src directory
========================================================================
Other:
------------------------------------------------------------------------
Save the current ianscfg -w [-f <filename>]
configuration in a file
(only after commit)
The default is an editable text file named '/etc/ians/ians.conf'.
------------------------------------------------------------------------
Automatically program a ianscfg -r [-f <filename>]
topology configuration
from a file
The default file is '/etc/ians/ians.conf)'
------------------------------------------------------------------------
Turn off probes ianscfg -P -t <team_name> -d
------------------------------------------------------------------------
Get status ianscfg -s
------------------------------------------------------------------------
Get help on the ianscfg ianscfg
utility
========================================================================
Structure of the ANS Build Tree
===============================
- Kernel dependant source files (src/*.[ch], src/lib/*.[ch])
- Kernel independent precompiled object file (bin/[ARCH]/ians_core.o)
- Makefiles
- ANS configuration utility (bin/[ARCH]/ianscfg)
- ANS general utility daemon (bin/[ARCH]/iansd)
- Installation, uninstall and configuration scripts
NOTE: [ARCH] is either "ia32" or "ia64".
Distribution of files:
By default, the components are distributed as follows:
- /lib/modules/<kernel_version>/kernel/drivers/net/ians.o
- /usr/sbin/ianscfg
- /usr/sbin/iansd
- /usr/share/man/man1/ianscfg.1.gz
modules.conf file example:
#alias eth0 eepro100
#alias eth1 eepro100
#alias eth2 eepro100
alias eth0 e100
alias eth1 e100
alias eth2 e100
alias parport_lowlevel parport_pc
alias scsi_hostadapter aic7xxx
Example Setup
=============
Example File for Setting up AFT Mode with VLANs: (two PRO/100 adapters)
-----------------------------------------------------------------------
insmod e100
insmod ians
ianscfg -a -t team1 -M AFT -V
ianscfg -at team1 -m eth0 -p primary
ianscfg -at team1 -m eth1 -p secondary
ianscfg -at team1 -v vadapt1 -i 10
ianscfg -at team1 -v vadapt2 -i 15
ianscfg -c team1
ianscfg -s
ifconfig vadapt1 192.168.1.1 netmask 255.255.255.0
ifconfig vadapt2 192.168.2.1 netmask 255.255.255.0
Troubleshooting
===============
NOTE: For distribution-specific information, see the ldistrib.txt file
included in the driver tar.
1. If an adapter has been running standalone with an assigned IP address,
you must configure the IP address to 0.0.0.0 before adding it to a team:
ifconfig ethx {0.0.0.0}.
2. Always bind the protocol to the virtual adapter and NOT to the physical
adapter for adapters that are in a team. This applies to stand-alone
adapters as well.
3. If you do not remove references to other possible base drivers in the
configurations, you risk multiple interfaces and unpredictable outcomes
for adapters you wish to use in the team.
4. If you receive an error message, "module not loaded," during
configuration of the team, start over. To do so, enter:
./INSTALL veryclean all SMP=[0|1] MODVERSIONS=[0|1]
Choose 0 or 1 for SMP, and select MODVERSIONS to match the configuration
for the current kernel tree.
NOTE: This error occurs when the target module does not match the kernel
version and when install was done without parameters (found using
'./INSTALL' options).
5. If, when adding the ANS script to the init process, you receive an error
message, "service ans does not support chkconfig", manually create the
symbolic link to the ANS file for each run level desired by entering:
ln -s /etc/rc.d/init.d/ans /etc/rc.d/rcX.d/S09ans
where X is the number of the desired run level.
6. If you are moving adapters in and out of teams with Jumbo Frames, check
the MTU settings for Jumbo Frames.
With certain versions of the e1000 base driver, VLANs cannot be used
with Jumbo Frames. To use Jumbo Frames and VLANs simultaneously you must
use an e1000 driver version prior to 4.4.10.
7. If you receive the error message, "Intel Advanced Network Services (iANS)
has determined you have selected network adapters that are not eligible
to participate as members of an iANS team. Please install Intel Server
Adapters in your system and re-install the advanced server features.",
this indicates that either:
a. the team needs at least one Intel server adapter, or
b. the last chosen adapter is from another vendor and is not capable of
participating in the team.
8. When trying to compile the driver by running make install, the following
error may occur:
"Linux kernel source not configured - missing version.h"
To solve this issue, create the version.h file by going to the Linux
source tree and doing a make include/linux/version.h.
9. If a non-Intel adapter is selected as the preferred primary adapter, some
switch behaviors may cause the server to enter an infinite networking
failover loop. If the preferred primary is an Intel adapter and it
senses a link loss, ANS will failover to the non-Intel adapter (which
only becomes the current primary, not the preferred one) and the user may
encounter a temporary communication loss that automatically recovers as
soon as the switch is ready to start traffic on that port. Once the
preferred primary (Intel) adapter gets its link back, it will take over
again, this time without losing traffic.
10. PCI Hot Plug Add/Remove.
- When executing a PCI Hot Plug Remove operation on an adapter that is
part of an ANS team, the adapter is automatically removed from the team.
- When reactivating an adapter with a PCI Hot Plug Add operation, the new
interface should be manually added back into the team by an ANS Hot Add
operation.
11. If you are running an AFT/ALB team and receive the following messages
numerous times, "Adapter ethx does not sense any probes. Possible reason:
Adapter deactivated, Adapter isolated, Partitioned team." and then,
"Adapter ethx rejoined.", probe packets are being dropped (by the kernel
queues, switch, etc.) resulting in the ANS team losing probes. This could
happen in a healthy system that is under heavy stress.
As a workaround, disable the probes by issuing the following command:
ianscfg -P -t <team_name> -d
12. Different switches react differently when the switch manager disables a
switch port. Some switches react with a link loss of the disabled port
and others do not change the link status at all. If the link status is
not affected when a port is disabled then ANS cannot always detect that
a switch port that is connected to an ANS member has been disabled by
the switch manager. ANS detects that the port has been disabled even
though no link status change occurs only if one of two conditions exist:
- Probes are enabled and there are more than two enabled and active
members in the team (relevant to AFT & ALB teaming modes only). ANS
detects that the member attached to the disabled port is missing
probes while others are receiving and transmitting probes successfully.
- Teaming mode is 802.3ad - ANS deactivates the member attached to the
disabled port since no LACPDUs will be received by ANS on the disabled
port.
To avoid problems of fault tolerance in FEC, GEC, and ALB teaming modes
the switch manager should physically disconnect the link on the disabled
port or remove the member connected to the disabled port from the team.
In AFT mode it is enough to set an active member that is attached to an
enabled port to be the preferred primary and make sure that the priority
of the member attached to the disabled port is "none".
Support
=======
For general information, go to the Intel support website at:
http://support.intel.com
If an issue is identified with the released source code on the supported
kernel with a supported adapter, email the specific information related to
the issue to linux.nics@intel.com.
License
=======
This software program is released under the terms of a license agreement
between you ('Licensee') and Intel. Do not use or load this software or any
associated materials (collectively, the 'Software') until you have carefully
read the full terms and conditions of the licenses located in this software
package. By loading or using the Software, you agree to the terms of this
Agreement. If you do not agree with the terms of this Agreement, do not
install or use the Software.
* Other names and brands may be claimed as the property of others.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.