How to: Upgrade BIG-IP Next on rSeries from BIG-IP Next Central Manager¶

Overview¶

This document describes how to upgrade BIG-IP Next on an rSeries from BIG-IP Next Central Manager.

Prerequisites¶

Before upgrading, you must import the new software image to the rSeries chassis as a Tenant Image. For more information, refer to the rSeries Systems documentation.

Authenticate with the BIG-IP Next Central Manager API. For details refer to How to: Authenticate with the BIG-IP Next Central Manager API.

Under Download locations, select the appropriate location.
Click Download. The file is downloaded to your local system, which can take up to an hour because of the size of these files. 1. Log in to BIG-IP Next Central Manager as admin, click the Workspace icon next to the F5 icon, and then click Infrastructure.
To upload the image, first log in to the rSeries WebUI.
Click on Target Images from the menu on the left side of the screen.
. Click on Upload.
Navigate to the location of the .tar.bundle you downloaded, select it and click Open.
Wait until the images grid shows three related files (image bundle file, image file and image deployment file) and all files have status Replicated.
Log in to BIG-IP Next Central Manager as admin, click the Workspace icon next to the F5 icon, and then click Infrastructure.
Select the checkbox next to the BIG-IP Next instance you want to upgrade.
On the top right of the screen, click Actions and select Upgrade.
In the Chassis Partition IP Address or FQDN field, enter the IP address or FQDN of the rSeries chassis partition on which the BIG-IP Next instance tenant is located.
Enter the Username and Password for the rSeries chassis partition.
In the Tenant field, type the name of the tenant.
In the Image field, type or paste the name of the BIG-IP Next image you uploaded to rSeries.

Click the Authenticate & Upgrade button and accept the fingerprint displayed for authentication with the partition.
Confirm the upgrade by clicking the Upgrade button on the confirmation message.

Result¶

BIG-IP Next Central Manager upgrades the software for this BIG-IP Next instance.

If you plan to backup your instance files, you need to delete the large image files on the BIG-IP Next instance. See How to: Back up managed BIG-IP Next instances to BIG-IP Next Central Manager’s local drive instantly or on a schedule for more information.

:::

:::{tab-item} Central Manager API

To upgrade 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}}'
The rSeries BIG-IP Next upgrade requires an “image file” and “signature file”. Both files must be downloaded from F5 site and uploaded individually to the instance.

Use the *POST request to upload both the files simultaneously by sending a POST request to /spaces/default/instances/{remote-Big-IP-Next-ID}/proxy-file-upload: endpoint using instance_id of the instance you want to upgrade.

POST https://{{CM_IP}}/api/v1/spaces/default/instances/{{remote-Big-IP-Next-ID}}/proxy-file-upload:

For the API form data, use the following example, modifying the values as required.

file_name

File

bigip-next-signature-bundle.tgz.512.sig

name

Text

<tgz.512.sig file name>

description

Text

big-ip next upgrade signature file

*Note: The image file and signature file name ends with ‘.tgz’ and ‘.tgz.512.sig’ respectively.
Get the uploaded files by sending the GET request to the /device/v1/proxy/{{remote-Big-IP-Next-ID}}?path=/files endpoint using instance_id of the instance you want to upgrade. The image name and signature name is returned in the response.

GET https://https://{{CM_IP}}/api/device/v1/proxy/{{remote-Big-IP-Next-ID}}?path=/files
Initiate the instance upgrade by sending the POST request to the /spaces/default/instances/{{remote-Big-IP-Next-ID}}/upgrade endpoint using instance_id of the instance you want to upgrade.

POST https://{{CM_IP}}/api/v1/spaces/default/instances/{{remote-Big-IP-Next-ID}}/upgrade

For the request payload, use the following example, modifying the values as required.
```
{
    "upgrade_type": "appliance",
    "partition_address": "10.145.79.233",
    "partition_port": 5443,
    "partition_user": "admin",
    "partition_password": "example02!",
    "image_name": "test",
    "tenant_name": "test",
    "provider": "rSeries name"
}
```
Get the status for instance upgrade task by sending the GET request to the /spaces/default/instances/upgrade-tasks/{{bigip-next-upgrade-task-id}} endpoint.

GET https://{{CM_IP}}/api/v1/spaces/default/instances/upgrade-tasks/{{bigip-next-upgrade-task-id}}
In the response, when the state indicates wait for user input, accept the fingerprint to trust the certificate. Accept the fingerprint by sending a PATCH request to the /spaces/default/instances/upgrade-tasks/{{bigip-next-upgrade-task-id}} endpoint to generate new certificates.

PATCH https://{{CM_IP}}/api/v1/spaces/default/instances/upgrade-tasks/{{bigip-next-upgrade-task-id}}

For the request payload, use the following example, modifying the values as required.
```
{
    "is_user_accepted_untrusted_cert": true
}
`
```


file_name	File	bigip-next-signature-bundle.tgz.512.sig
name	Text	<tgz.512.sig file name>
description	Text	big-ip next upgrade signature file

Result¶

After the upgrade process, the BIG-IP Next instance displays with the new version on the My Instances page.

:::

::::

Previous Next