No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Ping Packet Loss Occurs Remotely Because a Slight Number of Error Packets Are Generated on an NE80E

Publication Date:  2013-01-07 Views:  39 Downloads:  0
Issue Description

Networking: Server--S3560—(10G LAN)NE80E--CRS-1

The NE80E can ping the server or S3560 without discarding packets irrespective of large packets or small packets. A user can ping the server remotely in any place within the province. However, packet loss occurs when a user pings the server from Beijing. About 1% of the packets are lost. However, the server can ping the NE80E, any place within the province, or Beijing without packet loss or affecting the user services.

Handling Process

Check the traffic volume on the NE80E and find that the traffic volume on the NE80E is less than 8 Gbits. However, the total upstream traffic volume is 30 Gbits. There is no problem with the forwarding capability of the NE80E.

The NE80E can ping the server or S3560 without discarding packets irrespective of large packets or small packets. A user can ping the server remotely in any place within the province. Therefore, the link connected to the NE80E is not faulty.

Ping the other servers attached to the NE40E remotely from Beijing and no packet loss occurs. It is doubted that traffic congestion occurs above the provincial network because traffic congestion on a provincial network affects all users within the province instead of several servers. Verify the analysis at 5:00 in the morning when the network is not busy and find that the problem persists. However, no packet loss occurs when the other servers attached to the NE40E are pinged, indicating that the problem is not caused by traffic congestion on the provincial network.

The server performance deterioration may cause packet loss. Since the traffic volume on the server is large, it is difficult to verify the analysis during the day. To check whether the problem is caused by the server, verify the analysis at 5:00 in the morning when the network is not busy and find that the problem persists. Therefore, the problem is not caused by the server.

It is doubted that inconsistency in the paths between Beijing and the server results in traffic congestion and therefore causes the packet loss. However, if the packet loss occurs on the provincial network, there is a probability that some of the local servers must lose packets. Since the problem only involves slight packet loss on the server attached to the NE80E and no packet loss occurs on the servers attached to the NE40E, the problem is caused by traffic congestion on the provincial network.

It is suddenly found that the count of CRC error packets increases slightly on one of the three bundled links connected to the NE80E. After the link is shut down, no packet loss occurs.

Root Cause

the count of CRC error packets increases slightly on one of the three bundled links connected to the NE80E

Solution

Resolve the CRC problem or shut down the link on which the CRC error packets are increasing.

Suggestions
Do not ignore the error packets on an interface that may cause the packet loss in the ping operation.

END