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:
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.
rootNow you can start the MNC service as user satnms and check if its running.
satnmssatnms-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:
sudo systemctl start satnmssudo systemctl stop satnmsCheck if the MNC service start successfully:
systemctl status satnmssatnms@satnms7-dev:~$ systemctl status satnms
● satnms.service - sat-nms MNC service
Loaded: loaded (/etc/systemd/system/satnms.service; enabled; preset: enabled)
Active: active (running) since Thu 2026-04-23 13:57:55 UTC; 3 days ago
Main PID: 461 (satnms-start)
Tasks: 34 (limit: 2298)
Memory: 118.2M
CPU: 41min 43.795s
CGroup: /system.slice/satnms.service
├─461 /bin/bash /home/satnms/satnms-start
├─491 /bin/bash /home/satnms/satnms-start
└─532 java -cp "satnms.jar:/home/satnms/jars/*" -mx512m -Djava.security.egd=file:/dev/./urandom -Dhostname=EDB-BCKP satnms3.vl>
Apr 23 13:58:00 satnms7-dev[771]: satnms : PWD=/home/satnms ; USER=root ; COMMAND=/usr/sbin/dmidecode -t baseboard
Apr 23 13:58:00 satnms7-dev[771]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Apr 23 13:58:00 satnms7-dev[771]: pam_unix(sudo:session): session closed for user root
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 2015A 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-statAdditionally you can lookup the process ID (PID) of the MNC 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 -eNow 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))
...