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 path calculation currently displays standby (passive) firewall devices in path results even though these devices do not carry live traffic, since failover has not occurred. This can create confusion when reviewing a path, as the standby device appears as an active hop despite not participating in actual traffic flow. This enhancement would allow path calculation to identify standby firewalls and exclude them from the displayed path result, regardless of branch or topology. Customers troubleshooting network paths would gain a more accurate representation of real traffic flow, reducing the time spent distinguishing active devices from standby ones during analysis.
NetBrain's webhook follow-up action currently does not support inserting variable values, such as an OAuth token, into the HTTP headers of an outbound webhook call. As a result, integrations that require token-based authentication in the request header cannot be configured through this mechanism. This enhancement would allow users to reference a variable and pass its resolved value into a custom HTTP header when a webhook follow-up action is triggered. Supporting this capability would enable OAuth-based authentication for third-party integrations, such as ServiceNow, allowing customers to meet their security and compliance requirements while automating incident or change creation from NetBrain diagnostics.
NetBrain currently exports and imports parser-level data within library ZIP files in a readable form, without any mechanism to obscure content that may include customer-specific details embedded in parser definitions. When libraries are reused or modified across environments, this creates a risk that one customer's sensitive information could be inadvertently exposed to another customer. This enhancement proposes applying an obfuscation method, such as a reversible encoding transformation, to parser-level data during library export, with corresponding decoding during import, while preserving the underlying data structure. Customers would benefit from reduced risk of unintended exposure of sensitive information when libraries are shared, transferred, or modified across accounts.
The GES log currently does not display the intent name or execution path associated with each log entry, making it difficult to trace which intent generated a given log line. In addition, there is no option to export the GES log for offline review or sharing. This enhancement would update the GES log to include the intent name and path for each entry, and add a log export function so the full log can be saved to a file. Customers troubleshooting intent execution issues would benefit from clearer log context and the ability to share exported logs with support or team members without manual copying.
The Device Group edit window does not currently display the Dynamic Search criteria used to define group membership, requiring users to export the group to a CSV file to view this information. This becomes time-consuming when reviewing criteria across multiple groups. This enhancement would surface the Dynamic Search criteria directly within the Device Group edit window, similar to how criteria are displayed in the Site Creation window. Customers managing many device groups would benefit from faster, more direct visibility into group definitions without needing to export data.
NetBrain currently requires users to navigate between separate interfaces, the Template Manager and Template Profile Manager, to complete folder and profile creation when templatizing a troubleshooting process, and it also requires Save and Publish to be performed as two distinct actions rather than a single combined step. This fragmented workflow can cause users to lose track of a saved template or abandon the templatizing process altogether. This enhancement would introduce an inline capability to create a folder or profile without leaving the active save workflow, along with a combined Save and Publish action that allows users to select or create a folder and profile in one step. Reducing the number of screens and clicks required would encourage more consistent use of runbook templatization and reduce user frustration during time-sensitive troubleshooting scenarios.
NetBrain Runbooks currently have no native way to search device configuration or command output for a specific text string; achieving this today requires building a custom QApp to query and filter the underlying data. This enhancement would introduce a Search node within the Runbook canvas that accepts a search string as input and returns the devices where the string is found, along with a configurable number of context lines before and after each match, similar to a grep function. Adding this capability directly to Runbook would remove the need for custom scripting, make troubleshooting workflows more self-contained, and support Runbooks that are triggered from external systems as part of an automated process.
The Topology Manager currently does not display VLAN, media type, or VRF information for device interfaces, which limits a user's ability to identify the correct interface when manually establishing a link between devices. This enhancement would add VLAN, media, and VRF attributes to the interface details shown within the Topology Manager, allowing users to reference this context directly while creating manual connections. Customers working in environments with overlapping VLANs or multiple VRFs would benefit from more accurate manual link creation and reduced reliance on external data sources to confirm interface context.
NetBrain currently does not preserve the configured data type of an Automated Data Table (ADT) field when that field is referenced within a Network Intent. A field set to the Device type in the ADT is instead evaluated as a string when consumed by the intent, causing a type mismatch. This enhancement would ensure that Network Intent correctly recognizes and preserves the original ADT field data type, including Device type, when referencing ADT values. Maintaining accurate type handling would reduce automation errors and eliminate the need for manual workarounds when building device-type based intent logic.
NetBrain currently does not support discovery and topology mapping of Hitachi Tropos SuprOS gateway devices used to bridge wired switches across an RF wireless mesh network, resulting in broken Layer 2 and Layer 3 topology continuity where a mesh segment sits between two connected switches. This enhancement would add a discovery and benchmark driver for Tropos SuprOS gateway devices, enabling NetBrain to identify these devices and correctly map the mesh-connected links on topology maps. Customers operating wireless mesh backhaul networks would gain continuous, accurate end-to-end topology visibility across mesh segments without relying on manual link creation or workarounds.
NetBrain does not currently provide a way to test connectivity from multiple Front Servers to a defined set of target devices and report the results of ping, SNMP, and CLI (including login) checks in a single view. This enhancement would add a connectivity test report that lets a user select a device list, group, or CSV of devices, run ping, SNMP, and CLI tests from each available Front Server to those devices, and view the pass/fail results per Front Server and device. Customers undergoing network migrations or infrastructure changes would benefit from being able to validate which Front Servers can reach which devices ahead of time, helping ensure uninterrupted communication and reducing the risk of unexpected connectivity loss during and after migration.
NetBrain currently allows users to multi-select and restart pending data migration tasks in bulk, but certain individual entries do not display a start option, leaving deletion as the only available action for that entry. This enhancement would extend the restart action to individual pending migration entries so the same start capability available in multi-select scenarios is consistently accessible for single entries. Customers managing data migration tasks would benefit from being able to resume a specific pending entry without deleting and recreating it, reducing administrative effort and avoiding unnecessary data loss.
NetBrain does not currently offer a native or certified integration with Dynatrace, a widely used application performance monitoring platform. This enhancement would add a supported integration that allows NetBrain to exchange device and monitoring data with Dynatrace, enabling cross-referencing of network visibility data with application performance insights. Customers evaluating or running Dynatrace alongside NetBrain would benefit from consolidated visibility across network and application layers, reducing manual effort in correlating data between the two platforms.
The API parser currently applies a fixed data size limit of approximately 2MB when receiving payloads from custom API adapters. When the data passed to the parser exceeds this threshold, the parser returns a truncated string rather than the complete payload, with no option to adjust the limit. This enhancement would make the API parser data size limit a configurable setting, allowing administrators to raise the threshold to match their integration needs. Customers building custom API adapters that return larger data sets would be able to process complete responses without truncation or the need for workarounds that split data into smaller chunks.
NetBrain currently schedules network change tasks using a single system or default time reference, requiring users to manually calculate offsets when working across time zones. In addition, the product does not validate command syntax when defining change commands, so entries with typographical errors, such as an incorrect command form, are not flagged before execution. This enhancement would add a configurable time zone setting for network change scheduling, allowing tasks to be scheduled directly in a user's local time zone without manual conversion. It would also introduce syntax or typo detection when change commands are defined, alerting users to likely command errors before they are applied. These additions would reduce scheduling errors across distributed teams and lower the risk of failed or incorrect command execution during network changes.
When a user identifies a device by an IP address during troubleshooting and initiates a Smart CLI login, the session currently connects using the IP address that was entered, rather than the MGMT IP configured for that device in Shared Device Settings. This can result in login attempts against an unintended interface when the entered IP differs from the device's designated management address. This enhancement would allow Smart CLI to log in using the MGMT IP stored in Shared Device Settings for the identified device, either by default or through a selectable option to choose which IP address is used for the connection. Customers would benefit from more reliable and consistent device access during troubleshooting, since login behavior would align with the management IP intended for administrative access rather than the IP address used only to identify the device.
The Smart CLI device search currently requires users to type an exact or partial contiguous string to locate a device, without support for wildcard characters such as an asterisk to represent any sequence of characters. This enhancement would add asterisk-based wildcard matching to the Smart CLI device search field, consistent with the pattern-matching behavior found in common network automation consoles. Customers managing large device inventories would benefit from faster, more flexible device lookup, reducing the time spent scrolling or typing exact names when initiating a Smart CLI session.
NetBrain currently provides a function to determine the subnet of a given IP address, but does not offer the reverse capability of expanding a subnet into its list of individual IP addresses. This limitation requires users to manually enumerate IP addresses within a subnet when building automation scripts. This enhancement proposes adding a Network Intent function that accepts a subnet as input and returns all IP addresses contained within it. Customers building automated test workflows, such as dynamically pinging all critical IP addresses in a subnet, would benefit from reduced manual configuration and more reliable, scalable automation.
NetBrain currently does not provide a way for external systems to populate an Automated Data Table (ADT) through the API. Users must manually enter or import IP address lists into an ADT before automation can act on that data. This enhancement would introduce a REST API endpoint that allows external systems to write or update ADT contents, such as a list of IP addresses, so that NetBrain can immediately operate on the supplied data. Customers running triggered automation workflows would benefit from being able to feed data into NetBrain programmatically, removing the need for manual data entry and enabling tighter integration with external systems.
NetBrain currently requires administrators to manually run Tune Live Access or Re-validate from Shared Settings whenever SNMP or SSH connectivity fails, since the daily system benchmark only checks SSH credentials and does not validate SNMP. This enhancement would add a GUI option to schedule Tune Live Access or Re-validate as a recurring task, similar to other scheduled system tasks. Customers who rely on automated data collection and live network access would benefit from reduced manual intervention and faster recovery from intermittent connectivity failures.
NetBrain Change Management currently does not support pushing configuration changes to devices managed through Aruba Central via its API, requiring customers to rely on manual, out-of-band processes for these devices. This enhancement would extend Change Management to integrate with the Aruba Central API, enabling configuration changes to be pushed and tracked in the same manner as other supported device platforms. Customers managing Aruba Central environments would benefit from consistent, automated change workflows and reduced manual effort in maintaining device configurations.
NetBrain parser execution currently cannot process commands that require privilege elevation, such as commands prefixed with 'sudo' on Linux-based network operating systems. When a device requires a password prompt to complete an elevated read-only command, the parser task fails or cannot proceed without a supported way to supply and respond to that credential challenge. This enhancement would allow the parser to detect a sudo or similar elevation prompt and automatically supply the configured device credentials to complete execution. Supporting this capability would allow customers running Linux-based network operating systems to automate log and data collection tasks that rely on privilege-elevated commands, removing the need for manual workarounds.
NetBrain currently allows users to select Generate NCT Table and View NCT Table options when right-clicking an Internet Cloud object in the cloud manager, even though these options are only intended to function for MPLS L3 VPN cloud types. This enhancement would remove or disable the Generate NCT Table and View NCT Table menu options when the selected cloud object type is Internet Cloud. Customers configuring cloud objects would benefit from a cleaner, more accurate interface that only presents actionable options relevant to the selected cloud type, reducing confusion during topology configuration.
NetBrain currently allows the MAC Table retrieval method for a device driver to be set to 'None' only through a direct database change, rather than through a supported configuration option, even when a device driver variant does not have a MAC table to retrieve. This enhancement would expose the retrieval method selection, including a 'None' option, as a standard configurable setting for applicable device drivers. Customers managing devices with driver variants that differ in MAC table availability would be able to configure retrieval behavior correctly without relying on unsupported database modifications, reducing configuration errors and support effort.
NetBrain's Jumpbox settings currently support only Telnet, SSH, or SSH Key as individual connection modes, with no option to combine username, password, and SSH key credentials into a single authentication method. This enhancement would add a new Jumpbox connection mode that allows administrators to configure username, password, and SSH key together as a single authentication method. Customers whose jump servers require this combined authentication scheme would be able to connect successfully without needing manual workarounds or unsupported configurations.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.