Deploy in VMware vSphere ESXi (vCenter API)¶
PREREQUISITE: The following table lists the VNFM-required administrative VMware vSphere ESXi (vCenter) 6.5 environment components and guidelines that must exist PRIOR to creating a VNFM instance in your VMware project.
Verify that the following networks exist in your VIM. Click the following component links to learn more about using VMware vSphere ESXi, version 6.5:
Component Description Distributed Switch or Standard Virtual Switch You must create seven separate networks. You can create them however you want; using Distributed Switch, VLANs, and Distributed Port Group, or create a Standard Virtual Switch, and assign as many uplinks as you want. The only requirement is that you create seven, separated networks for the required pre-existing networks. Network Protocol Profile IPv4 Configuration
A network protocol profile contains a pool of IPv4 addresses for use by vApps. When you create a network protocol profile, you set up its IPv4 configuration.
The VLAN IDs for the PDN, PGW, and MGMT port groups must use the same VLAN IDs as the corresponding physical networks.
You can modify your OVF file and fine tune your instance for Nagios, DAG, and VNF resources. Options include:
- singlecpu - 1 CPU and 2048 MB RAM
- dualcpu - 2 CPUs and 4096 MB RAM (recommended for Nagios)
- quadcpu - 4 CPUs and 8192 MB RAM (recommended for VNF and DAG)
- octalcpu - 8 CPUs and 16384 MB RAM (high-performance configuration)
Use the wizard to deploy VM from OVF in content library:
At step 6: Customize template in the wizard, be sure to complete the guest network settings, so you can access the VNF Manager UI.