InDiscars

[gadisontag]

hello

we have a 5700 with 10g and 40 g interface

Did I notice that there is a Indiscard packet at the interface ? What it means? Is this a malfunction? Is there a way to solve?

to the switch connect server with vmware and 40g to main switch 5940

Port link-type: Trunk
VLAN Passing: 2-18, 20-22, 28-37, 41-47, 55, 57, 66-67, 70-72, 100-101, 109-1 13, 115, 119-121, 123, 131-133, 136-138, 160-161, 166, 210-215, 220, 222, 230, 2 37-238, 254, 261-266, 272-277, 280-285, 300-305, 380-382, 398-410, 415-435, 437, 439, 456, 500-509, 517, 539, 600, 701, 707, 777, 889, 1147, 1171, 1500, 1510, 1 595, 1701, 1720, 1800, 1834, 2335, 2358-2359, 2513, 3100, 3210, 3228, 3336, 3456 , 3513, 3620-3623, 4037
VLAN permitted: 2-4090
Trunk port encapsulation: IEEE 802.1q
Port priority: 0
Last link flapping: 27 weeks 5 days 19 hours 31 minutes
Last clearing of counters: 15:24:13 Sun 03/21/2021
Peak input rate: 4916011 bytes/sec, at 2021-03-21 15:32:02
Peak output rate: 6489199 bytes/sec, at 2021-03-22 08:56:08
Last 300 second input: 3696 packets/sec 2343763 bytes/sec 0%
Last 300 second output: 3997 packets/sec 2711924 bytes/sec 0%
Input (total): 287208043 packets, 129837313586 bytes
287132398 unicasts, 27069 broadcasts, 48576 multicasts, 0 pauses
Input (normal): 287208043 packets, - bytes
287132398 unicasts, 27069 broadcasts, 48576 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
Output (total): 302315849 packets, 122070402680 bytes
288120793 unicasts, 10391582 broadcasts, 3803474 multicasts, 0 pauses
Output (normal): 302315849 packets, - bytes
288120793 unicasts, 10391582 broadcasts, 3803474 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier

best regard

gadi

[Ivan_B]

Hi @gadisontag !

Please, post the output of "display packet-drop interface <physical interface>" command. That will help us to understand whether those drops are due to full buffers (GBP) or those are just packets that couldn't and shouldn't be forwarded anywhere, like link-llocal messages (LLDP) or packets with VLAN ID that doesn't allowed on the interface (FFP drops)

[gadisontag]

hello

<5700->display packet-drop interface Ten-GigabitEthernet 1/0/14
Ten-GigabitEthernet1/0/14:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output drop ped: 0

[5700-]display interface Ten-GigabitEthernet 1/0/14
Ten-GigabitEthernet1/0/14
Current state: UP
Line protocol state: UP
IP packet frame type: Ethernet II, hardware address: 5c8a-38a7-3f48
Description: Ten-GigabitEthernet1/0/14 Interface ESX 50 - trunk - nic2
Bandwidth: 10000000 kbps
Loopback is not set
Media type is twisted pair
port hardware type is 10G_BASE_T
10Gbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
Maximum frame length: 10000
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
PVID: 1
MDI type: Automdix
Port link-type: Trunk
VLAN Passing: 2-18, 20-22, 28-37, 41-47, 55, 57, 66-67, 70-72, 100-101, 109-113, 115, 119-121, 123, 131-133, 136-138, 160-161, 166, 210-215, 220, 222, 230, 237-238, 254, 261-266, 272-277, 280-285, 300-305, 380-382, 398-410, 415-435, 437, 439, 456, 500-509, 517, 539, 600, 701, 707, 777, 889, 1147, 1171, 1500, 1510, 1595, 1701, 1720, 1800, 1834, 2335, 2358-2359, 2513, 3100, 3210, 3228, 3336, 3456, 3513, 3620-3623, 4037
VLAN permitted: 2-4090
Trunk port encapsulation: IEEE 802.1q
Port priority: 0
Last link flapping: 27 weeks 5 days 20 hours 45 minutes
Last clearing of counters: 15:24:13 Sun 03/21/2021
Peak input rate: 6740575 bytes/sec, at 2021-03-22 10:44:13
Peak output rate: 8321190 bytes/sec, at 2021-03-22 10:27:13
Last 300 second input: 6992 packets/sec 5093182 bytes/sec 0%
Last 300 second output: 7226 packets/sec 4574162 bytes/sec 0%
Input (total): 310009359 packets, 146107711203 bytes
309929540 unicasts, 28122 broadcasts, 51697 multicasts, 0 pauses
Input (normal): 310009359 packets, - bytes
309929540 unicasts, 28122 broadcasts, 51697 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
Output (total): 327427779 packets, 140324040057 bytes
312228311 unicasts, 11118092 broadcasts, 4081376 multicasts, 0 pauses
Output (normal): 327427779 packets, - bytes
312228311 unicasts, 11118092 broadcasts, 4081376 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier

