NetXMS Support Forum

Same results after upgrading. The routing table does take much longer to timeout now. "Route From" now just shows "Incomplete;0 hops"

Will do! Thanks

Bump

File uploaded. Thanks

Yes I am seeing "request timed out" when trying to open the routing table on Mikrotik devices. Server is running on Windows 10.

Thanks

Server version 5.2.3

We made some routing changes on our network and now the "route from" option no longer works. The routing table for our mikrotik routers no longer loads, just a time out error.

I just need some assistance on how to troubleshoot this. I am able to see the arp cache and all the interfaces, and there are no SNMP errors.

That was exactly what I needed. Thanks! Posting setup here for reference.

Node goes down.
2 minutes later slack alert goes out
5 minutes later slack alert goes out
20 minutes later slack alert goes out

If the node comes up prior to 2 minute alert, alarms are cleared and no alert is sent. 

I believe after messing around with this for some time it is working. Once I added all nodes on the routes between the server and the nodes, did "route from" to the Netxms server, initial testing is showing dependencies working properly. Even on the UBNT ap's and other devices without SNMP. 

Big thank you to everyone who helped get me through this!

I figured out how to do that. Thank you! I also learned that SQL Server Express that comes with Netxms has a 10GB database size limit. Looks like we need to upgrade to Standard to get around that.

The monitor section is filling up with these critical errors. Can anyone shed some light on what this means? I have plenty of hard drive space. 

Standard windows install using built in database. 

15.10.2024 15:12:01 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2162 (item_id,idata_timestamp,idata_value,raw_value) VALUES (9031,1729023120,'-74','-74'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2162'.'idx_idata_2162_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)

15.10.2024 15:11:59 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2162 (item_id,idata_timestamp,idata_value,raw_value) VALUES (9029,1729023119,'-43','-43'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2162'.'idx_idata_2162_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)

15.10.2024 15:11:53 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2162 (item_id,idata_timestamp,idata_value,raw_value) VALUES (9023,1729023113,'-60','-60'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2162'.'idx_idata_2162_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)

15.10.2024 15:11:51 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2813 (item_id,idata_timestamp,idata_value,raw_value) VALUES (12294,1729023111,'333','333'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2813'.'idx_idata_2813_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)

15.10.2024 15:11:50 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2162 (item_id,idata_timestamp,idata_value,raw_value) VALUES (8218,1729023109,'4144','19176478311'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2162'.'idx_idata_2162_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)

15.10.2024 15:11:48 NetXMS Server 111 Critical SYS_DB_QUERY_FAILED Database query failed (Query: INSERT INTO idata_2751 (item_id,idata_timestamp,idata_value,raw_value) VALUES (9200,1729023108,'5072','15860024'); Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.idata_2751'.'idx_idata_2751_id_timestamp' in database 'netxms_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)

My goal is to have three alarms when a node goes down. One alarm after being down for 2 min, another alarm after being down 5 minutes, and a third alarm once the node has been down for 20 minutes. 

Once the node comes back on line then we get a node Up alert.

With my current setup this is all working with one snag. If a node goes down for less than 2 minutes and then comes back up I get a node up alert. Since the node was down for less than 2 minutes I never get the node down alert. 

Very similar to the issue in this post from 2012, but when I try to add the first script Netxms tells me its deprecated. 
https://www.netxms.org/forum/general-support/event-based-on-resolving-an-alarm-timeout/

I'm not familiar with scripting at all so I was hoping I could get this accomplished using some combo of event processing policies. Any help would be appreciated.

Attached. Thanks

Can you be more specific about capabilities? The mikrotik does support LLDP but the UBNT AP does not. Is that what you are meaning?

I added the rest of the routers between the server and the tower and now "route from" works and knows the whole route back to the server.

The main tower routers still do not see the UBNT access points as peer nodes. I can't see any way to manually add them.

From what I can find they do not support LLDP, only CDP.

I tried "route from" and pointed to the server and got this result: