<![CDATA[Strange behavior of method in API]]>I made a script in python to populate a network, in which I condigure the name, IP, snmp port, snmp community and so.

In class org.netxms.client.NXCObjectModificationData, when using the method void setSnmpVersion(int snmpVersion), I noticed the following:

  • If I pass number 1 as a paramether to the method, it configures as version 2c;
  • If I pass number 2 as a paramether to the method, it configures as version 1.

Is this supposed to happen? Because of that, in my script I wrote this to configure correctly:

    if objectSnmpVersion == "V1":
        objectSnmpVersion = 2
    elif objectSnmpVersion == "V2C":
        objectSnmpVersion = 1
    elif objectSnmpVersion == "V3":
        objectSnmpVersion = 3
    md.setSnmpVersion(objectSnmpVersion)
        
but didnt' like it...  ???

]]>https://forum.netxms.org/topic/3768/strange-behavior-of-method-in-apiRSS for NodeFri, 13 Nov 2026 08:53:38 GMTMon, 11 May 2015 11:48:53 GMT60<![CDATA[Reply to Strange behavior of method in API on Thu, 14 May 2015 11:45:23 GMT]]>In this situation yes, because we won't monitore this nodes using SNMP, but I made this way so the script can be reused to populate the rest of the nodes!

Thank you,
Jhúlia Graziella

]]>https://forum.netxms.org/post/16868https://forum.netxms.org/post/16868Thu, 14 May 2015 11:45:23 GMT<![CDATA[Reply to Strange behavior of method in API on Wed, 13 May 2015 13:29:39 GMT]]>Btw, is it intended to create all nodes with SNMP access disabled?

Best regards,
Victor

]]>https://forum.netxms.org/post/16857https://forum.netxms.org/post/16857Wed, 13 May 2015 13:29:39 GMT<![CDATA[Reply to Strange behavior of method in API on Wed, 13 May 2015 13:25:42 GMT]]>@victor said in Strange behavior of method in API:

Hi!

SNMP version constants are a bit illogical (for historical reasons). They are following:

0 = SNMP v1
1 = SNMP v2
3 = SNMP v3

2 is an invalid value, so it falls back to v1 (as any invalid value will do). You can use constants from AbstractNode class:

AbstractNode.SNMP_VERSION_1, AbstractNode.SNMP_VERSION_2C, AbstractNode.SNMP_VERSION_3

Best regards,
Victor

Oh, okay! Thank you very much! 😄 I'll correct it.

]]>https://forum.netxms.org/post/16856https://forum.netxms.org/post/16856Wed, 13 May 2015 13:25:42 GMT<![CDATA[Reply to Strange behavior of method in API on Wed, 13 May 2015 13:24:55 GMT]]>I have attached the script here.
I'm sorry, but all my comments are written in portuguese so here goes a little explanation about the code:

In the beggining of the script it's defined the name of the container in which the nodes will be created. It checks if there already is a container with that name and if there isn't we create it. In any case we get the ID of the container of that name.
Then, it opens an archive named input.csv with reading option and mark its delimiter as ';'.
This archive has the following format:

NAMEORIP;10.106.7.252;COMMUNITY;0rqu1dea;SNMPPORT;161;SNMPVERSION;V2C;SEEDNAME;a-rg-fcc-arq-001-araraquara;ACCESSMODE;ICMPSNMP;ADDRESSFORMAT;AUTOADDRESS;
NAMEORIP;10.11.133.170;COMMUNITY;0rqu1dea;SNMPPORT;161;SNMPVERSION;V2C;SEEDNAME;a-rg-fcc-ula-085-cadministrativo;ACCESSMODE;ICMPSNMP;ADDRESSFORMAT;AUTOADDRESS;
NAMEORIP;10.224.0.110;SNMPPORT;161;SNMPVERSION;V2C;SEEDNAME;a-rg-fcc-ula-301-image-01;ACCESSMODE;ICMPONLY;ADDRESSFORMAT;AUTOADDRESS;;;
NAMEORIP;10.5.1.132;COMMUNITY;0rqu1dea;SNMPPORT;161;SNMPVERSION;V2C;SEEDNAME;a-rg-fcc-bet-511-guaruja;ACCESSMODE;ICMPSNMP;ADDRESSFORMAT;AUTOADDRESS;
NAMEORIP;10.5.1.134;SNMPPORT;161;SNMPVERSION;V2C;SEEDNAME;a-rg-fcc-bhe-010-liberdade;ACCESSMODE;ICMPONLY;ADDRESSFORMAT;AUTOADDRESS;;;

Above there are some lines of the archive. It's in this format because this is how it was exported by our running network management system (yeah I know it looks ugly!). As you can see, not all collumns are filled for all lines, and the names in upercase letters represent what parameter comes next, so we "treat" this in the if-chain by reading 2 collumns at a time and checking what that collumn represents. We save the data collected in variables.

Then it's the creation part:
First it checks if an object with that name already exists. If so, it doesn't create it. If not, it calls the methods of classes NXCObjectCreationData and NXCObjectModificationData and create it with the parameters got from the archive.

Sorry about my not-so-good english, hope I made it clear!  ;D
If you have any questions about anything feel free to ask me, I'll be glad to explain!

Regards,

Jhúlia Graziella

popular-formatoSmarts.py

]]>https://forum.netxms.org/post/16854https://forum.netxms.org/post/16854Wed, 13 May 2015 13:24:55 GMT<![CDATA[Reply to Strange behavior of method in API on Wed, 13 May 2015 13:12:11 GMT]]>Hi!

SNMP version constants are a bit illogical (for historical reasons). They are following:

0 = SNMP v1
1 = SNMP v2
3 = SNMP v3

2 is an invalid value, so it falls back to v1 (as any invalid value will do). You can use constants from AbstractNode class:

AbstractNode.SNMP_VERSION_1, AbstractNode.SNMP_VERSION_2C, AbstractNode.SNMP_VERSION_3

Best regards,
Victor

]]>https://forum.netxms.org/post/16852https://forum.netxms.org/post/16852Wed, 13 May 2015 13:12:11 GMT<![CDATA[Reply to Strange behavior of method in API on Wed, 13 May 2015 08:48:48 GMT]]>can you show a full version of your script?

]]>https://forum.netxms.org/post/16849https://forum.netxms.org/post/16849Wed, 13 May 2015 08:48:48 GMT