Getting duplicate "External IP" addresses assigned...

hennish · ‎09-12-2012

Hi. We are having some problems with the IP Allocation function in one of our Organization Networks:

The "External IP" (NAT) addresses are not always being released even though we delete the vApp. When creating a new vApp we sometimes get assigned an IP address that was previously used by another (now deleted) vApp. This results in the VMs in question not getting any IP traffic to/from the outside network.

I tested this by listing all the IP addresses used by the vse-VMs:

foreach ($vm in get-vm -name vse-*) { $vm.guest.ipaddress }

The result (masked the third octet) shows a lot of duplicates:

---

192.168.xx.102

192.168.xx.103

192.168.xx.104

192.168.xx.105

192.168.xx.106

192.168.xx.107

192.168.xx.50

192.168.xx.51

192.168.xx.52

192.168.xx.53

192.168.xx.54

192.168.xx.55

192.168.xx.56

192.168.xx.57

192.168.xx.58

192.168.xx.59

192.168.xx.60

192.168.xx.61

192.168.xx.62

192.168.xx.63

192.168.xx.64

192.168.xx.65

192.168.xx.66

192.168.xx.67

192.168.xx.69

192.168.xx.70

192.168.xx.71

192.168.xx.72

192.168.xx.73

192.168.xx.74

192.168.xx.75

192.168.xx.76

192.168.xx.77

192.168.xx.78

192.168.xx.79

192.168.xx.80

192.168.xx.81

192.168.xx.82

---

We can manually work around the problem by setting the VM's "Mapping mode" to Manual, and then back to "Automatic", but that's not feasable in the long run.

Any ideas on why and how this happens?

hennish · ‎09-12-2012

I think we found the problem: It's probably because of old vApps not being deleted properly when the lease time runs out.

I found a lot of dvPortgroups in 'Stranded items', which I had to find and manually stop and delete its corresponding vse-* VM. After that, deleting the dvPortgroups worked better, and new vApps don't pick duplicate IP addresses.

There might also have been some problems with vShield manager in the past which caused this. Now we're running an updated version.

All

Getting duplicate "External IP" addresses assigned by vCD