Browse, vote, and track the status of feature requests from the NetBrain community
Browse open ideas available for voting, feedback, and discussion.
View ideas that are planned for future product development.
Explore ideas that are currently being developed by the product team.
Explore ideas that are now available in the product.
View ideas that are not currently planned for product development.
NetBrain does not currently provide native onboarding or discovery support for 6WIND devices, which limits visibility and digital twin creation for environments that rely on this vendor's platform. This enhancement proposes adding a dedicated adapter or driver for 6WIND devices, along with documented prerequisites and setup guidance to streamline onboarding. Customers operating 6WIND infrastructure would benefit from extended multi-vendor coverage, allowing them to fully model and manage these devices within NetBrain without manual workarounds.
NetBrain maps do not automatically refresh to reflect updated device status and topology changes after a Scheduled Network Intent completes execution; users must manually refresh the map to see current results. This enhancement would enable maps to automatically update with the latest device status and topology data once a scheduled intent run finishes. Automating this refresh would ensure network maps consistently display accurate, current information without requiring manual intervention, improving reliability for monitoring and troubleshooting workflows.
NetBrain currently supports only standard username and password authentication for MongoDB connections, with no ability to specify an authSource database or an authentication mechanism (authMech) required by certain MongoDB deployment configurations. This enhancement would add configurable authSource and authMech fields to the MongoDB connection settings, allowing administrators to align NetBrain with their specific MongoDB authentication requirements. Customers running MongoDB environments that require a designated authentication database or a non-default authentication mechanism would benefit from successful connectivity without needing workarounds or configuration changes on the database side.
The System Administration panel does not currently allow administrators to sort user accounts by the Department field, and this field is also unavailable when exporting the user list. This enhancement would add Department as a sortable column in the user management grid and include it as a field in user list exports. Administrators managing large or organizationally structured user populations would benefit from a faster way to group, review, and audit accounts by department.
NetBrain currently relies on a single consolidated command to retrieve full device configuration for supported models. For devices that do not offer such a command but instead can generate a batch file containing the complete configuration, there is no supported way to retrieve and parse that file through NetBrain. This enhancement would allow NetBrain to issue a command that triggers generation of a configuration batch file on the device and then retrieve that file for use in configuration checks and analysis. Supporting this retrieval method would extend certification coverage to device models that lack a single consolidated show command, giving customers consistent configuration visibility across a wider range of hardware.
NetBrain currently does not collect MAC table data from Cambium Microwave Radio devices, since the driver lacks support for the relevant command used to retrieve this information. This enhancement would extend the driver to collect the MAC learning table, consistent with how similar data is gathered from comparable device drivers. Adding this capability would allow NetBrain to accurately discover Layer 2 connections involving Cambium Microwave Radio devices, improving topology completeness for customers operating microwave backhaul links.
I noticed, that in NetBrain we have build in API for FortiManager. I tried to add our FortiGate manager there, but I found out, that it's not supporting discovery of firewalls. Could you please consider adding support for firewall discovery using existing FortiManager API?Case: 00180683
Our environment has a lot of IPv6 only devices that NetBrain don't support for now, so we have to assign IPv4 addresses to each one of them manually and that's very time consuming. Since we are planning to have more and more pure IPv6 devices, I'd like to request NB to fully support those devices just like you do with IPv4. IPv6 is the next big thing, so supporting IPv6 will greatly increase our adoption with NetBrain.
From a map with L2 connections I would like to have an export of all shown connections as text. Something like this format:device1, interface Gi1 - device2, interface Gi1/1device1, interface Gi2- device3, interface Gi1/5 and so on.I imagine this should not be too difficult because the information is already available on the map, it could be done as a CSV export or in a Note on the map.
When using the Get Device Neighbors by Topology Type API I can request L2 or L3 neighbours from a device. The L3 result looks the same in format just providing L3 neighbours instead of L2, naturally.For L2, I get a result that looks like this{'neighbors': [{'hostname': 'R4', 'interface': 'Ethernet0/1 123.10.1.1/30'},.....What you will immediately realize is that it is a simple JSON list giving neighbouring hostname and its interface.What you will not get is the interface on the queried switch to which the neighbours are connected. This L2 information would be very usefull and even for L3 it would be interesting if the local L3 interface were provided.
Right now Device Groups have a flat hierarchy whereby one can’t easily navigate the groups once they are over a limit of scrolling (~50).With a foldered structure it would be much more neat and understandable.
We are using Inventory report to help us find the devices that have some violation with our compliance. After finding those devices, we want to do change on them immediately to make our network work in the way we want. But we didn’t find a way to import those devices from inventory report to Change Management Node or Change Management Template. It could tremendously save our time if we could import problematic devices into CM task from inventory report or Qapp directly.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.