Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Dani@M3T

#316
General Support / Re: Syslog from source <unknown>
July 15, 2014, 12:17:54 PM
Victor

Can you realize this change in V1.2.15?
#317
General Support / Re: Syslog from source <unknown>
July 09, 2014, 09:52:41 PM
Hi Victor

Thanks a lot for your help. That would be very good for me. But I will report this to ZyXEL as well. But I don't know with success or not ;-)
Should I stop the logs from this device for the moment. Can you integrate this change in V1.2.15?


Dani
#318
General Support / Re: Syslog from source <unknown>
July 09, 2014, 01:39:54 PM
Hi Victor

That behaviour seems to be new. I didn't had this on older ZyXEL devices. I have attached a tcpdump.

Thanks
Dani
#319
General Support / Re: Syslog from source <unknown>
July 09, 2014, 09:30:46 AM
Hi Victor

If the 'host' field is the part to map I see the problem. I have attached two printscreens. The old node name was 'fw1' the new name is 'gw1'. I can see the old device has 'fw1' in the host part, the new one has in the host part '2014' and the name is in 'tag'. Hmm looks like a bug from ZyXEL. I can choose 'CEF/Syslog' or 'VRPT/Syslog' format on the device but that makes no difference in the 'host'- and 'tag'-fields.
#320
General Support / Syslog from source <unknown>
July 07, 2014, 07:47:04 PM
We just changed our internet gateway (same manufacturer but a bigger device model). In NetXMS I left the existing node, changed the node name and started configuration-, interface-name- and topology poll. All DCIs are still ok.
But the syslog messages from the new gateway arrive at the NetXMS-syslog-server with source <unknown>. The new gateway has the same IP address as the old. Maybe the gateway uses a wrong source interface to send the syslog messages. Is there an easy way to see the source IP address of the syslog messages in NetXMS server? As long as I know NetXMS is mapping incoming syslog messages by source IP adress to existing nodes. Right? On the other side SNMP Traps are working, source node is ok there. Or does anybody has an idea what could be wrong? Thank's in advance!

Addition:
I checked the source IP address of the syslog packets with wireshark. All syslog packets arrives with the primary IP address of this node. So the cause must be something else.
#321
Ok, everything clear. Thank's Alex
#322
Has anybody an idea, it is a problem in our database or a known bug?
#323
I can confirm that. When I use "%n" in server command it's expanded to nodes name. Thank's
#324
General Support / Re: ConditionStatus()
June 26, 2014, 07:09:27 PM
Ok, thank's. The workaround with legacy console is absolutely ok.
#325
General Support / ConditionStatus()
June 26, 2014, 10:08:40 AM
I tried to use the internal DCI ConditionStatus() on a node to read the status of a condition. As I read in the forum the node must be in the trusted node list of the condition. But there is no trusted node list in condition (V1.2.14).
And what is the argument of ConditionStatus()? The condition "name" or the "Object ID"?
#326
I also get "OBJECT_NAME" in a server script using %OBJECT_NAME% in the Object Tools.

Update:
I saw this in admin guide:
QuoteAction, file download, local command, and URL tool types allows macro substitution.
#327
Hi Victor

That fixed it, thank you
#328
thank you Victor
#329
Yes I always build the server on Linux x64 from sources. A patch would be very nice.

Thanks for your very good forum support!
#330
When we want to change object tools in our NetXMS installation (V1.2.14) we get database errors like:

[ERROR] SQL query failed (Query = "DELETE FROM object_tools_acl WHERE tool_id=?"): 08P01 ERROR:  bind message supplies 9 parameters, but prepared statement "netxms_stmt_0x7f51d4056c40_1403626097" requires 1


What can we do to fix it? Thanks in advance