Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Configuring Global Liveness Detection for DHCP Relay Agent Clients

Requirements

• Juniper Networks MX Series routers.
• Junos OS Release 12.1R1 or later.
• Configure DHCP relay agent. See Extended DHCP Relay Agent Overview.

Overview

1. Enable liveness detection globally for DHCP relay subscribers.
2. Specify BFD as the liveness detection method for all dynamically created DHCP relay subscribers.
3. Configure BFD-specific statements to define how the protocol behaves.
4. Configure the action the router takes when a liveness detection failure occurs.

Note: This example explains how to configure liveness detection for a DHCPv4 network. Liveness detection is also supported for DHCPv6 configurations. To configure DHCPv6 liveness detection, include the liveness-detection statement, and any subsequent configuration statements, at the [edit forwarding-options dhcp-relay dhcpv6] or [edit forwarding-options dhcp-relay dhcpv6 group group-name] hierarchy level.

Configuration

Step-by-Step Procedure

1. Specify that you want to configure liveness detection.
   [edit forwarding-options dhcp-relay]user@host# edit liveness-detection
2. Specify that you want to configure the liveness detection method.
   [edit forwarding-options dhcp-relay liveness-detection]user@host# edit method
3. Specify BFD as the liveness detection method that you want DHCP to use.
   [edit forwarding-options dhcp-relay liveness-detection method]user@host# edit bfd
4. Configure the detection time threshold (in milliseconds) at which a trap is produced.
   [edit forwarding-options dhcp-relay liveness-detection method bfd]user@host# set detection-time threshold 50000
5. Configure the time (in milliseconds) for which BFD holds a session up notification.
   [edit forwarding-options dhcp-relay liveness-detection method bfd]user@host# set holddown-interval 50
6. Configure the BFD minimum transmit and receive interval (in milliseconds).
   [edit forwarding-options dhcp-relay liveness-detection method bfd]user@host# set minimum-interval 45000
7. Configure the minimum receive interval (in milliseconds).
   [edit forwarding-options dhcp-relay liveness-detection method bfd]user@host# set minimum-receive-interval 60000
8. Configure a multiplier value for the detection time.
   [edit forwarding-options dhcp-relay liveness-detection method bfd]user@host# set multiplier 100
9. Disable the ability for BFD interval timers to change or adapt to network situations.
   [edit forwarding-options dhcp-relay liveness-detection method bfd]user@host# set no-adaptation
10. Configure the BFD session mode.
    [edit forwarding-options dhcp-relay liveness-detection method bfd]user@host# set session-mode automatic
11. Configure the threshold and minimum interval for the BFD transmit interval.
    [edit forwarding-options dhcp-relay liveness-detection method bfd]user@host# set transmit-interval threshold 60000 minimum-interval 45000
12. Configure the BFD protocol version you want to detect.
    [edit forwarding-options dhcp-relay liveness-detection method bfd]user@host# set version automatic
13. Configure the action the router takes when a liveness detection failure occurs. In this example, the failure action is to clear the client session only when a liveness detection failure occurs and the local interface is detected as being up.
    [edit forwarding-options dhcp-relay liveness-detection]user@host# edit failure-action action

Results

From configuration mode, confirm your configuration by entering the show forwarding-options command. If the output does not display the intended configuration, repeat the instructions in this example to correct it. The following output also shows a range of configured interfaces in group frankfurt.

If you are done configuring the device, enter commit from configuration mode.