Overruns are not result of the problem with link/device connected to the port where you see overruns. They are actually a signal of oversubscription on some other port.
There are several ingress ports: Gi2/9, Gi3/9, Gi4/7 - just for example I took those numbers. And there is single outgoing port for those 3 - Gi 1/1.
If all 3 ports will be receiving traffic up to 1 Gig and try to send that out of Gi1/1 - they will cause oversubscription on Gi1/1. This port will start complaining to switch fabric about it. Fabric will recognise the ingress ports which cause this oversubscription and send flow control message towards them to slow down. Thus all these ports will slow down - but to do that they can only start buffering traffic on the line card to which this port belongs - Gi2/9 on LC2 (corresponding ASIC buffer), Gi3/9- LC3, Gi4/7 -LC4.
However as the traffic still comes in from the ingress port - the buffers are quickly filled and start dropping. Those drops you see as overruns.
Thus to troubleshoot it further - find the port which has output drops growing. Understand what traffic is going out of it. Consider to add another port to it and bundle in etherchannel to avoid oversubscription issues.
The 6716 blade is a highly oversubscribed card. if I remember correctly, it is 4:1 overubscribed. What that means is that there are four ports on a single ASIC connecting back to the fabric. The overruns are due to the other ports on the same ASIC preventing this port from being able to send all of its traffic to the fabric.
You may be able to reorganize what is plugged into which port, and perhaps balance the ASICs more evenly.
In the end, though, you need to make sure that the aggregate total of this port and the other three on the same ASIC never reach (or exceed) 10G. QoS *input* policies on all four of those ports might give you some opportunity to drop low priority traffic to protect the NAS critical traffic.
You could also consider a 6708 card, which is only 2:1 oversubscribed.
Or you could consider a 6704, which is 1:1 and thus not oversubscribed at all, and would be able to carry whatever the NAS sent.
The 6716 blade is probably not a good choice for a NAS, assuming has high peaks of traffic. The 4:1 oversubscription is probably more suitable for blade servers which tend to infrequently hit their peaks.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.