Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

Device Config Issues after Upgrade

Upgraded from v 11.5.3 to v 12.1.3.5 and after the upgrade, the device is back up and seems to have partial configuration such as device name, ip address, login credentails, but all the LTM and APM configs are wiped clean. I get the message " The configuration has not yet loaded. If this message persists, it may indicate a configuration problem." when loading the config utility page.

Any suggestions on why I have this error and how i can get all my configs back ?

0
Rate this Question
Comments on this Question
Comment made 13-Jul-2018 by jaikumar_f5 1929

Can you share your upgrade steps.

0
Comment made 13-Jul-2018 by apatel16 54

Took a backup, uploaded 12.1.3.5 iso to the device, installed on a separate partition, once installed booted from that partition. System booted and license had to be reactivated as I did not check the Service Check Date before hand. Reactivated and service check date is updated, but I get config errors as below.


Last login: Thu Jul 12 22:16:35 2018 from 10.8.106.244
[admin@localhost:INOPERATIVE:Standalone] ~ # tmsh load sys config verify
Validating system configuration...
/defaults/asm_base.conf
/defaults/config_base.conf
/defaults/ipfix_ie_base.conf
/defaults/ipfix_ie_f5base.conf
/defaults/low_profile_base.conf
/defaults/low_security_base.conf
/defaults/policy_base.conf
/defaults/wam_base.conf
/defaults/analytics_base.conf
/defaults/apm_base.conf
/defaults/apm_saml_base.conf
/defaults/app_template_base.conf
/defaults/classification_base.conf
/var/libdata/dpi/conf/classification_update.conf
/defaults/urlcat_base.conf
/defaults/daemon.conf
/defaults/pem_base.conf
/defaults/profile_base.conf
/defaults/sandbox_base.conf
/defaults/security_base.conf
/defaults/urldb_base.conf
/usr/share/monitors/base_monitors.conf
Validating configuration...
Loading schema version: 11.5.3
/config/bigip_base.conf
/config/bigip_user.conf
/config/bigip.conf
/config/bigip_script.conf
Loading schema version: 12.1.3.5
There were warnings:
AdminIp fixed up with dhcp_enabled = falseapm sso saml-sp-connector /Common/saml_office365 : A new setting sp-encryption-certificate set to has been added to the system.
Profile /Common/vdi has been added to virtual server /Common/VPN1-mobility-policy_vs because profile /Common/remotedesktop was found in the virtual serverProfile /Common/vdi has been added to virtual server /Common/VPN1-policy_vs because profile /Common/remotedesktop was found in the virtual serverProfile /Common/vdi has been added to virtual server /Common/citrix-xenapp3.app/citrix-xenapp3_webui_https because profile /Common/remotedesktop was found in the virtual serverProfile /Common/vdi has been added to virtual server /Common/citrix-xenapp4.app/citrix-xenapp4_webui_https because profile /Common/remotedesktop was found in the virtual serverProfile /Common/vdi has been added to virtual server /Common/citrix-xenapp.app/citrix-xenapp_webui_https because profile /Common/remotedesktop was found in the virtual server
01071772:3: Self device (/Common/f5.test.com) specified floating config sync IP (10.255.255.1), which is not associated with non-floating traffic group (/Common/traffic-group-local-only).
Unexpected Error: Validating configuration process failed.

[admin@localhost:INOPERATIVE:Standalone] ~ #

0

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

The main issue of failed load config as mentioned by Boneyard is

01071772:3: Self device (/Common/f5.test.com) specified floating config sync IP (10.255.255.1), which is not associated with non-floating traffic group (/Common/traffic-group-local-only).

It means that IP address 10.255.255.1 is a floating IP but it has not related non-floating.

You can not create floating IP until you create non-floating. You need to analyse bigip_base.conf file and see if 10.255.255.1 has related non-floating IP. If not, then the file need to be manually updated.

0
Comments on this Answer
Comment made 16-Jul-2018 by apatel16 54

Thanks. That was it.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

01071772:3: Self device (/Common/f5.test.com) specified floating config sync IP (10.255.255.1), which is not associated with non-floating traffic group (/Common/traffic-group-local-only). Unexpected Error: Validating configuration process failed.

does that make sense to you? are you loading a config from a unit form a Device Service Cluster to a stand alone one?

0
Comments on this Answer
Comment made 15-Jul-2018 by Mohanad 172

maybe you need to re-activate your lic

0
Comment made 15-Jul-2018 by boneyard 5579

he already did that, as pointed out here: System booted and license had to be reactivated as I did not check the Service Check Date before hand. Reactivated and service check date is updated

0
Comment made 16-Jul-2018 by apatel16 54

Issue was the floating config sync IP. Box use to be part of an HA pair and was removed from the pair but the config was not cleared.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

I'd revert to the previous boot volume, which you might have already done, and start over, re-activating the licences beforehand. Also you might want to run your config through iHealth to see if it picks up any anomalies in your current configurations.

0
Comments on this Answer
Comment made 15-Jul-2018 by Jie 2732

My point is to validate you current configuration first, and try not to have issues carried over into an upgrade process.

0
Comment made 16-Jul-2018 by apatel16 54

Issue was the floating config sync IP. Box use to be part of an HA pair and was removed from the pair but the config was not cleared. Once cleared config reloaded and everything was back to normal.

Thanks.

0