2811 - Replacing offline BloxOne Hosts

Scenario

A user's BloxOne lab environment containing hosts connected to the Cloud Service Portal (CSP) has expired. However, the CSP account is still active, resulting in those hosts being offline in the CSP UI.

To continue learning with a new BloxOne lab, you're tasked with replacing two offline Docker BloxOne hosts from the previous lab. You have remote access to the replacement virtual machines, which are pre-installed with Docker, allowing you to install the BloxOne Host image and connect it to the CSP.

Estimate Completion Time

• 60 to 70 Minutes

Prerequisites

• Administrative access to the CSP

• Prior Completion of Lab 2801

Course References

• 2161: Managing BloxOne Hosts and Services

Tasks

1. Rename the offline BloxOne hosts.

2. Create a new join token.

3. Deploy Docker Instance on oph1.

4. Deploy Docker Instance on oph2.

5. Validate BloxOne Hosts are connected to the CSP.

6. Swap offline BloxOne instances with new hosts on CSP.

Task 1: Rename the offline BloxOne hosts

• Using your lab’s Jump-Desktop, log into the CSP. Rename the current Offline BloxOne hosts, and add a prefix of offline to their names for later identification.

Task 2: Create a new join token

• From CSP, create a join token and save the join token as a text file using the text editor Geany for later use.

Task 3: Deploy Docker Instance on oph1

• SSH into oph1 virtual machine using the IP address 10.100.0.110 on port 65522, and the credentials of [training/infoblox].

  • Once logged in, run the script named deploy-BloxOne-oph with admin-level access and provide the join token when prompted.

Task 4: Deploy Docker Instance on oph2

• SSH into oph2 virtual machine using the IP address 10.200.0.110 on port 65522, and the credentials of [training/infoblox].
  o Once logged in run the script named "deploy-BloxOne-oph" with admin-level access and provide the join token when prompted.

Task 5: Validate the new BloxOne Instances are connected to the CSP

• Verify both Instances are visible on CSP, and that both are online.

  • Locate the Online Host with the IP address 10.100.0.110 and change its name to oph1.techblue.net.

  • Similarly, locate the second Online host with the address 10.200.0.110 and change its name to oph2.techblue.net.

It may take up to 30 mins for the two instances to be online.

Task 6: Swap offline BloxOne instances with new hosts on CSP

• Locate the offline host with the IP address 10.100.0.110 (offlineoph1.techblue.net) and replace it with the online instance, oph1.techblue.net.

• Similarly, locate the second offline host with the address 10.200.0.110 (offlineoph2.techblue.net) and replace it with the online instance, oph2.techblue.net.

Solutions

Task 1 Solution: Rename the offline BloxOne hosts

1. On the Jump-Desktop, use a browser to access CSP UI. Once logged into the CSP, navigate to Manage → Infrastructure → Hosts.

2. Locate the Offline Host with the IP address 10.100.0.110 by expanding the Hosts entry in the list (the toggle is on the right-hand side). It should currently display the status as ‘Error’ or ‘Offline’.

3. Place a check in the box next to the Host and click the Edit button.

4. Change the name to offlineoph1.techblue.net, then click Finish and Save & Close.

5. Repeat the same steps for the offline Host with the IP address 10.200.0.110, rename it to offlineoph2.techblue.net, and then click Finish and Save & Close.

Task 2 Solution: Create a join token.

1. On the Jump-Desktop, click on the start menu and run the application Geany, which we will use to save our join tokens for use in a later step.

2. Switch to your CSP browser window, navigate to Manage → Infrastructure, select the Join Tokens tab, and click on Create.

3. Enter a name for this join token, give the token a description, and click Save & Close.

4. The join token will be displayed on a pop-up window. Click Copy to copy the join token to the clipboard and paste it into Geany.

5. Save this document to the Desktop as join-token.txt.

Make sure you have saved the text of the join token, as the token will not be visible again. If we don't save it, we will need to revoke the token and create a new one.

Task 3 Solution: Deploy Docker Instance on oph1

1. On the Jump-Desktop, open the terminal application on your application taskbar.

2. Start a secure shell connection to the oph1 virtual machine on IP address 10.100.0.110 on port 65522 using the command ssh -p 65522 training@10.100.0.110 and when prompted, enter the password infoblox.

3. Deploy the host using the command sudo deploy-bloxone-oph and enter the join token when prompted. Finally, answer y after verifying the token is correct.

Task 4 Solution: Deploy Docker Instance on oph2

1. On the Jump-Desktop, open the terminal application on your application taskbar, if it is not already open.

2. Start a secure shell connection to the oph2 virtual machine on IP address 10.200.0.110 on port 65522 using the command ssh -p 65522 training@10.200.0.110 and when prompted, enter the password infoblox.

3. Deploy the host using the command sudo deploy-bloxone-oph and enter the join token when prompted. Finally, answer y after verifying the token is correct.

Task 5 Solution: Validate the new BloxOne Hosts are connected to the CSP

It may take up to 30 mins for the two BloxOne Host containers to be online.

1. Switch to your CSP browser window, and navigate to Manage → Infrastructure → Hosts

2. Your new BloxOne Host containers should appear in the list of hosts. If they are not visible, wait 10 seconds and refresh the browser.

3. Your BloxOne Host container status may at first indicate Offline or Degraded. This is normal as it comes up. You should also see the Platform Management in an Upgrading state. All BloxOne Hosts are automatically upgraded to the latest version to work with the CSP. Refreshing the page periodically may show a change.
   

   

4. Then your BloxOne Host container will change from Pending, to Review Details, to Online. Once both of your Host's statuses are Online, they are ready for configuration. Refreshing the page may show a change.
   

   

5. Locate the Online Host with the Host IP address 10.100.0.110 by expanding the Hosts entry in the list (the toggle is on the right-hand side).
   

   

6. Place a check in the box next to the Host and click on the Edit button.

7. Change the name to oph1.techblue.net, and then click Finish and Save & Close.

8. Locate the Online Host with the Host IP address 10.200.0.110 by expanding the Hosts entry in the list (the toggle is on the right-hand side).

9. Place a check in the box next to the Host and click on the Edit button.

10. Change the name to oph2.techblue.net, and then click Finish and Save & Close.

Task 6 Solution: Swap offline BloxOne instances with new hosts on CSP

1. From the CSP browser window, navigate to Manage → Infrastructure → Hosts.

2. Click on the ‘ellipsis’ icon for the offline host offlineoph1.techblue.net. Use the Replace option. From the 'Replacement Host' list, select oph1.techblue.net. Then, click on Save & Close.

3. A confirmation message is displayed. Click Confirm to replace the existing host with the new host.

4. Repeat the same steps for offlineoph2.techblue.net by clicking on the ellipsis icon for the offline host offlineoph2.techblue.net. Select the Replace option. From the 'Replacement Host' list, select oph2.techblue.net. Then click Save & Close.

5. A confirmation message is displayed. Click Confirm to replace the existing host with the new host.

6. After 2-3 minutes, the offline Hosts will now appear in Pending status. Click on the ellipses icon for the offline host offlineoph1.techblue.net. Select the Remove option. For the first confirmation message, click Remove. For the 2nd confirmation message, check the box beside ‘I understand the risk’ and click Remove. This would remove the offline Host from the CSP.

7. Repeat the last step for the offline host offlineoph2.techblue.net as well.

8. The statuses of your new BloxOne Host containers may now indicate 'Offline' or 'Degraded' for both hosts. This is normal, as the configurations are being transferred. Periodically refreshing the page may show changes.

It may take up to 30 mins for the two new BloxOne Host containers to be online after the last step.