Infrastructure configuration

The Infrastructure configuration is managed in the TPE Services Cockpit module.

Viewing the infrastructure configuration

1. In the TPE Services Cockpit module, click the TPE cluster operations dropdown button and then Show infrastructure configuration
2. A modal opens displaying the configuration

Editing the infrastructure configuration

1. In the TPE Services Cockpit module, click the TPE cluster operations dropdown button and then Redeploy cluster
2. A wizard opens. Change the configuration on the first step of the wizard
3. Click Redeploy
4. The second step of the wizard displays the progression of the redeploy
5. Once the redeploy is finished, the wizard can be closed

Infrastructure configuration properties

Installation ID

The Installation ID is read-only. It is the identifier of the installation and is hardware-dependent.

If the TPE instance must be reinstalled on new hardware, the license becomes invalid. Additionally, for online installation, the repository (that is used for yum, docker images, catalogs, and Base Station images) also becomes unreachable unless a new license is subscribed.

To change your license subscription or subscribe to a new license, go to the Actility Central portal.

NTP configuration

NTP servers (IP address or hostname) that will be used for time synchronization.

WARNING

For High Availability deployment, each TPE node must be synchronized with NTP servers. Be sure to configure at least one functional NTP server.

Level 3 remote access server

SSH remote server location for level 3 access ([user@]host[:port][/path]).

Installation repository

Keep defaults if you are going to install TPE by using Actility's remote repository.

Put the local repository URL if you are going to install TPE by using the local media, see Local repository installation on how to install/start the local repository and get the local repository URL.

Installation proxy URL

URL of the proxy server used for installation repository access, only HTTP is supported.

Leave blank if you don't want to use a proxy.

Internal Subnet

By default, the subnet that the TPE platform will use internally for container networking is 192.168.0.0/20. You can change it if needed by setting a different /20 IPV4 block. If the internal subnet is customized, the IPsec subnets may also be customized accordingly just after the cluster creation in the TPE configuration screen.

info

For gateways configured to use IPsec, the addresses of LRC0, LRC1, FTP0 and FTP1 must be customized by the user. The IPs to set for are:

• LRC0: 140th address of the subnet
• LRC1: 2nd address of the subnet (for a HA deployment)
• FTP0: 142nd of the subnet
• FTP1: 3rd address of the subnet (for a HA deployment)

For instance, if you choose the subnet 10.5.16.0/20, IPs to configure on the gateways are:

• LRC0: 10.5.16.140
• LRC1: 10.5.16.21 (for a HA deployment)
• FTP0: 10.5.16.142
• FTP1: 10.5.16.32 (for a HA deployment)

The IPs that match your configuration are displayed when viewing the infrastructure configuration.

Source addresses allowed to access the system monitoring SNMP

IP addresses allowed to access the SNMP agent exposing the system monitoring metrics of the node. See SNMP monitoring for more information.