Forum Discussion
AlaaIbrahim
Dec 24, 2023Nimbostratus
Migration to rSeries using Journeys
Hello All! We were trying to migrate from VE Big-IP v16.1.3.2 to rSeries 2600. Removed all device group config from the configuration, configured VLANs, LAGs and Interfaces manually and tried to us...
yakai
Dec 26, 2023Cirrus
Hello,
I would suggest an other approach
From the migration point of view you are trying to migrate from a VE to an rSeries wich is not the same platform.
Therefore, there will be some concerns.
- If you have already configured networking, connect to the r2600 and copy /config/bigip_base.conf (vlan names should be the same)
- On the old VE run f5mku -K to retrieve the current master key, put it on notepad (we will use it soon)
- On the r2600 run f5mku -r <paste VE MasterKey>
- On the VE generate a fresh ucs
- On the r2600 upload the VE ucs, and run tmsh load sys ucs <ucsname> -no-license -no-platform-check
- Configuration will fail to load because of networking
- on r2600 rename the existing /config/bigip_base.conf to bigip-base.conf.bak1 upload the bigip_base.conf you downloaded in step1 and run tmsh load sys config base.
- The network config should be loaded
- Run tmsh load sys config, config should be able to load correctly
Note :
- Always take a backup ucs before any step
- Target r2600 should have at least the same licensing as the source bigip VE.
- If your F5 is in production env refer to F5 support for assistance
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects