Recently active topics

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 does not currently provide a built-in SCP client for uploading and downloading device configuration files or performing firmware upgrades, nor does it offer a scriptable SSH client for automated device interaction. This limits the platform's ability to manage devices that rely on SCP and scripted SSH workflows, such as networked UPS systems, within a single tool. This enhancement would add native SCP client functionality alongside a scriptable SSH client, enabling automated configuration backup, restore, and firmware upgrade tasks directly from NetBrain. Customers managing large fleets of third-party network-connected devices would benefit from consolidating auditing and configuration management into NetBrain, reducing reliance on custom external scripts and improving operational consistency.

NetBrain's AI Dashboard feature currently does not support creating dashboards using data from a custom-built Automated Data Table (ADT). Users are limited to existing supported data sources when configuring AI Dashboard content, which restricts visibility into custom automation data. This enhancement would allow administrators to build AI Dashboards directly from custom ADT tables, giving customers greater flexibility to visualize and monitor data they have already structured for their automation workflows.

NetBrain currently displays device field data on maps in a fixed, static position, giving users no ability to reposition this text for improved layout. This enhancement would allow users to move device field labels freely within the map canvas to accommodate custom arrangements. Customers building large or densely populated maps would benefit from improved readability and layout flexibility without being constrained by fixed label placement.

Site Manager currently requires users to manually click the expand arrow on each individual site to view its contents, with no option to open or close all sites at once. This enhancement would add an Expand All and Collapse All shortcut control to the Site Manager interface, allowing all sites in the list to be expanded or collapsed with a single click. Customers managing a large number of sites would benefit from faster navigation and reduced repetitive manual clicking when reviewing the site hierarchy.

NetBrain currently does not provide a consolidated dashboard view that displays all tasks that are actively running, particularly Automation Tasks, at a given point in time. Users must check individual task lists or logs separately to determine what is currently in progress across the system. This enhancement would add a dashboard widget or view that aggregates and displays live, in-progress tasks, with particular visibility into running Automation Tasks. Customers managing large-scale or concurrent automation activity would gain a single point of reference to monitor active work, helping them identify long-running or stalled tasks and better plan operational activity without navigating multiple screens.

NetBrain currently shows only a total license consumption figure, without a detailed breakdown of how licenses are allocated across individual devices, including devices that do not require licenses or that share licenses with other devices. This enhancement would provide a device-level license consumption view that clarifies which devices consume licenses, which do not, and how shared licenses are distributed among multiple devices. Customers managing complex licensing scenarios would benefit from improved visibility into license allocation, supporting more accurate capacity planning and license audits.

The Triggered Automation dashboard currently limits users to a fixed set of predefined time range filters and does not offer a 'Last 1 Month' preset or the ability to define a custom date range when reviewing task activity. This enhancement would add a custom time range selector along with a 'Last 1 Month' option to the dashboard's filtering controls. Customers managing longer-running automation activity would gain more flexibility to review and analyze task history over the periods most relevant to their operational and reporting needs.

NetBrain currently does not indicate, within Benchmark logs, whether a retrieved table such as a routing table was collected via CLI or SNMP. This makes it difficult to determine the data source during troubleshooting, and the only available workaround is to disable the SNMP routing feature in the driver to force CLI-based retrieval. This enhancement would add a clear indicator or filter within Benchmark logs to distinguish CLI-retrieved tables from SNMP-retrieved ones. Customers troubleshooting data discrepancies would benefit from faster identification of the retrieval method without modifying driver configurations.

NetBrain's Front Server registration process currently does not honor proxy settings configured at the system or browser level, which prevents Front Servers from completing registration with the Front Server Controller in environments where outbound connectivity requires a proxy. This enhancement would update the Front Server registration workflow to detect and route through configured proxy settings when establishing its connection to the Front Server Controller. Customers deploying Front Servers in proxy-restricted or cloud network environments would benefit from a successful, unattended registration process without requiring manual network reconfiguration or workarounds.

