Просмотреть исходный

1 Preparing hosts for the update

ECSS-10 version 3.17 supports two licensing types: file-based licensing (with or without a token) and ELM licensing. Depending on the licensing type, different commands will be executed during the update.

You can check which type is used on your SSW with the following command:

/cluster/storage/ds1/licence/list-licence

The output for file-based license is as follows:

/cluster/storage/ds1/licence/list-licence
┌──┬───────────────────┬────────────┬──────┬───────────────────┬────────────────────┬────────────┐
│Id│Creation date(UTC) │   SSW ID   │Active│    Description    │Expiration date(UTC)│ Time left  │
├──┼───────────────────┼────────────┼──────┼───────────────────┼────────────────────┼────────────┤
│1 │31.10.2025 14:16:00│ECSS 010070 │*     │Eltex SC softswitc │31.12.2026 23:59:59 │112d 21h 31m│
│0 │                   │ECSS DEFAULT│      │Default licence    │                    │            │
└──┴───────────────────┴────────────┴──────┴───────────────────┴────────────────────┴────────────┘

The output for ELM license is as follows:

/cluster/storage/ds1/licence/list-licence                  
┌──┬───────────────────┬────────────┬──────┬────────────────┬────────────────────┬────────────┐
│Id│Creation date(UTC) │   SSW ID   │Active│  Description   │Expiration date(UTC)│ Time left  │
├──┼───────────────────┼────────────┼──────┼────────────────┼────────────────────┼────────────┤
│1 │02.12.2025 13:51:39│ECSS2000000 │*     │ECSS ELM License│02.12.2026 13:51:39 │364d 11h 47m│
│0 │01.01.1990 00:00:00│ECSS DEFAULT│      │Default licence │                    │            │
└──┴───────────────────┴────────────┴──────┴────────────────┴────────────────────┴────────────┘

Preparing gluster volume for an update.
If one of the cluster nodes becomes unavailable, issues with the files may arise. Once the node is back online, the files will be out of sync, requiring you to manually initiate synchronization between the nodes.
To resolve this issue, use the cluster.favorite-child-policy parameter.
When enabled, all files that are split will be automatically synchronized with each other according to the specified rule.
To enable this parameter, use the following command:

sudo gluster volume set ecss_volume cluster.favorite-child-policy size

sudo gluster volume set ecss_volume cluster.favorite-child-policy size
volume set: success

 sudo gluster volume info
 
Volume Name: ecss_volume
Type: Replicate
Volume ID: 4bc875b1-f966-44e2-9b3f-04f3a7af83f3
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 10.0.10.51:/var/lib/ecss/glusterfs
Brick2: 10.0.10.52:/var/lib/ecss/glusterfs
Options Reconfigured:
cluster.favorite-child-policy: size
performance.client-io-threads: off
nfs.disable: on
transport.address-family: inet
storage.fips-mode-rchecksum: on
cluster.granular-entry-heal: on

When updating the cluster, update the servers one at a time. This ensures that one of the servers will always be running during the update, and service operation will not be interrupted. To split the cluster, use the ecss-control tool on both servers.
SIP signaling is exchanged via the SIP-VRRP IP address. This functionality is implemented to enable IP address migration to another host in the event of a failure, shutdown, or maintenance of the primary host. IP address migration is managed by the keepalived service on each host.
To redirect traffic to the first server (ecss1), you must stop keepalived on the second host (ecss2). In this case, both SIP-VRRP IP addresses will be on the first host (ecss1). Run the following command:
sudo systemctl disable --now keepalived.service
Use the ifconfig command to check that all VRRP IP addresses are located on ecss1 (VRRP-SIP1/VRRP-SIP2):
ifconfig

All nodes on the server that is being updated first should be masked and have their autorun disabled:

sudo systemctl mask --now ecss-ds ecss-mycelium ecss-mediator ecss-core ecss-pa-sip ecss-sorm

After the specified command is executed, the notification will appear.

Warning: The unit file, source configuration file or drop-ins of ecss-ds.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of ecss-mycelium.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of ecss-mediator.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of ecss-core.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of ecss-pa-sip.service changed on disk. Run 'systemctl daemon-reload' to reload units.

These messages are not an error. Continue the procedure.

On ecss1, split SSW into two independent servers using the following command:

The ecss-control command uses standard hostnames: ecss1/ecss2.

sudo ecss-control detach

Check the status:

sudo ecss-control status

sudo ecss-control detach
detach host: ecss2, ip: 10.0.10.52
complete
sudo ecss-control status
locked ip: 10.0.10.52

2 Preparing for updating SSW services

Update the SSW repository:

