Nodes are used by LiveNX to provide additional collection and processing capabilities in networks with a large number of devices. The Nodes run on Linux OS or Windows Server and communicate to the central LiveNX Server.
1. Download the LiveNX Node from: http://liveaction.com
2. Install the LiveNX Node software of a Windows or Linux Server.
3. For Windows, follow the installer directions.
4. For Linux, use the shell script LiveActionNode-<VERSION>.x86_64.sh on a Linux computer or VM.
a. chmod +x LiveActionNode-<version>.x86_64.sh
c. Enter the LiveNX Node and Server IP address
d. Enter the LiveNX data directory. For consistency, name the data directory to correspond with the Server data directory. Type y to create a new data directory. When complete, the LiveNX Node is installed.
5. Define the Nodes using the LiveNX Server and then start the LiveNX Node Console to load the Node configuration.
a. Return to the LiveAction Management Console and click on Add Node in the Nodes tab. Define a Node Name and type in the IP Address on the Linux computer or VM. If desired, create a password to protect the connection file or uncheck the Encrypt checkbox. Click on the Browse button to save the *.nodeconn file.
b. After clicking on Add Node, LiveNX will provide a success notification.
c. Verify the new Node’s name, IP address and status in the LiveAction Management Console.
d. Start the LiveNX Node Console on the Linux PC or VM by typing:/opt/LiveActionNode/4.2/LANodeManagementConsole
e. Once the LiveNX Node Console is running, import the LiveNX Node connection file by clicking on: Manage > Import Connection File
f. Click on Browse to select the saved *.nodeconn file. In this example, the *.nodeconn file was copied onto the desktop of the Linux machine containing the LiveNX Node.
g. Click on OK and then re-enter the password used to create the *.nodeconn file. Click on Import.
h. On the LiveNX Node Console, go to Manage > Start Service. When completed, a green LED appears in the bottom of the Node Console with “Node is currently running.”Verify that the Node Name and Node ID matches the Node Name and Node ID in the Node tab in the Management Console and that the Node status in the Management Console is connected.
NOTE: If the LiveNX Node daemon fails to start up and the log shows an error with setting the Node-name property in ‘akka.conf’ file, then it is likely that Cent OS failed to statically configure the loopback IP address in the /etc/hosts file. This issue is OS dependent. To resolve, type “hostname” to retrieve the hostname.
i. Edit /etc/hosts file and type in the hostname.
j. Restart the LiveNX Node Console by clicking on Manage > Start Service.