cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Welcome to Cisco Firewalls Community


181
Views
0
Helpful
0
Replies
Highlighted
Beginner

ASA5505 overruns growth

Hello community!

 

I investigated problem with rapid overruns growth on inside interfaces on my ASA5505 and havent more ideas. 

 

Interface Ethernet0/1 "", is up, line protocol is up
Hardware is 88E6095, BW 100 Mbps, DLY 100 usec
Auto-Duplex(Full-duplex), Auto-Speed(100 Mbps)
Input flow control is unsupported, output flow control is unsupported
Description: ## Inside ##
Available but not configured via nameif
MAC address 0021.d856.5c5f, MTU not set
IP address unassigned
7468867 packets input, 6708226941 bytes, 0 no buffer
Received 35639 broadcasts, 0 runts, 0 giants
25821 input errors, 0 CRC, 0 frame, 25821 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
5 switch ingress policy drops
7787230 packets output, 7412000690 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
0 switch egress policy drops
0 input reset drops, 0 output reset drops

==============================

Interface Ethernet0/6 "", is up, line protocol is up
Hardware is 88E6095, BW 100 Mbps, DLY 100 usec
Auto-Duplex(Full-duplex), Auto-Speed(100 Mbps)
Input flow control is unsupported, output flow control is unsupported
Description: ## New Core ##
Available but not configured via nameif
MAC address 0021.d856.5c64, MTU not set
IP address unassigned
13212754 packets input, 12114929185 bytes, 0 no buffer
Received 49602 broadcasts, 0 runts, 0 giants
12884 input errors, 0 CRC, 0 frame, 12884 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
0 L2 decode drops
2381 switch ingress policy drops
13612094 packets output, 13349049508 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
0 switch egress policy drops
0 input reset drops, 0 output reset drops

===============================

Traffic profiles:

Ethernet0/1:
received (in 1104.750 secs):
7038899 packets 6309320560 bytes
6371 pkts/sec 5711084 bytes/sec
transmitted (in 1104.750 secs):
7323153 packets 6997126029 bytes
6628 pkts/sec 6333673 bytes/sec
1 minute input rate 7228 pkts/sec, 6516007 bytes/sec
1 minute output rate 7515 pkts/sec, 7259898 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 6643 pkts/sec, 6008199 bytes/sec
5 minute output rate 6939 pkts/sec, 6681011 bytes/sec
5 minute drop rate, 0 pkts/sec

=================================

Ethernet0/6:
received (in 1119.620 secs):
6562065 packets 6015023195 bytes
5860 pkts/sec 5372379 bytes/sec
transmitted (in 1119.620 secs):
6745789 packets 6638153810 bytes
6025 pkts/sec 5928934 bytes/sec
1 minute input rate 6365 pkts/sec, 5912421 bytes/sec
1 minute output rate 6494 pkts/sec, 6229000 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 6133 pkts/sec, 5784379 bytes/sec
5 minute output rate 6166 pkts/sec, 5947946 bytes/sec
5 minute drop rate, 0 pkts/sec

==================================

CPU-hogged:

Process: ssh, NUMHOG: 10, MAXHOG: 102, LASTHOG: 10
LASTHOG At: 10:56:10 UTC Jul 19 2019
PC: 8bf3f9c (suspend)
Call stack: 8bf3f9c 8c029e9 8bf88d5 8bf8d75 8bf9333 88af605 937959e
80d9315 80cc731 80cd6da 8063bb3

Process: ssh, PROC_PC_TOTAL: 3, MAXHOG: 13, LASTHOG: 12
LASTHOG At: 10:56:11 UTC Jul 19 2019
PC: 88b7de5 (suspend)

Process: ssh, NUMHOG: 3, MAXHOG: 13, LASTHOG: 12
LASTHOG At: 10:56:11 UTC Jul 19 2019
PC: 88b7de5 (suspend)
Call stack: 88b7de5 88b0de0 898f018 898f191 88b0c57 88b0cc1 88b8cb6
88ba3da 80cb501 80cc8aa 80cd6da 8063bb3

Process: ssh, PROC_PC_TOTAL: 26, MAXHOG: 102, LASTHOG: 17
LASTHOG At: 05:56:16 UTC Jul 24 2019
PC: 8bf3f9c (suspend)

Process: ssh, NUMHOG: 14, MAXHOG: 17, LASTHOG: 17
LASTHOG At: 05:56:16 UTC Jul 24 2019
PC: 8bf3f9c (suspend)
Call stack: 8bf3f9c 8c00c7d 8bfedfe 8bffc0f 8c025fc 8c02872 8bf8ef5
8bf9333 88af605 937959e 80d9315 80cc731 80cd6da 8063bb3

Process: Dispatch Unit, PROC_PC_TOTAL: 50, MAXHOG: 241, LASTHOG: 11
LASTHOG At: 00:07:40 UTC Jul 25 2019
PC: 81ac059 (suspend)

Process: Dispatch Unit, NUMHOG: 50, MAXHOG: 241, LASTHOG: 11
LASTHOG At: 00:07:40 UTC Jul 25 2019
PC: 81ac059 (suspend)
Call stack: 81ac059 8063bb3

CPU hog threshold (msec): 10.240
Last cleared: None

=============================

 

In fact i have actual CPU-hogs by Dispatch Unit and rapid overruns growth, but it doesnt correlate in time.

 

How can it be explained?

 

--

Thank you for answers in advance!

 

 

 

 

 

 

Everyone's tags (2)