Forum Discussion

ndubey2's avatar
ndubey2
Icon for Altocumulus rankAltocumulus
Jun 30, 2025

F5 rSeries deployment and migration

I need to deploy rSeries 5900 F5 LTM and also need to migrated services from vCMP boxes to new rSeries 5900. Can I simply download UCS file from existing vCMP and upload it on new rSeries? If not what will be the best way to migrate the services including network settings? 

 

Thanks,

16 Replies

    • ndubey2's avatar
      ndubey2
      Icon for Altocumulus rankAltocumulus

      Thanks Jeffrey_Granier​ for the suggestion, is Journey Migration Tool is free? and is there any guide available to use it? 
      One other question, currently vCMP is running on version 14.1.2.8, can we directly migrate the services from this version to rSeries? 

  • f51's avatar
    f51
    Icon for Cumulonimbus rankCumulonimbus

    Direct UCS import is not supported and may result in errors or an unusable configuration. As Jeffrey_Granier​  mentioned, you can use Jouneys as described.

    I encountered various issues during the Virprions to rSeries migration. I adjusted my plan and followed the steps below. And you can use as your plan B

    • Create and deploy a BIG-IP tenant (matching the required version) on the rSeries 
    • Assign the necessary VLANs and interfaces to the tenant from the F5OS-A layer.
    • Generate an SCF file :
      tmsh save /sys config file <filename>.scf
    • Before loading, review and edit the SCF file meaning Remove any vCMP-specific configuration blocks.
    • Transfer the SCF file to the new rSeries tenant and run : 
      tmsh load /sys config file <filename>.scf merge

     

  • 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

    • Nikoolayy1's avatar
      Nikoolayy1
      Icon for MVP rankMVP

      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​  ?

      • ndubey2's avatar
        ndubey2
        Icon for Altocumulus rankAltocumulus

        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. 

    • ndubey2's avatar
      ndubey2
      Icon for Altocumulus rankAltocumulus

      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_Kostas's avatar
        Injeyan_Kostas
        Icon for Cumulonimbus rankCumulonimbus

        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.

  • Hi ndubey2​  especially recommend you to check if the vlans and (LAG) trunk ports are defined correctly on F5OS. You cannot assign ports to trunk from within the tenant. Especially if you use more than one route domain. I recommend you to do this with this in mind.

    • ndubey2's avatar
      ndubey2
      Icon for Altocumulus rankAltocumulus

      Thanks for the response Ozzy​ I am planning configure VLAN and interfaces manually and then will create the tenants, hope, VLAN & interfaces config will be replicated automatically to tenant and then will upload the UCS using journey tool. 

  • Hello All Ozzy​ Jeffrey_Granier​ Injeyan_Kostas​ Nikoolayy1​, thanks for the response ! 

    If I understood correctly, I need to follow the below steps. 
    1- Build the new rSeries box, configure all the VLANs and interfaces manually. 
    2- create the tenant > download UCS file from vCMP guest > use Journey tool to make the UCS file compatible to rSeries > upload the UCS file on Tenant > verify all the configuration. 

    Do I also need to transfer the master-key before upload the UCS on tenant? 

    As my vCMP is running on version 14.x.x.x, would I be able to upload the using on new rSeries tenant? considering I can`t downgrade rSeries platform. 

    • Injeyan_Kostas's avatar
      Injeyan_Kostas
      Icon for Cumulonimbus rankCumulonimbus

      ndubey2​ rseries tenants support only 15.x.x and 17.x.x versions
      I would suggest upgrade vcmps to, at least, latest 15 version before migrating

      • ndubey2's avatar
        ndubey2
        Icon for Altocumulus rankAltocumulus

        Injeyan_Kostas​ those are EOL EOS, running in production. I don`t want to take any risk. Is there any other way please?