Orphan Device API

[rohanrajnv]

Orphan Device API

[rc9000]

Hi! This doesn't seem to be in the API currently. But for a quick solution you can take the SQL from here, put in a custom report and fetch that via the API.

[ollyg]

Hi no it’s just in the web front end config only.

…

On Sat, 16 Dec 2023 at 13:24, rohanrajnv ***@***.***> wrote: Thanks for your response. Do we have to update all the deployment.yaml for the custom report? i have 6 backend — Reply to this email directly, view it on GitHub <#1144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAHHVPBEB6B4QGOVKHATB3YJWOHPAVCNFSM6AAAAABAW56PPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYHAYTQMBZGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[rohanrajnv]

Thanks for your response. Do we have to update all the deployment.yaml for the custom report? i have 6 backend

[rohanrajnv]

Thanks for your response. Yes, but in my case, all the backend is hosting the web, so I updated all the deployment.yml.
I can see that the orphan list shows an IP that does not even have a device. Like the IP 192.168.55.10 is not a used ip in my network, I am still able to see it in the orphan list. i have changed the query to include devices with ports but i dont think this is the correct way. any suggessions please?

Is there any way to run the discovery, arpnip macsuck, snapshot, and nbtstat from the API?

[rohanrajnv]

Some devices are still showing as orphans even when they have a connected port.
Like Device 192.168.35.11, it is on switch port 1 of switch 10 as per the Neighbors tab and still in the orphan list.