Private & Confidential

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

For large scale nDisplay setups involving clusters, each node needs some pre-requisits setup before nDisplay can function.

These include:

  • Setting up the nDisplay listener to run on Startup

  • Mapping a network drive for the content

  • Setting the IP address and recording it

  • Ensuring that firewall permissions are granted

  • Syncronising the displays

  • Testing with test content.

nDisplay Switchboard Listener

This is the easiest part of the install as we’ve automated the process.

  1. Download this zip: nDisplay Cluster Installation Files

  2. Extract it to the desktop of the PC.

  3. Run the InstallClusterFiles.bat batch file (and allow administrator privilages)

  4. Run C:/Program Files/Switchboard/switchboard_Listener.exe

The last step is optional, because once a restart is completed the listener will run automatically every time.

However, it’s helpful to do after due to it asking for firewall access on it’s first run.

Part of the setup would’ve seen the installation of the UE4/5 Prerequisits which are also a requirement for any Unreal game to function. Due to a dll being required for the switchboard listener, they have been installed as part of this setup process.

Mapping a network drive for the content

Setting the IP Address

Our preffered method for setting IP addresses is via reserved IP’s. In our case this is done on the Netgate Gateway. We prefer this method over using Static IP’s as it creates less long term headaches when components within the system need to be swapped out.

We like to keep each node of the cluster alligned with it’s number in the cluster. So in our case:

  • Our cluster leader, is known as Node_0. So it has an ip address of 192.168.1.50

  • Our first cluster work node, is known as Node_1. So has the IP address of 192.168.1.51

The process of reserving an IP Address will be different depending on where it’s done within your specific network archetecture. So it won’t be documented here. However, if someone else is going to reserve the IP addresses for you; the information they will ask for is:

  • The IP you’d like to give each machine

  • The mac address of each machine.

It’s also useful to create a small table within your documentation with this information.

Firewall permissions

Make sure all ethernet ports are set to Private via the network settings page.

Also make sure that any applications that have been installed have their private firewall permission given.

Synchronising Displays

Testing

  • No labels