How to: Create a BIG-IP Next VE, VELOS and rSeries HA from BIG-IP Next Central Manager¶
Overview¶
Create a BIG-IP Next HA instance to manage and safeguard your applications and traffic in the event there is an issue with the provider the BIG-IP Next is installed on. If there is an issue, BIG-IP Next Central Manager will failover from the active BIG-IP Next HA node to the standby node with no disruption to current traffic or applications.
Prerequisites¶
Two healthy standalone BIG-IP Next instances created from BIG-IP Next Central Manager running the same software version on the same provider type. See How to: Create a BIG-IP Next instance in a VMware vSphere environment using an onboarding template for details.
The modules provisioning state should be the same for both instances/tenants before HA pair creation. Otherwise, HA creation will fail.
Network Interfaces: Both instances must have the same network interfaces.
NTP Configuration: Network Time Protocol (NTP) must be configured on both instances.
Module Provisioning: The same module must be provisioned on both the standby and active instances.
VLAN ID: For Velos and rSeries, both instances must have configured the same VLAN ID.
Authenticate with the BIG-IP Next Central Manager API. For details refer to How to: Authenticate with the BIG-IP Next Central Manager API.
Procedure¶
Use this procedure to create BIG-IP Next HA Instance using Central Manager GUI:
Log in to BIG-IP Next Central Manager as admin, click the Workspace icon next to the F5 icon, and click Infrastructure.
Click the mode link of the standalone BIG-IP Next instance you want to become the active node in the BIG-IP Next HA instance.
The High Availability panel opens.Click the Enable HA button.
The HA Nodes panel opens.The name and IP address for the BIG-IP Next instance that you selected displays.
This will be the active node in the BIG-IP Next HA instance after it’s created.From the Available Standby Instances list, select the BIG-IP Next instance you want to designate as the standby node in the BIG-IP Next HA instance, and click the Next button.
BIG-IP Next Central Manager displays only BIG-IP Next instances that meet the requirements to be a standby node. That is, only healthy BIG-IP Next instances running the same software version as the future active node on the same provider (VE).From the Control Plane VLAN list, select a VLAN for this BIG-IP Next HA instance.
Alternatively, you can create a new VLAN by clicking the Create VLAN link and specifying its properties so that VLAN becomes available to select from the list.
Important: When creating a new VLAN, the name must be unique and no longer than 15 characters. Longer names cause issues if troubleshooting is required.From the Data Plane VLAN list for this BIG-IP Next HA instance, select a VLAN.
Alternatively, you can create a new VLAN and interface by clicking the Create VLAN link and specifying its properties so that VLAN becomes available to select from the list.
Important: When creating a new VLAN, the name must be unique and no longer than 15 characters. Longer names cause issues if troubleshooting is required.After you select the VLANs, click the Next button.
The HA Properties panel opens.Enter the HA Management (Floating) IP Address, ensuring it belongs to the same subnet as the Management network IP address.
This enables failover to the standby node and acts as a floating management IP, regardless of which node is active in the high availability setup.Enter the Control Plane and Data Plane IP addresses by selecting two different subnets that are different from the Management network. These IP addresses will enable communication between active and standby nodes
The CIDR must be unique for each IP address and must use the same interface.Click Next.
The Traffic VLANs panel opens and displays the VLANs you specified for traffic.
You can have only one IP address for each active and standby node, but you can add additional floating IP addresses by clicking on the VLAN name.Click each VLAN to open a panel to add the respective Active, Standby, and Floating IP addresses.
When each VLAN displays a green check mark, you can proceed.Click Next.
The Summary screen opens to display the BIG-IP Next HA configuration you specified.
Use this procedure to create BIG-IP Next HA Instance using Central Manager APIs:
Get Instance details by sending a GET request to
/spaces/default/instances
endpoint. Identify the ID of the instance that you want to upgrade.GET https://{{CM_IP}}/api/v1/spaces/default/instances?filter=address eq '{{bigip_next_mgmt_ip}}'
Create a HA Pair for BIG-IP Next Instance by sending the POST request to the
/spaces/default/instances/<remote-Big-IP-Next-ID>/ha
endpoint.POST https://{{CM_IP}/api/v1/spaces/default/instances/<remote-Big-IP-Next-ID>/ha
For the request payload, use the following example, modifying the values as required.
{ "auto_failback": false, "cluster_management_ip": "xxxx.xxxx.xxxx.xxxx", "cluster_name": "eq-next-ha", "standby_instance_id": "a8180470-b9df-4c37-84d5-87fac5b5bdd2", "control_plane_vlan": { "name": "ha-cp-vlan", "tag": 0 }, "data_plane_vlan": { "name": "ha-dp-vlan", "tag": 0, "networkInterface": "1.3" }, "traffic_vlan": [ { "name": "internal", "networkName": "internal", "selfIps": [ { "address": "Node_1_IP_Address", "instanceName": "FLOATING-IP" }, { "address": "Node_2_IP_Address", "instanceName": "ACTIVE-NODE" }, { "address": ""Node_3_IP_Address", "instanceName": "STANDBY-NODE" } ] }, { "name": "external", "networkName": "external", "selfIps": [ { "address": ""Node_1_IP_Address", "instanceName": "FLOATING-IP" }, { "address": ""Node_2_IP_Address", "instanceName": "ACTIVE-NODE" }, { "address": ""Node_3_IP_Address", "instanceName": "STANDBY-NODE" } ] } ], "nodes": [ { "name": "node1", "control_plane_address": "control_plane_IP_Address", "data_plane_primary_address": "data_plane_primary_IP_Address" }, { "name": "node2", "control_plane_address": "control_plane_IP_Address", "data_plane_primary_address": "data_plane_primary_IP_Address" } ] }
Result¶
BIG-IP Next Central Manager converts the standalone BIG-IP Next instance to a BIG-IP Next HA instance consisting of an active and standby node.