The only way to fully avoid collisions is to operate the Ethernet in full duplex. There are no collisions in full duplex.
If you operate the Ethernet in half duplex there will be some collisions. Some collisions are normal in half duplex and are not a problem. What can be a problem is too many collisions. If you look at the total number of frames on the interface and look at the number of collisions you can get the ratio of collisions and that can help you to determine if you are having too many collisions.
Not all devices support full duplex Ethernet, e.g. old equipment and 10 Mbps Ethernet.
Duplex mode, to work correctly, must be the same between the two devices.
Many newer Ethernet devices support an "auto" duplex mode, but it can sometime fail to function properly. It will also usually revert to half duplex expecially if the other side is configured "full" -- which causes very poor performance.
Valid duplex configuration combinations between devices are half-half, full-full or auto-auto. (Auto-auto usually should bring the two devices interfaces to full-full, but it might set them to half-half. The latter is less than optimal performance, but again, you don't want to see half-full, whether hard configured that way or set that way by auto-auto.)
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.