cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
881
Views
0
Helpful
2
Replies
Highlighted
Frequent Contributor

Urgent,Nexus3064 interface input discard !

 HI Everyone,

 

I am meeting a issue about nexus3064 some interface have “  input discard ” . Just as below:

Ethernet1/12 is up
Hardware: 100/1000/10000 Ethernet, address: xxxx.xxxx.xxxx (bia xxxx.xxxx.xxxx)
Description:
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 10 Gb/s, media type is 10G
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped 10week(s) 1day(s)
Last clearing of "show interface" counters 5d02h
30 seconds input rate 3572512372 bits/sec, 431787999 bytes/sec, 1301033 packets/sec
30 seconds output rate 0 bits/sec, 0 bytes/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 3.64 Gbps, 1.33 Mpps; output rate 42 bps, 0 pps
RX
194258987693 unicast packets 41244003 multicast packets 12170707 broadcast packets
193367181001 input packets 91149121305111 bytes
0 jumbo packets 0 storm suppression packets
0 giants 0 input error 0 short frame 0 overrun 0 underrun
0 watchdog 0 if down drop
0 input with dribble 193459831164 input discard(includes ACL drops)
0 Rx pause
TX
0 unicast packets 3612 multicast packets 0 broadcast packets
3612 output packets 1113846 bytes
0 jumbo packets
0 output errors 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble
0 Tx pause
0 interface resets

 

I can see the reason is "  Receive Drops" by "  show hardware internal interface indiscard-stats front-port x " command.

N3K# show hardware internal interface indiscard-stats front-port 12

+-----------------------------------------+-----------------+----------------+-------------------------------------+
| Counter Description | Count | Last Increment | Last Increment Time |
+-----------------------------------------+-----------------+----------------+-------------------------------------+
IPv4 Discards 0 0
STP Discards 81621341 5000823 06-01-2019 01:34:13.48752
Policy Discards 0 0
ACL Drops 81618341 5000823 06-01-2019 01:34:13.48766
Receive Drops 571600022159 663987 06-21-2019 10:17:22.811106  <<<<<<
Vlan Discards 31311 31311 05-30-2019 12:23:12.481132
+-----------------------------------------+-----------------+----------------+-------------------------------------+

 

Receive Drops--- This drop increment represents a condition when no output port is determined for an ingress packet. Receive drops happen because of variety of reasons including IPv4, STP and policy discards. The drop counter increments in conjunction with one of the above counters or separately.

 

What reason about this ? It's still increase this time.I should how to fix it?

 

Thanks

2 REPLIES 2
Highlighted
Enthusiast

Highlighted
Frequent Contributor

Hi,

Thanks for your response!
I have found this document ,but i don't know why the "input discard " packtes is equel to "RX unicast packets". what is represent for this symptom?
Content for Community-Ad