You encounter a specific error on the network, such as a high count of Ethernet frame errors, or the whole network is freezing or hanging. Keep in mind that abnormally high network bandwidth usage can cause performance degradation on the network, which can present itself in the form of error conditions. If you immediately suspect high bandwidth usage as a problem, first use the procedures for checking hubs and repeaters to analyze the network bandwidth. If at this point you feel that the bandwidth is within normal parameters, continue with the following steps. Remember that by using any available error alarm-triggering features with your protocol analyzer, you can more dynamically observe any particular errors as they occur. Examine the captured data from the respective protocol analysis session for any recorded error conditions. Ethernet Error-Correction Procedures Keep in mind that errors are not always critical. Only certain levels (for example, collisions recorded above one percent of overall traffic) that are related to a specific address may indicate a marginal failure with that network component. So when following any recommended procedures in the following sections, use your own logic as to the seriousness of the failure symptom before taking any corrective action. When examining the type of error captured during the protocol analysis session, look closely at the error frame for the following information and take appropriate notes about the type of error and any associated Ethernet addresses in the error frame. Examine the respective error frame captured during the protocol analysis session for the type of error and associated addresses in the frame. Place your captured error type into one of the following six error type categories, and go to that Ethernet error type. Next, use the address information along with the presented isolation solution to identify the error failure cause. The Ethernet frame error types are as follows. For the appropriate troubleshooting procedures for each, click on the item in the list below. For a broader description of each error, click here . Local Collision Remote Collision CRC Long Frame or Short Frame Jabber Local Collision Error Troubleshoot the addresses in the assigned node by going to the Station Node Problem Menu and the NIC Problem Menu . Keep in mind that the reporting station NIC may be the failure cause. Remote Collision Error Tr oubleshoot the other segments for local collision levels that were attached to the internetwork involved in active data transfers when the error occurred. If a segment is located with a collision level above one percent of all traffic, then follow the preceding local collision process . CRC Error Troubleshoot the CRC errors by going to the Station Node Problem Menu and the NIC Problem Menu . Keep in mind that the reporting station NIC may be the failure cause. Long or Short Frame Error Troubleshoot the addresses in the assigned node by going to the Station Node Problem Menu and the NIC Problem Menu . Keep in mind that the reporting station NIC may be the failure cause. Jabber Error Check and replace the transceiver that is transmitting a high jabber and then retest. If problems are still present, troubleshoot the addresses in the assigned node by going to the Station Node Problem Menu and the NIC Problem Menu Keep in mind that the reporting station NIC may be the failure cause. Remember that when experiencing intermittent problems such as high errors on an Ethernet network, you can use traffic-generation techniques to load the network with additional traffic to flush out certain types of intermittent failure causes. By generating additional network traffic, you can stress the network enough to cause marginal network-component failures to surface. If a particular error occurs frequently and you have thoroughly analyzed the respective error, have followed the recommended troubleshooting steps, and you still cannot conclusively locate a failure cause for the error, go to the Repeater and Hub Menu and analyze the network bandwidth. November 15, 1996 Print This Page E-mail this URL