Dears,
I have Oxidized set up along with LIBRENMS and working.
If i go the oxidized website i see correctly the configuration correctly.
But if I want to see that same configuration from librenms, it can be seen with the following image.
any ideas?
Thanks
I have a similar issue.
My problem is that I don’t use DNS, so my routers are entered into LibreNMS by IP address and I use the “Display Name” field for the router’s name. My Oxidized has a router.db file in the format NAME:IP_ADDRESS:MODEL:GROUP. (I do this because I have stuff being backed up that is not in LibreNMS, and Oxidized can only use one source.)
I used tshark to capture the request from librenms to Oxidized and IIRC, it asks for the device by the IP Address, which Oxidize can figure out which name that is and gives the metadata (eg list of config history), but when LibreNMS tries to pull the config, it asks for the IP address again which Oxidize cannot find and give the “Sinatra didn’t know that diddy” error.
I have not figured out how to move past that. But since I have devices being backed up not being monitored by LibreNMS, I mostly use Oxidized WUI. I put configured apache to serve it as a proxy with some authentication to at least keep configs from being easily found by an internal scanner and went back to my normal work.
