Forum Discussion
NimbostratusMigrate partitions 2600i to 2600r
Hello SuppEsp_AX
Tenants are actually virtual BIG-IP instances.
So you current deployment can be migrated as is to a tenant, with its partitions and everything else
NimbostratusSo several partition can belong to the same tenant, right?
OK, i thought one partition in one tenant.
So i have 3 partitions in 2600i to move to 2600r (which only can have one tenant by design)
Yes rseries run F5 OS which is just a hypervisor
On top you run VMs(tenant).
Each tenant is a classic BIG-IP as you know it.
- SuppEsp_AX
Migration Procedure (Summary)
Preparation (iSeries):
Same version old and new de
Generate a UCS backup: tmsh save sys ucs <file_name>. i series
Export the master key: f5mku -K.
Recommendation: Remove all "Trunk" objects from the configuration before migration to avoid physical interface conflicts. Done by Journeys.
Initial Configuration (rSeries):
Configure the base F5OS system (management IP, licenses, NTP).
Create a Tenant (BIG-IP virtual machine) with sufficient resources (vCPU, Memory, Disk).
Assign VLANs and physical interfaces to the Tenant at the F5OS layer.
Create all HA sync config
Configuration Migration (Journeys):
Copy the UCS file and the master key to /var/local/ucs/ on the new rSeries Tenant.
Install the master key on the Tenant: f5mku -r <key_value>.
Load the UCS using the migration option: tmsh load sys ucs <file_name> no-license platform-migrate.
I have a doubt for cutover or maintenance window. Which better:
Disconnect all cables in old I and change to new device R. Or keep active i device and add in standby a node serie R?
how do you do the jobs to change device?
thanks
