Forum Discussion
Eric_27158
Nimbostratus
NimbostratusConfigSync OK? Upgrade from 10.0.1(HF3) to 10.2(HF1)
Guys,
I have a scheduled upgrade this Saturday to take our pair of LTMs from 10.0.1(HF3) to 10.2(HF1). I wasn't sure if there was anything special I need to be wary of when rebooting each of these to the new volume. I figured I'd configsync before rebooting either, then reboot the backup, make sure it comes back, do a "Force to Standby" (assuming this Redundancy works fine between these versions) from the master, and then reboot the other guy. Let me know if I might hit any hurdles. Thanks for reading!
Eric
- Chris_Miller
Altostratus
You can definitely have those 2 versions in a pair. In the interest of minimizing downtime, are you doing network failover or voltage cable? 
Eric_27158I'm doing network failover- Eric_27158Unfortunately, I rebooted the backup and it didn't come up as nicely as expected. I cannot use RADIUS to authenticate against it and don't have a way in otherwise (that i can remember right now). The primary box says "Sync Recommended" but when I click that it gives me an error:
Checking configuration on local box and peer box...
Peer's IP address: 172.19.29.22
Error: The peer box is not a redundant pair.
BIGpipe parsing error:
01110034:3: This system needs to be a redundant pair and have a peer address specification.
Please help !
Thanks
Eric - Chris_MillerEric - did you switchboot before rebooting? It almost seems like your box loaded a different config...does the local admin account work?
- Chris_MillerAlso...on your active unit, just re-confirm that it's set to be in a pair and that it has a peer management address defined.
- Eric_27158I ended up having to call F5 Support because we missed doing the "reactivation" before upgrading.... Once that problem was solved, the two wouldn't peer or do a config sync. Unfortunately for us, we decided to complete the upgrade of the other F5 and bricked a harddrive, so now we're running on one F5 til we can get an RMA :-/ Oh well, we learned to reactivate before upgrading, that configsync doesn't really work between different codes, and don't change the baud rate via the LCD before an upgrade because the F5 chokes on anything but 19200 for some reason.
- Chris_MillerEric - I totally spaced on the license upgrade too. That's one of my favorite things about having Enterprise Manager for doing upgrades...it lets me know that the device needs to be re-licensed first.
- Eric_27158I'll have to look into that.... It was our first upgrade and we approached it Cisco-style, whoops! Thanks again for the tips
