Forum Discussion
Nimbostratusmigration of ltm on GTM unit
We have currently a ltm cluster running in v9.4.7 . (yes i know , it's old & out of date) We have now deployed a new cluster with v.11.4 . We are actually in process of copying all pools & virtual servers & other configs (like profiles, monitors , etc...) onto the new cluster . So it will be running with an identicall config .We are also using same self IP's . But at this moment the new clusters is still isolated from network . (we only allow some vlans for management , but actuall traffic is blocked on network)
Purpose would be to isolate the old cluster at a certain moment from the network , and enable new cluster on network . As they are running with identicall configs , new clusters will take over . We have done similar migrations in the past , and it works fine.
But our current "old" cluster is also defined in a GTM pair . (as HA bigip under the server definitions) I can add now the new cluster also into GTM units . The self IP's used for this are available & reachable . But how will react GTM when the same VIP&port combinations are uploaded from different LTM pairs ? Does anybody have any experience with these kind of migration scenarios ?
1 Reply
Cory_50405Noctilucent
It shouldn't have an impact. All of your existing GTM configuration objects (wide IPs, pools, servers) reference content that exists on your "old" LTM pair. Adding "new" LTMs that have virtual servers/pools/nodes named the same will not cause any problems because they aren't referenced in the existing GTM config.
However, I don't know if your cutover will be as simple as you suspect. At least from the GTM's perspective, it knows about all of the virtual servers configured on the "old" LTM. All of your GTM pools reference those objects. When you remove the "old" LTM servers from the GTM config, all of those virtual servers are going to disappear out of your GTM pools.
