Create BIG-IP Next Central Manager on VMware¶

BIG-IP Next Central Manager (CM) is the management and app orchestration platform for BIG-IP Next. Use these instructions to install a new CM virtual machine on your vSphere hypervisor, set the password, and apply a base configuration.

Task Overview¶

Click below to jump to the appropriate section.

Prerequisites¶

MyF5 login and Central Manager OVA image
VMware vSphere hypervisor version 7.x or later and credentials
Hypervisor Resources:
- 8 vCPUs, 16GB RAM
- 350GB disk
- One network interface
Network Resources:
- IP Address, subnet, and hostname
- SMB or NFS network attached storage (NAS) and credentials
- NTP Server
- DNS Server
- Gateway Router
Review the appropriate Release Notes

Procedures¶

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

Download OVA¶

Use your credentials to sign in to my.f5.com
Click Downloads.
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.
Under Group, select BIG-IP_Next.
Under Product Line, select Central Manager
Under Product Version, select the latest version.
Under Select a product container, select the latest version.
Under Select a download file, select the OVA file.
Under Download locations, select the appropriate region.
Click Download.
Repeat these steps to download the sha256 or md5 checksum file.
Verify the downloaded OVA file using the checksum: linked instructions.
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¶

Log in to the VMware vSphere Client.
In the left hand navigation pane, select an appropriate host or cluster for CM.
Click ACTIONS > Deploy OVF Template.
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.
Click NEXT.
Type a VM name and select a location. Click NEXT.
Important: Do not use the plus ( + ) sign in the VM name.
Select a location for the compute resource and click NEXT.
Verify the temmplate details and click NEXT.
Select the storage for the configuration and disk files, and click NEXT.
Select a Destination Network and click NEXT.
Review the settings and click FINISH.

Launch console and change password¶

In left pane, click the icon for the Hosts and Cluster menu.
Navigate to the BIG-IP Next Central Manager virtual machine location.
Open the VM console using the Launch Web Console or Launch Remote Console.
The console opens.
For both the central-manager login and Password, type admin.
You are required to change your password… displays
Change your password. Type:
- Current password
- New password
- Retype new password
  The Welcome information displays.

Run the setup script¶

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.
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):
Network with a management IP address (No DHCP)
- Hostname (e.g. example.com):
- Management IP Address & Network Mask [192.168.1.245/24]:
- Management Network Default Gateway [192.168.1.1]:
- Primary DNS nameserver (e.g. 192.168.1.2):
- Alternate DNS nameserver (e.g. 192.168.1.3) (optional):
- 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.
Storage
- Do you want to set up an external storage mount (Y/n) [Y]:
- Storage type (samba/nfs):
  
  samba:
  - Address for the storage server:
  - Share path on the storage server:
  - Username for the storage server:
  - Password for the storage server:
  nfs:
  - Address for the storage server:
  - Share path on the storage server:
Summary and Installation

Sample output
```
Summary
-------

Hostname: central-manager.example.com
Management Network Already Configured: True
NTP Servers: 0.ubuntu.pool.ntp.org
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.

Sample output

...
[info] k3s node 'node/central-manager-abcd1234' is ready

Would you like to start the Central Manager application installation (Y/n) [Y]:

Type Y to install.

The BIG-IP Central Manager install is complete when this displays:
```
```
[INFO] Setup completed succssfully.
```
```

Access CM Web GUI¶

From a web browser, navigate to the address you configured earlier: https://<cm-ip-address-or-hostname/>.
Verify that the CM GUI appears.

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

Previous Next