[5700-]

[5700-

]display packet-drop interface FortyGigE 1/0/42
FortyGigE1/0/42:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

[5700-]display packet-drop interface FortyGigE 1/0/41
FortyGigE1/0/41:

Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0
[5700-]

best regard

[Ivan_B]

Neither of the interface listed has any discarded packets. I am afraid you need to check carefully your monitoring system and see what device is reporting IfInDiscards and for which interface precisely. If you are 100% sure it is this 5710, then maybe it's different port?

 Could you run "display packet-drop interface" command? It will give you statistics for all interfaces. Try to find the one where "Packets dropped" counter is not '0'

[gadisontag]

HELLO

FortyGigE1/0/41:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 2594249
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output drop ped: 0

FortyGigE1/0/42:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 3139292
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output drop ped: 0

FortyGigE2/0/41:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 147659
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output drop ped: 0

FortyGigE2/0/42:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output drop ped: 0

Ten-GigabitEthernet1/0/1:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 97
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/2:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 97
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/3:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 101
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/4:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 91
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/5:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 3
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/6:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 3
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/7:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 3
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/8:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/9:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/10:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/11:
Packets dropped due to full GBP or insufficient bandwidth: 1795955
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 1795955

Ten-GigabitEthernet1/0/12:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/13:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/14:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/15:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 8699
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/16:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 8699
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/17:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 8699
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/18:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 8699
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/19:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/20:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/21:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/22:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/23:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/24:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/25:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/26:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/27:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/28:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/29:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

Ten-GigabitEthernet1/0/30:
Packets dropped due to full GBP or insufficient bandwidth: 0
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 0

interface tenG is connec to server and vmware

best regard

[Ivan_B]

This port has oversubscription issue:

Ten-GigabitEthernet1/0/11:
Packets dropped due to full GBP or insufficient bandwidth: 1795955
Packets dropped due to Fast Filter Processor (FFP): 0
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped: 1795955

Other ports have no issues at all. FFP drops can be ignored.

[gadisontag]

hello

thank

interface ten 1/0/11 is fixed to 10g no auto 

i try to change or replace cable

best regard

gadi

[Ivan_B]

It won't help. I am afraid you can't fix oversubscription with new cable. Look, there is very important point we need to agree on before you proceed - IfInDiscards counter is not an error. Therefore you can't fix it by  disabling speed autonegotiation. Don't waste your time..

It is common misconception - many crappy monitoring tools generate alarms basing on this counter. And many users who don't understand networking basics think they have real issue basing their opinion on those monitoring alarms. And here's the point where hell begins - endless change of cables, ports, etc.

Let me explain you what is really happening with port 1/0/11. Imagine that you need to fill a bottle (your server behind port 1/0/11), but the neck allows a water stream of 50 ml per second maximum, it's just too tight. You put a funnel into the bottle (connect your server to the switch port) and start putting water in a much faster than 50 ml/sec rate, for example 100 ml/sec. What will happen? 50 ml of those 100 will flow to the bottle every second (10Gbps, your maximum port rate), but the rest 50 ml can't get through. And your funnel will start to fill up (switch starts to buffer excessive traffic). When your funnel will overflow (switch ran out of buffer memory dedicated to the port), what happens to that excessive water? It flows on the ground and it's lost (switch starts to discard traffic that can't be stored in the buffer). So that is GBP counter - that water that overlows the funnel and drops to the ground.

Now what you propose is to first, set the bottle's neck diameter fixed ('speed 10000'). But it can't go wider (can't go above 10G). Another idea was to replace the funnel (replace the cable). It won't help, that funnel will be the same.

I am sure now you see what is the real solution to your case - either make the bottleneck wider (use faster port, like 40G) or make that bottle a little bit fancier - add it another neck (another port) and start filling the bottle using two necks simultaneously (make both ports as Bridge-Aggregation, a LAG, Port-Channel, whatever term you prefer), so you can share the load between two necks and achieve up to twice as much throughput.

Hope this all makes sense now! (-:

P.S. If I need to use water analogy for FFP drops, imagine that your funnel has a filter that blocks sand and other contamination particles. You don't want those particles to enter the bottle, so filter just stops them. FFP drops are packets that shouldn't go anywhere and switch just drops those. Example - your port has allowed VLANs 10 and 20, but adjacent device sends you traffic from VLANs 10,20 and 30. Packets with tag '30' are dropped, FFP counter increments.

P.P.S. Drops due to STP blocking state - your port is in STP Blocking state, but adjacent device keeps sending traffic to you (absolutely normal situation for broadcast packets), so packets are dropped, STP drop counter increase. Nothing to worry about.