Splitting one device into several vCMP Guests
Hello,
I'm opening this case to interchange opinions regarding how to migrate one device with many objects (around several thousand nodes and several hundred VS) into smaller entities. I mean several vCMP Guests with smaller bunch of nodes and VS.
Taking into account that the 'big' device is under production, I would like to find a way to migrate this without taking too much risks.
My first approach is to prepare a custom configuration (with only the small set of VS/nodes of each new device) and migrate everything during a maintenance window using a command like '
load sys config
'
- PROS - It's not necessary to planning a strategy for migration.
- CONS - too much risky. I could forget to include something important in the config file.
My second approach is to disable Client VLAN access and migrate each VS and node gradually, but I have cases when Nodes and Clients share the same VLAN, so there is no way to create a new (replicated) VS with the same configuration in the same VLAN without interfering the production enviroment.
- PROS - permits to migrate the configuration gradually.
- CONS - not all the topologies permits client access isolation.
My third approach is to take advantage of config-sync device groups, trying to separate each group of VS in different device-groups, to synchronise part of the configuration of the 'big' device to the new members of the cluster (the new instances of vCMP Guests).
REF - https://support.f5.com/csp/article/K15496
- PROS - Less risk and fast.
- CONS - Requires to have already split the configuration in several Config-Sync groups, which it's not the case...
I would like to know your ideas and also if you have done something similar in the past. how was your impressions?
KR, Dario.