Recently active topics

NetBrain path calculation currently does not prioritize the display order of multiple path branches, so a successful branch may appear after failed or incomplete branches in the results. This enhancement would reorder the presentation of path branches so that a successful branch is listed first, ahead of any failed branches. Customers troubleshooting connectivity issues would be able to identify the working path more quickly, reducing the time spent reviewing unsuccessful branches before finding the relevant result.

NetBrain currently does not provide detailed usage logs for Chat Bot interactions, leaving administrators without visibility into which user triggered a given automation, which automation was executed, or how frequently it was run. This enhancement would introduce a logging capability that records Chat Bot usage details, including the initiating user, the automation invoked, and execution frequency. Customers would gain improved auditability and oversight of Chat Bot activity, supporting governance and troubleshooting of automation usage across their teams.

NetBrain currently does not surface ACI SDN-discovered devices within Site Manager or Site Maps according to the site definition, limiting visibility into how these devices fit within the broader site topology. This enhancement would extend Site Manager and Site Map functionality to recognize and display ACI discovered devices under their associated sites. Customers managing ACI environments would gain a unified view of site-based topology that includes SDN devices alongside traditional network devices, improving overall network visibility and reducing the need for separate tracking methods.

NetBrain search currently allows users to locate a MAC address only when it is associated with a Layer 3 interface; MAC addresses learned solely at Layer 2, such as entries found in a switch's MAC address table for non-routable segments, cannot be located through search. This enhancement proposes extending the search functionality to also query Layer 2 MAC address table data, so that a MAC address can be found regardless of whether it is tied to an L3 interface or exists only in an L2 forwarding table. This would allow customers to quickly locate the switch and port associated with a given MAC address without manually running CLI commands, improving troubleshooting efficiency in L2-only network segments.

QApp input dialogs currently support only static, pre-defined dropdown lists for parameter selection, with no mechanism to refresh the available options from an external data source before the QApp runs. This enhancement would allow a QApp input to call an API at runtime to retrieve a current set of selectable values, populate the dropdown with those items, and let the user choose one before execution. Customers whose valid input values change frequently would be able to select accurate, up-to-date options without manually editing the QApp definition each time the underlying list changes, reducing maintenance effort and the risk of running a QApp against stale input values.

NetBrain currently does not support image management or configuration management workflows for certain cellular router and gateway device models, limiting visibility and control over these devices within the platform. This enhancement would extend image management and configuration management capabilities to cover additional device types, including popular cellular gateway and router models, so administrators can manage firmware images and configurations consistently across their network estate. Extending this support would allow customers with mixed-vendor environments, including critical infrastructure operators, to maintain a unified change and configuration management process without manual workarounds for unsupported device types.

The OneIP Table does not always reflect the correct DNS-resolved hostname for an IP address, even when a direct DNS lookup against the configured DNS server returns accurate results. This enhancement would ensure the OneIP Table consistently uses the current DNS resolution for hostname display rather than relying on outdated or mismatched data. Customers depend on the OneIP Table for accurate identification of endpoints, and correct hostname resolution reduces confusion and manual verification during troubleshooting.

The Compare Tool currently caps displayed results at 5000 changed lines, and when configuration differences exceed this threshold, only the changed rows up to the limit are shown along with an error message rather than the complete comparison. This enhancement proposes raising or making configurable the maximum line limit so that full configuration differences can be reviewed without truncation. Customers rely on complete change comparisons to audit configuration history and correlate changes to their full context, and removing this artificial ceiling would allow accurate, complete audit and change analysis reporting for larger configuration files.

To access network devices via Smart CLI in a Managed Services environment, it is imperative to establish the connection from the NetBrain Front Server to the network devices. As the NetBrain Front Server is already authorized to communicate with network devices, this approach ensures smooth access for NetBrain users.Currently, the setup for Smart CLI necessitates a jump host (SSH) between NetBrain and the network devices. However, in a real-time managed services scenario, a Windows jump server is typically used to access network devices, as opposed to a jump host with only SSH capabilities. Exploring the installation of OpenSSH into the Front Server could provide a potential solution, though its reliability in a production environment needs to be thoroughly evaluated. It may be beneficial to conduct testing in a controlled lab environment to gauge its feasibility.In conclusion, optimizing Smart CLI for use in a Managed Services environment requires careful consideration of the connecti

NetBrain currently restricts editing, disabling, or deleting a Change Analysis task to the user who originally created it. When that user is no longer part of the organization or is unavailable, no other user can manage the task through the application, requiring direct database access to remove or modify it. This enhancement would allow a user with System Admin rights to edit or delete any Change Analysis task regardless of who created it. This would give administrators a supported way to maintain task hygiene and continuity without relying on direct database intervention.

