Version: TAO v1.x

Installations- und Upgrade-Verfahren

Diese Seite beschreibt das manuelle Installationsverfahren.

Nichtsdestotrotz können Sie das Zero-Touch-/automatisierte Installationsverfahren des Infrastructure Commissioning Service (ICS) nutzen. Wenden Sie sich dazu bitte an Ihr ThingPark Support-Team.

Für ein Upgrade müssen Sie die gleichen Schritte wie für das Installationsverfahren ausführen und die Box am Ende des Verfahrens neu starten.

Installationsanforderungen

Die nachfolgend beschriebene Installation ist manuell. Sie benötigen SSH-Zugriff auf die Basisstations-Box und das Root-Passwort.
Im Problemfall müssen Sie möglicherweise ein FTDI-Kabel verwenden, um die Box direkt anzuschließen.
Sie benötigen mindestens 500 MB freien Festplattenspeicher.
Sie benötigen das passende Installationspaket für Ihre Hardware:

scheme: TAO_<manufacturer>.<BS_PROFILE>_<version>

Neueste Releases

Hersteller	TAO-Paket	Referenz	Anmerkungen
UfiSpace	TAO_ufispace.UFISP_FCPICO.1_1.3.1	Ufispace Pico/Enterprise
	TAO_ufispace.UFISP_FCMLB.1_1.3.1	Ufispace MACRO V1.5
Gemtek	TAO_gemtek.GMTK_ODU.1_1.4.0	Browan Outdoor Micro
	TAO_gemtek.GMTK_FMTO.1_1.3.1	Browan Indoor Femto
Kerlink	TAO_kerlink.KERL_NANO.1_1.3.2	Kerlink Wirnet iFemtoCell	Kernel: keros 4.3.3
	TAO_kerlink.KERL_NANO.2_1.4.0	Kerlink Wirnet iFemtoCell-Evolution	Kernel: keros 5.10.1
	TAO_kerlink.KERL_NANO.2_1.3.1	Kerlink Wirnet iFemtoCell-Evolution	Kernel: keros 4.3.3
	TAO_kerlink.KERL_ISTA.1_1.4.0	Kerlink Wirnet iStation	Kernel: keros 4.3.3
	TAO_kerlink.KERL_IBTS.2_1.4.0	Kerlink Wirnet iBTS	Kernel: keros 4.3.3
Milesight	TAO_milesight.MILEST_UG65.1_1.4.0	Milesight UG65/UG67

Für das Browan Femto Indoor-Gateway benötigen Sie außerdem eine spezielle Firmware. Bitte folgen Sie dem entsprechenden Installationshandbuch: Browan Femto installation guidelines.
Für Milesight UG65/67 folgen Sie bitte dem zugehörigen Installationshandbuch: Milesight UG65/UG67 installation guidelines
Für Kerlink Wirnet iFemtoCell, iFemtoCell-Evolution, iStation, iBTS müssen Sie einen speziellen Kernel installiert haben. Bitte folgen Sie dem Kerlink wiki.

Installationsschritte

Kopieren Sie das Installationspaket auf Ihre Box unter /

scp TAO_<manufacturer>.<BS_PROFILE>_<version>  <admin>@<box ip>:/

Führen Sie das Installationspaket aus

ssh <admin>@<box ip>
cd /
chmod u+x ./TAO_<manufacturer>.<BS_PROFILE>_<version> 
./TAO_<manufacturer>.<BS_PROFILE>_<version> 

Hier ist die Ausgabe einer Kerlink-wirfevo-Installation; die Ausgabe wird in Ihrem Fall sicherlich anders sein:

root@klk-fevo-0404B3:/ # ./TAO_kerlink.KERL_NANO.2_1.3.1

Self Extracting Installer

