NetXMS Support Forum

Hi!

Looks like server bug. What nodes as duplicated? For example, node with IP 40.16.1.2 - what it is, how it's interface list looks like? (You can send this info to [email protected] if you don't wish to disclose this information on forum).

Best regards,
Victor

Lines started with * character defines a new config section (usually subagent configuration) - and parameters allowed in each section are specific to this section. Core agent parameters should be defined in "default" section - unnamed section in the beginning of the file. Order within section is not important.

Best regards,
Victor

Thank you for excellent howto! I'll probably never manage to write so long text

Some comments and corrections:

Quote from: jdl on June 19, 2009, 05:17:54 PM
which by the way you will not find in the available list

You will, but only after next configuration poll for that node. To prevent sending request for supported parameters to agent each time you press "Select" button in console, server reads list of supported parameters during configuration poll (each hour by default) and caches it. You should either wait for next configuration poll or force immediate configuration poll from console using Poll -> Configuration menu.

Quote from: jdl on June 19, 2009, 05:17:54 PM
I did not try but I would suggest not to use any existing data collection name... Possible conflict or simply possible problem easy to avoid - play it safe and simple ;-)

In fact, you can use names of existing parameters - if you do, built-in parameter's handler will be replaced by your script. Normally, this should be avoided, but sometimes it may help - for example, if built-in implementation of certain parameter is buggy, and you are able to provide replacement script as workaround.

Best regards,
Victor

Hello!

In fact, we need completely different log readers for Windows Vista and 2008 - Microsoft changes event log API (see http://msdn.microsoft.com/en-us/library/aa964766(vs.85).aspx), and old API used by logwatch.nsm is not always compatible with new logs. I'll add support for new event log API in upcoming release.

Best regards,
Victor

Yes, it's a bug. Added it to bug tracker (#256).

Best regards,
Victor

Hello!

In theory, it should work. What you get - errors in agent's log, or just no events when records appear in log? What Windows version you are using? I have a lot of problem reports for Windows Server 2003, and there are known problems with Vista and Server 2008.

Best regards,
Victor

Idea sounds good.

What arguments should these parameters take? For file it probably should be file name and offset within file, plus string length for File.Content.String?
And what for shared mem?

Best regards,
Victor

We currently rewriting console from scratch using Eclipse platform. It should be much better than existing one, and we plan to add filtering for event log, alarms, etc.

As for documentation - unfortunately we are much better in writing code than documenting what we have done But we are working on documentation improvement, it just takes more time.

Best regards,
Victor

Looks lke agent cannot open log file for writing or connect to Windows event log service. Try to set LogFile parameter in nxagentd.conf to some writeable file, like C:\nxagentd.log and try to run it again.

Best regards,
Victor

Da, u menja bilo na porjadok men'she. Sdelaju testovij server s kuchej ob'ektov, budu testirovat' cherez GPRS.

Stranno. Ja vpolne uspeshno podkljuchalsja cherez GPRS. Vozmozno delo v kolichestve ob'ektov - skol'ko u vas ih primerno?

I hope so. I will try my best

Best regards,
Victor

It will be a long text I'll update manual with subagent description and post it on the web. I hope that 'll have time for this till end of June.

Best regards,
Victor

It's my mistake: ^node_agent is not correct regexp - ^ character means "beginning of the line", but command line in your case doesn't starts with node_agent, it starts with ./node_agent, so you should either remove leading ^ or use Process.CountEx(".*","^\\./node_agent")

Best regards,
Victor

Hi!

Auto bind/apply occurs during configuration polls. You can force configuration poll for specific node from console (via Poll -> Configuration menu), or decrease interval between configuration polls by changing server's parameter ConfigurationPollingInterval.

Attributes of node object:

name	Node name
id	Object identifier
status	Node status (0 = Normal, 1 = Warning, 2 = Minor, 3 = Major, 4 = Critical, 5 = Unknown, 6 = Unmanaged)
ipAddr	Node primary IP address (as text string, like 10.2.1.4)
isAgent	Agent presense flag: 1 if NetXMS agent present on node, 0 if not
isSNMP	SNMP support flag: 1 if SNMP is supported by node, 0 if not
isBridge	Bridge flag: 1 if node is bridge or switch, 0 if not
isRouter	IP router flag: 1 if node is Ip router (can forward IP packets), 0 if not
isPrinter	Printer flag: 1 if node detected to be a network printer, 0 if not
isCDP	CDP (Cisco Discovery Protocol) support flag: 1 node supports CDP, 0 if not
isSONMP	SONMP (SynOptics Network Management Protocol) support flag: 1 node supports SONMP, 0 if not
isLLDP	LLDP (Link Layer Discovery Protocol) support flag: 1 node supports LLDP, 0 if not
snmpVersion	SNMP version used for communication with node's SNMP agent
snmpOID	SNMP object ID
agentVersion	NetXMS agent version (as string, like 0.2.26)
platformName	Platform name, as returned by NetXMS agent (for example, windows-i386)

Best regards,
Victor