RHEV 3.4 and bridging
Hello, I am needing assistance in troubleshooting a new "Test" setup of RHEV.
Everything appears to be setup and working properly with one problem. I cannot get out to my main network on a Guest VM. This VM does get a valid DHCP ip address from my DHCP server which is location in my main lab.
From the guest VM I can ping the Host that it is running on, but that is all.
The host is a RHEV-h Hypervisor and not RHEL running a hypervisor. I see in the setup guides that the Bridge is created automatically when the hypervisor is connected to RHEV-m. However It appears that I cannot get to a commandline to verify this in the hypervisor.
I have tried creating several different logical networks and have not been able to get any configuration to work.
Currently I only have the rhevm management server setup. Vm network is checked.
Can anyone offer guidance on this matter? I am sure I am overlooking something simple.
Please ask for more detail if I was not clear enough.
Responses
Running RHEL 6.5, HP c7000, 04 blades, HP Virtual Connect, same problem...
Another error: if call the logical networks only with number: 10, 20, 30, etc, and use "tcpdump -nnei 20" the output say "... listen on bond0.89". In my case the blade has 08 nic:
eth6+eth7=bond0, mode 5 --> 20
eth0+eth1=bond2, mode 5 --> TRUNK
eth3+eth4=bond3, mode 2 --> rhevm
eth2+eth5=bond4, mode 5 --> backup
20 is the network for blade and for vm's, 192.168.33.0/24, untagged, the other networks don't care....
new vm's using network 20 only see the blade (192.168.33.203), don't see gateway....
any idea ? libvirt ?
if use the workaround with "etables...." work fine, but if reboot vm lost connections, if migrate simply don't work....
thanks in advance for any help !!
Red Hat
Guru
7257 points
Mode 5 bonding does not work with virtual machines, as it can perform MAC rewriting when traffic is load-balanced out a non-primary slave:
We have several known issues where SR-IOV switches, or external switches, reflect broadcast traffic back due to firmware bugs or misconfiguration:
Correct, the initial bridge with the rhevm default network is automatic. Make sure you are not trying to do vlan tagging because it is documented that it will not work on that default virtual network. I have setup additional networks with vlan tagging.
You should be able to console or ssh into the hypervisor.
With limited details this sounds like a switch configuration issue, or network issue more than a rhev issue.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.