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 an option to set a downward tree layout as the default arrangement for site maps. This enhancement would allow administrators to configure downward tree layout as the standard default across all site maps. Standardizing this default would improve map readability and consistency, reducing the need for manual layout adjustments each time a site map is generated or refreshed.
NetBrain currently does not provide a report that identifies the purpose or source of API calls triggered within the API Trigger Automation Manager. This enhancement would add a reporting capability that summarizes API call activity, including the intent or context behind each call. Customers managing automated integrations would gain improved visibility into API usage, supporting easier troubleshooting and audit of automation activity.
NetBrain currently allows empty Runbooks, containing no nodes beyond the Start node, to be saved and remain attached to maps, with no mechanism to identify or remove them in bulk. This enhancement would introduce a way to detect and bulk-delete existing empty Runbooks across maps, along with a safeguard that prevents new empty Runbooks from being saved with a map going forward. Customers who rely on frequently accessed maps for critical sites would benefit from a cleaner Runbook list, reducing time spent opening multiple Runbooks to identify the correct one to execute.
Service Monitor currently raises alerts whenever a monitored service is found stopped, even when the service is intentionally offline, such as a standby node in a multi-datacenter deployment. There is no mechanism to mark a service as expected to be in a stopped state so that Service Monitor can suppress alerts for it. This enhancement would allow administrators to designate specific services or devices as intentionally stopped or in standby mode, so that Service Monitor excludes them from triggering alerts while still tracking their status. This would reduce alert noise and prevent unnecessary escalation for customers running high-availability or multi-datacenter architectures where certain services are expected to remain inactive until failover occurs.
NetBrain currently requires users to move device groups into folders one at a time, selecting each group individually from a dropdown menu and choosing a destination folder. Drag-and-drop and multi-select move actions are not supported, which makes reorganizing a large number of device groups into folders a slow, repetitive task. This enhancement proposes adding multi-select capability to the device group list, allowing users to select several device groups at once and move them together to a chosen folder in a single action. This would significantly reduce the time and effort needed for customers managing large numbers of device groups, particularly when reorganizing an environment after adopting a new folder structure.
NetBrain currently does not provide a way to automatically purge or bulk delete triggered maps once they exceed a defined age, requiring users to remove outdated maps manually one at a time. This enhancement would introduce a configurable retention policy or bulk delete option that allows administrators to automatically remove triggered maps older than a specified number of days. Customers generating large volumes of triggered maps through integrations would benefit from reduced manual maintenance and better control over map repository growth.
NetBrain does not currently provide a direct method to identify all switches, trunk links, and access ports associated with a specific VLAN ID and automatically render that information as an L2 topology map. Customers must rely on manual command output review or ad hoc device grouping to approximate this view, which becomes impractical when many VLANs span multiple VRFs and does not reliably capture access port connections. This enhancement would add a capability to specify a VLAN ID and automatically generate an L2 topology map showing all associated switches, trunk interfaces, and access ports. This would give customers an efficient, accurate way to visualize VLAN-scoped L2 topology without manual workarounds, improving troubleshooting and network documentation for environments with a large number of VLANs.
NetBrain currently does not support discovery and mapping of AWS Gateway Load Balancer (GWLB) resources within cloud environments. This enhancement would add native support for GWLB, allowing the platform to discover, model, and represent GWLB endpoints and associated traffic flows in topology maps. Customers deploying GWLB as part of their AWS network architecture would gain complete visibility into their environment without manual workarounds.
NetBrain path trace currently does not allow a VPN-terminating device to be selected as the first-hop gateway when calculating the path for a VPN client, even when that device is the actual point of entry into the network. In environments where multiple gateway-capable devices exist, the path engine may default to an unrelated device, producing an inaccurate path that does not reflect real traffic flow. This enhancement would allow the path trace engine to correctly identify and offer the actual VPN-terminating device as a selectable gateway option for VPN client path calculations, ensuring the resulting path reflects the true routing behavior. Customers relying on path trace for VPN troubleshooting would gain accurate, end-to-end visibility without needing to manually correct or reinterpret an incorrect calculated path.
NetBrain currently does not reliably complete Path node execution when it is included as part of a scheduled network change task, causing the live post-change path to fail to generate. In addition, when both pre-change and post-change paths are captured, the resulting report does not clearly separate or distinguish the two paths from one another. This enhancement would ensure that Path nodes execute consistently within scheduled change workflows and would present the pre-change and post-change path results as distinct, clearly labeled sections in the generated report. Reliable path execution and clear before-and-after comparison would give customers confidence in validating the network impact of scheduled changes without manual follow-up.
NetBrain path trace currently does not support multicast path calculation on Juniper routers, limiting visibility during multicast troubleshooting scenarios. This enhancement would extend the path trace engine to recognize and correctly compute multicast paths across Juniper devices. Customers troubleshooting multicast traffic in mixed-vendor environments would gain complete, accurate path visibility without needing manual workarounds.
In Multi-Vendor Support, Vendor Model, when you add a new SysObjectID, please sort the list of vendors alphabetically without differentiating between upper case and lower case letters. In this list, APC comes before Acgate and CXR Telecom comes before Cisco.Capital letters (upper case) are generally considered to be identical to their corresponding lower case letters for the purposes of alphabetical ordering, as in this case.I also found the vendors Allen-Bradely and Allen-Bradley in this list, surely one of them is a typo.
On the maps, the devices are shown with host name, IP and device type but device type is not very informative e.g. “Cisco IOS Switch”. It would be much better to show the model like “C9500-40X”.
Currently, the change analysis reports shows diff in UTC time zone. is there any way where we can have it in IST Time zone.
Hi,I have several scheduled Qapps searching for various kinds of errors. When the result is empty, meaning the qapp ran but no error was found, there is no CSV published. Instead of providing no information which could be interpreted as a Qapp error, please provide confirmation that the Qapp ran successfully but no result was produced.
Smart CLI would be much more useful if it was possible to :Open a connection to multiple devices at once (e.g. select multiple devices on a map, right-click and choose “Smart CLI”). Send a command to multiple devices at once.
In order to understand which devices are properly onboarded to NetBrain (via either SSH access, API access or other means that guarantee full visibility for a device in NetBrain) and which aren’t, one way to check is by using Domain Management => Operations => Advanced Tools => Tune Live Access.However, all the benefits of this tool/functionality are negated by the fact that the output is not exportable to e.g. a CSV file.Can you please address this gap or suggest other ways to check which devices are fully onboarded to NetBrain and which aren't (i.e. visible via SNMP polls only or ping only but not SSH/API access)?
Per NB DEV team, if there’s more than 1 entry for a given IP, the old one will be considered first as it was inserted into the DB first…Which doesn’t make sense because the most recent record from One-IP table should be used for every endpoint.Can the above mentioned behavior be changed somehow?
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.