cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
865
Views
0
Helpful
2
Replies

Catalyst 6800IA interface "overrun"

Mark Ibrahim
Level 1
Level 1

I have a Catalyst 6880X with five FEX's, each FEX is a stack of two.  I am running software version 15.1(2)SY2 and I have noticed overruns on every interface on the FEX's excluding the uplinks.  Has anyone seen this problem?

2 Replies 2

dean holroyd
Level 1
Level 1

I also see it to. I'm not sure it is a problem as there have been no complaints, but the overruns are there on one of my devices as you say

 

GigabitEthernet117/1/0/2 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 3623878656 overrun, 0 ignored
GigabitEthernet117/1/0/3 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 3523215360 overrun, 0 ignored
GigabitEthernet117/1/0/4 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 3338665984 overrun, 0 ignored
GigabitEthernet117/1/0/5 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 2348810240 overrun, 0 ignored
GigabitEthernet117/1/0/6 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
GigabitEthernet117/1/0/7 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 1207959552 overrun, 0 ignored
GigabitEthernet117/1/0/8 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 4177526784 overrun, 0 ignored
GigabitEthernet117/1/0/9 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 1543503872 overrun, 0 ignored
GigabitEthernet117/1/0/10 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 1962934272 overrun, 0 ignored
GigabitEthernet117/1/0/11 is down, line protocol is down (notconnect)
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
GigabitEthernet117/1/0/12 is down, line protocol is down (notconnect)
     0 input errors, 0 CRC, 0 frame, 2449473536 overrun, 0 ignored
GigabitEthernet117/1/0/13 is up, line protocol is up (connected)
  L3 out Switched: ucast: 3602946785 pkt, 2723711788131 bytes - mcast: 0 pkt, 0 bytes
     0 input errors, 0 CRC, 0 frame, 301989888 overrun, 0 ignored
GigabitEthernet117/1/0/14 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 1056964608 overrun, 0 ignored
GigabitEthernet117/1/0/15 is up, line protocol is up (connected)
     25412439917 packets input, 11894315117797 bytes, 0 no buffer
     0 input errors, 0 CRC, 0 frame, 3959422976 overrun, 0 ignored
GigabitEthernet117/1/0/16 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 2499805184 overrun, 0 ignored
GigabitEthernet117/1/0/17 is up, line protocol is up (connected)
     0 input errors, 0 CRC, 0 frame, 2113929216 overrun, 0 ignored
GigabitEthernet117/1/0/18 is up, line protocol is up (connected)

 

Perhaps a Cisco employee can offer insight

I have a TAC case open, it appears to be a cosmetic bug which the DE's are working on now.

Review Cisco Networking products for a $25 gift card