Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of Alex.Huang@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Alex Huang <Alex.Huang@citrix.com>
To: "cloudstack-users@incubator.apache.org"
	<cloudstack-users@incubator.apache.org>
Date: Tue, 23 Oct 2012 10:58:49 -0700
Subject: RE: Cloudstack mixing Vlan and creating a big mess...
Thread-Topic: Cloudstack mixing Vlan and creating a big mess...
Thread-Index: Ac2w/3GnTEqUbYERTU2Q01GbbZmLpQASFw0g
Message-ID: 
 <B1DF26ECC0458748AC97CECE2DA98D41012FA089D7C5@SJCPMAILBOX01.citrite.net>
References: 
 <CADq5e0xjx2t+XtqEyx7BBjzDauujXrx_XjrmenouJkwy6o1M5A@mail.gmail.com>
In-Reply-To: 
 <CADq5e0xjx2t+XtqEyx7BBjzDauujXrx_XjrmenouJkwy6o1M5A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Arnaud,

Can you provide more information?=20

What are the networks and the network  configurations you are deploying the=
 VM into?  How did you setup your zone?  Is this 3.x, 4.x, 2.x?

--Alex

> -----Original Message-----
> From: Arnaud Gaillard [mailto:arnaud.gaillard@xtendsys.net]
> Sent: Tuesday, October 23, 2012 2:18 AM
> To: cloudstack-users@incubator.apache.org
> Subject: Cloudstack mixing Vlan and creating a big mess...
>=20
> Hello,
>=20
> We are currently facing a critical issue.
>=20
> Cloudstack is currently mixing vlan for VM migration or creation bringing
> down part of our network.
>=20
> We are currently using multiple guest network with different Vlan for
> segmentation.
>=20
> Here is a quick exemple (extract from the cloud agent log in debug mode):
>=20
> "nics":[{"deviceId":0,"networkRateMbps":10000,"defaultNic":true,"ip":"10.=
1
> 28.8.3","netmask":"255.255.240.0","gateway":"10.128.15.254","mac":"06:7d:=
4
> 6:00:16:50","dns1":"172.16.11.10","broadcastType":"Vlan","type":"Guest","=
b
> roadcastUri":"vlan://120","isolationUri":"vlan://811","isSecurityGroupEna=
ble
> d":false,"name":"cloudVirBrPriv1"}
> {"deviceId":1,"networkRateMbps":10000,"defaultNic":false,"ip":"172.20.2.4=
",
> "netmask":"255.255.240.0","gateway":"172.20.15.254","mac":"06:1a:a2:00:14=
:
> 50","dns1":"172.16.11.10","broadcastType":"Vlan","type":"Guest","broadcas
> tUri":"vlan://811","isolationUri":"vlan://120","isSecurityGroupEnabled":f=
alse,
> "name":"cloudVirBr120"},{"deviceId":2,"networkRateMbps":10000,"defaultN
> ic":false,"ip":"10.192.6.3","netmask":"255.255.248.0","gateway":"10.192.7=
.25
> 4","mac":"06:07:8e:00:11:52","dns1":"172.16.11.10","broadcastType":"Vlan"=
,"
> type":"Guest","broadcastUri":"vlan://400","isolationUri":"vlan://400","is=
Secu
> rityGroupEnabled":false,"name":"cloudVirBr400"}]},"wait":0}}]
> }
>=20
>=20
> As you can see broadcastUri and isolationUri are not in the same Vlan. Th=
e
> Vlan120 is only present on another physical interface (CloudVirBr120), an=
d
> must not be present on this interface. In order for this to work broadcas=
t and
> isolation must both be in the 811 vlan. The same problem arise from
> deviceid1 where the mix is inverted....
>=20
>=20
> From where does cloudstack get the value for Broadcast and Isolation URI?
> How can such a mix/mess happend?
>=20
> Thanks for your help!
>=20
> Arnaud