Welcome to the F5 BIG-IP Migration Assistant - Now the F5 Journeys App

[Chase_Abbott]

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/journeys

by default)

Feature requests

Ideas for enhancements are welcome here

For questions or further discussion please leave your comments below. Enjoy!

[JoshBecigneul]

Awesome. Is support for other cloud providers planned?

How does the AWS integration work? I don't see an option to specify that as a destination.

[jong_39455]

AWS support is coming in early 2018. Other cloud platforms are also planned including Azure and Google. No firm dates yet.

[Stanislas_Piro2]

Does it mean platform-migrate now support any BIGIP module?

previously, this feature supported only LTM migration.

[labilbo_133663]

Yes, platform-migrate on versions 12.1.3 or 13.1.0 or greater now supports all modules

[Stanislas_Piro2]

Nice, the documentation doesn't say that the command existed before with such limitation. I hope it will be changed! it can help people who want to migrate to previous versions even if last versions are recommended.

I would have preferred that it be available before. I migrated a BigIP with LTM, AFM, ASM, APM last summer to version 13.0 to vCMP and I had to migrate without this option because of this limitation.

[P_K]

Awesome tool! Right on time for our DR project.. But I keep getting this error

TypeError: Cannot read property 'description' of undefined

when tried to add devices.

[jong_39455]

PK: A couple questions:

1. Are you uploading a UCS by hand, or are you having Migration Assistant contact your devices for you?
2. What version of Migration Assistant are you working with?
3. What OS is running the machine where you are using Migration Assistant?

Thanks!

[jong_39455]

Stanislas: I will see about getting the documentation updated to mention the older version of platform-migrate in TMOS for older versions.

Thanks for the comments.

[P_K]

Jong: See my response below

1. I'm just trying to add devices from Add device tab. I'm not there yet to do the migration. 2. v1.0.1 3. Win10

[jong_39455]

PK: Thanks, I will have our dev team look into this.

[labilbo_133663]

PK: thanks for the feedback, I'll do my best to reproduce and fix that issue for the next release. If you're able to provide the BIG-IP model and software version, that should be a big help in producing the repro.

[P_K]

Will: I tried adding below devices

Big-IP 4000 running 11.5.4, vCMP guest running 12.1.2(w/ Latest HF) host is running 11.5.4(5250v), Big-IP VE running 12.1.2.. All the above resulted in below error Big-IP VE 13.1.0 was added to the list with no issues.

[labilbo_133663]

Ok thanks PK! Just one thing to note, the Migration Assistant won't be able to connect directly to the BIG-IP running 11.5.4 (it requires software versions 12.1 or greater), but it should be returning a more friendly notification so I'll get that fixed. If you'd like to migrate from an 11.5.4 config, the Migration Assistant 'archives' panel provides a tool for selecting a previously generated UCS from versions 11.1 or greater, which can then be used for migration. We'll get the TypeError issue fixed for next release- thanks again!

[Srini_87152]

Folks,

I dont see any software on github to download, is that something im wrong?

All im seeing .MD readle files.

Thx

Srini

[Stanislas_Piro2]

Click on the zip or tar.gz links

[Srini_87152]

yes,i did and unzipd those..all im seeing FAQ,README,SETUP and SUPPORT .md files and one folder with resources[ .png files].

Thx

Srini

[jong_39455]

Hi Srini,

This link should contain the executables for the tool:

https://github.com/f5devcentral/f5-big-ip-migration-assistant/releases

Does that work for you?

[Srini_87152]

Hi Jong,

I dont see any executable files, all it has just .md and .png file.

Thx

Srini

[jong_39455]

Srini,

I apologize, I believe if you reload the page you should now see executables.

[Srini_87152]

Thanks Jong,im able see now.

Thx

Srini

[jong_39455]

All 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.

[Rickwho]

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?

[Laurent_Boutet_]

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

[labilbo_133663]

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?

[jong_39455]

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

[zipzip_65424]

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.

[svs]

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!

[jong_39455]

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 .

[Joe_Reifel]

Hi @sp,

An alternative to the Migration Assistant is to just follow the steps outlined in K82540512: Overview of the UCS archive platform-migrate option.

[Nikunj]

Can this be used to migrate config from hardware to VE?

[svs]

Yes, this is possible. The difference between `platform-migrate` and the migration tools is, that the tools supports migrating interfaces, using an assistant, while platform migrate will just omit all device-specific configuration, like interfaces and trunks.

[ghchee]

Hi Team,

Able to share F5 BIG-IP Migration Assistant tools for download?

[Mrad]

hello does this tool cover the migration from I-series to Rseries

[RomanJ]

Hello @Mrad yes Journeys App supports migration from Series to rSeries either using the full migration or per-app flow. Thanks!

[Nikoolayy1]

If you modify docker compose file a little you can have the VM to expose the public ip address to connect to it.

In the docker compose file:

- DB_IP=${DB_IP}
command:
runserver

ports:
- "${DB_IP}:${JOURNEYS_PORT}:443"

And In the .env file add:

DB_IP=x.x.x.x

If the docker compose ip just redeploy:

docker compose down

docker compose up -d