Configuration reading from ASA to Security Cloud Control
Configuration reading is a management process that
-
enables Security Cloud Control to maintain its own copy of the ASA running configuration file for device management
-
occurs during device onboarding when Security Cloud Control reads and saves a copy of the device configuration file for the first time, and
-
provides options to Check for Changes, Accept without Review, or Read Configuration when reading configurations from an ASA.
When Security Cloud Control needs to read ASA configurations
Security Cloud Control needs to read an ASA configuration in these circumstances:
-
When deployment of configuration changes to the ASA fails and the device state is not listed or Not Synced.
-
When device onboarding fails and the device state is No Config.
-
When changes are made to the device configuration outside of Security Cloud Control and those changes have not yet been polled or detected. In this case, the device state is Synced or Conflict Detected.
In these cases, Security Cloud Control needs a copy of the last known configuration stored on the device.
For more information, refer to Reading, Discarding, Checking for, and Deploying Configuration Changes.