Troubleshooting Incrementing Tx/Rx errors on a Velocloud edge interface.
Article ID: 381072
Updated On:
Products
Issue/Introduction
In some scenarios, we can observe that the Velocloud interface is incrementing Tx or Rx errors on the output of the interfaces on the VCO, this document addresses how to troubleshoot/fix such issues.
Environment
In most cases, incrementing errors are a cause of layer 1 issues such as cabling, ports or speed/duplex mismatch.
We can check the output of the interface status from the remote diagnostics.
We can also check for the same output on the CLI of the edge.
edge:Test(active):~# ifconfig ge6
ge6 Link encap:Ethernet HWaddr F0:8E:DB:E2:8F:86
inet addr:10.10.10.10. Bcast:10.1.72.1 Mask:255.255.255.252
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:47620181 errors:0 dropped:0 overruns:0 frame:0
TX packets:51761287 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7487381972 (7140.5 Mb) TX bytes:6666913452 (6358.0 Mb)
Cause
Mostly caused by a layer 1 issue, could be cabling, port, peer device or speed/duplex mismatch.
Resolution
Confirm that the speed/duplex settings match on both ends, if both are set to auto, hardcode both sides to match.
Move the connection to a different port on the Velocloud edge.
Move the connection on a different port on the peer device.
Change the cables between edge device and the peer device.
If still incrementing after the above then please contact Velocloud support and we can consider if a hardware replacement is necessary.
Feedback
