Connecting Additional Axonius Nodes
  • 4 Minutes To Read
  • Print
  • Share
  • Dark
    Light

Connecting Additional Axonius Nodes

  • Print
  • Share
  • Dark
    Light

On partially connected networks, Axonius allows the creation of additional collector nodes and connecting them to the core node. This architecture enables fetching data from networks with limited connectivity or strict firewall rules.

Axonius Architecture (1).png

To connect a collector node, the following are required:

  • The Axonius collector node must be installed on the partially connected network, with the same Axonius release version as the Axonius core node.
  • The below ports must be open between the Axonius Collector Node to the Axonius Core Node:
    • TCP/6783
    • UDP/6783
    • UDP/6784
Source Destination Protocol Port
Collector Node Primary Node TCP 6783
Collector Node Primary Node UDP 6783
Collector Node Primary Node UDP 6784

Node Sizing Recommendations

Number of Assets sent through Node RAM CPU Cores Disk*
< 30k 16 GB 4 virtual cores 100 GB
> 30k 32 GB 8 virtual cores 100 GB
> 100k 64 GB 8 virtual cores 100 GB

* SSD is not required for storage

Connecting an Additional Node

  1. Deploy an Axonius node into the additional network and start the machine. There is no need to login to the Axonius GUI.
  2. Log into the Axonius core node, and go to the Instances page. The Instances page opens, displaying the installed Axonius instances, that includes tagged name, hostname, IP address, last seen and the status (activated/deactivated) of each instance.

image.png

  1. To connect an additional collector node, click Connect Node.
    You should see a message box that instructs you how to connect an additional node to the core node. This involves logging into the node machine with ssh credentials 'node_maker:M@ke1tRain' and then typing a connection string that looks like this:
    [Axonius-Hostname] [Secret Token] [User-Nickname]

    • Axonius-Hostname - Specify the IP/hostname of the core node, which is accessible from the additional node.
    • Secret Token - Copy and paste the secret token above, which was generated by the core node.
    • User-Nickname - Specify a name for the additional node, e.g. 'node-1'.



    An example of a connection string could be:
    10.0.7.43 oBB9aaOTC2Sh88i0pDv5IE5x0LeOXFHH node-1
    image.png

  2. Once you paste the connection string, wait a few minutes until the node connects. You should see a success message, and an additional collector node is added in the Instances page with an Activated status.

As a result, you can now configure any adapter to utilize the newly added Axonius collector node.

Deactivating and Reactivating Nodes

To deactivate an activated node:

  1. From the Instances page, select one or more activated Axonius collector nodes. The Deactivate action button is displayed.
  2. Click Deactivate. Once confirmed:
    • All the adapter connections utilizing the selected Axonius node(s) are removed.
    • The status of all selected Axonius collector node(s) is updated as Deactivated.

To reacticated a deactivated node:

  1. From the Instances page, select one or more deactivated Axonius collector nodes. The Reactivate action button is displayed.
  2. Click Reactivate. Once confirmed, the status of all selected Axonius collector node(s) is updated as Activated.

Renaming Instances and Hostnames

To allow you to manage your Instances better you can rename the Instances as well as the Hostnames
To rename an Instance:

  1. From the Instances page, click on an Instance.
  2. The instance drawer will appear when you can rename the Instance Name or Hostname.
    The Hostname field should not include spaces or special chars.
    image.png

Adding Instance Indication

To allow you to easily distinguish your different Axonius machines we added the "Instance Indication toggle to the Axoniuse core node instance.

  1. From the Instances page, click on an Instance.
  2. The instance drawer will appear where you can set an instance indication on the Axonius core node instance.
    • The Instance Indication (required, default: False) select whether to display a banner with the Instance Name field value on all system pages.
      image.png

Instance Performance Metrics

To view instance performance metrics:

  1. From the Instances page, click on an Instance.

  2. The instance drawer will appear where you can view instance performance metrics.

  3. The following performance metrics will be shown:

    • CPU Usage - CPU usage in percentages
    • Hard Drive: Free Size (GB) - The available disk space that is left on the Instance machine.
    • Hard Drive: Size (GB) - The total disk space that is configured on the Instance machine.
    • Free RAM (GB) - The available memory that is left on the Instance machine.
    • Total RAM (GB) - The total memory that is configured on the Instance machine.
    • Free Swap (GB) - The available Swap memory that is left on the Instance machine.
    • Total Swap (GB) - The total Swap memory that is configured on the Instance machine.
    • Total Physical Processors - Total number of physical processors on the instance machine.
    • CPUs: Cores - Number of CPU cores on the instance 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.

    image.png

Was This Article Helpful?