./
./rootfs-patch-tao-1.3.1-wirfevo.tar.gz
./install.autorun
Execute tao-install.sh
LRR custom configuration
-> TAO fresh install, add complete lrr custom folder
ipsec is in /etc, need to clean files and folder
System characteristics: setting file not present: automatic creation ...
-----------------------------------------------------------
Checking consistency of system definition
OK: SYSTEM defined: wirfevo
OK: MANUFACTURER defined: kerlink
OK: FIRMWARE defined: keros
OK: MANUFACTURER_OUI defined: 7076ff
OK: SEMTECH_REFDESIGN: 1.5 in (1.0 1.5 2.1)
OK: at least one option set in [SEMTECH_V1_0 SEMTECH_V1_5 SEMTECH_V2_1]
OK: TERMINFO defined: export TERMINFO=/etc/terminfo/
OK: NETSTAT defined: netstat -an
OK: VIEW_NTP_CONF defined: cat /etc/ntp.conf
OK: TRACE_BACKUP_DIR defined: /user/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: IPSEC: valid executable /usr/sbin/ipsec
OK: IPSEC_CONF: valid file /etc/ipsec.conf
OK: NTP_SERVICE: valid file /etc/init.d/ntpd
OK: SFTP: valid executable /user/actility/lrr/sftp/sftp
OK: IPTABLES_BIN: valid executable /usr/sbin/iptables
OK: NETWORK_INTERFACE_FILE defined: /etc/network/interfaces
-----------------------------------------------------------
/user/actility used as root directory
System : wirfevo
ROOTACT not present in /etc/profile : add it
New installation mechanism detected
create service checkntp
create service checktls
create service checkvpn2
create service gwmgr_restore
create service ipfailover2
create service lrr
create service lrrplan
Stopping Kerlink firewall
Flushing iptable rules.
Set default policy to 'ACCEPT'
Flushing ip6table rules.
Setting default IPv6 policy to 'ACCEPT'
Starting LRR firewall
Thu Apr 27 10:32:22 2023 [/etc/rcU.d/S89lrrfirewall] Info: create /var/run/lrrsystem: ROOTACT=/user/actility
/etc/rcU.d/S89lrrfirewall: line 53: /user/actility/var/log/lrr/iptablesfrom.log: No such file or directory
iptables are installed
Keros system setting
Restarting OpenBSD Secure Shell server: sshdstopped /usr/sbin/sshd (pid 980)
.
Fix /etc/nsswitch.conf issue
LRR characteristics: setting file not present: automatic creation ...
-----------------------------------------------------------
Checking consistency of lrr definition
OK: CHECKVPN_SERVICE: valid executable /etc/rcU.d/S90checkvpn2
OK: IPFAILOVER_SERVICE: valid executable /etc/rcU.d/S90ipfailover2
OK: SYSTEM_LOG: valid file /var/log/messages
-----------------------------------------------------------
execute postinstall script /user/actility/lrr/postinstall/ipfailover2.sh
execute postinstall script /user/actility/lrr/postinstall/migrate2nfr920.sh
82 - checkvpn2: Can't find vpn.cfg to migrate, no conversion to be done...
;       Defines the principal interface
        principal=eth0
;       Defines the bandwidth constraint to be applied on the principal interface (0: No constraint, 1: Limited bandwidth, 2: Very limited bandwidth)
        bandwidthconstraint_principal=0
[bandwidthconstraint_principal:0]
;       In seconds, defines at which frequency we test connectivity on principal interface when principal interface is used
;       In seconds, defines at which frequency we test connectivity on principal interface when rescue interface is used
;       In seconds, defines the ping timeout used for testing connectivity on principal interface
;       Defines the amount of consecutive failed ping before deciding to restart the principal interface
        maxfailedprincipal=5
[bandwidthconstraint_principal:1]
;       In seconds, defines at which frequency we test connectivity on principal interface when principal interface is used
;       In seconds, defines at which frequency we test connectivity on principal interface when rescue interface is used
;       In seconds, defines the ping timeout used for testing connectivity on principal interface
;       Defines the amount of consecutive failed ping before deciding to restart the principal interface
        maxfailedprincipal=5
[bandwidthconstraint_principal:2]
;       In seconds, defines at which frequency we test connectivity on principal interface when principal interface is used
;       In seconds, defines at which frequency we test connectivity on principal interface when rescue interface is used
;       In seconds, defines the ping timeout used for testing connectivity on principal interface
;       Defines the amount of consecutive failed ping before deciding to restart the principal interface
        maxfailedprincipal=5
89 - ipfailover2: ipfailover2.ini already exists, no conversion to be done...
439 - ipfailover cleansing: nothing to clean...
596 - ipfailover2: force postinstall after possible service activation
600 - ==== Migration to NFR920 not requested ... ====
VPN only supports LRRUUID-based uidmode (fromtwa or fromtwaonly)
execute postinstall script /user/actility/lrr/postinstall/system_postinstall.sh
Keros post-installation
Removing any system startup links for ztp ...
  /etc/rc0.d/K10ztp
  /etc/rc1.d/K10ztp
  /etc/rc2.d/S54ztp
  /etc/rc3.d/S54ztp
  /etc/rc5.d/S54ztp
  /etc/rc6.d/K10ztp
