# Filebeat 7.3.2 Cisco Module Parsing issue for ASA Syslog rfc3164

**URL:** <https://discuss.elastic.co/t/filebeat-7-3-2-cisco-module-parsing-issue-for-asa-syslog-rfc3164/204554>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 21, 2019, 9:08pm UTC](https://discuss.elastic.co/t/filebeat-7-3-2-cisco-module-parsing-issue-for-asa-syslog-rfc3164/204554 "2019-10-21T21:08:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thurston](https://avatars.discourse-cdn.com/v4/letter/t/53a042/32.png) [@thurston](https://discuss.elastic.co/u/thurston)\
**Post date:** [October 21, 2019, 9:08pm UTC](https://discuss.elastic.co/t/filebeat-7-3-2-cisco-module-parsing-issue-for-asa-syslog-rfc3164/204554/1 "2019-10-21T21:08:15Z")

</div>

Getting Error from Filebeat 7.3.2 related to CISCO module. Sending Cisco ASA logs to Filebeat / Cisco module.

I have read several threads here on elastic, stackoverflow, and other random sites. Not finding a clear solution.

### Cisco ASA Config Info

- Not using syslog in EMBLEM format
- Send Syslog to Filebeat using UDP/9001
- Syslog format; Facility Code LOCAL4(20)
- Include timestamps in syslogs is NOT enabled

### filebeat.yml Config Info

```auto
filebeat.inputs:
- type: log
  enabled: true
filebeat.config.modules:
  path: ${path.config}/modules.d/*.yml
  reload.enabled: false
setup.template.settings:
  index.number_of_shards: 1 
  paths:
    - /var/log/*.log
output.elasticsearch:
  hosts: ["localhost:9200"]

```

### Cisco.yml Config Info

```auto
- module: cisco
  asa:
    enabled: true   
    var.input: syslog
    var.syslog_host: 0.0.0.0
    var.syslog_port: 9001
    var.log_level: 7
ios:
   enabled: true
   var.input: syslog
   var.syslog_host: 0.0.0.0
   var.syslog_port: 9002

```

### Error found when typing: (I replaced IP info and names with XXX)

```auto
sudo systemctl status filebeat

```

```auto
Oct 21 15:03:06 prod-elk filebeat[4367]: 2019-10-21T15:03:06.615-0500 ERROR [syslog] syslog/input.go:132 can't parse event as syslog rfc3164 {"message": "<166>asa5520 %ASA-6-106100: access-list inside-in permitted tcp inside/XXXXX(59641) -> outside/54.243.56.217(80) hit-cnt 1 first hit [0x2fe1648d, 0x1f4b0d90]\n"}

```

---

<div class="post-metadata">

**Author:** ![faec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faec/32/46988_2.png) [@faec](https://discuss.elastic.co/u/faec)\
**Post date:** [October 23, 2019, 3:20pm UTC](https://discuss.elastic.co/t/filebeat-7-3-2-cisco-module-parsing-issue-for-asa-syslog-rfc3164/204554/2 "2019-10-23T15:20:41Z")

</div>

Hello! Unfortunately the problem you're seeing is that your Cisco logs aren't Syslog rfc3164, they're Syslog rfc5424, a newer standard that Filebeat doesn't support yet. You may be able to change your Cisco settings to use rfc3164 instead. You can also chime in on the [feature request](https://github.com/elastic/beats/issues/6872) to support rfc5424, which will help increase its priority 🙂

---

<div class="post-metadata">

**Author:** ![thurston](https://avatars.discourse-cdn.com/v4/letter/t/53a042/32.png) [@thurston](https://discuss.elastic.co/u/thurston)\
**Post date:** [October 24, 2019, 8:46pm UTC](https://discuss.elastic.co/t/filebeat-7-3-2-cisco-module-parsing-issue-for-asa-syslog-rfc3164/204554/3 "2019-10-24T20:46:53Z")

</div>

Thank you @faec  
This helps clear up many of the other threads i was reading.

---

<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:** [November 21, 2019, 8:46pm UTC](https://discuss.elastic.co/t/filebeat-7-3-2-cisco-module-parsing-issue-for-asa-syslog-rfc3164/204554/4 "2019-11-21T20:46:55Z")

</div>

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