Applies To:
Show Versions
BIG-IQ Cloud and Orchestration
- 1.0.0
Integrating with VMware NSX
Network requirements for communication with VMware cloud services
For proper communication, BIG-IQ® Cloud must have network access to the resources on which VMware software is installed. Before you can manage cloud resources, you must define a network route between the BIG-IQ Cloud device’s VLAN and the management VLAN on the VMware.
Discovering devices located in the VMware cloud
After you license and perform the initial configuration for the BIG-IQ® system, you can discover BIG-IP® devices running version 11.5 or later. For proper communication between the managing BIG-IQ device and the devices it manages, you must configure the BIG-IQ system with a route to each F5 device you want to manage. If you do not specify the required network communication route between the devices, then device discovery fails.
You must know the IP address that the BIG-IQ device will use to access the BIG-IP device.
Discover a device by providing the BIG-IQ® system with the device's IP address, user name, and password.
About configuring the BIG-IQ device for a VMware integration
The BIG-IQ ®device facilitates the integration between the VMware NSX and the BIG-IP® device or device cluster. The work flow for configuring this integration takes you back and forth between the two participants in this integration.
You can either integrate with a standalone BIG-IP virtual machine, or with a high availability (HA) cluster of BIG-IP virtual machines. The process for setting up the two configurations is nearly identical. Optional steps and settings to enable HA are noted where applicable.
You can ensure that the traffic management function is always available by configuring two or more BIG-IP systems in a high availability (HA) configuration. Any configuration change that occurs on one BIG-IP system is immediately synchronized with its peer devices. If one BIG-IP system in an HA configuration fails, a peer BIG-IP system takes over the traffic management.
The BIG-IP HA cluster that you create with this process is a single failover group that uses the default traffic group and automatic sync. For a complete discussion of the significance of these details, refer to the BIG-IP® Device Service Clustering: Administration guide, which is available on http://support.f5.com/kb/en-us.html.
Prepare the BIG-IQ devices for NSX integration
To begin the process of preparing the BIG-IQ® device for integration, you set up one or more BIG-IQ devices, create an NSX call back user, and a new server image, and then create an NSX connector.
Configuring a high availability configuration
Configuring BIG-IQ® Cloud as part of a high availability (HA) cluster ensures that you do not lose management capability of the BIG-IP® devices in your network because one BIG-IQ Cloud system fails.
If you have a primary BIG-IQ system (it can either be brand new, or one that you have been using for a while), and you want to add one or more new BIG-IQ Cloud systems as backup, you simply add the new systems to the primary system's cm-cloud-all-big-iqs group.
If discovery of the newly configured BIG-IQ system fails, a Delete button displays. Verify the correct self IP address and credentials. Then click the Delete button to remove the incorrect information, and re-type the self IP address, user name, and password.
About activating a pool license
When you integrate with VMware NSX to create BIG-IP® VE virtual machines, you can activate a pool license so that BIG-IQ® software can use a license from that pool to license the BIG-IP VE systems that it creates.
You can choose not to use a pool license and skip to discovering devices. If you make this choice, the BIG-IQ device still creates BIG-IP VE systems, but you need to license them before they can be used.
You initiate the license activation process with a base registration key. The base registration key is a character string that the license server uses to verify the functionality that you are entitled to license. If the system has access to the internet, you select an option to automatically contact the F5 license server and activate the license. If the system is not connected to the internet, you must manually retrieve the activation key from a system that is connected to the internet, and then transfer it to the BIG-IQ system.
Automatically activating a pool license
Manually activating a pool license
Creating an NSX callback user
Creating a new server image
Creating a connection between BIG-IQ Cloud and NSX Manager
To enable integration between a third-party cloud provider and BIG-IQ® Cloud, you must configure a cloud connector. A cloud connector is a resource that identifies the local or virtual environment in which a tenant deploys applications and, when necessary, adds parameters required by third-party cloud providers.
For VMware NSX version 6.2 and later, BIG-IQ Cloud also helps you manage VMware resources required to run applications. Management tasks include discovering, creating, starting, and stopping VMware NSX application servers running in the private cloud. You can use this feature to accommodate seasonal traffic fluctuations by periodically adding and retracting devices and application servers as needed. Additionally, you can also provide tenants access to self-deployable iApps® through VMware integration.
As part of the connection creation process, the BIG-IQ system does the following:
- Creates a new default tenant for the new connector.
- Verifies connectivity to the NSX Manager and vCenter APIs, and registers the BIG-IQ system as an NSX Partner Service provider.
- Creates a callback user role that enables NSX to access the BIG-IQ software resources necessary for interaction with the BIG-IQ REST API.
Prepare VMware NSX for integration
After you finish preparing the BIG-IQ® device for integration, there are a couple of tasks to perform in the VMware NSX environment to complete the integration. You need to create an NSX Edge Service Gateway and enable a load balancing service for it.
Creating an NSX Edge Services Gateway
The NSX Edge Service Gateway establishes the network within which network services such as firewall, NAT, and load balancing are deployed. To integrate a BIG-IP® device with NSX, you must create at least one Edge Service Gateway.
- Choose to create the gateway in undeployed mode.
- If you are configuring an HA cluster of BIG-IP virtual machines, select Enable High Availability, otherwise leave it cleared.
- Choose the X-Large Appliance size.
- Make sure that the NSX Edge you create identifies the Cluster/Resource Pool and the Datastore, but does not identify any interfaces. Otherwise, follow your standard practice for NSX Edge creation.
Enabling a service for the Edge
You must provision IP pools and port groups before you enable an Edge load balancer.
If you are configuring an HA cluster of BIG-IP® virtual machines for two-arm deployments, you need to configure four vnics (1 for management, 2 for data, and 1 for HA). For one-arm deployments, you need three vnics (management, data, and HA). If you are not using HA, you can use one less vnic in each case.
The NSX Edge Service Gateway establishes the network within which network services such as firewall, NAT, and load balancing are deployed. To integrate a BIG-IP® device with NSX, you must create at least one Edge Service Gateway.
Prepare the new BIG-IP devices for integration
After the VMware NSX integration creates the BIG-IP® virtual devices, there are a couple of tasks to perform on the BIG-IP device environment to complete the integration. If the devices are configured in an HA cluster, you only perform these tasks on one device, after which the configuration is replicated on the other cluster members using Config sync.
Uploading a custom iApp to the BIG-IP device
Creating a customized application template
An iApp is an application template located on F5 devices. When you discover an F5 device, all iApps® templates installed on that device are imported to the BIG-IQ® system. You can customize iApp templates, specifying which parameters are displayed, and which are tenant-editable. Once deployed, these parameters are available in the NSX user interface.
Complete the NSX integration
After you finish preparing the BIG-IP® devices for integration, there are a couple of tasks to perform in the BIG-IP device environment to complete the integration. Because the devices are configured in an HA cluster, you only perform these tasks on one device, after which the configuration is replicated on the other cluster members using Config sync.