# Installing and Configuring Intel® Advanced Networking Services (ANS) on the Linux* 2.2.x and 2.4.x Kernels (Intel 32/64-bit architectures)

Overview

Installing and Configuring ANS

Saving ANS Configuration Across Reboots

Removing ANS

Modifying ANS Configurations

Available Commands

Structure of the ANS Build Tree

Example Setup

Troubleshooting

Support

## Overview

This file describes the Intel® Advanced Network Services (ANS) package, version 1.6.x, for Linux* systems. Intel ANS provides both teaming (including Multi-Vendor Teaming), and IEEE VLAN capabilities.

This package was tested primarily on the Red Hat* Linux 2.4.7 kernel on both UP and SMP Intel processor-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. A list of supported adapters and kernels is available in the e100 and e1000 base driver documentation.

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. Includes fault tolerance.

> | NOTE: ALB does not require that all team members have matching speed/duplex settings.

> FEC/LA/802.3ad (Cisco*'s Fast EtherChannel* Technology (FEC), Intel Link Aggregation, or IEEE 802.3ad Link Aggregation). A team of 2-8 adapters at 10/100 speeds that simultaneously receive and transmit data. Includes fault tolerance and load balancing. Must match speed/duplex settings on all team members. This requires a switch that supports Intel Link Aggregation, Cisco's FEC, or static 802.3ad. Spanning Tree Protocol must be turned off. Must match switch aggregation requirements.

> GEC/LA/802.3ad (gigabit equivalent of FEC). Requires a switch that supports Intel Link Aggregation, Cisco's GEC, or static 802.3ad. Requires PRO/1000 Adapters. Other requirements similar to FEC above.

> 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.

| NOTE: The Intel ANS driver requires at least one Intel PRO/100 or PRO/1000 server adapter to form a team.
| NOTE: 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/LA/802.3ad, GEC/LA/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 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.

## Installing and Configuring ANS

To install and compile the base driver package(s), see the readme included with those drivers. Use the latest driver from the Intel support website.

| 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:

> For 2.2.x kernels: /lib/modules/<kernel_version>/net/

> For 2.4.x kernels: /lib/modules/<kernel_version>/kernel/drivers/net/

The locations listed above may vary for certain Linux distributions. For exceptions, refer to ldistrib.htm.

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:

   1. 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 procfg.htm. PROCfg is available on the Intel Customer Support
      website, http://support.intel.com.

   2. Scripted (suggested ONLY for specific releases of Red Hat, SuSE*, Caldera*, and TurboLinux*)

   3. Manual (suggested for users with command-line experience)

### Scripted Method

For ease of configuration, Intel supplies interactive scripts that are only supported on:

> | Red Hat (6.x, 7, 7.1, 7.2)
> | SuSE (6.4, 7.1)
> | Caldera (2.2, 3.1)
> | TurboLinux (6.0 server, 6.1 server)

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, 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.

For ANS support, you must use driver version 1.8.x (or higher) for PRO/100 and/or driver version 4.1.x (or higher) for PRO/1000. 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) and not any previous drivers. See the Example Setup section for an example file.

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 V LAN.

   "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) - None | AFT | ALB | FEC/LA/802.3ad | GEC/LA/802.3ad."
   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.

### Manual Method

| 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.
| NOTE: FEC and GEC are the command line values for FEC/LA/802.3ad and GEC/LA/802.3ad.

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. For ANS support, you must use driver version 1.8.x (or higher) for PRO/100 and/or driver version 4.1.x (or higher) for PRO/1000.

   | NOTE: 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) and not any previous drivers. See the Example Setup section for an example file.

4. 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.

5. 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.

6. Create team(s):

   > ianscfg -a -t <team_name> [-M <mode >] [-V]

   -M sets the teaming mode (AFT (default)| NONE | ALB | FEC | GEC).
   -V sets a VLAN.

   | NOTE: Use -M NONE -V to set a VLAN with no teaming mode specified.

7. Determine the teaming mode (AFT, NONE, ALB, FEC, GEC) for each team:

   > ianscfg -C -t <team_name> -M <mode>

   | NOTE: The teaming mode may be specified in either steps 6 or 7

8. Add adapters to the team and specify their role (priority):

   > ianscfg -a -t <team_name> -m <ethx> [-p <priority role>]

   Priority may be none, primary, or secondary

9. Create virtual adapters:

   > ianscfg -a -t <team_name> -v <vadapter_name> [-i <vlan_id>]

   vadapter_name 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 options (vlan_id) only on VLAN-based teams or adapters.

10. Activate the team:

    > ianscfg -c <team_name>

11. Activate the virtual adapter:

    > ifconfig <vadapter_name> <IP_address> netmask <netmask> [broadcast <broadcast>]

    | NOTE: This binds the protocol to the virtual adapter.

12. 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.

### Saving ANS Configuration Across Reboots

| NOTE: Do not complete these steps if you are using the scripted configuration method. Sample lines are Red Hat 6.x specific. You must modify the examples for your distribution.

