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 currently does not provide validated support for installing or operating on Rocky Linux, which limits customers who need to move off CentOS as it approaches end of support. This enhancement would extend NetBrain server installation and runtime support to include Rocky Linux as a supported operating system, along with documented guidance for migrating an existing database and deployment from CentOS to Rocky Linux. Customers modernizing their infrastructure would be able to complete the operating system transition without disrupting their existing NetBrain environment.
Service Monitor currently does not provide a way to track RabbitMQ pending message counts or notify administrators when queue backlog exceeds an acceptable level. This enhancement would add a configurable threshold for RabbitMQ pending messages within Service Monitor, along with automated notifications when the threshold is exceeded. Customers would gain earlier visibility into message processing backlogs, allowing them to address underlying issues before they impact system performance or availability.
NetBrain currently does not support discovery of Azure Operator Nexus (Carrier-Grade Infrastructure), a newer Azure service used to host carrier network functions in the cloud. This enhancement would add the ability to discover and map Operator Nexus node types, topologies (such as L2, L3, and overlay), and traffic types (including unicast, multicast, and high-availability paths). Customers operating carrier-grade workloads in Azure would gain full visibility into their hosted services alongside existing Azure cloud infrastructure already modeled in NetBrain.
NetBrain's Benchmark results currently list devices in the 'Devices with retrieval failures' table when certain commands fail during data retrieval, even if those commands are only applicable in a global context or a specific VDOM and the overall retrieval status shows succeeded. This creates confusion, as customers see devices flagged as failures without a clear indication that the underlying data was retrieved successfully. This enhancement would refine command scoping logic for multi-VDOM firewalls so that VDOM-specific or global-only commands are correctly evaluated per context, and would exclude devices from the failure table when no genuine retrieval or processing issue exists. Providing accurate failure reporting would reduce unnecessary investigation effort and improve customer confidence in Benchmark results for multi-vendor, multi-VDOM environments.
NetBrain's QApp Python scripting environment currently has no built-in method for a script to write its output directly into the platform's Public or Private file folders; any generated files must be handled and stored outside of NetBrain. This enhancement proposes adding a Python API function within the QApp scripting context that allows a script to save output files directly to a specified Public or Private folder. This would let customers persist automation output within NetBrain for future reference and reuse without relying on manual file transfer steps.
Custom reports currently stop generating once output reaches 100,000 lines, preventing users from viewing or exporting complete results when the underlying data set is larger. This enhancement would make the report line limit configurable, allowing administrators to raise the threshold to accommodate larger data sets. Customers working with large-scale environments would benefit from complete, accurate reporting without truncation or the need for manual workarounds to piece together full results.
NetBrain currently allows Inventory Reports to be generated and exported manually, but there is no option to schedule recurring report generation or have the results automatically delivered by email. This enhancement would add a scheduling capability for Inventory Reports, allowing users to configure a report to run on a recurring basis, such as quarterly, and be automatically emailed to designated recipients. This would support audit and compliance workflows by providing a reliable, time-stamped record of report delivery without requiring manual export or screenshot capture.
NetBrain currently applies a fixed default protocol (IPv4 with UDP/TCP) for path calculation, and this default applies uniformly to all users without any administrative control over it. This can produce results that are misleading when a policy match is evaluated against a protocol that does not reflect the traffic type the user actually intends to analyze. This enhancement would allow administrators to configure the default protocol and port used for path calculation, such as ICMP or TCP on port 443, so that the system-wide default better reflects common troubleshooting scenarios. Customers would gain more accurate and predictable path calculation results out of the box, reducing confusion around policy match outcomes and the need for users to manually adjust protocol settings on each path calculation.
NetBrain currently displays a protocol label in path trace denial results that does not accurately reflect the underlying evaluation logic. When IPv4 is selected without specifying a transport protocol, the path denial message states that the path was denied by a matched TCP/UDP policy, even though no specific transport protocol was actually evaluated or matched. This enhancement would correct the displayed wording to accurately represent the matching logic used, such as labeling the result as IP-based or indicating that any protocol is permitted when no specific transport protocol is selected. Accurate labeling would help customers correctly interpret path trace results and avoid misdiagnosing policy behavior during troubleshooting.
NetBrain currently renders SD-WAN connectivity between nodes as a full mesh of individual tunnel links on topology maps, which can make maps with many SD-WAN edge devices difficult to read and interpret. This enhancement would allow SD-WAN tunnel connectivity to be consolidated and displayed as a single SD-WAN cloud object, similar to how other cloud-based network types are represented. Customers mapping SD-WAN environments would benefit from cleaner, more readable topology maps that better reflect the logical SD-WAN fabric rather than a dense mesh of point-to-point tunnel links.
NetBrain currently reloads the Script Manager window and resets it to its default state whenever a user switches away to another browser tab and then returns, causing the prior view or working state to be lost. This enhancement would allow Script Manager to retain its last active state so that returning to the tab restores the window as it was left. Preserving this state would reduce disruption to users working across multiple tabs and eliminate the need to manually re-navigate to their prior position within Script Manager.
NetBrain currently does not provide a way to search for objects directly within the Check Point ACL policy table, requiring manual review of table entries to locate specific objects. This enhancement would add search functionality that allows users to query and locate objects within the Check Point policy table. Customers managing Check Point firewall policies would benefit from faster identification of relevant rules and objects, reducing manual effort during policy review and troubleshooting.
NetBrain's audit log currently provides limited information about incident portal usage, making it difficult for administrators to determine which user accessed a given incident, or which tenant and domain an incident belongs to when accessed through the portal URL, whether authentication is performed via user account or access code. This enhancement would expand audit logging, or provide a query capability, to capture incident portal access details including the authenticated user (when applicable), the access code used (when applicable), and the associated tenant and domain for each incident accessed. Administrators would benefit from improved visibility into portal-based incident access, supporting security review and compliance reporting across tenants and domains.
NetBrain path calculation currently does not correctly resolve paths across Cisco's IP Fabric for Media solution, resulting in discovery failures for this architecture. This enhancement would extend path calculation logic to properly recognize and traverse IP Fabric for Media topologies, ensuring accurate end-to-end path results. Customers operating media transport networks on this Cisco solution would gain reliable path visibility for troubleshooting and validation, removing the need for manual workarounds.
NetBrain path calculation currently does not evaluate or carry forward Layer 2 QoS DSCP markings established at the first hop, so downstream L3 routers and SD-WAN devices such as Viptela are not assessed for DSCP inheritance during path analysis. This enhancement would extend the path calculation engine to check the L2 QoS DSCP value at the first hop and verify that it is correctly inherited by subsequent L3 or SD-WAN devices along the calculated path. Customers relying on QoS-based traffic prioritization would gain accurate end-to-end path visibility into DSCP handling, improving confidence in SLA compliance and reducing manual verification during performance troubleshooting.
NetBrain path calculation logic currently does not correctly account for Layer 2 QoS configuration on certain Cisco switch and Viptela SD-WAN platforms, which can produce a path that does not reflect actual network behavior when QoS policies are applied at Layer 2. This enhancement would update the path calculation parsing logic to correctly recognize and incorporate Layer 2 QoS settings for these device types, ensuring the calculated path reflects real traffic handling. Customers relying on path calculation for QoS-sensitive troubleshooting would gain accurate path visibility, reducing the need for manual verification of QoS behavior outside the tool.
NetBrain currently may fail to correctly detect and populate vendor and model information for certain devices added through configuration file import, which in turn prevents accurate topology link calculation for those devices. This enhancement would improve the parsing logic used during configuration file import to reliably extract vendor and model attributes, ensuring devices are properly identified and topology links are calculated correctly. Customers who rely on configuration file import for devices without direct CLI or SNMP access would benefit from more accurate device inventories and complete topology visibility without manual correction.
NetBrain currently exposes a Last Discovery Time field that reflects the most recent discovery attempt for a device, regardless of whether that attempt succeeded. As a result, users cannot rely on this field to determine when a device was last successfully accessed and its data confirmed current. This enhancement proposes adding a distinct, reportable field for Last Successful Discovery Time (or Last Successful Access Time), populated only when discovery completes successfully for a device. Customers managing large device inventories would gain a reliable way to identify devices with stale or unconfirmed data, supporting more accurate reporting and targeted troubleshooting of access failures.
NetBrain currently does not provide a way to export the full list of system users along with their assigned roles in a structured file format such as CSV or XML. This enhancement proposes adding an export capability for the user list, including each user's assigned role, accessible from user management. Customers managing large user populations would benefit from a faster, more reliable way to support periodic access audits and compliance reviews without manually cross-referencing user records.
NetBrain's compare function currently supports comparing device configuration data only, with no option to compare CSV files generated as QApp output. This enhancement proposes extending the compare function to allow selection and comparison of QApp-generated CSV outputs, similar to how configuration comparisons are handled today. Adding this capability would give customers a consistent way to identify differences across QApp results over time, supporting troubleshooting and change validation workflows.
NetBrain currently limits Device Access Policy privileges to two broad options: View Network Data and Execute Network Change. Administrators cannot assign more granular permission levels within this policy to distinguish between varying degrees of network data access or change execution. This enhancement would introduce additional, more granular privilege tiers within Device Access Policy, allowing administrators to define finer-grained access levels beyond the current two options. Customers with complex organizational access requirements would benefit from more precise control over which users can view or modify specific types of network data, supporting stronger adherence to least-privilege access principles.
NetBrain currently does not allow users to export the list of devices along with their configured credentials, aliases, usernames, vendor, and IP address directly from the Network Setting window. Users must first add devices to a Device Group and export from there, which adds extra manual steps for a straightforward reporting need. This enhancement would add a direct export option within the Network Setting window that includes device identity and credential details, along with an option to trigger device rediscovery from the same view, similar to the rediscovery workflow available in Fine Tune. Customers performing credential audits and compliance reviews would benefit from faster, more direct access to this information without navigating through Device Group creation.
NetBrain does not provide a way to automatically detect or recover a Front Server whose status remains stuck in "Checking" within the portal, even after the server and its services are restarted. Administrators currently have no built-in diagnostic or self-healing mechanism to resolve this condition and must rely on manual troubleshooting. This enhancement would introduce automated detection of a Front Server remaining in a "Checking" state beyond an expected threshold, along with a recovery action or clear diagnostic guidance to resolve the condition. Customers would benefit from reduced downtime and less manual intervention when Front Server status monitoring fails to update correctly.
NetBrain global search currently requires an IPv6 address to be entered with its subnet mask, such as in CIDR notation, in order to return results; a plain IPv6 address without a mask does not return a match, unlike IPv4 addresses, which can be searched without a mask. This enhancement would extend global search to recognize and return results for IPv6 addresses entered without a subnet mask, bringing IPv6 search behavior in line with IPv4. Customers working in IPv6 environments would be able to locate devices and interfaces by address more efficiently, without needing to know or supply mask information during troubleshooting.
NetBrain currently does not provide an email notification indicating when a network change execution begins and when it completes. Users must manually monitor the change process to confirm whether it started and finished successfully. This enhancement would introduce automatic email alerts triggered at the start and end of a network change execution, including an indication of success or failure. Customers running network changes would gain timely confirmation of execution status without needing to manually track progress, improving change management visibility and reducing operational risk.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.