For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Subrun's avatar
Subrun
Icon for Cirrostratus rankCirrostratus
Jan 19, 2020

F5 Code Upgrade Problem-- Showing The Configuration not yet loaded message

Hello,

 

While doing Code Upgrade for an HA F5 , when I boot with New Code it shows " The Configuration not yet loaded, if this message persists, it may indicate a configuration problem" . 1st started with Standby node after License reactivation and it shows said message.

 

If I rollback to Old Code,  Device Comes back normally. 

 

What could be the problem , attached couple of screenshot related to the problem ?

 

Whats the available size required for version 14.1.0.6 ? Just note that existing code is 13.1.0 and was trying to upgrade to 14.1.0

8 Replies

  • Boot into the upgraded partition.

    Log in via ssh

    From the bash prompt, run

    # tmsh load sys config verify

    This should show the config element that is causing the config load error.

    • Subrun's avatar
      Subrun
      Icon for Cirrostratus rankCirrostratus

      It shows output similar to below when I boot with Unsuccessful Load

       

      [admin@F5_Box_1:Offline:Disconnected] ~ # 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_oauth_base.conf

       /defaults/apm_saml_base.conf

       /defaults/app_template_base.conf

       /defaults/classification_base.conf

       /var/libdata/dpi/conf/classification_update.conf

       /defaults/ips_base.conf

       /var/libdata/ips/ips_update.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

       /defaults/cipher.conf

       /defaults/ilx_base.conf

      Validating configuration...

      Loading schema version: 13.1.0.5

       /config/bigip_base.conf

       /config/bigip_user.conf

       /config/bigip.conf

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:10:48 AST):

       

      logger[13348]: Re-starting tmm

       

      2020 Mar 1 10:10:48 F5_Box_1.emera.root.local logger[13348]: Re-starting tmm

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:10:48 AST):

       

      logger[13357]: Re-starting tmm1

       

      2020 Mar 1 10:10:48 F5_Box_1.emera.root.local logger[13357]: Re-starting tmm1

       /config/bigip_script.conf

      Loading schema version: 14.1.0.6

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:10:48 AST):

       

      logger[13366]: Re-starting tmm2

       

      2020 Mar 1 10:10:48 F5_Box_1.emera.root.local logger[13366]: Re-starting tmm2

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:10:48 AST):

       

      logger[13375]: Re-starting tmm3

       

      2020 Mar 1 10:10:48 F5_Box_1.emera.root.local logger[13375]: Re-starting tmm3

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:10:48 AST):

       

      logger[13384]: Re-starting tmm4

       

      2020 Mar 1 10:10:48 F5_Box_1.emera.root.local logger[13384]: Re-starting tmm4

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:10:48 AST):

       

      logger[13393]: Re-starting tmm5

       

      2020 Mar 1 10:10:48 F5_Box_1.emera.root.local logger[13393]: Re-starting tmm5

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:10:48 AST):

       

      logger[13402]: Re-starting tmm6

       

      2020 Mar 1 10:10:48 F5_Box_1.emera.root.local logger[13402]: Re-starting tmm6

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:10:48 AST):

       

      logger[13411]: Re-starting tmm7

       

      2020 Mar 1 10:10:48 F5_Box_1.emera.root.local logger[13411]: Re-starting tmm7

      01070311:3: Ciphers list '!EXPORT:!DH:RSA+RC4:RSA+AES:RSA+DES:RSA+3DES:ECDHE+AES:ECDHE+3DES:@SPEED' for profile /Common/serverssl-insecure-compatible denies all clients

      Unexpected Error: Validating configuration process failed.

      [admin@F5_Box_1:INOPERATIVE:Disconnected] ~ #

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:11:08 AST):

       

      logger[14393]: Re-starting tmm

       

      2020 Mar 1 10:11:08 F5_Box_1.emera.root.local logger[14393]: Re-starting tmm

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:11:09 AST):

       

      logger[14402]: Re-starting tmm1

       

      2020 Mar 1 10:11:09 F5_Box_1.emera.root.local logger[14402]: Re-starting tmm1

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:11:09 AST):

       

      logger[14411]: Re-starting tmm2

       

      2020 Mar 1 10:11:09 F5_Box_1.emera.root.local logger[14411]: Re-starting tmm2

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:11:09 AST):

       

      logger[14420]: Re-starting tmm3

       

      2020 Mar 1 10:11:09 F5_Box_1.emera.root.local logger[14420]: Re-starting tmm3

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:11:09 AST):

       

      logger[14429]: Re-starting tmm4

       

      2020 Mar 1 10:11:09 F5_Box_1.emera.root.local logger[14429]: Re-starting tmm4

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:11:09 AST):

       

      logger[14438]: Re-starting tmm5

       

      2020 Mar 1 10:11:09 F5_Box_1.emera.root.local logger[14438]: Re-starting tmm5

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:11:09 AST):

       

      logger[14447]: Re-starting tmm6

       

      2020 Mar 1 10:11:09 F5_Box_1.emera.root.local logger[14447]: Re-starting tmm6

       

      Broadcast message from systemd-journald@F5_Box_1.emera.root.local (Sun 2020-03-01 10:11:09 AST):

       

      logger[14456]: Re-starting tmm7

       

      2020 Mar 1 10:11:09 F5_Box_1.emera.root.local logger[14456]: Re-starting tmm7

       

      • Subrun's avatar
        Subrun
        Icon for Cirrostratus rankCirrostratus

        Is it because of following error ? Just note that This SSL Profile is no where we called explicitely.

         

        01070311:3: Ciphers list '!EXPORT:!DH:RSA+RC4:RSA+AES:RSA+DES:RSA+3DES:ECDHE+AES:ECDHE+3DES:@SPEED' for profile /Common/serverssl-insecure-compatible denies all clients

        Unexpected Error: Validating configuration process failed.

         

  • Subrun's avatar
    Subrun
    Icon for Cirrostratus rankCirrostratus

    Hello,

     

    I actually rollbacked and to try that command I need maintenance window. However I ran same during Pre Upgrade and actually had one error. But I did overlook that as I do not have any active VIP running for that reference. Does this stop me to load the New Code ? And I am actually copying config from Old Volume to New Volume.

     

    [User@F5_Peer :Active:In Sync] ~ # 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_oauth_base.conf

    /defaults/apm_saml_base.conf

    /defaults/app_template_base.conf

    /defaults/classification_base.conf

    /var/libdata/dpi/conf/classification_update.conf

    /defaults/ips_base.conf

    /var/libdata/ips/ips_update.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

    /defaults/cipher.conf

    /defaults/ilx_base.conf

    Validating configuration...

    /config/bigip_base.conf

    /config/bigip_user.conf

    /config/bigip.conf

    /config/bigip_script.conf

    01070734:3:Configuration error: Can't associate firewall policy (/Common/Host.Domain.com.app/Host.Domain.com_firewall) folder does not exist

    Unexpected Error: Validating configuration process failed.

  • I would open a support case and ask that an engineer be available to assist during your scheduled maintenance window. I've had a similar issue happen and it ended up taking some time to resolve with the tech's assistance.

  • Can you try with partition all verify... It looks like you have partitions across and the config fails to load others and it stops verify.