System keeps telling me to perform a reboot...

I would recommend two actions, in order:

1. From the console, run the following:

   tmsh load sys config
   

   If there is an issue with the configuration this should alert you to that.

2. If the above does not produce any errors, I'd probably open a support case.

hmm, didn't work and support seems to not have an answer. I see there are: [error] proxy: AJP: failed to make connection to backend: localhost err httpd[8751]: [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 (*) failed errors in my httpd logs.

I see there are: [error] proxy: AJP: failed to make connection to backend: localhost err httpd[8751]: [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 (*) failed errors in my httpd logs.

i do not think the httpd error relates to this issue. it may have some clues in /var/log/ltm during the reboot time.

hmm interesting, anything thing I found that looks like something...

Jan 3 12:59:00 xxxxxxxxxxxxxxxx warning chmand[6654]: 012a0004:4: File I/O error:22 /sys/devices/system/cpu/cpu0/cpufreq/user_limit:2400000

Jan 3 12:59:00 xxxxxxxxxxxxxxxx emerg chmand[6654]: 012a0000:0: The system must be rebooted for some changes to take effect. This is an expected behavior when upgrading performance license.

you have seen ID414385, haven't you? it is the closet i found.

ID414385 - 'Reboot required' status doesn’t change to Active even after reboot/load sys config default

I'll give it a go right now.

how can i view ID414385? can't find any reference to it and in the same situation.

run with 11.4.1 HF2 on a 4000 (AFM/ASM/LTM) this happens, same setup on a 2000 doesnt.

run with 11.4.1 HF2 on a 4000 (AFM/ASM/LTM) this happens, same setup on a 2000 doesnt.

ID414385 is fixed in 11.3.0. it seems not affect 11.4.x. you may have to open a support case.

Sorry I slacked on my response here.

I actually solved this by going through a complicated algorithm and process....

I just re-licensed my box first with my base key. The base key had the GTM module active...fine. Then I deleted the add-on GTM key and replaced it with my LTM add-on key and got the new dossier and rebooted and all was good.

I'm thinking I had an initial messed up dossier which caused something to mess-up.

I wish I had a better explanation..

worked through this with support, in the end it became clear it was an issue with the original license, after it was revoked and relicensed the issue went away. nothing to solve on your own, call support :)