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.
Golden Intent currently displays only Alert messages in the results dashboard, while the underlying Golden Config displays both Alert and Success messages for the same check. This inconsistency limits visibility into checks that passed successfully when reviewing Golden Intent output. This enhancement would update Golden Intent to surface Success messages in the dashboard in the same manner as Alert messages, matching the behavior already present in Golden Config. Providing complete pass and fail visibility would give customers a reliable, single view of compliance check results without needing to cross-reference the source Golden Config.
NetBrain currently does not detect when a path's associated gateway has become invalid or stale, such as when the gateway reference was imported from a CSV file and no longer resolves correctly. When this occurs, the path calculation throws an exception and Path Browser/Path History simply displays N/A, giving no indication that an invalid gateway is the underlying cause. This enhancement would improve the path-handling logic to detect an invalid or stale gateway condition and either automatically re-resolve the gateway or clearly surface the invalid-gateway state to the user in Path Browser/Path History, rather than returning an unexplained N/A. Customers would benefit from faster root-cause identification and would avoid the manual workaround of forcing gateway re-resolution to restore path visibility.
When exporting diagnosis results to CSV from the dashboard, the export currently includes all historical data with no option to limit the scope. This enhancement proposes adding a selection option to export only the last execution or a user-specified time range. This would reduce file size and eliminate the need for manual post-export filtering, saving time for customers who only need recent or targeted diagnostic data.
NetBrain currently allows default map settings to be configured only at the individual map level, requiring the same settings to be re-entered on every map that shares a common layout style. This enhancement would allow default map settings to be defined once at the Layout Style level, so that all maps using a given style automatically inherit those defaults. Customers managing multiple layout styles across different site types would benefit from reduced repetitive configuration and more consistent map presentation across their environment.
In runbook is a node, that have capabilities to compare benchmarks. I would like to add option to ignore information like: uptime from cisco show version, or interface statistics from show interface commands, so I can compare only relevant information.Or there should be option to show only the table compare. For example if in benchmark I select, that I want device information, the compare should compare only information in the table and not directly the source commands.
When multiple Network Intent status codes are posted together to a ServiceNow incident, they currently appear as a single unformatted string, making the combined result difficult to read. This enhancement would apply readable formatting, such as line breaks or a list layout, when multiple status codes are included in a single ServiceNow update. Customers reviewing incidents with multi-status results would benefit from clearer, more scannable diagnostic information without needing to parse a dense text block.
NetBrain's Device Pane Properties Panel currently does not display any indication of benchmark task status or execution history for the selected device, requiring administrators to navigate to separate task management or history views to confirm whether benchmark data collection succeeded, failed, or is pending. This enhancement would surface benchmark task status directly within the Device Properties Panel, such as last run outcome and timing, so administrators can quickly verify data currency and task health without leaving the device context. Providing this visibility would reduce troubleshooting effort and improve confidence in device data accuracy during day-to-day network operations.
NetBrain currently falls back to Telnet for device connections when SSH fails, even when administrators have configured SSH as the preferred or forced protocol. This enhancement would introduce a setting that fully disables Telnet at the system level, preventing any fallback attempt regardless of SSH connection outcome. Organizations with security policies that prohibit Telnet use need assurance that no Telnet sessions can occur, and this control would let them enforce compliance without manual verification.
When a scheduled Discovery or Benchmark task is configured with device scope set to a Device Group, the Task Management screen currently displays 'N/A' in the device scope column instead of the selected group name, leaving administrators unable to confirm which scope was actually applied to the task. This enhancement would update the Task Management view to display the actual Device Group name (or other selected scope type) for scheduled Discovery and Benchmark tasks. Providing this visibility would allow administrators to verify scheduled task configurations are correct without needing to reopen or re-edit the task definition, reducing uncertainty and troubleshooting effort for scheduled discovery operations.
NetBrain currently adds devices to the domain during discovery even when the device is not accessible via SNMP or CLI, and it does not provide a way to exclude devices from onboarding based on the outcome of CLI access attempts alone. This requires administrators to manually identify and remove inaccessible or partially accessible devices after they have already been added. This enhancement would introduce configurable domain management discovery exclusion rules tied to SNMP and CLI access results, allowing administrators to prevent a device from being added to the domain when both SNMP and CLI are unreachable, or when CLI access specifically fails. Customers managing large or sensitive environments would benefit from cleaner, more accurate domain inventories and reduced manual cleanup effort following discovery.
The OneIP Table currently displays only IPv4 addresses, leaving IPv6 addresses absent from this reference view even when IPv6 is present in the environment. This enhancement proposes extending the OneIP Table to capture and display IPv6 addresses alongside existing IPv4 entries. Customers operating dual-stack or IPv6-enabled networks would gain a complete, unified view of IP address data without needing to build separate workarounds to track IPv6 information.
The Fine Tune page currently does not display devices that are discovered through SD-WAN integrations or through API-based discovery methods, limiting administrators from reviewing and managing these devices alongside traditionally discovered network devices. This enhancement would extend Fine Tune to include SD-WAN and API-discovered devices, giving administrators a consolidated view for tuning and validation. Customers operating hybrid environments with SD-WAN or API-based device onboarding would gain complete visibility into device status without needing to rely on separate tools or manual checks.
The Do-Not-Scan list, which relies on hostname matching, does not currently extend its exclusion logic to devices added or discovered through API-based methods. As a result, devices intended to be excluded from scanning may still be processed when introduced via API integrations. This enhancement would extend Do-Not-Scan enforcement to recognize and exclude API-discovered devices using the same hostname matching logic applied to other discovery methods. Customers using API-based device onboarding would benefit from consistent exclusion behavior and reduced risk of scanning devices that should remain excluded.
NetBrain currently attempts SNMP access against every IP address identified during a live network discovery, even when the IP does not respond to an initial ping check. In large-scale environments, this results in significant time spent on SNMP attempts against unreachable or non-existent hosts, extending overall discovery duration. This enhancement would introduce an option to skip SNMP attempts for IP addresses that fail a preliminary ping check during discovery. Customers running large seed-based or full-network discoveries would benefit from substantially reduced discovery times and more efficient use of scanning resources.
NetBrain currently does not detect Inter-Switch Links (ISL) between switches in a Brocade VCS Fabric, which prevents these fabrics from being automatically drawn on the topology map. This enhancement would add discovery logic to identify ISL connections within Brocade VCS Fabric environments and represent them as links on the map. Customers operating Brocade VCS Fabrics would benefit from accurate, automatically generated topology views without needing to manually add these links.
NetBrain currently recalculates L2 and L3 topology through a full nightly rebuild process, which can take several hours to complete across the entire network. Customers who make localized network changes, such as re-cabling a switch connection in a single office, must wait for the next full topology cycle before the updated connectivity is reflected in health checks and maps. This enhancement would introduce the ability to trigger an on-demand topology recalculation scoped to a selected site or map, rather than requiring a full network rebuild. Providing a targeted recalculation option would let customers validate recent physical or logical changes quickly, reducing wait time and improving the accuracy of near-real-time health monitoring.
NetBrain currently has no mechanism to automatically retrieve or synchronize device credentials from a third-party Privileged Access Management (PAM) solution. When a PAM system rotates SSH credentials on a scheduled or event-driven basis, administrators must manually update the corresponding credentials in NetBrain, and this burden increases when each device uses a unique credential set. This enhancement would introduce native integration with PAM solutions, such as CyberArk, allowing NetBrain to automatically pull current, valid credentials at the time of device access rather than storing static values that require manual maintenance. Customers using PAM-driven credential rotation policies would benefit from reduced administrative overhead and continuous, uninterrupted device access without manual credential updates.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.