Drift detection is a mechanism that detects a configuration mismatch or drift before (pre) provisioning a server against a blueprint template for the server. The blueprint is in JSON format and contains information such as the firmware version, CPU Core count, and hardware model.
- Configuration blueprints must exist.
- Discover a device using either IP or CSV. See Manual device discovery for details.
- Under Discovery based on compatibility, select from these menu options:
Table 23. Blueprint attributes Blueprint | Select a user-created blueprint from the available list. |
Scan | Select Pre-Scan, which initiates a drift check before a server is provisioned. Note: On a server where a drift detection prescan is performed, you can not remove the hardware profile applied to the server using the Web User Interface. Edit the server using the CLI. Remove the profile label and set "scan" to "none" in the audit section. You can only perform this action on one server at a time. |
Action | Select one of these options: - Allow—allows further server provisioning even after a drift is detected.
- Deny—default value, which does not allow server provisioning after a drift is detected. If a mismatch occurs, the server is marked as noncompliant.
|