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.
The Runbook Ping node currently limits selectable target IPs to a device's known interface addresses, with no option to specify a management IP that falls outside those interfaces. This becomes a limitation when a device's management IP is reached through NAT translation, since none of the listed interface IPs are actually reachable for connectivity testing. This enhancement would allow the Ping node to accept and target a device's management IP directly, even when that IP is not one of the device's native interface addresses. Supporting this option would allow customers with NAT-translated management access to run accurate connectivity checks within Runbooks, reducing manual workarounds and improving diagnostic reliability.
NetBrain currently does not reliably assign devices discovered through multiple AWS API endpoints or accounts to their corresponding site group, even when an existing site definition should match them. Affected devices are left unassigned rather than being placed into the expected site or the default Unassigned Devices group, making it difficult for administrators to locate and organize newly discovered cloud resources. This enhancement would ensure that site-assignment logic correctly evaluates devices discovered from every configured AWS API endpoint against defined site rules, placing matching devices into the appropriate site group during discovery. Customers managing multiple AWS accounts would gain consistent, predictable site organization for cloud resources, reducing manual remediation and improving confidence in topology and inventory accuracy.
Triggered Automation Framework currently does not allow users to export task information filtered to a specific, user-selected time range, nor does it provide a count of tasks that fall within that range. Reviewing task activity for a defined period requires manual inspection of the full task list. This enhancement proposes adding two capabilities to Triggered Automation task views: an export option that generates task detail limited to a selected time range, and a count display that shows the number of tasks matching that same time range. These additions would give customers a faster way to review, report on, and audit automation activity for a specific period without manually filtering or counting task records.
NetBrain currently does not provide a way to schedule Ansible tasks and incorporate their results into preventive automation workflows in the same manner that flash probes are scheduled and evaluated today. Customers who rely on Ansible for prechecks, such as collecting software version data, must manage that automation outside of NetBrain and cannot use it to drive conditional actions within the platform. This enhancement would allow Ansible tasks to be scheduled and integrated into preventive automation logic, so that task output, such as version compliance results, can trigger downstream actions like automated change scheduling for non-compliant devices. This would allow customers already standardized on Ansible for network validation to extend their existing automation investment into NetBrain's proactive monitoring and change workflows, reducing duplication of effort across tools.
NetBrain's discovery and benchmark drivers currently rely on the 'show running-config' command, which requires privilege level 15 access on Cisco devices. Some customers manage devices under restricted local accounts with lower privilege levels, where this command cannot be permitted, even though the more limited 'show running-config view full' command is available to them. This enhancement would introduce a driver option to retrieve device configuration using 'show running-config view full' as an alternative to the standard command, configurable in a way that does not affect other tenants or customers in shared, multi-tenant environments. This would allow customers who do not have full administrative access to devices, such as during a transition between service providers, to complete discovery and benchmarking using a reduced set of permitted commands.
When Gateway Fix-Up rules correctly resolve a path, the map visualization does not reflect this resolution and continues to display the affected end node as disconnected from the fix-up device. This creates a mismatch between the accurate underlying path calculation and what is shown to the user on the map. This enhancement would update the map rendering logic so that, when a Gateway Fix-Up rule successfully resolves a node's connection, the visualization displays the node as properly connected to the fix-up device. Consistent visualization would give customers confidence that the displayed map accurately reflects the calculated path, reducing confusion and unnecessary manual verification.
NetBrain currently requires direct network connectivity to managed devices for SNMP, CLI, ICMP, and REST API access, with no supported mechanism to route these protocols through an intermediary proxy. This enhancement would add configurable proxy support for each of these access methods, allowing NetBrain to reach devices in environments where direct connections are restricted or unavailable. Customers operating in segmented or security-restricted network environments would benefit from broader device visibility and management without requiring architectural changes to their existing access controls.
NetBrain currently discovers virtual systems, such as virtual appliances created on top of physical chassis or virtualized application instances, without providing a way to distinguish them from their physical counterparts. Customers must manually investigate each device type or driver to determine whether a discovered system is physical or virtual, which makes it difficult to report accurately on infrastructure composition. This enhancement would introduce a device attribute, such as a boolean flag, indicating whether a discovered device is physical or virtual, applied consistently across supported device types and drivers. Customers would benefit from the ability to quickly identify and report on the proportion of physical versus virtual devices in their environment without performing manual, per-device-type investigation.
NetBrain currently limits site map membership for Azure-based infrastructure to VMware and Azure MSEE device types, which prevents other Azure resources from being represented in site maps. This enhancement would extend site map support to include additional Azure device and resource types, allowing them to be discovered and added to site definitions alongside existing supported types. Customers managing Azure environments would gain more complete visibility into their cloud infrastructure directly within NetBrain site maps, improving overall network management for hybrid and cloud-based deployments.
NetBrain currently does not provide a way to automatically trigger a Benchmark task immediately upon completion of a Scheduled Discovery task. Administrators who need both tasks run in sequence must monitor Discovery completion and manually initiate the Benchmark task afterward. This enhancement proposes allowing a Benchmark task to be configured to run automatically once a linked Scheduled Discovery task concludes, without requiring manual initiation. This would reduce administrative overhead and optimize execution time for customers who routinely need Discovery and Benchmark results processed back to back.
NetBrain currently does not consistently report configuration retrieval status as "Succeeded via SNMP" when SNMP retrieval succeeds but CLI retrieval fails, differing from prior behavior customers relied on. This enhancement would restore the status display so that a successful SNMP-based configuration retrieval is clearly reflected even when CLI access fails for the same device. Customers depend on accurate status reporting to distinguish partial access success from full failure, and inconsistent labeling can lead to unnecessary troubleshooting and confusion about device accessibility.
NetBrain currently does not provide a way to export device search results directly from the search interface. Users must first add the matching devices to a Device Group before they can export the list, which adds an unnecessary manual step for simple lookups. This enhancement would add an export option directly on the search results view, allowing users to export the full list of matching devices without first creating a Device Group. Customers who search frequently would benefit from faster access to device lists for reporting, auditing, and troubleshooting purposes.
NetBrain currently allows a Benchmark task to be triggered automatically after a manual Discovery completes, but this option is not available for Scheduled Discovery tasks. Administrators running scheduled discoveries must manually initiate or schedule a separate Benchmark task rather than having it launch automatically upon discovery completion. This enhancement would extend the auto-trigger capability so that a Scheduled Discovery task can automatically initiate a Benchmark task once the discovery run finishes, consistent with the existing manual discovery workflow. This would reduce manual coordination between discovery and benchmark scheduling and help ensure benchmark data stays current without requiring an administrator to monitor scheduled discovery completion times.
NetBrain currently returns device configuration through the API as a single, complete configuration file, with no option to retrieve only a specific portion of that configuration, such as routing protocol sections, access control lists, interface settings, or global configuration blocks. This limitation requires consumers of the API to parse the full file themselves to isolate relevant sections, adding overhead to automation and integration workflows. This enhancement proposes segmenting device configuration into logical categories aligned with common configuration areas and providing an API parameter or endpoint to retrieve a specific segment rather than the entire file. Customers building automation around configuration auditing, compliance checks, or targeted analysis would benefit from more efficient data retrieval and reduced parsing effort on their end.
When a device is configured with only a Privilege password and no Privilege Username, the Privilege Username field in Shared Device Settings displays as empty, giving users no visual confirmation of which credential alias is currently selected. This enhancement would display the associated Alias in the Privilege Username field whenever no explicit username is configured, so the selected credential set remains visible. Customers troubleshooting device connectivity would gain clarity on which credentials are active without needing to modify shared settings that could affect other devices using the same profile.
NetBrain path calculation for Cisco ACI fabrics can currently include leaf switches from a data center or pod that is not part of the actual traffic path, producing a calculated path that does not reflect real forwarding behavior across multi-site or multi-pod ACI deployments. This enhancement would extend the path calculation logic to recognize pod and site boundaries within an ACI fabric, ensuring that only leaf switches within the correct data center are included in the calculated path. Customers operating multi-DC ACI environments would gain accurate path visibility, reducing confusion during troubleshooting and eliminating the need to manually verify which data center the calculated path actually traverses.
NetBrain's path calculation API currently returns only a general failure reason and the IP pair between which a path failed, without exposing the specific security group, checkpoint rule, or other blocking detail that the Web UI displays for the same failed path. This creates a gap between the level of diagnostic detail available through the UI and what is accessible programmatically. The API should be enhanced to return the same detailed blocking information available in the UI, including the specific rule or object that caused the failure at the relevant hop. Customers automating path validation and troubleshooting through the API would gain the ability to pinpoint the exact cause of a path failure without needing to cross-reference results in the Web UI, improving efficiency for automated network verification workflows.
NetBrain currently displays EPG information in the NCT table for ACI environments but does not surface related Bridge Domain or subnet details for a given IP address. This enhancement would add Bridge Domain and subnet columns to the NCT table and make this data searchable through global search. Customers managing ACI fabrics would gain faster access to Bridge Domain and subnet context during troubleshooting, reducing the need to cross-reference separate tools.
NetBrain currently does not provide a function or ADT option that returns whether a device connection was established using SSH or Telnet. As a result, automation and remediation scripts cannot conditionally verify the login protocol before taking action on a device. This enhancement would introduce a callable function or ADT option that returns the protocol used for the current device session. Customers enforcing security policies that require disabling Telnet only on devices confirmed to use SSH would be able to automate this validation safely, reducing the risk of losing connectivity to devices where SSH is not functioning.
Runbook input fields currently present as small, single-line text boxes with a limited character capacity, which restricts the amount of detail a user can enter when populating fields for integrations, such as third-party change request systems that support longer text entries. This enhancement would enlarge the input field display to span multiple rows and increase the supported character limit to align with common third-party field capacities. Customers would gain the ability to enter detailed implementation plans, justifications, and other extended information directly within Runbook inputs without truncation or workaround.
NetBrain currently does not provide a way to export Cisco ACI license consumption details, including which ports are consuming licenses. This enhancement would add an export capability for ACI license usage that lists port-level license consumption alongside existing license summary data. Customers managing ACI environments would benefit from improved visibility into license allocation, enabling more accurate license audits and capacity planning.
NetBrain currently does not allow administrators to disable notification or admin-level email alerts for a specific individual user while leaving that user's automatic update functionality intact. Email settings are managed in a way that does not separate notification preferences from update processing on a per-user basis. This enhancement would introduce a user-level setting that allows an administrator to disable notification and admin email alerts for a designated user account without impacting that user's automatic update process. This would give organizations greater flexibility to manage email preferences for specific roles, such as executive or admin-level users, without disrupting core system functionality.
NetBrain currently supports exporting Visio site maps to local or on-premise file locations, but does not provide an option to export directly to a Box cloud storage share path. This enhancement would add Box as a configurable destination for both manual and scheduled Visio site map export tasks. Customers who rely on Box for centralized document sharing would be able to automate distribution of network diagrams without manual file transfer steps.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.