Hello FrancisM,
Thursday, April 7, 2016, 11:20:20 AM, you wrote:
After trying the method using the 'nmcli' its the same error result as what I encountered in using the 'nmtui' by the way after configuring then check it in the nmtui its the same configuration as what I have done earlier.
You mast use or NetworkManager.service or network.service, not both
systemctl disable network.service systemctl enable NetworkManager.service
nmcli connection show
[root@server network-scripts]# systemctl status network.service -l ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code) since Tue 2015-04-07 17:19:00 SGT; 1min 13s ago Docs: man:systemd-sysv-generator(8) Process: 48732 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS) Process: 49302 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Apr 07 17:17:28 server network[49302]: [ OK ] Apr 07 17:17:29 server network[49302]: Bringing up interface team1_slave_enp5s0f1: Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/69) Apr 07 17:17:29 server network[49302]: [ OK ] Apr 07 17:19:00 server network[49302]: *Bringing up interface vlan247: Error: Timeout 90 sec expired.* Apr 07 17:19:00 server network[49302]: *[FAILED]* Apr 07 17:19:00 server network[49302]: Bringing up interface br247: [ OK ] Apr 07 17:19:00 server systemd[1]: network.service: control process exited, code=exited status=1 Apr 07 17:19:00 server systemd[1]: Failed to start LSB: Bring up/down networking. Apr 07 17:19:00 server systemd[1]: Unit network.service entered failed state. Apr 07 17:19:00 server systemd[1]: network.service failed. [root@server network-scripts]#
I will try to use other configuration on this bridge. Does it matter if I use TEAMING and not BONDING on this bridging configuration because the two nic card that is trunk is configured as TEAMING in my CentOS7
I am using teaming +bridge +vlan. All works as expected/