[an error occurred while processing this directive] [an error occurred while processing this directive]
 

dhcp-local-server

Syntax

  dhcp-local-server { authentication { password password-string; username-include { circuit-type; delimiter delimiter-character; domain-name domain-name-string; logical-system-name; mac-address; option-60; option-82 <circuit-id> <remote-id>; routing-instance-name; user-prefix user-prefix-string; } } dhcpv6 { authentication { password password-string; username-include { circuit-type; client-id; delimiter delimiter-character; domain-name domain-name-string; logical-system-name; relay-agent-interface-id; relay-agent-remote-id; relay-agent-subscriber-id; routing-instance-name; user-prefix user-prefix-string; } } group group-name { authentication { password password-string; username-include { circuit-type; client-id; delimiter delimiter-character; domain-name domain-name-string; logical-system-name; relay-agent-interface-id; relay-agent-remote-id; relay-agent-subscriber-id; routing-instance-name; user-prefix user-prefix-string; } } interface interface-name <upto upto-interface-name> <exclude>; overrides { interface-client-limit number; } } } overrides { interface-client-limit number; } } dynamic-profile profile-name <aggregate-clients (merge | replace) | use-primary primary-profile-name>; group group-name { authentication { password password-string; username-include { circuit-type; delimiter delimiter-character; domain-name domain-name-string; logical-system-name; mac-address; option-60; option-82 <circuit-id> <remote-id>; routing-instance-name; user-prefix user-prefix-string; } } dynamic-profile profile-name <aggregate-clients (merge | replace) | use-primary primary-profile-name>; interface interface-name <upto upto-interface-name> <exclude>; overrides { client-discover-match; interface-client-limit number; no-arp; } } overrides { client-discover-match; interface-client-limit number; no-arp; } pool-match-order { ip-address-first; option-82; } traceoptions { file filename <files number> <size size> <world-readable | no-world-readable> <match regex>; flag flag; } }

Hierarchy Level

  [edit logical-systems logical-system-name routing-instances routing-instance-name system services], [edit logical-systems logical-system-name system services], [edit routing-instances routing-instance-name system services], [edit system services]

Release Information

Statement introduced in JUNOS Release 9.0.

The dhcpv6 stanza added in JUNOS Release 9.6.

Description

Configure Dynamic Host Configuration Protocol (DHCP) local server options on the router and enable the router to function as an extended DHCP local server. The DHCP local server receives DHCP request and reply packets from DHCP clients and then responds with an IP address and other optional configuration information to the client.

The DHCP local server supports the attachment of dynamic profiles and also interacts with the local AAA Service Framework to use back-end authentication servers, such as RADIUS, to provide subscriber authentication. You can configure dynamic profile and authentication support on a global basis or for a specific group of interfaces.

The DHCP local server also supports the use of JUNOS address-assignment pools or external authorities, such as RADIUS, to provide the client address and configuration information.

The extended DHCP local server is incompatible with the J Series routers DHCP server and is not supported on J Series routers. Also, the DHCP local server and the DHCP/BOOTP relay, which are configured under the [edit forwarding-options helpers] hierarchy level, cannot both be enabled on the router at the same time. The extended DHCP local server is fully compatible with the extended DHCP relay feature.

The dhcpv6 stanza configures the router to support Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The DHCPv6 local server is fully compatible with the extended DHCP local server and the extended DHCP relay feature.

Note: When you configure the dhcp-local-server statement at the routing instance hierarchy level, you must use a routing instance type of virtual-router.

The statements are explained separately.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.


Published: 2009-07-07

[an error occurred while processing this directive]