Use the 2 NIC of my server for manage network traffic of VMs

[nicothebrush]

Hello,
I wonder if is correct, for use the 2 NICs, create 2 bridge, vmbr0 that use eth0 and vmbr1 that use eth1, my need is shaping the traffic of the VM hosted in my server (so 2 server could use vmbr0 and the other 2 use vmbr1).
I previously asked for create a bond but in my network I don't have a manage switch (no LACD) so I don't think is the best solution...
Thanks

 

[Nemesiz]

You can create bond active-backup mode or you can do as you described.

Another suggestion is to use one NIC for management and another for VM

 

[nicothebrush]

Thanks for (very fast) reply Nemesiz,
I try to do bond0 (eth0 eth1) and vmbr0 on bond0 but I want to "force" some server (production server) to use particular NIC (not share a sort of "folks" NIC), that's why I think about 2 (or more) bridge.
But, if I choose 2 bridge, it's important what IP address I give to them (obv. except for administration connections), I want to use 2 IP on the same LAN, ex.:
vmbr0 (on eth0) 192.168.1.10 << 1 VM (192.168.1.99)
vmbr1 (on eth1) 192.168.1.11 << 3 VM (192.168.1.100, 192.168.1.101, 192.168.1.102)
Or could create some problems?

 

[Nemesiz]

Your server will use only private subnets or you have read IP ?

 

[nicothebrush]

I don't know what "read IP" means, you mean public IP address? Currently my "one or more" server will stay in a LAN for manage it/them

 

[Nemesiz]

Then I suggest you to try

mbr0 (on eth0) 192.168.1.10 << 1 VM (192.168.1.99)
vmbr1 (on eth1) 192.168.1.11 << 3 VM (192.168.1.100, 192.168.1.101, 192.168.1.102)

Maybe it will be reachable inside server x.99 x.100.... or maybe it will go through switch.

 

[nicothebrush]

You doubt is about .99 that "maybe" doesn't see .100 or it has worse performance because it depend on switch for transfer packets?

PS: I try to make a LAN test now and post results

 

[nicothebrush]

At a first sight seems that VMs on vmbr0 ping all network except VMs in vmbr1 and "vice versa"

 

[Nemesiz]

If you can run tcpdump and try to ping.

all at the same time on separate consoles

tcpdump -ni eth0
tcpdump -ni eth1
tcpdump -ni vmbr0
tcpdump -ni vmbr1

Need to determine where the packet stops.

 

[nicothebrush]

Nemesiz .. my fault... it depends on win firewall enabled on the 2 PC, disabled it all works (both pings)
Thanks again