Recently active topics

NetBrain's Change Management module currently requires an approval step for every change task regardless of whether the change is classified as service-impacting or non-service-impacting, which can delay routine maintenance activities that carry minimal risk. This enhancement would allow administrators to designate certain change templates or tasks as non-service-impacting and permit those changes to be executed without requiring approval, while retaining the approval requirement for changes that carry service impact. Reducing unnecessary approval overhead for low-risk, routine changes would allow teams to execute maintenance work more efficiently while preserving governance controls for changes that carry higher risk.

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's API currently supports path calculation for individual source-destination pairs and does not provide a way to submit bulk, many-to-many path requests or to identify which firewalls are traversed along each resulting path. This enhancement would add an API capability to calculate paths across multiple source-destination pairs in a single bulk operation and return the firewalls present along each computed path. Customers implementing Zero Trust network segmentation would benefit from the ability to programmatically validate firewall placement and policy enforcement across large sets of network flows, reducing the manual effort required for segmentation audits and compliance verification.

I would like to suggest for consideration to add option remediate to configlet. So we can not only check all golden rules that apply for certain device, but also remediate them.NetBrain Case #00182577

The OneIP Table currently does not display VRF information for an IP address, even though this information is available and shown in device ARP tables. This enhancement would add a VRF column to the OneIP Table so that VRF context is visible alongside other IP details. Customers working in multi-VRF environments would benefit from improved visibility and would no longer need to cross-reference ARP tables to determine VRF membership.

NetBrain's REST API and Python API currently do not provide a method to programmatically execute the global 'Full Search' function that is available in the web UI, requiring users to submit each search manually through the interface. This enhancement would introduce an API endpoint that accepts full search queries and returns results equivalent to the UI-based search. Customers who need to run large volumes of searches would benefit from the ability to automate this process, reducing manual effort and enabling integration with external workflows.

NetBrain currently requires geolocation to be configured separately for each device through the geolocation manager, with no link to site definitions. As new devices are discovered and added to sites, they are not automatically assigned a geolocation, making it difficult to identify and update devices lacking location data, particularly across multiple domains. This enhancement would add a geolocation attribute to leaf site definitions, so that all devices belonging to a site automatically inherit that location. As site membership is refreshed during discovery, newly added devices would be assigned geolocation automatically without manual intervention. Extending the site management REST APIs to support geolocation attributes would also allow customers to automate site and geolocation setup for new domains or customers. This would reduce the manual effort required to maintain geolocation data, improve accuracy as networks scale, and simplify onboarding for customers managing many site

NetBrain currently requires administrators to configure discovery for each AWS account individually, with no capability to discover resources across an entire AWS Organization from a single configuration point. This enhancement would add native support for AWS Organization-level discovery, allowing administrators to provide organization-level credentials or a cross-account role so that all member accounts under the organization are automatically enumerated and included in discovery scope. Customers managing large multi-account AWS environments would benefit from simplified onboarding and complete visibility into their cloud infrastructure without manually configuring discovery for each individual account.

NetBrain's discovery and benchmark drivers for Cisco IOS Switch, Cisco Router, and Cisco SD-WAN Router devices currently issue the standard 'show running-config' command, which does not return default or implicit configuration parameters that some configuration assessment workflows require. This enhancement would introduce a driver option to retrieve configuration using 'show running-config all' instead, configurable so that it persists reliably across patches and upgrades and does not affect other tenants or customers in shared environments. Customers who rely on configuration assessment rule sets that depend on complete configuration detail, including default values, would benefit from consistent and accurate results without needing manual driver modifications after each upgrade.

Our organization restrict access to Public AI Models ( Open AI / ChatGPT etc.) for privacy and security concern. Is there any way where we can integrate the NetBrain with Internal / On prem AI model.

NetBrain currently does not support placing devices on a geographic map based on their physical location. This enhancement would introduce geolocation-based mapping, allowing devices to be plotted on a map view similar to common mapping applications, using location coordinates or address data associated with each device. Customers with geographically dispersed infrastructure, such as devices mounted on remote poles or field sites, would gain improved visibility into the physical distribution of their network assets.

Task Manager currently displays an internal, system-generated process identifier for tasks triggered by Network Intents, rather than the actual Intent name, making it difficult for administrators to identify which Intent is associated with a running or scheduled task. This enhancement would update Task Manager to display the actual Intent name for Intent-triggered tasks in place of the internal identifier. Providing this visibility would allow administrators to more efficiently monitor, troubleshoot, and manage scheduled and running tasks without needing to cross-reference internal naming conventions.

In Cloud Manager, add Equinix Fabric as a Cloud Type.

