How to enforce specific settings through new configuration changes

I'l get this out the way - only apply connection mirroring if it makes sense to do so

- i.e. for long-lived TCP connections that have a moderately high setup cost, or connections that do not auto-recover.

There is limited value in setting up connection mirroring for HTTP/HTTPS connections that have been designed with an expectation of connection loss and recovery. The cost in memory and network utilization for the mirroring is generally higher than the benefit.

There is also no value in connection mirroring for stateless performance layer 4 virtuals (i.e with loose initiation/loose close).

For consistent templating:

The traditional answer would be to write an iApp template to apply the relevant settings.

The recent answer would be to script the configuration with the RestAPI and tools that use it.

The more recent answer lies in AS3, and declarative onboarding.

Now we have FAST templates, which also use AS3:

F5 Application Services Templates (FAST)