Forum Discussion
LTM - check if config was loaded from wrong HD partition during upgrade
Also if you insall the configuration but not make the boot volume active and you continie to do changes, after weeks when you switch the active volume, the new volume will have the old configuration, even if you select again to install the configuration before the boot. Install the configuration can be done one time after that you need to delete and again install an iso image in the volume to be able to do install the configuration.
If the missing configuration is only new changes this could be the issue.
Hi Nikoolay1 and thank you for your reply.
What you're stating is true, but I'm not missing a few days of configuration, I'm missing several months. The image was installed on the partition at most a few hours prior to the activity.
I know that F5 produces an ucs archive when the HD partition is created, and I believe this is likely being used when the partition is booted - or maybe for downgrades/rollback.
This is also why I'm thinking that the config on the old partition was installed: it surely did not load the configuration that was on the device at the time the new image was installed on the volume.
Moreover, appliance was NOT running v12.1.2, it was somewhere in 13.1.1.x.
This is why that log really messed with my mind, and I was wondering if any more evidence could confirm my doubt.
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