Juniper EX3400

liveness-detection
Syntax liveness-detection {
failure-action (clear-binding | clear-binding-if-interface-up | log-only);
method {
bfd {
version (0 | 1 | automatic);
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
detection-time {
threshold milliseconds;
}
session-mode(automatic | multihop | singlehop);
holddown-interval milliseconds;
}
}
}
Hierarchy Level [edit system services dhcp-local-server],
[edit system services dhcp-local-server dhcpv6],
[edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit system services dhcp-local-server group group-name],
[edit system services dhcp-local-server dhcpv6 group group-name],
[edit forwarding-options dhcp-relay group group-name],
[edit forwarding-options dhcp-relay dhcpv6 group group-name]
Release Information Statement introduced in Junos OS Release 12.1.
Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Description Configure bidirectional failure detection timers and authentication criteria for static
routes.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege
Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
DHCP Liveness Detection Overview on page 95•
• Configuring Detection of DHCP Local Server Client Connectivity on page 96
• Configuring Detection of DHCP Relay or DHCP Relay Proxy Client Connectivity on
page 98
• Example: Configuring Group Liveness Detection for DHCP Local Server Clients
227Copyright © 2017, Juniper Networks, Inc.
Chapter 12: Configuration Statements (DHCP and DHCP Relay)