Welcome to the F5 BIG-IP Migration Assistant - Now the F5 Journeys App
The older F5 BIG-IP Migration Assistant is deprecated and is replaced by F5 Journeys.
Welcome to the F5 Journeys App - BIG-IP Upgrade and Migration Utility
F5 Journeys App Readme @ Github
What is it?
The F5® Journeys BIG-IP upgrade and migration utility is a tool freely distributed by F5 to facilitate migrating BIG-IP configurations between different platforms. F5 Journeys is a downloadable assistant that coordinates the logistics required to migrate a BIG-IP configuration from one BIG-IP instance to another.
Why do I need it?
JOURNEYS is an application designed to assist F5 Customers with migrating a BIG-IP configuration to a new F5 device and enable new ways of migrating.
Supported journeys:
- Full Config migration - migrating a BIG-IP configuration from any version starting at 11.5.0 to a higher one, including VELOS and rSeries systems.
- Application Service migration - migrating mission critical Applications and their dependencies to a new AS3 configuration and deploying it to a BIG-IP instance of choice.
What does it do?
It does a bunch of stuff:
- Loading UCS or UCS+AS3 source configurations
- Flagging source configuration feature parity gaps and fixing them with provided built-in solutions
- Load validation
- Deployment of the updated configuration to a destination device, including VELOS and rSeries VM tenants
- Post-migration diagnostics
- Generating detailed PDF reports at every stage of the journey
Full config BIG-IP migrations are supported for software paths according to the following matrix:
| DEST | |||||||
|---|---|---|---|---|---|---|---|
| X | 11.x | 12.x | 13.x | 14.x | 15.x | 16.x | |
| <11.5 | X | X | X | X^ | X^ | ||
| 12.x | X | X | X | X^ | |||
| SRC | 13.x | X | X | X | |||
| 14.x | X | X | X | ||||
| 15.x | X | X | |||||
| 16.x |
How does it work?
F5 Journeys App manages the logistics of a configuration migration. The F5 Journeys App either generates or accepts a UCS file from you, prompts you for a destination BIG-IP instance, and manages the migration. The destination BIG-IP instance has a tmsh command that performs the migration from a UCS to a running system. F5 Journeys uses this tmsh command to accomplish the migration using the platform-migrate option (see more details K82540512) .
The F5 Journeys App prompts you to enter a source BIG-IP (or upload a UCS file), the master key password, and destination BIG-IP instance. Once the tool obtains this information, it allows you to migrate the source BIG-IP configuration to the destination BIG-IP instance either entirely or in a per-application depending what you choose.
Where do I obtain it?
F5 Journeys App Readme @ Github
What can go wrong?
Bug reporting
Let us know if something went wrong. By reporting issues, you support development of this project and get a chance of having it fixed soon. Please use bug template available here and attach the journeys.log file from the working directory (
/tmp/journeysFeature requests
Ideas for enhancements are welcome here
For questions or further discussion please leave your comments below. Enjoy!
Updated Jun 06, 2023
Version 3.0
Chase_Abbott
Employee
EmployeeAll in this thread -
I enabled Issues in the github repository:
https://github.com/f5devcentral/f5-big-ip-migration-assistant/issues
If you run into any issues with the software itself, please file an issue at the url above, and we will do our best to address it.
I apologize for the confusion in this thread trying to track and respond to issues you have encountered.
I will also update the documentation to reference the github Issues rather than this article for support.
RickwhoNimbostratus
I tried using this for my source running 12.1.2 to my already licensed target running 12.1.3, and the tool hangs at one of the first steps, "Licensing target device". I did enter the registration key I copied from the target into the tool, and don't have ability to uncheck the "License Device" option. How do I make it work?
Hello, I had a little issue between 13.1.0.2 and 13.1.0.1. The tool complains the the 13.1.0.2 is oldest than 13.1.0.1, so I wasn't able to migrate from 13.1.0.1 to 13.1.0.2 VE. I suspect the build versions confuse the tool. :) Thanks
Hi Laurent, we added support for nth element versioning in release 1.0.3 ( https://github.com/f5devcentral/f5-big-ip-migration-assistant/releases/tag/v1.0.3 )- could you give that a try?
Rickwho and Laurent, we will look into these issues - I know it's a hassle, but is there any chance you can register these as issues in github for us? Tracking bugs in this thread is fraught with peril, and I wouldn't want to lose track of your problems.
I would enter them myself, but then I wouldn't want you to not know when they get updated.
Thanks!
https://github.com/f5devcentral/f5-big-ip-migration-assistant/issues
The platform-migrate option causes the UCS loader to ignore configuration objects related to the following items: •Interfaces •Interface bundles •High availability (HA) groups •Trunks •Virtual Local Area Networks (VLANs) •Self IP addresses •Port mirroring •Certificates •Management IP and route •Traffic groups •Trust domains •Hardwired failover •Route domains •Layer 2 (L2) forwarding •Spanning Tree Protocol (STP)
Apparently, now is just ignores mgmt IP, mgmt route, interface and join object referencing interface.
Are there plans to fix this please.
svsCirrostratus
Thanks for providing this tool. Unfortunately it doesn't work for me. During the migration process the first step is the license activation, but this process hangs without any message. After around 30 minutes I've stopped the process.
Additionally I cannot see the greater value in using this tool, instead of using UCS platform-migrate import. It would be awesome to have the chance of selecting the objects (or just the object types) which should be migrated, but it doesn't seem to work like this.
Cheers
- rafaelbn
Hello guys!
I tried using this tool to migrate from a viprion to a virtual edition. Viprion was running v12.1.1-HF2 and the VE was on v12.1.3.
Got a LACP error
Jul 16 18:56:13 localhost emerg load_config_files: "/usr/bin/tmsh -n -g load sys config partitions all platform-migrate" - failed. -- 01070687:3: Link Aggregation Control Protocol (LACP) is not supported on this platform. Unexpected Error: Loading configuration process failed.This migration in particular had some partitions with route-domains and on the main screen I saw no VLAN from the other partitions. Just VLANs from de /Common.
Any thoughts?
Cheers!
Hey @rafaelbn,
I'm sorry to inform you that development of this tool has been put on hold for now. I'll update the article to reflect this fact.
- SP_266134
Can we use this tool to migrate LTM VE 13.0 on prem to Azure F5. Is this product discontinued or still we can use for our migration .
