RHEV-M network bonding

Latest response

Hi,

I recently setup ovirt with 4 nodes and two interfaces each... but as I am testing this for use with CloudForms, I have now moved on to RHEV. RHEV-M 3.4. I have setup the 4 nodes using RHEV-H ISO. I have added all the hosts, but then when I try to create the bonded network onto a VLAN using trunked ports doesn't work. This worked fine with ovirt. I used the GUI and dragged the rhevm network, which I created a new cluster and enabled vlan on the network and set my vlan... but it seems to only be able to use one interface. One seems to be used for communication and I cannot use it on the rhevm network...

I get the error message if I use the one that is currently being used to communicate with the host that it loses communication with the peer. If I try to do it all in one go and add both interfaces, to the rhevm network that the interface is already in use. My memory is pretty bad, but I'm pretty sure this worked fine (I did it on all four nodes) under ovirt. Not sure if I could have forgotten something, but this was something I was quite impressed with on ovirt - all I had to do was configure a single interface and set the VLAN on it on the hypervisor itself and connect it to the manager, and then I could configure the bonding by just dragging and dropping the interfaces and networks - but I have tried on several nodes now and the same thing always happens. Any idea what I might be forgetting or doing wrong?

Thanks
Bill

wd
Log in to join the conversation

Responses

wd Active Contributor 232 points
22 October 2014 8:18 AM

hmm, that was a lot of faffing... I added the unused interface to the rhevm network. That got a dhcp address, I changed the address of eth0 to a temp address, I removed the host and then added the host using the temp address - hmm, getting mixed up now, long and short of it, I eventually got the static address I wanted to use on the rhevm network with eth1 and connected to the rhev-m server.. then downed the eth0 address and then I could add it and make them bonded. And I had to add and remove the hosts as I shuffled the IP addresses around. Why did that just work in ovirt? I thought it was pretty slick, but this was a pain, now I have to do it 3 more times...

st Active Contributor 207 points
19 November 2014 9:41 PM

Hi William

Not sure if you got it fixed or if I understand you correctly.
We've also recently set up a bunch of RHEV-H using RHEV-M 3.4.
The RHEV-M network needs a static IP as well as the migration network, if you decided to have a dedicated one.
What we have done is 2 NICs for RHEV-M network, bond type=1. However configuring the bond on the RHEV-H caused a few problems. So instead i put the static address on 1 single NIC. When added to RHEV-M I then create the bond simply by right clik on eth'x', I configured in RHEV-H, and choose bond with eth'y'
Thats works without any problems.

wd Active Contributor 232 points
20 November 2014 6:28 AM

Hi Stig,

I did get it working... it was kind of stupid :-( on my first host, I accidentally configured eth1 manually to get the node talking to the manager instead of eth0. THen when I tried to configure eth1 as I had done in the past using the manager, it said it was already in use and I didn't realise that it actually was, becuase I had configured it to connect to the mgmt network... so a lot of faffing around and I found my mistake and figured out it work well! Thanks!

DM Newbie 16 points
9 December 2014 2:11 PM

Hi .. On RHEV-H (not connected to RHEV-M) , have you managed to configure bond0 and bond1. On my server I have 4 x 1GB NIC's and want to configure bond0 (eth0 + eth1 ) and bond1 (eth2 + eth3) , but I am unable to do that , in RHEV-H under Networks am ONLY able to configure bond0 , and when try to configure bond1 , it resets bond0 (clears all the settings) , so in simple at any given time either I can create bond0 or bond1 and and not both, why ????

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.