Skip to main content

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.

  1. From SUPLOG's root menu, choose System configuration, then Backhaul. A screen similar to the following example will display:

  1. 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.

    For SaaS deployments

     LRC0 address / LRC1 addressFTP download 0 / FTP download 1FTP upload 0 / FTP upload 1Reverse SSH 0 / Reverse SSH 1
    TPE SaaS EU-PROD10.112.12.10 / 10.112.22.1010.112.12.10 / 10.112.22.1010.112.12.25 / 10.112.22.25a-support1-eu.thingpark.com / b-support1-eu.thingpark.com
    TPE SaaS AU-PROD10.132.12.17 / 10.132.22.1710.132.12.17 / 10.132.22.1710.132.12.25 / 10.132.22.25a-support1-au1.thingpark.com /b-support1-au1.thingpark.com
    TPE SaaS US-PROD10.102.12.10 / 10.102.22.1010.102.12.10 / 10.102.22.1010.102.12.25 / 10.102.22.25support1-us.thingpark.com / support2-us.thingpark.com
    ThingPark Community10.152.12.10 / 10.152.22.1010.152.12.10 / 10.152.22.1010.152.12.25 / 10.152.22.25support1-poc.thingpark.com / support2-poc.thingpark.com

    For self-hosted deployments

    • When base stations are using IPSEC:

       LRC0 address / LRC1 addressFTP download 0 / FTP download 1FTP upload 0 / FTP upload 1Reverse SSH 0 / Reverse SSH 1
      Default subnets192.168.0.140 / 192.168.0.2192.168.0.142 / 192.168.0.3192.168.0.142 / 192.168.0.3Use the public IP address(es) (Network Server IP) configured in Cockpit.
      Custom subnetsx.y.z.140 / x.y.z.2 (1)x.y.z.142 / x.y.z.3 (1)x.y.z.142 / x.y.z.3 (1)Use the public IP address(es) (Network Server IP) configured in Cockpit.

      (1) Where x.y.z is the custom subnet configured on the self-hosted ThingPark Enterprise deployment. For example, if the configured custom subnet is 10.5.16.0/24, LRC0 / LRC1 addresses are 10.5.16.140 / 10.5.16.2.

      Note IP address for LRC1, FTP download/upload 1 and Reverse SSH 1 shall only be filled if your self-hosted TPE is deployed in High Availability (HA) mode. When self-hosted TPE 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.

    • When base stations are using TLS:

      • LRC and FTP addresses are not configurable.
      • Use the public IP address (Network Server IP) configured in Cockpit to set the IP address(es) of Reverse SSH core endpoints according to your addressing plan.
      • For self-hosted TPE 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).

    • When base stations are not using any security framework (neither Ipsec nor TLS):

      • Use the public IP address (Network Server IP) configured in Cockpit to set the IP address(es) of LRC/FTP/Reverse SSH core endpoints according to your addressing plan.
      • For self-hosted TPE 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 IP address for Reverse SSH 1 shall only be filled if your self-hosted TPE is deployed in High Availability (HA) mode. When self-hosted TPE is deployed in standalone mode, fill this information only for nodes #0 (Reverse SSH 0) and remove information for nodes #1 if already pre-filled.

    Note The ICMP destinations used to validate the state of each network interface are automatically set as follows:

    • If PKI is active (meaning the 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, ICMP 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.

Copyright © 2023 Actility