ERROR:
From the Cat6500 perspective, input errors and CRCs are seen on Tx/x on both the switches:
Verified with these commands:
show counters interface TeX/X delta
show inventory
show queueing interface
show interface TeX/X
CRC is just a check in Ethernet based on an algorithm, that catches single and double bit errors. When a frame gets corrupted in transit, the Ethernet frame value is different than the expected in the algorithm and this cases the packet to be added as either a failed CRC check or an input error. Frames can get corrupted due to several reasons such as: duplex mismatch, faulty cabling and broken hardware.
we should still narrow down our investigation to a physical issue. I suggest that the following actions are taken:
1) Verify whether there is any duplex mismatch between the switchs // we already checked it(its ok both sides)
2) Clean or replace the fiber/cable.
3) Move the connection to another port to see whether hardware on that specific switch port is broken.
4) The last point would let us know if the problem is found to be specifically with the SFP as well.
futher analysis:
++ We need Wireshark capture , if none of the above issue match.
From the Cat6500 perspective, input errors and CRCs are seen on Tx/x on both the switches:
Verified with these commands:
show counters interface TeX/X delta
show inventory
show queueing interface
show interface TeX/X
CRC is just a check in Ethernet based on an algorithm, that catches single and double bit errors. When a frame gets corrupted in transit, the Ethernet frame value is different than the expected in the algorithm and this cases the packet to be added as either a failed CRC check or an input error. Frames can get corrupted due to several reasons such as: duplex mismatch, faulty cabling and broken hardware.
we should still narrow down our investigation to a physical issue. I suggest that the following actions are taken:
1) Verify whether there is any duplex mismatch between the switchs // we already checked it(its ok both sides)
2) Clean or replace the fiber/cable.
3) Move the connection to another port to see whether hardware on that specific switch port is broken.
4) The last point would let us know if the problem is found to be specifically with the SFP as well.
futher analysis:
++ We need Wireshark capture , if none of the above issue match.
No comments:
Post a Comment