Recently active topics

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.

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 may fail to correctly detect and populate vendor and model information for certain devices added through configuration file import, which in turn prevents accurate topology link calculation for those devices. This enhancement would improve the parsing logic used during configuration file import to reliably extract vendor and model attributes, ensuring devices are properly identified and topology links are calculated correctly. Customers who rely on configuration file import for devices without direct CLI or SNMP access would benefit from more accurate device inventories and complete topology visibility without manual correction.

NetBrain currently exposes a Last Discovery Time field that reflects the most recent discovery attempt for a device, regardless of whether that attempt succeeded. As a result, users cannot rely on this field to determine when a device was last successfully accessed and its data confirmed current. This enhancement proposes adding a distinct, reportable field for Last Successful Discovery Time (or Last Successful Access Time), populated only when discovery completes successfully for a device. Customers managing large device inventories would gain a reliable way to identify devices with stale or unconfirmed data, supporting more accurate reporting and targeted troubleshooting of access failures.

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 does not provide a way to export the full list of system users along with their assigned roles in a structured file format such as CSV or XML. This enhancement proposes adding an export capability for the user list, including each user's assigned role, accessible from user management. Customers managing large user populations would benefit from a faster, more reliable way to support periodic access audits and compliance reviews without manually cross-referencing user records.

NetBrain's compare function currently supports comparing device configuration data only, with no option to compare CSV files generated as QApp output. This enhancement proposes extending the compare function to allow selection and comparison of QApp-generated CSV outputs, similar to how configuration comparisons are handled today. Adding this capability would give customers a consistent way to identify differences across QApp results over time, supporting troubleshooting and change validation workflows.

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 limits Device Access Policy privileges to two broad options: View Network Data and Execute Network Change. Administrators cannot assign more granular permission levels within this policy to distinguish between varying degrees of network data access or change execution. This enhancement would introduce additional, more granular privilege tiers within Device Access Policy, allowing administrators to define finer-grained access levels beyond the current two options. Customers with complex organizational access requirements would benefit from more precise control over which users can view or modify specific types of network data, supporting stronger adherence to least-privilege access principles.

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 does not allow users to export the list of devices along with their configured credentials, aliases, usernames, vendor, and IP address directly from the Network Setting window. Users must first add devices to a Device Group and export from there, which adds extra manual steps for a straightforward reporting need. This enhancement would add a direct export option within the Network Setting window that includes device identity and credential details, along with an option to trigger device rediscovery from the same view, similar to the rediscovery workflow available in Fine Tune. Customers performing credential audits and compliance reviews would benefit from faster, more direct access to this information without navigating through Device Group creation.

NetBrain audit logs currently capture only login activity for Smart CLI sessions, without recording which domain or device was accessed during the session. This enhancement would expand Smart CLI audit logging to include the domain and device information associated with each session. Capturing this detail would support security and compliance requirements by giving administrators full visibility into user activity across domains and devices.

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 does not provide a way to automatically detect or recover a Front Server whose status remains stuck in "Checking" within the portal, even after the server and its services are restarted. Administrators currently have no built-in diagnostic or self-healing mechanism to resolve this condition and must rely on manual troubleshooting. This enhancement would introduce automated detection of a Front Server remaining in a "Checking" state beyond an expected threshold, along with a recovery action or clear diagnostic guidance to resolve the condition. Customers would benefit from reduced downtime and less manual intervention when Front Server status monitoring fails to update correctly.

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 global search currently requires an IPv6 address to be entered with its subnet mask, such as in CIDR notation, in order to return results; a plain IPv6 address without a mask does not return a match, unlike IPv4 addresses, which can be searched without a mask. This enhancement would extend global search to recognize and return results for IPv6 addresses entered without a subnet mask, bringing IPv6 search behavior in line with IPv4. Customers working in IPv6 environments would be able to locate devices and interfaces by address more efficiently, without needing to know or supply mask information during troubleshooting.

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.

NetBrain currently does not provide an email notification indicating when a network change execution begins and when it completes. Users must manually monitor the change process to confirm whether it started and finished successfully. This enhancement would introduce automatic email alerts triggered at the start and end of a network change execution, including an indication of success or failure. Customers running network changes would gain timely confirmation of execution status without needing to manually track progress, improving change management visibility and reducing operational risk.