Forum Discussion
Nimbostratusmigrate from serie I to R. Cluster LTM-GTM
CirrostratusHey SuppEsp_AX
First of all, choose which method you would like to go with
- Parallel
- Big Bang
If 1 is selected, you can build the rSeries appliance with new objects (MGMT, VLANs, SELF-IP, VIRTUAL SERVER) and connect to the network. Migrate one by one applications to the new system using DNS and FW changes.
For the second option, if you have rack space available, mount the rSeries appliances in the same rack as the iSeries. Wire it up to the MGMT port. Define a new MGMT IP address/pool for it. For the DATA plane connections, either swap the cables from i to r during the maintenance window, or patch new cables for rSeries (up to you).
Since the DNS Sync group is tied to the software version, migrate the DNS-enabled appliances as a group. If not, you can migrate one pair at a time as well. But note that the DNS changes will not propagate to members running different versions.
Always remember that once DNS sync is enabled, the member with the latest commitID will push the configuration to the cluster.
It's recommended to run the gtm_add script when you bring a DNS appliance to the cluster. Remember, gtm_add uses a PULL approach rather than a PUSH. Run the script from the new/replaced device every time.
With the second approach, we have completed dozens of F5 migrations (SWAP DATA cables) with less than 10 minutes of downtime.
SuppEsp_AXThanks a lot for your response. Ill go to the second one (BINGBANG). iseries and tenant(rseries) will be the same 17.5.1.3.
My idea is to put the new R Series node in standby, remove the cables from the standby iSeries node, and connect them to the new R Series node instead.
My question is whether the synchronization from the active node (iSeries) to the passive node (R Series) would work correctly. Would the configuration synchronize (LTM/GTM) properly, or could it fail because the hardware is different (tenant)?
- Anoop_Jayadharan
As long as the devices in the cluster run an identical TMOS version, the sync should work.
Additionally, license and resource provisioning should align.
The following KB provides a detailed explanation.
- SuppEsp_AX
In order to add the new serie R device to the GTM existing cluster. Its only necesary add this command in the new member "gtm_add IP_EXISTING_MEMBER CLUSTER".
What about bigip_add? is this also need it?
