topic Re: ASA 5505 - Input Errors in Network Security

ASA 5505 - Input Errors

antoninNet — Wed, 24 Feb 2021 18:44:50 GMT

Hello everyone,

I am happy that I joined this community. I know that this is the best place to learn and help people, but at this moment I need some help because it's very urgent.

I have 2 ASA 5505 connected by an interface. The interface is to ensure the failover mechanism.

The problem I am facing is that when I run the "show interface" (interface connecting both ASA) command I get 456.773 "input errors", 158 CRC but the "overrun" value is 0! That make me understand that the input errors is not related to the overrun mechanism. The problem is that I'm having 80.000 more error inputs each hour! (When the problem had just appeared I had just 279.324 "input errors".

Could you please help me to understand what is going on? I don't really understand why that much input errors

Best regards,

Antonin

Re: ASA 5505 - Input Errors

balaji.bandi — Wed, 24 Feb 2021 22:37:09 GMT

can you post-show interface GigabitEthernetx/x to understand the issue also what ASA Code you running.

how about the other side switch side, is the same issue or errors?

what kind of traffic is this FW handling?

Re: ASA 5505 - Input Errors

antoninNet — Thu, 25 Feb 2021 09:08:57 GMT

Hello,

Here you have the output:

Auto-Duplex(Full-duplex), Auto-Speed(100 Mbps)

Input flow control is unsupported, output flow control is unsupported

Description: failover

Available but not configured via

MAC address x, MTU not set

IP address unassigned

101182346 packets input, 14532451234 bytes, 0 no buffer

Received 1124542 broadcasts, 0 runts, 1032 giants

2142342 input errors, 215 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

0 pause input, 0 resume input

0 L2 decode drops

3 switch ingress policy drops

121242823 packets output, 12015463027 bytes, 0 underruns

0 pause output, 0 resume output

0 output errors, 0 collisions, 0 interface resets

0 late collisions, 0 deferred

0 rate limit drops

Re: ASA 5505 - Input Errors

antoninNet — Thu, 25 Feb 2021 09:09:35 GMT

In the other side, I checked that the interface of the other switch (the one that is directly connected) does not have any input errors neither overruns:

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

0 pause input, 0 resume input

0 L2 decode drops

3 switch ingress policy drops

321547823 packets output, 72015463027 bytes, 0 underruns

0 pause output, 0 resume output

0 output errors, 0 collisions, 0 interface resets

0 late collisions, 0 deferred

0 rate limit drops

These FW handle my client traffic and their VPNs.