Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Services Applications

  • RFC 8402 SR support for TWAMP probes (MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—We have added support in Two-Way Active Measurement Protocol (TWAMP) for segment routing (SR) as defined in RFC 8402, which broadly specifies the SR architecture. We support two types of SR for TWAMP probes:

    • SR-MPLS: Uses a list of labels, each representing a segment end node.

    • SRv6: Uses a type 4 IPv6 routing header introduced in RFC 8754, with each segment end node represented as an IPv6 address or IPv6 segment identifier (SID).

    You can specify the list of SR-MPLS or SRv6 segments for a TWAMP probe to reach the reflector and from the reflector to the client. This return path information is embedded in the probe itself by using the extensions proposed in Simple TWAMP (STAMP) Extensions for Segment Routing Networks, draft-ietf-ippm-stamp-srpm, namely, the return path TLV and its return segment list sub-TLVs. The information is embedded depending on the segment routing type. The device timestamps the TWAMP probes in either the Routing Engine or the Packet Forwarding Engine.

    To configure this feature, include the source-routing statement at the [edit services rpm twamp client control-connection name test-session session-name hierarchy level.

    [See Understand Two-Way Active Measurement Protocol and source-routing.]

  • Use FQDN targets in RPM probes (MX204, MX240, MX304, MX480, and MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—Configure a real-time performance monitoring (RPM) probe test with a fully qualified domain name (FQDN) target (instead of an IPv4 or IPv6 address) to adapt to endpoint address changes. The device resolves the FQDN through the Domain Name System (DNS) at the start of each test and then sends probes to the resolved address at each interval. Telemetry first displays the FQDN until resolution and then shows the destination address to help you track changes. If DNS resolution fails, the probe results retain the FQDN as the target address. Configure the fqdn or the fqdnv6 option at the [edit services rpm probe owner test test-name target] hierarchy level.

    [See target.]

  • Traffic selector support for inline IPsec (MX304, MX10004, and MX10008)— Inline IPSec encrypts and decrypts IPsec tunnel traffic directly within the Packet Forwarding Engine. by eliminating the need for a dedicated services card. A traffic selector is an agreement between IKE peers to permit traffic through a tunnel if the traffic matches a specified pair of local and remote addresses.

    [See Inline IPSec.]