Skip to main content
Skip table of contents

2570 - Configuring DHCP Services in Universal DDI

Scenario

The DHCP service needs to be enabled on two NIOS-X Servers before we begin to configure DHCP services. Then we need to plan Global Options and configure an initial DHCP Config Profile for the DHCP clients to use.

Estimated Completion Time

  • 15 to 20 minutes

Prerequisites

Course References

  • 2170 DHCP Services

Tasks

  1. Enabling DHCP service Instances for NIOS-X Servers oph1 and  oph2.

  2. Creating an Option Group for Techblue NYC Branch.

  3. Configuring the DHCP Config Profile for Techblue NYC Branch.

  4. Applying the DHCP Config Profile to a Service Instance.

Task 1: Enabling DHCP service instances for NIOS-X servers oph1 and oph2  

  • A DHCP service instance needs to be created for two NIOS-X servers, oph1.techblue.net and oph2.techblue.net.

  • Name the services Techblue DHCP service 1 and Techblue DHCP service 2 per the table below:

Server IP Address

Server Name

Service Name

10.100.0.110

oph1.techblue.net

Techblue DHCP service 1

10.200.0.110

oph2.techblue.net

Techblue DHCP service 2

Task 2: Creating an Option Group for Techblue NYC Branch

  • Create an IPv4 Option Group named Techblue NYC Branch using the specifications from the following table:

Type

Space

Name (code)

Value(s)

Option

DHCPv4

domain-name-servers (6)

10.100.0.110,10.200.0.110

Option

DHCPv4

domain-name (15)

techblue.net

Option

DHCPv4

ntp-servers (42)

10.100.0.10

Option

DHCPv4

routers (3)

172.31.101.1

Task 3: Configuring the DHCP Config Profile for the Techblue NYC Branch

  • Create a new DHCP Config Profile named Techblue NYC Branch with a short lease time of 4 minutes to account for some DHCP client testing.

  • Allow leases for unknown clients.

  • Use the IPv4 DHCP Option Group we created called Techblue NYC Branch.

Task 4: Applying the DHCP Config Profile to a Service Instance

  • Apply the DHCP Config Profile to the Service Instance Techblue DHCP service 1 but not Techblue DHCP service 2 yet.


Solutions

Task 1 Solution: Enabling DHCP service instances for NIOS-X servers oph1 and oph2  

When starting, the Service Status will change from Stopped to Online. It may also indicate Error in this process. It may take 3 to 5 minutes for the service to show as Online. If the service remains stopped, attempt to restart it by selecting the checkbox for the service and choosing Restart from the Service Actions drop-down menu.

  1. Log into your lab’s jump-desktop.

  2. Use your Education Infoblox Portal Credentials to log into the Infoblox Portal.

  3. Navigate to ConfigureService Deployment Protocol Services.

  4. Click on Create Service and choose DHCP from the drop-down menu.

    image-20250107-130206.png
  5. Enter the name Techblue DHCP Service 1.

  6. Click on Select Server and locate the NIOS-X server with the name oph1.techblue.net. If you do not see it on the list, review tasks from Deploying NIOS-X Servers to ensure that you have changed the NIOS-X server names correctly.

  7. Select the Server and click on the Select button on the right.

  8. Click Next and confirm this is the correct NIOS-X server.

  9. Click Finish and then Save & Close.

    image-20250107-130512.png
  10. Repeat steps 4 to 9 to create a second service called Techblue DHCP Service 2 and locate the server with the name oph2.techblue.net.

  11. Refresh the page until you see each service indicates Online.

Task 2 Solution: Creating an Option Group for the Techblue NYC Branch

We'll need an IPv4 Option Group to offer specific DHCP options to any clients getting an IP address from these DHCP servers. We will create an IPv4 Option Group named Techblue NYC Branch using the specifications from the following table:

Type

Space

Name (code)

Value(s)

Option

DHCPv4

domain-name-servers (6)

10.100.0.110,10.200.0.110

Option

DHCPv4

domain-name (15)

techblue.net

Option

DHCPv4

