Web interface showing "Starting web server" and CLI shows "logger: Re-starting mcpd" every 2 seconds after shutting down 13.1.0.5 Build 0.0.5 Virtual
I have an F5 LTM virtual machine loaded up on a GNS3 VM for a lab. The virtual machine is activated with interfaces/VLANs and a couple pools/VIPs and a policy. When I go to shut down the virtual, I am greeted with the web interface saying... Starting web server Please do not reboot your device. The device is starting services required for the communication with the configuration utility. This process takes approximately 1-2 minutes. and then it runs for 30+ minutes. Logging in to the console with the root account results in endless logger: Re-starting mcpd I have tried... touch /service/mcpd/forceload Forcing a file system check on the next system reboot I should also note that the CLI shows that the LTM is INOPERATIVE so I cannot issue TMSH commands. This issue has happened to me earlier in the week and I just decided to install it as a new VM but I do not want to have to do that every time I need to shut down my host. The lab is only temporary and for testing so I just need to make sure things work but I do not want to have to keep the virtual machine running when I am done for the day in order to keep this machine working. I should also mention this is just a trial license. Any help would be much appreciated.
BIG IP Ver 13 - Where has the learn button gone from ASM Events
Hi, Previously in other versions of BIG IP, I have been able to see an illegal request within the ASM module on the F5 and if I want to allow the request to go through, I could click learn. In version 13, it appears as though the learn button has been removed. I see that I can look at the Traffic Learning for any ASM policy and enforce learnings from there however if there is a specific event that I am looking at that I find in the Event logs, I am unable to address this from the Event logs. In fact I am unable to marry up that request via the event id in the Traffic Learnings where I can address the learning. What is the intended way to allow a blocked request in BIG IP Ver 13? Based on the finding I can make the change directly on the policy however I expect that I am missing the new alternative of what the learn button is/was. Thank you.
