[eepro100] e100 Intel driver and iANS utility: impossible to
ping
SECCI,SANDRO (HP-Italy,ex1)
sandro_secci@hp.com
Wed, 11 Jul 2001 11:35:24 +0200
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01C109EC.CF78B210
Content-Type: text/plain;
charset="iso-8859-1"
Hi Christoph,
the module iANS developed by Intel permit to do some important things when
you work with multiple nic adapters:
ALB: load balancing between NICs
AFT: fault tolerance between NICs
FEC/GEC
For more informations you can see attachment.
Best Regards,
Sandro
-----Original Message-----
From: Christoph Plattner [mailto:christoph.plattner@alcatel.at]
Sent: Wednesday, July 11, 2001 11:30
To: SECCI,SANDRO (HP-Italy,ex1)
Cc: 'eepro100@scyld.com'
Subject: Re: [eepro100] e100 Intel driver and iANS utility: impossible
to ping
I always want to know, what the iANS module is ?
I have not fount it in README, etc, so I have no idea for what ...
I also had no idea, what to do with the iANS, after I had done a short
code reading, reading commets, etc....
Can anybody explain this in some words ?
With friendly regards
Christoph P.
"SECCI,SANDRO (HP-Italy,ex1)" wrote:
>
> Hello all,
> I'm working with two D5013B HP nic cards and I try to work with ALB
(Adapter
> Load Balancing) functionality offered by iANS Intel Utility. I use for
this
> purpose the Intel driver e100 version 1.6.6 and the iANS utility version
> 1.3.06. I work with Linux RH 7.0 kernel 2.2.16.
> For trying to do ALB I unload default eepro100 module and I load modules
> e100 and ians. I follow exactly all instruction to create configuration
and
> all seems to work without errors. I set one virtual lan and I configure
this
> with ifconfig. When I try to ping the virtual lan from another PC the
> virtual lan don't answer. I cannot ping also from the virtual lan another
> card but I can ping themself.
> In the routing table the virtual lan is present.
> system work with 2 nics when I use e100 drivers without iANS.
> Somebody know what can I do to ping out of the box? I nothing change in
the
> modules.conf. Must I insert aliases?
> Must I define other routing roules? Must I install another kernel version?
>
> Thank you very much for your help.
>
> Sandro Secci
>
> Hewlett Packard
>
>
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100
------------------------------------------------------------------
private: christoph.plattner@gmx.at
company: christoph.plattner@alcatel.at
------_=_NextPart_000_01C109EC.CF78B210
Content-Type: text/plain;
name="ans.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="ans.txt"
Installing and Configuring Intel(R) Advanced Networking Services (ANS)=20
on the Linux 2.2.x and 2.4.x Kernels (Intel IA-32 architecture only)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Contents:
- Overview & Environment
- Installation of Advanced Networking Services=20
- Configuring the Adapters and Teams
- Saving the Configuration across Reboots
- Removing Advanced Networking Services
- Modifying Advanced Networking Services Configurations
- Available Commands=20
- Example of Setting Up an AFT team
- Troubleshooting (also includes file distribution and conf.mod=20
example)
- License
Overview and Environment
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
This package was tested on Red Hat* Linux* with 2.4.0 on both=20
UP and SMP Intel processor based PCs. =20
Installation assumes all necessary kernels and build tools are loaded =
and that you are using the latest Intel base drivers found at =
support.intel.com.(Base drivers provided in some distributions do not =
contain the necessary hooks for ANS.)=20
Note: Base drivers provide support for some beta features which are not =
supported at this time by ANS including Compaq hotplug and Intel(R) =
Itanium(TM) architecture")
These Advanced Networking Services only work with Intel(R) PRO/100 =
server and desktop adapters and each team requires at least one Server =
adapter.=20
Linux is not supported on the Intel(R) PRO/100 Intelligent Server =
Adapter.
ANS is not supported on the Intel(R) PRO/100 VE Adapter.
The package supports IEEE VLANs and the following teaming modes:=20
* AFT ( 10/100 and 1000) Adapter Fault Tolerance
* ALB ( 10/100 or 1000) Adaptive Load Balancing (includes AFT)
* FEC (10/100) or GEC (1000) Link Aggregation/FEC/GEC=20
Descriptions of the teaming modes and their specific requirements are:
- AFT (Adapter Fault Tolerance). Default mode. A secondary adapter in =
the team will automatically take over on any failure of the primary=20
connection (cable, adapter or port). Only one card is active at a=20
time. After a failover, if the connection to the primary adapter is=20
restored, control passes automatically back to that primary adapter. =
May mix speed and duplex capabilities and settings. May use a hub or =
any switch.
- ALB (Adaptive Load Balancing or asymmetrical link aggregation). A=20
team of 2-8 adapters share the transmission load while the primary=20
receives and transmits. Includes fault tolerance. Must match speed/
duplex settings on all team members. May use any switch.
- Link Aggregation (Cisco*'s Fast EtherChannel* Technology (FEC) or=20
Intel Link Aggregation). A team of 2-8 10/100 adapters which=20
simultaneously receive and transmit. Includes fault tolerance and=20
load balancing. Must match speed/duplex settings on all team =
members. =20
This requires a switch that supports Intel Link Aggregation or =
Cisco's=20
FEC. Spanning Tree Protocol must be turned off. Must match switch=20
aggregation requirements.
- GEC (Gigabit equivalent of FEC). Requires GEC compatible switch and
PRO/1000 Adapters. Similar requirements to FEC/LA above.
Roles - For AFT and ALB, you may specify which adapters in a team you =
want
to use as the Primary and Secondary adapters. The Primary will be the =
main
adapter to be used in a team. For fault tolerance, the Primary is the =
only
adapter used until a failure. For ALB, the Primary is the adapter that =
both
transmits and receives. The Secondary is the preferred adapter (in a =
team
consisting of more than 2 adapters) to fill the role of Primary adapter =
if
it fails. If Priority is not specified, the adapter with the highest
supported speed will be chosen. If all adapters support the same =
speed,
the last one added will be the primary.
IEEE 802 Virtual LANs (VLANs) are based on the addition of a tag to the =
packet header. All equipment on the network that will pass this =
traffic=20
must be capable of handling the extra length. Settings on the adapter=20
must match the VLAN settings on the switch. VLANs also add to load time=
=20
and require additional memory resources. There is a limit of 64 VLANs=20
per server. However VLANs may be numbered from 1-4096. =20
Installation of the ADVANCED NETWORKING SERVICES Package
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
Please install and compile the base driver package(s) per the readme=20
included with those drivers. Please use the latest driver from the =
Intel
support site.=20
*Not for use with eepro100 (module removal may be necessary).
Verify that all interfaces are working and that you have=20
the basedriver file(s) (e100.o, e1000.o) located in
(2.2.x) /lib/modules/<kernelversion>/net/
(2.4.x) /lib/modules/<kernelversion>/kernel/drivers/net/
1. Login as root.
2. Copy the iANS-x.x.x.tar.gz package file to a directory of your =
choice. =20
3. Open the package file by running 'tar xzf iANS-x.x.x.tar.gz'
This will create iANS-x.x.x as a subdirectory under the current=20
directory.
4. Enter the iANS-x.x.x directory.
At this point, choose between the 2 separate methods for installation:
1. Manual (suggested for experienced users)
2. Scripted (suggested ONLY for Red Hat* 6.x, 7.0, 7.1, SuSE* 6.4, =
Caldera* 2.2, and TurboLinux* Server 6.0 users)=20
Manual Installation and Configuration =20
-------------------------------------
1. From the directory iANS-x.x.x 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 kernel itself, run 'make options" to list options available for =
=20
overriding the source tree settings. These include SMP, =
MODVERSIONS,=20
and NODEBUG (not listed). NODEBUG values are 0 (debugging is on),=20
1 (debugging is off). Default is 0.
2. Run 'make install'. (Default file locations may be changed by=20
editing the paths at the top of Makefile - see Troubleshooting=20
section.) There will not be any messages after make install.
=20
See the Troubleshooting section for a list of files and their=20
default locations.
=20
3. You must use Base Driver version 1.5.5 (or higher) for PRO/100=20
and/or Base Driver version 2.6.6 (or higher) for PRO/1000 for ANS=20
support.
NOTE: Make sure no other base drivers are loaded (nor compiled into =
the kernel, for any of the Intel adapters. (e.g. eepro, eepro100, =
eexpress, e100,e1000). Be sure the configuration files have been=20
edited to alias the new driver(s) and not any previous drivers. =20
Please see the trouble-shooting 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,=20
run ifconfig ethx 0.0.0.0 to remove the IP number.)
ifconfig - a - will list all current network devices
ifconfig ethx down - will down adapters so ANS may be loaded
Note: You should leave other vendor's Ethernet adapters configured=20
as well as any Intel adapters that you will not adding to teams. =20
This will ensure that network device name assignment remains=20
consistent after reboot.
=20
5. Load the Advanced Networking Services module by running=20
'insmod ians'. In the following command lines, optional items are=20
placed in [ ]. All VLAN settings are shown as optional.
6. Create team(s);=20
ianscfg -a -t<team_name> [-M<mode >] [-V]
Use the -M flag to specify the teaming mode (default AFT, others=20
NONE | ALB | FEC | GEC ). =20
Use the -V flag to specify a VLAN . =20
Use -M NONE if you wish VLANs on single adapters without link=20
aggregation. Any other mode may be specified to use VLANs and link
aggregation simultaneously.
7. Determine the teaming mode (AFT, ALB, FEC, GEC) for each=20
team.
ianscfg -C -t<team_name> -M<mode>
NOTE: team mode can be specified in either steps 6 or 7
8. Add Intel adapters to the team and specify role (priority)
ianscfg -a -t<team_name> -m<ethNN> [-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>]=20
vadapter_name may be anything except ethx as long as it ends with=20
an instance suffix
specify the -i options (vlan_id) only on VLAN based teams or adapters.
=09
10. Activate the team=20
ianscfg -c<team_name>
11. Activate the virtual adapter =09
Note: This binds the protocol to the VIRTUAL adapter.
ifconfig <vad_name> <ip#> netmask <mask#> [broadcast =
<broadcast>]
12. Check team status
ianscfg -s
At this point the team is now active. You should be able to send and=20
receive packets via the virtual adapter.
Scripted Installation and Configuration
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
For ease of configuration, Intel is supplying interactive scripts - =
which
are only supported on:
Red Hat* (6.x, 7.0, 7.1)
SuSE* (6.4)
Caldera* (2.2)
TurboLinux* (6.0 server)
ANS will set up 4 directories named Red Hat, SuSE, Caldera, and Turbo =
to
match each of these distributions under iANS-x.x.x/install/
To use the install script, enter iANS-x.x.x/install/[dist_name] and =
type
./INSTALL=20
NOTE: The module is created with support for the SMP/UP and =
MODVERSIONS
features as defined by the configuration of the current kernel =
source
tree (/usr/src/linux/). On some systems, there might be a mismatch
between this configuration and the kernel image itself. If there is
a mismatch, it will not be apparent until further in the process.
Run 'INSTALL options' to see extra compilation switches that allow
overriding the kernel source tree settings.
Then follow the instructions displayed on the console. You will be =
asked
some questions during the Process:
1. "Would you like the configuration utility to remove all network=20
interfaces automatically?" The installation process must bring down =
the=20
network interfaces related to Intel adapters, in order to unload =
the old
Intel drivers and replace them with the new ones.
Select Yes (default) removes all network interfaces (including =
other=20
brands). =20
Select No to choose for each interface.
2. "Enter team name,(Enter) to end." You must enter either a team name =
(often a number) or press Enter (CR) to quit adding teams (skips to =
Step 6). "Would you like to VLANs in team (name)" - Yes will =
create=20
a VLAN-based team. "Select members for team (name)" will list all=20
applicable interfaces and you need to type in the number of the=20
adapter to add to the team. Select the role (none, primary or=20
secondary). Repeat for each adapter (enter 0 when done.)=20
3. "Enter virtual adapter name for team (name)" This can be anything=20
but ethx and must end in an instance suffix. =20
"Enter VLAN id for virtual adapter (name)" (for VLAN-based teams=20
only) enter a number 1-4095 to specify the Virtual LAN.
"Enter boot protocol (none, bootp, dhcp, or other)",=20
If choose none will need to manually enter IP address and netmask. =20
If choose bootp or DHCP must be able to reach another machine
assigning the IP address and netmask.
If choose Other must enter protocol name (such as IP)
NOTE: This information will NOT be saved until you confirm your=20
selection after configuring the team.
4. "Select Teaming Mode for Team (name) - None\AFT\ALB\FEC\GEC\"=20
- for descriptions see the first section of the readme. For Intel=20
Link Aggregation use FEC or GEC. WARNING: Choosing None will still =
create a team!
5. "Are you sure?" Yes commits the team. Choosing No will make you=20
start again at step 3.
After commit, you may make another team, or press Enter to proceed.
6. "Would you like to save this configuration and load it on boot?"
Yes (default) - modifies init file. Choose which run-levels will=20
have the ANS module automatically loaded. (Recommendation: select=20
same level as the network boot - commonly 2,3,4, or 5)=20
No - means the configuration will not be saved for boot.
7. "Would you like to start the network now?"
Yes - activates the team=20
No - should still show installation and configuration completed=20
successfully.
ANS will start at reboot if configuration was saved in step 4.
Saving ADVANCED NETWORKING SERVICES configuration across reboots=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
NOTES: Do not use if setting up via Scripted configuration method.
Sample lines are Red Hat 6.x specific - please modify 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>]
(default is /etc/ians/ians.conf)
2. Make sure that the adapters that were selected as members of=20
the team(s) are NOT configured on boot. To do so, change=20
"ONBOOT=3Dyes" to "ONBOOT=3Dno" in every matching /etc/sysconfig/
network-scripts/ifcfg-ethX file.
3. Set each virtual adapter to configure on boot by creating a config=20
file /etc/sysconfig/network-scripts/ifcfg-<vadapter_name>,
which should look something like this:
DEVICE=3D<vadapter_name>
BOOTPROTO=3D"none"
ONBOOT=3D"yes"
IPADDR=3D"192.168.1.1" (sample)
NETMASK=3D"255.255.255.0" (sample)
4. Create an init script that will load the e100.o, e1000.o (if =
needed)=20
and ians.o modules, and configure the ANS topology. You can use=20
the sample script file by copying iANS-x.x.x/install/Red Hat/ans
to /etc/rc.d/init.d/ans Configuration will be read from /etc/ians/
ians.conf by default. Modify the script if you wish to use any=20
other file.
5. Add the ANS script to the init process of the appropriate run =
levels.
Run 'chkconfig --level <run levels> ans on' where <run levels> is=20
the run levels you would like ANS to start in.
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, you should create a symbolic link=20
/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=20
stopped.
=20
Removing ADVANCED NETWORKING SERVICES
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
There are several stages to removing Advanced Networking Services.
* Bringing down all vadapter 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: manual and scripted.
Manual method of Removing ANS
-----------------------------
1. Login as root.
2. Run 'ifconfig -a' to see every virtual adapter configured in the=20
system.
3. For each virtual adapter, run 'ifconfig <vadapter-name> down'=20
4. Remove the ians module by running 'rmmod ians'
5. In each virtual adapter file, either modify the file to contain the =
line ONBOOT=3D"no" instead of ONBOOT=3D"yes" or remove the file =
completely.
6. For each file for stand alone adapters, modify the file to contain=20
the line ONBOOT=3D"yes" instead of ONBOOT=3D"no".
7. You may leave the Intel base driver or you may edit the modules =
config
file (usually /etc/conf.modules or /etc/modules.conf) and restore =
its
original form by removing the lines containing e100 or e1000 as the =
drivers that were added and restoring every line that was commented =
out. =20
8. Remove the ANS initialization script and all links to it.
(e.g. /etc/rc.d/init.d/ans and /etc/rc.d/rc.3/S09ans).
9. From iANS-x.x.x directory, run 'make uninstall' to remove all the=20
files
Scripted Method (only those distributions covered by scripted install)
----------------------------------------------------------------------
1. Login as root.
2. Enter the iANS-x.x.x/install/[distribution_name] directory. =20
3. Run 'UNINSTALL'.
4. The rest of the process is interactive. Follow the instructions=20
displayed on the console.
Prompts:
Restore member adapters to original role (stand alone).
Answer Yes for each adapter you wish to continue using standalone. =
This
configuration will be made using Intel's e100(0).o driver although you
may restore other drivers.
Removal of the ANS module from memory will not down the adapters =
running
in stand alone mode. The script will remove all files, scripts, and =
links
created except the /etc/ians/ians.conf.
Restarting the Network with the Original Configuration
For the new settings to take, you will have to restart the network
service either by rebooting the system or by running the network init =
script
with the restart parameter. /etc/rc.d/init.d/network restart
NOTE: =20
If you used the automatic INSTALL method for configuring ANS, note that =
lines
were added to the /etc/conf. modules file. These lines are not removed =
by
the UNINSTALL script. If you want to remove them, you must do so =
manually.
Modifying ADVANCED NETWORKING SERVICES Configuration
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
ANS configuration and topology may be changed, with a few limitations.
After commit, you may change priority and add or remove a team member
(but not the last one). You may not:
Change team mode.
Remove a team or a virtual adapter.
Remove the last member of an active team.
Teams, members adapters and virtual adapters may be added on the fly =
while
the service is running via the hot add and hot remove features (using =
the
same set of commands). (Not to be confused with Hot PCI Add/Remove.)
There are 2 methods of reconfiguring
- Semi-automatic - good for changing mode and/or moving members =
between
teams (can't create new teams plus all adapters must remain in teams).
- Manual reconfiguration (see below)
Semi-automatic Reconfiguration
------------------------------
1. Manually modify the ANS topology description file =
(/etc/ians/ians.conf).
2. Call the ANS initialization script with the restart parameter=20
/etc/rc.d/init.d/ans restart.
3. To reactivate, run the network service initialization script with =
the=20
restart parameter.=20
/etc/rc.d/init.d/network restart=20
=20
Manual Reconfiguration
----------------------
1. Take down the virtual adapter=20
ifconfig <vadapter_name> down
2. Remove the ians module
rmmod ians
3. Create or modify the ians topology file to match the new desired=20
topology (default location /etc/ians/ians.conf), or create script=20
containing a set of calls to ianscfg that will generate the desired =
topology.
4. Load the ians module
insmod ians
5. Run the script created in step 3, or run the command:
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 name format should be ifcfg-<vadapter-name>
* Sample file content:
DEVICE=3D<vadapter_name>
BOOTPROTO=3D"none"
ONBOOT=3D"yes"
IPADDR=3D"192.168.1.1"
NETMASK=3D"255.255.255.0"
8. If any unnecessary virtual adapter configuration file is left,=20
remove it or modify it.
9. For any adapter that is desired as stand alone connection, you may=20
continue to use the Intel base driver.
List of Available Commands:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
=20
Create a Team:
Create team(s);=20
ianscfg -a -t<team_name> [-M<mode>] [-V]
Use the -M flag to specify the teaming mode=20
(default AFT, others NONE | ALB | FEC | GEC | ). =20
Use the -V flag to specify a VLAN . =20
=20
Set/Change team mode: (only before commit)
ianscfg -C -t<team_name> -M <mode>
=20
Add team members:
ianscfg -a -t<team_name> -m<ethNN> [-p Y]
where Y can be none, primary or secondary, optional=20
(Only existing Intel Ethernet devices may be added to a team)
Add virtual adapter=20
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. =20
The name of the virtual adapter can be any except ethx but must=20
include instance number suffix.
Activate (commit) the team:
ianscfg -c<team_name>
After a team has been activated you can still add/remove =
members.
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 <vadap_name> <ip#> netmask <mask#> broadcast =
<broadcast>
Get Status:
ianscfg -s
Get help on the ianscfg utility - Type 'ianscfg'
To remove a member:
ianscfg -d -m<ethX>
Note: You cannot remove the last member of a team.
Don't specify the team here. =20
To Disable the Virtual Adapter:
ifconfig <virtual_adapter_name> down
To remove a team (only before commit):
ianscfg -d -t<team_name>
To remove a virtual adapter: (only before commit)
ianscfg -d -v<vadapter_name>
To disable a virtual adapter:
ifconfig <vadapter name> down
To Remove the ANS Module: (down all vadapters first)
rmmod iANS
To remove ANS files from your system: (after downing vadapters
and resetting the configuration)
make uninstall (from the iANS-x.x.x directory)
To Save the current configuration in a file: (only after commit)
ianscfg -w [-f <filename>]
(default is /etc/ians/ians.conf - editable text file)
To automatically program a topology configuration from a file:
ianscfg -r [-f <filename>]
(Again, the default file is /etc/ians/ians.conf)
Turn off probes
ianscfg -P -t<team_name> -d
Example File for Setting up AFT mode with VLANs: (2 PRO/100 adapters)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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=20
ianscfg -at team1 -v vadapt2 -i 15
=20
ianscfg -c team1
ianscfg -s
ifconfig vadapt1 143.185.254.10 netmask 255.255.255.0
ifconfig vadapt2 143.185.254.10 netmask 255.255.255.0
Troubleshooting
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
1. If an adapter has been running standalone with an assigned IP=20
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. (You still=20
bind the protocol to the physical adapter for standalone adapters.)
3. If you do not remove references to other possible base drivers in=20
the configurations, you risk multiple interfaces for adapters you
wish to use in the team with an unpredictable outcome.
4. If you receive an error message "module not loaded" during
configuration of the team, you need to start over. To do so type
./INSTALL veryclean all SMP=3D[0|1] MODVERSIONS=3D[0|1]
choose 0 or 1 for SMP and MODVERSIONS to match the configuration
of the current kernel tree.
Cause: This will occur when the target module doesn't match the
kernel version and 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'
then create the symbolic link (to the ans file) manually for each
run level desired with the command:
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. Jumbo Frames and ANS cannot be run simultaneously.
7. Mac Address changes of the virtual adapter are not supported.
Structure of the ANS build tree
* kernel dependant source files (src/*.[ch], src/lib/*.[ch])
* kernel independent precompiled object file (bin/iANS_core.o).
* Makefiles.
* Advanced Networking Services configuration utility (bin/ianscfg).
* installation, uninstall and configuration scripts
Distribution of files:
By default, the components are distributed as follows:
- /lib/modules/[KERNEL_VERSION]/net/ians.o
- /usr/sbin/ianscfg
- /usr/man/man1/ianscfg.1
conf.modules 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
License
=3D=3D=3D=3D=3D=3D=3D
Copyright (c) 1999 - 2001, Intel Corporation. All rights reserved.
Redistribution and use in source and binary forms, with or without=20
modification, are permitted provided that the following conditions
are met:
1. Redistribution's of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistribution's in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided
with the distribution.
3. Neither the name of Intel Corporation nor the names of its
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE. =20
------_=_NextPart_000_01C109EC.CF78B210--