1.2.4 Configuration

This section describes only the intital configuration step for the sat-nms MNC service. Because the configuration of the M&C itself can be done via Web interface. Please refere to the following chapters:

• web client: Device-Setup
• web client: Screen-Editor

The system ships a default configuration which is "ready-to-run" but you can modify some configuration to adapt the system to your environment. For a all-in-one MNC System no additional configuration is required.

Several other options require your attention only for complex setups which includes server redundancy. A detailed description of all options from is available in the Administration Section of this Manual.

To ensure the MNC service will automatically start on reboot, login as root and enable this service.

• login as root
• enable autostart with `systemctl enable satnms"

Now you can start the backend service as user satnms and check if its running.

• login as satnms
• run the satnms-watch

┌──────────────────────┤ sat-nms state ├─────────────────────────┐
│                                                                │
│   hostname / MNC name : satnms7-dev / MNC                      │
│   satnms OS version   : debian-satnms-7.01 2023-10-05          │
│   ____________________________________________________________ │
│                                                                │
│   MNC service         : STOPPED                                │
│   MNC service version : not installed                          │
│                                                                │
  ...
│                                                                │
│   last updated        : 2025-14-02 16:48:48 UTC                │
│   ____________________________________________________________ │
│                                                                │
│             refresh      refresh service states                │
│             satnms-start start MNC Service                     │
│             backend-stop stop Backend Service                  │
│             nginx-start  start Nginx Webserver                 │
│                                                                │
│             <Select service>           <Exit>                  │
└────────────────────────────────────────────────────────────────┘

The output depends on the installed services. In the example above, only the sat-nms MNC service is installed and running.

You can also control the MNC service directly with the follwing commands:

• start MNC service sudo systemctl start satnms
• stop MNC service sudo systemctl stop satnms

Check if the MNC service start successfully:

• status of MNC service systemctl status satnms

satnms@satnms7-dev:~/backend$ systemctl status backend
TODO

You can test if the MNC started successfully by checking the output of the log file /home/satnms/debug.log. The first line shows an early stage of start process and is an indication that the MNC service begins to start. The second line shows that all sub processes are now initialized and the MNC service is ready to serve client requests. Starting from this the backend service or clients are able to connect to the MNC service.

satnms@satnms7-dev:~$ tail /home/satnms/debug.log
...
000000 2025-03-05 12:32:18 2025-03-05 12:32:18   I SYSTEM Loading setup data (sat-nms MNC default config)
...
000000 2025-03-05 12:32:18 2025-03-05 12:32:18   I SYSTEM VLC 3.68.9 2025-03-05 07:22:02 is up
...

Some more details and extended error messages if something failed are available in /home/satnms/.panic.log

A typical output of the default installation should looks like this:

satnms@satnms:~$ cat .panic.log
satnms version 3.68.9 2025-03-05 07:22:02
TRAPREC: File traprcv.json not found
TRAPREC: Cannot parse traprcv.json
TRAPREC: Trap receiver not started.
Universal SNMP agent listening at port 2261
TCP remote control server (r/w) listening at port 2016
TCP remote control server (r/o) listening at port 2017
SSL remote control server (r/w) listening at port 2015

A detailed description how to run the sat-nms MNC service is available in the administration manual.

Troubleshooting

If you have trouble to bring up the MNC service check first if the MNC service is still running with:

• systemctl status satnms or
• /home/satnms/satnms-stat

Additionally you can lookup the process ID (PID) of the backend service process:

satnms@satnms7-dev:~$  ps aux |grep satnms.jar
satnms   8204 ?   Sl   25:18 java -cp satnms.jar:/home/satnms/jars/* -mx512m -Djava.security.egd=file:/dev/./urandom -Dhostname=MNC satnms3.vlc.Server -e

Now check if the MNC process with this PID (here 8204 from the second column) is associated to a process listening on TCP ports from 2000 and above. The real number of listing ports depends on the actual configuration, but at least 2000-2007 should be visible.

satnms@satnms7-dev:~$ ss -tanp |grep 8204
LISTEN 0      50                      *:2000                   *:*     users:(("java",pid=8204,fd=11))
LISTEN 0      50                      *:2001                   *:*     users:(("java",pid=8204,fd=35))
LISTEN 0      50                      *:2002                   *:*     users:(("java",pid=8204,fd=42))
LISTEN 0      50                      *:2003                   *:*     users:(("java",pid=8204,fd=40))
LISTEN 0      50                      *:2004                   *:*     users:(("java",pid=8204,fd=12))
LISTEN 0      50                      *:2005                   *:*     users:(("java",pid=8204,fd=13))
LISTEN 0      50                      *:2006                   *:*     users:(("java",pid=8204,fd=19))
LISTEN 0      50                      *:2007                   *:*     users:(("java",pid=8204,fd=17))
...

!!!! The backend internal web server runs on Port 8443 and serves only HTTPS requests. ???? You should that this process is LISTEN on all interfaces (*:8443)