Hi all,
As I couldn't find any other place for feature requests, I would like to post my list here in these forums. I've been using software versions 19.2.3, 19.2.4 and 20.3.2 and I ran into a bunch of things that I would like to see improved for a better user experience.
If you have anything to add, please feel free to mention this in the comments.
Controllers:
- Back button on "Push Feature Template Configuration".
One mistake requires a complete do-over for one or more devices instead of correcting a typing error. - Geography map reflects alarm status per group of devices.
Geograhphy map shows the number of routers in a location, but the color also indicates the exact same info. Why? Please make the color reflect the alarms that are currently open for one or more routers within that set of devices. So, if I have 20 routers in Europe and one of them has one or more critical alarms, color that group red and I know I need to open it up. Now the geography function is just a fancy way of showing your manager where you're routers are located. Pointless otherwise.
Addition: setting squares on each bubble with the number of minor, major and critical alarms would be even more informational and could help transform this view to be more usable for a NOC. - Ability to see vbond orchestrator connections & connections-history through the GUI.
That way I can see routers coming up, before they connect to vManage. OR, if the vManage or control connection to vManage has an issue, I could quickly verify that the router is at least talking. - Ability to see vSmart connections to edges in the GUI.
- If/else constructs in statements and templates.
Setting up TLOC extensions is a lot of copy pasting. Especially because its the same for each site. Example, if edge.name ends with -1, apply feature template: .... If edge.name ends with -2, apply feature template: .... - Allow me to set coordinates through the GUI via a drag and drop for example
- Allow object or variable inheritance.
Routers with the same site-id will have the same coordinates. The map doesn't zoom in far enough anyway to allow for routers to be placed on different ends of a building. - Group Application-Aware routing statistics by WAN connection (as an option).
Crappy long distance links will always show up here, tunnel by tunnel. Even if they have only one crappy WAN connection. - Make Application-Aware routing statistics more flexible by allowing the user to set thresholds for packet loss.
- Make Application-Aware routing statistics more usable by establishing a baseline and show deviations.
- Auto-login into devices via SSH terminal.
Perhaps allow us to set SSH credentials under our vManage user account. Using complex passwords is a pain if you don't have direct SSH access to a router. - Transport health will only show the average per color to color transport.
This is pretty useless on a large scale. Please allow us to set it to just the Hub TLOCs for example or worst performing TLOCs or something like that. - Better scale the Top Applications on the vManage dashboard instead of some sort of logarithmic scaling.
Router feature request:
- Standard call-home feature reporting port, NAT state and local and public WAN IP addresses to a portal at Cisco.com.
This can aid with remote router deployment when not using ZTP. If this information is picked up by vManage, that's even better.