NimbostratusHow do I perform a Hardware Upgrade 1600 to 2000
What is the best and safest way to move all configurations from a 1600 to a 2000 model? What is a safe way to replace the 1600 with a 2000 on a production network with minimal or no down time?
I have several single WEB servers behind a 1600 HA pair (serial fail over cables), and have to upgrade to 2000's. I have tried to copy the UCS file into the 2000, but it had a huge number of errors. So I manually tried to copy all configs one page at a time to the new 2000. I am still having an issue with one WEB server not coming up for users. I am using the default cert (client and server ssl) for the VS and suspect there is an ssl issue with the WEB server not recognizing the new 2000 VS. Our Data Center is very reluctant to give me any down time to try and bring the new 2000 online and drop the 1600's to troubleshoot.
Does anyone know if there is a way to get the 1600's to sync with the 2000's (documentation says no), or if there is a "best practice" to use when upgrading from older models? I tried putting them both online at the same time, and this caused a huge network issue at the chassis with the VM's, since the IP's were all matched up. The only idea I can think of is to force the Sys Admins to clone the WEB servers, and then put the new ones into a separate VLAN with separate IPs - then re-IP the new F5 to match (removing all self IPs and other VLANs) so it doesn't cause other network problems and hopefully be able to pinpoint the WEB server problem.
Does anyone have an idea of a better/safer way to try? I only have a production network to work with unfortunately. Thanks
