Recently active topics

The Change module currently executes commands in a continuous stream, offering only a fixed sleep delay or a send-enter step, with no mechanism to pause execution and require operator confirmation before proceeding to the next command. This enhancement would add an interactive pause point within Change module execution, allowing the operator to confirm, cancel, issue a custom command, or commit before continuing, along with an option to close the session. This capability would give operators greater control and oversight when running long or complex automation scripts against production devices, reducing the risk of unintended changes propagating without review.

NetBrain currently does not support the Nutanix API, which prevents discovery of Nutanix servers within the platform. This enhancement would add a dedicated Nutanix API adapter to enable discovery and modeling of Nutanix infrastructure alongside other supported device types. Customers running Nutanix environments would gain full visibility into their server infrastructure without relying on manual workarounds.

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.

NetBrain does not currently provide drivers to discover and manage certain Tier 1 network devices, including Ciena MCP and Virtuora platforms, which prevents these devices from being brought into automation and topology workflows. This enhancement would add driver and adapter support for these device types, enabling discovery, benchmarking, and topology construction consistent with other supported platforms. Customers operating this equipment would benefit from complete network visibility and reduced manual effort in mapping and managing these devices.

NetBrain currently provides no way to associate a Change Runbook with the ServiceNow change or incident that originated it. Users must manually track and cross-link the two records, since the Change Management module does not prompt for or store a reference to the source ticket at creation time. This enhancement would prompt users, when creating a Change Runbook, to confirm or select the originating ServiceNow change or incident, and would maintain an automatic link back to that ticket throughout the runbook lifecycle. Customers using ServiceNow alongside NetBrain Change Management would benefit from reduced manual cross-linking effort and improved traceability between the two systems.

Automated Application Mapping currently has no way to schedule path runs at a recurring frequency with alerting on failure or change; this capability is only available through Benchmark, which requires collecting data across all or a specified set of devices first, making frequent runs impractical. This enhancement would add a standalone scheduler to Automated Application Mapping that executes path runs at a defined interval and triggers an alert when a run fails or the resulting path changes, without requiring the broader device data collection that Benchmark currently needs. Customers would gain the ability to monitor critical application paths more frequently and receive timely notification of failures or changes, improving responsiveness to path issues without the overhead of full data collection.

NetBrain currently does not support discovery and mapping of AWS Cloud WAN, a managed wide-area networking service used to interconnect cloud and on-premises networks. This enhancement would add native discovery, modeling, and topology mapping capabilities for AWS Cloud WAN resources, consistent with existing support for other AWS networking constructs. Customers migrating from AWS Transit Gateway to Cloud WAN would gain complete visibility into their evolving network architecture without relying on manual workarounds.

In the Intent diagnosis view, Compare and Diagnosis Details operate as independent features, with Compare always showing current output versus a fixed baseline regardless of the diagnosis logic defined. The current interface does not communicate this separation, leading users to assume the two features reference the same underlying data. This enhancement would add a GUI indicator, such as a tooltip or inline hint, clarifying that Compare and Diagnosis Details function independently and explaining how Compare's baseline comparison relates to the diagnosis logic. Providing this clarity would reduce user confusion and support inquiries related to misinterpreting the relationship between these two features.

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.

NetBrain's webhook follow-up action currently requires users to manually base64 encode their username and password before entering the combined string into the Authorization header when configuring Basic Authentication. This manual step introduces the risk of formatting errors and requires customers to perform the encoding outside of NetBrain using external tools. This enhancement would allow NetBrain to accept a plain username and password for Basic Authentication and automatically perform the base64 encoding internally before constructing the Authorization header. Customers with security requirements around credential handling would benefit from a more streamlined and less error-prone configuration process when setting up webhook integrations.

NetBrain currently requires administrators to manually delete the stale hostname entry left behind in Inaccessible Devices after using the 'Keep the Latest' action to update a device's hostname in All Discovered Devices. This enhancement would have 'Keep the Latest' automatically perform the cleanup of the old hostname entry as part of its workflow, while preserving the active device record and its historical data. Customers would benefit from a simplified process that eliminates manual follow-up steps and reduces the risk of stale, inaccessible duplicate entries accumulating over time.

The CVE Report currently does not provide a way to mark individual CVE entries as verified or invalid, nor does it support adding comments directly within the report. As a result, reviewers must export the data and track verification status and notes outside of NetBrain. This enhancement would add two columns to the CVE Report: a Verify/Invalid status field and a free-text Comments field, allowing users to annotate each CVE entry in place. Customers responsible for vulnerability review would benefit from a streamlined workflow that eliminates manual export and external tracking, improving efficiency and accuracy of CVE assessment reviews.

NetBrain does not currently provide a way to reserve IP addresses for planned or future use, unlike dedicated IPAM solutions that offer this capability. This enhancement would introduce an IP address reservation feature, allowing administrators to mark specific addresses or ranges as reserved before they are assigned to a device. Customers who rely on NetBrain alongside or in place of separate IPAM tools would benefit from consolidated address planning, reduced risk of address conflicts, and improved visibility into available address space during network changes.

