Migration from i5800 to r5800

Question

Hi,Request to help me migration plan step by step from i5800 to r5800. In our production we are using i5800 hardware box with Active and standby HA link with version 17.1.2 and running both LTM and GTM. The hardware i5800 is going to end of support we are planning to migrate to hardware r5800. I request to help me step by step plan without any production impact and also help for the plan like tenant to tenant moving to new hardware to test and move rest of the configuration.Please let me know if any more information is required.Thanks in advance!&nbsp;

injeyan_kostas · Answer

Hello,&nbsp;My approach would be to a create new tenant in r5800 assign the same vlans as current cluster but with new self ips.&nbsp;Add these new self ips to whatever fw rules you may have for the old ones.Then add the new tenant as member of the existing cluster.Sync and confirm that new node is able to communicate with as many pools as the active one.During a maintenance window failover to new node and confirm functionality.If everything is fine proceed with the other r5800At the end you will have a cluster of 4 and you can start decommissioning i5800.&nbsp;Another option is to shutdown standby i5800, use it's self ips to new r5800 tenant and add it to the cluster. Confirm again connectivity, failover, check functionality etc.This way you do need new ips.

ayish · Answer

&nbsp;Hello injeyan,&nbsp;Thanks for your reply. I hope your doing well.&nbsp;I was expecting some step by step procedure for migration but in the reply I see only for self ip migration anyhow thanks for your reply.Is there any chance to get migration document and details about rseries 5800 model how differ from i5800 wrt gui interface and other parameters tab.Also, any guide to transfer each partition migration.I also studied one of F5 document that rseries doesn't have HA between hardware box instead it has tenants redundancy with HA is this correct like what are the differences between i5800 and r5800.&nbsp;Please help me if any clear document for migration i5800 to r5800 for reference.&nbsp;Thanks in advance.&nbsp;Regards,Moula Ali

injeyan_kostas · Answer

Hi Ayish​&nbsp;In the scenario I described, you only see the Self IPs because you’re essentially creating a new, empty BIG-IP with fresh Self IPs, adding it to the existing cluster, and then syncing it. This means there’s no need to manually migrate any configuration, it will all be synchronized automatically.Regarding the differences between iSeries and rSeries:rSeries runs F5OS, which is a completely different operating system that acts as a hypervisor.On top of F5OS, you deploy BIG-IP instances (called tenants).Like any hypervisor, you must first configure all networking in F5OS (interfaces, trunks, VLANs, etc.) and then assign the VLANs to the BIG-IP tenants.F5OS itself is standalone, so as you correctly noted, there is no HA at the F5OS layer. However, HA is fully supported at the tenant (BIG-IP) level, just as with traditional BIG-IP deployments.If you’ve worked with vCMP before, the concept is almost identical.Regarding partitions, these will also be synchronized as part of the cluster sync process.For the initial configuration of F5OS, you can refer to:https://techdocs.f5.com/en-us/hardware/f5-rseries-systems-getting-started/gs-system-initial-config.htmlOnce the BIG-IP tenant is created, the workflow is exactly the same as you’re already familiar with.

anothersean · Answer

HiHave you applied this procedure to any production environment already?&nbsp;Sean.

Forum Discussion

AppWorld Berlin 2026 – iRules Contest Winning Results

One Quick Step to Make your website AI-Agent/MCP Ready with an iRule

IPv8 Would Fix My Routing Tables. It Will Never Ship.

Recent Discussions

Related Content

Migrate Configs from 5250 to i5800, MINUS HOST specific

Migrating between sites using stretched VLANs

Seamless Application Migration Across Heterogeneous Environments with F5 BIG-IP

App Migration across Heterogeneous Environments using F5 Distributed Cloud

App Migration and Portability with Equinix Fabric and F5 Distributed Cloud CE