What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

PRTG and SNMP monitoring: same device, two SNMP ports

Votes:

0

Hi all,

I am monitoring hardware parameters of an Linux server (acting as proxy server) using its SNMP service on default port 161. The proxy software is SQUID 2.6, and it has its own SNMP subsystem on port 3401.

This forces me to have the same server declared as two distinct devices, since I cannot add a sensor changing its port (it defaults to parent's device port). Would not be beautiful extend the inheritance mechanism as an option even on SNMP port on same device sensors ?

TIA

Claudio Duffini

proxy prtg snmp wishlist

Created on Apr 15, 2010 5:09:53 PM

Last change on Apr 16, 2010 8:01:40 AM by Daniel Zobel [Product Manager]



Best Answer

Accepted Answer

Votes:

0

While not supported by PRTG (would require two distinct devices), please check the guide by Markus below:

@Markus - Thank you for the contribution!


Best Regards,
Luciano Lingnau [Paessler Support]

Created on Oct 24, 2016 5:33:44 AM by Luciano Lingnau [Paessler]

Last change on Oct 24, 2016 5:34:45 AM by Luciano Lingnau [Paessler]



7 Replies

Votes:

0

We will add it to the wish list, but it is unlikely that we will see this implemented any time soon.

Created on Apr 16, 2010 4:39:54 AM by Aurelio Lombardi [Paessler Support]

Last change on Apr 16, 2010 8:01:20 AM by Daniel Zobel [Product Manager]



Votes:

0

Has this feature been released? Thanks!

Created on Feb 27, 2015 2:54:32 PM



Votes:

0

No, sorry.

The request for this is rather low, so it is unlikely that we will implement this any time soon.

Created on Mar 2, 2015 7:57:11 AM by Aurelio Lombardi [Paessler Support]



Votes:

0

I'm currently testing the product. Working to add important sensors to monitor network trafic, found that there is no sensor for squid (one of the best free proxy abiable). The produc is excelent, and just in a few days , found some configurations problem on the network, but is determinating for me to have a Proxy sensor. How could i help to have it ? Current version of squid is 3. Thanks

Created on May 18, 2015 5:32:13 PM



Votes:

0

@pquzman: As PRTG allows the execution of own scripts and exe files you might write your own sensor and execute the using the EXE/Script (Advanced) sensors of PRTG.
Best regards

Created on May 22, 2015 7:36:08 AM by Konstantin Wolff [Paessler Support]



Votes:

1

HowTo: Configure linux net-smtp to proxy all other snmp calls from custom smtp-ports like squid, apache, etc.

Here is my prtg-monitoring solution for squid-proxy server:

1.) Configure Squid for snmp access

Modify squid.conf (usually /etc/squid3/squid3.conf) and replace all your_ variables with your own values acl snmp_poll snmp_community your_community_string snmp_port 3401 snmp_access allow snmp_poll localhost

Restart squid service

2.) Modify Linux Net-SMNP config

Change net-snmp daemon config to proxy all squid snmp calls (usually /etc/snmp/snmpd.conf)
Add the following line to the end of your snmpd.conf (remember to change all your_ variables with your own value(s))

proxy -v 2c -c your_community_string localhost:3401 .1.3.6.1.4.1.3495.1

Restart net-snmpd

Now you should be able to receive all the squids snmp output via standard snmp call on port 161 while using PRTGs standard SNMP sensors. No extra devices, no custom scripting, no workarounds. Clean and easy.

3.) Test: root@squid-proxy:~# snmpwalk -v 2c -c your_community_string localhost .1.3.6.1.4.1.3495.1

Sample output:

iso.3.6.1.4.1.3495.1.1.1.0 = INTEGER: 240
iso.3.6.1.4.1.3495.1.1.2.0 = INTEGER: 3774872
iso.3.6.1.4.1.3495.1.1.3.0 = Timeticks: (156790) 0:26:07.90
iso.3.6.1.4.1.3495.1.2.1.0 = STRING: "proxy-admin"
iso.3.6.1.4.1.3495.1.2.2.0 = STRING: "squid"
iso.3.6.1.4.1.3495.1.2.3.0 = STRING: "3.3.8"
iso.3.6.1.4.1.3495.1.2.4.0 = STRING: "ALL,1"
iso.3.6.1.4.1.3495.1.2.5.1.0 = INTEGER: 512
iso.3.6.1.4.1.3495.1.2.5.2.0 = INTEGER: 4096
iso.3.6.1.4.1.3495.1.2.5.3.0 = INTEGER: 95
iso.3.6.1.4.1.3495.1.2.5.4.0 = INTEGER: 90
...

4.) Additional resources and useful stuff:

  • squid-mib path (Ubuntu 14.04): /usr/share/squid3/mib.txt

Happy squid monitoring!
- Markus

Created on Oct 23, 2016 1:40:54 PM

Last change on Oct 24, 2016 5:32:14 AM by Luciano Lingnau [Paessler]



Accepted Answer

Votes:

0

While not supported by PRTG (would require two distinct devices), please check the guide by Markus below:

@Markus - Thank you for the contribution!


Best Regards,
Luciano Lingnau [Paessler Support]

Created on Oct 24, 2016 5:33:44 AM by Luciano Lingnau [Paessler]

Last change on Oct 24, 2016 5:34:45 AM by Luciano Lingnau [Paessler]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.