bond2team(1) [centos man page]
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)
Check Out this Related Man Page
IFSERVICES(5) Network configuration IFSERVICES(5) NAME
ifservices-* - control network services with ifup/down SYNOPSIS
/etc/sysconfig/network/ifservices-<configuration_name>/ DESCRIPTION
The directory /etc/sysconfig/network/ifservices-<configuration_name>/ is read by the script /etc/sysconfig/network/scripts/ifup-services which starts and stops system services when an interface is set up/down. ifup-services is used by /sbin/ifup, which is the command line user interface for setting up network interfaces. This is useful if you don't have a permanent network connection. If you sometimes boot without network and plug in the network cable later you can add links to system services in this directory. These services will then be started with ifup and stopped with ifdown. The configuration name used for ifservices-* should match exactly the configuration name of the ifcfg-* file for the interface. For the usage with NetworkManager (where you don't necessarily need a ifcfg-* file) you can also use /etc/sysconfig/network/ifser- vices-<interface>-<essid>/ (for wlan interfaces) or if that does not exist /etc/sysconfig/network/ifservices-<interface>/. As a final fallback /etc/sysconfig/network/ifservices/ is checked as well. If NetworkManager is active services will be stopped after the interface is down. The links in this directory are equal to the links in the runlevel directories /etc/init.d/rc*.d/ They have to point to service start scripts which are usually in /etc/init.d/. Links starting with 'S' are start links, which are called in alphabetical order after ifup has set up the interface. Links starting with 'K' are kill links which are called before ifdown takes down the interface. See also section Sequencing Directories in boot (7). EXAMPLE
In this example we use an interface with MAC address 00:de:ad:be:af:00. This interface is not always physically connected. As soon as you plug in the cable ypbind and autofs should be started. When you pull the cable they should be stopped. This can be reached with: in file /etc/sysconfig/network/ifcfg-eth-id-00:de:ad:be:af:00 ... STARTMODE=ifplugd ... in dir /etc/sysconfig/network/ifservices-eth-id-00:de:ad:be:af:00/ S10portmap -> /etc/init.d/portmap S20ypbind -> /etc/init.d/ypbind S30autofs -> /etc/init.d/autofs S20autofs -> /etc/init.d/autofs K30ypbind -> /etc/init.d/ypbind Now you have to disable the start of this services at boot time chkconfig ypbind off chkconfig autofs off Notes: You may call scripts/create-ifservices-directory [<interface_name>] to create a directory with the links from this example. This will cre- ate the directory ifservices-<interface_name> or if no interface name was given ifservices-template. Maybe you have to add also variable IFPLUGD_PRIORITY. For details about startmode ifplugd read ifup (8). The service portmap had to be added because ypbind needs it. This service is still started at boot time because it does not need an active network connection. But ypbind may now be started earlier as usual. Therefore we make sure that portmap is started before. Starting an already running service again does not affect the service. SEE ALSO
ifup(8), ifcfg(5). AUTHOR
Christian Zoz <zoz@suse.de> sysconfig February 2005 IFSERVICES(5)