Configuring core network endpoints
This task allows you to configure the endpoints of the ThingPark core network on your base station. In ThingPark terminology, the LoRaWAN® network server is called LRC (Long Range Controller).
Follow these steps to edit your backhaul configuration, you may also need to do this task if you want to move your base station from one ThingPark platform to another.
From SUPLOG’s root menu, choose System configuration, then Backhaul. A screen similar to the following example will display:
For ThingPark Enterprise deployments, use the following table to fill this form.
Note For SaaS deployments, since PKI (IPSec) should be enabled, the LRC and FTP core network endpoints use private IP addresses.
Note Reverse SSH server is a system component included in ThingPark core network architecture. It acts as a jump server, allowing remote access to the base station through reverse SSH.
LRC0 address / LRC1 address FTP download 0 / FTP download 1 FTP upload 0 / FTP upload 1 Reverse SSH 0 / Reverse SSH 1 TPE-SaaS EU-PROD 10.112.12.10 / 10.112.22.10 10.112.12.10 / 10.112.22.10 10.112.12.25 / 10.112.22.25 a-support1-eu.thingpark.com / b-support1-eu.thingpark.com TPE-SaaS AU-PROD 10.132.12.17 / 10.132.22.17 10.132.12.17 / 10.132.22.17 10.132.12.25 / 10.132.22.25 a-support1-au1.thingpark.com /b-support1-au1.thingpark.com TPE-SaaS US-PROD 10.102.12.10 / 10.102.22.10 10.102.12.10 / 10.102.22.10 10.102.12.25 / 10.102.22.25 support1-us.thingpark.com / support2-us.thingpark.com ThingPark Community 10.152.12.10 / 10.152.22.10 10.152.12.10 / 10.152.22.10 10.152.12.25 / 10.152.22.25 support1-poc.thingpark.com / support2-poc.thingpark.com TPE-OCP* (PKI enabled) 192.168.0.140 / 192.168.0.2 192.168.0.142 / 192.168.0.3 192.168.0.142 / 192.168.0.3 Use the public IP address (Network Server IP) configured in Cockpit TPE-OCP**(PKI disabled) Use the public IP address (Network Server IP) configured in Cockpit * IP address for LRC1, FTP download/upload 1 and Reverse SSH 1 shall only be filled if your TPE-OCP is deployed in High Availability (HA) mode. When TPE-OCP is deployed in standalone mode, fill this information only for nodes #0 (LRC0, FTP download/upload 0 and Reverse SSH 0) and remove information for nodes #1 if already pre-filled. **For TPE-OCP deployment without IPSec/TLS, set the IP address(es) of LRC/FTP/Reverse SSH core endpoints according to the addressing plan used for the deployment of your ThingPark Enterprise instance. For TPE-OCP High Availability mode, use both IP addresses set in cockpit for primary LRC (set it for nodes #0) and secondary LRC (set it for nodes #1).
Note The ICMP destinations used to validate the state of each network interface are automatically set as follows:
If PKI is active (meaning backhaul connection is secured either by IPSec or TLS): ICMP pings the ThingPark core network component that terminates the IPSec/TLS connection (also known as SLRC).
Otherwise, ICPM pings the ThingPark Network Server (also known as LRC).
Once you are done with your changes in this menu, click Confirm to save your configuration.
Note At this stage, the configuration is only saved by the system, but it has not yet been applied to the base station. To learn more, see Apply/Commit/Rollback mechanism.