Forum Discussion
CirrusLoad Config from one Single IP F5 to another Single IP F5
Hi All,
We use a ELB -> Active/Active F5 cluster in AWS, which we do without using the cloud scripts provided by F5 ( multiple reasons why ). My upgrade path in the past is to create two new EC2 F5 instances ( via a new AMI that matches the version of current code on the clsuter ), cluster them to the existng solution ( so we end up with 4 in the cluster ) and then upgrade the code on the new devices and remove them from the cluster ( so we then have 2 x Active/Active clusters of 2 F5s in each cluster ). These devices run LTM/ASM.
I am looking at ways off de-risking the upgrade, by skipping the clustering step if possible. As the devices are all Single IP devices I would like to:
- Still build 2 x New EC2 F5s
- Create a UCS from the old single IP F5s
- Load the UCS onto the new single IP F5s
- Cluster the new F5s as required
So the intent of this question is basically: can I load the UCS to a new single IP F5 from another single IP F5.
danielpennaTried "load sys ucs UCS_12th_June_2020.ucs no-license platform-migrate" and got the below errors. ( I masked IPs )
2020 Jun 12 07:41:27 new-build-May-2020 load_config_files: "/usr/bin/tmsh -n -g load sys config partitions all platform-migrate" - failed. -- 01071ac6:3: Invalid Self-IP '10.x.x.250/255.255.255.0': it must be the same as the management-IP '10.x.x.44/255.255.255.0' in VE-1NIC. Unexpected Error: Loading configuration process failed.
2020 Jun 12 07:41:29 new-build-May-2020 load_config_files: "/usr/bin/tmsh -n -g load sys config partitions all base " - failed. -- 01071ac6:3: Invalid Self-IP '10.x.x..250/255.255.255.0': it must be the same as the management-IP '10..x.x.44/255.255.255.0' in VE-1NIC. Unexpected Error: Loading configuration process failed.
As you can see, as a single IP F5 the SelfIP and management IP are the same.