![]() ![]() ![]() notice it's still queueing when using "discover all" from the web gui.have a device that was once known but is offline.Perhaps using -enqueue option could work? Steps to Reproduce (for bugs) Only deleting via the web gui seems to remove it from the discover queue Possible Solution ![]() Interrogation of these control APIs in conjunction with adjacent SNMP-enabled equipment can help flesh out the network topology of heterogeneous environments utilizing these proprietary stacks.ĭeleting a once known device via netdisco-do delete should remove it from the discover queue Current Behavior The control APIs generally contain all of the data elements sought by SNMP interrogation today - names, serial #s, interfaces, VLANs, addresses, routes, etc. They are replacing these systems with proprietary WAN-based API endpoints permitting interrogation and management of device/cluster configuration. Vendors are disabling, eschewing, or just ignoring implementation of SNMP in an increasingly large number of model lines - Aruba InstantOn APs, Arista Wireless (they bought Mojo), etc. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |