Last Modified: Dec 07, 2023
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.1.0, F5OS-C 1.1.1
Fixed In:
F5OS-C 1.1.2
Opened: Mar 10, 2021 Severity: 3-Major
After restoring a config backup, the system controller software assigns auto-generated IDs for the partitions. These auto-generated IDs are not mapped to blades and OpenShift cluster namespaces. This behavior causes the system to not work properly.
System goes into an Inoperative state for tenant deployments.
Reset the system to factory default settings using the system controller CLI, and then restore the backup.
The steps outlined below walk you through the entire process of taking a backup of the system, and then restoring the system to the factory default settings. The steps also include sample commands. Note: You must have console access to the system to complete this task. Running the reset-to-default command removes the management network. Backup ======= 1.) Backup tenant configs by logging into the tenant. Save the config, and then copy the config file backup to a safe, external location: tmsh save sys ucs /var/tmp/config.ucs 2.) Backup partition configs by logging into each partition. Backup the database, and then copy the database backup to a safe, external location: part2-1(config)# system database config-backup name <partition-backup-filename> result = Database backup successful. part2-1(config)# scp admin@@partitionIP:configs/<partition-backup-filename> <external-device-ip> 3.) Backup the controller config by logging into the system controller using a floating IP address, and then copy the backup config file to a safe, external location: syscon-2-active(config)# system database config-backup name <controller-backup-filename> response Succeeded. syscon-2-active(config)# scp root@floatingIP:/var/confd/configs/<controller-backup-filename> <external-machine-ip> Important: Once you execute the reset-to-default command, the system controller deletes the associated filesystems and backup files. So make sure to backup the system controller, tenant, and partition configs before continuing. 4.) Delete partition configs: part2-1(config)# system database reset-to-default proceed yes result Database reset-to-default successful. part2-1(config)# System message at 2021-03-11 00:02:21... Commit performed by admin via tcp using cli. 5.) Put all slots in the none-partition: syscon-2-active(config)# slots slot 1 partition none syscon-2-active(config)# slots slot 2 partition none syscon-2-active(config-slot-2)# commit Commit complete. 6.) Remove the partitions from the system controller: syscon-2-active(config)# no partitions partition part2 syscon-2-active(config)# no partitions partition part3 syscon-2-active(config)# commit Commit complete. 7.) Using a console connection, reset the controller config to factory defaults from the system controller CLI: syscon-2-active(config)# system database config reset-default-config true syscon-2-active(config)# commit Commit complete. 8.) Reboot the controllers. Once controllers are fully rebooted, proceed to the restore task. Restore ======= 1.) Set up the system controller mgmt network using the wizard/CLI. 2.) Import the backup from the external device to the system controller: ssh root@floatingip mkdir -p /var/confd/configs/ scp <external-machine>:<backup> /var/confd/configs/ 3.) Restore the controller config: syscon-1-active(config)# system database config-restore name <controller-backup> response Succeeded. 4.) Reboot the blades. 5.) To restore the partition config (including VLANs/tenants/interfaces/etc.), import the partition config to the active partition that is running on the controller (running 'show partitions' from the system controller CLI displays which controller is running the active partition): part2-2(config)# system database config-restore name <partition-backup> result Database restore successful. part2-2(config)# System message at 2021-03-11 01:10:34... Commit performed by admin via tcp using cli. 6.) Restore the tenant config once the tenant mgmt-ip is reachable. To do so, copy the config after the partition restores (where config.ucs is your .UCS filename): tmsh load sys ucs /var/tmp/config.ucs
Config backup and restore to factory default settings now works properly.