NetXMS Support Forum

Please login or register.

Login with username, password and session length
Pages: [1] 2 3 ... 10
 1 
 on: February 16, 2018, 11:42:21 pm 
Started by jdesousa - Last post by jdesousa
Please set the default snmp version to 2c. (node properties--->communications-->snmp-->version (1 2c 3)
Respective versions 1 and 2c are bidirectionally compatible, no reason it should be V1.

 2 
 on: February 16, 2018, 07:07:36 pm 
Started by aarb00 - Last post by aarb00
I noticed that on my NetXMS server, where the agent is installed, and the machine I want to be a proxy, where it says isagent it says no.  Is that a display bug, or is my NetXMS server not seeing itself as an agent.  As shown above, my agent service is running. 

Could this be the issue?

 3 
 on: February 15, 2018, 11:06:22 pm 
Started by Carl Green - Last post by Carl Green
Opted to start again with fresh database under MSSQL instead of using the SQLLite database.

 4 
 on: February 15, 2018, 12:08:48 pm 
Started by ErnestGWilsonII - Last post by ErnestGWilsonII
We are not using Jira and we want to integrate with various ticket systems.
Currently we have alerts calling a shell script that calls curl via the command line to make API calls.
Today these calls post messages into our chat channel.
We would like to start opening, updating and closing tickets instead of just spamming our chat channel.
Before we just update our shell script (that uses curl) to make API calls into our ticket system (which we can do), we want to get some feedback please:

1. Is there a preferred method for integrating external systems? (We could have a ton of shell execs kicking off curl API calls under heavy ticket volume, that seems not optimal)
Is there any specific hooks or methods or pub/sub inside or bolted on to NetXMS we should use?

2. What about inbound (and/or two-way) integration to NetXMS from ticket systems?
If a person acknowledges a ticket in a ticket system for example, is there a way to add fields mapped back to alerts in NetXMS and indicate things like ticket #1234 is open and owned by John Doe?

What options currently exist?
What is considered to be the "NetXMS" way?
What are most folks doing in this area (we are not looking to reinvent the wheel if tooling already exists)?

Thank you,
Ernest

 5 
 on: February 14, 2018, 06:28:38 pm 
Started by silvanet - Last post by StanHubble
My 2 cents:

There are a number of ways to do this currently.
You can setup containers to group nodes any way you want (or multiple ways).  I have an infrastructure tree with around 25000 containers that group subsets of 5500 nodes in 100's of different ways.

You could also setup "custom attributes" on the nodes in question and then create a seldom polled dci that queries the custom attribute and have it show up in the "last values" panel on the overview tab of the object.


 6 
 on: February 14, 2018, 05:50:11 pm 
Started by silvanet - Last post by silvanet
Thanks for the tremendous work that has been done on this project. 

We use this to monitor lots of devices in various buildings.  A feature that would be helpful is an additional location field for nodes.  Possibly a Building field that would tell us which building this device is in.  Although having additional fields like Floor, Room would be also helpful, we could use the building field and put in additional info in the one field like "Building A, Floor 2, Room 223".

As requested in other feature requests, it would be helpful that this field could be added to a customized alarm view so we can quickly know where this device is located.


 7 
 on: February 14, 2018, 04:42:52 pm 
Started by gdodd - Last post by gdodd
Is there an option during a Windows agent silent install to set the "Download configuration file from management server on startup"?

 8 
 on: February 14, 2018, 02:12:12 pm 
Started by anw - Last post by anw
Hey
after the recent last upgrade to the newest version 2.2.3 and the the needed DB (postgres) update , we encounter a lot of issues

For e.g. the SyslogParser is not showing correctly anymore
also the Performance Tab on the Object Detail Overview is giving errors, not working at all.

See attached pictures

Any idea how to fix this?

Best

 9 
 on: February 14, 2018, 01:28:35 am 
Started by Carl Green - Last post by Carl Green
Ran this command instead to ignore SQL errors on upgrade, its working on 2.2.1 so will see how things go.


C:\NetXMS\bin>nxdbmgr.exe upgrade -t -X
NetXMS Database Manager Version 2.2.1 Build 9502 (2.2.1) (UNICODE)

Upgrading database...
Upgrading from version 21.4 to 21.5
>>> ALTER TABLE nodes ADD rack_orientation integer
>>> ALTER TABLE chassis ADD rack_orientation integer
>>> UPDATE nodes SET rack_orientation=0
>>> UPDATE chassis SET rack_orientation=0
Unable to set not null constraint.
Unable to set not null constraint.
>>> UPDATE metadata SET var_value='5' WHERE var_name='SchemaVersionMinor'
Upgrading from version 21.5 to 22.0
>>> INSERT INTO metadata (var_name,var_value) VALUES ('SchemaVersionLevel.21','5')
>>> UPDATE metadata SET var_value='22' WHERE var_name='SchemaVersionMajor'
>>> UPDATE metadata SET var_value='0' WHERE var_name='SchemaVersionMinor'
Upgrading from version 22.0 to 22.1
>>> SELECT var_value FROM config WHERE var_name='NumberOfDataCollectors'
>>> INSERT INTO config (var_name,var_value,default_value,is_visible,need_server_restart,is_public,data_type,description) VALUES ('DataCollector.ThreadPool.BaseSize','10','10',1,1,'N','I','Base size for data collector thread pool.')
>>> INSERT INTO config (var_name,var_value,default_value,is_visible,need_server_restart,is_public,data_type,description) VALUES ('DataCollector.ThreadPool.MaxSize','250','250',1,1,'N','I','Maximum size for data collector thread pool.')
>>> UPDATE config SET default_value='250' WHERE var_name='DataCollector.ThreadPool.MaxSize'
>>> DELETE FROM config WHERE var_name='NumberOfDataCollectors'
>>> UPDATE metadata SET var_value='1' WHERE var_name='SchemaVersionMinor'
Upgrading from version 22.1 to 22.2
>>> INSERT INTO config (var_name,var_value,default_value,is_visible,need_server_restart,is_public,data_type,description) VALUES ('DBWriter.MaxRecordsPerTransaction','1000','1000',1,1,'N','I','Maximum number of records per one transaction for delayed database writes.')
>>> UPDATE metadata SET var_value='2' WHERE var_name='SchemaVersionMinor'
Upgrading from version 22.2 to 22.3
>>> CREATE TABLE dci_access (   dci_id integer not null,   user_id integer not null,   PRIMARY KEY(dci_id,user_id))
>>> UPDATE metadata SET var_value='3' WHERE var_name='SchemaVersionMinor'
Upgrading from version 22.3 to 22.4
>>> SELECT var_value FROM metadata WHERE var_name='SchemaVersionLevel.21'
>>> UPDATE metadata SET var_value='4' WHERE var_name='SchemaVersionMinor'
Upgrading from version 22.4 to 22.5
>>> ALTER TABLE items ADD instance_retention_time integer
>>> ALTER TABLE dc_tables ADD instance_retention_time integer
>>> UPDATE items SET instance_retention_time=-1
>>> UPDATE dc_tables SET instance_retention_time=-1
>>> INSERT INTO config (var_name,var_value,default_value,is_visible,need_server_restart,is_public,data_type,description) VALUES ('InstanceRetentionTime','0','0',1,1,'Y','I','Default retention time (in days) for missing DCI instances')
Unable to set not null constraint.
Unable to set not null constraint.
>>> UPDATE metadata SET var_value='5' WHERE var_name='SchemaVersionMinor'
Database upgrade succeeded

 10 
 on: February 14, 2018, 01:06:44 am 
Started by Carl Green - Last post by Carl Green
Hi

I have migrated from x86 to x64 netxms system on v2.1.2 on SQLLite database successfully so had a go at upgrading to v2.2.1 but hitting issue of:

C:\NetXMS\bin>nxdbmgr.exe upgrade -t
NetXMS Database Manager Version 2.2.1 Build 9502 (2.2.1) (UNICODE)

Upgrading database...
Upgrading from version 21.4 to 21.5
>>> ALTER TABLE nodes ADD rack_orientation integer
>>> ALTER TABLE chassis ADD rack_orientation integer
>>> UPDATE nodes SET rack_orientation=0
>>> UPDATE chassis SET rack_orientation=0
Unable to set not null constraint.
Rolling back last stage due to upgrade errors...
Database upgrade failed

Any pointers to fix this?

I might have to bite the bullet reconfigure the system from scratch as my plan was to migrate over to MSSQL database but as I can't get the migrate to work either looking like this might be my only option.

Thanks

Carl

Pages: [1] 2 3 ... 10