ntp-servers (42)

10.100.0.10

Option

DHCPv4

routers (3)

172.31.101.1

  1. We start by navigating to Configure NetworkingIPAM/DHCP.

  2. Select the Option Groups tab.

    image-20250107-130930.png
  3. Click Create and choose the IPv4 Option Group selection.

    image-20250107-131041.png
  4. Give the Option Group a name: Techblue NYC Branch.

  5. Configure the Domain Name Servers DHCP option:

    1. Under DHCP OPTION CODES, click Add

    2. From the Type drop-down menu, select Option

    3. From the Space drop-down menu, select dhcp4

    4. From the Name drop-down menu, select domain-name-servers (6)

    5. Specify the Value: 10.100.0.110, 10.200.0.110

      image-20250107-131643.png
  6. Configure the Domain Name DHCP option:

    1. Under DHCP OPTION CODES, click Add

    2. From the Type drop-down menu, select Option

    3. From the Space drop-down menu, select dhcp4

    4. From the Name drop-down menu, select domain-name (15)

    5. Specify the Value: techblue.net

  7. Configure NTP Servers DHCP option:

    1. Under DHCP OPTION CODES, click Add

    2. From the Type drop-down menu, select Option

    3. From the Space drop-down menu, select dhcp4

    4. From the Name drop-down menu, select ntp-servers (42)

    5. Specify the Value: 10.100.0.10

  8. Configure routers DHCP option:

    1. Under DHCP OPTION CODES, click Add

    2. From the Type drop-down menu, select Option

    3. From the Space drop-down menu, select dhcp4

    4. From the Name drop-down menu, select routers (3)

    5. Specify the Value: 172.31.101.1

image-20250107-132010.png
  1. Click Save & Close

Task 3 Solution: Configuring the DHCP Config Profile for Techblue NYC Branch

We want to use our new Option Group with the Techblue NYC Branch DHCP clients, and we want to be able to designate specific settings for the Techblue NYC Branch DHCP service that may differ from the Global Configuration. We can do this with a DHCP Config Profile. Create a new DHCP Config Profile named Techblue NYC Branch with a short lease time of 4 minutes to account for some DHCP client testing. We also want to allow leases for unknown clients. For DHCP Options, we want to use the IPv4 DHCP Option Group we created called Techblue NYC Branch.

  1. We start by navigating to Configure NetworkingIPAM/DHCP.

  2. Select the DHCP Config Profiles tab.

    image-20250107-132342.png
  3. Click the Create DHCP Config Profile button.

  4. Give the DHCP Config Profile a name: Techblue NYC Branch.

    image-20250107-132631.png
  5. Under DHCP Configuration, expand the Leases section.

  6. For our lab environment, we want changes to show quickly, so configure the Lease Time as 4 minutes (you will need to click the Override toggle to override the default setting). 

  7. Enable/check Allow Leases for Unknown Clients (you will need to click the Override toggle to override the default setting).

    image-20250107-132827.png
  8. Collapse the Leases section and expand the DHCP Options section.

  9. Under IPV4 DHCP Option Codes, click Add.

  10. From the Type drop-down menu, select Option Group.

  11. From the Name drop-down menu, select Techblue NYC Branch.

    image-20250107-133052.png
  12. Click Save & Close

Task 4 Solution: Applying the DHCP Config Profile to a Service Instance

Our DHCP Config Profile has not been applied to any DHCP services yet. We will now apply the DHCP Config Profile to the Service Instances we started on Techblue DHCP Service 1.

  1. Navigate to Configure NetworkingIPAM/DHCP.

  2. Select the DHCP Config Profiles tab.

  3. Click the hamburger icon next to the TechBlue NYC Branch DHCP Config Profile, and select Edit.

    image-20250107-133401.png
  4. Under Select Service Instance, click Add

  5. Select the service instance Techblue DHCP Service 1 from the list and click Select. (Note: Do not add Techblue DHCP Service 2 yet. It will be used in a later lab.)

    image-20250107-133558.png
  6. Click Save & Close


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.