Working with Axonius Compute Nodes

You can create one or more compute nodes that connect to a primary node. There can be only one primary node. Compute nodes allow you to:

• Add load balancing to improve the overall performance of your Axonius deployment.

To connect a compute node, the following are required:

• The Axonius compute node must be installed on the partially connected network, with the same Axonius release version as the Axonius primary node.
• The following ports must be open from the Axonius compute node to the Axonius primary node for OpenVPN:
  • TCP/6783:

Node Sizing Recommendations

* SSD is not required for storage

Connecting a Compute Node to a Primary Node

1. Copy the connection string from the primary node

To connect a compute node to a primary node, you need to copy a connection string from the primary node and us it when configuring the compute node.

1. Log into the Axonius primary node, and go to the Manage Nodes page. The Manage Nodes page opens, displaying installed Axonius nodes, including the tagged name, hostname, IP address, last seen, installed version, and the status (activated/deactivated) of each node.
   

2. Click Connect Node. From the message box that opens, click Generate and Copy to generate and copy the connection string that contains the node name.

   Note:

   * From version 6.0.12 it is possible to use the same connection string to connect more than one node.
   * However, it is also possible to generate a separate different connection string for each node, if you require this.

2. Deploy the compute node and connect to the primary node with the connection string.

1. Make sure any prerequisites listed above are met.

2. Deploy an Axonius node into the additional network and start the machine.

3. Decrypt the system using the steps provided by Axonius.

4. Configure the IP address per the "Setting the IP address" section in Configuring the Axonius Platform

5. Install the license as described in Logging on and Signing Up. However, do not fill in signup details or configure an Admin user. Once the decryption and installation process is complete, the Axonius Machine opens:
   

6. From the Node Type select Compute Node.

7. Paste the connection string copied from the primary node into the Connection string pane.
   

8. Click Continue.

9. Some systems may have issues with the IP address of the primary node, in which case the following is displayed. Go back to the Manage Nodes page and copy the IP address of the Primary node into the Primary node field and click Retry.
   

The system begins to install, this might take a few minutes.

You should see a success message. An additional compute node is now added to the Manage Nodes page in the primary node with a status of Activated. The Axonius user interface is available only from a primary node. Once a node is connected to a primary node as a compute node, you will not be able to access the user interface on the compute node machine any more.

You can now configure any adapter to use the newly added Axonius compute node.

Managing Compute Nodes

You can deactivate, reactivate, delete rename, compute nodes.

Deactivating a Compute Node

You can deactivate a compute node from the system using the Manage Nodes drawer. When you deactivate a compute node, all adapter connections using this compute node are removed from the primary node.

To deactivate a compute node:

1. From the Manage Nodes page, click on an active node. The Manage Nodes drawer opens.

2. Click the Actions button and choose Deactivate. The system asks you to confirm your action.

   

   Once you confirm the action:

   • All the adapter connections that use the selected Axonius compute node are removed.
   • The status of the compute node is marked as Deactivated.

Reactivating a Compute Node

You can reactivate a node using the Manage Nodes drawer.
To reactivate a deactivated node:

1. From the Manage Nodes page, click on a node which is not currently active. The Manage Nodes drawer opens.
2. Click the Actions button and choose Reactivate. The system asks you to confirm your action. Once confirmed, the status of the selected Axonius Compute node(s) is updated as Activated.

Deleting a Compute Node

You can delete a Compute node from the Manage Nodes page.
You can only delete a compute node if it has not been used for two days. Once you delete a compute node it is completely removed from the system and will have to be installed again if you want to use it again.
To delete a compute node

1. First you have to Deactivate the compute node. It is now possible to delete the compute node.
2. From the Manage Nodes page, click on a node (not the primary node). The Manage Nodes drawer opens.
3. Click the Actions button and choose Delete. The system informs you that this completely deletes the node, and asks you to confirm the action. Once confirmed, the selected Axonius compute node is deleted from the systems.

Renaming Nodes and Hostnames

To allow you to manage your Nodes better you can rename the Nodes as well as the Hostnames
To rename a Node:

1. From the Manage Nodes page, click on a Node.
2. The Manage Nodes drawer is displayed. You can rename the Node Name or Hostname.
   The Hostname field should not include spaces or special characters.

Node Performance Metrics

To view node performance metrics:

1. From the Manage Nodes page, click on a Node.
2. The Manage Nodes drawer opens and displays node performance metrics.
3. The following performance metrics are displayed:
   • CPU Usage - CPU usage in percentages
   • Hard Drive: Free Size (GB) - The available disk space that is left on the Node machine.
   • Hard Drive: Size (GB) - The total disk space that is configured on the Node machine.
   • Free RAM (GB) - The available memory that is left on the Node machine.
   • Total RAM (GB) - The total memory that is configured on the Node machine.
   • Free Swap (GB) - The available Swap memory that is left on the Node machine.
   • Total Swap (GB) - The total Swap memory that is configured on the Node machine.
   • Total Physical Processors - Total number of physical processors on the Node machine.
   • CPUs: Cores - Number of CPU cores on the Node machine.
   • CPUs: Threads in core - Number of threads per core.
   • Last Historical Snapshot (GB) - The amount of storage taken up by the most recent historical snapshot.
   • Days Remaining for Historical Snapshots - The number of estimated days, historical snapshots will still be saved given available storage capacity. Note: This field will only be visible if 1) historical data retention is not configured OR 2) the number of days configured for historical data retention is higher than the estimated number of available snapshots.