🎟️ Win a Free Pass to NetBrain Live 2026!
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.
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.
I would like to suggest for consideration to add option remediate to configlet. So we can not only check all golden rules that apply for certain device, but also remediate them.NetBrain Case #00182577
Our organization restrict access to Public AI Models ( Open AI / ChatGPT etc.) for privacy and security concern. Is there any way where we can integrate the NetBrain with Internal / On prem AI model.
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.
In v8 we were able to remove multiple commands at once using Ctrl-click, and do it for multiple devices simultaneously.In v10 we can only remove the commands one by one, and need to repeat it for every device in the list.Can we please go back (or have an option to switch) to v8 functionality when it comes to executing batch CLI commands?
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.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.