Migrating older F5 BIG-IP has 3 partitions & Route Domains (RD) to new F5 BIG-IP with 2 partion & RD
Hi everyone, I have an old appliance with 3 partitions and each partition has its own route domain. I want to terminate one of the partitions in the new appliance due to a change in the design. Is there any way to remove the partition before moving it to the new appliances? Rather than migrating the configuration to the new appliance and starting deleting the configuration for a specific partition.
Migrate APM Config between versions
Hi everyone! I've been performing a large migration for a customer and all has been going fine. However, I'm now working on a set of appliances that have the APM feature enabled. What is the best way to perform an APM migration between two systems of different versions? The source is version 12.1.5.3. The destination appliance is version 14.1.4.1. The other caveat is that the source appliance's configuration resides in the Common partition. The destination appliance has a few partitions and I need to migrate this APM configuration into a partition. Not sure if that'll make a difference. I've been using the config file to perform these migrations. I've been parsing the configuration file and making modifications so that it imports into the correct partition on the new appliance. However, this is my first time migrating an APM configuration and the configuration seems a bit more complicated than LTM. Again, what is the best way to migrate this configuration? I've already read that I can't simply export/import if the versions are different. Should I just do it all manually? Thanks in advance for any suggestions you can provide.
UCS Platform Migration
Hi all, I'm looking for some assistance with moving the configuration from an old BIGIP to a new platform. Both boxes are running different code versions at the moment (old box is running 11.5.4, the new box is on 12.1.2), and are two different platforms. I haven't had much success with the platform-migrate option (the new BIGIP has a different hostname, and management address), and it throws up an error when loading it (and locks me out of the config utility at the same time!). I'm guessing that I can create an SCF on the old box, modify it, and load it onto the new box? However, i do have a concern that the SCF contains platform specific information and the software versions won't match. Would i need to merge the SCF from the old box, with an SCF on the new box? Any assistance would be much appreciated! Thanks.porting config from older hardware to newer (both v11.4.1)
Hi, We're upgrading 3 pairs from 1600 to 10000 units and I'm having trouble importing the configs between old and new. Any suggestions on the best way to do this? What I've done so far: started by getting basic networking and VLANs working, configuration, along with HA. All pairs now appear OK and configsync and failover is configured. then I imported certs by export/import and that appears OK. so I guess next up is irules/datagroups/pools/vips, etc... But I get tons of errors importing bigip.conf... datagroup files complaining (ignoring for now), most worrysome for now is: 01070313:3: Error reading key PEM file /config/filestore/files_d/Common_d/certificate_key_d/:Common:NAME_2.key_19719_1 for profile /Common/NAME: error:0906A065:PEM routines:PEM_do_header:bad decrypt Any ideas? Should I copy cert files manually from /Common_d ? Is there a way to partially import a UCS, except for networking info? (so I won't overwrite already done config)? Should I use tmsh or bash? ThanksNetscaler WAF Migration
hi guys, i have a migration scenario and need you inputs for best approach to migrate. currently i have following scenario: Firewall > Netscaler WAF > F5 LTM and need to replace the Netscaler WAF and F5 LTM with a new F5 LTM + WAF on same appliance. obviously, i can't migrate the learned traffic from old Netscaler WAF to New F5 LTM+WAF. actually i'm thinking to migrate the existing F5 LTM to the new F5 LTM+WAF and after completely finish of the migration, i will create the ASM policies on the new devices and keep it in learning mode. the scenario become as Firewall > Netscaler WAF > New F5 LTM+WAF and F5 WAF in learning mode, once the new F5 WAF learned the traffic, i will change the NAT from the Netscaler WAF to the NEW F5 LTM+WAF. what do you think about that? also if any one have another applicable idea here, please share.
BIG-IP LTM VE virtual hardware upgrade: Migrate to new virtual appliance or upgrade in place?
We have 2 instances of BIG-IP LTM VE deployed in separate environments and both were deployed to their respective vSphere environments several years ago and are still running at VMware HW Version 7, though the BIG-IP LTM versions running on them are currently 14.1.6. We have been upgrading them by ISO files (standard software upgrade procedure) without changing the VMs' configurations or virtual hardware versions. We have since upgraded our vSphere environments to 6.7 U3, and we plan to upgrade the BIG-IP LTM VE appliances we have to version 15.1.x from 14.1.x (and later, our physical F5 BIG-IP nodes from 13.1.x to 15.1.x). What is the best approach or path to upgrading both the virtual hardware and software versions running on them? Do I just upgrade the virtual HW in place to the latest available, or is it better/easier to deploy the 15.1.x VE OVA and just backup/copy/migrate the configs (UCS..?) over to the new appliance? If upgrading HW in place, does the VM need to be powered off? I want the most stable upgrade method possible, since the HW upgrade is a big jump up, especially when also upgrading a major OS version. Note, we can easily power the virtual F5 appliances down as these are in test environments.
Migration from F5-VE to F5 Hardware i2000 series
I am a novice with F5 BigIP. I am looking for a procedure as to how I can migrate my config from my existing configuration to the hardware appliance. F5-VE has interface names as 1.1,1.2,1.3... and i2000 series interface names are 1.0 2.0 - I am not sure where and how to edit the base config file.F5 LTM and GTM Migration from Hardware to vCMP Guest
Hello, I have a few questions in regards to the decision being made to move the LTM and GTM hardware platform to VCMP based platform. We are in the process of understanding the procedure to do the same and therefore need some help from you all guys. I have searched some of the Q&A and got some pretty good idea of the migration, however would need want to understand a new more things. Please answer my question if you have done a similar migration in the past. Three data centers, each has a pair of LTMs in HA and a pair of GTMs in standalone mode. All the six GTMs and LTMs are in iQuery full mesh. All the GTMs are already upgraded to vCMP guests. New LTM and GTM guests are already provisioned with a newer Management IPs, Self-IPs, and Listener IPs. Based on my understanding from various article, here is what supposed to be done. Configure the new LTM devices with the new management and Self-IPs (and leave them shutdown), install device certificates etc. Add the new LTM device1 in config-sync with the existing HA pair of LTM devices and get all the configuration from the existing production system. Add LTM device2 in HA mode with LTM device1 and sync the config. This way the newer devices will have the same exact configuration as that of production devices. We will later shutdown the interfaces on the existing hardware platform and enable the interfaces of the newer devices. How efficient is this process? Question 1: When the migration is complete from the older to newer systems, how would the GTMs update their wide-IPs with the Virtual Servers path pointing to newer devices?
