-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Offline mode for iseries or VE migration #47
Comments
@fjl80 could you give more details about the failing offline scenario? |
Hey,
When you work in offline mode you cant choose the destination version neither platform series . You can only choose Velos or rSeries (what about VEs or iseries)
![image](https://user-images.githubusercontent.com/54593030/161217681-584fda32-d5c7-4a3b-8ca3-2fd80f2076ac.png)
This customer I am working with needs to go from 5250V to i5800, so I cant do it in offline mode in my lab.
As far as I have checked in my lab (I don’t have a i5800) with a VE is that if I work in online mode I can migrate the config to a VE (the same config from the 5250V), so the journeys app recognize the VE and version correctly.
Is it clear my ask?
Tks
|
Yes, that is true. Currently Journeys App does not support offline migrations other than to VELOS tenants. |
Filed internal Jira SOLUTIONS-5766. |
Just adding my voice to supporting Offline mode for BIG-IP Classic. As is, Journeys is still an excellent tool! |
Is your feature request related to a problem? Please describe.
Being able to use the tool to migrate configurations in the offline mode not only for VELOS or rseries but also to VE or iseries
Describe the solution you'd like
When you work with the tool and want to migrate between old TMOS versions and new versions the offline mode doesnt work for VE or iseries devices, neither its possible to choose the TMOS release you would like to go
it would be nice to be able to work in the offline mode in that way, otherwise you need the new devices connected/installed to start working on the migration tasks
Tks
The text was updated successfully, but these errors were encountered: