Ping and Traceroute Commands

Overview

RBFS provides the following ping and traceroute functionalities:

  • IP Ping

  • IP Ping over an MPLS Transport

  • IP Traceroute

  • IP Traceroute over an MPLS Transport

  • MPLS LSP Ping

  • MPLS LSP Traceroute

IP Ping

IP Ping is a tool that tests network reachability by sending ICMP echo requests. It provides information about the round-trip time of the packets and their status. PI Ping tests network reachability by sending ICMP echo requests. It provides information about the round-trip time (RTT) of the packets and their status. Ping is primarily used to verify general IP connectivity and diagnose basic network issues.

This utility performs a basic connectivity test using ICMP Echo Request and Reply messages. It checks the reachability of IP addresses between two endpoints, measures round-trip time, and assesses packet loss. The process works by sending ICMP Echo Requests from a source to a destination IP address. If the destination is reachable, it responds with Echo Reply messages.

IP Ping over an MPLS Transport

RBFS support ping utility that pings from one IP endpoint to another endpoint within an MPLS network. This ping checks the IP connectivity across an MPLS backbone and determines whether MPLS forwarding allows the IP packet to reach its destination. The originating device send standard ICMP packets. These packets are label-switched within the MPLS core and are decapsulated at the egress edge router before reaching the destination. This method is used to validate Layer 3 VPN/IP reachability through an MPLS transport network.

IP Traceroute

IP Traceroute is a utility that is used to get information about the hop-by-hop path IP packets take between two devices. It identifies each router in the sequence and measures the latency for every hop. It can detect routing loops or points of packet loss. Traceroute operates by sending IP packets (using UDP, ICMP, or TCP) with progressively increasing Time-to-Live (TTL) values. Each router that decrements the TTL responds with a 'TTL exceeded' message, providing its address. Traceroute is useful for visualizing the exact route the traffic traverse across an IP network.

IP Traceroute over an MPLS Transport

IP Traceroute over an MPLS Transport allows you to trace an IP path between two endpoints when the underlying network uses MPLS for forwarding. The traceroute is initiated at the IP layer, the packets are transported through the MPLS core using label switching. It enables to understand how IP packets traverse an MPLS-based infrastructure and ensures that the IP reachability across the MPLS backbone. This utility allows to validate end-to-end connectivity across an MPLS core, especially in environments where IP traffic is tunneled or carried over label-switched paths.

It helps identify forwarding issues, pinpoint bottlenecks or failures within the MPLS transport, and verify correct label handling by transit routers. It provides visibility into the forwarding behavior of IP packets across the MPLS cloud, IP Traceroute over MPLS and enhances troubleshooting.

MPLS LSP Ping

RBFS supports MPLS LSP (Label Switched Path) Ping that enables administrators to verify an LSP. LSP Ping works by sending packets through chosen LSP to a specific destination (remote endpoint) and checks for a response. It helps to identify if a Label Switched Path is disrupted.

A labeled packet (echo request) is sent towards a destination FEC to verify that this packet terminates at the correct egress LSR that services the FEC. If the egress node’s Echo Reply message is received, it confirms that the LSP is established successfully.

MPLS LSP ping currently supports IS-IS for both IPv4 and IPv6 SID-Index, as well as LDP protocol for IPv4 and IPv6 FECs.

MPLS LSP Traceroute

The MPLS LSP Traceroute utility is designed to verify the label switch path by sending MPLS Echo Request packets. It uses the Time-to-Live (TTL) mechanism to determine how many MPLS hops an MPLS packet goes through. This utility can map the route a packet takes to its destination and provides information about each hop, including the latency at each point.

As each Label Switching Router (LSR) along the path receives the packet, it decrements the MPLS TTL. When the TTL reaches 1, the router sends back an MPLS Echo Reply. The source router then sends additional MPLS Echo Request packets with TTL values incrementing from 2, 3, and so on. Each time, a different LSR in the path responds as the TTL expires. This process continues until the egress LSR is reached.

MPLS LSP traceroute supports IS-IS for both IPv4 and IPv6 SID-Index, as well as LDP for both IPv4 and IPv6 FECs.

Supported Platforms

Not all features are necessarily supported on each hardware platform. Refer to the Platform Guide for the features and the sub-features that are or are not supported by each platform.