Overview

This workflow validates a set of default parameters and custom parameters, if any, in the F5 load balancers managed in the AppViewX. Post validation, it generates a report of compliant and non-compliant parameters.

• Complaint parameter - The value of the parameter in the device matches with the value defined in the Compliance Policy in AppViewX for the parameter.
• Non-complaint parameter - The value of the parameter in the device does not match with the value defined in the Compliance Policy in AppViewX for the parameter.

This workflow provides an option to make the non-compliant parameters to compliant parameters in the F5 load balancer by writing the value as defined in the AppViewX. AppViewX ships the Standard Compliance policy Default_F5_Configuration_Compliance with Default parameters and sample values. The Standard Compliance policy file is non-editable. You can create Custom Compliance policies with Custom or selected Default parameters of your choice.

• Default Parameters – The parameters supported by default in AppViewX are:
  • Command to read the values for the parameter.
  • Command to write the value for the parameter.
  • Command to revert the value for the parameter.

In F5, the commands are defined in AppViewX.

• Custom Parameters – The Parameters newly added by the user. The user must provide the command to read, the command to write, the command to revert, as an input in the Workflow.

Compliant or Non-compliant parameters are decided based on the logic below:

• A value is mapped to a parameter in the Policy.
• The Parameter complete config is taken from the device, as a response.
• If the value defined in the Policy is available in the response, then it is compliant, else non-compliant. For a few default parameters (syslog_param, cm-device-group-auto-sync, net-self-allow-service), the logic changes. For more details, click here.