You will see these bytes in the hexadecimal decode of the packet as either several bytes of AA’s or several bytes of 55’s at the very end of the frame (Remember, AAh=1010b, 55h=0101b. Generally, when a collision occurs, several bytes of the preamble of the colliding frame will be read into your Analyzer’s buffer before the signal is completely destroyed. CollisionsĬollisions are the most easily recognizable of the four causes of physical frame corruption. Twisted-Pair Ethernet networks, because each station is connected to a hub or switch, do not manifest these exact corruption patterns.

It is important to remember that these corruption patterns will only be evident on a coaxial Ethernet (10BASE-2 Thin Ethernet, 10BASE-5 Thick Ethernet). Caused by gremlins, helpful users, natural disasters, etc…Īt the end of the discussion there is a Troubleshooting Flowchart to help you identify the cause of frame corruption. Caused by nearby power grids, fluorescent lighting, X-ray machines, etc… Caused by un-terminated cables, impedance mismatch, and exceeding the maximum allowable bend radius of the cable. There are four possible causes of physical frame corruption in an Ethernet Network, each one different in the way it corrupts the frame and is therefore recognizable. While the tips here are universal, other Analyzers’ behavior might differ in such a way as to make these tips invalid or unusable. This page discusses troubleshooting with reference to the LiveNX Analyzer. Twisted-pair Ethernet implementation will NOT manifest these types of corruption patterns! It is important to remember that the frame corruption that is being discussed is SPECIFIC TO COAXIAL ETHERNET. In this essay, we will discuss the different causes of physical frame corruption and the characteristics of each one. When troubleshooting your Ethernet network, the first thing to look for is physical frame malfunction. Ethernet Troubleshooting: Physical Frame Corruption

Etherpeek nx