# Plugin Install fails\`gem install logstash-core -v '6.1.3'\`

**URL:** <https://discuss.elastic.co/t/plugin-install-fails-gem-install-logstash-core-v-6-1-3/118006>\
**Category:** Logstash\
**Created:** [February 1, 2018, 11:18am UTC](https://discuss.elastic.co/t/plugin-install-fails-gem-install-logstash-core-v-6-1-3/118006 "2018-02-01T11:18:41Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![sarlacpit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sarlacpit/32/22567_2.png) [@sarlacpit](https://discuss.elastic.co/u/sarlacpit)\
**Post date:** [February 14, 2018, 12:15pm UTC](https://discuss.elastic.co/t/plugin-install-fails-gem-install-logstash-core-v-6-1-3/118006/13 "2018-02-14T12:15:56Z")

</div>

This has been fixed, there was a final piece of the puzzle which was Logstash not recognising the Cisco IPV4 TTL.

> [@Netflow: Unsupported field in template](https://discuss.elastic.co/t/netflow-unsupported-field-in-template/119772/2):
>
> Working with sarlacpit on this issue, I've found the 'unsupported field in template' warning appears in log when passing the following field from a Cisco flow record to logstash: collect ipv4 ttl After removing the field from the Cisco flow record template, we've seen the error no longer appears in the logstash logs, and flows are received.

---

_[View the full topic](https://discuss.elastic.co/t/plugin-install-fails-gem-install-logstash-core-v-6-1-3/118006)._