@travisrigby - Thank you for your question.
"No buffer" errors indicate the number of packets that were dropped due to the buffer being full upon its arrival.
"Throttles" indicate the number of times a NetVanta device is unable to handle the incoming data rate and, as a result, proactively drops packets to get it to a rate that it can handle.
First thing you will want to make sure of is that there is not a duplex mismatch on that interface. Keep in mind that the ethernet interface on the AOS device and the interface that it is connected to MUST be set the same. This means either both are set to "auto-negotiate" OR both are hard-set to the same speed and duplex.
Second, depending on the applications you have running on your device, you may want to try and enable "ip ffe". This feature streamlines the processing of packets and may relieve the CPU load on the AOS device causing the errors to cease.
Finally, it would be worthwhile to check the throughput of the traffic you are actually sending and receiving. Occasionally, a host or hosts in the network could potentially send a burst of traffic that the AOS device is unable to handle, such as a broadcast.
In the end, if you continue to see the errors accruing it may be time to look into upgrading the bandwidth of your connection to handle the data rates your network is seeing. However, I would strongly recommend that the network be investigated before looking to upgrade.
Let us know if you have any further questions.
Thanks,
Noor
@travisrigby - Thank you for your question.
"No buffer" errors indicate the number of packets that were dropped due to the buffer being full upon its arrival.
"Throttles" indicate the number of times a NetVanta device is unable to handle the incoming data rate and, as a result, proactively drops packets to get it to a rate that it can handle.
First thing you will want to make sure of is that there is not a duplex mismatch on that interface. Keep in mind that the ethernet interface on the AOS device and the interface that it is connected to MUST be set the same. This means either both are set to "auto-negotiate" OR both are hard-set to the same speed and duplex.
Second, depending on the applications you have running on your device, you may want to try and enable "ip ffe". This feature streamlines the processing of packets and may relieve the CPU load on the AOS device causing the errors to cease.
Finally, it would be worthwhile to check the throughput of the traffic you are actually sending and receiving. Occasionally, a host or hosts in the network could potentially send a burst of traffic that the AOS device is unable to handle, such as a broadcast.
In the end, if you continue to see the errors accruing it may be time to look into upgrading the bandwidth of your connection to handle the data rates your network is seeing. However, I would strongly recommend that the network be investigated before looking to upgrade.
Let us know if you have any further questions.
Thanks,
Noor
@travisrigby - I marked this as "assumed answered," but if you have further questions on this topic do not hesitate to reply. I will be happy to help.
Thanks,
Noor
I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post and unmark it and select another in its place with the applicable buttons. If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.
Thanks,
Noor