Network requirements

This document presents a list of network ports on which communication of particular functionalities of VERTEX controllers takes place. In order for all functionalities to work correctly, you must ensure proper network rules for controllers.

Internal network (LAN)

Operator stations and all VERTEX controllers in the local area network must be set up according to the following rules.

Vertex - basic functionalities

Vertex commissioning - configuring with Firestarter

Services only for maintenance work

Description of services required for the basic functionalities of VERTEX controllers

1. Main WebApplication

The user interface and access to system functionality:

• Displaying information from individual modules/luminaires, monitoring

• Triggering actions on devices in the system

• Communication with a user who is on the same network through the website page

Consequences resulting from lack of access to the service:

• Lack of possibility to monitor the system

• No possibility to trigger any actions in the system

2. LogicEditor WebApplication

Logic editing interface of the lighting system:

• Graphical logic editor of lighting system operation

• Using it to create a logic of the lighting system

• Communication with a user who is on the same network through the website page

Consequences resulting from lack of access to the service:

• Lack of possibility to adapt the logic of the lighting system operation

3. VERTEX2VERTEX InternalMessageBUS

Service launched on VERTEX control units that are in the same local network, responsible for:

• exchange of messages between VERTEX control units

• synchronization of data between VERTEX control units

Consequences resulting from lack of access to the service:

• Total lack of control on lighting devices

Description of commissioning and initial configuration services for VERTEX devices

1. VERTEX-DISCOVERY NeighbourhoodDISCO

The service is used to communicate with the FIRESTARTER application. The application is used for the initial configuration of VERTEX control units. The configuration is made once during the system setup or in emergency situations that require service.Enables changing:

• The group in which Vertex works (1-8 or ungrouped)

• The default gateway for each selected group

• Subnets for each of the selected groups

• DNS for each selected group

• IP address for each device

Consequences resulting from lack of access to the service:

• It is impossible to correctly start the VERTEX controller (change network parameters, remember addresses of modules/luminaires)

Description of services required to carry out maintenance work for VERTEX devices

1. SSH-port

Service that allows direct service access to the VERTEX controllers. Login and access only by an authorized Glamox employee

Consequences resulting from lack of access to the service:

• There is no possibility to carry out service work

2. ServicePort

The service is used for local failure diagnostics. Login and access only by an authorized Glamox employee.

The consequences resulting from lack of access to the service:

• There is no possibility to carry out service work

Outbound to GLAMOX infrastructure

For proper operation of SLS services, it is required to allow outgoing traffic in accordance with the following rules.

Default policy

deny (incoming), allow (outgoing), deny (routed)

Opened ports