Forum Discussion
F5 r2600 Tenants
- Jan 27, 2025
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.
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!!!
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