NetXMS Support Forum

Hi!

NetXMS Server should detect new interfaces at configuration polls. By default configuration polling interval set to 1 hour. If new interfaces not detected after that, try to run configuration poll manually, and check output for possible errors.

Best regards,
Victor

File is correct. Check that you really download updated version: MD5 sum should be 72c21f88b19b74e5524b98ec8716828f. Maybe you are using proxy and got cached version for some reason?

Best regards,
Victor

Check that you have correct agent version. Run nxagentd.exe -v, you should get this:

NetXMS Core Agent Version 1.2.10 Build 7856

If build number is different, then you have to download correct version from web site. Also, maybe you'll need to do uninstall and then install from correct package.

Best regards,
Victor

Hi!

There is a separate section in manual dedicated to data collection: https://www.netxms.org/documentation/adminguide/data-collection.html. Please read it first and feel free to ask any specific questions not covered in the manual.

Best regards,
Victor

Hi!

There was a bug in the installer which sets command line for service in the registry incorrectly. I've uploaded corrected version of the installer to the website. File name is the same, but agent should show build number 7856 in version information.

Best regards,
Victor

Нашел баг - инсталлер 1.2.10 прописывает неправильную командную строку для сервиса в registry. Выложил обновленный инсталлер на веб (имя файла не изменилось, но агент должен показывать билд 7856 в версии).

В версии 1.2.10 добавил две новые вкладки для подсетей - список узлов и карта адресов. Занятыми адресами считаются те, для которых есть обьект в NetXMS, т.е. корректные данные будут только при включенном network discovery.

Попробуйте агента версии 1.2.10 - я исправил обработку /proc/drbd

Hi!

Bug should be fixed. We have uploaded updated installers, Please download updated version and reinstall.

Best regards,
Victor

Hi all!

NetXMS version 1.2.10 is released. Changes from previous release:

- Event processing policy rules can be exported and imported
- NXSL:
   - Implemented post-increment and post-decrement for array elements
   - New functions: GetDCIValues
- Server's ICMP ping timeout can be configured
- DB/2 monitoring subagent
- DB/2 supported as backend database
- Table DCIs can be used in condition objects
- nxapush can push data on behalf of other nodes
- Transformation script can be run on aggregated DCIs
- Unknown SNMP trap sources can be automatically added as nodes
- Syslog processing optinmized for performance
- Default shared secret for agents can be configured
- Driver for Ping3 devices
- Driver for Allied Telesis switches
- Agent installer on Windows automatically adds firewall exception
- Database migration tool
- Additional parameters in Solaris platform sub-agent
- Management console:
   - New command line option -fullscreen
   - Option to draw borders around each value in "gauge" dashboard elements
   - Sorting by value in "Last Values" view takes data type into consideration
   - "Nodes" tab in object details view for subnets and containers
   - "Address Map" tab in object details view for subnets
   - Czech and Russian localization
- Fixed issues: #150, #226, #307, #330, #362, #363, #364, #366, #367, #373, #378, #384, #387, #390, $401, #410, #414, #416, #419, #439, #440

Best regards,
Victor

Hi!

It's not possible yet. All you can do is to setup two thresholds and use filtering script in event processing policy to block events at specific time of the day. However, soon (I plan for 1.2.11 so far) you'll be able to create thresholds as NXSL scripts, then it will be much easier.

Best regards,
Victor

Hi!

I've changed the drbd.cpp (protocol version should also work as expected). These changes are included in 1.2.10 release. Thank you for fixing it!

Best regards,
Victor

*PING - это начало новой секции конфига. ActionShellExec должен быть в основной секции, вот так:


MasterServers = trampampam.ru
ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
logFile = C:\NetXMS\var\log.txt
FileStore = C:\NetXMS\var
SubAgent = ecs.nsm
SubAgent = ping.nsm
SubAgent = logwatch.nsm
SubAgent = portcheck.nsm
SubAgent = winperf.nsm
SubAgent = wmi.nsm
SubAgent = ups.nsm

ActionShellExec = ResroreWinVPN:C:\Windows\system32\rasdial.exe $1 $2 $3

*PING
Timeout = 1000
PacketRate = 12
Target = 10.0.0.1:target_1


Hi!

1.2.10 should be released today.

Best regards,
Victor

Hi!

You can create new internal DCI with custom schedule to run once per month and either read current value of cumulative counter in transformation script. The tricky part is timing to ensure that monthly DCI runs before cumulative counter resets at month change. Alternative option could be storing value temporarily in node's custom parameters - when cumulative counter resets, it stores it's current value into some custom attribute, and then monthly DCI reads it.

Best regards,
Victor