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's Traceroute function does not consistently apply user-specified max hops and timeout values during execution, with some device platforms disregarding these inputs entirely. This enhancement would ensure the Traceroute engine reliably enforces configured max hops and timeout parameters across all supported device types. Consistent parameter enforcement would give customers predictable, accurate trace results and reduce troubleshooting effort caused by unexpected trace behavior on specific platforms.
When a device is imported and shared across multiple domains, deleting that device in the source or parent domain does not currently remove it from the child domains where it was imported, leaving administrators to manually identify and delete the corresponding device in each destination domain. This enhancement would introduce a mechanism to automatically synchronize device deletions from the source domain to all domains that imported the shared device. Customers managing multi-domain environments with shared device imports would benefit from consistent inventory across domains and reduced manual cleanup effort.
NetBrain currently does not support use of the built-in AWS VPC Route Table data within Intent when the underlying data is obtained through NIT-based replication, limiting the ability to pull VPC routing information through standard Intent workflows. This enhancement would extend built-in data table support so that AWS VPC route table data can be accessed and used within Intent when NIT replication is in use, enabling consistent access to VPC routing information without manual workarounds. Customers managing AWS cloud environments would benefit from more complete automation coverage and improved reliability when validating VPC routing configurations.
NetBrain can currently retrieve interface data through Network Intent, such as identifying trunk interfaces and their descriptions, and compute a new value (for example, prepending a keyword to the existing description). However, there is no mechanism to take that computed, per-device result and automatically push it back to the corresponding device configuration through the Change Management module. This enhancement proposes integrating Network Intent with Change Management so that intent-derived, per-device values can be used as input for a follow-up configuration change, applied and saved across a large group of devices in a single automated workflow. Customers managing large-scale, per-device configuration updates would significantly reduce manual effort and engineering time compared to reviewing and updating each device individually.
Network Intents currently cannot reference variables or tables that were captured or computed in a parent Network Intent when a child Network Intent is executed. As a result, child intents must independently re-run commands to obtain data already available at the parent level. This enhancement would allow a child Network Intent to access select variables or tables from its parent, similar to how later canvases in a qApp can reference tables generated in earlier canvases. This would reduce redundant command execution, conserve memory in large-scale environments, and simplify troubleshooting of nested Network Intent logic.
NetBrain's Smart CLI login dialog currently provides no visible feedback once a user enters credentials and clicks OK, and the connection status display does not indicate which protocol (SSH or Telnet) is being used to reach the device. When the default protocol is Telnet and the device does not respond, users only see a generic connecting message followed by a timeout, with no indication of the protocol attempted or that the login action was received. This enhancement would add clearer in-progress feedback after credentials are submitted and would display the protocol being used during connection attempts, for example showing distinct status messages for SSH and Telnet targets. Customers would benefit from reduced confusion when troubleshooting failed or delayed Smart CLI connections, since the protocol and connection state would be visible without needing to inspect device settings separately.
NetBrain currently requires customers to provide master or management account access credentials, including access ID and secret key, in order to automatically discover and onboard AWS accounts during onboarding. Many customers consider these credentials highly sensitive and are hesitant to share them, which creates friction in the onboarding process. This enhancement proposes allowing customers to import a list of AWS accounts from a CSV or text file as an alternative onboarding method, removing the need to supply master account credentials. Customers with strict security policies around credential sharing would benefit from a safer, more flexible onboarding path that still allows their AWS accounts to be configured in NetBrain.
NetBrain currently does not notify users when they assign a PE interface IP address that already exists elsewhere in the domain or in the One IP table, nor does it warn when multiple PE interfaces within an MPLS cloud are given identical names. Both conditions can lead to inaccurate or broken topology construction without any indication to the user that a conflict has occurred. This enhancement would add validation checks during MPLS Cloud configuration that detect and notify users when an entered PE interface IP is already present elsewhere in the domain or One IP table, and when duplicate PE interface names are entered. Customers configuring MPLS Cloud objects would benefit from earlier detection of naming and addressing conflicts, reducing topology build errors and the time spent troubleshooting them.
NetBrain's Golden Config Command feature currently offers only an Enable/Disable control for the entire override set. When a customer needs to correct or add an override for a single device model, the current workflow requires disabling the entire feature, which resets all valid results to errors, and then re-enabling it, with each step taking significant time. This enhancement would introduce a (Re)Generate action scoped to a specific model within Domain Management/Advanced Settings, allowing an override update to take effect without disabling and re-enabling the full feature. This would reduce processing delays and prevent unnecessary disruption to valid results across unrelated device models, improving efficiency for customers managing overrides at scale.
NetBrain currently does not provide a way to lock a saved prompt within the Deep Diagnosis module, leaving it open to unintended edits once created. This enhancement would add a lock option for saved prompts, preventing modification unless explicitly unlocked by an authorized user. Locking saved prompts would allow administrators to safely delegate their use to junior engineers without risking accidental changes to established diagnostic logic.
NetBrain's discovery and polling processes currently depend on stable, consistently assigned IP addresses and run on a fixed twice-daily schedule, which limits accuracy in environments using dynamic addressing schemes such as CGNAT. This creates gaps in device visibility when IP addresses change more frequently than the discovery cycle can account for. This enhancement would add native support for Zscaler Zero Trust Branch architecture, including discovery and polling logic that accommodates dynamic CGNAT-assigned IP addresses, with scheduling options aligned to DHCP lease timing or FQDN-based device tracking. Customers adopting zero-trust network architectures at distributed or high-risk locations would benefit from continued network visibility and uninterrupted runbook and topology workflows during and after migration.
NetBrain does not currently provide Golden Assessment Library coverage for devices using the Dell Force10 Switch driver, preventing customers from running Deep Diagnosis and Runbook Companion assessment checks against this platform. This enhancement would extend Golden Assessment Library content to include validated support for Dell Force10 Switch devices. Customers operating Dell Force10 switches would benefit from consistent, out-of-the-box configuration compliance and assessment coverage without needing to build custom checks.
NetBrain's Golden Assessment Library currently does not include validated assessment content for devices using the Dell Networking Switch driver, leaving these devices without coverage in Deep Diagnosis and Runbook Companion workflows. This enhancement would extend Golden Assessment Library support to include Dell Networking Switch driver devices, enabling standard configuration compliance checks for this platform. Customers running Dell Networking Switches would benefit from consistent, supported assessment coverage without needing to build custom checks for these devices.
NetBrain's Golden Assessment Library currently does not include devices using the Dell EMC Switch driver, which prevents these devices from being evaluated through Deep Diagnosis and Runbook Companion workflows. This enhancement would extend Golden Assessment Library coverage to include the Dell EMC Switch driver, aligning its support with other supported device drivers. Customers operating Dell EMC switches would benefit from consistent assessment coverage across their network, without gaps in automated diagnostics for this device type.
NetBrain currently does not provide an API method to retrieve the URL of a specific Change record, which prevents that URL from being included in a corresponding ticket created in an external system such as ServiceNow. This enhancement would add an API endpoint or field that returns the direct URL to a NetBrain Change record, allowing integrations to embed that link within external change or incident tickets. Customers using automated remediation workflows that raise tickets in third-party systems would benefit from being able to navigate directly from the external ticket to the associated NetBrain Change record, improving traceability and reducing time spent searching for the corresponding change.
NetBrain Runbook nodes currently default to having the 'Use Active Cache' option checked, and there is no administrative or global setting to change this default behavior. Users must manually uncheck this option on each node to ensure data is retrieved live rather than from cache. This enhancement would introduce a configurable setting that allows administrators to control the default state of 'Use Active Cache' across Runbooks. Customers who require live-data-only execution by default would benefit from reduced manual effort and lower risk of inadvertently running diagnostics against stale cached data.
NetBrain currently does not provide a REST API capability to close a NetBrain incident based on the closure status of its corresponding ServiceNow ticket. This enhancement would introduce an API endpoint or automation trigger that closes the associated NetBrain incident when the linked ServiceNow ticket is marked closed. Customers integrating NetBrain with ServiceNow would benefit from synchronized incident lifecycle management, reducing manual effort and eliminating discrepancies between the two systems.
NetBrain currently does not provide a way to export AI analysis results, including AI Bot and Deep Diagnosis output, or runbook analysis data, in a non-editable document format such as PDF. This enhancement proposes adding a native export option that generates AI analysis and runbook analysis results as a locked, non-editable PDF file. Customers who must submit these results for internal and external audits require documentation that cannot be altered after export, and this capability would eliminate reliance on manual workarounds to meet compliance requirements.
NetBrain currently does not support discovery and mapping of AWS Kubernetes environments, resulting in gaps in topology visibility where Kubernetes-managed resources reside. This enhancement would add native discovery, modeling, and topology mapping capabilities for AWS Kubernetes clusters and their associated networking constructs, consistent with existing support for other AWS resources. Customers running containerized workloads on AWS Kubernetes would gain complete end-to-end visibility into their network architecture without encountering unmapped or unknown segments.
NetBrain currently does not offer an integration with ExtraHop for packet-level analysis during path trace operations. This enhancement would allow a path trace, when run with a specified TCP port and time frame, to invoke ExtraHop for corresponding packet analysis on the relevant path segment. Customers troubleshooting network issues would gain the ability to correlate path trace results with packet-level detail from ExtraHop, reducing the need for manual cross-referencing between tools.
Dashboard alert scheduling currently supports only fixed recurring intervals, such as every 24 hours or every 7 days, and does not allow alerts to be scheduled for specific days of the week or month at a designated time. This enhancement would add the ability to configure Dashboard alert schedules for specific weekdays or specific days of the month, paired with a designated time, such as every Monday at 8:00 AM or the first day of each month at 9:00 AM. This would allow customers to align alert notifications with their operational and reporting schedules, reducing unnecessary alerts outside of relevant business windows and improving the relevance of alert timing.
NetBrain currently does not provide a way to quickly determine everything a given application server or workstation can reach across the environment, such as destination systems, applicable firewall rules, or a visual access map. Architects and security teams must manually piece this together using multiple tools and manual analysis. This enhancement would introduce a capability, potentially leveraging automation or AI-assisted analysis, to generate a list of reachable destinations, applicable firewall rules, or a visual map of access for a specified source device. Customers responding to security and architecture review questions would gain faster, more reliable access visibility without relying on manual, time-consuming investigation.
NetBrain AI features currently send original, unmasked network data to third-party AI providers for reasoning, which prevents organizations with strict data handling requirements from enabling these features. This enhancement proposes adding pre-egress masking, tokenization, or redaction controls that protect sensitive data before it is transmitted to the third-party AI provider. Providing this capability would allow security teams to approve the use of AI-driven features while meeting internal data protection and compliance requirements.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.