Nimbostratus
NacreousThere will be some hassle involved and the procedure won't be straight-forward. Contact F5 professional services to get assistance with the migration, or find a freelance consultant to help you out.
If you want to try yourself, then prepare a UCS archive file, and attempt to restore configuration from it, using
no-platform-checkno-licence/var/log/ltm
NimbostratusDear Hannes, Many thanks for your reply. As one simpler and better solution, I think it's possible to revise the default "SCF" file of new LTMs based on current configurations, and then importing the new revised SCF file into TMOS v11.x
NacreousSCF formatting has changed a lot, it's not faster by any means. There are other problems, for instance, SCF does not include private keys and SSL certificates. That means the importing of those, and linking with relevant profiles will be yet another separate task to do. UCS adaptation works the best, but it's not the easiest of options for 1st time triers.
If you don't feel like using the UCS adaptation method, give a try to "playing with lego" approach. You can use "tmsh load sys config merge file /var/tmp/confFile.txt" to re-build configuration from a scratch. You will create multiple files, one containing nodes, the second file containing profiles, 3rd file containing health-check monitors... (you get the idea). You load them in one part of configuration at a time. The good thing about config merge option is that it also recognizes old v10 formatting (no need to re-invent the wheel with your own migration scripts), and it's also forgiving to obsolete/incorrect syntax (any unrecognized rubbish will just be discarded).
NimbostratusDear Hannes, Many thanks in advance for your tips, OK, as you mentioned, It seems that UCS archives are better choice in current situation. So let me think about what should I do in this regard... Certainly, if the need arises, I need your help again.