# Filebeat 7.2.0 - Cisco ASA module not parsing IPv6 correctly

**URL:** <https://discuss.elastic.co/t/filebeat-7-2-0-cisco-asa-module-not-parsing-ipv6-correctly/187509>\
**Category:** Beats\
**Created:** [June 26, 2019, 7:47am UTC](https://discuss.elastic.co/t/filebeat-7-2-0-cisco-asa-module-not-parsing-ipv6-correctly/187509 "2019-06-26T07:47:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elastic22](https://avatars.discourse-cdn.com/v4/letter/e/6de8d8/32.png) [@elastic22](https://discuss.elastic.co/u/elastic22)\
**Post date:** [June 26, 2019, 7:47am UTC](https://discuss.elastic.co/t/filebeat-7-2-0-cisco-asa-module-not-parsing-ipv6-correctly/187509/1 "2019-06-26T07:47:59Z")

</div>

Hello guys

I was excited to hear that there is now a built-in module for Cisco ASA in filebeat. I quickly tried it in our test environment and saw the following issue:

The ASA will log HTTP requests that it is able to inspect like this:  
`Jun 26 09:23:11 2001:db8:beef::1 %ASA-5-304001: 2001:db8:beef::250 Accessed URL 2001:db8:beef:10::201:http://mirror.example.com`

But this causes the following filebeat error, because it is not able to parse the IPv6 address correctly:

```
{"type":"mapper_parsing_exception","reason":"failed to parse field [destination.ip] of type [ip] in document with id 'CUizkmsBK1dsQzpOSnZ2'",
"caused_by":{"type":"illegal_argument_exception","reason":"'2001' is not an IP string literal."}}

```

Other than that, it seems to work fine.

---

<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:** [July 24, 2019, 10:00am UTC](https://discuss.elastic.co/t/filebeat-7-2-0-cisco-asa-module-not-parsing-ipv6-correctly/187509/2 "2019-07-24T10:00:55Z")

</div>

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