Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

DHCP for Tenant Systems

Understanding DHCP support for Tenant Systems

Starting in Junos OS Release 18.4R1, a tenant system supports the DHCP client feature to learn IP addresses for interfaces assigned to the tenant systems. Additionally, starting in Junos OS Release 18.4R1, tenant systems support the DHCP relay feature. A DHCP relay agent forwards DHCP requests and responses between the DHCP client and the DHCP server.

An interface of an SRX Series device operating as a DHCP client receives the TCP or IP settings and the IP address from an external DHCP server.

An SRX Series device operating as a DHCP relay agent for tenant systems forwards incoming requests from the DHCP clients to a specified DHCP server. The client requests pass through interfaces on the tenant systems.

Minimum DHCPv6 Relay Agent Configuration for Tenant Systems

The following example describes the minimum configuration required to configure an SRX Series device as a DHCPv6 relay agent for the tenant system.

Before you begin determine the following:

  • The DHCP routing instance name, the DHCP relay group and the DHCP active server-group for the tenant system.

  1. Create a DHCPv6 relay group that includes at least one interface for the tenant system.
  2. Specify the DHCP group and add interfaces belonging to the group.
  3. Specify the name of the server-group and add the IP address for the DHCP servers belonging to the same group.
  4. Specify the name of the active server-group.
  5. Confirm your configuration by entering the show tenants TSYS1 routing-instances R1 command.

Example: Configuring a DHCPv6 Client for Tenant Systems

This example shows how to configure a device as a DHCPv6 client for tenant systems.

Requirements

This example uses the following hardware and software components:

  • An SRX Series device

  • Junos OS Release 18.4R1

Before you begin:

  • Read the Understanding DHCP support for Tenant Systems to understand how and where this procedure fits in the overall tenant systems support for DHCP.

    No special configuration beyond device initialization is required before configuring this feature.

Overview

In this example, a tenant system administrator configures an SRX Series device as a DHCPv6 client for a tenant system.

The DHCPv6 client for a tenant system includes the following features:

  • Identity association for non-temporary addresses (IA_NA)

  • Identity association for prefix delegation (IA_PD)

  • Autoconfig or stateful mode

  • DHCP unique identifier (DUID)

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring DHCPv6 Client in a Tenant System

Procedure

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide.

  1. Configure security zones to permit traffic for a tenant system.

  2. Create a routing instance and assign the routing instance type to a tenant system.

  3. Specify the interface name for the routing instance.

  4. Configure the DHCPv6 client type. The client type can be autoconfig or stateful for a tenant system.

    • To enable DHCPv6 auto configuration mode, configure the client type as autoconfig.

    • For stateful address assignment, configure the client type as stateful.

  5. Specify the identity association type.

    • To configure identity association for nontemporary address (IA_NA) assignment, specify the client-ia type as ia-na.

    • To configure identity association for prefix delegation (IA_PD), specify the client-ia-type as ia-pd.

  6. Configure the DHCPv6 client identifier by specifying the DHCP unique identifier (DUID) type for the tenant system. The following DUID type is supported:

    • Link Layer address (duid-ll)

  7. Specify the DHCPv6 client requested option as dns-server for the tenant system.

  8. Configure the router advertisement.

Results

  • From configuration mode, confirm your configuration by entering the show tenants TSYS1 command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

  • From configuration mode, confirm your configuration by entering the show protocols command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

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

Verification

To confirm that the configuration is working properly, perform these tasks:

Verifying the DHCPv6 Client for the Tenant System

Purpose

Verify that the DHCPv6 client information is configured.

Action

From the operational mode, enter the show dhcpv6 client binding tenant TSYS1 command.

Meaning

The output displays the address binding information for the tenant system.

Verifying the DHCPv6 Client Binding for the Tenant System

Purpose

Verify that the DHCPv6 client binding information is configured.

Action

From the operational mode, enter the show dhcpv6 client binding detail tenant TSYS1 command.

Meaning

The output displays the detailed client binding information for the tenant system.

Verifying the DHCPv6 Client Statistics Information for the Tenant System

Purpose

Verify that the DHCP client statistics information is configured.

Action

From the operational mode, enter the show dhcpv6 client statistics tenant TSYS1 command.

Meaning

The output displays the information about the number of packets discarded, the number of messages received and the number of messages sent by the DHCP client for the tenant system.