VMware Communities: VMA 5.0 ip address pool required ?

Skip navigation

VMware

Up to Discussions in VMware ESXi 5

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)

4,140 Views 8 Replies Last post: Jan 13, 2012 10:03 AM by JoyYu

sc_2111@vmtn

219 posts since
Feb 20, 2007

Currently Being Moderated

Sep 13, 2011 7:18 AM

VMA 5.0 ip address pool required ?

Hi ,

I've downloaded and imported the VMA 5.0 472630

While importing it I noticed a warning about the fact that it requires an IP POOL but gave it no much importance as I wanted to assign a fixed IP.

So after the import I tried to start the VM but it fails with the error the no IP ADDRESS POOL was associated to the virtual lan.

So I created an IP POOL and associated it to the lan and have the VM booted.

after booting I was prompted for the initial network configuration .

I set a static IP , so I hoped to get rid off the IP POOL . But removing the association prevented again the VM from booting.

So my question is :

What the use for IP POOL if I want to use a static IP ?

Can I get rid of such requirement ?

thanks

jslarouche

196 posts since
Jan 20, 2007

Currently Being Moderated

1. Sep 15, 2011 12:11 PM

in response to: sc_2111@vmtn

Re: VMA 5.0 ip address pool required ?

I am getting the same issue.. With no workaround as of yet.

Report Abuse

jslarouche

196 posts since
Jan 20, 2007

Currently Being Moderated

2. Sep 15, 2011 12:18 PM

in response to: jslarouche

Re: VMA 5.0 ip address pool required ?

if you right click your vMA 5.0 vm and edit it's settings.. Go to the Options Tab and disable vApp Options.. Once i did that on mine then i was able to boot the appliance. try that..

Report Abuse

marktbreaux

42 posts since
Mar 9, 2009

Currently Being Moderated

3. Sep 16, 2011 12:32 PM

in response to: jslarouche

Re: VMA 5.0 ip address pool required ?

thanks jslarouche I was able to find the culprit because of you suggesting to turn off vApp. It is a setting in Advanced Property Configuration. You can get there by going to the vMA app > Edit settings> Options Tab > Under vApp Options > Select Advanced. From there you will see a Properties box. The top key listed in the culprit. Its labeled "vami.DNS0.<nameofyourappliance>"

Not sure its function. Maybe someone else can explain but deleting that key will prevent the error. Also disabled vApp will too but I thought that I should keep it as original as possible.

Edit: Looks like any of the dynamic keys in there will through it for a loop. I changed to static and filled in my static entries.

Report Abuse

BenjaminTroch

1 posts since
Nov 24, 2010

Currently Being Moderated

4. Oct 17, 2011 10:19 PM

in response to: marktbreaux

Re: VMA 5.0 ip address pool required ?

I had the same error. If you go into Edit Settings\Options\Advanced\IP Allocation and under IP Allocation Scheme tick "OVF environment" it does the trick and the VMA boots with vAPP options enabled.

Cheers,

Benjamin

Report Abuse

1q2w3e4r

81 posts since
Apr 23, 2006

Currently Being Moderated

5. Nov 1, 2011 3:41 PM

in response to: sc_2111@vmtn

Re: VMA 5.0 ip address pool required ?

I had a similar issue, I have the vCloud Usage Meter which is an appliance from vmware. I rebooted it to update the virtual machine hardware from 7 to 8, but not sure whether it was this upgrade or the fact that I needed an IP pool to deploy the appliance which I had subsequently deleted (since I don't use DHCP for my VMs), and then the reboot was looking for this and couldn't find it?

In any case I could no longer boot the vm with the vami.dns0.. error which was a bit shitty, so I just disabled the vApp options (edit settings->options tab->vApp options->disable), and now I'm back in business.

Report Abuse

AnthonyChow

221 posts since
Jun 7, 2010

Currently Being Moderated

6. Dec 30, 2011 9:44 PM

in response to: sc_2111@vmtn

Re: VMA 5.0 ip address pool required ?

sc_2111@vmtn wrote:

So I created an IP POOL and associated it to the lan and have the VM booted.
after booting I was prompted for the initial network configuration .
I set a static IP , so I hoped to get rid off the IP POOL . But removing the association prevented again the VM from booting.

I am seeing the same problem and I see from the other posting how to fix it.

I have created the IP pool at the Datacenter level. Just wanted to know how do you associate the IP pool to the vm port group?

thanks for the information,

anthony.