Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos OS] ICMP Ping Showing Latency for Host Inbound and Outbound traffic



Article ID: KB28157 KB Last Updated: 05 Sep 2019Version: 2.0

This article discusses latency in ICMP pings when a Junos OS platform is responsible for ICMP echo reply.


An ICMP ping shows intermittent latency on a directly connected link with the default Junos Class of Service (CoS) configuration.



router1 ( router2


From router1, ping the directly connected interface IP

router1> ping

64 bytes from icmp_seq=28 ttl=64 time=0.524 ms
64 bytes from icmp_seq=29 ttl=64 time=0.503 ms
64 bytes from icmp_seq=30 ttl=64 time=16.205 ms
64 bytes from icmp_seq=31 ttl=64 time=0.543 ms
64 bytes from icmp_seq=32 ttl=64 time=32.299 ms

Note that the time is nearly 0.5 ms for most of the ping requests, but in some instances we see a value which is much larger.

Although ICMP is a great way to check for link availability, it is not a good way to test latency or delay on a Juniper Networks platform. One of the best and most accurate ways to test for latency is to simulate data plane traffic using a traffic generator for the transit traffic.

Juniper Networks platform architecture separates the control plane from the data plane. There are various rate-limiting and prioritization functions within the packet forwarding engine (PFE) and the routing engine. When a ping is sent from the routing platform to the end device, it is using the control plane on the local router in order to generate the ICMP request packet. The control plane is used again when the ICMP reply packet is received from the end device.

ICMP messages are considered low priority within Junos OS, so the routing platform will respond to and process other higher priority messages, such as routing updates, before processing the ICMP messages. The microkernel may introduce tens of milliseconds of processing delay to ICMP message handling. The delay is not uniform, meaning that some ICMP messages might be delayed while others may not be delayed. This matches the behavior observed here with the testing.

ICMP ping latency in traffic generated for the device itself is not a recommended way of testing the bandwidth or integrity of the link.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search