차차 Bonding을 대체하게될 Teaming을 사용해보자.
# nmcli device status
# nmcli connection show
----------------------------------
# nmcli con add type team con-name CNAME ifname INAME [config JSON]
Where CNAME will be the name used to refer the connection ,INAME will be the interface name and JSON (JavaScript Object Notation) specifies the runner to be used. JSON has the following syntax:
'{"runner":{"name":"METHOD"}}'
where METHOD is one of the following: broadcast, activebackup, roundrobin, loadbalance or lacp.
----------------------------------
Master 장치 생성
# nmcli connection add con-name team0 type team ifname team0 config '{"runner":{"name":"loadbalance"}}'’
Slave 장치 추가
# nmcli connection add con-name team0-sl1 type team-slave ifname eth1 master team0
# nmcli connection add con-name team0-sl2 type team-slave ifname eth2 master team0
# nmcli connection modify team0 ipv4.addresses 192.168.18.10/24 ipv4.method manual
상태 확인 및 테스트
# teamdctl team0 state
# nmcli connection down team0-sl1
# teamdctl team0 state
# ifup eth1
http://vinzlinux.blogspot.kr/2014/12/configuring-network-teaming-using-nmcli.html
http://myredhatcertification.com/2015/02/03/rhel7-network-configuration/
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Network_Bonding_Using_the_Command_Line_Interface.html#sec-Create_a_Channel_Bonding_Interface
