Skip to main content
Skip table of contents

2539 - Discovering networks in NIOS


After provisioning the new network in one of your data center, you notice some clients that were not provisioned with your knowledge. Use the network discovery function in NIOS to help you discover what other devices may be on the network.

Estimate Completion Time

  • 10 to 15 minutes






Grid Manager UI




  • Administrative access to the Grid

Course References

  • 2010: Configuring NIOS IPAM and Discovery

Lab Initiation

Access jump-desktop

Once the lab is deployed, you can access the virtual machines required to complete this lab activity. To initiate the lab, click on the jump-desktop tile and login to the Linux UI:

Username: training

Password: infoblox

Initiate lab

To initiate the lab, double-click the Launch Lab icon on the Desktop.

Launch Lab

Launch Lab

Choose the lab number from the list and click OK.

After clicking OK, you will see a pop-up message with a brief description of the lab task. If the description looks correct, click Yes to continue lab initiation.

Lab initiation will take a couple of minutes to finish.

Once complete, you will see another pop-up message with the login credentials and the URL for the Grid Manager’s User Interface. Note that the credentials may differ from those from prior labs.

Screenshot 2024-05-06 at 3.16.57 PM.png


Task 1: Performing a discovery on a network

Perform a discovery on the network

Hint: the Grid member provides DHCP service to this network. It is the most ideal member to perform the network discovery.

Task 2: Checking discovery progress

Use the dashboard to monitor the discovery progress.

Task 3: Investigating potential conflicts

After a successful discovery, investigate a potential conflict on the IP address


Task 1 Solution: Performing a discovery on a network

  1. In the GM web interface, navigate to Data Management → IPAM.

  2. Go to the network, and select the IP Map view. You should see something similar to the screenshot below.

  3. In the Toolbar, click Discovery → Discover Now.

  4. The Discovery Manager dialog appears.

  5. In Member Name, change member by clicking on Select Member and choose

  6. Click on the IPv4 Device Discovery tab and confirm the mode is FULL, and the network is listed.

  7. Click Save. Then click the Start button, this will perform a one-time discovery on the network.

  8. You may click Close and the discovery will continue to run in the background.

Task 2 Solution: Checking discovery progress

  1. To check on the status of the discovery, navigate to Dashboards → Status.

  2. Find the Discovery Status widget. It displays the current discovery progress.

  3. Wait for the discovery to be completed. This could take a few minutes.

Task 3 Solution: Investigating potential conflicts

  1. Navigate to Data Management → IPAM, to the network → IP Map.

  2. The IP Map is now updated with the results from the network discovery. You should see some yellow entries (unmanaged hosts), and one red entry (conflict).

  3. Click on the red entry (conflict), the IP address Additional information is displayed both when you hover over the entry, and at the bottom of the screen.

  4. With the conflict entry highlighted, click Toolbar → Resolve Conflict.

  5. The description reads: “Discovered address is within an existing DHCP range but does not match an existing lease, fixed address, or exclusion range.”

  6. At this point you may choose one of the 3 resolutions:

    1. Create a fixed address: If you chose this option, the IP address will always be assigned to the MAC address b0:3a:3f:f2:13:7f.

    2. Create a reservation: If you chose this option, the IP address will be reserved and never assigned to anyone.

    3. Ignore this conflict: You may need to investigate further before deciding what to do. If that is the case, choose this option.

The most likely option given the circumstances, would be Create a reservation. This will prevent a potential IP address conflict when the DHCP server hands out to another device, while you investigate the root cause of why this MAC address b0:3a:3f:f2:13:7f is on this address. There are 2 possibilities: 1) it is configured statically/manually, or 2) it received this IP address from a different DHCP server. In the first case, you should still use Create a reservation, in addition to creating the appropriate DNS or Host information; in the second case, you need to locate the rogue DHCP server, so that all devices on this network receive DHCP leases only from the NIOS member.

JavaScript errors detected

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

If this problem persists, please contact our support.