restart service checkntp
Stopping /user/actility/lrr/com/checkntp.sh service: [FAILED]
/user/actility/lrr/com/checkntp.sh is already stopped
Starting /user/actility/lrr/com/checkntp.sh service: [OK]
restart service checktls
Stopping checkTLS service: [FAILED]
checkTLS is already stopped
Starting checkTLS service: [OK]
restart service checkvpn2
VPN only supports LRRUUID-based uidmode (fromtwa or fromtwaonly)
restart service gwmgr_restore
restart service ipfailover2
Stopping /user/actility/lrr/failovermgr/ifacefailover2.sh service: [FAILED]
/user/actility/lrr/failovermgr/ifacefailover2.sh is already stopped
Starting /user/actility/lrr/failovermgr/ifacefailover2.sh service: [OK]
restart service lrr
Stopping lrr service: [FAILED]
lrr is already stopped
Starting lrr service: wirfevo
no command to power on radio board
Analyze calibration file ...
File /user/actility/usr/etc/lrr/lowlvlgw.ini created
Updating /user/actility/usr/etc/lrr/versions.ini file
/user/actility/usr/etc/lrr/versions.ini file updated
[OK]
restart service lrrplan
Stopping lrrplan service: [FAILED]
lrrplan is already stopped
Starting lrrplan service: [OK]
System configuration done
-----------------------------------------------------------
Checking consistency of system definition
OK: SYSTEM defined: wirfevo
OK: MANUFACTURER defined: kerlink
OK: FIRMWARE defined: keros
OK: MANUFACTURER_OUI defined: 7076ff
OK: SEMTECH_REFDESIGN: 1.5 in (1.0 1.5 2.1)
OK: at least one option set in [SEMTECH_V1_0 SEMTECH_V1_5 SEMTECH_V2_1]
OK: TERMINFO defined: export TERMINFO=/etc/terminfo/
OK: NETSTAT defined: netstat -an
OK: VIEW_NTP_CONF defined: cat /etc/ntp.conf
OK: TRACE_BACKUP_DIR defined: /user/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: IPSEC: valid executable /usr/sbin/ipsec
OK: IPSEC_CONF: valid file /etc/ipsec.conf
OK: NTP_SERVICE: valid file /etc/init.d/ntpd
OK: SFTP: valid executable /user/actility/lrr/sftp/sftp
OK: IPTABLES_BIN: valid executable /usr/sbin/iptables
OK: NETWORK_INTERFACE_FILE defined: /etc/network/interfaces
-----------------------------------------------------------
/user/actility used as root directory
System : wirfevo
System : wirfevo
New installation mechanism detected wirfevo
create service lrc
create service mqtt
create service node-red
create service tao
Keros system setting
trying to set UUID 7076FF-7076FF05179F in FDB_lora
UUID 7076FF-7076FF05179F in FDB_lora is set
/user/actility/lrc/keyencrypt/keyencrypt.x: /user/actility/lrr/keros_addon/lib/libcrypto.so.1.0.0: no version information available (required by /user/actility/lrc/keyencrypt/keyencrypt.x)
/user/actility/lrc/keyencrypt/keyencrypt.x: /user/actility/lrr/keros_addon/lib/libcrypto.so.1.0.0: no version information available (required by /user/actility/lrr/keros_addon/lib/libssl.so.1.0.0)
/user/actility/lrc/keyencrypt/keyencrypt.x: /user/actility/lrr/keros_addon/lib/libcrypto.so.1.0.0: no version information available (required by /user/actility/lrr/keros_addon/lib/libssl.so.1.0.0)
/user/actility/lrc/keyencrypt/keyencrypt.x: /user/actility/lrr/keros_addon/lib/libcrypto.so.1.0.0: no version information available (required by /user/actility/lrr/keros_addon/lib/libssl.so.1.0.0)
/tmp/selfextract.WQ8Qx2
migrateScript=/user/actility/tao-system/bootstrap/migrate-from-none.sh
/user/actility used as root directory
System : wirfevo
restart service lrc
Stopping lrc.x service: [FAILED]
lrc.x is already stopped
Starting lrc.x service: wirfevo
[OK]
restart service mqtt
Stopping mosquitto service: [FAILED]
mosquitto is already stopped
Starting mosquitto service: wirfevo
[OK]
restart service node-red
Stopping node-red service: [FAILED]
node-red is already stopped
Starting node-red service: wirfevo
[OK]
restart service tao
Stopping tao-server service: [FAILED]
tao-server is already stopped
Starting tao-server service: wirfevo
[OK]
System configuration done
Stopping lrr service: [OK]
Starting lrr service: wirfevo
no command to power on radio board
Analyze calibration file ...
File /user/actility/usr/etc/lrr/lowlvlgw.ini created
Updating /user/actility/usr/etc/lrr/versions.ini file
/user/actility/usr/etc/lrr/versions.ini file updated
[OK]
Installation done

Sie können das Gateway nun neu starten.

Installationsanforderungen​

Neueste Releases​

Installationsschritte​

Installationsanforderungen

Neueste Releases

Installationsschritte