Note: This does NOT include NSX at this stage (might follow later)
Network Profiles aren’t really necessary. It depends how you manage your networks. When you create a reservation – you also need to specify a port group used for your virtual machine networking.
A network profile essentially provides your VM with information such as IP / Netmask / Gateway etc., and vRA then also keeps a record of IPs used from the pool.
If you don’t have a profile – you effectively have to manage this externally. You can set a blueprint to use DHCP etc., but if you want to use static IPs, you will need to configure all that manually.
So Network Profiles are the way to go.
Here I have assigned the following pool for vRA deployments:
- Assigned IPs : 10.10.0.170 – 10.10.0.189
Navigate to Infrastructure > Reservations > Network Profile
Click New > External
I am unable to use NAT / Routed as I do not have NSX in my environment.
Enter the subnet details and name
Move to the tab IP Ranges. Click New
Give it a pool of IPs
That’s it ..