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 OneIP Table currently displays switch and port information concatenated together in a single switchport column, which limits the ability to filter or sort on switch or port values independently. This is particularly problematic when the table is exported to a spreadsheet, as users must manually split the column into two before they can filter or sort effectively. This enhancement proposes separating the switchport field into two distinct columns, one for the switch and one for the port, so the data is usable immediately upon export. Customers who rely on the OneIP Table for spreadsheet-based analysis would benefit from reduced manual data preparation and improved efficiency when filtering or sorting on switch or port values.
NetBrain currently does not provide visibility into which automation assets (QApp, Network Intelligence, DVT, GApp) depend on a given parser, nor does it propagate a parser name change to those dependent assets automatically. As a result, renaming or modifying a parser can break dependent automation, requiring users to manually locate and update each affected asset individually. This enhancement would add the ability to view all dependent automation assets before a parser change is made, automatically update references when a parser name changes, and optionally load a copy of a parser into an automation asset to avoid unintended modification of the shared original. Adding version control for parsers is also proposed to support tracking and reverting changes over time. These capabilities would reduce manual maintenance effort and prevent unexpected automation failures for customers managing interdependent parser and automation libraries.
NetBrain Incident Manager currently does not provide a way to select and delete multiple incidents simultaneously, requiring users to remove incidents one at a time even when large volumes of stale or unwanted incidents accumulate. This enhancement would add a bulk selection and delete action within Incident Manager, allowing users to select all or a filtered subset of incidents and remove them in a single operation. Customers managing high incident volumes would benefit from significantly reduced manual effort and faster cleanup of the incident repository.
NetBrain currently truncates device hostnames displayed on maps when the name exceeds a fixed character limit, showing an ellipsis in place of the full name in both compact and extended label formats. This truncation also carries over when the map is exported, so the exported file does not contain the complete hostname either. This enhancement would increase or remove the character limit for hostname labels on maps, or provide a setting to display the full hostname on hover or in exported output. Customers with longer hostname naming conventions would benefit from accurate, complete device identification on maps without needing manual lookups or edits after export.
NetBrain's compare function currently requires users to select items individually when choosing which entries to include in a comparison, with no option to select all items at once. This enhancement proposes adding a select all control to the compare function so that users can select every available item in a single action. This capability would reduce manual selection effort and improve efficiency for customers comparing large sets of devices or data entries.
NetBrain currently does not provide a way to disable an individual Diagnosis definition while keeping its configuration intact for future use; the only available workaround is to duplicate the Diagnosis and modify the copy, which is not practical when replication is configured against the original. This enhancement would add an enable/disable toggle at the Diagnosis level, allowing a Diagnosis to be turned off without deleting it or losing its settings. Customers managing multiple similar Diagnoses, especially those with dependent replication, would benefit from a simpler way to temporarily deactivate and later reactivate a Diagnosis without duplicating effort.
NetBrain currently opens a separate SSH session for each CLI command task performed against a device, including sessions triggered by Network Intent, Runbook execution, and other live data retrieval operations. This results in multiple concurrent or sequential SSH connections being established to the same device for what could be handled through a single session. This enhancement would have NetBrain establish and reuse one SSH session per device across these CLI-driven tasks, rather than opening a new session for each task type. Customers would benefit from reduced login overhead on network devices, lower risk of hitting device session limits, and more efficient CLI-based data retrieval overall.
Custom DNS server settings configured for the OneIP Table are currently applied and executed only from the NetBrain core server, which in some customer environments does not have network connectivity to the designated DNS server. This limitation prevents hostname resolution from completing successfully even though a Front Server in the same environment does have the required connectivity. This enhancement proposes allowing the custom DNS server configuration and associated resolution calls for the OneIP Table to be executed from the Front Server instead of the core server. Customers whose DNS infrastructure is only reachable from the Front Server would gain accurate hostname resolution for unknown entries without requiring additional network changes or workarounds.
NetBrain currently stores Telnet/SSH credential values directly with each device record rather than maintaining a live reference to the credential definition. As a result, when a credential is deleted from Network Settings, devices that were assigned that credential retain the stale username and password values, and administrators have no way to identify which devices are affected. This enhancement would introduce a report or search capability that identifies all devices currently assigned a credential that no longer exists in Network Settings. Customers would benefit from the ability to proactively locate and remediate devices with orphaned credential assignments, improving credential hygiene and reducing the risk of failed or unauthorized access attempts.
NetBrain currently requires manual initiation of subnet scans and does not support automatic, recurring discovery against a defined list of subnets. It also has no mechanism to automatically remove devices from inventory when they become unreachable for an extended period. This enhancement would allow administrators to configure a list of subnets for automatic, scheduled scanning, so that any new device responding with valid SNMP configuration is automatically added to inventory. It would also add a configurable time threshold after which a device on a monitored subnet that remains unreachable is automatically removed from inventory. Customers managing large or dynamic environments would benefit from reduced manual inventory upkeep and more accurate, self-maintaining device records.
NetBrain currently requires each site map to be built and maintained independently, with no capability to reuse a defined portion of one map, such as a core and distribution layer segment, within other related maps. Customers who split large campus networks into separate building-level maps must manually recreate or reference shared infrastructure in each map, making it difficult to visualize connectivity from access-layer buildings back to the core and distribution building. This enhancement would allow a defined map segment to be reused or referenced across multiple site maps, so shared infrastructure appears consistently without manual duplication, along with maintained connectivity links between the shared segment and each building map. This would help customers managing large, multi-building campus networks maintain accurate topology views and end-to-end connectivity visibility without redundant map maintenance.
NetBrain currently does not allow a user to copy a device's IP address or hostname directly from the map for use in another tool such as Path. Users must rely on double-clicking a device to view its details, then manually retype the IP or hostname elsewhere. This enhancement would add a copy option, such as a right-click menu action or keyboard shortcut, that copies the selected device's IP address or hostname to the clipboard directly from the map. Customers would benefit from a faster, error-free workflow when transferring device identifiers from the map into the Path tool or other input fields.
NetBrain currently does not display creator or author information within the DVT description, making it difficult to identify who authored a specific DVT. QApp descriptions already include an author field, but this capability is not available for DVTs. This enhancement would add a creator/author field to the DVT description, consistent with the existing QApp author display. Providing this visibility would help administrators and engineers quickly identify DVT ownership for maintenance, review, and troubleshooting purposes.
NetBrain currently can produce differing traffic-permit results between L2 and L3 path calculations for the same firewall policy match, even when the same rule and port should apply consistently across both path types. This inconsistency creates confusion for customers evaluating whether a specific traffic flow is actually permitted or denied end-to-end. This enhancement would align the policy evaluation logic used in L2 path calculation with that used in L3 path calculation, ensuring both consistently reflect the same firewall rule decision for a given traffic definition. Customers validating security policy behavior through path trace would gain a single, trustworthy result regardless of path type, reducing troubleshooting time and eliminating the need to manually reconcile conflicting path outputs.
NetBrain currently provides no supported way to recover a map after it has been deleted, whether removed from the platform or deleted from disk. This enhancement would introduce a recovery mechanism, such as a recycle bin, retention window, or restore action, allowing administrators to reclaim a deleted map within a defined period. Customers who accidentally delete a map or need to reverse a deletion would avoid permanent data loss and reduce the effort required to rebuild the map from scratch.
NetBrain currently relies on Neighbor Discovery Protocol (NDP) data, such as CDP or LLDP, to calculate and render Layer 2 links on the topology map. When one or both connected devices do not provide this data, such as certain firewall or load balancer platforms, the L2 link is omitted from the map even when the devices reside in the same VLAN. This enhancement would allow NetBrain to derive L2 links using alternate data sources, such as MAC address tables, ARP tables, and VLAN membership correlation, when NDP data is unavailable from one or more connected devices. Customers operating mixed-vendor environments would gain complete and accurate L2 topology visibility without manual link creation, improving the reliability of network diagrams used for troubleshooting.
NetBrain currently compares configuration snapshots without accounting for whether each snapshot was retrieved via SNMP, CLI, or API. Because these collection methods capture differing scopes of configuration data, such as AAA, NTP, and ACL settings that may only be present in CLI or API captures, comparisons between snapshots from different sources can produce misleading or meaningless differences. This enhancement would have NetBrain detect the collection method associated with each configuration snapshot and skip or clearly flag comparisons when the two data points originate from different source types. Customers would benefit from more accurate change detection and would avoid unnecessary troubleshooting caused by false configuration drift alerts stemming from mismatched data sources.
NetBrain currently displays A-B path notes on maps by default, with no option to disable this behavior globally across the system. This enhancement would introduce an administrator-configurable setting to turn off A-B path notes for all users by default. Customers who do not require these annotations would benefit from a cleaner map view and reduced visual clutter during path analysis.
NetBrain currently does not automatically apply the Access Mode (SSH or Telnet) defined in Shared Device Settings when establishing a Smart CLI connection. As a result, devices that are only reachable via Telnet may not connect properly through Smart CLI unless the mode is manually reconciled. This enhancement would have Smart CLI automatically inherit the Access Mode configured in Shared Device Settings for each device. Customers managing mixed environments with both SSH- and Telnet-only devices would benefit from consistent, reliable connectivity without needing to manually adjust connection settings for each device type.
NetBrain currently stores Smart CLI local log files without a structured folder hierarchy, which can make it difficult for administrators to locate specific logs as the volume of files grows. This enhancement would allow log files to be organized into a folder structure, such as by device or by date. Customers managing large numbers of Smart CLI sessions would benefit from improved log organization and faster retrieval when troubleshooting or performing audits.
NetBrain currently does not transfer Smart CLI session execution logs into the platform, leaving administrators without a way to review command-level activity performed during Smart CLI sessions from within the NetBrain interface. This enhancement would capture Smart CLI execution log data and surface it within the NetBrain interface, recording the user, the action taken, and the time of execution. Providing this visibility would help administrators audit Smart CLI usage, support compliance reviews, and troubleshoot changes made through Smart CLI sessions without relying on external log sources.
NetBrain currently does not consistently reflect a successful live access result when a device is monitored by multiple front servers and the results differ between them. If one front server reports a successful ping or SNMP result while another reports failure, the overall device status may display as failed rather than reflecting the successful outcome. This enhancement proposes that the overall live access status prioritize a successful result over a failed one when multiple front servers test the same device, rather than defaulting to the most recently recorded result. Customers operating environments with multiple front servers depend on accurate live access status to avoid unnecessary troubleshooting and false indications of device unreachability.
NetBrain's Auto Link All feature currently supports establishing links only between device-to-device pairs, and cannot automatically create links involving site-cloud or site-to-site map objects. This limits users with many site maps who need to extend link coverage, including IPv6 links, across their full topology. This enhancement would extend Auto Link All functionality to detect and create links for site-to-device and site-to-site relationships, in addition to existing device-to-device support. Customers managing large numbers of site maps would benefit from reduced manual effort in maintaining accurate, complete topology connections.
The OneIP Table currently does not include a field indicating when an IP address or device was first detected, nor does it provide operating system identification for endpoints such as virtual machines. This limits the table's usefulness for security and compliance tracking that depends on knowing discovery history and endpoint OS type. This enhancement proposes adding a first-detected date field and an OS identification field to the OneIP Table. Customers using the OneIP Table to support security controls and asset inventory processes would gain more complete endpoint context directly within NetBrain, reducing reliance on separate scanning tools for this information.
NetBrain currently allows users to export configuration information for all devices on a map in a single batch (via Export to Word), but this only reflects the current or baseline configuration snapshot; there is no option to specify a past date and retrieve the configuration files that were in effect for all devices at that time in one batch action. This enhancement would add the ability to select a specific historical date and export the corresponding configuration files for all devices on a map or in a domain as a single batch, such as a zip archive. Customers who run daily benchmarking or periodic audits would benefit from being able to reconstruct a full historical configuration snapshot without manually retrieving each device's configuration file individually.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.