Preview Tool

Cisco Bug: CSCvv69719 - Config Archive for ASA is not getting triggered by syslogs

Last Modified

Oct 12, 2020

Products (1)

  • Cisco Prime Infrastructure

Known Affected Releases

3.7(0.0) 3.7(1)

Description (partial)

Prime Infrastructure's Config Archive for the ASA is not triggered by receiving a syslog. The initial archive is created when the device gets added, and inventory collection is completed. Subsequent archives are created by manually scheduling an archive collection.  The ASA is configured to send syslog messages to Prime Infrastructure, and these syslogs can be viewed on the Monitor > Syslog Viewer page.  Prime Infrastructure is configured to collect the archive, after the Hold Off timer (default 10 minutes.) when it receives syslog for the config change, however this is not working for ASAs.

This was observed in Prime Infrastructure 3.7 running with default configuration, managing an ASA 5515 that is configured to send syslogs to Prime Infrastructure.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.