Forum Discussion

Gemini6's avatar
Gemini6
Icon for Nimbostratus rankNimbostratus
Nov 21, 2020

F5 Migration

Hi Dears,   If I wanna migrate from two F5 devices in HA mode to a new one device, Should I extract the UCS file before splitting the HA or it is normal to generate the UCS file in HA mode?
application delivery
ASM Advanced WAF
BIG-IP
mshoaib's avatar
mshoaib
Icon for Cirrus rankCirrus

Hi Gemini6,

 

When you restore a HA UCS to a single unit, it will assume Active Unit config, IP addresses, etc and create IP conflict on the network.

 

I would setup a single unit on a network and disable its ports ( internal, external, dmz etc.) probably at the network switch level and made it accessible only from its management port.

 

Then I will restore the UCS to a single unit and verify the configuration. May be adjust IP addresses if needed and then bring it live on the network.

 

The single unit also assume there will be a standby unit and have HA config. You can either leave it as is or may be clean up.

 

I hope it helps.

 

-Muhammad

ecce's avatar
ecce
Icon for Cirrostratus rankCirrostratus
Nov 24, 2020

Theres more to consider. If you for example set the "forced offline" (or minimum blades up on VIPRION) that setting is saved in the bigDB and included in the UCS, and so the restored unit will be brought up in an offline mode. I've used that to ensure a device does not start process traffic after it is started.

 

If you're moving to another platform, check out the platform-migrate option when loading configuration. There's also a reset-trust option when loading config that might interest you if you load UCS config from HA devices.

 

Don't forget to copy the master key to the new unit. In HA it is replicated. If you restore config on a new device you need to first import the key.

 

It's also a good idea to do a tmsh load sys config verify before creating UCS so you know the UCS will actually load later and not bail out on a sytax error.