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 validate or account for cases where multiple provider edge devices use interfaces with the same name, which can cause the platform to incorrectly resolve L3 link endpoints and produce an inaccurate topology map. This enhancement would add logic to detect duplicate interface names across devices during L3 topology calculation and either enforce interface name uniqueness or correctly disambiguate links using additional attributes such as IP addressing or device context. Customers managing large multi-vendor or multi-tenant environments would benefit from accurate automated topology mapping without needing to manually identify and correct link errors caused by naming collisions.
NetBrain's discovery process can select a shared or virtual IP address, such as a VRRP address, as a device's management IP even when a unique IP address is also available for that device. Because a shared IP does not reliably identify a single device and may move between devices over time, this can lead to configuration retrieval failures and inconsistent device identification during troubleshooting. This enhancement proposes adding logic to the discovery process that prioritizes a unique IP address over a shared or virtual IP whenever both are available, avoiding reliance on shared addressing for device identification. Customers would benefit from more reliable device identification and configuration retrieval, and would no longer need to manually lock management IP settings on individual devices as a workaround, reducing administrative overhead and preserving discovery automation.
NetBrain does not currently retain customized Front Server configuration settings when the platform is upgraded, causing administrators to lose prior customizations and requiring manual reapplication after each upgrade. This enhancement would ensure that Front Server configuration settings persist through the upgrade process, whether by preserving the existing configuration file or by reliably merging it with any new default settings introduced by the upgrade. Maintaining configuration continuity across upgrades would reduce post-upgrade reconfiguration effort and lower the risk of misconfiguration or service disruption after an upgrade.
NetBrain currently provides no visual indication on the map when the Active Path option is selected during path calculation, making it difficult for users to confirm which path mode is currently applied while reviewing results. This enhancement would add an icon or similar visual marker on the map to clearly denote that Active Path selection is in effect. Providing this indicator would help customers quickly confirm the path mode being displayed, reducing confusion and manual verification during troubleshooting.
NetBrain currently displays path detail information for all branches together when a path calculation returns multiple branches, requiring users to manually scan through unrelated branch details to locate the one of interest. This enhancement would allow a user to click a specific path branch on the map and have the Path Detail panel automatically update to show only the information relevant to that selected branch. Customers troubleshooting paths with many branches would be able to isolate the target branch more efficiently, reducing the time spent manually searching through unrelated path detail logs.
NetBrain currently requires users to manually identify and open the appropriate Runbook and populate it with the relevant devices and commands whenever an alert occurs on a path or map, even when the same alert condition has occurred previously and a suitable Runbook template already exists. This enhancement would allow NetBrain to recognize a recurring alert condition and automatically open the associated Runbook template, pre-populating the relevant devices and commands so that an engineer only needs to review and click Run. Customers experiencing repeated or recurring network alerts would benefit from faster response times and would no longer need to reconfigure a Runbook each time a familiar issue recurs.
The OneIP Table currently does not support a way to permanently remove specific IP address entries from the active view. When a user manually deletes an entry, it reappears after the next benchmark task runs, since the underlying data remains in the system and is re-populated into the table. This enhancement proposes allowing users to mark selected IP addresses for permanent exclusion from the active OneIP Table, while preserving the associated historical data as versioned records for audit retrieval. Customers operating under compliance requirements that mandate multi-year historical retention would benefit from maintaining an accurate, up-to-date table view without losing access to historical data needed for audits.
NetBrain does not currently provide a way to verify network connectivity and service health across all servers before or during a System Update, requiring administrators to manually check each server individually, which becomes impractical in environments with many servers. Update failure logs also do not clearly identify the root cause when a required connection or service check fails. This enhancement would add a connectivity and service health test feature, accessible from the Server Monitor or System Update page, that checks required connections and service status across all servers and displays the results directly in the UI. Update failure logs would also be enhanced to surface root causes more clearly. This would reduce manual troubleshooting effort and help administrators identify and resolve update issues faster, particularly in larger multi-server environments.
Configuring and maintaining Golden Baseline and Network Intent checks today requires customers to manually define specific thresholds and rules for what constitutes a deviation from normal behavior. This setup and ongoing maintenance can be complex, particularly for customers who want to detect meaningful changes without specifying exact numeric or logical criteria in advance. This enhancement would introduce a machine learning-based option for Golden Baseline and Network Intent that automatically learns normal network behavior and flags deviations without requiring manually defined thresholds. Customers would benefit from reduced setup and maintenance effort while gaining more adaptive and accurate detection of meaningful changes in their network environment.
NetBrain currently does not retain manually applied server-side customizations, such as Front Server configuration adjustments or worker server memory settings, when the system is upgraded. As a result, administrators must rediscover and reapply these changes after every upgrade, and the details of prior adjustments are often not documented anywhere in the system. This enhancement proposes a mechanism to capture, preserve, and automatically reapply approved server-level customizations across upgrade cycles, or at minimum to surface a record of prior changes so they can be reapplied efficiently. Retaining these settings would reduce repeated troubleshooting effort and prevent recurring downtime for customers who rely on tuned server configurations for expected system performance.
NetBrain currently allows users to exclude an entire device or device group from data retrieval, but there is no option to exclude a specific table for select devices while still retrieving other data for those devices. This enhancement would add the ability to configure table-level exclusions on a per-device basis, allowing a problematic table to be skipped for specific devices without disabling data collection entirely. Customers who encounter recurring issues with a particular table on certain devices would benefit from more granular control, reducing unnecessary retrieval failures while preserving visibility into other relevant device data.
NetBrain currently does not provide a way to export a path calculation result, along with its associated snapshot, into a shareable document format such as Word or Visio. This enhancement proposes adding an export option that captures the path result and its snapshot directly into Word or Visio output. Customers would benefit from being able to share path analysis findings with colleagues who do not have access to the NetBrain client, reducing dependency on live sessions for collaboration and review.
NetBrain currently does not include system version, release, knowledge base, and license identification details within collected log files. Troubleshooting often requires this information, and support teams must gather it manually from the About NetBrain window. This enhancement would automatically capture and include these details in exported logs. Customers would benefit from faster and more complete log collection during troubleshooting, reducing the need for manual data gathering.
NetBrain currently requires users to select a parser and re-define intent logic separately for each device when building a Network Intent, even when the same logic should apply across many devices. There is no streamlined way to define a Network Intent once and apply the identical parser and definition to a list of devices, a device group, or similar device selections in a single step. This enhancement would allow a Network Intent to be created and configured on one device, then applied directly to additional devices selected from a list or device group, reusing the same parser and definition without manual re-configuration. Reducing repetitive setup would improve the efficiency of building Network Intents at scale and increase the practical value of intent-based automation for customers managing large device inventories.
NetBrain currently documents username and password format limitations for database and Linux components only in reference documentation, which many users do not review in full before installation or upgrade. As a result, invalid credentials are frequently entered, leading to deployment and upgrade failures that require support intervention. This enhancement would surface the applicable username and password limitations directly on the interactive installation page, near the corresponding input fields, so users see the constraints at the point of entry. Making this information visible during setup would reduce avoidable deployment blockers and lower the support effort associated with resolving invalid credential issues.
NetBrain currently has no automated mechanism to detect and retrigger devices that fail discovery due to accessibility or similar issues; failed discoveries require manual identification and re-initiation, which can cause the live inventory to drift out of sync with actual network state. This enhancement proposes introducing a flag-based tracking mechanism that records the success or failure state of each device discovery attempt and automatically retriggers discovery for devices flagged as failed, without requiring manual intervention. Customers managing large or frequently changing environments would benefit from improved inventory accuracy and reduced operational overhead from manually tracking and re-running failed discoveries.
NetBrain currently evaluates full firewall policy logic as part of every path calculation, which can significantly increase calculation time, particularly in environments with large or complex rule sets. This enhancement would introduce an optional mode that bypasses firewall policy checks and evaluates only routing reachability through the firewall, while still allowing the ignore strategy to be specified when calculating paths through the API. Customers who need faster path results and do not require policy-level detail for a given analysis would benefit from significantly reduced calculation time without sacrificing the ability to perform full policy-aware analysis when needed.
NetBrain's IP Conflict Detection feature currently determines duplicate IP conflicts using only the IP address combined with the interface GDR attribute. This approach cannot accurately identify a true duplicate IP conflict occurring between unrelated devices, and simply removing the GDR condition would cause legitimate HA and Anycast peer IP addresses to be incorrectly flagged as conflicts, which would also disrupt topology connection accuracy. This enhancement proposes refining the duplicate IP detection logic to incorporate additional differentiating attributes, such as device role or peer relationship context, so the system can reliably distinguish genuine IP conflicts from valid redundant addressing patterns like HA and Anycast pairs. Customers would benefit from more accurate conflict alerts and reduced false positives, improving confidence in network monitoring and topology accuracy.
NetBrain currently does not provide a Python API method to programmatically retrieve the config change and rollback command list defined within a Change Management change definition. This limits the ability of external systems to consume or act on this data without manual export or UI-based review. This enhancement would introduce a Python API function that returns the config change and rollback command list for a given change definition, allowing external platforms to retrieve this data directly. Customers integrating NetBrain with ticketing or IT service management platforms would gain the ability to automate the transfer of change and rollback commands into their existing workflows, reducing manual effort and improving change tracking.
NetBrain currently does not notify administrators when a user's assigned role or permission set changes, including changes that occur indirectly through SSO or identity-provider role mapping. Administrators must manually cross-reference multiple systems to detect that a user's effective permissions have changed, and there is no record of which account initiated the change. This enhancement would introduce an alerting mechanism that notifies designated administrators whenever a user's role or permission mapping changes, along with a record of the account that triggered the change. This capability would help organizations detect unauthorized privilege escalation, maintain continuity when administrative responsibilities transfer between staff, and support ongoing security and compliance review without manual investigation across systems.
NetBrain currently offers no mechanism to update Automated Data Tables (ADTs) or Network Intents that reference a device hostname once that hostname has changed. When a hostname is renamed, any ADT or Intent tied to the prior hostname becomes invalid, and administrators must manually recreate the affected objects rather than update the existing reference. This enhancement would introduce a refactoring capability that allows ADT and Intent definitions to be updated to reflect a renamed hostname while preserving the underlying logic and configuration. Customers who periodically rename devices would benefit from reduced administrative effort and avoid the risk of losing established automation work.
Dynamic Search currently strips special characters, such as '#', from search terms before matching, causing the search to return results based on the remaining substring rather than the exact term entered. This enhancement proposes updating Dynamic Search to preserve special characters during matching so that a term such as 'link#' returns only exact matches rather than all results containing 'link'. Customers searching for device or interface names that include special characters would receive precise results and avoid manually filtering out unrelated matches.
Hostname matching used in batch and site definitions is currently case sensitive, so devices whose hostname casing differs from the defined criteria can be excluded even when a definition is intended to cover all devices. This causes benchmark queries scoped to 'All Devices' to omit devices unexpectedly, without any indication to the administrator that a case mismatch is the cause. This enhancement would make hostname matching case-insensitive across batch and site definitions used in Benchmark and related queries. Customers would gain more reliable and predictable device coverage in their benchmark and discovery operations without needing to manually verify hostname casing.
NetBrain discovery currently does not support authenticating to devices using SSH public key credentials; only standard username and password based authentication is supported for establishing device sessions during discovery. This enhancement would allow administrators to configure and apply SSH key-based authentication (including specifying a private key file) as a valid credential method for device discovery. Customers whose network devices are configured to require or prefer public key authentication would be able to complete discovery successfully without falling back to less secure or unsupported authentication methods.
The Domain Accuracy Resolution view does not currently display the serial number for devices that are inaccessible or newly discovered, and users cannot customize which device attributes appear in this view. This enhancement would add serial number as a visible field for inaccessible and discovered devices, and would allow users to select and arrange the attributes shown in the view according to their own preferences. Customers managing large device inventories would benefit from faster device identification and a view tailored to their specific troubleshooting and reporting needs.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.