06-23-2016 01:33 PM - edited 03-12-2019 12:56 AM
Please, may someone explain this error
06-23-2016 11:47 PM
Hi,
You might want to check this bug CSCtt88306 which explains the same issue due to hash calculation issue.
Rate if it helps.
Thanks,
Ankita
06-27-2016 02:09 PM
Thanks Ankita,
However, still not sure to tweak this issue
"Use other syslogs such as 302013 or 302015 to track connection builds."
If you have more details, it would be very helpful
06-28-2016 12:49 AM
Hi,
Could you share the ASA version you are running ?
If you are running 9.3 and below then you need to upgrade to 9.3.2 for the fix.
"Use other syslogs such as 302013 or 302015 to track connection builds."
suggests that you can use the above two syslog id's to track same information for which the error is generated 106100 etc.
Rate if it helps.
Thanks,
Ankita
Thanks,
Ankita
06-28-2016 07:32 AM
Sure, ASA version is 9.6(1)
06-28-2016 10:55 PM
Hi,
Thanks for the update.
If you are on 9.6 and still observing this issue, I would recommend you to open TAC case so that we can assist you better.
Thanks,
Ankita
09-02-2016 05:46 AM
A Ticket is created and Tech Support this normal and its built-in config.
I asked let's change it, he said this device config and not configurable!
The ticket is closed!
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