Forum Discussion
F5 rSeries deployment and migration
- Aug 29, 2025
I used the UCS platform-migrate approach to migrate vCMP guest to rSeries Tenant and it worked perfectly fine as I have all the config. Below is the link.
I will personally always find it easier to create a new Tenant/VM, add it as node to existing cluster and let it sync.
The only drawback is you need new Self IPs and most probably new Firewall rules.
You can always remove the standby node from the cluster, use it's IPs to the new one and add it to the cluster
- Nikoolayy1Jul 02, 2025
MVP
The issue could be if the versions are different as for example going from 14.1.x to 15.1.x/17.1.x on the new platform. Also here is not the case but for devices without vCMP to be migrated to a Tenant without the journeys tool that will clean the USC config from things like vlan/interface/trunk but with the existing cluster option have you tried that Injeyan_Kostas ?
- ndubey2Jul 02, 2025
Cirrus
Nikoolayy1 I am migrating from version 14.1.2.8 to new rSeries and I believe, tenants need to be created manually, even if I upload the vCMP host UCS file having guest configuration, it will not work, is that correct?
and once rSeries platform the prepared with network layer configuration, will upload the guest UCS file on tenants, pls let me know if you agree with this approach. - Injeyan_KostasJul 03, 2025
Nacreous
Nikoolayy1 I have always migrate to same version. Without vcmp works fine too.
- ndubey2Jul 03, 2025
Cirrus
Hello Injeyan_Kostas vCMP guests are already in HA and in production. How can we create a new Tenant on a new box and bring it in HA with old one. Don`t you think there would be compatibility issue or it will impact the production?
- Injeyan_KostasJul 03, 2025
Nacreous
Hello ndubey2,
Of course you can as far the new tenats run on the same version as your current cluster.
You will need to create first the interface, lags, vlans etc on F5OS level.
Create the tenant, assign the appropriate vlans.
Create self IPs
Add it in the cluster
You could also mark it offline before add it to cluster just to prevent being promoted to active by any chance.
Then during a maintenace window you can failover traffic to new tenant and test.
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