NetXMS Support Forum

Hi!

It seems that you don't do real modification. Creating NXCObjectModificationData is not enough - after populating it you should call session.modifyObject with your NXCObjectModificationData object as argument. Should be something like

session.modifyObject(modificatore)

in your case.

Best regards,
Victor

Hi!

I see few options here. The best one is to use address filters in network discovery, if your network scheme allows this. Device address validated before trying to access device using SNMP, so this should help. Another possible option is to manually add these devices to NetXMS (or let them being discovered) and then disable SNMP access (in node properties, check "Disable SNMP for all polls" on "Polling" page), or just set them to "unmanaged" state.

Best regards,
Victor

Hi!

It should be in 1.2.8.

Best regards,
Victor

Hi!

I've seen similar behavior on a site I'm supporting. In 1.2.7 I've added additional locks to ensure database integrity. Looks like this feature causing excessive internal locks under some circumstances. I'll make it configurable and turned off by default in 1.2.8.

Best regards,
Victor

There was the problem with housekeeper process not clearing SNMP trap log. But I have fixed this in 1.2.6 or 1.2.7. What NetXMS version you are running?

Best regards,
Victor

Hi!

Core dump could be really helpful. Please send them to [email protected], and I'll take a look at it.

Best regards,
Victor

Hi!

There is the cache for changes in objects, but normally changes should be saved to database within one minute. How many objects was created during network discovery? I already have some reports with server being unresponsive after big number of changes in objects. Here may be the same problem.
Also, try to run database check (nxdbmgr check) - will it report any errors?

Best regards,
Victor

You forgot double quotes around OID passed to aboveZero function, so script ends up with syntax error. And you can shorten the script to just


return ($node->snmpOID == ".1.3.6.1.4.1.25506.1.1") && aboveZero(".1.3.6.1.4.1.25506.2.6.1.1.1.1.6.47");


function aboveZero will be called only if first condition is true, because NXSL uses short-circuit expression evaluation (http://en.wikipedia.org/wiki/Short-circuit_evaluation).

Best regards,
Victor

I agree that this is a workaround, not a full solution. I've added a feature request for built-in DCI data aggregation - should not be that hard to implement.

There are housekeeper job that starts at fixed intervals (controlled by server configuration parameter "HouseKeepingInterval"). It deletes all data that is older then retention time configured for DCI.

Best regards,
Victor

Quote from: sperlm on June 11, 2013, 07:00:36 PM
The "null" parameter in findObjectNode was not clear to me (but it works with it too).

It's a reference to already known object. Here is the explanation: http://wiki.netxms.org/wiki/SG:Security_Issues.

Best regards,
Victor

Hi!

Strange, this issue supposed to be fixed already. I'll check. Do you have any background set on map?

You can set default icon type in map object properties, on "Map Options" page. This is only related to predefined maps.

Best regards,
Victor

Node name is a string, not an object reference. If you want to find node object by name, you could use FindObject or FindNodeObject function, like this:


node = FindNodeObject(null, $1);
println "Node ID: " node->id;


Also check this script example: http://wiki.netxms.org/wiki/Script_Example:_Read_SNMP_Value_From_Node

Best regards,
Victor

Hi!

Attached is updated version of SYMBOL-WS driver. It should detect RFS6000 as supported device. I'll try to implement other changes we have discussed in 1.2.8 release (radio interfaces as separate objects and correct handling of down APs).

Best regards,
Victor

Quote from: sperlm on June 07, 2013, 01:49:48 PM
Thanks for the reply, filters work exactly as I need now.

Few clarifications:

a)
In my previous question 4) I was referring to the wiki information under Templates section "Macros in template items"

QuoteYou can use various macros in name, description, and instance fields of template DCI.

namely: script:name - String returned by script name. Script should be stored in script library (accessible via Configuration -> Script Library). Inside the script, you can access current node's properties via $node variable.

To put the question short - where exactly it can be used?
(as the wiki information does not make sense to me - DCI form has no "name", macro {instance} can be used in the Parameter on the other hand)

Macros in templates expands when template being applied to node. It is useful when you want to put some node-specific information during template apply (node IP address for example) into parameter name or description.  "name" was the old universal name for what you now see as "Parameter" for agent DCI, "OID" for SNMP DCI, etc. It is still used in some places.

Quote from: sperlm on June 07, 2013, 01:49:48 PM
b)
Performance tab - a little insight on this would be appreciated.
(did not find any on wiki or forums and this looks like it can solve my problem with viewing the collected data, namely the automated ones)

Performance tab shows line charts with last hour data for all DCIs marked to be shown on performance tab. You can enable DCI for performance tab in DCI properties, on "Performance Tab" page.

Quote from: sperlm on June 07, 2013, 01:49:48 PM
b)
If dci and node parameters are global, does it mean we can use class reference attributes like $node->snmpOID anywhere?
I am already filtering nodes for templates with this functionality so I assume it is possible.

Yes, all scripts related to nodes have $node variable set, and all scripts related to DCIs have $dci variable set.

Quote from: sperlm on June 07, 2013, 01:49:48 PM
c)
I also tried to use the same script functions from instance discovery in automatic apply rules for templates but could get results only with direct scripts, when I try to do the same thing with use/script it does nothing (or I was not able to test it properly).

There are no difference between automatic apply rule script an any other script regarding library use. Most likely you've make some mistake. Please post your scripts here.

Best regards,
Victor

Hi!

This feature seems interesting. I have added it to our issue tracker as feature request (https://www.radensolutions.com/chiliproject/issues/290). As for accessing AD from NetXMS server, on UNIX/Linux we probably can use LDAP.
Also, it is possible now to create Python script for nxshell (http://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations) which will use LDAP to access AD and NetXMS API to create appropriate objects under infrastructure services tree. This will not be simple script though.

Best regards,
Victor