[Cisco WiFi virtual Controller] Manually add device to Oxidized

Help Oxidized
#7

It appears that does not work if oxidized is on a different server.

#8

Hi,

I think it doesn’t really work if Oxidized is not on the same server, I have the Reload Oxidized nodes list, each time a device is added enabled.
When I add a new device in LibreNMS I have to access the Oxidized server and restart the service.

#9

Hello Laf,

I’ve tried to apply your advice.
Sadly, my cisco virtual controller are still not present in node list
That said, I’ve checked and my Moxa devices are neither present in node list.
I have no idea why these devices are not sent to the node list.

Vincent

#10

And, I have no problem with IOS, CiscoSMB, RouterOS, ironware devices.

Vincent

#11

It at least used to work ok.

The reload to oxidized is only called when discovery first runs against the device so by default this could be up to 5 minutes after you added the device was added to LibreNMS, have you waited that long?

#12

If you run:

curl -k -H 'X-Auth-Token: YOUR_API_TOKEN' https://YOU_LIBRENMS_URL/api/v0/oxidized

Can you see the device in the output and does the info look correct?

#13

Hi Laf,

Yes, the output with curl is good.

It is interesting that when I delete a device, I get this oxidized debug log.

I, [2022-01-28T09:33:40.772544 #995] INFO – : lib/oxidized/nodes.rb: Loading nodes
I, [2022-01-28T09:33:41.251877 #995] INFO – : lib/oxidized/nodes.rb: Loaded 551 nodes

When I added the device back in, waited over 15 min and I see no oxidized “loading nodes” message.

#14

Hello Laf,

Thank you for your help and your time.
Yes, I’ve waited that long. Neither Moxas nor Cisco WLCs appeared in Oxidized.

Regards,

Vincent

#15

A fix went into master a few days ago to fix a bug in reloading oxidized that we found, if you are using a stable release you’ll need to wait for middle of this month. If you’re not, make sure you’re upto date and it should be good now.

#16

Hello Laf,

Thank you for the fix !
Yesterday, I’ve added 2 news devices to librenms. A routeros and a ciscosmb. They were added to Oxidized automatically.
I removed one of my wlc then added it back, and it still not shown in Oxidized.

Tiki_

#17

Did you add the OS mapping as I showed earlier in a screenshot?

#18

Hello Laf,

Yes, I’ve added to OS mapping.
I’m using OS mapping for some cisco device that doesn’t support some kind of authentication and that work perfectly. But not for Cisco WLC and Moxa.
I think it’s because OS mapping is working after devices are added to Oxidized.

Tiki_

#19

If you call the LibreNMS api as per this post, do you see the correct OS returned?

#20

Laf,

I will check it.
Thank you.

Vincent

#21

Laf,

This is what I got when I call the API like you said :
{
“hostname”: “192.168.x.y”,
“os”: “ciscowlc”,
“ip”: null,
“group”: “aireos”
},
{
“hostname”: “172.16.x.y”,
“os”: “moxa-etherdevice”,
“ip”: null
},
So ciscowlc are correctly mapped to aireos.
But they are not shown on oxidized’s GUI.

Regards,

Vincent

#22

No that’s showing it’s mapped to a group, the OS hasn’t changed.

This is an example of an Arista device which has a mapping of arista_eos → eos:

    {
        "hostname": "arista_eos",
        "os": "eos",
        "ip": null
    }

If I update the mapping to eos1 then the os changes:

    {
        "hostname": "arista_eos",
        "os": "eos1",
        "ip": null
    }
#23

Thanks laf. This works for me. :slight_smile:

#24

Laf,

Oh, sorry for misreading. I’ll try it.

Vincent

#25

Hello Laf,

That works for me. Thank you so much.
For records, I’ve just discovered this list (https://github.com/ytti/oxidized/blob/master/docs/Supported-OS-Types.md), which will help me a lot.

Thank again,

Vincent

#26

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.