If you are sending data to time-based indices with date in the name you can not use rollover as part of ILM. The whole point of rollover is to have a single alias that you write to and let Elasticsearch roll over backing indices automatically based on size and age. This relies on you giving up control of exactly which data that go into which backing index.
You therefore have 2 options. The first is to use rollover and require you to write to the cisco-switch alias instead of index names with date in the names.
If you instead prefer to write to indices in the form cisco-switch-2022-07.26 you should remove rollover from the ILM policy.