ember 2017 00:14
An: dev@cloudstack.apache.org
Betreff: Re: 4.9 / 4.10 KVM + openvswitch + vpc + static nat /
secondary ip on eth2?
Hi Frank,
Great analysis, but what can we do now? Is there a workaround or who
can fix this?
CLOUDSTACK-10127
Greetings
Sven
-Ursprüngliche Nachricht-
Von: Vogel, Sven [mailto:sven.vo...@kupper-computer.com]
Gesendet: Mittwoch, 1. November 2017 00:14
An: dev@cloudstack.apache.org
Betreff: Re: 4.9 / 4.10 KVM + openvswitch + vpc + static na
@cloudstack.apache.org
Betreff: Re: 4.9 / 4.10 KVM + openvswitch + vpc + static nat / secondary ip on
eth2?
Hi Frank,
Great analysis, but what can we do now? Is there a workaround or who can fix
this?
Greetings
Sven
Am 31.10.2017 um 22:41 schrieb Frank Maximus
<frank.maxi...@nuagenetworks.
Hi Frank,
Great analysis, but what can we do now? Is there a workaround or who can fix
this?
Greetings
Sven
Am 31.10.2017 um 22:41 schrieb Frank Maximus
>:
That seems to be a bug in the lookup of the device number,
That seems to be a bug in the lookup of the device number, in case of
openvswitch.
The config clearly sets device to eth2, while it should be eth1.
More specifically:
in LibvirtComputingResource.prepareNetworkElementCommand()
The broadcastUriToNicNum map is filled depending on the VR nics.
In
Hi Frank,
root@r-29-VM:~# cat /etc/cloudstack/ips.json
{
"eth0": [
{
"add": true,
"broadcast": "169.254.255.255",
"cidr": "169.254.3.129/16",
"device": "eth0",
"gateway": "None",
"netmask": "255.255.0.0",
"network": "169.254.0.0/16",
I think that the bug you mentioned might not be related.
Could you please send the content of the file /etc/cloudstack/ips.json on
the VR.
That might provide useful information.
Kind regards,
Frank
On Tue, 31 Oct 2017 15:23 Vogel, Sven,
wrote:
> Hi Devs,
>
> i
Hi Devs,
i have the following problem.
When I look this jira ticket I see no solution.
https://issues.apache.org/jira/browse/CLOUDSTACK-6801 but I think the problem
is not solved correctly.
1. KVM
2. Bridges
bond with two interfaces and trunk (0,129,180,100-1500) to cloudbr0