Nimbostratusconfiguration not yet loaded...
In light of a recent security scan that brought to our attention the week ciphers and such on the F5 self-ip addresses it was decided to take the recommendation of setting the port lock down settings to allow-none. With a 2 node active/passive cluster I performed the port lock down on the active node first by doing the following. Click on all self-ip addresses (floating/non-floating) and set the port lock down setting to allow-none. I then performed a sync-to-group where everything sync'ed up just fine. I then let this sit for a few days to ensure we had no production problems with the configuration. I then did the same process on the standby node, port lock down on all sefl-ip then sync'ed-to-group.
When I did this on the passive node shortly after I started receiving a banner across the the top telling me "The configuration has not yet loaded. If this message persists, it may indicate a configuration problem.". Did I do something wrong here? I'm almost positive that it's a security best practice from F5 to enable these settings on the self-ip addresses.
