What is the best practice for migrating from iseries to rseries?

Hi Herman2024,

For me, the best migration strategy is:

1. Upgrade the i-series to v15.1.x, in this case, you could set offline one of the current devices and create a cluster with the new r-series device, make a failover, and test the services "it only applies if APM is not provisioned"
2. If APM is provisioned you have two options:
   1. Big bang - migrate the configs into new devices " I recommend updating the i-seres to avoid possible issues in the config migration", so in this case, you have to disable the current devices and then enable the new devices "at the SW level is the best option because you can configure the HA between the devices only provisioning the vlan for this propose but you have to replace the current IPs in the config"
   2. Migrate by services with a different networking config - In this case, the idea is migrating by group of services or VIPs, you have to keep a different network configuration, and in the new devices you have to disable the ARP, for VIPs and SNAT and the migration is easy, you have to disable ARP in the current devices for a group of services and enable in the new devices.

Note: If your current i-series can´t be upgraded because the support contract is over, you could contact your F5 SE to request a temporary license to upgrade the devices. 

I hope it works.

Herman2024​ What procedure did you follow and any issues you saw? I was looking at some documentation and had few questions with the procedure I was thinking to follow

1. From the iSeries platform (iF5-A(Active) and iF5-B(Standby)), need to take backups and move them to the /shared folder and edit the UCS file(bigip_base.conf for LTM and bigip_gtm.conf for GTM) by modifying the Management Ips, Adding new Vlans(as I want to have new subnet for VIPs), creating new self IPs for all the node subnets and edit the existing domain to a new domain(ex:ab.xyz.com to dc.xyz.com). Modified files are iF5-A.ucs and iF5-B.ucs.                                                                                                                                                 - We need to remove trunk config from the new UCS file(K50152613), so do we remove the full config including the config where trunk has all the vlans added along with deleting the trunk interface? We have to manually add the vlans and Trunks through F5OS?                                                                                                  -How can we edit iApps as they are no longer supported? 
2. On the new R-Series F5s, Bring them up and configure them for HA. Now when I copy using "platform migrate"  On the R-Series rF5-A(Active) and rF5-B(Standby), tmsh load sys ucs /tmp/iF5-A.ucs platform-migrate for rF5-A      tmsh load sys ucs /tmp/iF5-B.ucs platform-migrate for rF5-B.                                                I see that in the KB article, it saves the non compatible config in /var/local/ucs/platform_migrate_ignored_objects

           Based on this K82540512, Looks like interfaces, trunks and Vlans are not copied? Does it copy the VIPs, nodes, pool members without Vlans? and should we be doing this after manually creating the Trunks and Vlans on F5OS?