Input errors in the interface
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2016 10:56 AM - edited 02-20-2025 11:10 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2016 11:30 AM
Yes you have 2 input errors but you have 278543443 packets output... I would lean more towards the workstation. You can try to clear the counters on the interface and monitor the workstation but highly doubt this is a problem with the switch. If you are adamant about it being an issue with the switch you can always try to change ports and see if the issue follows the workstation. If it doesn't then you might have a bad port on that blade.
HTH
Jon

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2016 11:44 AM
I agree with Jon. Also note that input errors could be some bad packets being sent by the workstation and not being understood by the switch causing the input error counter to increment.
It can be a tedious task to find it as it would involve capture on both hosts and the switch and then looking for the differential as the input error packets will not be seen on the SPAN capture on the switch.
I really doubt that 2 input errors could cause workstation to disconnect. Most application running on the workstations uses TCP which can easily recover from this minuscule loss to be even noticeable for the workstation.
I do see 59 packets going out and 0 packets coming in on this interface snapshot. You may want to check if these 59 packets that is being sent out on the port is destined for that host. One possibility that I am speculating from experience is unknown unicast flooding which could be severe and would force the receiving NIC card to constantly inspect the packet and drop it causing these random issues. Again just talking from experience related to random issues.
-Raj