The Change Management execution node currently sends commands at a fixed time interval, or waits out a configured sleep timer, without evaluating whether the prior command has actually finished executing based on its output. This approach is unreliable for long-running operations, such as large file uploads or unzip operations during device image upgrades, where actual completion time can vary significantly and exceed a fixed wait period. This enhancement would introduce execution logic that inspects command output to determine whether a command has completed before issuing the next one, similar to behavior already used by device drivers. This would reduce failed or incomplete command sequences during long-running change operations and remove the need for administrators to manually tune sleep timers to accommodate worst-case execution durations.

NetBrain currently does not provide a way to run two different CLI commands, such as a startup configuration command and a running configuration command, against one or more devices and directly compare their outputs. Users must rely on the compare module for comparing results of the same command over time, which does not support comparing two distinct commands side by side. This enhancement would allow users to select two different CLI commands and one or more target devices, then generate a side-by-side comparison of the results. This capability would help network administrators quickly identify configuration drift between running and startup configurations, or between any two related commands, without manual cross-referencing.

NetBrain currently allows Inventory Reports to be generated and exported manually, but does not provide an option to schedule recurring generation with automatic email delivery. This enhancement would add a scheduling capability for Inventory Reports, allowing users to configure recurring runs (such as daily or weekly) with results automatically emailed to designated recipients. Customers who rely on Inventory Reports for ongoing asset and compliance tracking would benefit from reduced manual effort and more consistent access to up-to-date data.

Observability dashboards currently support only two status colors, green and red, to indicate condition states such as end-of-support timelines. This limits the ability to represent intermediate risk levels, such as an upcoming end-of-support date within a defined window. This enhancement would introduce additional configurable color options, such as yellow or orange, allowing status thresholds to be defined across multiple stages rather than a binary state. Customers tracking lifecycle or compliance timelines would gain a clearer, more actionable view of upcoming risk without relying on manual reporting outside the platform.

NetBrain configuration scripts today do not support a variable whose underlying value can differ by device while keeping the script logic uniform; when interface naming or other configuration elements vary across device types (for example, mgmt0 versus vlan161, or vendor-specific interface naming conventions), engineers must create separate scripts for each variation rather than a single reusable template. This enhancement would allow users to define a global variable and map it to distinct values for each device or device group, then reference that variable within a configuration script so the script automatically resolves to the correct value at execution time. Customers managing large, heterogeneous device fleets would be able to build standardized change templates that account for non-standard configurations across devices, reducing the need to maintain and distribute multiple versions of the same script.

NetBrain currently allows devices to be organized into groups on a map, but the grouped devices remain individually displayed, which can make large or complex maps difficult to read. This enhancement would allow a device group to be collapsed into a single representative icon or box, with the option to expand it back to view the individual member devices. Providing this capability would improve readability of large topology maps and allow users to focus on relevant sections of the network without visual clutter from unrelated device groupings.

NetBrain currently does not optimize device positioning on site maps to reduce the number of crossing links, which can make maps with many connections difficult to read. This enhancement would introduce a layout algorithm that automatically arranges devices to minimize link crossings when a map is generated or refreshed. Customers managing large or densely connected site maps would benefit from clearer, more readable topology views without manual repositioning.

Device Group exclusion criteria currently only support a static list of manually selected devices, which does not update when the referenced source group's membership changes. This requires administrators to manually re-open dependent groups and adjust the exclusion list whenever devices are added or removed from the excluded group, creating ongoing maintenance overhead and risk of drift between groups. This enhancement would allow a Device Group's exclusion criteria to reference another Device Group directly as a live object rather than a static device list. When the referenced group's membership changes, the dependent group's computed membership would update automatically on next evaluation. Customers managing groups with overlapping or conditional membership requirements would benefit from reduced manual maintenance and improved accuracy in group-based access, compliance, or reporting workflows.

NetBrain currently requires administrators to manually configure map layout and link visibility settings, such as switching to a downward tree layout or hiding Layer 2 links, on a site-by-site basis. In environments with a large number of sites, this manual process is time-consuming and prone to inconsistency across the site map hierarchy. This enhancement would introduce a global, admin-configurable setting that allows a defined map layout style and link visibility rules to be applied consistently across all site maps at once, rather than requiring individual site-level adjustments. This reduces manual configuration effort, ensures visual consistency across large site map hierarchies, and lowers the administrative burden for customers managing extensive network topologies.

NetBrain currently retrieves and stores device configuration data without masking password-type values that may appear in clear text or reversible form, such as bind-password entries found in some device configurations. This exposes sensitive credential information to anyone with access to the retrieved configuration data. This enhancement would mask or redact password-type values within configuration retrieval output, consistent with how such values are protected elsewhere in the product, helping customers reduce credential exposure risk and meet security and compliance requirements around sensitive data handling.