大网数据广告活动
服务器运维问答

Unexplained 0.1% packets time out when pinging from router

· 52CE 我爱测

I'm troubleshooting a customer who requires the ability to send 5000 pings from the router to their remote site over a satellite link with zero timeouts, yet they keep experiencing one to five packets lost per test. Under ordinar…

问题原文

原帖链接 · Liesmith · CC BY-SA 3.0

I'm troubleshooting a customer who requires the ability to send 5000 pings from the router to their remote site over a satellite link with zero timeouts, yet they keep experiencing one to five packets lost per test.

Under ordinary circumstances, I'd be willing to chalk up such a low loss rate as the cost of a satellite link, but the drops only show up when pinging from the router to the remote site. To clarify, here's the involved network devices:

Outbound Traffic

  1. 192.1.1.51 Router Hub
  2. 192.1.1.52 TX Switch Hub
  3. 192.1.1.50 Encapsulator Hub
  4. 172.1.1.1 Remote Site Remote

Return Traffic

  1. 172.1.1.1 Remote Site Remote
  2. 192.1.1.28 Channel Unit Hub
  3. 192.1.1.53 RX Switch Hub
  4. 192.1.1.51 Router Hub

When pinging from the Router to the remote site, the losses show up. When pinging from a Sun server attached to the TX switch (bypassing the router), the 5000 pings complete without a single loss. This verifies the entire satellite path, and all equipment except for the router.

Then I tried sending 5000 pings from the router to all of the other devices aside from the remote site...and I got back all 5000 almost instantaneously with no drops, so the connection from the router to everything else in the path is verified good.

The router in question is a Cisco 7206VXR, and the cpu utilization doesn't appear to ever go above 50%. The highest process is only at 20%, so I'm not confident that it's simply a matter of the router dropping ICMP packets due to lower priority, particularly given the router will send 5000 packets to local devices with no issues.

I also looked into the possibility of a null route, but the only possible culprit is an essential route for remote access, according to the customer, and I can't post their running config here to get a second opinion.

Any suggestions would be greatly appreciated. I have very little networking experience, and I'm beating my head against the wall to reconcile these seemingly contradictory symptoms.

已采纳解答

原帖链接 · Liesmith · CC BY-SA 3.0

It turns out the problem was that CEF was enabled globally on the hub router, but explicitly disabled ("no ip route-cache cef") on the interface which connects to the hub LAN. Once the explicit disable statements were removed, the packet loss vanished.

I don't understand why that worked, given that there was no packet loss between the hub devices and the hub router, but I can't argue with the results.

Hopefully, this can help anyone else who is stuck trying to isolate a very minor packet loss.
Thanks again to everyone who offered advice on this issue.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2013-08-13)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。