Unimus forum

The manage / unmanage (without it using a license) would solve my issue that I posted here:

viewtopic.php?f=7&t=332

Thanks!

We import a number of groups from our NetXMS system into Unimus for backup and this generally works very well. However, there are a couple of groups where Unimus does not currently know how to backup the device and therefore fails on it daily when it attempts either discovery or backup. We would pre...

Thanks for the quick response and links to the ticketing system items. I completely agree that BOTH the text and binary configurations need to be managed for all of the reasons given and look forward to the enhancements in the future to support this.

I have read the other posts regarding this and feel that the backup being made currently is not really in usable format. Why not just have the Unimus server perform the needed steps automatically so that you can download a working .ncfg file and then place it on the server? My guess is that when it ...

Love the simple upgrade process, now if wget would only work with the Google drive links created we would not have to get scp involved. The new version does indeed seem to work properly as documented. Thanks for the quick fix! I not the version still shows 1.5.0 in the dashboard, but obviously the f...

Is upgrading as simply as replacing the .jar file in /opt/unimus with the new one and restarting? Do not really see any documentation for the upgrade process. Thanks!

Until this enhancement can be completed I decided to tackle it on the NetXMS side of things in a way that would not require maintaining the bind rules in two places. Here is the solution: First, create a filter function as follows which is recursive: sub xlInContainers(myNode, containers) { parents ...

Those would both be awesome!

That suggestion will of course work, but is a kludge at best. Now every time the auto-bind rules for the other containers change (and yes, that is infrequent) we need to remember to modify the auto-bind rule in this new container as well. Always seems when you have to maintain the same information i...

Excellent, that is great that very little permissions are needed. Next, how do we specify the container names? We have something like: Infrastructure Services | |-Device Types | |- Access Points | |- Mikrotik |- Cambium |- Ubiquiti |- Routers |- Mikrotik |- Cisco ... If we want to specify Infrastruc...