Pre-deployment validation - BlueCat Integrity - 9.5.0

Address Manager Administration Guide

Locale
English
Product name
BlueCat Integrity
Version
9.5.0

Address Manager includes deployment validation to let you verify the syntax of deployment data before the actual deployment.

Setting validation options at the configuration level or server level will enable the pre-deployment validation to be part of a manual or scheduled deployment process. For more information about setting validation options, refer to Setting validation options for a configuration or Setting server level validation options.

When you set validation options at the configuration level or server level, Address Manager runs the validation check against the following areas to verify the deployment data:
  • dhcpd.conf
  • named.conf
  • DNS zone files
Note: Pre-deployment validation doesn't check all combinations of deployment data. The deployment might still fail even after pre-deployment validation is successful. In the event of issues after successful pre-deployment validation, the Deployment Status page will display the results. You can also navigate to the Event List page to check the logs.
Note: Address Manager does not currently validate against the assignment of a DHCPv4 role to an IPv6-only server. Assignment of a DHCPv4 role to an IPv6-only server will cause a deployment error with the generic event description of "DHCP deployment failed". Validation against this improper DHCPv4 role assignment will be added in a future release of Address Manager.
If pre-deployment validation fails, the deployment will stop. Examine log files for details on the validation failure. The outcome of the validation check depends on the options you selected:
  • If the configuration file fails the validation test: deployment is labelled as invalid and the DNS data on the managed DNS Server isn't updated. Any existing DNS data on the DNS Server remains untouched. The invalid deployment is noted in the Address Manager Event List and you can review the DNS Validation server log to determine the cause.
  • If the configuration file passes the validation test and you didn't enable zone validation: deployment proceeds and the DNS data on the managed DNS Server is updated.
  • If you selected Fail for any of the zone validation options and a syntax error is detected in the data: deployment is labelled as invalid and the DNS data on the managed DNS Server isn't updated. The invalid deployment is noted in the Address Manager Event List and you can review the Zone Validation server log to determine the cause.
  • If you selected Warn or Ignore for any of the DNS zone validation options and a syntax error is detected in the data: deployment proceeds and the DNS data on the managed DNS Server is updated. Warnings are noted in the Address Manager Event list and you can review the Zone Validation server log to determine the source.
  • If no syntax errors are detected in the data: deployment proceeds and the DNS data on the managed DNS Server is updated.

If pre-deployment validation succeeds, the deployment will go through and you will be immediately directed to the Deployment Status page where you can track the status of the active deployment.