NetBrain does not currently provide a way for an external application to trigger a path trace through the Triggered Automation Framework and receive the resulting path data, such as device names along the path, back through the same API interaction. Applications that need this information must rely on a separate path calculation API call, which can sometimes produce a different path result than the one generated by the triggered automation, creating inconsistency between the two data sources. This enhancement would introduce a way for a triggered automation execution to return path trace results, such as the ordered list of devices in the path, directly in the API response or through a related endpoint, without requiring a second, independent path calculation call. Customers integrating NetBrain with external applications would benefit from consistent, reliable path data sourced from a single automation execution, reducing the need to build and maintain a separate integration path and

NetBrain currently supports configuration of only a single mail server for outbound email delivery, and it provides no built-in mechanism to monitor that mail server's availability or alert administrators when it becomes unreachable. This enhancement would allow administrators to configure a secondary mail server that email delivery automatically falls back to when the primary server is unavailable, along with a monitoring capability that tracks mail server availability and issues alerts on failure. Customers would benefit from uninterrupted delivery of system notifications and faster detection of mail server outages, reducing the risk of missed alerts during critical events.

NetBrain currently has no automated way to convert a benchmark task failure, such as a device or CI failing to back up configuration, NDP table, route table, ARP table, MAC table, STP table, device info, or interface info, into a trackable remediation action; support staff must manually review benchmark alert emails and create tickets themselves. This enhancement would extend the existing ServiceNow alert integration so that a benchmark run reporting a device backup failure automatically generates a ServiceNow ticket for remediation, leveraging the existing OAuth-based connection and alert plugin. Customers relying on ServiceNow for operational workflows would benefit from faster identification and tracking of backup failures, reducing manual monitoring effort and improving remediation turnaround time.

Today, generating a remediation script for configurations that aggregate multiple protocols requires manual identification of the correct parent class-map and policy-map structures before a modification can be applied. This process is error-prone because a single configuration may contain multiple protocol-specific class-map and policy-map sections, making it difficult to reliably determine which parent structure a given change belongs to. This enhancement would improve remediation script generation to automatically and accurately identify the correct parent class-map and policy-map structure for a requested modification, such as removing a specific match statement under the correct class or updating a priority statement under the correct policy-map and class combination. Customers managing complex, multi-protocol configurations would benefit from more accurate automated remediation, reduced manual review, and lower risk of applying changes to the wrong configuration section.

The Observability Dashboard currently has no dedicated view for AAM path intents that consolidates a path and its associated follow-up diagnosis checks, such as Ping Response or Routing Next Hop verifications, into a single entry. When using the existing Intent Dashboard filtered to path-based intents, each follow-up check appears as a separate entry rather than being grouped under its parent path, creating confusion when assessing path health. This enhancement would introduce a dedicated Observability Dashboard view for AAM paths that displays one consolidated entry per path intent, incorporating success or alert status derived from all related diagnosis checks. Customers monitoring critical paths would gain a clearer, continuous assessment view without needing to manually correlate separate entries for the same path.

Dashboards currently display only the results of the most recent run, with no option to filter by a broader time range or to view how results have changed over time. This enhancement would introduce built-in time range filters, such as Last Hour, Last 24h, and Last 7 Days, along with a trend visualization capability at the dashboard level. Customers would gain the ability to review historical performance and identify patterns over time, improving visibility into operational trends without relying on manual comparison of individual runs.

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's current self-healing workflow allows external systems to trigger remediation through a Network Intent that generates a Change Management runbook, but it does not support triggering a troubleshooting runbook—consisting of a diagnostic sequence of CLI and Network Intent nodes—directly from a ticketing system, nor does it return a summarized result back to the originating record. This enhancement would extend the Triggered Automation Framework to allow a ServiceNow ticket to invoke a troubleshooting runbook, automatically targeting devices at a specified site, and to post a summarized diagnostic result back to the incident. Customers using ServiceNow for incident management would benefit from faster triage and reduced manual effort, since diagnostic context would be available directly within the ticket without requiring a separate remediation workflow.

NetBrain currently requires a full seat license for any user to view AI Co-Pilot or Chatbot generated insights, even when that user only needs read-only access to the portal for insight consumption rather than full platform functionality. This limitation prevents organizations from extending AI-driven insights to a broader set of stakeholders without incurring additional licensing costs. This enhancement would introduce a lightweight or restricted access mode that allows users to view AI Chatbot insights through the customer portal without requiring a full seat license. Customers with large teams or occasional viewers would benefit from wider visibility into AI-driven insights while managing licensing costs more efficiently.

NetBrain currently does not provide a way to convert a manually established Fix-Up link into a native L2 border link within ACI-Switch topology, leaving such links classified differently from natively calculated L2 border links even after the connection has been validated. This enhancement would add the capability to convert a Fix-Up link to an L2 border link, allowing the corrected connection to be represented consistently with other calculated fabric links. Customers operating ACI environments would benefit from more accurate topology representation and reduced manual link maintenance during troubleshooting and documentation.

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.

NetBrain discovery does not consistently identify all VPN tunnels for SD-WAN devices from certain vendors, which can leave some devices unreachable for CLI-based access even though they are configured with valid credentials. This enhancement would extend discovery to use the vendor's REST API to retrieve tunnel and device relationship data directly from the SD-WAN controller, filling gaps left by traditional discovery methods. Customers running SD-WAN environments would gain more complete and reliable topology and device visibility, reducing troubleshooting delays caused by incomplete discovery.