Hi Somesh

I have made all the guest vlan range in the trunk port. Which is working
when i migrate the vm along with my VR to hypervisor 2.

Right now my VR is running on hypervisor 1 and i am trying to migrate one
of the guest from hypervisor 1 to hypervisor 2. Migration is successful but
i could not able to reach out to the guest vm.

I am confirming the network outage by doing telnet to ssh port on this
guest vm. Connection time out.

Please help me to fix this issue.

Thx
AR
On 24 Dec 2014 22:37, "Somesh Naidu" <somesh.na...@citrix.com> wrote:

> > my VR is running on node001 which is not reachable from node002 via
> 169.254.0.0 network.
>
> That's not supposed to work, link local networks are local context (host
> wide) only.
>
> > also when I do brctl show in node001 I could see there are so many
> > interfaces are created but the same interfaces are not available in
> node002.
>
> Don't think this is relevant.
>
> What you need to check is if the guests that are not accessible are able
> to ping their default gateway, the VR that is. If not, did you trunk the
> zone vlan ids on the corresponding ports on the switch connecting the two
> hosts?
>
> -----Original Message-----
> From: Abdul Rasool [mailto:rasool...@gmail.com]
> Sent: Wednesday, December 24, 2014 8:58 AM
> To: cloudstack-us...@incubator.apache.org; users@cloudstack.apache.org
> Subject: VR is not able to ping from node002
>
> Hi,
>
> In my setup I have 2 computing nodes both are same HW platform, in that I
> have created multiple guest VMs which is working fine in first node. when I
> migrate any guest VM to second node I am loosing connection to the guest
> VM. when I start debugging the issue I found my VR is running on node001
> which is not reachable from node002 via  169.254.0.0 network.
>
> also when I do brctl show in node001 I could see there are so many
> interfaces are created but the same interfaces are not available in
> node002.
>
> could some one help me why the virtual bridge interfaces are not created in
> my node002 machine ?
>
> Thanks
> AR
>

Reply via email to