Obviously I would rather send you the output of whatever snmpcommand you specify but if remote access is definitely what you need, PM me.

It means that those details are stored in XML files called templates and should be imported into NetXMS and configured ... thks for the link and would try to grab max. from it.. -------------------- rojaRAJU, O+ ==========

Hi, there was a bug in server - check for already queued address was not performed for addresses discovered from syslog messages or SNMP traps. Just fixed it in development branch, fix will be included in 2.1.1. Best regards, Victor

Update: starting with version 2.1 is is possible to use agent list System.IO.Devices for instance discovery.

Thanks tomaskir, i will read documentation about zoning and proxy to try this. Thanks again!

Thank you for help :). It is strange, that admin user does not have permissions to view alarms after update.

Hello Victor, thanks for the examples. I changed as described and it worked. Thanks. Best regards, Marco

Alright, so I got the server to start finding all the subnets. I had to change my active discovery subnets from the  /16 subnet, to two /24 subnets. I guess a /16 is just too large an address space for the server to search through in a timely fashion (especially since most of the subnet space it was looking at, was non-existent). The only issue that is left is that not a single node that it discovers, does it discover it with the proper subnet. It is finding everything as a /32 instead of /24...so right now what I have to do is go in and stop the server, manually change the subnets in the database, then start the server back up. At this point all the hidden nodes start showing up and going in their correct groups.

Thank you for the answer! We also think it will be good to have them in future release.

Thank you for the answer. We think this ability will be a good additional functionality request for future release....

Hi, {instance-name} is a placeholder which is replaced only during instance discovery. You can set it's value by returning third element from instance filter script, like this: return %(true, "this will became instance", "this will became instance name"); Best regards, Victor

Hi, it is know issue with table DCI performance when accessing historical data. We change the way how table DCIs data is stored in 2.1, so upgrade may help. Best regards, Victor

Hi, there should be no changes in sorting order. I'll check it. Best regards, Victor

Yes, we miss this bug again... I'll try to fix it before 2.1.1 patch release. Best regards, Victor

Hello, at the moment I am facing the problem that I want to install the netxms reporting server but at running the "reporting-server-2.1.jar" file it throws an exception called "BeanCreationException" at the end. I attached the command prompt output to this thread. I follwed the instruction at the netxms wiki page. I created the folder structure, executed the sql scripts and created a config file. Is there anyone who had the same problem or know how to fix this? Best regards, Philipp output.log

