Forum Discussion

sain014_80857's avatar
sain014_80857
Icon for Nimbostratus rankNimbostratus
Jun 07, 2017

LTM Configuration issues after restore

Recently I upgraded the OS of the F5 VE LTM boxes to version 11.5.4.0.0.256 and HF 11.5.4.4.0.313-HF4. after that I face the below issues

 

1) The secondary device shows as INOPERATIVE and TACACS access is not working

 

2)So I rebooted from the previuos image wokring one, TACACS working, but in CLI I see the errors "emerg logger: Re-starting apd" and "emerg logger: Re-starting apmd"

 

3) So I stopped it using the CLI but when I reboot it again I see these errors reoccurs

 

4)From the GUI I see the errors "The configuration has not yet loaded. If this message persists, it may indicate a configuration problem" and I couldnt see the virtual servers, menu and none of the configurations

 

5)so I tried to restored from the backup UCS and I see the error "General database error retrieving information."

 

Could someone help me how to make the device again to work?

 

application delivery
BIG-IP
LTM
security

2 Replies

Sort By
  • Ashwin_Venkat's avatar
    Ashwin_Venkat
    Icon for Employee rankEmployee
    Jun 21, 2017

    The configuration not loading warning at the top of the screen in the GUI is an indication that there's some misconfiguration within your configs that's preventing the configuration from loading successfully. You can run "tmsh load sys config verify" (without the quotes) from the bash prompt to see what the error message is. If you see some warning messages about some iRule syntax issues, you can ignore it, as that can't prevent the config from loading. Depending on what the error is, I would recommend opening up a Support ticket with F5 and have that investigated along with knowing whether its safe to make modification to overcome that error.

     

    As for the "General database error retrieving information", there are numerous issues that can cause this and we do have multiple bugs related to it when viewing SSL certificate, Pool or Node list etc. I would recommend opening up a ticket for this info as well and having that investigated, as well as the TACACS issue.

     

    That would be 3 separate cases, given our one issue per ticket policy.

     

  • P_K's avatar
    P_K
    Icon for Altostratus rankAltostratus
    Jun 22, 2017
    1. You should re-activate licenses before you upgrade an F5.
    2. If you installed your new image on different partition(HD), try rebooting back to your old HD. Say if you installed new image on HD1.3 and have old image on HD1.2, you would do "switchboot -b HD1.2" (without quotes) from CLI of the device. Then use "reboot" (without quotes") to reboot into old partition. This should fix inoperative or configuration errors.