ifcfg-bonding(5) [suse man page]

IFCFG-BONDING(5)					       Network configuration						  IFCFG-BONDING(5)

NAME

       ifcfg-bonding - interface bonding configuration

SYNOPSIS

       /etc/sysconfig/network/ifcfg-bond*

Bonding Interfaces
       To setup a bonding interface you need a configuration file ifcfg-bond<X> with the usual network settings. But you must add additional vari-
       ables

       BONDING_MASTER
	      must be set to 'yes' to identify this interface as a bonding interface

       BONDING_SLAVE_<X>
	      here you specify the interface name representing the slave network interfaces.

       BONDING_MODULE_OPTS
	      contains bonding options. Here you can set interface timeouts or working modes ('mode=active-backup' for	backup	mode).	For  addi-
	      tional information take a look into the documentation mentioned at the bottom.  Note, that this options are not passed as parameters
	      to the bonding kernel module any more, but set via sysfs interface. This variable will be renamed in the feature.

       BONDING_SKIP_REMOVE_WORKAROUND
	      When set to "yes", a bonding interface will be not removed while ifdown any more to avoid problems, e.g. when some third party  ker-
	      nel module, such as Veritas 'llt' module, does not react correctly to the UNREGISTER event and does not remove its references to the
	      bonding interface causing all network related operation to stuck.

	      Note: the bonding options are not reverted when this option is enabled and it is required to either explicitly keep the old  options
	      and set them to their default setting on bonding configuration changes or to reboot.

Example
       Example for a bonding interface on eth0 and eth1 using the backup mode

       ifcfg-bond0
	  STARTMODE='onboot'
	  BOOTPROTO='static'
	  IPADDR='192.168.0.1/24'

	  BONDING_MASTER='yes'
	  BONDING_SLAVE_0='eth0'
	  BONDING_SLAVE_1='eth1'
	  BONDING_MODULE_OPTS='mode=active-backup miimon=100'

Additional Information
       For  additional	and  more  general  information  take  a look into /usr/src/linux/Documentation/networking/bonding.txt.  Maybe you need to
       install the kernel sources to get this additional documentation.

       The configuration of routes for this kind of interface does not differ from ordinary interfaces. See man routes for details.

BUGS

       Please report bugs at <http://www.suse.de/feedback>

AUTHOR

       Christian Zoz <zoz@suse.de> -- ifup script
       Wilken Gottwalt <wgottwalt@suse.de> -- ifcfg-bonding manual page

SEE ALSO

       ifcfg(5), ifup(8).

sysconfig							    April 2005							  IFCFG-BONDING(5)

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)