source-routing
Syntax
source-routing {
forward (srmpls-nodes <label hop1...n> | srv6-nodes <IPv6 SID hop1...n>);
return (srmpls-nodes <label hop1...n> | srv6-nodes <IPv6 SID hop1...n>);
}Hierarchy Level
[edit services monitoring twamp client control-connection name test-session name]
Description
TWAMP supports segment routing as defined in RFC 8402, which broadly specifies the segment routing architecture. We support two types of segment routing 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. In addition, you can specify the same information for the return path 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, as appropriate depending on the segment routing type. The TWAMP probes are timestamped in either the Routing Engine or the Packet Forwarding Engine.
You do not have to configure anything additional on the TWAMP server to activate this feature. You can specify only the forward path, only the return path, or both paths. If configuring both paths, the forward and return paths should be of the same type.
Options
| forward (srmpls-nodes <label hop1...n> | srv6-nodes <IPv6 SID hop1...n>) | Specify the forward path. |
| return (srmpls-nodes <label hop1...n> | srv6-nodes <IPv6 SID hop1...n>) | Specify the return path. |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Evolved Release 24.4R1.