offload-type (TWAMP)
Syntax
offload-type (inline-timestamp | none | pfe-timestamp);
Hierarchy Level (Junos OS)
[edit services rpm twamp client control-connection name test-session] [edit services rpm twamp server] [edit services rpm twamp server light]
offload-type statement,
see test-session (Junos OS
Evolved).Description
By default for most platforms, timestamps are set in the Packet Forwarding Engine host processor. To account for latency in the communication of probe messages, you can offload timestamping of the probe packets to the Packet Forwarding Engine hardware. This kind of timestamping is called inline timestamping, where the timestamping is done in hardware at the generator or the reflector, right before the packet leaves the device. Support for this offloading and inline timestamping varies by release, platform, and line card support. You cannot configure this statement for cRPD or SRX Firewalls.
Options
| inline-timestamp |
For those MX line cards that support it, timestamping performed inline in the Packet Forwarding Engine hardware at the generator, and reflection performed in the hardware at the reflector. An MX device often has a mixture of supported and unsupported line cards. When the packets reach the unsupported cards, those cards timestamp on the Packet Forwarding Engine host processor instead. If |
| none |
Timestamping performed on the Routing Engine. Default for cRPD. |
| pfe-timestamp |
(Default for most platforms) Timestamping performed in the Packet Forwarding Engine host processor. |
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement in the configuration.
Release Information
Statement introduced in Junos OS Release 25.4R1.