Create a BIG-IP Next Central Manager on VMware

This document describes how to create the BIG-IP Next Central Manager on VMware.

Prerequisites

  • MyF5 login and Central Manager OVA image

  • VMware vSphere hypervisor version 7.x and credentials

  • Hypervisor Resources:

Deployement Type Resources
Standalone Node
  • 8 vCPUs, 16 GB RAM
  • 350 GB disk
High Availability (3 nodes)
  • 3 × 8 vCPUs, 3 × 16 GB RAM
  • 3 × 350 GB disk

  • Network Resources:

    • IP Address, subnet, and hostname

    • NFS or SAMBA network attached storage (NAS) and credentials

    • NTP Server

    • DNS Server

    • Gateway Router

  • Review the appropriate Release Notes

Limitation

The BIG-IP Next Central Manager has specific requirements for NFS external storage. These requirements must be met to ensure proper functionality:

  • The CM root user must be able to create directories within the external storage directory.

  • The CM root user must be able to change ownership of those directories to UID and GID 1000.

  • The CM admin user with UID and GID 1000 must be able to create files and directories inside the directories established by the CM root user.

The configuration required to meet these standards can vary depending on the storage vendor. The following configuration has been tested and verified to support these requirements.

  • Operating System: Ubuntu 22.04 server

  • NFS Export Configuration: Configured using no_root_squash

  • Directory Ownership: The exported directory must be owned by the root user and group.

  • Directory Permissions: The permissions on the exported directory must be set to 0777.

Procedures

Complete the steps below to install BIG-IP Central Manager.

Download OVA

  1. Use your credentials to sign in to my.f5.com

  2. Click Downloads.

  3. Review the EULA and Program Terms, then click I have read and agreed to the terms of the End User License Agreement and Program Terms., then click Next.

  4. Under Group, select BIG-IP_Next.

  5. Under Product Line, select Central Manager

  6. Under Product Version, select the latest version.

  7. Under Select a product container, select the latest version.

  8. Under Select a download file, select the OVA file.

  9. Under Download locations, select the appropriate region.

  10. Click Download.

  11. Repeat these steps to download the sha256 or md5 checksum file.

  12. Verify the downloaded OVA file using the checksum: linked instructions.

  13. Move the verified OVA file to a desired location.

You are now ready to deploy the OVA to create the CM virtual machine.

Deploy OVA

  1. Log in to the VMware vSphere Client.

  2. In the left hand navigation pane, select an appropriate host or cluster for CM.

  3. Click ACTIONS > Deploy OVF Template.

  4. Locate the previously downloaded OVA file to use to install a VM:

    1. Select Local file and then click UPLOAD FILES.

    2. Select the OVA file, and click Open.

  5. Click NEXT.

  6. Type a VM name and select a location. Click NEXT.
    Important: Do not use the plus ( + ) sign in the VM name.

  7. Select a location for the compute resource and click NEXT.

  8. Verify the temmplate details and click NEXT.

  9. Select the storage for the configuration and disk files, and click NEXT.

  10. Select a Destination Network and click NEXT.

  11. Review the settings and click FINISH.

Launch console and change password

  1. In left pane, click the icon for the Hosts and Cluster menu.

  2. Navigate to the BIG-IP Next Central Manager virtual machine location.

  3. Open the VM console using the Launch Web Console or Launch Remote Console.
    The console opens.

  4. For both the central-manager login and Password, type admin.
    You are required to change your password… displays

  5. Change your password. Type:

    • Current password

    • New password

    • Retype new password
      The Welcome information displays.

Run the setup script

Note: This is required if the user wants to configure a static IP address for the VM instance or the DNS server configurationsis is available only during the initial setup. After the CM services are started, adding these conifiguration settings are not available. Follow the instructions below.

  1. While still on the CM console, at the $ prompt, type setup
    Welcome… and instructions display.

    Note: Message if BIG-IP Next Central Manager is already installed:

    BIG-IP Next Central Manager has already been installed.
    Running setup again will destroy all current configuration and data.
    Please run /opt/cm-bundle/cm uninstall -c prior to running setup if you wish to continue.

  2. Type inputs

    Example values are shown within parentheses. If there is a default value, it will be shown within square brackets and will automatically be used if no value is entered.

Network with DHCP

Hostname (example.com): 
['10.145.77.192'] found on the management interface.
Do you want to configure a static IP address (N/y) [N]:  
Primary NTP server address (0.pool.ntp.org) (optional):
Alternate NTP server address (1.pool.ntp.org) (optional):<br>

Network with a management IP address (No DHCP)

Hostname (e.g. example.com): central-manager-server-1
IP address(es) ['10.192.10.136'] found on the management interface.
Do you want to configure a static IP address (N/y) [y]: Y
Management IP Address & Network Mask [192.168.1.245/24]: 10.192.10.139/24
Management Network Default Gateway [192.168.1.1]: 10.192.10.1
Primary DNS nameserver (e.g. 192.168.1.2): 10.196.1.1
Alternate DNS nameserver (e.g. 192.168.1.3) (optional): 10.196.1.1
Primary NTP server address (i.e 0.ubuntu.pool.ntp.org) (optional):
Alternate NTP server address (e.g. 1.ubuntu.pool.ntp.org) (optional):
IPv4 network CIDR to use for service IPs [100.75.0.0/16]:
IPv4 network CIDR to use for pod IPs [100.76.0.0/14]:

Note: About the two inputs for service and pod IPs: the system uses the two internal IP addresses for communication between invidual containers. Make sure the defaults listed do not conflict with the existing IP address space on your network. If they do, choose a different IP range for the service and pod IPs to resolve the conflict.

Summary and Installation

Summary
-------
Hostname: central-manager-server-1
Management Network Already Configured: False
Management IP Address: 10.192.10.139/24
Management Gateway: 10.192.10.1
DNS Servers: 10.196.1.1, 10.196.1.1
IPv4 network CIDR to use for service IPs: 100.75.0.0/16
IPv4 network CIDR to use for pod IPs: 100.76.0.0/14

  • Would you like to complete configuration with these parameters (Y/n) [N]:

    Type Y to complete.

Access the BIG-IP Next Central Manager GUI

  1. From a web browser, navigate to the address you configured earlier: https://<cm-ip-address-or-hostname/>.

  2. Verify that the CM GUI appears.

    Note: The CLI password for admin and the GUI password are not the same. The default GUI password is admin/admin. If you set the CLI password for admin, it does not change the GUI password.

Proceed by creating a BIG-IP Next Instance to secure apps.

Configure the BIG-IP Next Central Manager

The BIG-IP Next Central Manager has been successfully created. You can configure it using BIG-IP Next Central Manager GUI or API. See Configure the Standalone or High Availability using BIG-IP Next Central Manager GUI.