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 does not currently offer a native or certified adapter for integrating with ManageEngine OPManager, a widely used network monitoring platform. This enhancement would add a supported integration that allows NetBrain to exchange device and monitoring data with OPManager, such as pulling end-system details or cross-referencing discovered devices. Customers running OPManager alongside NetBrain would benefit from consolidated visibility and reduced manual effort in correlating data between the two platforms.
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.
NetBrain does not currently provide an audit trail that identifies which user added, deleted, or modified a device record within the device inventory. As a result, administrators have no reliable way to trace how a previously removed device reappeared in the system, which can create confusion when reconciling inventory against external systems such as a CMDB. This enhancement would add audit log entries that capture the user, action type, and timestamp for each device addition, deletion, or modification. Administrators would gain clear visibility into inventory-level changes, supporting faster root-cause analysis and more accurate reconciliation with external systems of record.
NetBrain currently does not support discovery and mapping of Google Cloud VMware Engine (GCVE) environments. This enhancement would add native discovery, modeling, and topology mapping capabilities for GCVE resources, consistent with existing public cloud support. Customers running VMware workloads on Google Cloud would gain complete visibility into their hybrid and multi-cloud infrastructure without relying on manual workarounds.
NetBrain currently does not provide a way to identify which version of the Smart CLI client each user has installed, leaving administrators without visibility into client version distribution across their organization. This enhancement would introduce a report or tracking view listing users along with their currently installed Smart CLI client version. Having this visibility would help administrators plan upgrades in advance, particularly in environments where users lack administrative rights to install or update the client independently, and where new releases require a minimum client version.
NetBrain currently does not provide validated support for installing or operating on Rocky Linux, which limits customers who need to move off CentOS as it approaches end of support. This enhancement would extend NetBrain server installation and runtime support to include Rocky Linux as a supported operating system, along with documented guidance for migrating an existing database and deployment from CentOS to Rocky Linux. Customers modernizing their infrastructure would be able to complete the operating system transition without disrupting their existing NetBrain environment.
Service Monitor currently does not provide a way to track RabbitMQ pending message counts or notify administrators when queue backlog exceeds an acceptable level. This enhancement would add a configurable threshold for RabbitMQ pending messages within Service Monitor, along with automated notifications when the threshold is exceeded. Customers would gain earlier visibility into message processing backlogs, allowing them to address underlying issues before they impact system performance or availability.
NetBrain currently does not support discovery of Azure Operator Nexus (Carrier-Grade Infrastructure), a newer Azure service used to host carrier network functions in the cloud. This enhancement would add the ability to discover and map Operator Nexus node types, topologies (such as L2, L3, and overlay), and traffic types (including unicast, multicast, and high-availability paths). Customers operating carrier-grade workloads in Azure would gain full visibility into their hosted services alongside existing Azure cloud infrastructure already modeled in NetBrain.
NetBrain's Benchmark results currently list devices in the 'Devices with retrieval failures' table when certain commands fail during data retrieval, even if those commands are only applicable in a global context or a specific VDOM and the overall retrieval status shows succeeded. This creates confusion, as customers see devices flagged as failures without a clear indication that the underlying data was retrieved successfully. This enhancement would refine command scoping logic for multi-VDOM firewalls so that VDOM-specific or global-only commands are correctly evaluated per context, and would exclude devices from the failure table when no genuine retrieval or processing issue exists. Providing accurate failure reporting would reduce unnecessary investigation effort and improve customer confidence in Benchmark results for multi-vendor, multi-VDOM environments.
NetBrain's QApp Python scripting environment currently has no built-in method for a script to write its output directly into the platform's Public or Private file folders; any generated files must be handled and stored outside of NetBrain. This enhancement proposes adding a Python API function within the QApp scripting context that allows a script to save output files directly to a specified Public or Private folder. This would let customers persist automation output within NetBrain for future reference and reuse without relying on manual file transfer steps.
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.
Custom reports currently stop generating once output reaches 100,000 lines, preventing users from viewing or exporting complete results when the underlying data set is larger. This enhancement would make the report line limit configurable, allowing administrators to raise the threshold to accommodate larger data sets. Customers working with large-scale environments would benefit from complete, accurate reporting without truncation or the need for manual workarounds to piece together full results.
NetBrain currently applies a fixed default protocol (IPv4 with UDP/TCP) for path calculation, and this default applies uniformly to all users without any administrative control over it. This can produce results that are misleading when a policy match is evaluated against a protocol that does not reflect the traffic type the user actually intends to analyze. This enhancement would allow administrators to configure the default protocol and port used for path calculation, such as ICMP or TCP on port 443, so that the system-wide default better reflects common troubleshooting scenarios. Customers would gain more accurate and predictable path calculation results out of the box, reducing confusion around policy match outcomes and the need for users to manually adjust protocol settings on each path calculation.
NetBrain currently displays a protocol label in path trace denial results that does not accurately reflect the underlying evaluation logic. When IPv4 is selected without specifying a transport protocol, the path denial message states that the path was denied by a matched TCP/UDP policy, even though no specific transport protocol was actually evaluated or matched. This enhancement would correct the displayed wording to accurately represent the matching logic used, such as labeling the result as IP-based or indicating that any protocol is permitted when no specific transport protocol is selected. Accurate labeling would help customers correctly interpret path trace results and avoid misdiagnosing policy behavior during troubleshooting.
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 renders SD-WAN connectivity between nodes as a full mesh of individual tunnel links on topology maps, which can make maps with many SD-WAN edge devices difficult to read and interpret. This enhancement would allow SD-WAN tunnel connectivity to be consolidated and displayed as a single SD-WAN cloud object, similar to how other cloud-based network types are represented. Customers mapping SD-WAN environments would benefit from cleaner, more readable topology maps that better reflect the logical SD-WAN fabric rather than a dense mesh of point-to-point tunnel links.
NetBrain currently reloads the Script Manager window and resets it to its default state whenever a user switches away to another browser tab and then returns, causing the prior view or working state to be lost. This enhancement would allow Script Manager to retain its last active state so that returning to the tab restores the window as it was left. Preserving this state would reduce disruption to users working across multiple tabs and eliminate the need to manually re-navigate to their prior position within Script Manager.
NetBrain currently does not provide a way to search for objects directly within the Check Point ACL policy table, requiring manual review of table entries to locate specific objects. This enhancement would add search functionality that allows users to query and locate objects within the Check Point policy table. Customers managing Check Point firewall policies would benefit from faster identification of relevant rules and objects, reducing manual effort during policy review and troubleshooting.
NetBrain's audit log currently provides limited information about incident portal usage, making it difficult for administrators to determine which user accessed a given incident, or which tenant and domain an incident belongs to when accessed through the portal URL, whether authentication is performed via user account or access code. This enhancement would expand audit logging, or provide a query capability, to capture incident portal access details including the authenticated user (when applicable), the access code used (when applicable), and the associated tenant and domain for each incident accessed. Administrators would benefit from improved visibility into portal-based incident access, supporting security review and compliance reporting across tenants and domains.
NetBrain path calculation currently does not correctly resolve paths across Cisco's IP Fabric for Media solution, resulting in discovery failures for this architecture. This enhancement would extend path calculation logic to properly recognize and traverse IP Fabric for Media topologies, ensuring accurate end-to-end path results. Customers operating media transport networks on this Cisco solution would gain reliable path visibility for troubleshooting and validation, removing the need for manual workarounds.
NetBrain path calculation currently does not evaluate or carry forward Layer 2 QoS DSCP markings established at the first hop, so downstream L3 routers and SD-WAN devices such as Viptela are not assessed for DSCP inheritance during path analysis. This enhancement would extend the path calculation engine to check the L2 QoS DSCP value at the first hop and verify that it is correctly inherited by subsequent L3 or SD-WAN devices along the calculated path. Customers relying on QoS-based traffic prioritization would gain accurate end-to-end path visibility into DSCP handling, improving confidence in SLA compliance and reducing manual verification during performance troubleshooting.
NetBrain path calculation logic currently does not correctly account for Layer 2 QoS configuration on certain Cisco switch and Viptela SD-WAN platforms, which can produce a path that does not reflect actual network behavior when QoS policies are applied at Layer 2. This enhancement would update the path calculation parsing logic to correctly recognize and incorporate Layer 2 QoS settings for these device types, ensuring the calculated path reflects real traffic handling. Customers relying on path calculation for QoS-sensitive troubleshooting would gain accurate path visibility, reducing the need for manual verification of QoS behavior outside the tool.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.