Forum Discussion
Move "complet" VS settings - TEST to PROD
Hello All,
In our setup we are using TEST and PROD env. When we are developing a new VS many of profiles (like HTTP, SSL profiles, etc...) are customised and many other settings (like Policy, iRules, monitors ) are added as new to VS.
I'd like to ask what's the best approach/method to move VS configuration from TEST F5 to PROD F5? I mean how to "move" entire VS configuration (including modified profiles and settings) from TEST to PROD?
Thank you.
Hi zandar,
you may play around with a partial configuration export/import using the TMSH utility.
1.) SSH to your TEST-System and launch TMSH
2.) Export the desired configuration via the various LIST commands
(tmos) list ltm virtual VS_HTTP_210 ltm virtual VS_HTTP_210 { destination 172.21.17.210%1:http ip-protocol tcp mask 255.255.255.255 profiles { http { } wam-tcp-lan-optimized { } } rules { HTTP_210 } source 0.0.0.0%1/0 source-address-translation { type automap } translate-address enabled translate-port enabled vs-index 41 }
Note: Also export the related configuration (e.g. Pools, Monitors, Profiles, etc) by using the various TMSH list commands.
3.) Combine the individual exports into a single txt file and customize the settings as needed (changing IPs, naming conventions used for Test/Prod, etc.)
4.) SSH to your Prod-System and launch TMSH
5.) Import the previously exported and already customize configuration exports via configuration merges.
(tmos) load sys config merge from-terminal Enter configuration. Press CTRL-D to submit or CTRL-C to cancel.
6.) Paste the customized configuration export and hit CTRL-D
Loading configuration...
7.) Enjoy your sparetime^^ 😉
Cheers, Kai
How many virtual servers are you trying to move.
I wouldn't move anything from test to Production, in case of error. I would rebuild fresh.
- zandar_304392Nimbostratus
Hi,
usually we are moving 1-2 VS. It is rare situation when we are moving more than that. By moving I mean "best way to configure already TESTed configuration to PROD".
While numerous of settings and profiles in VS are highly customised, you can imagine the clicking the new VS by hard is not comfortable way to configure it. Moreover I believe there is even better chance you'll make some "misclick".
Cheers,
zandar
Y
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