NetXMS Support Forum

No, this functionality presents from  the very beginning.

I'm working on 0.2.23 release, most likely it will be out this weekend.

Best regards,
Victor

Hello!

It's in our wish list. I have some ideas of how to implement this, and will try to do it in one of next releases. Unfortunately, I cannot define precise time frame for implementing this feature right now.

Best regards,
Victor

Hello!

Probably the problem is with access rights - by default, NetXMS agent service runs under Local System account. Try to run it under domain user with sufficient rights.

Best regards,
Victor

Just test it - there is a bug in SNMP proxy code - situation when host is an SNMP proxy for itself is handled incorrectly. I'll fix it.

Best regards,
Victor

Quote from: Player1 on November 10, 2008, 02:27:22 PM
i'd like to use the netxms agent on host C as a snmp proxy to localhost (to itself - host C). this is because of the firewall.
the snmp agent status in the console remains "inactive", but i can snmpwalk to localhost on host C. i can't figure out why.

One more question: did you try snmpwalk from host C to host C IP address (not localhost)? Because NetXMS agent will send SNMP requests from hosts's IP address to it's own IP address, it will not use loopback.

Best regards,
Victor

Hi!

I'll test this configuration later today or tomorrow.

Best regards,
Victor

Hi!

Since 0.2.22, you can set NetXMS ODBC database driver not to use unicode by adding

DBDrvParams = unicode=no

to your netxmsd.conf file. I have tested NetXMS server running on Ubuntu Linux with MS SQL 2005 via UNIX ODBC, and it works fine.


Best regards,
Victor

Доброе утро!

Для большого количества агентов желательно увеличить количество потоков, собирающих информацию. Попробуйте выставить параметры сервера (View -? Control Panel -> Server Configuration):

NumberOfStatusPollers = 75
NumberOfDataCollectors = 75
NumberOfConfigurationPollers = 10
NumberOfRoutingTablePollers = 20

Если не поможет, запустите пожалуйста сервер с ключом -D 7 (это включит отладочную информацию), и пришлите netxmsd.log (можно на dump - at - netxms.org).

Hello!

Server caches last values for each DCI, so when console displays them, data is coming directly from server's memory, not from SQL database.
However, you may use something like this:

If you wish to get last values for all DCIs on given node, you can use the following query:


select A.item_id,A.ts,D.idata_value,I.description from
(
select item_id,max(idata_timestamp) as ts from netxms.idata_14 group by item_id
) A
join netxms.idata_14 AS D on A.item_id=D.item_id and D.idata_timestamp = A.ts
join netxms.items AS I on I.item_id = A.item_id


For node with id 14.

You can also define the stored procedure for retrieving last values for given node:

CREATE PROC LastValues
@Id integer
AS
EXEC ('
select A.item_id,A.ts,D.idata_value,I.description from
(
select item_id,max(idata_timestamp) as ts from netxms.idata_' + @Id + ' group by item_id
) A
join netxms.idata_' + @Id + ' AS D on A.item_id=D.item_id and D.idata_timestamp = A.ts
join netxms.items AS I on I.item_id = A.item_id'
)
GO


I'm not good in SQL, so probably there are better way to do this

Best regards,
Victor

Hello!

Try to type TREND in lowercase.

Best regards,
Victor

Очень хорошо Поскольку повторить это у себя мне так и не удалось, и особых идей не было...

Thanks for reporting, I'll fix it.

Best regards,
Victor

Hello!

libnxsnmp.so is not a subagent - it's just our SNMP client implementation used internally by NetXMS server and SNMP-related command line tools (nxsnmpget, nxsnmpset, and nxsnmpwalk). Names of subagent modules always starts with libnsm_.

Best regards,
Victor

Hello!

In this topic (https://www.netxms.org/forum/index.php/topic,485.0.html) you can find description how NetXMS stores collected data in database - probably it should be enough for report generation. If you will need additional information, just to ask me.

Best regards,
Victor

Hello!

You can achieve notification escalation in various ways:

1. If you monitor some DCI, you can define different thresholds with different events, for example one event if CPU utilization exceedes 90% for 1 minute, and other if it exceeds 90% for 10 minutes, and then process these events by sending appropriate emails.
2. You can set timeouts on alarms, and process these timeout events. So, if problem occurs, you create alarm from an event, and if nobody acknowledges this alarm within given timeout period, you get another event which you may process and send another notification (and probably create another alarm with timeout, which will trigger third level of escalation, and so on).
3. If you just need to re-send notifications all the time to same destination for DCI threshold violations, you can simply set "repeat interval" in threshold configuration.

Best regards,
Victor