Discards -TRANSMIT-RECEIVE AND ERRORS

What router are you using? Cisco, Nortel...?

If the other interfaces that have the errors are ethernet, you may want to check that both sides of that interface are set to the same speed/duplex, if they are not, you will transmit/receive discards and errors. If they are T1s or any other serial interface, make sure that the settings match the circuit, just keep in mind that you will see discards and errors on the serial interfaces, that is normal, as long as they are not that high. You should worry if they are getting 3000 per day on a T1 with 30% utilization. on a cisco switch just do a sho int s0/0/0 to show the stats for the serial interface. How long has the OC12 been running? and what time frame is the 31 million descards for? 31 mil in 1 year? What is the utilization of the OC12? More than likely you either have a high utilization on your OC12 or it is not configured correctly, either on your end or the Bell's side.

Here is the run down on the equipment and utilization on our OC12

Bothe ends of the OC12 we have Cisco 7304 using pos connection I can run sho int pos monitor and see the connection live without any errors or discards on the interface.

Interface Name:         POS2/0/0   Interface Status: up

Line Statistics:         Total:      Rate(/s):         Delta:
Input Bytes:          345577535        1040918        5204593
Input Packets:          3538601           9540          47702
Broadcast:                    7              0              0
Output Bytes:        7078600496       18126370       90631854
Output Packets:         4868522          12484          62422

Error Statistics:        Total:      Delta:
Input Errors:                 0           0
CRC Errors:                   0           0
Frame Errors:                 0           0
Ignored:                      0           0
Output Errors:                0           0

No Interface Resets:     0

both ends are set the same, same UDP and both connect from the gig ports to a cisco 6513 and run throught he fwsm. We always nail the interface and same connecting speeds and duplex so that is not an issue.

Utilization on this link is below 50% for the last 7 days

but yet I keep seeing this

Transmit discards are *not* errors. They're well formed frames that had to be discarded because the bandwidth of the link + buffer exceeded the offered load. You're just crushing the link. A sniffer won't help you because it can't see what wasn't sent (e.g. discarded before it was transmitted.) The first fix is to stop using UDP for the transfer and use TCP for the window control. To directly answer your question, it comes from IfMibII and is perfectly valid.

Will

I am not showing the link being crushed it is a 622Mbps link that is currently only transmitting 19Mbps and receiving 8Mbps which is hardly curshing it with an average utilization of 4.7938% for the last hour and shows 2 million discards. I am not saying your wrong but I don't see how I am crushing the line with that kind of traffic.

I just did a mib walk on the device and I am still searching for the Mib do you know the OID?

The sniffer is picking up some retransmissions so it is catching something.

Thanks

Do you have an access list on that link?  I believe that anything blocked by an access list will show up as a discard.

Has this been certified as a true statement by the admins/tech support here?

I had the same problem on my 2gig fiber links between my switches. Bandwidth was below 40% but transmission was slow and getting a ton of discards. the fix was to default the interface on each end and build them back from scratch. After that, everything was fine.

My switch logs didnt show any discards either, just orion did.

I'm having same issue and have seen several threads with htis issue.  Based on Danny L's comment in This thread, Orion uses:
ifInDiscards = "1.3.6.1.2.1.2.2.1.13."
ifInErrors = "1.3.6.1.2.1.2.2.1.14."
ifOutDiscards = "1.3.6.1.2.1.2.2.1.19."
ifOutErrors = "1.3.6.1.2.1.2.2.1.20."

I found a good Cisco page showing what these correlate to::