04-28-2017 07:59 AM
Hi everyone,
We have 3 ESAs in a cluster reporting to an SMA. We have been seeing more duplicate MIDs when searching message tracking in the SMA. As I understand it, clustered ESAs do not coordinate MID generation. But is it possible to seed the starting MID number, on each of the ESAs, far enough apart so that MIDs would not conflict with each other?
https://supportforums.cisco.com/sites/default/files/media/duplicate_mids-sanitized.png
04-28-2017 08:17 AM
Hello,
We do not support changing the MID value. Due to this, my recommendation would be to perform more advanced searches to narrow down your results. For instance, you can select which ESA to search against, which can help mitigate against duplicate MID results on separate appliances.
Thanks!
-Dennis M.
05-03-2017 10:09 AM
The more ESA's you have the more likely this will be the case for MID, and DCID's. Beside searching only on one appliance at a time if you search a smaller time window you will also find less matches.
Maybe be should ask Cisco to open a feature request to be able to prepend a letter or hostname like you can for the log files.
05-04-2017 10:26 AM
Great idea, Marc. I've submitted a feature request.
What features would be changed or added?
Two possible solutions:
05-05-2017 05:56 AM
did you get a feature request number you could share ?
05-05-2017 10:45 AM
Yes, and once the Release Notes are approved, it will show up in the Bug Search Tool.
Here's a direct link:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCve28569
10-06-2021 04:55 AM
Thank you for your efforts.
Unfortunately, more than 4 years later, the situation remains the same ...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide