Recently active topics

NetBrain currently does not allow users to filter or search for devices by Last Discovery Time when building a Device Group, and it does not provide a bulk action to remove outdated devices directly from the Inventory Report. As a result, administrators must manually identify and delete stale or offline devices one at a time, or rely on manual CSV export and custom API scripting to clean up the domain. This enhancement would add Last Discovery Time as a searchable criterion for Device Group creation and introduce a bulk 'Remove from Domain' action available from the Inventory Report or a resulting Device Group. Customers managing large device inventories would benefit from a streamlined, repeatable method to identify and remove outdated or retired devices, reducing manual effort and improving overall inventory accuracy.

NetBrain Change Management currently does not support executing configuration changes through API-driven firewall management platforms such as FortiManager, Palo Alto Panorama, and Cisco Firepower Management Center. As a result, customers managing firewalls through these centralized platforms cannot leverage CM automation and must rely on manual, out-of-band change processes for these devices. This enhancement would extend Change Management to integrate with the APIs of FortiManager, Panorama, and Firepower Management Center, allowing changes to be pushed and tracked through these platforms in the same manner as other supported device types. This would give customers consistent, automated change workflows across multi-vendor firewall environments, reducing manual effort and improving change tracking and compliance for security infrastructure.

NetBrain currently relies on CLI-based or SNMP-based polling to retrieve BGP routing information and does not support BMP (BGP Monitoring Protocol) as a data collection method for BGP route monitoring. This enhancement would add BMP support, allowing NetBrain to receive real-time BGP route updates and state changes directly from routers configured as BMP stations. Customers with large or dynamic BGP environments would benefit from more timely and lower-overhead BGP route visibility, reducing dependence on repeated polling and improving the accuracy of route change detection.

Chat Bot automation currently executes only one Network Intent at a time, even when multiple intents share a matching tag or are selected together within an Automated Data Table. This enhancement would allow multiple intents to be triggered and run concurrently, either through tag-based matching or by selecting multiple intents within the ADT for simultaneous execution. Enabling concurrent intent execution would allow end users to perform multiple diagnostic checks in a single automation cycle, reducing troubleshooting time and improving overall efficiency of automated workflows.

When installing rules through Rule Discovery, users must manually unselect each rule individually if they only want to install a subset, such as vendor-specific rules. This enhancement would add an 'Unselect All' or 'Clear Selection' action to the Config Rule Template selection interface, allowing the full list to be cleared in a single action before filtering and selecting the desired rules. Customers installing targeted rule subsets would benefit from a faster, less error-prone selection workflow.

NetBrain currently requires each Golden Intent to be scheduled individually, with no option to configure scheduling across multiple intents at once. This enhancement would allow users to select multiple Golden Intents and apply or update scheduling settings simultaneously in a single action. Customers managing large numbers of Golden Intents would benefit from reduced administrative effort and faster configuration of recurring checks.

NetBrain currently does not automatically propagate device inventory updates across all nodes in a clustered deployment, requiring administrators to manually verify and synchronize device changes between environments. This enhancement would allow device additions, removals, or updates to be automatically reflected across all cluster nodes without manual intervention. Customers operating multiple synchronized environments would benefit from consistent device visibility and reduced administrative effort in maintaining cluster parity.

NetBrain currently requires users to manually extract diagnosis results from a Network Intent or automation unit and use them to define a corrective change within the Change Management module, with execution initiated separately by the user. This enhancement would allow diagnosis results from an Intent or automation unit to automatically trigger creation of a change runbook, populate the required change definition, and route the change for approval; once approved, the change would execute automatically to resolve the identified issue. Customers performing proactive corrective maintenance or incident remediation would benefit from a fully automated, approval-gated workflow that reduces manual effort and accelerates issue resolution.

NetBrain currently requires users to manually assign Layout Tags to individual devices, even when those devices belong to a defined device group. When a device group's membership changes, such as new devices being added or existing devices removed, the associated tags do not update automatically, requiring repeated manual effort to keep tagging accurate. This enhancement proposes allowing a Layout Tag to be associated directly with a device group so that any device added to the group automatically inherits the tag, and any device removed from the group has the tag automatically removed. Customers managing large or frequently changing device groups would benefit from consistent, up-to-date tagging without ongoing manual maintenance.

The audit log currently does not provide sufficient detail to identify the exact nature of a change made within the system, making it difficult for administrators to trace specific modifications. This enhancement would expand audit log entries to capture granular details of each change, such as the specific field, setting, or configuration element affected and its before-and-after values. Administrators would benefit from improved visibility into system changes, supporting faster troubleshooting and more accurate compliance and change management reviews.