NetXMS Support Forum

Hi!

Yes, that was the intention. Minimal package contains only NetXMS itself.

Best regards,
Victor

Hi all!

Finally, NetXMS version 1.2.7 is out! We had some unexpected delays with this release, but now we are back on track and I hope that next versions will come out faster. Changes since previous release are following:

- Simplified configuration of DCIs based on Windows performance counters
- Basic software inventory
- Network discovery improved
- Status of zone's proxy node now used in "node down" event correlation
- Configurable default DCI retention time and polling interval
- New NXSL functions: CreateNode, GetSumDCIValue
- New NXSL operator @ (safe get object's attribute)
- New MIBs added: ASTARO-MIB, CPQHOST-MIB, CPQPOWER-MIB
- Special support for wireless switches
- Driver for Motorola/Symbol wireless switches
- Fixed bugs in template export/import
- Database manager: Fixed bugs in database export
- New parameters for Windows Security Center provided by WMI subagent:
   System.AntiSpywareProduct.Active
   System.AntiSpywareProduct.DisplayName
   System.AntiSpywareProduct.UpToDate
   System.AntiVirusProduct.Active
   System.AntiVirusProduct.DisplayName
   System.AntiVirusProduct.UpToDate
   System.FirewallProduct.Active
   System.FirewallProduct.DisplayName
   System.FirewallProduct.UpToDate
- Management console:
   - "Export to CSV" option added to most tabular data views
   - Auto login option for web console
   - Last values of selected DCIs can be shown in object tooltips
     on network maps
- Fixed issues: #86, #199, #242, #246, #249, #250, #251, #256, #260, #268, #275

Best regards,
Victor

Hi!

Most information located in tables nodes, interfaces, and object_properties. You can consult data dictionary for detailed information about these tables: https://www.netxms.org/documentation/NetXMS_data_dictionary.pdf.

Best regards,
Victor

Quote from: jamesof on May 09, 2013, 06:20:53 PM

Quotewhat do you mean by security policy on agent?

agent check manager have right to do action.

There are 3 level of access for an agent. Depending on how server's IP address listen in nxagentd.conf, it will have different access level. If server listed in:

1. MasterServers - full access
2. ControlServers - can read data and execute predefined actions, but cannot change config nor install policies.
3. Servers - read only access

Quote from: jamesof on May 09, 2013, 06:20:53 PM
and another question . can we have any accounting feature? which user how many usage which app ... for any session in remote device that running agent .

No, we don't have functionality like that.

Best regards,
Victor

Quote from: jamesof on May 08, 2013, 06:41:55 PM
is it possible to return generated output. i remember you said it is not possible (around 2010) . is this feature added to netxms?

still not possible

Quote from: jamesof on May 08, 2013, 06:41:55 PM
can i set snmp oid with agent?

Only by calling external tools. You can copy nxsnmpset to agent and configure action which will call it.

Quote from: jamesof on May 08, 2013, 06:41:55 PM
can i define security policies on agent ?

what do you mean by security policy on agent?

Best regards,
Victor

Hi!

You can include custom attribute in mail and/or alarm message by using %{name} macro. For example, if you have custom attribute named additionalInfo, you can use %{additionalInfo} to insert value of this attribute into message text.

Inserting comments into message is a bit more complicated - you have to create script in script library, like this:


return $node->comments;


and then call it using %[script_name] macro.

Best regards,
Victor

Hi!

There are two problems in your config:

1. You put Action keyword in wrong section. It should be like this:

ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
LogFile = {syslog}
FileStore = C:\NetXMS\var
SubAgent = ecs.nsm
SubAgent = ping.nsm
SubAgent = logwatch.nsm
SubAgent = portcheck.nsm
SubAgent = winperf.nsm
Action= dir:cmd.exe /c "dir c:\ > c:\1.txt"
SubAgent = wmi.nsm
SubAgent = ups.nsm

2. On server side, you should only put name of the action configured on agent in "agent action" field. It will be just dir in your case.

Best regards,
Victor

Конфигурацией такого не сделать, только изменением консоли. Если Java/Eclipse программирование не пугает, то расскажу в деталях как это можно сделать.
Вообще в планах уже довольно давно стоят "активные карты", как мы их называем - возможность добавлять текстовую информацию и графики на карты. Но пока не успеваем сделать.

From that message:

[03-May-2013 17:13:44.671] Unable to bind socket: Only one usage of each socket address (protocol/network address/port) is normally permitted.

it seems that you either trying to run agent twice, or that some other process already listen on port 4700. Please check that there are no other nxagentd processes, and then run agent in debug mode again.

Best regards,
Victor

Hi!

There are lot of possible solutions, depending on what tools are available and what level of access you have to these devices:

1. It is not necessary to run agent under root user to get most of the information, especially on Linux. If you can run agent as non-root user, that could be a solution.

2. If you can put additional binaries to the device, you can use shell scripts and nxpush command line tool to push data to management server.

3. You can create scripts on management server (or any other system) to query data from the device and use nxpush or nxapush to push data to management server.

I agree that having "exec" type of DCI origin will simplify configuration in case #3. I have added it as feature request for 1.2.8 release.

Best regards,
Victor

Моя рекомендация вообщем-то такая-же: использовать IP адрес туннеля как primary host name. Странно что snmpget принимает ответы с другого IP - технически понятно как это сделать, но это поперек всех стандартов. Если IP адрес туннеля динамический, то можно использовать DNS имя.

Если все настроено правильно, то разные часовые пояса влиять на работу системы не должны. Внутри используется только время в UTC (если быть точным, то UNIX time: http://ru.wikipedia.org/wiki/UNIX-%D0%B2%D1%80%D0%B5%D0%BC%D1%8F), часовой пояс используется только при отображении информации. Если настройки часового пояса правильные, то UTC время везде должно быть одинаковым. Проблемы возникают обычно, если неправильно выставлен часовой пояс, и время ставят по локальному времени - визуально выглядит правильным, но время в UTC оказываетя со сдвигом.

Hi!

NAT may be an issue. Check that incoming connection from server is from same IP address that is listed in MasterServers parameter in agent configuration file. You can also try to run agent on remote node from console in debug mode, like this:

nxagentd -D9

and see if it rejects connections from server for some reason.

Best regards,
Victor

Hi!

Thanks for reporting, it's fixed now.

Best regards,
Victor

Unfortunately there are no ready to use documentation on communication protocol. I suggest to read server source code. All command handlers are located in file src/server/core/session.cpp. Client source code could help as well. Feel free to ask if you have any more specific question.

Best regards,
Victor