NetXMS Support Forum

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

Is node_agent real executable or shell script? If it is a shell script, then executable name will be sh (or bash, ksh, etc. - whatever your shell is), so Process.Count(node_agent) will always return 0 - because it will look for executable named node_agent. You can find processes by command line using Process.CountEx, like this:

Process.CountEx(".*","^node_agent")

Please note, that Process.CountEx uses regular expressions to find matching processes.

Best regards,
Victor

Hello!

Looks like some of the system functions has misleading names. We have:

1. Actions on server (configurable under Control Panel -> Actions): it's an actions server can perform as a result of event processing. These actions can only be used in event processing policy.

2. Actions on agent (configurable in agent's configuration file via Action or ActionShellExec parameters): it's a predefined commands agent can execute upon request.

3. Object tools (configurable via Control Panel -> Object Tools): something which can be executed by operator on currently selected node in console. Object tools can be:

a) Command - local command execution (executed on same machine where netXMS console is running);
b) Action - predefined action execution on agent
c) SNMP table - get data from SNMP
d) Agent table - get data from agent
e) Open URL - open given URL in embedded browser



If you wish to run something on remote machine via agent, you should:

1. Define action on agent (using Action or ActionShellExec - if you wish to use shell functionality like output redirection, you should use ActionShellExec).

2. Depending on your need: if you wish to run something automatically, as a reaction to event, then:
2a. Define server action (Control Panel -> Actions) of type "execute action on remote agent", enter name of agent's action into "Action" field;
2b. Add your server action to event processing policy.

If you wish to be able to run something on remote machine manually, via "Tools" menu:
2a. Create new object tool (Control Panel -> Object Tools) of type "Action", enter name of agent's action into "Action" field.

Hope this helps!

Best regards,
Victor

Hi!

Unfortunately, it's not possible with standard NetXMS functionality. You should either write your own tool which will analyze list of processes on target machine and send data to NetXMS server in some way (using nxpush or nxevent for example), or use NetXMS agent instead of SNMP to monitor processes on target machine - NetXMS agent allows you to identify processes by executable name or command line.

Best regards,
Victor

Hi!

It's a bug. I'll fix it soon.

Best regards,
Victor

Hi!

"&" characters prepends character which will be used as keyboard shortcut when tool menu navigated via keyboard. For example, if you open object's context menu via "context menu" key on keyboard instead of right mouse click, you'll see characters prepend with "&" underlined, and pressing appropriate keys will select corresponding menu items.

Best regards,
Victor

Could you please post output of ps -ef and NetXMS parameter you are using to count your custom processes?

Best regards,
Victor

You should define action on agent, and than define tool to execute that action in console via Control Panel -> Object Tools.

To define custom action, add to agent's config:

Action = ActionName:command

Best regards,
Victor

Vse sobrannie dannie hranjatsja v SQL baze v tablicah idata_xx. Est' topic na anglijskom, v kotorom obsuzdalas' struktura bazi: https://www.netxms.org/forum/index.php/topic,485.0.html. Samaja prostaja vesch' - dlja togo chtobi poluchit' dannie po konkretnomu DCI naprjamuju iz bazi, nado znat'  node id i dci id, i sdelat' zapros

SELECT * FROM idata_node_id WHERE item_id=dci_id

Yes, all common performance parameters (CPU utilization, memory usage, disk space) are available for Linux. You only have to have platform subagent (libnsm_linux.so) loaded - it is done automatically by default. If you just start NetXMS agent on Linux node and don't see available parameters in DCI configuration, do configuration poll on that node - this will update server's cache.

Best regards,
Victor

Hello!

Most likely port 4700 is already in use. Try to run command


netstat -atnp | grep 4700


to see what process uses it.

Best regards,
Victor