Forum Discussion
Upgrade from 10.2.3 to 12.0.0
Hello,
I'm upgrading a pair of BIG-IP LTM VE 10.2.3(112) to the latest 12.0.0(606) in the lab. They're in active/standby mode with only one module provisioned: LTM. Network failover is enabled. There is one VS configured (serving FTP) with Connection Mirroring checked. The Default Persistence Profile for the FTP VS is set to source_addr (with Mirror Persistence enabled).
The failover of 10.2.3(112)'s works as expected. I can force standby to active and vice versa without losing active FTP connections. I also see mirrored connections (incl. persistent) on both units, so all is good.
I'm following https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-upgrade-active-standby-11-6-0.html for the upgrade.
I force standby unit (Device B) to offline, update the software and reboot. The status of Device B changes to Standalone (ONLINE STANDBY) after the reboot. After that, I force active unit (Device A) to offline, all current FTP sessions are dropped and reconnected to Device B. I update the software on Device A, reboot and sync both units.
So I end up with Device B being Active and Device A being Standby.
Here comes my question. I don't see any mirrored connections on Standby unit at this stage, so if I force Device A to become Active FTP connections are dropped again. Once I perform this initial switchover, I can see mirrored connections on both units and further changes from Standby to Active don't result in FTP interruptions. Is this expected? I mean is it normal that I don't see mirrored connections on Standby unit immediately after the reboot?
Thank you.
2 Replies
im not sure i totally understand your situation. but if you are wondering about the moment where you have one 10.2.3 box and one 12.0 box then at that stage i would expect mirroring not to work correctly. if im not mistaken your are even advised to turn off mirroring during an upgrade.
see also: https://devcentral.f5.com/questions/disable-mirroring-on-ha-pair
- nov1ce_120072
Nimbostratus
Thanks! The first outage is clear to me, I was wondering about the outage when both boxes run 12.0.
You see, when you start the upgrade Device A is in active mode and Device B is in standby. When you finish with the upgrade, Device B is active and Device A is in standby. When you initially force Device A to become active, this is where the outage happens. Once it's done, things get back to normal and both units keep connections table.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com