3CX ISO Install and SNMPD monitoring to PRTG

Status
Not open for further replies.

bughatti

Forum User
Joined
Dec 2, 2019
Messages
2
Reaction score
0
Hello all, new to the forums. We are currently using the 3CX ISO install in a virtual environment. No issues so far. Today I wanted to get it setup for SNMPD monitoring with our PRTG environment. We use to have 3CX running on a windows machine and had no issues with getting PRTG to read data. We had the windows firewall turned off. The new system is using the same IP, same name, same environment location, but is now debian, since that is what is built on the ISO downloaded from 3CX. I had no issues getting snmpd installed using

Code:
#apt-get install snmpd

/etc/snmp/snmpd.conf

restart the service



snmpd.service - Simple Network Management Protocol (SNMP) Daemon.
   Loaded: loaded (/lib/systemd/system/snmpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-12-02 10:41:56 MST; 2min 36s ago
  Process: 646 ExecStartPre=/bin/mkdir -p /var/run/agentx (code=exited, status=0/SUCCESS)
 Main PID: 651 (snmpd)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/snmpd.service
           └─651 /usr/sbin/snmpd -Lsd -Lf /dev/null -u Debian-snmp -g Debian-snmp -I -smux mteTrigger mteTriggerConf -f

The problem is, it wont communicate at all with the prtg server other than ping. I made sure to add

Code:
iptables -I INPUT -j ACCEPT
iptables -I OUTPUT -j ACCEPT

The next step was to try to disable iptables with -F but that broke the server. Also doing apt-get remove iptables broke it completely, even after a reboot it would not come back up. Restored from backup and it was fine. I have read a few articles on here that say iptables is not so drastically integrated that it would prevent it from working properly, but that does not seem to be the case. What is the best route to get our 3CX server to work with PRTG.
 
Just want to update this thread, I found the fix for it. We use a standard config for all our centos machines that works out of the box. With the same config applied on debian, it does not unless I add this line

Code:
#  AGENT BEHAVIOUR
#

#  Listen for connections from the local system only
agentAddress  udp:127.0.0.1:161,udp:192.168.xxx.xxx:161
#  Listen for connections on all interfaces (both IPv4 *and* IPv6)
#agentAddress udp:161,udp6:[::1]:161
 
Glad you found the fix. Was going to say that this wasn't a 3CX issue and you were better off asking in the Debian forums but it looks like you are all set.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,934
Messages
589,821
Members
164,813
Latest member
divdigital