VSM - Network Port Specification

General Network Port Usage across the VSM system

Communication across network connections is a key functionality of vsmStudio and all of its components. Communication ports used for this communication can be manifold, depending on the type of controlled devices or the individual configuration of a connection.

In addition, we understand that open communication ports in systems can pose a security risk. It is therefore applicable to actively close or block ports, e.g. on a vsmServer. Before closing ports, it is mandatory to check if a port is not used for a specifics data connection. The following tables will help you to identify possibilities.

VSM Systems are shipped without active system firewall and without any ports deactivated. If you want to run a firewall on a vsmServer, please check the Operational Server Specifications for detail.

Handling of Default System Ports

Communication Ports used for Broadcast Control

When you are about to create a connection to a device for control purposes, you mostly use a TCP/IP connection, and you have to set IP address and port. Unfortunately, there are hundreds of ports which are used for various connections, so it is hard to remember them all. Here is a list of default port settings per connection type, to help you setting up your system.

• Almost all ports used for broadcast control - independent whether Lawo or 3rd party devices - range in the area >1000.
• Information about ports which are used by third party APIs can be found in the vsmGadgetServer Driver Specifications.

When you create a connection to a device, either through vsmStudio directly or via vsmGadgetServer, please refer to the specification of the device you want to control, to find out which control port(s) it uses for external control. It is often the case, that such ports can be configured, so make sure, you set them to an unused, non-blocked port number / or negotiate with your IT, to unblock the port.

Default port setting may have been customized in the system you work with, and therefore may not apply.

The table below lists Lawo specific, Ember+ specific or other 3rd party related control ports, which are often utilized.