Configuring interface delay
SR Linux supports the configuration of static and dynamic delay measurement and
provides a configuration parameter to determine precedence. You can configure both
static and dynamic delay under the same interface. The delay-selection
(
delay-selection) parameter within the network instance IGP
context (network-instance.protocols isis. instance interface.delay
) provides the following options to customize the handling. staticdynamicstatic-preferreddynamic-preferred
static or dynamic), or the designation of a
preferred option should both delay types exist (using either
static-preferred or dynamic-preferred
options). The interface delay is a link property. There may be a period between the
initialization of the interface and the reporting of a valid
dynamic delay value. This interval may require some deployments
to configure a static delay value to bridge the gap while waiting for the initial
report on link measurement. In such cases, preferring dynamic allows the routing
engine to advertise the static value until the dynamic delay report is
available..When you configure interface delay for an IGP, the IGP automatically incorporates these details in its LSP. This information is necessary for traffic engineering. For information about how the interface delay is mapped to the link state delay advertisement, see "Advertising link delay with IS-IS" in the SR Linux Segment Routing Guide.
Configuring static delay
The following example shows the configuration of static delay.
--{ * candidate shared default }--[ ]--
# info interface ethernet-1/1 subinterface 0
interface ethernet-1/1 {
subinterface 0 {
admin-state enable
unidirectional-link-delay {
static-delay 1234
}
ipv4 {
admin-state enable
address 192.168.0.0/31 {
}
}
ipv6 {
admin-state enable
address 2002::c0a8:0/64 {
}
}
}
}