Warning! This is advanced network configuration. Changing the group assignment can result in the LumiNode becoming unreachable when not configured correctly.
Process engine indication
Practical examples
Art-Net data is broadcasted, so it is important that source and receiver are part of the same IP subnet. Console operators are not always in the ability to modify their IP configuration to match the IP subnet of a venue. This can easily be solved by adding another IP address to the LumiNode. If you use networked outputs, make sure to select the IP address you would like to use for outgoing network packets.
In this example, the 'house' network is using the default 2.x.x.x/8 IP range, but a guest comes in with a console that is for some reason configured for 192.168.1.x/24.
- Add another IP address to the virtual interface (1)
- Select the IP address you would like to use for outgoing network packets (2)
- Save the configuration.
Pass through a group to a second network port
It is possible to forward a group or trunk between the 2 physical network ports of a LumiNode. This can be useful in various situations where switch ports are limited or where you would like to avoid additional network cabling. This can be an intercom system, the camera feed for a RoboSpot system, the management group of your switches,...
- Select "Assign group"
- Assign a trunk (ISL) to the network port that will be used to connect to your switch. Make sure to use the same trunk configuration on your switch. Also make sure that the trunk contains the group used to configure the LumiNode so you can still access and use your LumiNode
- Assign the group you would like to forward to the other network port.
- Save your configuration
Split configuration and lighting data
It is possible to separate configuration of the LumiNode and the actual lighting data in separate groups.
- Assign a trunk to the physical network port(s) that contains both the management and data group
- Add a new virtual interface for the data group
- Disable 'input/output' on the management interface and enable 'input/output' on the data interface
- Give the data interface an IP address. Since this will not have 'allow config' enabled, the IP address can be in the same IP subnet as management, but it is recommended to use a different IP subnet for each group, just to keep things easier to manage.
- Save your configuration.
- Make sure to assign the trunk from step 1 to the switch port on which the LumiNode is connected.
Have a separate interface for IT monitoring
In some networks with a dedicated IT department, the IT department might require access to networked equipment for monitoring purposes using 'ping' and/or
SNMP. However, it is often not desired to give the IT department full configuration access or forward all lighting data to the IT department. This can be solved by adding a virtual interface to the LumiNode dedicated to monitoring.
- (Optionally) create a new custom trunk. Make sure to add the groups you will be using to this trunk. The 'untagged' group/vlan has to match the untagged VLAN on the switch port on which the LumiNode is connected.
- (Optionally) edit the group configuration to match the VLAN IDs provided by your IT department.
- Assign the custom trunk from step 1 (or the ISL) to the network port connected to the IT infrastructure. The switch port on which the LumiNode is connected has to use a matching group/VLAN configuration.
- Add a new virtual interface using the group that will be used for IT monitoring.
- Give this new interface an IP address provided by your IT department
- Save your configuration.