Unicon documentation migration is in progress. You might find some broken links or experience minor issues in the documentation. We are working on resolving these issues.

X

System requirements

General requirements

  • System resources

    • 4 CPUs
    • 8 GB RAM
    • 24 GB hard disk space
  • Network

    • OneIP address in the VPN address range for each connected eLux device[1[[ ]from SCG 1 2209]]

    • Internal HTTPS access to the SCG WebAdmin interface (Interface for configuration and management)

    • Bi-directional connection (via network card or firewall rules) of eLux devices to the Scout Server and of the Scout Cloud Gateway to the Identity provider

  • Scalability by means of clustering

    If required, multiple machines can be installed. as SCG servers. 1024 devices can be connected per server.

You can set up your instance with the help of a Debian Installer under a Linux system. Alternatively, [Unicon] offers a ready configured virtual appliance. In both cases, the network must be configured before the SCG is started to enable routing from the DMZ to the internal network. The virtual machine assists with the setup.

  Debian package Virtual machine
Download Debian package (.deb) Virtual appliance (.ova)
    The virtual machine is installed using an .ova template (Open Virtual Appliance).
Required system Configured Debian Linux system Virtualization platform such as VMware
  We recommend Ubuntu 20.04.  
Specifics   Wizard supports system configuration
    Additional functions in the WebAdmin interface
   
  • Upload public keys for SSH access to the instance
   
  • Upload individual HTTPS certificates for the WebAdmin interface connection (to replace the automatically created self-signed certificate)

Availability from the Internet

  • Management protocol between eLux devices and Scout Server

For connecting the devices, the SCG server should be reachable from the Internet as FQDN. The default port for communication is 22125.

If you are running multiple SCG instances in a cluster, we recommend that you distribute the requests to the different instances via router.

  • VPN port for connecting devices

For cluster operation: Each SCG instance requires a unique combination of FQDN and port for its VPN server.

The administrator performs the configuration in the SCG [WebAdmin interface], see Gateways.

Internal availability

  • HTTPS Port 443 for connecting the WebAdmin interface (configuration, clustering, management)

  • If Active Directory or Keycloak is used, the servers must be reachable

  • Only virtual machines ([.ova]): port 22 for access via SSH to the instance for administrative access (optional)

  • For cluster operation: MongoDB port 27017 for internal communication of the databases across the SCG instances

Note:

Make sure that your Linux system is always up to date. To do so, use the standard commands apt-get update and apt-get upgrade.

For support periods and the compatibility matrix see the Whitepaper Releases, Lifecycles and Compatibility.

System requirements