Configure SovLabs IPAM for NSX Consumption

Brandon Miller
by Brandon Miller

Categories

Overview

The SovLabs IPAM Profiles can be utilized as a custom External Network Profile to allow blueprint design actions for NSX Load Balancer components. Follow this guide to configure NSX to use the SovLabs IPAM Profile.

 

Considerations

This method does not currently support network ranges inside the Network Profile

 

Procedure

Create a SovLabs IPAM Profile
  1. Follow the documentation at http://docs.sovlabs.com/latest/vRA/7.5/modules/ipam/infoblox-ipam/ to configure an IPAM profile

  2. Note: When creating the IPAM profile, be sure that the Network name inserted in the configuration matches the VMware Port Group inside vCenter that references the NSX Logical Switch
Create a SovLabs DNS configuration
  1. Follow the documentation at http://docs.sovlabs.com/latest/vRA/7.5/modules/dns/infoblox-dns/ to configure a DNS configuration

Create a vRA Endpoint in vRO
  1. In vRO navigate to Library>vRealize Automation>Configuration>Add a vRA Host
  2. Create a vRA host using the vsphere.local target tenant
  3. Ensure that the authentication is using the "administrator@vsphere.local" account, as this account will be required to register the IPAM Endpoint via a REST connection.

Register the IPAM Endpoint
  1. Connect to the vRealize Orchestrator configured for the tenant
  2. Run the vRO workflow - Register the IPAM Endpoint located in the following location:
    • SovLabs -> IPAM -> vRA Framework -> Configuration -> Register IPAM Endpoint
  3. Follow the below table for workflow run selections:
Selection Value
Common parameters>The created vRA host The vphere.local tenant which is not labeled as “Default”
Common parameters>IPAMProfile Navigate to Sovlabs VRA Extensibility Modules>Ipam and select the IPAM profile
vRA [blank]
IPAM Endpoint [blank]
 
Create a new Network Profile in vRA
  1. Navigate to the vRA website and browse to Infrastructure>Reservations>Network Profiles

  2. In the Network Profiles pane, click New>External

  3. Click the IPAM endpoint drop down and select the SovLabs IPAM profile that was created during the vRO workflow execution
  4. Once selected, enter in a name for the network profile.
  5. Note: it is suggested to insert a name that is the same as the IPAM endpoint for cross-reference
  6. For the Network Ranges tab, it is expected to be blank.
  7. Note: SovLabs build 2018.3.0 and below does not support network ranges at this time. Check the SovLabs plugin release notes website for updates
  8. Click OK to create the Network Profile
 
Modify the Reservation(s)
  1. Ensure that all necessary reservations are modified to include the new network profile as needed. SovLabs properties will not apply to this new configuration
 
Create/Modify a Blueprint for NSX Load Balancer
  1. Navigate in vRA to the Design tab and create/modify a blueprint

  2. The assumption is there is already or will be a vSphere (vCenter) machine type in the blueprint
  3. Click on the Blueprint Properties
  4. From the Categories section click on Network & Security
  5. In the Transport zone: drop down, select the Transport zone from your NSX configuration
  6. Click and drag the Existing Network component onto the blueprint Design Canvas
  7. Click the new Network Component and select the Network profile that was created
  8. Click on the vSphere machine component(s) and select the Network tab
  9. Click New or select an existing NIC already configured, then select the Network Profile created to assign to the component
  10. In the Network & Security category, click and drag the On-Demand Load Balancer component on the Design Canvas
  11. Click the On-Demand Load Balancer component and select the Member, Member network, and VIP Network that correspond to the vSphere and Existing Network component
  12. For multiple IPAM profiles, repeat the all sections above

 

Important Note for Infoblox IPAM usage with NSX

The Infoblox IPAM will throw an error if the following custom property is NOT set for the build itself. This property needs to be assigned to the build due to a duplicate DNS registration error that can occur.

  • Custom Property: VirtualMachine.Network0.IPAMCreatedHostRecord = true

 

Additional information

N/A

 

Click to download PDF

The first step in providing reliable self-service automation for your CMP is starting a free trial.

Free Trial
Wave One Wave One
Wave Two Wave Two