NetXMS Support Forum

Hi,

I have a remote node that I would like to use snmp with. This node is on a different network. Can I use the netxms agent as a snmp proxy for the node it's installed on?

I currently have this setup:

Host A = netxms server
Host B = remote server on different network

Host B's agent is configured like this:

EnableProxy = yes
EnableSNMPProxy = yes

MasterServers = HostA_Address
ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
LogFile = {syslog}
FileStore = C:\NetXMS\var
SubAgent = winperf.nsm
SubAgent = ups.nsm

RequireAuthentication = yes
SharedSecret = *******

Then on Host A in netxms Host B's node is configured with itself as the snmp proxy.

When I do a configuration poll the agent works 100% but the snmp times out. The port 4700 is forward on both Node A and Node B's routers.

SNMP is working on Node B as I can snmpwalk locally without any issues. Is there any way I can have the netxms agent be an snmp proxy for the node it's installed on?

Does any one know if this is possible?

I found if I add a second node with the IP 127.0.0.1 and setting Host B as the SNMP proxy I can access Host B's SNMP. But this isn't ideal as I now have two nodes for Host B. One for the NetXMS agent and one for SNMP.

I am using version 2.0-M2. Is this issue possibly a bug?

Hi,

SNMP proxy functionality was broken in 2.0-M2. I've fixed it in 2.0-M3. I've also change logic a bit so if node is proxy for itself it will use loopback address instead of primary IP address for SNMP requests - this can help avoid possible firewall problems and secure SNMP access to node by allowing only requests via loopback.

Best regards,
Victor

Quote from: Victor Kirhenshtein on April 07, 2015, 08:59:49 PM
Hi,

SNMP proxy functionality was broken in 2.0-M2. I've fixed it in 2.0-M3. I've also change logic a bit so if node is proxy for itself it will use loopback address instead of primary IP address for SNMP requests - this can help avoid possible firewall problems and secure SNMP access to node by allowing only requests via loopback.

Best regards,
Victor

Hi Victor, Thank you for fixing this issue. SNMP in 2.0-M3 works great.