Restoring Config onto different unit - odd results

I have the exact same setup but ConfigSync.pl was not sufficient because we want to replicate things that are in bigip_base.conf. i.e. VLANs and interfaces which in our env are plentiful and changing enough that we'd rather just have them synced to DR.

 

 

We backup our configs off the device anyway so in a DR event we will restore the entire UCS config to our DR device. Our plan looks something like this:

 

 

1. SCP UCS from backup location to DR device

 

2. SSH to AOM address an run hostconsh

 

3. Restore the UCS to the DR box

 

b config install /path/to/config.ucs

 

4. Change the management IP back to what it is supposed to be

 

b mgmt 10.10.10.10 { netmask 255.255.255.0 }

 

b mgmt route default inet { gateway 10.10.10.1 }

 

5. Fix the hostname

 

b system { hostname our.f5.example.com }

 

6. Make the unit into a stand alone unit

 

b failover redundant disable

 

7. Test

 

8. Extinguish any hair that is on fire

 

 

The only thing we are considering doing to make it more automatic is to make sure that a copy of the config from UNIT 1 in the production HA pair is copied automatically to the DR unit. The reason we haven't is because the box we use to connect to the DR unit is the same box we keep the backups on. So if we can't get to that we can't do much anyway. I supposed if the backup were on the DR unit someone could console the F5 to get it up.

 

 

Hope this helps.

 

 

-Alan