# Bug in Cisco Module for Filebeat 7.17.8

**URL:** <https://discuss.elastic.co/t/bug-in-cisco-module-for-filebeat-7-17-8/322633>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 6, 2023, 5:12pm UTC](https://discuss.elastic.co/t/bug-in-cisco-module-for-filebeat-7-17-8/322633 "2023-01-06T17:12:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mmh13](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mmh13/32/115666_2.png) [@mmh13](https://discuss.elastic.co/u/mmh13)\
**Post date:** [January 6, 2023, 5:12pm UTC](https://discuss.elastic.co/t/bug-in-cisco-module-for-filebeat-7-17-8/322633/1 "2023-01-06T17:12:28Z")

</div>

Hey,

When trying to run **Filebeat 7.17.8** with the **Cisco module** enabled we found that new amp events were not being ingested.

The `var.first_interval` parameter was respected and initially populated the index with amp events but no new events would be ingested unless we manually disabled and re-enabled the module.

This appeared to be a silent failure - could not gain anything from the logs that indicated anything was wrong, although I didn't try debug log level.

Rolling back to **7.16.3** resolved the problem.

Hope this is useful to anyone experiencing a similar issue configuring the Cisco module.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 3, 2023, 7:13pm UTC](https://discuss.elastic.co/t/bug-in-cisco-module-for-filebeat-7-17-8/322633/2 "2023-02-03T19:13:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
