NetXMS Support Forum

Hi,

yes, it's possible. You can create two push DCIs and a script. Set this script as an action for your event, extract numbers from message text, and use PushDCIData function to push data into appropriate DCIs.

Best regards,
Victor

 It is internal diagnostic messages meaning that data collection scheduler was not able to work with DCI because it was locked by other part of the system. Most often it happens when DCI is locked because of database update. Other possible reason could be long running transformation scripts.
If you don't experience issues with data collection and don't get "thread not responding" alarms then you can ignore those messages.

Best regards,
Victor

Hi,

do you have wrong data collected or data is correct but not shown on the map?

For link status - could you please share screenshot of link properties?

Best regards,
Victor

P.S. You can also try to use "nxdbmgr migrate" to move data directly to target database without creating intermediate dump.

Hi,

it's a bug in DB manager, fixed in upcoming 2.1.2.

Best regards,
Victor

Hi,

could it be that objects are being deleted from the map and then re-added? Positions looks like default positions for newly added objects.

Best regards,
Victor

Hi,

you can use filtering script. If you are handling SYS_IF_DOWN event then parameters of the event will be following:

1) Interface object ID
2) Interface name
3) Interface IP address
4) Interface netmask
5) Interface index

They are accessible within script via $event->parameters[n]. For example, to process only events for interfaces Ge0/0 and Ge0/2:


ifName = $event->parameters[2];
return (ifName == "Ge0/0") || (ifName == "Ge0/2");


Best regards,
Victor

Hi,

you have to set two server configuration parameters:

SMSDriver to smseagle.sms
SMSDrvConfig to configuration string in key1=value1;key2=value2;... format. SMSEagle driver accepts the following parameters: host,port,login,password. For example:

host=10.10.10.2;port=1234;login=user;password=UserPass

You'll have to restart server after setting SMS driver parameters.

Then you can create SMS sending action as usual and use this action in event processing policy.

Best regards,
Victor

Hi,

that's a bug in export/import procedure. I registered it in our issue tracker: https://track.radensolutions.com/issue/NX-1330

Best regards,
Victor

Dashboard elements expected to show floating point numbers as well. What elements exactly do not show them? Can you share screenshots of dashboard element configuration and result?

Best regards,
Victor

Hi,

you can only disable configuration polls for that node completely. Could you please provide output of command

nxget -T node_ip_here System.InstalledProducts

?

Best regards,
Victor

Hi,

probably process is crashing. If you try to compile just one MIB, will it go any further?

Best regards,
Victor

Hi,

maximum number of threads in MAIN pool is hard-coded. We didn't expect that this limit can be reached...

Best regards,
Victor

Hi,

it's a bug in UI, we will fix it in next patch release.

Best regards,
Victor

Hi,

you mean you see IP in interface overview in NetXMS UI? Then you can use script to get it into your message/DCI/etc. Function GetInterfaceObject can give you Interface object, which contains list of IP addresses.

Best regards,
Victor