Migrate your BIG-IP Configuration using F5 Journeys App

The Journeys application assists F5 Customers with migrating a #BIG-IP configuration to a new F5 device. Choose a fully automate migration for ease of use and speed or a detailed, step-by-step process to ensure granular control. Both options are available via a well-documented API or intuitive GUI.

This demo shows how to use F5 #JourneysApp to perform a full migration or a per-application migration of a BIG-IP config to another BIG-IP:

00:00: open
0:05: Full Config migration - migrating a BIG-IP configuration from any version starting at 11.5.0 to a higher one, including next generation F5 Hardware VELOS and rSeries systems.
04:30: Per-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.


⬇️⬇️⬇️ JOIN THE COMMUNITY! ⬇️⬇️⬇️

DevCentral is an online community of technical peers dedicated to learning, exchanging ideas, and solving problems - together.

Find all our platform links ⬇️ and follow our Community Evangelists! 👋

Your Community Evangelists:

[alanlewis]

Possibly a daft question. But once I have installed journeys, as a docker image... what is the url to access it?
Its running under docker on my Synology, but the one thing that is not obvious from the repository, and one thing that is not shown in any video tutorial .. is the url suffix used to access it! :)

[alessandropc]

in offline deployment, In destination list only you have 2 systems diffents. In my case I only see VELOS and RSERIES.. Then, this is a tool limitation.

[Fraiquilom]

Is the "deployment and diagnostics" step really necessary to execute?
I'm asking this because we only have access to either the old device or the new one, so we cannot access both devices at the same time