Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of cloudstck@trick-solutions.com
 designates 216.249.106.136 as permitted sender)
In-Reply-To: <2a2401d02a27$b06080f0$112182d0$@trick-solutions.com>
References: <282e01d02a1b$50bb7350$f23259f0$@trick-solutions.com>
 <CAO+D_1wD5pqr8JVa9+=xXsSp0pXp7+bR4sFrEzysUhQ85GYihA@mail.gmail.com>
 <2a2401d02a27$b06080f0$112182d0$@trick-solutions.com>
User-Agent: Blue for Android
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----G5YB1WK1JS1WIAGVWLJ1XF9Y2CSE2K"
Subject: RE: Vlan issue with ACS 4.4 and XenServer 6.2
From: Matthew Midgett <cloudstck@trick-solutions.com.INVALID>
Date: Wed, 07 Jan 2015 15:13:06 -0500
To: users@cloudstack.apache.org
Message-ID: <32b931cc-6990-4390-9aa4-78bca2ea989f@email.bluemailapp.com>
Content-Transfer-Encoding: 7bit

------G5YB1WK1JS1WIAGVWLJ1XF9Y2CSE2K
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Does anyone else have an idea?


On Jan 6, 2015, 10:12 PM, at 10:12 PM, Matthew Midgett <cloudstck@trick-s=
olutions.com.INVALID> wrote:
>It is there because I can disable the zone, delete the VM and network.
>Use XenCenter to add a vlan of 501. Manually install 2 VM's on
>different hypervisors and ping both VM and the GW that on the router.
>This config tells me that 501 is configured correctly. The switch ports
>for the vlan 501 network are trunked. When ACS creates the vlan 501
>from the network config it doesn=E2=80=99t work correctly. When the VM a=
nd VR
>are on the same host it works just fine. When there not the Vlan isn 't
>working. It's strange. I can ping the GW from both VM's but can't ping
>the VM on the other hypervisor or the VR. If I migrate all the VM's and
>VR to the same hypervisor it works as expected.
>
>The vlan 501 on the router holds the GW address so if it wan't there I
>would 't be able to ping it.
>
>I have tried everything from new networking services to vlan's trunking
>and not trunking and just switchport with vlan. It doen't want to work.
>
>The vlan500 how ever is the console router and SSVM. I think that it
>works as expected but I havn't ssh into them to try. They are doing
>their job and I can have an public ip console and ssvm is downloading
>templates and moving VM templates from Sec storage to primary.
>
>Any more ideas?
>
>-----Original Message-----
>From: Ahmad Emneina [mailto:aemneina@gmail.com]=20
>Sent: Tuesday, January 06, 2015 9:11 PM
>To: dev@cloudstack.apache.org
>Subject: Re: Vlan issue with ACS 4.4 and XenServer 6.2
>
>Hey Matt, it sounds like you have a vlan trunking issue. Check the
>switch port configuration for the port(s) yout hypervisors are
>connected to, ensure that vlan is present.
>
>On Tue, Jan 6, 2015 at 5:43 PM, Matthew Midgett <
>cloudstck@trick-solutions.com.invalid> wrote:
>
>> In my test deployment I have 2 hypervisors with XenServer 6.2=20
>> installed. I am creating a private network with public Ips, so that=20
>> the VR is only used to hand out IPs and meta data. The vlan is 501,=20
>> and it has a range of 216.249.111.2-254. What happens is that when I=20
>> create new VM's and they spawn on the server with the VR cloud-init=20
>> works and it gets the password and the server is good. When is spawns
>
>> on the other hypervisor it can't connect to the VR and because of
>this=20
>> it doesn't get its meta data. What I do is quickly move the VR to the
>
>> other hypervisor, this allows it to get the meta data so I can login.
>
>> Once this is done I can login and ping the gateway for vlan 501 but=20
>> can't ping the other VM or the VR if it's not on the same hypervisor.
>
>> I know my trunks and vlans are correct and the interfaces that's
>being=20
>> assigned. To test this I shutdown the zone and deleted the network.
>> Then I removed Vlan501 from the XenServer's and created it manually
>on=20
>> the exact same nic as it was before. Then I added a ISO repo and=20
>> manually installed 2 vms manually assigning the public ip's. It works
>
>> as expected, I can ping the gateway and the other VM on the other=20
>> hypervisor. This was to prove my vlan config.
>>
>>
>>
>> What do I do?
>>
>>

------G5YB1WK1JS1WIAGVWLJ1XF9Y2CSE2K--