Result of nxdbupgrade with -X to skip errors, all other version upgrade steps after 410 to 411 run with no errors. Upgrading from version 410 to 411 >>> SELECT var_value FROM metadata WHERE var_name='TdataTableUpdated' >>> SELECT var_name,var_value FROM metadata WHERE var_name LIKE 'TDataTableCreationCommand_%' OR var_name LIKE 'TDataIndexCreationCommand_%' >>> DELETE FROM metadata WHERE var_name LIKE 'TDataTableCreationCommand_%' OR var_name LIKE 'TDataIndexCreationCommand_%' >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataTableCreationCommand_0','CREATE TABLE tdata_%d (item_id integer not null,tdata_timestamp integer not null,tdata_value varchar null)') >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataIndexCreationCommand_0','CREATE INDEX idx_tdata_%d ON tdata_%d(item_id,tdata_timestamp)') >>> SELECT id FROM nodes Converting table tdata_108: failed >>> DELETE FROM metadata WHERE var_name LIKE 'TDataTableCreationCommand_%' OR var_name LIKE 'TDataIndexCreationCommand_%' >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataTableCreationCommand_0','CREATE TABLE tdata_%d (item_id integer not null,tdata_timestamp integer not null,record_id number(20) not null,UNIQUE(record_id))') >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataTableCreationCommand_1','CREATE TABLE tdata_records_%d (record_id number(20) not null,row_id number(20) not null,instance varchar(255) null,PRIMARY KEY(row_id),FOREIGN KEY (record_id) REFERENCES tdata_%d(record_id) ON DELETE CASCADE)') >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataTableCreationCommand_2','CREATE TABLE tdata_rows_%d (row_id number(20) not null,column_id integer not null,value varchar(255) null,PRIMARY KEY(row_id,column_id),FOREIGN KEY (row_id) REFERENCES tdata_records_%d(row_id) ON DELETE CASCADE)') >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataIndexCreationCommand_0','CREATE INDEX idx_tdata_%d_id_timestamp ON tdata_%d(item_id,tdata_timestamp)') >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataIndexCreationCommand_1','CREATE INDEX idx_tdata_rec_%d_instance ON tdata_records_%d(instance)') >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataIndexCreationCommand_2','CREATE INDEX idx_tdata_rec_%d_id ON tdata_records_%d(record_id)') Rolling back last stage due to upgrade errors... Database upgrade failed root@d699ef6920c2:/opt/netxmsdb# nxdbmgr upgrade -t -X NetXMS Database Manager Version 2.1 Build 9012 (2.1-RELEASE) (UNICODE) Upgrading database... Upgrading from version 410 to 411 >>> SELECT var_value FROM metadata WHERE var_name='TdataTableUpdated' >>> SELECT var_name,var_value FROM metadata WHERE var_name LIKE 'TDataTableCreationCommand_%' OR var_name LIKE 'TDataIndexCreationCommand_%' >>> DELETE FROM metadata WHERE var_name LIKE 'TDataTableCreationCommand_%' OR var_name LIKE 'TDataIndexCreationCommand_%' >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataTableCreationCommand_0','CREATE TABLE tdata_%d (item_id integer not null,tdata_timestamp integer not null,tdata_value varchar null)') >>> INSERT INTO metadata (var_name,var_value) VALUES ('TDataIndexCreationCommand_0','CREATE INDEX idx_tdata_%d ON tdata_%d(item_id,tdata_timestamp)') >>> SELECT id FROM nodes Converting table tdata_108: failed Converting table tdata_126: failed Converting table tdata_134: failed Converting table tdata_160: failed Converting table tdata_194: failed Converting table tdata_232: failed >>> SELECT id FROM clusters >>> SELECT id FROM mobile_devices >>> SELECT id FROM access_points >>> SELECT id FROM chassis >>> UPDATE metadata SET var_value='411' WHERE var_name='SchemaVersion' All tdata_ tables failed to convert, as i look to sources looks like something wrong is in logic of static BOOL H_UpgradeFromV410(int currVersion, int newVersion) function.

Hello! I'm using LOGWATCH subagent to monitor events from Windows event log. In many occasions happened that a node got crazy and I received 20K+ mails informing about a repetitive event happened every second (especially during the night). Since NetXMS doesn't provide an "in-house" mechanism to prevent this, thanks to Victor's suggestions, I found the following solutions that I'm reporting here to simplify life of users that had similar problems. Basic concepts is this: Setup a counter to increase every time I receive an event I'm interested in Send standard email if the counter is below specific threshold Send warning email when the counter is equal to specific threshold Stop sending email when counter is above threshold without losing the received events Reset the counter after a specific time frame since the first event Example, threshold 50, time frame 1h. This means that the system will send up to 50 emails in 1 hour, then after the 50th events (whithin 1 hour) will send an e-mail informing about the storm and will store events in the system without sending more emails. After 1 hour since the first event the counter will be reset (through a scheduled task)) and NetXMS will start again sending email for new events of that type. Here attached you can find my sample scripts to use as base for further developments. Scripts are partially parametrized, feel free to extend and post here improvements AlarmCounterTools: script for checking threshold of counter, increase counters and other support tools ResetAlarmCounter: script for scheduled task to reset the counter after specified time frame (I don't know ho to pass parameter "eventCount" and use directly function from AlarmCounterTools) IncreaseAlarmCounter: script to increase the counter (I don't know ho to pass parameter "eventCount" and use directly function from AlarmCounterTools) Scheduled task sample EPP sample (3 rules) AlarmCounterTools.txt ResetAlarmCounter.txt IncreaseAlarmCounter.txt [image: ScheduledTask.PNG] [image: EPP.PNG]

Hi, yes, you need to create separate user with limited access rights. Workstation itself is not important - access control is done on user level. Best regards, Victor

Hi, it's a bug, already fixed in development branch. Best regards, Victor

Great thanks for those scripts Tursiops. Still have to enable debug, and post the logs to try and narrow down the cause of the failure.