[CentOS] KVM Virtualization Network VLAN CentOS7

On Thu, Apr 7, 2016 at 1:51 PM, FrancisM <francis at mytechrepublic.com> wrote:

>
>
> On Thu, Apr 7, 2016 at 1:26 PM, Subscriber <ml-lists at agoris.net.ua> wrote:
>
>> Hello FrancisM,
>>
>> Thursday, April 7, 2016, 8:03:38 AM, you wrote:
>>
>>
>> > I tried last night and it seems like the vlans that I created is
>> failing to
>> > bring-up. So this is what Im doing
>>
>> > in my DATA trunk port at my HomeLab Im doing this
>>
>> > 2 port configured for teaming1 (set as link only port) -> Create Bridge
>> > (br0 port) on top of the teaming1 -> create slave vlan10,20,30,40 and
>> the
>> > parent is br0. Am I doing this correctly? Thanks
>>
>> not exactly.
>>
>> nmcli connection add con-name br10 ifname br10 type bridge stp no
>> nmcli connection down br10
>> nmcli connection edit br10
>> set ipv4.method disabled
>> set ipv6.method ignore
>> save
>> quit
>> nmcli connection up br10
>>
>> nmcli  connection  add  con-name  vlan10  ifname  vlan10 type vlan dev
>> teaming1 id 10
>> nmcli connection down vlan10
>> nmcli connection edit vlan10
>> set connection.master br10
>> set connection.slave-type bridge
>> verify fix
>> save
>> exit
>> nmcli connection up vlan10
>>
>> similarly for br20+vlan20, br30+vlan30, br40+vlan40
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS at centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
> Thanks for providing the command I will definitely try this method.
>
>
Hi,

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.

[root at 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 at 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