<![CDATA[syslog message originating from nat network]]>Hey all

i need some tips on handling syslog messages originating from behind a nat router.

the source and host in the messages takes the routers info, but the messages contains <time><device><log event>

how can i handle these messages, so they will end up on the correct devices (i have an agent running snmp off the devices)?

i cant seem to figure out how to use the parser for this...

]]>https://forum.netxms.org/topic/4874/syslog-message-originating-from-nat-networkRSS for NodeFri, 13 Nov 2026 14:49:50 GMTTue, 17 Jan 2017 20:45:46 GMT60<![CDATA[Reply to syslog message originating from nat network on Thu, 23 Feb 2017 17:32:11 GMT]]>Then NetXMS server cannot match it to correct device - there are just no enough information. You can setup syslog proxy on agent behind NAT so it will receive syslog messages from original addresses and forward to NetXMS server.

Best regards,
Victor

]]>https://forum.netxms.org/post/21881https://forum.netxms.org/post/21881Thu, 23 Feb 2017 17:32:11 GMT<![CDATA[Reply to syslog message originating from nat network on Fri, 10 Feb 2017 13:50:34 GMT]]>here is the problem;

the string looks like this, without the hostname set...

[6d:06h:02m:45s] NEXANS-00C029260F62:Port Link Change: Link-State=100FDX, Portnumber=1, Description=TP-1, Name=<none>

first a timestamp containting the running time, then the hostname, and then the syslog message

]]>https://forum.netxms.org/post/21819https://forum.netxms.org/post/21819Fri, 10 Feb 2017 13:50:34 GMT<![CDATA[Reply to syslog message originating from nat network on Tue, 17 Jan 2017 22:20:08 GMT]]>Hi,

if syslog message contains correct device name and you have that device under same name in NetXMS, try to set server configuration parameter SyslogNodeMatchingPolicy to 1 (which means "host name then IP") and restart server.

Best regards,
Victor

]]>https://forum.netxms.org/post/21672https://forum.netxms.org/post/21672Tue, 17 Jan 2017 22:20:08 GMT