Upgrade F5 rSeries Host Software v1.8.3 (1.x)

Perform software upgrades on F5 rSeries host devices to keep the host OS up to date with the latest features and security patches. This workflow manages the upgrade execution process, verifying prerequisites, backing up current configuration, and safely upgrading the F5 rSeries host operating system.

Before upgrading F5 rSeries host software v1.8.3 (1.x), ensure you have:

Valid AppViewX credentials with permissions to run ADC workflows
At least one F5 rSeries host device onboarded in ADC inventory
Target F5 rSeries device(s) reachable and responsive
Latest F5 OS image already transferred to the device (using F5 ISO Image Transfer workflow)
The new ISO image file present in the /shared/images directory on the rSeries device
Administrative access credentials for the F5 rSeries host device
Network connectivity between AppViewX and rSeries management interface
Access to rSeries device management port (typically port 443 for HTTPS)
Sufficient disk space on the rSeries device for upgrade operations
A backup of current rSeries configuration (optional but recommended)
Maintenance window scheduled with appropriate stakeholders
Understanding of potential service disruption during upgrade
All dependent services and applications documented for recovery

Important: Before initiating the upgrade, verify that F5 rSeries tenants (if deployed) are in a stable state. Tenant services may be temporarily unavailable during host OS upgrade.

Prepare for the software upgrade.
1. Verify that the new F5 OS image has been successfully transferred to the target rSeries device.
2. SSH to the F5 rSeries host device and verify the image is present in /shared/images:
```
SSH to rSeries host (for example, it-cbe-f5rsr1.lab.appviewx.net)
# tmsh
tmsh# list sys software image
Name                                         Installed  Build    Built
BIGIP-21.0.0.1-0.0.13.ALL-F5OS.tar.bundle   no         0.0.13   Apr 21 2026
```
3. Create a backup of the current F5 rSeries configuration using the RSeries Device Backup workflow for safety and recovery purposes.
4. Notify all stakeholders about the scheduled maintenance window.
5. Document current system state, running tenants, and active connections for recovery reference.
Log into AppViewX and access the upgrade workflow.
1. Log in to AppViewX with your credentials.
2. Navigate to ADC+ > AUTOMATION > Workflow Catalog > View/Run.
3. Locate and select the F5 rSeries Host Software Upgrade workflow.
4. The upgrade form opens with input fields for configuration.
Configure upgrade parameters.
1. Select the target F5 rSeries host device from the device list.
  
  Tip: Only rSeries host devices (not tenants) are available for selection. Ensure you select the correct device.
2. Verify the current installed image version displayed in the workflow.
3. Select the target image for upgrade from the available images in /shared/images:
  - The dropdown displays all uploaded ISO images available on the device
  - Select the new image version you previously transferred
  - Ensure this is a newer version than currently installed
4. Review upgrade options if available:
  - Preserve Configuration: Attempt to preserve existing configuration during upgrade
  - Reboot Timeout: Set timeout for device reboot completion (typically 30-60 minutes)
  - Rollback on Failure: Enable automatic rollback if upgrade fails
  - Force Upgrade: Override safety checks if necessary (use with caution)
Validate upgrade prerequisites.
1. Click the Pre-Check or Validate button to verify all prerequisites are met.
2. The validation process checks:
  - F5 rSeries device connectivity and responsiveness
  - Target image file exists and is readable
  - Sufficient disk space for upgrade operations
  - Device is not currently processing an upgrade
  - No active migrations or deployments in progress
  - Device is in stable state for upgrade
3. Review the validation results and resolve any issues identified.
4. If validation fails, address the reported issues before proceeding with the upgrade.
Review and acknowledge upgrade implications.
1. Review the upgrade summary showing:
  - Target device and current image version
  - Upgrade target image version
  - Estimated upgrade time
  - Expected downtime duration
  - Rollback availability options
2. Acknowledge that you understand:
  - All services on the rSeries device will be temporarily unavailable
  - Any running tenants will be temporarily offline
  - Active connections will be dropped during the upgrade
  - The upgrade process cannot be interrupted once started
  - Rollback may not be possible for all configurations
3. Confirm you have taken backups and notified stakeholders.
Initiate the upgrade process.
1. Click the Start Upgrade or Execute button to begin the upgrade.
2. The workflow submission confirmation page appears with a request ID.
3. The upgrade workflow initiates on the F5 rSeries device.
Monitor upgrade execution.
1. Click View Request to open the Request View page.
2. Monitor the upgrade progress through the following phases:
  - Pre-Upgrade Checks: Final verification before upgrade begins (5-10 minutes)
  - Image Installation: Upgrade image is installed to the device (10-30 minutes)
  - Reboot Sequence: rSeries device reboots with new image (5-10 minutes)
  - Post-Upgrade Validation: Verifies upgrade success and device stability (5-15 minutes)
  - Service Recovery: Services and tenants come back online (5-10 minutes)
3. Total estimated upgrade time: 30-75 minutes depending on device and image size.
4. Do not interrupt the upgrade process once it has started.
5. Monitor logs for any error messages or warnings during the three phases.
Wait until the device completes its reboot and is fully operational.
1. During the Reboot Sequence phase, the F5 rSeries device will become temporarily unreachable.
2. Do not attempt to access the device or interrupt the reboot process.
3. Allow 5-10 minutes for the device to complete the reboot and return to service.
4. The workflow automatically waits for the device to come back online and become responsive.
Verify upgrade completion and success.
1. When the workflow completes, check for a "Success" status in the Request View.
2. SSH to the rSeries device and verify the new image is installed and active:
```
SSH to rSeries host
# tmsh
tmsh# list sys software image
Name                                         Installed  Build    Built
BIGIP-21.0.0.1-0.0.13.ALL-F5OS.tar.bundle   yes        0.0.13   Apr 21 2026
```
3. Verify the device version matches the expected upgrade target:
4. Check that all system processes are running normally:
5. If the device is running rSeries tenants, verify tenants are coming back online and returning to Running state.
Validate post-upgrade functionality.
1. Verify F5 rSeries host device health using the F5 rSeries CPU and TMM Report workflow to confirm normal operation.
2. Test connectivity to the device management interface.
3. Verify all configured virtual services are active and responding to traffic.
4. Check system logs for any post-upgrade errors or warnings.
5. If running tenants, verify each tenant is in Running state and operational.
6. Run application health checks to ensure services are functioning normally post-upgrade.
Handle upgrade failures or rollback if necessary.
1. If the upgrade workflow reports a failure, review the error logs for the specific cause.
2. Common failure reasons include:
  - Device became unreachable during upgrade process
  - Insufficient disk space for upgrade operations
  - Corrupted or incompatible image file
  - Device hardware compatibility issue with new image
3. If rollback is available and enabled, the workflow may automatically attempt to restore the previous image.
4. If automatic rollback failed, use the RSeries Device Restore workflow with your previous backup to recover the device to its pre-upgrade state.
5. After recovery, investigate the root cause of the upgrade failure before attempting another upgrade.
Document upgrade completion and notify stakeholders.
1. Record the upgrade completion details:
  - Device name and IP address
  - Original image version and new image version
  - Upgrade start and completion timestamps
  - Total upgrade duration
  - Any issues encountered and resolutions
2. Notify stakeholders that the F5 rSeries host upgrade has completed successfully.
3. Update configuration management and CMDB records with the new image version.
4. Archive the upgrade logs for compliance and future reference.