06-29-2011 05:26 AM - edited 03-07-2019 01:01 AM
Hi,
I have noticed input error and CRC error on our mpls wan interface , but we dont have packet drops or communication issue now.
Is it normal for WAN interfaces ?
Regards,
Solved! Go to Solution.
06-29-2011 06:03 AM
What sort of interface is it?
if its ethernet and you connect to your provider on it, make sure you verify the duplex settingss. some providers set their interface to "auto" rather then hard set . This can cause CRC errors and no drops, but serious performance degradation.
Just a thought
06-29-2011 06:13 AM
isclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Agree with Alain, but want to emphasis it should be a very small percentage.
Cisco says (for serial lines):
Note
Any input error value for cyclic redundancy check (CRC) errors, framing errors, or aborts above 1 percent of the total interface traffic suggests some kind of link problem that should be isolated and repaired.
Personally I prefer no worst than 1 in 1,000 or even better 1 in 10,000.
06-29-2011 05:33 AM
Hi,
Yes it could be as long as they are a small percentage of total input packets.
Regards.
Alain.
06-29-2011 06:03 AM
What sort of interface is it?
if its ethernet and you connect to your provider on it, make sure you verify the duplex settingss. some providers set their interface to "auto" rather then hard set . This can cause CRC errors and no drops, but serious performance degradation.
Just a thought
06-29-2011 06:13 AM
isclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Agree with Alain, but want to emphasis it should be a very small percentage.
Cisco says (for serial lines):
Note
Any input error value for cyclic redundancy check (CRC) errors, framing errors, or aborts above 1 percent of the total interface traffic suggests some kind of link problem that should be isolated and repaired.
Personally I prefer no worst than 1 in 1,000 or even better 1 in 10,000.
06-29-2011 10:58 AM
Thanx all for information
This is serial interface only.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: