How to: Upgrade a Standalone BIG-IP Next VE from BIG-IP Next Central Manager

Overview

This procedure describes on how to upgrade the software for standalone BIG-IP Next Virtual Edition (VE) instances from BIG-IP Next Central Manager.

Prerequisites

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

Results

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

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:

1. 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}}'

2. The VE 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	<signature_filename>
   description	Text	big-ip next upgrade signature file

   *Note: The image file and signature file name ends with ‘.tgz’ and ‘.tgz.512.sig’ respectively.

3. 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

4. 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": "ve",
       "image_name": "<bigip_next_image_filename>",
       "signature_name": "<bigip_next_signature_filename>"
   }
   

5. 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}}

6. 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
   }
   

Result

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

:::

::::