How can I check whether the network speed is slow or the performance is poor?

Q:Network management often encounters some difficult problems, such as slow network or poor performance. At this time, if a network tester helps detect faults, it will undoubtedly greatly improve work efficiency. So how to use FLUKE's LANMETER network tester to detect slow network speed or poor performance?

A:Run the Network statistics Network Stats test to check high Network utilization and abnormal high collision rate. Apply a small amount of background traffic 100 fps llc traffic, 100 bytes per frame) and then run the test again. If you find a collision or an increase in the number of failures with the increase in transmission, you should run a Cable Scan ).

If the number of collisions exceeds 5%), run the Collision Analysis test to determine how much bandwidth is lost due to the Collision. After the bandwidth loss caused by local and remote collisions is added, fault diagnosis is required if the average value is greater than 0.5%. At the same time, check whether the collision is "abrupt", and the increase of the burst collision does not increase with the increase of network traffic. That is to say, if there is a large change in the number of collisions without a large increase in traffic, there may be serious physical layer problems somewhere. The traffic level must be related to the collision. If the network performance is at an acceptable level and the number of collisions has been large, there may be too many sites in the collision domain for transmission, or the network structure needs to be optimized to reduce the distance between network sites. Excessive collisions are often caused by physical media, such as connectors with no or incorrect ends, broken impedance, connection cables, and extruded cables ), or a bad Nic.

If the utilization rate is high, the peak value exceeds 60%), and the number of collisions is acceptable. The average value is lower than 5%), the network may be saturated. This is not possible because Ethernet segments usually have a high collision rate if they have a high utilization rate. When the utilization rate is close to 100%, the number of collisions will far exceed the number of good frames. In this case, you may need to install switches, bridges, or routers to separate the networks into subnets that are small enough to support traffic load.

Run the Network statistics Network Stats) test and check for errors other than collision ). If an Error occurs, run the Error Stats command to test and Zoom in. Then, use an Expert to test the Expert-T) to isolate specific problems or use a Cable to scan Cable) to check the cables. If the problem is intermittent, try to replace the suspected Nic, because these problems may not be displayed during testing.

Check whether the server or service that the user is connecting to is at the far end of the WAN or is connected through a route. If so, use Ping test NetWare Ping, ICMP Ping) to check the response through the network segment, and compare the result with your benchmark test or hearing test result. In order to ensure that frames are not lost, Ping tests should be performed continuously, and check that the number of requests is equal to the number of responses. The IP host often fails to respond to the first Ping request, so you need to try multiple times ). If the quantity is inconsistent, remote media or interconnect device bridges, routers, etc.) may be at full load or have problems. Frame dropping is also a symptom of a cable failure, such as the string winding of the UTP cable or the earth loop of the same axis. If a frame is suspected to be dropped, run the Cable scan Cable) to test the Cable connecting the slow site and the corresponding file server to the network, or connect any bridge or router and the cables between them.