SEDIC (System networking)
Functional description
The HOOC system networking – or secure device interconnect (SEDIC) – is a permanent layer 3 networking service for the operation of central applications. It enables the communication from a central point (or virtually) to controllers and systems at decentralized locations. This means that once the service is administered, all systems (e.g. SCADA) are permanently and simultaneously available for queries from the central site.
Configuration
Since SEDIC is a user-level service, for its configuration you won’t navigate to Site as you would normally do, but instead stay at the user level (Reseller or Customer) by going directly to Services -> SEDIC.
Service client
In order to be able to use SEDIC, you first have to set up the service once. For this purpose, you will need a service network.
Instructions for the setup of the SEDIC service:
- The IP address (Service Client) must not be in the subnet 10.42.0.0/16.
- No system device should be located in the same network segment (IP address / netmask) as the Service Client.
Please note that based on the selected netmask, a certain number of device mappings can be recorded. Set the Service password. Once systems and devices have been set up, you can use your HOOC ClientApp in order to use the service. For login in use Service user as user name and Service password as password.
Important: After having created mappings to your sites, the service network settings can no longer be changed.
Used sites
In order to add your sites and plants, you need a service IP address for each of them.
The following must be observed:
- The address range must not be in the same network segment as the one of the Service Client.
- The service IP address must not be in the 10.42.0.0/16 subnet.
- However, the service IP address must be in the same address range as the system devices.
- Please ensure that the IP address is free and will also will not be used in the future.
By clicking on the icon, you can add a site to the service.
The following must be observed:
| Property | Description |
|---|---|
| IP address | Enter a free and unused IP address from the subnet of the system devices |
| IP subnet | Enter a subnet mask |
Actions
| Actions | Description |
|---|---|
| Edit settings | |
| Remove the site from the service (if there are no system devices) | |
| Switch to site |
Devices and mappings
After a site has been added to the service, you can now add its devices or mappings (layer 3). A mapping means that when a request is sent from the Service Client to a service IP address, it will from there directly be forwarded to the IP address of the device.
| Property | Description |
|---|---|
| Service IP address | Enter a free IP address in the IP subnet (the Service Client will then communicate with this IP) |
| Site selection | Define the site to which a mapping is to be created |
| Device name | Enter the name or a short description of the device |
| IP address of device | Enter the address of the device to which the virtual service IP address is to be linked |
Actions
| Action | Description |
|---|---|
| Execute ping on device | |
| Remove device mapping |
How to use SEDIC in the HOOC ClientApp
The Service Client is integrated in the HOOC ClientApp; as soon as you log in, the connection to the networking service will be established. The communication to the system devices will then be established via query to the service IP addresses.