3.2.1.1 Example configurations

MNC and Backend services on same host (all-in-one installation)

This is a very simple configuration running backend and MNC service on the same host without any additional features:

# MNC server
backend.mnc.1.ip=127.0.0.1
backend.mnc.1.name=MNC

# EventDB server
eventdb.server=127.0.0.1

Two MNC systems and a backend server on different host

This setup includes 3 different hosts:

• One central server running the backend service, event database SatDB datbase.
• Two hosts running the MNC service.

The backend service connects via network to the MNC services on both host. And the MNC services deliver their events to the central server and using the SatDB on the central server.

# MNC servers
backend.mnc.1.ip=10.16.2.1
backend.mnc.1.name=UPLINK-TP1
backend.mnc.2.ip=10.16.2.2
backend.mnc.2.name=UPLINK-TP2

# EventDB server
eventdb.server=10.16.2.21

# SatDB server
db.satlist.host=10.16.2.22
db.satlist.user=postgres
db.satlist.password=mysecretpassword
db.satlist.usessl=true

backend server controlling redundant MNC systems

This setup includes also 3 different hosts:

• One central server running the backend service, event database SatDB datbase.
• A redundant pair of MNC services (Main and Backup)

The backend service connects via network to both hosts and control which one is the currently active MNC service. The backend services monitors the availability and stops & starts the MNC services on the hosts as required.

The active MNC service delivers its events to the cental EventDB server

# MNC servers
backend.mnc.1.ip=10.16.2.1
backend.mnc.1.name=UPLINK-TP1
backend.mnc.1.backup.ip=10.16.2.2
backend.mnc.1.backup.retries=3
backend.mnc.1.backup.delay=30

# EventDB server
eventdb.server=10.16.2.21