История страницы

...

• ECCM Application Server  — server on which an application is deployed that ensures the operation of the system and interaction with devices, as well as a web user interface;
• Database Server  — server with Postgres14 databases. It is possible to use one that already exists in the cluster infrastructure.;
• Device Management Network  — IP network for managing equipment, through which ECCM has access via L3.;
• Operator/Administrator  — system operator engaged in monitoring and configuration of the controlled equipment/system administrator of the company or ELTEX technical support specialist, if remote access has been agreed upon.

...

To run the project with the required logging level, add the --logging key to the launch line:

sudo ./compose-tools.sh --start <ECCM ADDRESS> --logging DEBUG

Since version 1.5, the project has a DHCP server with support for Zero Touch Provisioning (ZTP) functionality, which automatically adds devices to the system. The server is disabled by default. To activate, add the --dhcp key to the launch line.:

sudo ./compose-tools.sh --start <ECCM ADDRESS> --dhcp

To save all container images to archives .tar.gz run the command:

sudo ./compose-tools.sh --save

To convert archives with images (.tar.gz ) in docker images, run the command:

sudo ./compose-tools.sh --load

To convert a container with the new parameters, run the command (the container will be recreated according to the file.env of the corresponding compose project):

sudo ./compose-tools.sh --recreate-service monitoring-service

...

sudo docker network inspect $(docker network ls --filter "DRIVER=bridge" --format '{{ .Name }}')  -f '{{ .Name  }} {{ (index .IPAM.Config 0).Subnet }}'

Possible errors during the work of the project

Error: monitoring is not working correctly, device metrics are not collected.

Possible reason: the monitoring service does not have enough memory to work correctly. The monitoring-service logs contain entries like:

WARN  [b1a52920966f70af] [item-poll-executor  ] o.e.e.m.service.BackpressureController   : Batch size adjusted for job 'item polling': 100000 → 0 (adjustment factor: 0.000, memory usage: 97%)

Solution: increase the memory limit for the monitoring-service. To do this, increase the value of the ECCM_MONITORING_SERVICE_XMX variable in the eccm/.env file:

-ECCM_MONITORING_SERVICE_XMX=1G  <--- old value
+ECCM_MONITORING_SERVICE_XMX=2G  <--- new value

...

Contact the company's Service Center for advice on system operation. Refer to the last page of this manual for contact methods.

For faster and more convenient interaction with ECCM technical support specialists, please provide the following information when contacting:

1. The installed version of ECCM and the license used;
2. Whether there is access to the Internet from the server where the firmware is deployed (no access, direct access, via NAT, via Proxy, etc.);
3. The time the issue occurred (preferably as accurate as possible);
4. Screenshot or video file if the issue occurred in the browser GUI;
5. Device information (this could be device IP address, device model) if the problem was related to some device.

Defining the ECCM version and license

It is possible to determine the installed version of ECCM using one of the following methods:

1. When downloading a release archive, look for version information in its name, eccm-2.2.tar.gz.
2. If the original tar.gz archive has been deleted, the version information can be found in the configuration file $ECCM_ROOT/eccm/.env (in a line like: ECCM_TAG=2.2).
3. Check the version information in the lower left corner of the web interface screen of the running ECCM:

...

Якорь
Script Script

Information collection script

The script automates the collection of metrics from the ECCM system, and then packages them into a compressed archive for more convenient transportation. Designed to run on Linux/Ubuntu OS.

Running the script:

1. Enter the ~/eccm/<ECCM version> directory/:

cd ~/eccm/<ECCM version>/

2. Run the following command:

sudo ./technical_support.sh

...