bulk-leasequery (DHCP Relay Agent)

Syntax

Hierarchy Level

Description

Enable support for bulk leasequery on a DHCPv4 or DHCPv6 relay agent. You can also configure parameters that the DHCP relay agent uses when sending DHCP bulk leasequery messages to obtain lease information from the DHCP local servers in the logical system/routing instance.

Note:

You must also configure support on the relevant DHCP local servers with the allow-leasequery statement.

Options

attempts number-of-attempts

Specify the number of times the DHCP relay agent attempts to send DHCP bulk leasequery messages to the configured DHCP servers in the logical system/routing instance. DHCP relay agent resends the query message if the configured timeout value is reached, and either a confirmed reply or a reply from all configured DHCP servers has not been received. DHCP relay agent sends the subsequent messages only to the DHCP servers that have not replied to previous queries.

Range:
- (DHCPv4 bulk leasequery) 1 through 10
- (DHCPv6 bulk leasequery) 1 through 720
Default:
- (DHCPv4 bulk leasequery) 6
- (DHCPv6 bulk leasequery) 360

timeout seconds

Specify the number of seconds that DHCP relay agent waits before resending a leasequery message to the DHCP servers when all servers have not responded to a previous message.

Range: 1 through 10
Default: 10

trigger automatic

(DHCPv6 only) Specify that the DHCPv6 relay agent always sends a bulk leasequery message whenever the jdhcp daemon is started or restarted and there are no bound subscribers in the session database. The automatic trigger updates the DHCP relay agent’s binding information for clients associated with the requesting DHCPv6 relay agent.

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 Release 16.1.

ON THIS PAGE