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 displays map text, such as device and interface labels, at a fixed size with no setting available to enlarge it. This enhancement would introduce a configurable text size setting for map elements, allowing users to increase text size as needed. Providing this control would improve readability for customers working with dense topology maps or presenting maps in group settings, and would support users who require larger text for accessibility purposes.
QApps currently cannot retrieve certain data already present in the Current Baseline unless the user manually selects a 'Raw data' execution option, and this option is not available when a QApp is configured to run on a schedule. As a result, scheduled automation tasks may return no output even when the required data exists in the baseline, forcing reliance on live data collection instead of reusing already-collected information. This enhancement would extend the raw data retrieval option to scheduled and automated QApp execution, allowing scheduled tasks to correctly access parsed baseline data without requiring manual intervention. Customers running automated troubleshooting and reporting workflows would benefit from consistent, accurate results without unnecessary duplicate live data collection, reducing execution time and network load.
NetBrain currently surfaces xconnect table data only within the device info panel and does not expose Pseudowire/VPLS xconnect endpoints as neighbors within the L2 Overlay, so users cannot extend a topology map to include these connections through the standard expand (+) workflow. This enhancement would add xconnect-derived endpoints to the L2 Overlay neighbor list and allow them to be added and drawn on the map using the same neighbor-expansion interaction available for other L2 neighbor types. Customers running Pseudowire/VPLS environments would gain complete topology visibility for these logical connections, reducing manual map construction and improving accuracy for troubleshooting and documentation.
The Compare action currently evaluates only global routing and ARP tables on Cisco devices, even though VRF-specific route and ARP table data is already collected through the Retrieve Live Data action and available for review. This enhancement would extend the Compare action to recognize and include VRF routing and ARP tables, allowing users to select all relevant VRFs when performing a comparison. Customers operating multi-VRF environments would gain complete and accurate change detection across all routing contexts, rather than being limited to the global table only.
The Device data table does not currently populate stack switch member details for Cisco and Juniper devices when exporting map data, leaving stacked chassis information incomplete in the exported table. This enhancement would extend data collection to capture stack member details for Cisco and Juniper devices, using the relevant device commands that expose stack membership, and populate that information in the Device data table. Customers relying on exported data tables for documentation and troubleshooting would gain accurate, complete visibility into stacked switch configurations without needing to manually supplement the exported data.
When searching for a VLAN group, the search results currently display the group and only a single matching entry, requiring users to manually navigate to the group to view all associated devices. This enhancement would keep VLAN groups collapsed by default in search results and add a right-click option to jump directly to the target group with all entries expanded. This would reduce the time needed to locate and review all devices within a specific VLAN group, improving efficiency during troubleshooting and data accuracy review.
Inventory Report filtering currently supports only two levels of criteria and does not offer logical operators such as AND or NOT, limiting users to basic single or dual-condition filters within the panel view. This enhancement would introduce support for multi-condition filtering with configurable logical operators, allowing users to build more precise, layered filter combinations directly within the report interface. Customers working with large device inventories would benefit from the ability to isolate specific subsets of data natively, reducing reliance on exporting data to external tools for further analysis.
Inventory Report filtering currently limits users to applying a maximum of two filters when narrowing report results. This enhancement would remove that restriction and allow users to apply multiple filter criteria simultaneously when generating or refining Inventory Report results. Customers managing large and complex device inventories would benefit from more precise filtering, reducing the need for manual post-processing to isolate relevant data.
NetBrain currently requires users to select individual sub-groups, such as each AS number under System Device Groups or each sub-group under a Policy Device Group, in order to generate a report or export device details. There is no option to select a parent group and automatically include devices from all of its sub-groups. The same limitation applies to the Site tree, where users cannot select a higher-level tier, such as a country or region, to report on or export all devices contained within that tier and its lower levels. This enhancement would allow users to select a parent Device Group or any tier of the Site tree as the basis for a report or export, with the output including all devices from the underlying sub-groups or sub-tiers and configurable device detail fields. Customers managing large environments with many sub-groups or site tiers would benefit from reduced manual effort and faster access to consolidated device data for reporting and auditing purposes.
NetBrain benchmark tasks currently do not provide a configurable timeout for individual device data retrieval, so a device that is slow or unresponsive can continue retrying for extended periods, in some cases 20 minutes or longer, before the task proceeds to the next device. When multiple devices experience this delay, the overall benchmark run time can be extended substantially. This enhancement would introduce a configurable retrieval timeout setting, allowing administrators to define a maximum wait time per device after which the task stops retrieval attempts and moves to the next device. Customers managing large device inventories would benefit from more predictable and efficient benchmark completion times, reducing the impact of a small number of unresponsive devices on overall benchmark duration.
NetBrain's ServiceNow App integration currently depends on UI Macro, a mechanism that ServiceNow Agent Workspace, the newer front-end interface for incident management, does not support. This enhancement would rebuild or extend the ServiceNow App integration so that its functionality operates correctly within Agent Workspace. Customers migrating to Agent Workspace would benefit from uninterrupted access to NetBrain diagnostic and troubleshooting capabilities directly within their incident management workflow.
NetBrain currently allows site maps to be exported to a shared folder as part of a scheduled Benchmark task only in Visio format, with no option to export directly as a JPEG or other image format. This enhancement would add a JPEG/image format option alongside the existing Visio output for Benchmark-driven site map exports. Customers who need lightweight, universally viewable diagrams for reporting or archiving would be able to obtain them automatically without post-processing or converting Visio files.
NetBrain currently does not support Cisco Firepower Management Center (FMC) as a controller type for device discovery, unlike its existing support for controller-based platforms such as Cisco ACI APIC. This enhancement would add FMC as a selectable controller source within API Server Manager, enabling discovery and modeling of devices managed through FMC. Customers operating Cisco Firepower environments would gain complete network visibility without relying on manual workarounds outside NetBrain.
NetBrain currently provides an execution log with per-device success and failure feedback only when a QApp is run interactively at the site map level. This visibility is not available when a QApp is run through the Scheduler or when it is invoked at scale through a QApp-based Inventory Report, leaving users unable to determine whether individual devices were successfully accessed during the run. This enhancement would extend execution log reporting to scheduled QApp runs and to QApp-based Inventory Reports, capturing per-device access outcomes consistent with the interactive execution experience. Customers running automation and compliance workflows at scale would gain the ability to identify which devices failed during a scheduled or report-driven run, supporting timely troubleshooting and more reliable audit reporting.
NetBrain currently has no way to automatically build a source-to-destination path when source and destination IP addresses are supplied through a trigger source, such as a ticketing system, email, or bot, for a given application. Users must manually input path endpoints before running any diagnostic checks, which delays troubleshooting for ticket-driven automation. This enhancement would allow the source and destination IP addresses parsed from a trigger source to automatically populate a path calculation on the fly, and then execute a predefined, application-specific set of diagnostic intents, such as device health, interface health, and application health checks, against that path to produce a diagnosis output. Automating path creation and diagnosis directly from trigger data would reduce manual setup time and speed up root-cause identification for customers running high volumes of ticket-triggered network and application health investigations.
NetBrain currently does not compare an application's active path against its designated golden path or most recent last-known path within PAF, so unexpected path changes are not proactively surfaced to users. This enhancement would extend PAF to evaluate the application path against the golden and last path, generate an alert when a deviation is detected, and automatically trigger path intents to verify the health of the path and related application-critical parameters. This capability would give customers earlier visibility into unexpected path changes and streamline validation of path and application health without requiring manual investigation.
NetBrain Smart CLI currently displays only one active session view at a time, requiring users to switch between open sessions rather than viewing them together. This enhancement would allow users to arrange multiple open Smart CLI sessions side by side within a single window. Providing this layout option would help network engineers compare output and manage several device sessions simultaneously without repeatedly toggling between windows.
NetBrain currently does not display IPv6 neighbor information for a device when viewed from within a Site topology map, limiting visibility into IPv6-based connections at the site level. This enhancement would extend the Site map neighbor display so that IPv6 neighbor relationships are shown from the device end, consistent with existing neighbor visibility for other address types. Customers operating IPv6-enabled or dual-stack environments would gain more complete topology visibility within Site maps without needing manual cross-referencing to confirm IPv6 neighbor connections.
The Device Health Report currently reports a count of L2 topology issues per device but does not identify which specific interface is associated with each flagged issue. When a device has multiple interfaces, customers cannot determine which one requires attention without manual investigation. This enhancement would add interface-level detail to topology issue entries in the Device Health Report, so each flagged issue clearly references the affected interface name. Customers managing a large number of topology issues would be able to prioritize and resolve them more efficiently, reducing the manual effort needed to isolate the root cause among multiple interfaces on a device.
NetBrain currently supports configuring a single jumpbox hop when establishing Smart CLI connections to end devices, with no mechanism to define a sequence of two or more jumpboxes in a chain. This enhancement would allow administrators to configure multiple jumpboxes in a chained sequence, so that a Smart CLI session can traverse each hop in order to reach the target device. Customers operating segmented or layered network environments that require multiple jump hosts to reach end devices would gain full connectivity through Smart CLI without relying on manual, unsupported workarounds.
NetBrain currently allows Event templates for third-party integrations to be configured only at the domain level, requiring administrators to manually recreate or copy the same template into every domain. This enhancement would allow Event templates to be defined and managed at the Tenant and System level, so they can be applied across multiple domains without duplication. Customers managing large multi-domain environments would benefit from reduced administrative effort and more consistent event configuration across their organization.
NetBrain's live access log currently displays timestamps without consistent timezone labeling, and different features within the log may show local time, UTC, or another reference zone without indicating which is used. This creates ambiguity when interpreting log entries, particularly during troubleshooting across distributed teams or time zones. This enhancement would add explicit timezone labels to all timestamps shown in the live access log, ensuring consistency across the features that populate it. Customers and support teams would benefit from reduced confusion and faster, more accurate troubleshooting when reviewing live access history.
NetBrain currently applies a fixed approach to management interface selection during discovery, without allowing administrators to define a preferred order among multiple management interfaces based on device type or device group. This enhancement would introduce configurable interface selection priority rules that can be set per device type or device group, so discovery consistently uses the intended management interface. Customers managing diverse device fleets would benefit from more predictable and accurate discovery results, reducing the need for manual correction after discovery runs.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.