NetXMS Support Forum

Hi!

Can you post at least one example of your DCI configuration? And don't forget that any SNMP OID has "instance" - so, for example, system description OID shown in MIB tree as ".1.3.6.1.2.1.1.1", should be configured in DCI as ".1.3.6.1.2.1.1.1.0". You can check what instances are available by using "walk" option in MIB explorer.

Best regards,
Victor

Hi!

Sorry, I was unable to find the reason immediately, and then I forgot about that. Could you please send me results of the following walk:

nxsnmpwalk -c your_community switch_ip .1.3.6.1.2.1.4.20

Best regards,
Victor

Hi!

Most likely agent returns an error in response for those parameters. You can check it with nxget command line tool. Also, please note that physical disk parameters are working only for some devices.

Best regards,
Victor

By default it will be file name (exactly as written in <file> tag), and you will be able to change it by adding name attribute to <parser> tag. For example,
for parser

<parser>
  <file>*System</file>
  ...
</parser>

instance name will be *System, and for


<parser name="SystemLog">
  <file>*System</file>
  ...
</parser>

instance name will be SystemLog.

Best regards,
Victor

Done it. Next release will have these parameters implemented.

Best regards,
Victor

Hi!

It is because Java and legacy console threats invalid numbers differently. Legacy console tries to parse value as a number, and if it starts with a number, uses that part, so 13gb becomes 13. Java console threats all incorrect numbers as zeros, so 13gb becomes 0.

Best regards,
Victor

Hi!

Looks like it is not possible with current implementation of WMI.Query. I'll take a closer look at it in a few days - looks like this functionality can be added with simple changes in WMI subagent.

Best regards,
Victor

Hi!

Last error is ok if you do not have DRBD installed. It cannot affect agent's communications. When you do configuration poll for node in NetXMS, did you get anything in agent's log? You should see at least lines like this:

[01-Nov-2011 09:48:34] Incoming connection from 127.0.0.1

If you don't, that means that server cannot even establish TCP session with the agent, and problem is on the network layer - firewall, routing, etc.

Best regards,
Victor

Hi!

They are still not implemented. Agent shows them, but always returns an error.

Best regards,
Victor

It should automatically add node object on management server, to simplify deployment of agents. You can register agent at any time from command line:

nxagentd.exe -r server

Best regards,
Victor

I plan to release stable version till end of the year. Key points to be achieved before release of 1.2.0 is to implement all functionality of legacy console in Java console and made application stable.

Best regards,
Victor

Yes, you have to add all other nodes to trusted nodes list on  ISP_gateway. So in your case it's probably easier to disable trusted nodes checking.

Best regards,
Victor

You can use function FindNodeObject and then use attribute status of that node. For example, if you have node named ISP_gateway, your script to check if it is down may looks like following:


gw = FindNodeObject($node, "ISP_gateway");
return gw->status == 4;


This script will return true if node named ISP_gateway has status "critical". DOn't forget to add node for which this script executes to the list of trusted nodes for node ISP_gateway, or disable trusted nodes checking completely by setting server configuration variable CheckTrustedNodes to 0.

Best regards,
Victor

Hi!

No, it contains only those 3 fixes listed in change log. I plan to close 1.0.x branch completely as soon as I made 1.1.x stable (it will becomes 1.2.0 then).

Best regards,
Victor

Hi!

I've made a fix for nxalarm. Unfortunately it involves changing server code, so I create a new maintenance release 1.0.13 which includes this change as well as few other fixes.

Best regards,
Victor