cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Neumann - AOD <>
Subject RE: CS VR on VMware
Date Wed, 16 Jul 2014 16:37:56 GMT
Hi Jayapal,

Thanks very much for the reply.

This is a custom network offering with a default egress policy of deny.

Slight correction from earlier, it appears the default iptable entries are identical between
Xen VR & VMware VR of the same network offering. Also I’ve tested and confirmed that
additional egress policies do successfully get applied to the iptables in both scenarios.

What I found though was that the source nat entry on the VMware VR was missing, so it seems
that isn’t being created for some reason.

I’ve also noticed that the VMware VR had 5 NICs, rather than the 3 NICs I was expecting
– 1xmgmt_network, 1xcloud.guest.916.10000.VDSNAME, 1xcloud.public.3004.10000.VDSNAME and
then an additional 2x in cloud.public.3004.0.VDSNAME which doesn’t seem right.

network_offerings table’s entry of the offering in question -
(just to recap though, the problem seems to present on VMware only, not Xen even though they
share the same network offering…)

the management server log output when creating a new network/VR is here -

The juicy bit seems to be this part (thought I’m not entirely sure what it means… ☺

2014-07-16 14:08:45,297 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-322:ctx-4b3460ba <<ESXHOST_IP>>)
Failed to find DomR VIF to associate/disassociate IP with.

2014-07-16 14:08:45,297 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-322:ctx-4b3460ba <<ESXHOST_IP>>)
Unexpected exception: Failed to find DomR VIF
to associate/disassociate IP with. will shortcut rest of IPAssoc commands Failed to find DomR VIF to associate/disassociate
IP with.






                at org.apache.cloudstack.managed.context.ManagedContextRunnable$

                at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$

                at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(

                at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(


                at java.util.concurrent.Executors$

                at java.util.concurrent.FutureTask$Sync.innerRun(


                at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(

                at java.util.concurrent.ScheduledThreadPoolExecutor$

                at java.util.concurrent.ThreadPoolExecutor.runWorker(

                at java.util.concurrent.ThreadPoolExecutor$


Thanks again,


-----Original Message-----
From: Jayapal Reddy Uradi []
Sent: Wednesday, 16 July 2014 6:36 PM
To: <>
Subject: Re: CS VR on VMware

Hi Eric,

Did you created network with default network offering or customer network offering ?

What is egress default policy value (true) in the network offering ?

Can you please send iptables rules on VR, MS server log after VR start and network_offerings,
network table output in



On 16-Jul-2014, at 3:48 PM, Eric Neumann - AOD <<>>


> Hi All,


> I’ve encountered a strange issue whereby egress firewall rules don’t seem to apply
to any CS VRs that are running on our VMware cluster, whereas any CS VRs running on our XenServer
cluster work as expected (these are in the same and only zone). Even more strangely, port
forwarding and ingress firewall rules do apply correctly in either scenario.


> Has anyone encountered anything similar or has any troubleshooting tips for this? I have
confirmed WAN connectivity, etc. from the VRs console and can see that there’s no matching
entry in the iptables.


> We are running Citrix CloudPlatform


> Any pointers would be greatly appreciated!

> Thanks,

> Eric


View raw message