issue with External Nat-routed Organization

[zpeewee]

Hello,

I have created an External NAT-Routed Organization Network on a VLAN backed pool. A vm has been attached to it and NAT is configured correctly.

Now, i am experiencing the following issue :

When the vshield edge service (vse-134...) runs on the same host as the virtual machine, natting is ok. When the vshield edge service and the vm are on different hosts, the natting does not work anymore and the vm is unreachable from outside.

This is not a normal behavior i guess but i can't fix it.

May you can help me.

Thanks

[zpeewee]

Issue has been fixed.

My cluster is split over 2 datacenters and the vlans are published on both datacenter but the interconnect between them was not done. Now it is fixed

[depping]

As far as I know geographically dispersed clusters are not supported when it comes to vCD.

Duncan

VMware Communities User Moderator | VCDX

-

---

Now available: <a href="http://www.amazon.com/gp/product/1439263450?ie=UTF8&tag=yellowbricks-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=1439263450">Paper - vSphere 4.0 Quick Start Guide (via amazon.com)</a> | <a href="http://www.lulu.com/product/download/vsphere-40-quick-start-guide/6169778">PDF (via lulu.com)</a>

Blogging: http://www.yellow-bricks.com | Twitter: http://www.twitter.com/DuncanYB

[troyprouty]

Hi Duncan,

I just stumbled onto this post and was hoping you could clarify your statement around geographically dispursed clusters not being supported in vCD?  Is there any sort of best practice guidelines around deploying a vCloud environment across multiple geo's?  Whether that means completely seperate vCloud instances or just seperate cells and resources clusters, etc.  If it's not supported at this time I understand that, but I'm looking for VMware's view on the best way to work around it while still using vCloud.

Thanks,

Troy