NetXMS Support Forum

Hi!

It's possible only with external tools. You can define external parameter on any agent like this:

ExternalParameter = DNS.Check(*):/usr/bin/dig +noall +short @$1 $2 A | grep $3 | wc -l

You'll get new agant parameter DNS.Check, which accepts 3 arguments: DNS server address, DNS name to test, expected IP address. It will return 1 for successful test and 0 for failed. For example, in my network I can call it like

DNS.Check(172.30.30.1,www.netxms.org,5.9.19.37)

to check that my local DNS server at 172.30.30.1 resolves DNS name www.netxms.org to correct IP address (5.9.19.37).

Best regards,
Victor

Btw, how many nodes you are monitoring? And what kind of nodes (more switches/routers or servers)? Could it be that you have network devices with very large MAC tables or routing tables?

Best regards,
Victor

Hi!

When node will be shown as down again, try to run status poll from console and post it's output. Also, check log of agents running as proxy - they could exceed maximum number of allowed connections, so you may need to increase it.

Best regards,
Victor

Hi!

You actually thinking in right direction - you can use SNMPGet function to read value of each instance and determine to include it or not. Below is a working example of such approach. I use OID .1.3.6.1.2.1.2.2.1.16 (ifOutOctets) as a base. I use

Port traffic: {instance}

as description and

.1.3.6.1.2.1.2.2.1.16.{instance}

as parameter name. Correct parameter name is important, because {instance} will be the part after base OID you configure on instance discovery page, not the full OID.

Then, on instance discovery page, I set discovery method to "SNMP Walk - OIDs", set base OID to .1.3.6.1.2.1.2.2.1.16, and use the following filtering script:

snmp = CreateSNMPTransport($node);
return SNMPGetValue(snmp, ".1.3.6.1.2.1.2.2.1.16." . $1) != 0;

Now just close data collection configuration for the node and run configuration poll. You should get DCIs for all OIDs with non-zero value.

Best regards,
Victor

Поменять приоритет события из скрипта нельзя. Что можно сделать - генерировать новые события функцией PostEvent, и из них уже делать алармы. Где-то на форуме уже был пример использования PostEvent.

That's strange indeed. I'm not sure if this real source of you problem, but we should try Attached is updated pgsql.ddr. It will also log SQL state code in error message, so if error will repeat, please send me new error messages.

Best regards,
Victor

Hi!

It was designed that way - we had a request for exactly two-state status indicator. I can add an option to switch it to usual status color mode.

Best regards,
Victor

Just send them to [email protected], preferably with some comments on where to look for information about VLANs and physical ports.

Best regards,
Victor

Hi!

I found explanation for this problem: http://postgresql.1045698.n5.nabble.com/BUG-2305-quot-No-bufferspace-available-quot-error-on-large-insert-td2120136.html. Looks like the only way to fix it is to add check for this error in POstgreSQL driver on NetXMS side and do sleep and retry to allow DB server to process data it already have. I'll make a patch and post updated driver here.

Best regards,
Victor

Hi!

I see that snmptester uses SNMP version 1. Is it possible that device does not support SNMP version 2c? Can you try to run nxsnmpget  with -v1 option?

Best regards,
Victor

Don't have time to look into it in details yet. Hopefully will be able to work on it this week. I have similar report in Russian forum, so you are not alone with this problem

Best regards,
Victor

Hi!

It's a bug.

Best regards,
Victor

Hi!

Looks like broken database. Can you try to stop the server and run database check (with command nxdbmgr check)?

Best regards,
Victor

Hi!

NetXMS server has "network device drivers" which handles all vendor/device specifics. As there are no standard MIBs for reading physical port information, "Ports" tab is blank for devices without drivers. It also can affect VLAN info display. If you can point me to appropriate MIBs for AlliedTelesis switches, I can create a driver and include it into next release.

Best regards,
Victor

Hi!

Do you see SNMP in node capabilities? I see that your node using non-standard port - did you set it correctly in communication properties for the node? If you do configuration poll manually, what messages you get about SNMP support?

Best regards,
Victor