Forum Discussion
Workaround to avoid password change after ucs restore
Hello,
I am currently working on a migration projet using JOURNEYS.
One small issue we are facing is that after restoring ucs from old bigip on a new tenant after the JOURNEYS processing, the admin and root account password's are changed.
Off course, it is possible to change them if you are still connected through SSH with :
tmsh modify auth password root
tmsh modify auth password admin
But if you forget it, or lost your session, it become much more complicated.
One workaround I found is to open the .ucs as an archive and remove the "/etc/shadow" file before the restoration.
I have found no articles about this solution, and no drawback yet.
Feel free to let me know if there is issues I have not seen yet or if it a tips you already know,
Cheers,
SamCo
1 Reply
- f51
Cumulonimbus
Hi SamCo,
I have encountered this issue before when importing the UCS and unable to access the F5 (due to incorrect passwords).
I have tried your described method in my lab and successfully loaded the file.
FYI, I’ve tested multiple incorrect passwords to see if the accounts get locked or log any activity, but they didn’t.
Recent Discussions
Related Content
* 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