Too many ACL's & packet rate is too high issue

[GONÇALO_NUNO_CO]

Hi, When i configure the switch to download Xos image to upgrade its verson im getting too many "Too many ACL's & packet rate is too high" messages in the switch logs.

02/24/2017 11:34:27.76 Slot-1: Denied packet on ingress interface vlanIf=1000010 slot=1 port=49, too many ACL's & packet rate is too high.

This messages refer to the trunk where i dont have any access-list applied. Ive run the "sh access-list port 1:49" and got this:

#Dynamic Entries ((*)- Rule is non-permanent )
RuleNo Name Application Zone Sub-Zone
(*)1 idmgmt_ks_tcp_dst IdentityManager SYSTEM 0
(*)2 idmgmt_ks_udp_dst IdentityManager SYSTEM 0
(*)3 idmgmt_ks_tcp_src IdentityManager SYSTEM 0
(*)4 idmgmt_ks_udp_src IdentityManager SYSTEM 0

apart form not having any acl applied to the port 49 i dont have neither the identity management configured on port 49.

Can someone guide me to where should i look for the cause of that log message?

Thanks

[Tripathy__Priya]

First of all welcome to HUB for your participation here. I could see you had posted this question 3 days back for the reported error log message and requesting us to provide the cause of these messages.

Looking at the below log messages:

02/24/2017 11:34:27.76 Slot-1: Denied packet on ingress interface vlanIf=1000010 slot=1 port=49, too many ACL's & packet rate is too high.

As far as my understanding is concerned this is reflected in the log if the "refresh policy" command is invoked by adding few more entries in the policy file, then after unconfiguring that specific ACL, EXOS switch will start logging messages like "Denied packet on ingress interface vlanIf=1000223 slot=1 port=1, too many ACL's & packet rate is too high ".

I can see you had already mentioned that no ACL is configured at this moment. That is true but we never know if in the recent past something was configured and later it was unconfigured. While doing this if the policy files contain more than 1 entries then later it would throw these messages.

Hope you understand whatever i have explained here referring to the provided log message and its cause.