# Index rollover given an error for alias

**URL:** <https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [August 24, 2020, 5:20am UTC](https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049 "2020-08-24T05:20:48Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jijo.john](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jijo.john](https://discuss.elastic.co/u/jijo.john)\
**Post date:** [August 24, 2020, 5:20am UTC](https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049/1 "2020-08-24T05:20:48Z")

</div>

Hi Team,

Kindly help us to resolve below error which we are receiving for our custom index created from filebeat cisco asa module.

`illegal_argument_exception: index.lifecycle.rollover_alias [ciscobeat-7.6.2] does not point to index [cisco-beat-2020.08.21]`

Regards,  
Jijo John

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 3, 2020, 11:50pm UTC](https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049/2 "2020-09-03T23:50:54Z")

</div>

Please make sure you bootstrapped the initial index - [https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-index-lifecycle-management.html#ilm-gs-alias-bootstrap](https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-index-lifecycle-management.html#ilm-gs-alias-bootstrap)

---

<div class="post-metadata">

**Author:** ![jijo.john](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jijo.john](https://discuss.elastic.co/u/jijo.john)\
**Post date:** [September 5, 2020, 10:44am UTC](https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049/3 "2020-09-05T10:44:43Z")

</div>

Hi Mark,

After doing the bootstrap index , its creating a new index with rollover name 000001 but as soon as i start the filebeat service its creating a new index. Please see the screenshot below

 ![index](https://us1.discourse-cdn.com/elastic/original/3X/4/2/4265523826e7adce8f2544d31e523f244d27f040.jpeg)

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2020, 11:01am UTC](https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049/4 "2020-09-05T11:01:33Z")

</div>

What does your Filebeat config look like? Have you configured it to write to the write alias?

---

<div class="post-metadata">

**Author:** ![jijo.john](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jijo.john](https://discuss.elastic.co/u/jijo.john)\
**Post date:** [September 5, 2020, 1:35pm UTC](https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049/5 "2020-09-05T13:35:58Z")

</div>

Hi Christian,

Below is the filebeat config

```
index: "cisco-beat-%{+yyyy.MM.dd}"
setup.ilm.enabled: false
setup.template.name: "cisco"
setup.template.pattern: "cisco-*"

```

and below is the put command used to create an initial bootstrap index

```
PUT cisco-beat-2020.09.05-000001
{
  "aliases": {
    "cisco": {
      "is_write_index": true
    }
  }
}

```

basically i am trying to create a custom index name for cisco asa module so that i can store firewall logs in a separate index and configure separate ilm for that

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 5, 2020, 8:41pm UTC](https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049/6 "2020-09-05T20:41:56Z")

</div>

It is writing to an index with the specified name, which is expected since you have disabled ILM and are not writing to the write alias.

---

<div class="post-metadata">

**Author:** ![jijo.john](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jijo.john](https://discuss.elastic.co/u/jijo.john)\
**Post date:** [September 10, 2020, 2:55pm UTC](https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049/7 "2020-09-10T14:55:13Z")

</div>

Thank you Christian and Mark , I configured the filebeat with below option and its working fine now .

setup.ilm.enabled: auto  
setup.template.name: "cisco-dc"  
setup.template.pattern: "cisco-dc-\*"  
setup.ilm.rollover\_alias: "cisco-dc"  
setup.ilm.pattern: "{now/d}-000001"

Ran the Command  
filebeat setup --ilm-policy

`write alias` pointed me to the right doc

---

<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:** [October 8, 2020, 2:55pm UTC](https://discuss.elastic.co/t/index-rollover-given-an-error-for-alias/246049/8 "2020-10-08T14:55:19Z")

</div>

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