NetXMS Support Forum

Hello!

There is one way to do this, however it's not universal (i.e. you will not be able to use this in generic templates). You can define DCI which collect free physical memory in bytes, and than convert it to percents using transformation script - however, you will need to hardcode total amount of physical memory on target machine into this script. For example, if you have 1GB of memory on your server, you can write the following transformation script for parameter System.Memory.Physical.Free:

($1 / 1073741824) * 100

where $1 represents current  DCI value (which is free physical memory in bytes), 1073741824 is a total amount of physical memory in bytes.

Best regards,
Victor

Почти все из перечисленного NetXMS делать может. Визуализaция сети находится в зачаточном состоянии. Нет audit лога (но будет). И я не очень понял что имеется в виду под "Визуализация состояния оборудования" и "Подключение к устройствам".

Best regards,
Victor

Hi!

По пунктам:

1. Какой-то баг, будем смотреть.

2. Сделаем к следующему релизу.

3. Тоже обязательно будем делать, постараемся к 0.2.19, но 100% не обещаю.

4. Сделаем к следующему релизу, благо ничего сложного здесь нет.

Best regards,
Victor

Spasibo za ssilku.

V 0.2.18 ispravlena problema v clientskoj biblioteke kotoraja vizivala crash nxhttpd na FreeBSD (na ostal'nih OS vse rabotalo). Ispravili v ponedel'nik.

Moj ICQ number: 379055985

Best regards,
Victor

ICQ net, no mogu postavit'.  Kogda zaregistrirujus', v forum napishu id.
Novij forumnij soft mi uze zapustili (simple machines forum), nemnogo potestim/ponastraivaem i perekljuchimsja na nego. Edinstvennaja sloznost' - hotelos' bi smigrirovat' suschestvujushih userov i topiki.

Best regards,
Victor

Hi all!

Version 0.2.18 is released. Changes from previous version:

- Windows console: added "subordinates" view in object browser
- WinPerf subagent:
  - Improved non-English Windows support
  - Added new parameter: System.IO.DiskTime
- New MIB added: FIBRE-CHANNEL-FE-MIB
- Fixed issues: #23, #129, #163, #164, #165, #167, #168, #170, #172, #173, #174, #175, #176, #177, #178

Best regards,
Victor

A kakaja OS stoit na mashine otkuda dannie ne berutsja?

Protiv sozdanija portov - razumeetsja ne protiv.

Best regards,
Victor

Hello!

It's a bug, I have fix it in 0.2.18.

Best regards,
Victor

1) web

Skoro vilozim reliz 0.2.18, nadejus' tam budet poluchshe. S core dump'om odnu problemu ja na dnjah ispravil, etot fix dolzen okazatsja v 0.2.18. Faili dlja DocuentRoot dolzni avtomatom kopirovatsja pri make install v <prefix>/share/netxms/nxhttpd. Esli oni tam i lezat, to DocumentRoot mozno ne ukazivat', on po umolchaniu pokazivaet na etot katalog. V source packag'e ves' static content lezit v srx/nxhttpd/static.

2) Statistika po traffic'u
Mozno poprobovat' takuju vesch: delaem DCI po interface bytes in (parametr agenta Net.Interface.BytesIn), stavim retention time 365 (ili bol'she), chtobi dannie hranilis' minimum god, v zakladke transformation stavim "SImple Delta". Posle etogo sobrannie dannie za nuznij period mozno budet exportirovat' v tekstovij fail, otkrit' v Excel i prosummirovat'. Perezagruzki nado proverit' naskol'ko horosho budut obrabativatsja - esli budut s etim problemi - pochinim, vesh' nuznaja.

3) Forum
Soft budem menjat', nineshnij prosto pervim nashelsja kogda ja iskal chto-nibud' chtobi bistro postavit'.

Best regards,
Victor

Hi!

Foruma na russkom jazike dejstvitel'no net (pohoze uze pora delat'), no est' mailing list nextxms-users-ru.

Porti dlja FreeBSD - plani est', no tochnoj dati poka obeschat' ne mogu.

Best regards,
Victor

Hello!

You have found a new bug, just introduced in 0.2.17 Problem is with malformed SQL request - you can see it in the log if you enable logging of failed SQL queries by adding LogFailedSQLQueries = yes to netxmsd.conf. I'll fix it today. Looks like 0.2.17 is one of the buggiest versions we ever release...

Best regards,
Victor

P.S. Normally, server commits all unsaved configuration changes to database periodically - every 60 seconds by default. All unsaved changes also will be commited on shutdown.

Hello!

Having NetXMS agents on monitored systems is recommended, but not required. If you only interested to now if particular host is alive or not (responds to ping) and/or that particular services (like ssh or http) are alive, you don't need agent on that host. But if you wish to get more information (like CPU usage or status of particular process) you will need an agent on monitored system (you may also use SNMP agent and collect data via SNMP).

Best regards,
Victor

Hello!

All timestamps used in NetXMS internally stored in UTC and converted to local clock when shown. As far as UTC times on client machine and server are identical everything should be ok. If you don't see graphs correctly, possibly UTC time on your server or client is incorrect. One example of possible incorrect time settings:

1. My timezone is EET, which is GMT + 2 hours.
2. On my workstation, I set timezone to EET, but on server in the same location - GMT.
3. On both workstation and server I set time 14:00. Looks like both shows time correctly, but internally workstation has UTC time 12:00 (because of timezone settings), but server has UTC time 14:00. If I will connect with NetXMS console to server I'll see unexpected timestamps.

Best solution is to use NTP for time synchronization (it will always set your machine clock to correct UTC time) on both server and client.

Best regards,
Victor

Hello!

This is an expected behavior. Main idea is that all IDs should be unique,  so system just keeps first unused id and increments it after every creation. There are two reasons why we don't reuse freed IDs:
1. If, due to error, reference to deleted object will remain somewhere, it will later be threated as an error because ID is invalid. But, if we reuse the id, later it will be impossible to determine if this was undeleted reference to old object or valid reference to new one.
2. Optimization of code - server don't need to scan for free ID - not a big issue however.

It should not be a problem, because we have 32-bit IDs, so we have more than 4 billions of available IDs. I hardly imagine monitoring system where such number of id's can be exhausted in reasonable period of time. Even if system's administrator will create and delete new trap record every second, it takes more than 126 years to exhaust ID space. Also, if such problem ever arises, it will not be hard to write special database maintenance tool which will "compact" id space.

Best regards,
Victor

Hello!

Ensure that winperf subagent is loading. You should have line in your config like this:

SubAgent = winperf.nsm

You can check list of currently loaded subagents by selecting node object in console, then Tools->Info->Agent->Subagent List.

Best regards,
Victor