NetBrain currently does not provide detailed usage reporting that shows how individual users interact with the platform, including which QApps, Runbooks, DVTs, or features are being used, how many users rely on a given tool, or how frequently specific devices are accessed. The existing Automation Usage overview on the Domain page also lacks clarity, as it does not explain what its figures represent or how they are calculated. This enhancement would introduce detailed usage analytics and reporting covering per-user, per-feature, and per-device activity, including QApp, Runbook, DVT, and automation/diagnosis execution statistics with clearly defined metrics. This capability would help administrators demonstrate platform value to management, identify unused artifacts for cleanup, and compare usage of overlapping functionality against unique capabilities to better guide automation strategy.

NetBrain currently requires removal of the entire Azure Cloud instance in order to release licenses associated with individual VNets, since there is no option to delete a specific VNet on its own. This enhancement would introduce the ability to select and delete individual VNets within an Azure Cloud instance, without impacting the remaining discovered resources. Customers managing large or evolving Azure environments would benefit from more precise license management and reduced administrative effort when decommissioning specific network segments.

NetBrain currently does not provide a reliable plugin-based method to retrieve the complete list of discoverable VPC resource IDs for Google Cloud (GCP), which limits the accuracy of include/exclude VPC discovery scoping in GCP environments. This enhancement would introduce a GCP-specific mechanism to fetch and validate discoverable VPC resource IDs, aligning GCP discovery capabilities with those already available for AWS and Azure. Customers managing GCP infrastructure would benefit from more accurate and dependable control over which VPCs are included or excluded during discovery, reducing errors caused by incomplete or outdated resource ID lists.

We use inventory reports to gather data on our network and would like some of our other tools to use that data as well for management dashboards.  It would be great to get this data via inventory reports.

Summary Dashboards currently present results only as raw numbers, without an option to display values as percentages. This enhancement would allow Summary Dashboard results to be shown in percentage format in addition to or instead of numeric counts. Presenting data as percentages would give management-level stakeholders a clearer, faster overview of network status when reviewing dashboards.

When creating a new device group using the Static, Dynamic Search, or Exclude options, the Select dialog for choosing devices or interfaces does not support full RegEx pattern matching. Users are limited to basic filtering and cannot construct precise expressions to target device or interface subsets. This enhancement proposes adding full RegEx search capability to these Select dialogs across all three device group creation methods, for both device and interface selection. Customers managing large or complex environments would gain a more precise and efficient way to build device groups without relying on manual selection or workarounds.

NetBrain currently does not provide a way to monitor user seat license consumption or notify administrators as usage approaches the licensed limit. Administrators can only observe seat usage manually and have no visibility until the limit is fully reached, which does not allow time to plan for additional capacity. This enhancement would add configurable threshold-based alerting for user seat consumption, notifying administrators when usage reaches defined levels below the full seat count. Customers would gain advance visibility into approaching seat limits, allowing them to budget and procure additional seats before running out.

NetBrain currently skips hostname change detection and handling for devices that share a serial number with another device, such as virtual systems on a Checkpoint firewall sharing the serial number of the physical firewall. When the hostname changes on one of these devices, administrators must manually remove and rediscover it to resume configuration retrieval, which results in the loss of historical data for that device. This enhancement would extend hostname change detection and in-place hostname update support to devices with shared serial numbers, allowing NetBrain to recognize the hostname change and update the device record without requiring removal and rediscovery. Customers managing these device types would benefit from continuous configuration retrieval and preserved historical data when hostnames change.

NetBrain's OneIP Table export currently produces a full data set without an option to limit results to IP addresses associated with a specific group of devices, such as a Device Group. Users who need IP data for only a subset of their environment must export the complete table and manually filter it afterward. This enhancement would add the ability to select a Device Group as a filter criterion prior to export, so that only IP addresses related to devices in that group are included in the output. Customers managing large or segmented environments would benefit from reduced manual post-processing and more efficient access to relevant IP data for audits, troubleshooting, or reporting.

NetBrain currently applies a single global forced CLI timeout setting of 600 seconds, which is shared across all modules and cannot be adjusted specifically for Change Management operations such as image uploads or other tasks that require longer execution windows. This enhancement would introduce a dedicated, configurable CLI timeout setting for the Change Management module, independent of the global forced CLI timeout value. Providing this control would allow administrators to accommodate longer-running change tasks without altering timeout behavior for other parts of the product, reducing task failures caused by premature timeouts during change execution.

NetBrain currently applies the CLI support setting at the device type level, so all devices sharing a type are treated identically for CLI access, even when certain individual devices should only be monitored via SNMP or other non-CLI methods. This enhancement would allow administrators to override the CLI support setting on a per-device basis, letting specific devices be flagged as not supporting CLI without changing the behavior for the rest of the device type. Customers managing mixed environments, such as servers intended for SNMP-only data collection, would benefit from more accurate device configuration and would avoid unnecessary CLI connection attempts on devices that do not require or support such access.

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.