jrgalleg
Enthusiast
Enthusiast

Do I need to create a Network Profile and enable IP Pool?

Hello, This is my platform:

vCenter: 6.0 U3

Esxi: vCenter Server 6.0 Update 3c

vSphere Replication Appliance: VMWare-vSphere_Replication-6.1.2.16016-7026558

I´m trying to deploy the vSphere Replication Server and after deploy the .ovf succesfully I try to power on the server and obtain this error:

Cannot initialize "vami.gateway.vsphere_replication_appliance" Network "ONM_SRV" has no associated network protocol profile

This is not true because this network (ONM_SRV) HAS a network protocol profile. But I didn´t enable the "IP Pool" in this profile.

Do you think that this is the problem? I mean, maybe I have to enable the "IP Pool" in this profile? Or maybe another different issue?

And... Is there any impact if I enable this "Ip Pool"?

Thanks in advance.

0 Kudos
6 Replies
jrgalleg
Enthusiast
Enthusiast

Sorry, this is my real platform:

vCenter Server 6.0 Update 3c Build 7037394

ESXi 6.0 Express Patch 5 Build 56840

VMWare-vSphere_Replication-6.1.2.16016-7026558

0 Kudos
a_p_
Leadership
Leadership

This is not true because this network (ONM_SRV) HAS a network protocol profile

Please double-check that the port group has been selected in the Network Profile settings' "Assosciations" tab.

André

0 Kudos
jrgalleg
Enthusiast
Enthusiast

Yes, the port group is selected... But I did NOT create an IP Pool.

0 Kudos
a_p_
Leadership
Leadership

AFAIK there's no need to enable an IP Pool.

Configuring the IP settings (network address, mask, gateway, and DNS servers), and associating the profile with the port group that's used for the vR deployment should do, if you are using static IP settings.

André

0 Kudos
jrgalleg
Enthusiast
Enthusiast

I´ve just double chek:

All is configured: network address, mask, gateway, and DNS server

And  the profile is associatted with the port group

Same error, no way...

0 Kudos
jrgalleg
Enthusiast
Enthusiast

Any other suggestion please?

I´ve red that maybe it´s needed to create an Ip Pool in this KB2070950

VMware Knowledge Base

https://kb.vmware.com/s/article/2070950

0 Kudos