Page tree
Skip to end of metadata
Go to start of metadata

NetXMS importer can import devices from NetXMS.

You can specify multiple containers to sync devices from.
Please note each sync container should be provided on a separate line.

Required privileges in NetXMS

The user used for sync doesn't need any System Rights at all.

It only needs access to the containers configured for sync, and all the objects in those containers which should be synced.
For the containers and objects, only "Read" access right is required

Specifying import criteria

All devices under the sync containers will be synced into Unimus.
(Unimus will find all nodes bound to each sync container and all containers under the sync container)

Unimus now supports specifying sync container in 3 ways:

1) Specify just the container name

If only the container name is specified, the first container found in NetXMS matching the name will be used. To do so, following key value formant need to be used "container=Name".

For example "container=Customer A" (without quotes) would sync from container with name Customer A.

2) Specify exact container path

You can also specify exact container path if you have multiple container with the same name.

For example, consider the following NetXMS strucutre:

|- Infrastructure Services
   |- Customer A
      |- Routers
      |- Switches
   |- Customer B
      |- Routers/Switches
      |- Wireless

You can specify "container=Customer A/Routers" (without quotes) to only sync devices from that container.

You can use "\" as an escape character if your container name contains "/".
For example, you can specify "container=Customer B/Routers\/Switches" (without quotes) to properly sync that container.

3) Specify container IDs to sync from

You can specify container IDs by key value format “id=id value"

For example, specifying "id=1574" (without quotes) would sync from container with ID 1574

How to configure the importer

1) Provide full NetXMS server URL in the "NetXMS server address" field.

For example: ""

2) Provide Username and password to access NetXMS.

3) Configure Container Names or Container IDs to import devices from, one per line.

4) Optionally, you can also schedule the importer.

You simply need to select an existing (or use the default) schedule.With this configuration, Unimus will sync against the NMS periodically.

  • No labels