How to Enable and Configure Cloud Clustering?

How to Enable and Configure Cloud Clustering?

Cloud is a NodeGrid feature that establishes a secure and resilient connection among other NodeGrid platforms so that when Cloud Clustering is enabled, multiple NodeGrid systems can easily manage and access all managed devices from other nodes.

NodeGrid makes cloud access management even easier with cloud asset search. By logging into any NodeGrid node users can search the entire NodeGrid-managed enterprise network and cloud with a single interface.

This allows vertical and horizontal scalability.


Below are the steps to configure Clustering in the NodeGrid Cloud:

1. Log in to your first NodeGrid's WebUI as admin

2. Go to Cloud::Settings page

3. Check 'Enable Cloud' checkbox

4. Enter a Cloud Name

5. Select Type as Coordinator, and enter a Pre-Shared Key

6. Check 'Enable Clustering' checkbox

7. Save

8. Go to your second Nodegrid and log in as admin

9. Go to Cloud::Settings page, and enable Cloud

10. Enter the same Cloud name from the Coordinator NodeGrid

11. Select Type as Peer, and enter the IP address and the same Pre-Shared Key of the first NodeGrid

12. Check 'Enable Clustering' checkbox

13. Save

Repeat steps 8 through 13 for other NodeGrids that you want to be part of the Cloud Clustering

Go to Cloud::Peers page and wait until all units establish internal communication and get Status 'Online'

Go to Access page and all the nodes should be listed there.


Example of Configuration via CLI 

Note: replace the values of the parameters with your own

1. Access the first NodeGrid via ssh or local port (Console or HDMI) and log in as admin

2. Type the following commands:

[admin@nodegrid /]# cd /settings/cloud/ 

[admin@nodegrid cloud]# set enable_cloud=yes type=coordinator 

[+admin@nodegrid cloud]# set cloud_name=cloudname 

[+admin@nodegrid cloud]# set psk=presharedkey 

[+admin@nodegrid cloud]# set enable_clustering=yes

[+admin@nodegrid cloud]# commit

3. Access the second Nodegrid via ssh or local port, and log in as admin

4. Type the following commands:

[admin@nodegrid /]# cd /settings/cloud/ 

[admin@nodegrid cloud]# set enable_cloud=yes type=peer

[+admin@nodegrid cloud]# set cloud_name=cloudname

[+admin@nodegrid cloud]# set coordinator_address=

[+admin@nodegrid cloud]# set psk=presharedkey

[+admin@nodegrid cloud]# set enable_clustering=yes

[+admin@nodegrid cloud]# commit


Repeat the commands for other NodeGrids for the Clustering.

    • Related Articles

    • How to Configure the NodeGrid to Be More Secure?

      As far as the NodeGrid software's networking services, it comes with some security in mind, but it still is not as closed as some network policies require. This can be accomplished by changing the services settings in Security :: Services page per ...
    • Can I Cascade NodeGrid Serial Console Units?

      NodeGrid Serial Console (NSC) serial console server is able to share network ports with fellow devices, sharply reducing network switch port usage for OOB device management. This new port saving feature is already reliably and securely saving many ...
    • How to: Enable ZPE Cloud in a Nodegrid device

      ZPE Cloud is a powerful platform that allows you to manage your Nodegrid devices from anywhere in the world. In order to use the benefits of managing your Nodegrid devices through ZPE Cloud, you need to enroll the Nodegrid device to your company and ...
    • How to: Enable ZPE Cloud Remote Access...Remotely

      You just got your ZPE Nodegrid up and running and it is connected and enrolled in your ZPE Cloud. But you can't access it remotely because the remote access buttons are grayed out. It is online, but no access available. The way to get remote access ...
    • How to Connect and Configure a USB Serial device on the NodeGrid ?

      Overview: The Nodegrid OS supports the serial connections via USB as well. In particular, it supports the connections USB - USB Micro, very used on some vendor switches (e.g. Cisco), as alternatives to the RJ45 console ports. For the testing, we used ...