Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 8801
  • Last Modified:

Powering on vMA (VApp) getting 'has no associated network protocol profile' error

I attempted to install the vMA vApp on our vSphere 5.1 cluster. I got the VM to install from an OVF, but when I boot the first time I get the following message:

vSphere Management Assistant (vMA) Cannot initialize property 'vami.netmask0.vSphere_Management_Assistant_(vMA)'. Network 'VM Mgmt Network' has no associated network protocol profile.

I have searched the documentation and I cannot figure how to create or associate a "network protocol profile. It has a NIC and the NIC is assigned to the VM Mgmt Network. When I follows the OVF install wizard it as for an IP and I chose Fixed IP when it asked me a network time. I gave it a valid unique IP.

Any ideas what to do here?
0
sweetseater
Asked:
sweetseater
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You need to assign a vApps an IP Pool.

Select the IP Pools Tab, and Add an IP Pool before you Import any vApp.

IP Pool - vApp
0
 
coolsport00Commented:
Don't recall the error I got upon bootup, but what I did to get mine to tun on, and if you have no vApps..and just wanna use the vMA VM, I believe all you need to do is rt-click on the new vMA VM > Edit Settings > Options, then disable the vApp option. Your error sounds like it's different than what I recv'd though.

~coolsport00
0
 
sweetseaterAuthor Commented:
This one did the trick.
0

Featured Post

Veeam Task Manager for Hyper-V

Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now