Now that the Ethernet and ANS drivers are configured, follow the instructions below to configure the system to activate ANS the same way every time it boots.

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 --level <run levels> ans on', where <run levels> is a set of run level where ANS starts. For example, 345.

   | NOTE: This script must be invoked BEFORE the system starts the network services. For example, if your network init script for run level 3 is '/etc/rc.d/rc3.d/S10network', create a symbolic link '/etc/rc.d/rc3.d/S09ans' that points to '/etc/rc.d/init.d/ans'. ANS service is automatically stopped when the network service is stopped.

## Removing ANS

There are several stages to removing ANS:

> | Bringing down all virtual adapter interfaces
> | Removing the ANS configuration from future reboots
> | Removing the ANS module
> | Removing the files from the system

There are two methods for removing ANS:

1. Scripted Method

2. Manual Method

### Scripted Method (only those distributions covered by scripted install)

1. Login 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'.

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. These lines are not removed by the UNINSTALL script. If you want to remove them, you must do so manually.

### Manual Method

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.

   | NOTE: For some 2.2.x kernel systems, the modules configuration file is named 'conf.modules'.

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.

## Modifying ANS Configuration

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.

There are two methods of reconfiguring:

1. Semi-automatic: good for changing the mode and/or moving members between teams. Neither new teams nor virtual adapters can be created with this feature, and all adapters must remain in teams.

2. Manual

| NOTE: When disabling all members of a team or VLAN, you must bring down the virtual adapter before bringing down any member interface.

### Semi-automatic Method

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

### Manual Method

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 following command, where <filename> is the new topology file:

   > ianscfg -r [-f <filename>]

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 files would normally reside in '/etc/sysconfig/network-scripts/'
   > | 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.

## Available Commands

| 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.
| NOTE: FEC and GEC are the command line values for FEC/LA/802.3ad and GEC/LA/802.3ad.

#### Create a team:

> ianscfg -a -t <team_name> [-M <mode>] [-V]

> Use the -M flag to specify the teaming mode. The default is AFT. Other options include NONE, ALB, FEC, or GEC.
> Use the -V flag to specify a VLAN.

#### Set/change team mode (only before commit):

> ianscfg -C -t <team_name> -M <mode>

#### Add team members:

> ianscfg -a -t <team_name> -m <ethx> [-p Y]

> where Y can be none, primary or secondary, optional. 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>]

> | NOTE: On non-VLAN teams, define ONLY one virtual adapter per team. On VLAN teams, the -i options (vlan_id) must be specified. The name of the virtual adapter can be anything except 'ethx' but must include an instance number suffix.

#### Activate (commit) the team:

> ianscfg -c <team_name>

> After a team has been activated, members may still be added or removed.

> | NOTE: At this point the virtual adapter appears (ifconfig -a) in the adapters list, but it is in the down state.

#### Activate the virtual adapter:

> ifconfig <vadapter_name> <IP_address> netmask <netmask> broadcast <broadcast>

#### Get status:

> ianscfg -s

#### Get help on the ianscfg utility:

> ianscfg

#### To remove a member:

> ianscfg -d -m <ethx>

> | NOTE: Do not specify the team here.

#### To disable the virtual adapter:

> ifconfig <vadapter_name> down

#### To remove a virtual adapter (except the last one):

> ianscfg -d -v <vadapter_name>

#### To remove a team (without members/virtual adapters):

> ianscfg -d -t <team_name>

#### To remove a team (recursively, with all associated members and virtual adapters):

> ianscfg -d -t <team_name> -r

#### To remove the ANS module (down all virtual adapters first):

> rmmod ians

#### To remove ANS files from your system (after bringing down virtual adapters and resetting the configuration), from the iANS-x.x.x/src directory:

> make uninstall

#### To save the current configuration in a file (only after commit):

> ianscfg -w [-f <filename>]

> The default is an editable text file named '/etc/ians/ians.conf'.

#### To automatically program a topology configuration from a file:

> ianscfg -r [-f <filename>]

> The default file is '/etc/ians/ians.conf)'.

#### Turn off probes:

> ianscfg -P -t <team_name> -d

## 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:

> - For 2.2.x kernels: /lib/modules/[KERNEL_VERSION]/net/ians.o

> - For 2.4.x kernels: /lib/modules/[KERNEL_VERSION]/kernel/drivers/net/ians.o

> - /usr/sbin/ianscfg

> - /usr/sbin/iansd

> - For Red Hat 6.x: /usr/man/man1/ianscfg.1.gz

> - For Red Hat 7, 7.1, 7.2: /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 issues, see ldistrib.htm.

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 standalone 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.

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:

   1. the team needs at least one Intel server adapter, or

   2. 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. Setting a non-Intel adapter to a priority higher than the current primary adapter's priority can cause the system to lose its stability and enter a mode where continuous failovers occur.
   This type of failover tends to appear when certain switches have a delayed recovery time after a link loss. If you are using a switch and notice such behavior, avoid setting an MVT adapter as the primary adapter.

10. PCI Hot Plug Add/Remove.

    1. 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.

    2. 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.

## Support

For general information and support, 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.

Copyright © 2002 Intel Corporation. Legal Information