Installations- und Upgrade-Verfahren
Tipp
Sie können diese Aufgabe ignorieren, wenn ThingPark Enterprise All-in-One bereits von Ihrem Systemintegrator auf Ihren Gateways installiert wurde.
Diese Seite beschreibt das manuelle Installationsverfahren.
Sie können jedoch das Zero-Touch-/automatisierte Installationsverfahren nutzen, das vom Infrastructure Commissioning Service (ICS) bereitgestellt wird. Wenden Sie sich hierfür bitte an Ihr ThingPark Support-Team.
Für ein Upgrade müssen Sie dieselben Schritte wie für das Installationsverfahren befolgen und am Ende des Verfahrens Ihre Gateways neu starten.
Installationsanforderungen
-
Die nachfolgend beschriebene Installation ist manuell. Sie benötigen SSH-Zugriff auf die Basisstation und das Root-Passwort.
-
Sie benötigen mindestens 400 MB freien Speicherplatz auf der Festplatte.
-
Sie benötigen das passende Installationspaket für Ihre Hardware:
scheme: TAO_<manufacturer>.<BS_PROFILE>_<version>
Neueste Releases
| Hersteller | TAO-Paket | Referenz | Anmerkungen |
|---|---|---|---|
| Browan | TAO_gemtek.GMTK_ODU.1_2.6.1 | Browan Outdoor Micro (ODU) | |
| Kerlink | TAO_kerlink.KERL_NANO.1_2.6.1 | Kerlink Wirnet iFemtoCell | Kernel: KerOS 5.11.0 |
| Kerlink | TAO_kerlink.KERL_NANO.2_2.6.1 | Kerlink Wirnet iFemtoCell-Evolution | Kernel: KerOS 5.11.0 |
| Kerlink | TAO_kerlink.KERL_ISTA.1_2.6.1 | Kerlink Wirnet iStation | Kernel: KerOS 5.11.0 |
| Kerlink | TAO_kerlink.KERL_IBTS.2_2.6.1 | Kerlink Wirnet iBTS | Kernel: KerOS 5.11.0 |
| Milesight | TAO_milesight.MILEST_UG65.1_2.6.1 | Milesight UG65/UG67 | Firmware 60.0.0.47-a4 |
| Tektelic | TAO_tektelic.TEKT_KONA.3_2.6.1 | Kona Micro | BSP 7.1.9 und 7.1.12 |
| UfiSpace | TAO_ufispace.UFISP_FCPICO.1_2.6.1 | Ufispace Pico/Enterprise | |
| Ufispace | TAO_ufispace.UFISP_FCMLB.1_2.6.1 | Ufispace MACRO V1.5 |
-
Für Kerlink-Gateways finden Sie im Kerlink-Wiki Informationen zum Upgrade Ihres Kernels auf KerOS 5.11.0.
-
Für Milesight UG65/67 folgen Sie den in den Milesight UG65/UG67 Installationsrichtlinien beschriebenen Installationsschritten.
-
Für das Browan Femto Indoor-Gateway wird eine spezifische Firmware benötigt. Folgen Sie den in den Browan Femto Installationsrichtlinien beschriebenen Installationsschritten.
Installationsschritte
Zuerst müssen Sie die Server-Installationsschritte auf Ihrem Master-Gateway ausführen. Dieser Server fungiert als erste Basisstation und hostet zusätzlich den LoRaWAN Network Server, einen MQTT-Server, den Node-RED-Server und die Benutzeroberfläche.
Wenn Sie anschließend ein Multi-Gateway-ThingPark Enterprise All-in-one (TAO) bereitstellen, müssen Sie die Remote-Gateway-Installationsschritte auf jedem Gateway ausführen, das als Remote-Basisstation fungiert, um Ihr LoRaWAN®-Netz zu erweitern. Sie können bis zu vier Remote-Gateways mit Ihrem TPE All-in-One-Server verbinden.
Hinweis
In einer Multi-Gateway-Bereitstellung muss das Master-Gateway, das als TAO-Server fungiert, eine statische IP-Adresse haben; Remote-Gateways können statisch oder per DHCP konfiguriert sein.
Speicherort des Installationspakets
Je nach Ihrem System muss das Installationspaket an einem bestimmten Speicherort auf Ihrer Basisstation installiert werden:
/homefür Ufispace/mnt/extrafür Tektelic/für Kerlink, Milesight, Browan
TAO-Installation für das Server-Gateway
-
Kopieren Sie das Installationspaket auf Ihr Gateway unter den spezifischen Speicherort.
scp TAO_<manufacturer>.<BS_PROFILE>_<version> <admin>@<gateway ip>:<specific location> -
Führen Sie das Installationspaket aus, indem Sie den Server-Installationsbefehl ausführen:
ssh <admin>@<gateway ip>
cd <specific location>
chmod u+x ./TAO_<manufacturer>.<BS_PROFILE>_<version>
./TAO_<manufacturer>.<BS_PROFILE>_<version> serverNachfolgend sehen Sie die Ausgabe einer Tektelic Kona Micro Server-Installation; die Ausgabe wird in Ihrem Fall sicherlich abweichen:
kona-micro-0173BA:/mnt/extra# ./TAO_tektelic.TEKT_KONA.3_2.6.1 server
TAO Installer [TAO_tektelic.TEKT_KONA.3_2.6.1]
Extracting ...
LRR custom configuration
-> TAO fresh install, add complete lrr custom folder
ipsec is not configured
/home/actility used as root directory
Execute system preparation scripts if any
execute script /home/actility/system/preinstall/10-add-ssh-keyscan.sh
/usr/bin/ssh-keyscan
execute script /home/actility/system/preinstall/20-add-ipsec2swanctl.sh
/usr/bin/ipsec2swanctl.py
System characteristics: setting file not present: automatic creation ...
-----------------------------------------------------------
Checking consistency of system definition
OK: SYSTEM defined: tek_generic
OK: MANUFACTURER defined: tektelic
OK: FIRMWARE defined: tekos
OK: MANUFACTURER_OUI defined: 647FDA
OK: at least one option set in [SEMTECH_V1_0 SEMTECH_V1_5 SEMTECH_V2_1 SEMTECH_CORECELL]
OK: TERMINFO defined: export TERMINFO=/etc/terminfo/
OK: NETSTAT defined: netstat -an
OK: VIEW_NTP_CONF defined: cat /etc/ntp.conf
OK: REBOOT_CMD defined: reboot
OK: TRACE_BACKUP_DIR defined: /home/actility/traces
OK: at least one option set in [TAR_OPTION_X TAR_OPTION_EXCLUDE]
OK: NETWORK_INTERFACE_FILE: valid file /etc/network/interfaces
OK: SYSTEM_ETC: valid directory /etc
OK: SWANCTL defined: /usr/sbin/swanctl
OK: SWANCTL: valid executable /usr/sbin/swanctl
OK: NTP_SERVICE: valid file /etc/init.d/ntpd
OK: SFTP: valid executable /home/actility/lrr/sftp/sftp
OK: IPTABLES_BIN: valid executable /usr/sbin/iptables
OK: NETWORK_INTERFACE_FILE defined: /etc/network/interfaces
-----------------------------------------------------------
System : tek_generic
ROOTACT already present in /etc/profile
Can't find '/etc/init.d/checklrr', can't stop service
Can't find '/etc/init.d/checkntp', can't stop service
Can't find '/etc/init.d/checkpki', can't stop service
Can't find '/etc/init.d/ipfailover2', can't stop service
Can't find '/etc/init.d/lrr', can't stop service
Can't find '/etc/init.d/lrrplan', can't stop service
Warning: One or more services return in error
create service checklrr
create service checkntp
create service checkpki
create service gwmgr_restore
create service ipfailover2
create service lrr
create service lrrplan
Adding system startup for /etc/init.d/firewall.
iptables are installed
New password: Retype new password: passwd: password updated successfully
Executing LRR usr_postinstall.sh
Common usr_postinstall.sh
- generate ipfailover2.ini
-----------------------------------------------------------
Checking consistency of lrr definition
OK: IPFAILOVER_SERVICE: valid executable /etc/init.d/ipfailover2
OK: SYSTEM_LOG: valid file /var/log/messages
-----------------------------------------------------------
Execute post-installation scripts if any
execute script /home/actility/lrr/postinstall/10-system_postinstall.sh
execute script /home/actility/lrr/postinstall/20-ipfailover2.sh
There is no service named "network-monitor"
no process in pidfile '/var/run/network-monitor.pid' found; none killed
update-rc.d: /etc/init.d/network-monitor-startup-rc exists during rc.d purge (continuing)
Removing any system startup links for network-monitor-startup-rc ...
update-rc.d: /etc/init.d/wwan0-startup-rc exists during rc.d purge (continuing)
Removing any system startup links for wwan0-startup-rc ...
execute script /home/actility/lrr/postinstall/30-migrate_services.sh
30-migrate_services.sh: Process checkntp
30-migrate_services.sh: Process checkpki
30-migrate_services.sh: Process ipfailover2
30-migrate_services.sh: Process gwmgr
30-migrate_services.sh: Process lrrplan
30-migrate_services.sh: Process lrr
execute script /home/actility/lrr/postinstall/70-migrate2checkpki.sh
70-migrate2checkpki.sh: migration not needed (no previous checkvpn2/checktls config)
70-migrate2checkpki.sh: migration done.
execute script /home/actility/lrr/postinstall/75-migrate_cmd_shells_pidfiles.sh
75-migrate_cmd_shells_pidfiles.sh: migration not needed
Starting checklrr service: Warning: checklrr started WITHOUT nohup !
[OK]
Starting checkntp service: Warning: checkntp started WITHOUT nohup !
[OK]
Starting checkpki service: Warning: checkpki started WITHOUT nohup !
[OK]
Starting ipfailover2 service: Warning: ipfailover2 started WITHOUT nohup !
[OK]
/usr/bin/python3
Starting lrr service: tek_generic
no command to power on radio board
Analyze calibration file ...
File created
no AES key generation on tekos model
Updating /home/actility/usr/etc/lrr/versions.ini file
/home/actility/usr/etc/lrr/versions.ini file updated
Warning: lrr started WITHOUT nohup !
[OK]
Starting lrrplan service: Warning: lrrplan started WITHOUT nohup !
[OK]
System configuration done
-----------------------------------------------------------
Checking consistency of system definition
OK: SYSTEM defined: tek_generic
OK: MANUFACTURER defined: tektelic
OK: FIRMWARE defined: tekos
OK: MANUFACTURER_OUI defined: 647FDA
OK: at least one option set in [SEMTECH_V1_0 SEMTECH_V1_5 SEMTECH_V2_1 SEMTECH_CORECELL]
OK: TERMINFO defined: export TERMINFO=/etc/terminfo/
OK: NETSTAT defined: netstat -an
OK: VIEW_NTP_CONF defined: cat /etc/ntp.conf
OK: REBOOT_CMD defined: reboot
OK: TRACE_BACKUP_DIR defined: /home/actility/traces
OK: at least one option set in [TAR_OPTION_X TAR_OPTION_EXCLUDE]
OK: NETWORK_INTERFACE_FILE: valid file /etc/network/interfaces
OK: SYSTEM_ETC: valid directory /etc
OK: SWANCTL defined: /usr/sbin/swanctl
OK: SWANCTL: valid executable /usr/sbin/swanctl
OK: NTP_SERVICE: valid file /etc/init.d/ntpd
OK: SFTP: valid executable /home/actility/lrr/sftp/sftp
OK: IPTABLES_BIN: valid executable /usr/sbin/iptables
OK: NETWORK_INTERFACE_FILE defined: /etc/network/interfaces
-----------------------------------------------------------
/home/actility used as root directory
System : tek_generic
System : tek_generic
New installation mechanism detected tek_generic
create service lrc
create service mqtt
create service node-red
create service tao
New password: Retype new password: passwd: password updated successfully
FDB_lora l folder exists
FDB_lora l/ffffffff table not present, create it
trying to set UUID 647FDA-647FDA0173BA in FDB_lora
UUID 647FDA-647FDA0173BA in FDB_lora is set
ck:58cca96b6025664c305ba9cfd416589e
/mnt/extra
migrateScript=/home/actility/tao-system/bootstrap/migrate-from-none.sh
/home/actility used as root directory
System : tek_generic
change tao / support password
New password: Retype new password: passwd: password updated successfully
restart LRR after updates
restart LRR after updates
/usr/bin/python3
Stopping lrr service: [OK]
Starting lrr service: tek_generic
no command to power on radio board
Analyze calibration file ...
File created
no AES key generation on tekos model
Updating /home/actility/usr/etc/lrr/versions.ini file
/home/actility/usr/etc/lrr/versions.ini file updated
Warning: lrr started WITHOUT nohup !
[OK]
restart other services after updates
restart service lrc
Stopping lrc.x service: [FAILED]
lrc.x is already stopped
Starting lrc.x service: tek_generic
Warning: lrc.x started WITHOUT nohup !
[OK]
restart service mqtt
Stopping mosquitto service: [FAILED]
mosquitto is already stopped
Starting mosquitto service: tek_generic
Warning: mosquitto started WITHOUT nohup !
[OK]
restart service node-red
Stopping node-red service: [FAILED]
node-red is already stopped
Starting node-red service: tek_generic
Warning: node-red started WITHOUT nohup !
[OK]
restart service tao
Stopping tao-server service: [FAILED]
tao-server is already stopped
Starting tao-server service: tek_generic
Warning: tao-server started WITHOUT nohup !
[OK]
restartServices done
System configuration done
Installation done
Installation log file unter /home/actility/TAO_installation_20241011_105026.log -
Sie müssen das Server-Gateway jetzt neu starten.
TAO-Installation für Remote-Gateways
Achtung
Dieser Installationsschritt ist nur relevant, wenn Sie ein Multi-Gateway-ThingPark Enterprise All-in-one verwenden. Führen Sie diese Aufgabe nicht aus, wenn Sie ein Single-Gateway-ThingPark Enterprise All-in-one verwenden.
Sie können mit der Installation Ihrer Remote-Gateways erst fortfahren, nachdem die Installation des Server-Gateways erfolgreich abgeschlossen wurde, wie in TAO-Installation für das Server-Gateway beschrieben.
Sie müssen die IP-Adresse Ihres Server-Gateways kennen.
-
Kopieren Sie das Installationspaket auf Ihr Gateway unter den spezifischen Speicherort.
scp TAO_<manufacturer>.<BS_PROFILE>_<version> <admin>@<gateway ip>:<specific location> -
Führen Sie das Installationspaket aus:
ssh <admin>@<gateway ip>
cd /
chmod u+x ./TAO_<manufacturer>.<BS_PROFILE>_<version>
./TAO_<manufacturer>.<BS_PROFILE>_<version> gw <ip of server gateway>HinweisSie können die Adresse <gateway ip> später über einen Remote-Befehl ändern.
Nachfolgend sehen Sie die Ausgabe einer Tektelic Kona Micro Gateway-Installation; die Ausgabe wird in Ihrem Fall sicherlich abweichen:
kona-micro-0173BA:/mnt/extra# ./TAO_tektelic.TEKT_KONA.3_2.6.1 gw 10.100.31.122
TAO Installer [TAO_tektelic.TEKT_KONA.3_2.6.1]
Extracting ...
LRR custom configuration
-> TAO fresh install, add complete lrr custom folder
ipsec is not configured
/home/actility used as root directory
Execute system preparation scripts if any
execute script /home/actility/system/preinstall/10-add-ssh-keyscan.sh
/usr/bin/ssh-keyscan
execute script /home/actility/system/preinstall/20-add-ipsec2swanctl.sh
/usr/bin/ipsec2swanctl.py
System characteristics: setting file not present: automatic creation ...
-----------------------------------------------------------
Checking consistency of system definition
OK: SYSTEM defined: tek_generic
OK: MANUFACTURER defined: tektelic
OK: FIRMWARE defined: tekos
OK: MANUFACTURER_OUI defined: 647FDA
OK: at least one option set in [SEMTECH_V1_0 SEMTECH_V1_5 SEMTECH_V2_1 SEMTECH_CORECELL]
OK: TERMINFO defined: export TERMINFO=/etc/terminfo/
OK: NETSTAT defined: netstat -an
OK: VIEW_NTP_CONF defined: cat /etc/ntp.conf
OK: REBOOT_CMD defined: reboot
OK: TRACE_BACKUP_DIR defined: /home/actility/traces
OK: at least one option set in [TAR_OPTION_X TAR_OPTION_EXCLUDE]
OK: NETWORK_INTERFACE_FILE: valid file /etc/network/interfaces
OK: SYSTEM_ETC: valid directory /etc
OK: SWANCTL defined: /usr/sbin/swanctl
OK: SWANCTL: valid executable /usr/sbin/swanctl
OK: NTP_SERVICE: valid file /etc/init.d/ntpd
OK: SFTP: valid executable /home/actility/lrr/sftp/sftp
OK: IPTABLES_BIN: valid executable /usr/sbin/iptables
OK: NETWORK_INTERFACE_FILE defined: /etc/network/interfaces
-----------------------------------------------------------
System : tek_generic
ROOTACT already present in /etc/profile
Can't find '/etc/init.d/checklrr', can't stop service
Can't find '/etc/init.d/checkntp', can't stop service
Can't find '/etc/init.d/checkpki', can't stop service
Can't find '/etc/init.d/ipfailover2', can't stop service
Can't find '/etc/init.d/lrr', can't stop service
Can't find '/etc/init.d/lrrplan', can't stop service
Warning: One or more services return in error
create service checklrr
create service checkntp
create service checkpki
create service gwmgr_restore
create service ipfailover2
create service lrr
create service lrrplan
Adding system startup for /etc/init.d/firewall.
iptables are installed
New password: Retype new password: passwd: password updated successfully
Executing LRR usr_postinstall.sh
Common usr_postinstall.sh
- generate ipfailover2.ini
-----------------------------------------------------------
Checking consistency of lrr definition
OK: IPFAILOVER_SERVICE: valid executable /etc/init.d/ipfailover2
OK: SYSTEM_LOG: valid file /var/log/messages
-----------------------------------------------------------
Execute post-installation scripts if any
execute script /home/actility/lrr/postinstall/10-system_postinstall.sh
execute script /home/actility/lrr/postinstall/20-ipfailover2.sh
There is no service named "network-monitor"
no process in pidfile '/var/run/network-monitor.pid' found; none killed
update-rc.d: /etc/init.d/network-monitor-startup-rc exists during rc.d purge (continuing)
Removing any system startup links for network-monitor-startup-rc ...
update-rc.d: /etc/init.d/wwan0-startup-rc exists during rc.d purge (continuing)
Removing any system startup links for wwan0-startup-rc ...
execute script /home/actility/lrr/postinstall/30-migrate_services.sh
30-migrate_services.sh: Process checkntp
30-migrate_services.sh: Process checkpki
30-migrate_services.sh: Process ipfailover2
30-migrate_services.sh: Process gwmgr
30-migrate_services.sh: Process lrrplan
30-migrate_services.sh: Process lrr
execute script /home/actility/lrr/postinstall/70-migrate2checkpki.sh
70-migrate2checkpki.sh: migration not needed (no previous checkvpn2/checktls config)
70-migrate2checkpki.sh: migration done.
execute script /home/actility/lrr/postinstall/75-migrate_cmd_shells_pidfiles.sh
75-migrate_cmd_shells_pidfiles.sh: migration not needed
Starting checklrr service: Warning: checklrr started WITHOUT nohup !
[OK]
Starting checkntp service: Warning: checkntp started WITHOUT nohup !
[OK]
Starting checkpki service: Warning: checkpki started WITHOUT nohup !
[OK]
Starting ipfailover2 service: Warning: ipfailover2 started WITHOUT nohup !
[OK]
/usr/bin/python3
Starting lrr service: tek_generic
no command to power on radio board
Analyze calibration file ...
File created
no AES key generation on tekos model
Updating /home/actility/usr/etc/lrr/versions.ini file
/home/actility/usr/etc/lrr/versions.ini file updated
Warning: lrr started WITHOUT nohup !
[OK]
Starting lrrplan service: Warning: lrrplan started WITHOUT nohup !
[OK]
System configuration done
-----------------------------------------------------------
Checking consistency of system definition
OK: SYSTEM defined: tek_generic
OK: MANUFACTURER defined: tektelic
OK: FIRMWARE defined: tekos
OK: MANUFACTURER_OUI defined: 647FDA
OK: at least one option set in [SEMTECH_V1_0 SEMTECH_V1_5 SEMTECH_V2_1 SEMTECH_CORECELL]
OK: TERMINFO defined: export TERMINFO=/etc/terminfo/
OK: NETSTAT defined: netstat -an
OK: VIEW_NTP_CONF defined: cat /etc/ntp.conf
OK: REBOOT_CMD defined: reboot
OK: TRACE_BACKUP_DIR defined: /home/actility/traces
OK: at least one option set in [TAR_OPTION_X TAR_OPTION_EXCLUDE]
OK: NETWORK_INTERFACE_FILE: valid file /etc/network/interfaces
OK: SYSTEM_ETC: valid directory /etc
OK: SWANCTL defined: /usr/sbin/swanctl
OK: SWANCTL: valid executable /usr/sbin/swanctl
OK: NTP_SERVICE: valid file /etc/init.d/ntpd
OK: SFTP: valid executable /home/actility/lrr/sftp/sftp
OK: IPTABLES_BIN: valid executable /usr/sbin/iptables
OK: NETWORK_INTERFACE_FILE defined: /etc/network/interfaces
-----------------------------------------------------------
/home/actility used as root directory
System : tek_generic
System : tek_generic
New installation mechanism detected tek_generic
create service tao
migrateScript=/home/actility/tao-system/bootstrap/migrate-from-none.sh
/home/actility used as root directory
System : tek_generic
change tao / support password
New password: Retype new password: passwd: password updated successfully
restart service tao
Stopping tao-agent service: [FAILED]
tao-agent is already stopped
Starting tao-agent service: tek_generic
Warning: tao-agent started WITHOUT nohup !
[OK]
System configuration done
/usr/bin/python3
Stopping lrr service: [OK]
/usr/bin/python3
Starting lrr service: tek_generic
no command to power on radio board
Analyze calibration file ...
File created
no AES key generation on tekos model
Updating /home/actility/usr/etc/lrr/versions.ini file
/home/actility/usr/etc/lrr/versions.ini file updated
Warning: lrr started WITHOUT nohup !
[OK]
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.7 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
Installation done
Installation log file unter /home/actility/TAO_installation_20241011_105026.log -
Sie müssen das Remote-Gateway jetzt neu starten.