Skip to main content
Skip table of contents

Deploying NIOS-X Servers (2801)


Scenario

You are a DDI administrator preparing two NIOS-X servers in a lab environment for centralized management in the Infoblox Portal. You have remote access to the virtual machines from jump-desktop, Docker is already installed, and your goal is to install the NIOS-X image and connect it to the Infoblox Portal. Rename the servers as oph1.techblue.net and oph2.techblue.net after deployment.

Estimated Completion Time

  • 45 to 60 Minutes

Prerequisites

  • Administrative access to the Infoblox Portal

Tasks

  1. Create a join token.

  2. Deploy the first NIOS-X server.

  3. Deploy the second NIOS-X server.

Task 1: Creating a Join Token

From the jump-desktop, use the Education Infoblox Portal credentials to log in to the Infoblox Portal. Create a new Join Token in the Infoblox Portal and save the token string so you can use it during both server deployments. This gives each NIOS-X server the credential it needs to register with the Portal.

Task 2: Deploying the first NIOS-X Server

From jump-desktop, SSH into the NIOS-X virtual machines oph1 (10.100.0.110). Download and run the NIOS-X installer with the join token, wait for the server to register, and then rename the deployed server to oph1.techblue.net in the Infoblox Portal.

Task 3: Deploying the second NIOS-X Server

Repeat the deployment workflow for oph2 (10.200.0.110) and rename the deployed server to oph2.techblue.net in the Infoblox Portal so both lab servers are centrally managed and clearly identified.


Solutions

rocket-no.png

Do not use Launch Lab for this lab.

Launch Lab is only used for NIOS-based lab environments.

Task 1 Solution: Creating a Join Token

Before you deploy either server, create a Join Token and save it immediately. The token string is only shown once, so capturing it now prevents you from having to revoke and recreate it later.

  1. Log in to your lab’s jump-desktop.

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

  3. Navigate to System → Administration → Join Tokens.

    image-20260511-105803.png
  1. Click Create.

    1. In the token name field, enter JT-1.

    2. Click Save & Close.

  2. Copy the token string from the pop-up window.

Save the Join Token string, as it will not be visible again. If you don't, you must revoke the token and create a new one.

  1. Open the text editor Geany on jump-desktop, then save the token string to a text file for later use.

    image-20260513-093336.png

Task 2 Solution: Deploying the first NIOS-X Server

The NIOS-X server will change the status between Online, Degraded, and Offline several times while it updates and synchronizes with the Infoblox Cloud. The update process should take around 10-15 minutes.

  1. From jump-desktop, connect to oph1 at 10.100.0.110 on port 65522 by running ssh -p 65522 training@10.100.0.110.

  2. When prompted, enter infoblox as the password.

  3. Download the NIOS-X installation script to the oph1 virtual machine using this command.

    CODE
    wget https://s3.amazonaws.com/ib-noa-prod.csp.infoblox.com/bloxone_installer_v2.0.0.sh
  4. Make the installer executable by running chmod +x bloxone_installer_v2.0.0.sh.

  5. Run sudo ./bloxone_installer_v2.0.0.sh -j paste-your-join-token-here. Make sure you replace ‘paste-your-join-token-here' with the join token you have saved in Task 1.

    CODE
    sudo ./bloxone_installer_v2.0.0.sh -j paste-your-join-token-here
  6. If prompted, enter infoblox.

    2025-06-19_16-04-21-20250619-103442.png
  7. Wait about 10 to 15 minutes while the server updates and synchronizes with the Infoblox Cloud.

  8. In the Infoblox Portal, navigate to Network → Services & Servers → Servers.

  9. Select the deployed NIOS-X server and click Edit.

    image-20260513-102812.png
    1. On the General Info tab, change the server name to oph1.techblue.net.

      image-20260513-102938.png
    2. Click Finish and then Save & Close.

Task 3 Solution: Deploying the second NIOS-X Server

After validating the workflow on oph1, repeat the process on oph2 so the second server is also registered and named consistently in the Infoblox Portal.

  1. From jump-desktop, connect to oph2 at 10.200.0.110 on port 65522 by running ssh -p 65522 training@10.200.0.110.

  2. When prompted, enter infoblox as the password.

  3. Download bloxone_installer_v2.0.0.sh to oph2 by using the lab’s provided wget command from the Infoblox S3 location

    CODE
    wget https://s3.amazonaws.com/ib-noa-prod.csp.infoblox.com/bloxone_installer_v2.0.0.sh
  4. Make the installer executable by running chmod +x bloxone_installer_v2.0.0.sh.

  5. Run sudo ./bloxone_installer_v2.0.0.sh -j paste-your-join-token-here. Make sure you replace ‘paste-your-join-token-here' with the join token you have saved in Task 1.

    CODE
    sudo ./bloxone_installer_v2.0.0.sh -j paste-your-join-token-here
  6. If prompted, enter infoblox.

    2025-06-19_15-57-41-20250619-102802.png
  7. Return to Network → Services & Servers → Servers in the Infoblox Portal.

  8. Select the newly deployed server and click Edit.

    image-20260513-103128.png
  9. On the General Info tab, change the server name to oph2.techblue.net.

    image-20260513-103325.png
  10. Click Finish and then Save & Close.

JavaScript errors detected

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

If this problem persists, please contact our support.