Configuring A Dhcp Client; Minimum Dhcp Client Configuration; Configuring Optional Dhcp Client Attributes - Juniper ACX1000 Configuration Manual

ACX Series Universal Access Router Configuration Guide

Configuring a DHCP Client

Minimum DHCP Client Configuration

Configuring Optional DHCP Client Attributes

360
Minimum DHCP Client Configuration on page 360
Configuring Optional DHCP Client Attributes on page 360
Verifying and Managing DHCP Client Configuration on page 361
The following sample output shows the minimum configuration you must use to configure
an ACX Series router as a DHCP client. In this output, the interface is ge-0/0/0 and the
logical unit is 0.
[edit interfaces]
ge-0/0/0 {
unit 0 {
family inet {
dhcp-client
}
}
}
NOTE: To configure a DHCP client in a routing instance, add the interface in
a routing instance using the [edit routing-instances] hierarchy.
For an ACX Series router to operate as a DHCP client, you configure a logical interface
on the router to obtain an IP address from the DHCP local server in the network. You can
then set the client-identifier, lease time, retransmission attempts, retransmission interval,
preferred DHCP local server address, vendor class ID, and update server.
To configure optional DHCP client attributes:
Configure the DHCP client identifier as the routing instance name.
1.
DHCP client identifier as a user ID.
[edit interfaces ge-0/0/1 unit 0 family inet dhcp-client]
user@host# set client-identifier user-id {ascii ascii | hexadecimal hexadecimal}
DHCP client identifier as the description of an interface.
[edit interfaces ge-0/0/1 unit 0 family inet dhcp-client]
user@host# set client-identifier use-interface-description {logical | device}
DHCP client identifier as a prefix:
[edit interfaces ge-0/0/1 unit 0 family inet dhcp-client]
user@host# set client-identifier prefix [host-name logical-system-name
routing-instance-name]
Configure the DHCP client identifier prefix as the routing instance name.
2.
[edit interfaces ge-0/0/1 unit 0 family inet dhcp-client]
Copyright © 2017, Juniper Networks, Inc.