Forum Discussion
AltostratusBIGIP VE (ESXi) upgrade from v13.0 to v13.1
I can't find any f5 doc which suggest how to upgrade from v13.0 to v13.1.
Any help?
kolom_265617Cirrostratus
Hello flypast, This should be a normal & easy upgrade of uploading the image for 13.1 , confirm the integrity of the iso file by checking the md5sum , install the image to a new partition and change the boot location .
flypastHi Kolom, Thank you very much for your response!
What you suggest is for an "Update". I guess from 13.0 to 13.1 is an "upgrade"
From F5 link below, I see the "upgrade" process is:
Upgrading BIG-IP VE to 13.0To upgrade to 13.0, install BIG-IP® VE on a new virtual machine and then contact F5® to transfer your license.For the BIG-IP VE virtual machine you want to upgrade, save a UCS file offline.Important: A single configuration file (SCF) is not sufficient.Note the host name. You will need it when you restore the UCS.You can find the host name by typing tmsh show sys global-settings hostname.In the VMware vSphere client, power off the BIG-IP VE virtual machine.Deploy the current version of BIG-IP VE on a new virtual machine. See Deploying BIG-IP® VE on ESXi for details.Copy the UCS to /var/local/ucs/ on the newly deployed BIG-IP VE virtual machine.Run the command tmsh modify sys global-settings hostname xxx.xxx, where xxx.xxx is the host name.Restore the UCS on the new machine. For example, if the UCS is named webfarm1.ucs and is stored in /var/local/ucs, then the restoration command is tmsh load sys ucs webfarm1.
Please correct me if I am wrong.
- kolom_265617
Most of the Time , both update and upgrade are used in the context of updating the software version to a newer one using the same VM . Upgrading by installing a new VM is considered a fresh installation.
If you don't want to increase the assigned resources to the BIGIP VE , i would go with the update procedure mentioned in the link.
kolomHello flypast, This should be a normal & easy upgrade of uploading the image for 13.1 , confirm the integrity of the iso file by checking the md5sum , install the image to a new partition and change the boot location .
- flypast
Hi Kolom, Thank you very much for your response!
What you suggest is for an "Update". I guess from 13.0 to 13.1 is an "upgrade"
From F5 link below, I see the "upgrade" process is:
Upgrading BIG-IP VE to 13.0To upgrade to 13.0, install BIG-IP® VE on a new virtual machine and then contact F5® to transfer your license.For the BIG-IP VE virtual machine you want to upgrade, save a UCS file offline.Important: A single configuration file (SCF) is not sufficient.Note the host name. You will need it when you restore the UCS.You can find the host name by typing tmsh show sys global-settings hostname.In the VMware vSphere client, power off the BIG-IP VE virtual machine.Deploy the current version of BIG-IP VE on a new virtual machine. See Deploying BIG-IP® VE on ESXi for details.Copy the UCS to /var/local/ucs/ on the newly deployed BIG-IP VE virtual machine.Run the command tmsh modify sys global-settings hostname xxx.xxx, where xxx.xxx is the host name.Restore the UCS on the new machine. For example, if the UCS is named webfarm1.ucs and is stored in /var/local/ucs, then the restoration command is tmsh load sys ucs webfarm1.
Please correct me if I am wrong.
- kolom
Most of the Time , both update and upgrade are used in the context of updating the software version to a newer one using the same VM . Upgrading by installing a new VM is considered a fresh installation.
If you don't want to increase the assigned resources to the BIGIP VE , i would go with the update procedure mentioned in the link.