Oxidized is running on a separate server and is running just fine.
LibreNMS is on a different server and is running just fine.
Oxidized integration is mostly running fine, but I’m unable to see the configurations.
I get the sync information, the different version information, and the author information. In the are where the configuration is supposed to be is raw HTML.
The biggest piece of information in the code is :
Oxidized::NodeNotFound at /prod/node/version/view
unable to find ‘XXX.XXX.XXX.XXX’
(I did take out the HTML so that it wouldn’t interfere with the post.)
Odd thing is that LibreNME is connecting to the node, and Oxidized is connecting to the node.
Oxidized has support for feeding devices into it via an API call, support for Oxidized has been added to the LibreNMS API. A sample config for Oxidized is provided below.
You will need to configure default credentials for your devices in the Oxidized config, LibreNMS doesn’t provide login credentials at this time.
source:
default: http
debug: false
http:
url: https://librenms/api/v0/oxidized
map:
name: hostname
model: os
group: group
headers:
X-Auth-Token: '01582bf94c03104ecb7953dsadsadwed'
LibreNMS is able to reload the Oxidized list of nodes, each time a device is added to LibreNMS. To do so, edit the option in Global Settings>External Settings>Oxidized Integration or add the following to your config.
This guy here on youtube did a really good tutorial about this.
I followed his video to get it working on my system Did it twice and more times already There are alot things which are tricky and not working first.
It looks like what you are suggesting is to add devices automatically from LibreNMS to Oxidized. I’m not quite wanting to do that. I’m wanting LibreNMS to display the configuration that it received from Oxidized. I’m not wanting LibreNMS to add devices to Oxidized.
LibreNMS and Oxidized are MOSTLY talking. Again, they are separate instances running on two diffferent VMs. Oxidized is being fed by a local router.db file. I’m not wanting LibreNMS to feed Oxidized. If we add another device, we’ll just go ahead and add it in both places. I know…not efficient, but there it is.
As I mentioned, LibreNMS and Oxidized are mostly talking. I’m getting versioning information, node information, backup status, but not the actual backed up config. See the below graphic:
Neat, you are first one I’ve seen use that. You should make sure there are no bugs with using that and integrating with LibreNMS. Check all urls LibreNMS is using.
