ansss
asked on
Cisco6509
My device is 6509 switch with sup engine 32 and msfc is 2A. I have a P2P2 ROUTER which is connected to the next hop of the switch.ie, my switch gateway is 10.43.16.65 and router ip is 10.43.16.66.
Now the issue is when am ping the 10.43.16.66 from core I got packet drop. The first packet is always dropped. Hence there is no layer 1 issue.
Can anyone help me to resolve this issue ?
Now the issue is when am ping the 10.43.16.66 from core I got packet drop. The first packet is always dropped. Hence there is no layer 1 issue.
Can anyone help me to resolve this issue ?
Last Comment
If you ping it again within a reasonable time, does it still drop the first packet or do you get all 5 replies? It usually has to do with switch building its MAC and arp tables and not replying to ping until it's all done. I've seen this on a lot of cisco switches over the years and I don't even think about it.
When you ping from a router, it is expected for the 1st packet to drop, this is normal under circumstances and does not usually represent a problem -- the device you are pinging may not be in the arp table. The ping can be lost while the arp query is going out to find the MAC address of the device you are pinging.
Try running the ping multiple times. Try using a higher repeat count, e.g.
ping ip 10.43.16.66 repeat 20 timeout 3
See if the issue does not appear until no activity for 5 minutes or so.
Occasionally routers will also drop packets/fail to respond to a percentage of ping packets if their CPU is busy, because other processes such as forwarding production traffic and management functions are higher priority for a router than processing and responding to ping requests to the router itself.
When that happens it represents heavy load on the router, but not necessarily any kind of problem.
To test network performance ping between hosts, or use other tools that test connectivity between hosts, not routers.
Pinging a router is only a test of basic connectivity, not a reliable network performance, link quality, or loss test
Try running the ping multiple times. Try using a higher repeat count, e.g.
ping ip 10.43.16.66 repeat 20 timeout 3
See if the issue does not appear until no activity for 5 minutes or so.
Occasionally routers will also drop packets/fail to respond to a percentage of ping packets if their CPU is busy, because other processes such as forwarding production traffic and management functions are higher priority for a router than processing and responding to ping requests to the router itself.
When that happens it represents heavy load on the router, but not necessarily any kind of problem.
To test network performance ping between hosts, or use other tools that test connectivity between hosts, not routers.
Pinging a router is only a test of basic connectivity, not a reliable network performance, link quality, or loss test
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Networking Hardware-Other
Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.
28K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
One the new Sup engine we haven't have the problem.