Error Message when installing 13.0HF3
This isn't a question, just a solution/FYI because I couldn't find this issue when searching DevCentral for (Failure testing installer update status in /shared/images/) on VCMP. I ran into an issue when attempting to upgrade from 13.0HF2 to 13.0HF3 on my vCMP guest. The 13.0 ISO installed correctly to an empty boot location. However, I got an error message when I attempted to install Hotfix3 on that same partition. There's a bug ID for this (665725) and no fix yet, but the workaround is to restart the lind process on the guest. [notmylogin@notmyguestname-f5-prod:/S1-green-P:ForcedOffline:Disconnected] ~ clsh bigstart restart lind This allowed me to continue the software installation without issue. Hope that helps.
BIG-IP : upgrade fails to transfer configuration
BIG-IP 11.4.0 Build 2384.0 Final I want to upgrade to 11.4.1 retaining current configuration. I downloaded BIGIP-11.4.1.608.0.iso and uploaded to BIG-IP and installed to volume HD1.2 ( HD1.1 has 11.4.0 ). System > Software Management : Boot Locations I select HD1.2 , set Install Configuration to Yes , set Source Volume = "HD1.1:11.4.0" , and click Activate However on reboot the message is displayed : The configuration has not yet loaded. If this message persists, it may indicate a configuration problem.
How to best Create Big-IP lab on VE from Physical production configuration to test upgrade?
I'm in the process of upgrading our physical Big-IP LTMs and would like to import as much of the configuration as possible (while maintaining VE management configuration) into a virtual edition lab to perform a mock upgrade. I exported the SCF from the source physical and the VE for comparison. I found K81271448: Merging BIG-IP configuration objects into the running configuration using tmsh https://support.f5.com/csp/article/K81271448 So it looks like I could remove portions from physical source configuration file and massage the rest, and merge. I converted the vlans to use the last interface on the VE (and disconnected from the VM). But which parts of the config should I keep, and which should I remove prior to merging? I also read that a UCS configuration might be more appropriate to export and import. What is the best recommendation to migrate production Big-IP configuration to a VE lab to test an upgrade prior to actual upgrade?
Viprion Upgrade - How to make sure existing config is copied
Hi, We've got a number of Viprions (No vCMP, 1 blade) which I need to upgrade from 11.4.1 to 11.5.1. However when I get to the Boot Locations the option to copy config is greyed out and set to no. As these boxes are in a remote location, with no serial connectivity I don't really want to reboot without the existing config being copied over (especially the bigip_base.conf). Surprised that there isn't a SOL document (that I can find!) which explains the situation as having the config not come over is a major issue (and drawback). Can somebody confirm the precises steps to carry out to upgrade a Viprion and make the config move over as well. Many thanks in advancesync failed. The requested parent profile (tcp) was not found. upgrading two boxes from 11.2 - 11.6
I upgraded a box Friday night with no problem and let it run active in production for a few days. Today I ran the upgrade on the other box and when I went to sync the config to the newest box I get this StatusSync Failed SummaryA validation error occurred while syncing to a remote device DetailsSync error on 01: Load failed from 02 01020036:3: The requested parent profile (tcp) was not found. Recommended action: Review the error message and determine corrective action on the device I looked at my protocol profiles and see the few that I made and it lists the parent profiles like tcp-lan-optimized and tcp-wan-optimized. When I check on the parents.. they are there. Any thoughts?Does VIPRION support 2 clusters in the same chassis
Though a 3rd or 4th blade would automatically be added to the 1st cluster, can I establish a 2nd cluster and maintain 2x2? The use case is supporting dual versioning in production for greenfield on v11 and legacy on v10. There is already HA to a 2nd chassis, so HA would also be 2x2--2x2. Assume there is a valid business reason to not upgrade the chassis from v10 to v11 due to a limited maintenance window.
Upgrading from Version 10 to version 11 - Synchronization configs lost
Hello, I'm in the process of upgrading our version 10.2.4 devices (LTM 6900s) to version 11.5.1. When I boot into the new version, however, the device loses all information of the other devices in the HA pair, and becomes a standalone device that can't be synced. Is there a particular reason as to why this could happen? Thanks, Ryan
APM VE hotfix upgrade 11.6
I want to apply the first hotfix for the latest software version for APM. I have uploaded both the base software version and the hotfix to the hard drive in boot location 2. When I try to activate the software on either the standby or primary, I get a lengthy error. Is there something I'm missing?HotFix installation question
It's been a couple years since I've had to do any kind of code upgrade on an f5 ltm pair. So here's my current situation: 2 F5 LTM 3900s set up in Act/Pass pair, currently running LTM v11.3.0 build 3093 installed on volume 1.2. Both devices need to be upgraded to 11.4.0-20405-HF2. The hotfix image has been imported, but not installed, on both devices. Basically, I'm looking for a walkthru/refresher on the upgrade process. Thanks in advance.Upgrade issues with HA devices using Device trust
So I upgraded from 11.5.0 to 11.5.0 HF2 due to HeartBleed. I was running on HD1.3 with 11.5.0. I uploaded the new ISO and installed it on HD1.1 patched HF2 on HD1.1 and made it the active boot location and told it to copy over the config. The system booted and config was copied over and everything was happy besides the cert that is used didn't exist so I had to blow away the trust (via CLI by editing bigip_base.conf "cm cert /Common/dtca-bundle.crt") between the 2 boxes and rebuild after the fact. My question is: Is there a clean way to upgrade the system and copy over the cert so the trust doesn't need to be broken and rebuilt? or is that just part of the upgrade process?