sudo sh -c "echo deb [arch=amd64]  http://archive.eltex.org/ssw/jammy/3.18 stable main extras external > /etc/apt/sources.list.d/eltex-ecss10-stable.list"

Update the packets:
sudo apt update

3 Updating SSW services on ecss2

Make a full backup.

Update PostgreSQL:

Check the addresses where the Postgres database is running, run the following command:

psql -Upostgres -decss_storekeeper_db -h localhost -p5439 -c "SELECT node_local_dsn FROM bdr.bdr_nodes;"

Default password is "postgres1"

psql -Upostgres -decss_storekeeper_db -h localhost -p5439 -c "SELECT node_local_dsn FROM bdr.bdr_nodes;"
Password for user postgres: 
                                    node_local_dsn                                     
---------------------------------------------------------------------------------------
 host=10.0.10.51 port=5439 dbname=ecss_storekeeper_db user=postgres password=postgres1
 host=10.0.10.52 port=5439 dbname=ecss_storekeeper_db user=postgres password=postgres1
(2 rows)

Disable the Docker container:

sudo docker compose -f /srv/ecss/ecss-postgres-bdr-ssw/docker-compose.container.yml down

 sudo docker compose -f /srv/ecss/ecss-postgres-bdr-ssw/docker-compose.container.yml down
[+] down 2/2
 ✔ Container ecss-postgres-bdr-ssw-postgres-container-1 Removed                                                                                                                           
 ✔ Network ecss-postgres-bdr-ssw_default                Removed

Remove the old deb packet, since it doesn't support the upgrade option:

sudo apt remove ecss-postgres-bdr-ssw

Execut the remove command, not purge, because 'remove' saves the 'volumes' directory containing the database tables.

sudo apt remove ecss-postgres-bdr-ssw
Reading package lists… Ready
. . .
The following packages will be DELETED:
  ecss-postgres-bdr-ssw
. . .
Would you like to continue? [Y/N] y
Removing ecss-postgres-bdr-ssw (17.1.0.59+ssw) …

Install the new deb package:

sudo apt install ecss-postgres-bdr-ssw

During installation, you will be asked the same questions as during the initial installation:
Your answers must match the instructions in the procedure exactly; otherwise, the system will attempt to create a new database, and the installation will fail.

Question

Answer

Example

Current IP address of the network interface.

Select an IP address: the same one used during the initial installation,
since replication is tied to specific IP addresses.

(checked in step "a", 10.0.10.52 in the example).

10.0.10.52 (must be specified)

Installation in a cluster?
Select <Yes> if the package is being installed on a cluster node.

Yes (default value)

Is this node master?

Answer NO! Otherwise it'll try to create new bdr,
which will be impossible and will lead to installation error).

No (default value)

IP address used to connect to the cluster:

IP of the neighbor node (specified during its installation, checked in step "a", 10.0.10.51 in the example).

10.0.10.51 (must be specified)

sudo apt install ecss-postgres-bdr-ssw
. . .
=============================
 Checking replication status 
=============================
BDR replication is configured correctly: the data matches.
. . .
=======================================================
=======================================================
 ecss-postgres-bdr-ssw successfully installed/updated! 
=======================================================
=======================================================


┏┓┏┓┏┓┏┳┓┏┓┳┓┏┓┏┓  ┳┓┳┓┳┓  ┏┓┏┓┓ ┏
┃┃┃┃┗┓ ┃ ┃┓┣┫┣ ┗┓  ┣┫┃┃┣┫  ┗┓┗┓┃┃┃
┣┛┗┛┗┛ ┻ ┗┛┛┗┗┛┗┛  ┻┛┻┛┛┗  ┗┛┗┛┗┻┛

After the installation make sure, that the new image is loaded and the docker started. Run the following command:

docker ps

docker ps
CONTAINER ID   IMAGE                                           COMMAND                  CREATED         STATUS         PORTS                                         NAMES
80ef72d3b125   git.eltex.loc:4567/ecss/ecss-postgresbdr:3.18   "/docker-entrypoint.…"   8 minutes ago   Up 8 minutes   0.0.0.0:5439->5432/tcp, [::]:5439->5432/tcp   ecss-postgres-bdr-ssw-postgres-container-1

Updating SSW.

Updating the ecss-dns-env package:
sudo apt install ecss-dns-env
Updating the ecss-user package:
sudo apt install ecss-user
Updating the ecss-utils package:
sudo apt install ecss-utils

Install the License Provider package:

sudo apt install ecss-license-provider

When installing the ecss-license-provider package the following questions will be asked:

Questions

Answers

Examples

License Provider listen ip:

0.0.0.0 (default value)

ECSS-10 EN 3.18 > Updating a server cluster from version 3.17.1 to 3.18 > 2026-05-25_10-04.png

License Provider listen port:

