You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Kevin Landreth <cr...@gmail.com> on 2012/05/09 21:56:50 UTC

[xenserver6 networking] dual IP routes not supported for host machine

Emailing this to the list as per the IRC conversation.

I was having issues two nics and the default route which wasn't used
for cloudstack management.

I am using advanced networking so this "patch" works for me.  I don't
know exactly why the
conditional is in there or even why the gateway is needed, but
removing it has caused no ill
effects so far in my testing.

I submitted the following bug report:
http://bugs.cloudstack.org/browse/CS-14839 for tracking.


diff --git a/scripts/vm/hypervisor/xenserver/network_info.sh
b/scripts/vm/hypervisor/xenserver/network_info.sh
index 12d4e79..c6beccd 100755
--- a/scripts/vm/hypervisor/xenserver/network_info.sh
+++ b/scripts/vm/hypervisor/xenserver/network_info.sh
@@ -45,10 +45,7 @@ ipaddr=$1

 device=$(ip addr | grep $1 | head -1 | awk '{print $NF}')
 defaultdev=$(ip route | grep default | awk '{print $NF}')
-if [ "$device" == "$defaultdev" ]
-then
-  gateway=$(ip route | grep default | awk '{print $3}')
-fi
+gateway=$(ip route | grep default | awk '{print $3}')

 [ -n "$gflag" ] && echo $gateway && exit 0

Re: [xenserver6 networking] dual IP routes not supported for host machine

Posted by Kevin Landreth <cr...@gmail.com>.
Thanks for the response, here are some more details about my testing.

* two routes, a default for internet bound traffic and a seperate one
for "management" traffic.
* assign a /27 or /26 of 10.x.x.x address per segment.
** Each segment must cross a router.
** There is no proxy ARP.
*secondary storage on a separate segment
* local disks for primary storage (for the moment)
* enabled swift which is on yet another network segment.

Adding and activating the host were the primary problems, this
hack/patch fixes that problem.

I had an issue as well with connectivity, but to get the SSVM and
Console proxy apply the appropriate route, I set the global config
management.network.cidr to 10.0.0.0/8 which lets my management network
handle the routing.  I feel in more flat topologies this will not be
an issue.

On Wed, May 9, 2012 at 3:19 PM, Charles Russell
<Ch...@kisinc.net> wrote:
>
> How will Cloudstack management be able to function across datacenters without a gateway?
>
> I had a similar issue where I was inclined to do something similar, but instead I further separated the network because I realized that the one interface that must have a gateway is the management.   My example was that I had my Cloudstack Management my Cloudstack-Storage subnets contained in the same vlan-id and in the same subnet.
>
> Ex:  Both vlan id 1500 with a 172.16.16/20
>
> 172.16.25/20 was for cloudstack management
> 172.16.28/20 was for cloudstack storage
>
> While it worked in the confines of the cloudstack rules to stand up the zone, it broke because the servers would mix up which NIC to source the traffic from which broke my secondary storage and snapshots.  So I would end up traffic going different ways.
>
> To fix, I stood up separate vlan and subnet for storage traffic.
>
>
>
> -----Original Message-----
> From: Kevin Landreth [mailto:crackerjackmack@gmail.com]
> Sent: Wednesday, May 09, 2012 3:57 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: [xenserver6 networking] dual IP routes not supported for host machine
>
> Emailing this to the list as per the IRC conversation.
>
> I was having issues two nics and the default route which wasn't used for cloudstack management.
>
> I am using advanced networking so this "patch" works for me.  I don't know exactly why the conditional is in there or even why the gateway is needed, but removing it has caused no ill effects so far in my testing.
>
> I submitted the following bug report:
> http://bugs.cloudstack.org/browse/CS-14839 for tracking.
>
>
> diff --git a/scripts/vm/hypervisor/xenserver/network_info.sh
> b/scripts/vm/hypervisor/xenserver/network_info.sh
> index 12d4e79..c6beccd 100755
> --- a/scripts/vm/hypervisor/xenserver/network_info.sh
> +++ b/scripts/vm/hypervisor/xenserver/network_info.sh
> @@ -45,10 +45,7 @@ ipaddr=$1
>
>  device=$(ip addr | grep $1 | head -1 | awk '{print $NF}')  defaultdev=$(ip route | grep default | awk '{print $NF}') -if [ "$device" == "$defaultdev" ] -then
> -  gateway=$(ip route | grep default | awk '{print $3}') -fi
> +gateway=$(ip route | grep default | awk '{print $3}')
>
>  [ -n "$gflag" ] && echo $gateway && exit 0

RE: [xenserver6 networking] dual IP routes not supported for host machine

Posted by Charles Russell <Ch...@kisinc.net>.
How will Cloudstack management be able to function across datacenters without a gateway?

I had a similar issue where I was inclined to do something similar, but instead I further separated the network because I realized that the one interface that must have a gateway is the management.   My example was that I had my Cloudstack Management my Cloudstack-Storage subnets contained in the same vlan-id and in the same subnet.

Ex:  Both vlan id 1500 with a 172.16.16/20

172.16.25/20 was for cloudstack management
172.16.28/20 was for cloudstack storage

While it worked in the confines of the cloudstack rules to stand up the zone, it broke because the servers would mix up which NIC to source the traffic from which broke my secondary storage and snapshots.  So I would end up traffic going different ways.

To fix, I stood up separate vlan and subnet for storage traffic.  



-----Original Message-----
From: Kevin Landreth [mailto:crackerjackmack@gmail.com] 
Sent: Wednesday, May 09, 2012 3:57 PM
To: cloudstack-dev@incubator.apache.org
Subject: [xenserver6 networking] dual IP routes not supported for host machine

Emailing this to the list as per the IRC conversation.

I was having issues two nics and the default route which wasn't used for cloudstack management.

I am using advanced networking so this "patch" works for me.  I don't know exactly why the conditional is in there or even why the gateway is needed, but removing it has caused no ill effects so far in my testing.

I submitted the following bug report:
http://bugs.cloudstack.org/browse/CS-14839 for tracking.


diff --git a/scripts/vm/hypervisor/xenserver/network_info.sh
b/scripts/vm/hypervisor/xenserver/network_info.sh
index 12d4e79..c6beccd 100755
--- a/scripts/vm/hypervisor/xenserver/network_info.sh
+++ b/scripts/vm/hypervisor/xenserver/network_info.sh
@@ -45,10 +45,7 @@ ipaddr=$1

 device=$(ip addr | grep $1 | head -1 | awk '{print $NF}')  defaultdev=$(ip route | grep default | awk '{print $NF}') -if [ "$device" == "$defaultdev" ] -then
-  gateway=$(ip route | grep default | awk '{print $3}') -fi
+gateway=$(ip route | grep default | awk '{print $3}')

 [ -n "$gflag" ] && echo $gateway && exit 0