Forum Discussion
F5 r2600 Tenants
Apologies, this has probably been discussed before and more than likely I don't know how to search for it so I am asking. I am new to F5 and have been tasked to update our r2600, I am trying to understand something about Tenants. Is a tenant, lack for a better work just a virtual machine that is running off of the hardware of the r2600? So far from what I been able to read up on is that I have 2 F5s that we call bigIP01 and 02, based on my understanding 01 and 02 are just virtual machines that run off of he hardware of the r2600. They are currently 15.1.8 and on the rseries I see that in the tenant management the image is also 01.1.8 All-F5OS bundle. So if I have to upgrade 01 and 02 to the latest version 17.1.2.1 do I also need to upgrade the rseries as well to 17.1.2.1 All-F5OS bundle or can I just upgrade 01 and 02 to the latest version and leave the rseries as is? I am assuming I have to do the rseries as well, still trying to find docs on how do upgrade rseries tenant management but if you can direct me to the right doc to do so would be greatly appreciated.
Thank you all in advance!!!
Warren
The tenant image "bundle" is just used one time to deploy the tenant. Once it's deployed and running, you'll use the BIGIP iso file to upgrade the software from within the tenant (either web interface or TMOS shell).
To "upgrade the physical r2600 box" you'll want to stop the tenant (set it to "provisioned") and install the appropriate F5OS-A version. I recommend v1.5.2-EHF today.
- MikePollock
Altocumulus
Yes, "just a VM" is accurate for all intents and purposes. You don't want the tenant deployment image for an upgrade, though. You'll download the BIGIP-x.x.x.iso file and import/upgrade from within the tenant (Systems > Software Management).
- wgranada
Altostratus
So I can go ahead and upgrade the tenant only (bigIp01 and 02) without having to upgrade the physical r2600 box correct so in other words if I go to the r2600 go to tenant images I see that it has only one image(BIGIP-15 1.8-0.0.7 All-F5OS bundle) so I can leave that as is and go to the virtual BIGIP01 and 02) which is currently BIGIP-15.1.8 iso and upgrade these 2 to BIGIP-17.1.2.1 iso. When completed we have this
R2600 - BIGIP-15 1.8-0.0.7 All-F5OS bundle
BIGP01 and 02 - BIGIP-17.1.2.1 iso
Thank you, Sir!
- MikePollock
Altocumulus
The tenant image "bundle" is just used one time to deploy the tenant. Once it's deployed and running, you'll use the BIGIP iso file to upgrade the software from within the tenant (either web interface or TMOS shell).
To "upgrade the physical r2600 box" you'll want to stop the tenant (set it to "provisioned") and install the appropriate F5OS-A version. I recommend v1.5.2-EHF today.
- wgranada
Altostratus
Sorry sometime I am a rock, but thank Mike for your help!! For the benefit of others who may read this, and agree...yeah this guy is a Rock!!! I understand now, and please correct me if I am wrong. So you can associate this to the concept virtual machines. In my case I have the hardware r2600 which only allows 1 tenant or 1 virtual machine per r2600 box. When you first deploy, in my case the r2600 and create a tenant (virtual machine). you first have to download the "bundle" image you want to use onto the r2600 under the tab Tenant Management. this image that you downloaded is only used when you first set up your tenant (virtual machine), once your tenant configured, all future upgrades to the tenant (virtual machine) is done on the tenant (virtual machine) and the hardware r2600 no longer comes into play. This is only for tenant software upgrade. You can upgrade the physical box itself if you need to but that is a different procedure than what I am trying to explain here.
Hope that makes sense
Thank you all!!!
F5OS (Velos and rSeries) use kubervirt to manage the tenants that are actually KVM virtual machines managed like pods in kubernetes/openshift infrastructure as F5OS is using kubernetes in it's architecture .
See:
Overview of the F5 rSeries system architecture
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com