...

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

NetXMS importer supports remote UUIDs.

Required privileges in NetXMS

...

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

...

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

You can specify "Customer Acontainer=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.

...

You can specify container IDs by prefixing the ID with a "#".key value format “id=id value"

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

...

Then in Unimus, simply specify the 'Unimus sync' container to sync from.

How to configure the importer

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

For example: "10.2.0.111"

 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.