Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring MX Series Router Cloud CPE DHCP Services

1. Configuring the DHCP Server on the MX Series Router for the cCPE Context
2. Configuring Subscriber Address Pools for MX Series Router Cloud CPE DHCP Services

Configuring the DHCP Server on the MX Series Router for the cCPE Context

1. Configure the DHCP server in each routing instance that corresponds to a subscriber VPN site.
   [edit]user@host# edit routing-instances acme system services dhcp-local-server group default-group interface irb.subscriber-vlan-unit-id
2. (Optional) When you configure a DHCP server in a VRF, if you want the server to handle DHCP requests sent by DHCP relay agents located at remote sites of the same VPN, you need to add tunnel interfaces to the DHCP server. Specifically, you need to add the following configuration to the DHCP server:
   user@host set routing-instances acme system services dhcp-local-server group default-group interface lsi.0 upto lsi.16385

Configuring Subscriber Address Pools for MX Series Router Cloud CPE DHCP Services

Configure the address pools within the subscriber’s VRF routing instance. The address pools that you configure for the VPN site need to be part of the subscriber’s private subnets, configured for the IRB interface.

1. Configure the address pools within the subscriber’s routing instance.
   [edit]user@host# edit routing-instances subscriber-id access address-assignment pool acme-pool family inet
2. Configure the subnet information for the IPv4 address-assignment pool.
   [edit routing-instances acme access address-assignment pool acme-pool family inet]user@host# set network prefix/prefix-length
3. Configure a named range of IPv4 addresses, used within the address-assignment pool.
   1. Define the lower limit of the address range.
      [edit routing-instances acme access address-assignment pool acme-pool family inet]user@host# set range r1 low lower-limit
   2. Define the upper limit of the address range.
      [edit routing-instances acme access address-assignment pool acme-pool family inet]user@host# set range r1 high upper-limit
   3. Repeat the process for each subscriber and address range.
4. Configure address pools that can be used by different client applications. In the following example, we configure the DNS, WINS, and router servers, however, there are many other DHCP attributes that you can configure depending on your network requirements.
   1. Specify a DNS server to which clients can send DNS queries.
      [edit routing-instances acme access address-assignment pool acme-pool family inet]user@host# edit dhcp-attributes[edit routing-instances acme access address-assignment pool acme-pool family inet dhcp-attributes]user@host# set name-server dns-server-ip-address
   2. Specify one or more NetBIOS name servers that the client uses to resolve NetBIOS names.
      [edit routing-instances acme access address-assignment pool acme-pool family inet dhcp-attributes]user@host# set wins-server wins-server-ip-address
   3. Specify one or more routers located on the client’s subnet.
      [edit routing-instances acme access address-assignment pool acme-pool family inet dhcp-attributes]user@host# set router router-ip-address
5. Review the configuration.
   [edit routing-instances acme access address-assignment pool acme-pool family inet]user@host# show

   pool acme-pool {
       family inet {
           network 10.10.1.1/32;
           range r1 {
               low 10.10.0.1;
               high 10.10.10.10;
           }
           dhcp-attributes {
               name-server {
                   10.10.1.2;
               }
               wins-server {
                   10.10.1.3;
               }
               router {
                   10.10.1.4;
               }
           }
       }
   }