NetXMS Support Forum

Hi!

Did you add a rule to generate alarm? Having threshold will only generate you an event - you have to add a rule to event processing policy to make alarm from it. See Event Processing section in user manual for more information.

Best regards,
Victor

Hi!

This can be done using scripts. For example, the following script will return true if node has only subnets a parents:


result = true;
parents = GetNodeParents($node);
foreach(p : parents)
{
   if (p->type != 1)   // Type 1 = subnet
   {
      result = false;
      break;
   }
}


You can create separate container with autobind script which will bind nodes not located in any container. For example, if you call this container "NewNodes", autobind script could be like this:


parents = GetNodeParents($node);
foreach(p : parents)
{
   if ((p->type != 1) && (p->name != "NewNodes"))   // Type 1 = subnet, also ignore "NewNodes" container itself
   {
      return false;
   }
}
return true;


Best regards,
Victor

Hi all!

NetXMS version 1.2.16 is out. It's mostly a bugfix release to fix important issues found in 1.2.15. Full change log is following:

- Fixed database upgrade issues
- Fixed packaging issues
- Fixed bug causing outdated peer information on interface objects
- Fixed bug with upload to agent default path from server file store
- Instance display name for DCIs created via instance discovery
- DCIs created via instance discovery can be combined by instance into one chart on performance tab
- Transformation script terminated by "abort" call will not generate SYS_SCRIPT_ERROR event
- Database manager can detect and fix missing IData and TData tables
- NXSL:
   - String concatenation operation interprets NULL value as empty string instead of throwing runtime error
   - Fixed incorrect processing of ilike, match, and imatch operators
   - Added try / catch operator
- New MIBs added: NETUP-MIB
- Fixed issues: #424, #618, #619, #620

If you are upgrading from version 1.2.14 and below and encounter errors related to missing tdata tables during database upgrade please run command

nxdbmgr check-data-tables

and the run upgrade again.

Best regards,
Victor

Quote from: flynao on August 05, 2014, 04:30:18 PM
Hi  Victor,

I runned the nxupload on line command and the result is:


903: I/O failure


thanks

Hi,

file upload using core agent is fixed. We will release version 1.2.16 which will include that fix later today.

Best regards,
Victor

Quote from: lindeamon on August 05, 2014, 09:12:54 PM
Hi,

don't want to be a nag but, when does 1.2.16 with all the bugs fixes will be out ?

10x,
Lindeamon

Hi,

it's being packed and will be available later today.

Best regards,
Victor

Strange. Is it really same table, or maybe it is now with different ID or tdata instead of idata? Try to create four tables: idata_492, tdata_492, tdata_rows_492, tdata_records_492.

Best regards,
Victor

Hi!

Seems that you have some object (with ID 492)being deleted for which corresponding idata table does not exist. As a workaround try to create table with that name and any structure so server can delete it and proceed.

Best regards,
Victor

Сделал такую возможность для instance discovery DCI - теперь производные DCI объединяются на основе значения instance если в "attach to" был указан базовый DCI.

Не совсем понятно с чем объединять графики. Если после instance discovery создаются 10 DCI скажем, то для каждого делать график и к нему добавлять DCI в котором выбран instance discovery DCI как attach to?

Hi,

there are different ways to implement this. One could be to create DCI with origin "Internal" and parameter name "Dummy" (it will just generate 0 at given intervals), give it meaningful description like "Memory usage", and in transformation script read necessary SNMP values and do the computation. Transformation script cold look like following:


snmp = CreateSNMPTransport($node);
total = SNMPGetValue(snmp, ".1.3.6.1.4.1.2021.4.3");
avail = SNMPGetValue(snmp, ".1.3.6.1.4.1.2021.4.6");
cached = SNMPGetValue(snmp, ".1.3.6.1.4.1.2021.4.15");
return (avail + cached) / total;


Then you can add threshold "more then 0.9" or any other as usual.

Best regards,
Victor

Hi!

Quote from: flynao on August 01, 2014, 08:47:54 PM
Am I supposed to update all the agents I've running with previous versions (1.2.8 and 1.2.14) in order to upload a file from the netxms server (1.2.15)? and wait until the new realese (inclundin the missing file manager subagent).

Remote upgrade and file upload are supported by older agents also. For fully functional file manager you need agent 1.2.15 or higher and filemgr subagent (which will be included in 1.2.16).

Quote from: flynao on August 01, 2014, 08:47:54 PM
I've having a really hard time trying to install remotly software using the package manager on server 1.2.15, could it be a new bug?. NPI file are ok and sometime the server could achieve the task but mostly it fails.

Can you please provide more details? What errors you got, on what platforms, etc.

Best regards,
Victor

Quote from: lindeamon on July 31, 2014, 12:03:51 PM
how soon will you do it ? i want to download a full working version without extra files.

I plan to release 1.2.16 with all hotfixes today or tomorrow.

Best regards,
Victor

Yes, it's a bug. Updated version will be available later today.

Best regards,
Victor

По логу не видно что сервер вообще подключается. Попробуйте с командной строки послать СМС прямо на агент:

nxaction ip_address SMS.Send phone text

Попробуйте поставить уровень дебага повыше в агенте (скажем 6), тогда будет видно в логе что проишодит при отправке СМС на стороне агента.