NetBrain currently generates a separate CSV file for each Network Intent within an Automated Data Table, requiring users to manually open and cross-reference multiple files when reviewing results across different checks. This enhancement would allow the outputs of multiple intents within an ADT to be merged into a single consolidated CSV file. Customers performing configuration drift analysis across multiple features, such as NTP, AAA, banners, and ACLs, would benefit from a unified view of all findings without manual file consolidation.

NetBrain currently supports ServiceNow change management triggered automation using legacy Gapp and QApp constructs, which operate separately from the Network Intent framework and cannot take advantage of Intent-based capabilities such as diagnosis, reporting, and standardized workflow logic. This enhancement would provide a path to convert or migrate existing Gapp and QApp based automation, triggered by ServiceNow change management events, into equivalent Network Intent workflows. Customers relying on ServiceNow-driven automation would benefit from a consistent, Intent-based automation model that improves maintainability and aligns legacy workflows with current platform capabilities.

NetBrain currently does not support automatically sending an email alert and non-compliance report when a Network Intent template detects a configuration discrepancy, such as a mismatch between startup and running configuration. Users must manually review comparison results within the platform to identify non-compliant devices. This enhancement would allow a Network Intent template to trigger an automated email notification, including a non-compliance report, whenever the defined comparison logic identifies a discrepancy. Customers responsible for configuration compliance would benefit from immediate, proactive visibility into non-compliant devices without needing to manually monitor comparison results.

NetBrain currently does not track the dependency relationship between a virtual device and its primary physical device when determining device reachability status. As a result, a virtual device can remain in inventory and continue to appear accessible even after its primary device has become unreachable or has been removed from the domain, and it does not surface in the missed devices table the way other unreachable devices do. This enhancement would extend missed device detection logic to account for a virtual device's dependency on its primary device, so that when the primary device becomes unreachable or is removed, the dependent virtual device is flagged and included in the missed devices table. Customers managing environments with shared or virtualized device configurations would benefit from consistent, automated visibility into stale or orphaned devices, reducing the need for manual identification and cleanup.

NetBrain currently has no mechanism to suspend live access to specific devices during planned maintenance windows, which can result in failed access attempts, false alerts, or interference with ongoing maintenance work. This enhancement would allow administrators to place one or more devices into a Maintenance Mode with a configurable start and end datetime. While a device is within its maintenance window, NetBrain would skip all live access to that device, including scheduled discovery, on-demand CLI, path diagnosis, and runbook execution, then automatically resume normal access once the window expires. Customers performing scheduled device maintenance would benefit from reduced false alerts and fewer disruptions to maintenance activities, along with the convenience of automatic access resumption without manual intervention.

NetBrain path calculation today supports IP-based, TCP-based, and multicast path types, but does not offer a native path type where the source is a device and the destination is a VLAN for Layer 2 tracing. Customers can approximate this only through a plugin-based workflow that requires manually specifying source device, VLAN, interface, and destination device interface and VLAN, rather than a streamlined native calculation. This enhancement would add a native path type, positioned alongside existing IP and multicast path options, that accepts a source device and destination VLAN and calculates the traversed Layer 2 path across transport technologies such as VPWS, EVPN, Q-in-Q, and standard trunking. Customers operating complex Layer 2 transport environments would gain built-in, consistent path visibility for VLAN-based traffic without relying on plugin workarounds, reducing manual effort during troubleshooting.

NetBrain currently supports integration with the classic Aruba Central platform, but does not support the newer Aruba Central platform, which uses a different authentication method and returns API output in a different structure. This enhancement would add a dedicated integration path for the new Aruba Central platform, including its updated authentication flow and API response handling, so that discovery and monitoring can function correctly against it. Customers who have migrated or are migrating to the new Aruba Central platform would gain continued visibility and management capability without being blocked by the underlying platform change.