Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


MX Series Router Cloud CPE DHCP Services Overview

Using cCPE services, you can provide DHCP server and DHCP relay services to your customers.

DHCP Server

You can use the MX Series router DHCP server function in a VPN routing instance to provide DHCP services to Layer 2 CPEs. To use this service, enable the DHCP server in at least one routing instance corresponding to the subscriber VPN site; for all other sites you can use the DHCP relay agent pointing to the same DHCP server. In addition, you need to configure the address pools within the VRF routing instance. The address pools you configure for the VPN site need to be part of the subscriber’s private subnets configured for the IRB interface.

To protect the Routing Engine from DHCP flooding, you can define interface-specific firewalls.


The address assignment pool feature is part of the Junos Subscriber Management Feature Pack license. You must install and properly configure the license to meet the requirements for using the address assignment pool feature. The license includes 1000 address bindings.

DHCP Relay Agent

The MX Series router extended DHCP relay agent forwards DHCP request-reply packets between a DHCP client and a central DHCP server. You configure the relay agent within the cCPE context; in other words, within the VRF routing instance. Typically, the subscriber owns and operates the central DHCP server, and manages the address pools.


The stateless DHCP relay agent, which you can configure under the [routing-instance routing-instance forwarding-options helpers bootp] edit hierarchy, cannot coexist with the DHCP server in the same MX Series router, even if they are configured in different routing instances.