4321 (default value)

ECSS-10 EN 3.18 > Updating a server cluster from version 3.17.1 to 3.18 > 2026-05-25_10-05.png

Log level:

info (default value),
other options: debug, error, info

ECSS-10 EN 3.18 > Updating a server cluster from version 3.17.1 to 3.18 > 2026-05-25_10-05_1.png

License Provider cluster key:

specify a unique name
ecss-lm-cluster (default value)

Managers with the same names will attempt to form a cluster for mutual failover.

ECSS-10 EN 3.18 > Updating a server cluster from version 3.17.1 to 3.18 > 2026-05-25_10-06.png

The data is saved to the /etc/ecss/ecss-license-provider/config.env file:

ECSS_LM_HOST=0.0.0.0
ECSS_LM_PORT=4321
ECSS_LM_LOG_LEVEL=info
RELEASE_COOKIE=ecss-abf-lm-cluster

License Provider (LP) configuration

The ecss-license-provider service uses two configuration files: /etc/ecss/ecss-license-provider/config.env and /etc/ecss/ecss-license-provider/config.yaml.

The information is saved to the config.env file when the ecss-license-provider is installed.

The config.yaml file contains general settings for connecting to the ELM server and information about licenses: what licenses to take, where to take them from, and where to send them, all this information should be configured manually.

elm_addresses: []
licenses: []
ecss_nodes: []

To fill out these fields, open the ecss-elm-adapter configuration file used in the version 3.17 /etc/ecss/ecss-elm-adapter/config.env:

cat /etc/ecss/ecss-elm-adapter/config.env 
ELM_HOST=elm.eltex-co.ru
ELM_PORT=8099
ECSS_PRODUCT_ID=ECSS2000000
ECSS_LICENSE_KEY=ssw987654
LOG_LEVEL=info
LICENCE_FAIL_TIMER_SECONDS=10
LICENCE_PULL_TIMER_SECONDS=360

In the elm_addresses field, you must specify a list of ELM servers to which you want to connect to obtain licenses.
First address in the list is used as the main one. Additional lines contain backup addresses.
Example:

elm_addresses:
 - "elm.eltex-co.ru:8099"
 - "192.168.111.22:8099"
 - "elm-3.eltex.loc:8099"

Then licenses in the licenses field are specified.

The id can be anything, as long as it is unique for each license. It only affects the license address on the License Provider itself (e.g., 0, 1, 2, 3).
kind. For SSW, only SSW (in uppercase) is supported.
type is set to elm if this license is to be requested from the ELM server. If you need to use an SSW file-based license, set the type to ecss_license.
- For the elm type, you must specify the license_key and product_id fields to identify the license.
- For the ecss_license type, specify the license field, which contains the static license key.

license_key = ECSS_LICENSE_KEY and product_id = ECSS_PRODUCT_ID parameters must match the data previously uploaded to the ELM server.

ecss_nodes block.

You must specify the details of the services that will receive the license. A service is defined by three parameters:

id - the service identifier. In the case of SSW, this must match the ECSS_ID of the SSW being licensed.
kind - the type of service being licensed. As with the licenses block, the SSW and AUP types are supported. For SSW, only the SSW type is supported.
license_id - the identifier of the license that will be sent to this service. It corresponds to the license identifiers from the licenses block

Two SSWs with different ECSS_IDs cannot receive the same license; a configuration with such an assignment will be marked as invalid.
Additionally, two SSWs with identical ECSS_IDs cannot simultaneously obtain the same license from a single License Provider; therefore, it is extremely important to set your ECSS_ID correctly and ensure it is unique, at least within the scope of the License Provider being used.

ECSS_ID format.
It must begin and end with a Latin letter or a digit; periods and dashes may be used within the string.

[A-Za-z0-9][A-Za-z0-9.-][A-Za-z0-9]

For an SSW operating in a cluster, specify only one entry in the ecss_nodes block per cluster; you cannot specify entries individually for each host. Otherwise, two requests with the same ECSS_ID will be generated, which is not allowed.

elm_addresses:
 - "elm.eltex-co.ru:8099"
licenses:
 - id: 0
   kind: SSW
   type: elm
   license_key: "ssw987654"
   product_id: "ECSS2000000"
ecss_nodes:
 - id: eltex1.test
   kind: SSW
   license_id: 0

Restart the ecss-license-provider.service service to up date the configuration from the /etc/ecss/ecss-license-provider/config.yaml file via the following command:

sudo systemctl restart ecss-license-provider.service

No addditional actions required.

Update the ecss-node package:

sudo apt install ecss-node

ecss-node installation questions:

Question Answer Example

Cookie for the core node: (specify the unique cookie for the core, the example uses ecss-core-example)