ifenslave-2.6(8) [debian man page]

IFENSLAVE(8)						    BSD System Manager's Manual 					      IFENSLAVE(8)

NAME

     ifenslave -- Attach and detach slave network devices to a bonding device.

SYNOPSIS

     ifenslave [-acdfhuvV] [--all-interfaces] [--change-active] [--detach] [--force] [--help] [--usage] [--verbose] [--version] master slave ...

DESCRIPTION

     ifenslave is a tool to attach and detach slave network devices to a bonding device.  A bonding device will act like a normal Ethernet network
     device to the kernel, but will send out the packets via the slave devices using a simple round-robin scheduler.  This allows for simple load-
     balancing, identical to "channel bonding" or "trunking" techniques used in switches.

     The kernel must have support for bonding devices for ifenslave to be useful.

OPTIONS

     -a, --all-interfaces
	     Show information about all interfaces.

     -c, --change-active
	     Change active slave.

     -d, --detach
	     Removes slave interfaces from the bonding device.

     -f, --force
	     Force actions to be taken if one of the specified interfaces appears not to belong to an Ethernet device.

     -h, --help
	     Display a help message and exit.

     -u, --usage
	     Show usage information and exit.

     -v, --verbose
	     Print warning and debug messages.

     -V, --version
	     Show version information and exit.
     If not options are given, the default action will be to enslave interfaces.

EXAMPLE

     The following example shows how to setup a bonding device and enslave two real Ethernet devices to it:

     # modprobe bonding
     # ifconfig bond0 192.168.0.1 netmask 255.255.0.0
     # ifenslave bond0 eth0 eth1

AUTHOR

     ifenslave was originally written by Donald Becker <becker@cesdis.gsfc.nasa.gov>, and has since been updated by various kernel developers.

     This manual page was written by Guus Sliepen <guus@debian.org> for the Debian GNU/Linux system.

Debian GNU/Linux						   June 1, 2019 						  Debian GNU/Linux

BOND2TEAM(1)						  Bonding to Team conversion tool					      BOND2TEAM(1)

NAME

       bond2team -- Converts bonding configuration to team

SYNOPSIS

       bond2team [options]

DESCRIPTION

       bond2team is a tool to convert bonding options to team trying as much as possible to keep the original functionality.

       The resulting files are saved in a temporary directory using ifcfg style by default. In the case of converting an ifcfg file, it translates
       the bonding options to team, preserving all other options. In that case, it converts the respective slave ifcfg files to  team  port,  pre-
       serving	all  their other options too. In case of converting from given bonding options in the command line, the tool can use the specified
       ports as team ports.

OPTIONS

       --master <interface>
	      Specify  the  interface  name  or  ifcfg	file  to  convert.  If	the  interface	name  is  specified,  the  tool   will	 look	at
	      /etc/sysconfig/network-scripts/ for the respective ifcfg file.

       --rename <interface>
	      This is a convenient option to replace the original interface name by the specified name. For instance, if --master specifies bond0,
	      it is possible to use --rename team0 to change the final interface name to team0.

       --ifcfg
	      Set the output format to ifcfg config style. [default]

       --json Set the output format to JSON style. See teamd.conf(5) for further details.

       --bonding_opts '<bonding options>'
	      Specify the bonding options to be converted instead of reading them from the ifcfg file.

       --port <interface>
	      Set the specified interface as a team port.

       --configdir <directory>
	      Change the ifcfg configuration path from /etc/sysconfig/network-scripts to the specified <directory>.

       --outputdir <directory>
	      Set the output directory to <directory>.

       --stdout
	      Print the result to the screen instead of writing to files.

       --debug
	      Increase the debugging level.

       --quiet
	      Disallow any messages to be printed to console.

       --version
	      Print tool version to console and exit.

       --help Print help text to console and exit.

       --examples
	      Print common usage examples to console and exit.

EXAMPLES

       To convert the current 'bond0' ifcfg configuration to team ifcfg:

       # bond2team --master bond0

       To convert the current 'bond0' ifcfg configuration to team ifcfg renaming the interface name to 'team0'.  Caution : firewall  rules,  alias
       interfaces,  etc.,  that  might	be  tied to the original interface name can break after the renaming because the tool will only change the
       ifcfg file, nothing else.

       # bond2team --master bond0 --rename team0

       To convert given bonding parameters with ports without any ifcfg:

       # bond2team --bonding_opts 'mode=1 miimon=500 primary=eth1 primary_reselect=0' --port eth1 --port eth2 --port eth3 --port eth4

       For more examples, see the option --examples.

CAVEATS

       The tool will not convert any other configuration which might be tied to the current setup. For instance, firewall rules, alias interfaces,
       bridges, and so on.

AUTHOR

       Flavio Leitner is the original author of the tool.  Jiri Pirko is the original author and current maintainer of libteam.

SEE ALSO

       teamd(8), teamdctl(8), teamd.conf(5), teamnl(8)

libteam 							    2013-07-18							      BOND2TEAM(1)