You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
NTNU is slowly migrating their network to a fully Cisco-based infrastructure, complete with Software-Define Access (SDA)
They have expressed a desire for NAV to be able to fetch and display at least two separate switch port attributes from Cisco SDA (presumably through an API), which apparently cannot be pulled from the switch' running config itself using SNMP.
Describe the solution you'd like
Some questions remain unclear and we cannot proceed with planning this feature until they have been clarified. A non-exhaustive list of unclarified question is:
How do we access the Cisco SDA API? (Including: Where do we find API documentation?)
Is there a single API instance for all of the network, or are there multiple controllers/instances controlling groups of devices?
Should NAV fetch and store these values as part of its normal ipdevpoll inventory jobs for devices in such a network, or should it fetch the data live from SDA as the device pages are browser in the NAV web-UI?
How will NAV know which switches to fetch port configuration from SDA for, and which to not?
Where in the UI should NAV display these config values? Specifically, which tools, pages, reports, tabs, tables?
Additional context
NTNU currently have their own implementation/UI to summarize port configuration status, based on pulling configuration information over SSH connections to devices. Their UI currently looks something like this:
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
NTNU is slowly migrating their network to a fully Cisco-based infrastructure, complete with Software-Define Access (SDA)
They have expressed a desire for NAV to be able to fetch and display at least two separate switch port attributes from Cisco SDA (presumably through an API), which apparently cannot be pulled from the switch' running config itself using SNMP.
Describe the solution you'd like
Some questions remain unclear and we cannot proceed with planning this feature until they have been clarified. A non-exhaustive list of unclarified question is:
Additional context
NTNU currently have their own implementation/UI to summarize port configuration status, based on pulling configuration information over SSH connections to devices. Their UI currently looks something like this:
The text was updated successfully, but these errors were encountered: