External IP list not showing in vCloud VM list view

Posted by on May 24, 2013 in vCloud, VMware | 4 comments

I spent a few days with a customer this week and we noticed the following strange behavior. I built a multi-VM vApp to be able to deploy their application which consisted of 6 VMs. This vApp will allow them to deploy multiple copies of the app for testing and training. To make sure the application performs properly we needed to use consistent IPs on the VMs within the vApp. So I set static IPs and I configured the vApp to be fenced. This way when people deploy the vApp it will be protected by a vShield Edge device using NAT to hide the static IPs within the vApp.

Now onto what we noticed. Once the vApp deploys the IP addresses of the VM should show up as the static ones defined. Then each VM should also be assigned a NAT address which shows up in the External IP column in vCloud. You can see from the screen shot below. The view shown below is when I clicked on the vApp and then clicked onto he Virtual Machine tab to list all the VMs contained in the vApp. This view shows all of the IP address properly.


Now for the strange behavior. If you take a look at the VM list within the Organization in vCloud you can locate your VMs. But from the image below you will notice that the External IP column is empty. For some reason this display does not populate the External address column. Very strange since the column is there by default and why would it be there if you were not meant to see the details. We noticed this because after deploying we needed to locate our external IPs so that we could connect to the vApp. At first I thought the vApp might not have deployed properly, but after further investigation noticed that the addressed showed up when viewing the vApp.


Sure this is not enough to ruin your day, but I do hope that VMware fixes this bug soon. Little things like this hurts the perception of the product when customers are using.


About Brian Suhr

Brian is a VCDX5-DCV and a Sr. Tech Marketing Engineer at Nutanix and owner of this website. He is active in the VMware community and helps lead the Chicago VMUG group. Specializing in VDI and Cloud project designs. Awarded VMware vExpert status 6 years for 2016 - 2011. VCP3, VCP5, VCP5-Iaas, VCP-Cloud, VCAP-DTD, VCAP5-DCD, VCAP5-DCA, VCA-DT, VCP5-DT, Cisco UCS Design


  1. I’ve been complaining about this since VCD 1.0 and they still haven’t fixed it. I even talked with their engineers about it in July of last year. It’s a huge pain to our users as they tend to go to the VM’s view A LOT.

    • This seems like such a small easy fix, but it confuses me how it can still exist after several versions. Sucks to have a customer ask and you have to explain that its this way.

      • I know what you mean. I have 250 internal users and almost all of them have complained about it, even though I warned them during training. At this point I wish it could be hidden some how.

  2. Also, if the user only has the standard “vApp User” role they can stop and delete VM’s within the vApp from that view. If they stop/delete the last VM they cannot add a new VM to it or stop the vApp. I’ve had to write a script to look for these vApps and clean them up. PITA

Leave a Comment

Your email address will not be published. Required fields are marked *