Browse, vote, and track the status of feature requests from the NetBrain community
Browse open ideas available for voting, feedback, and discussion.
View ideas that are planned for future product development.
Explore ideas that are currently being developed by the product team.
Explore ideas that are now available in the product.
View ideas that are not currently planned for product development.
NetBrain currently does not provide a way to configure or limit the number of concurrent connections used during Discovery and Benchmark tasks. Network segments with a restricted number of available authentication sessions, such as environments with limited TACACS license capacity, can be affected when NetBrain opens more simultaneous connections than the environment can support. This enhancement would allow administrators to set a configurable concurrency value within Discovery and Benchmark task settings to control the maximum number of simultaneous connections. This would help customers with session-constrained network segments avoid authentication failures and maintain stable task execution.
NetBrain currently requires users to view logical and physical topology elements in separate views, and the logical view does not surface as much supporting detail as some troubleshooting workflows require. This enhancement would introduce a unified view that combines logical and physical elements, along with expanded information displayed directly within the logical view. Consolidating this data would reduce the need to switch between views during troubleshooting and give customers a more complete picture of network state in a single pane.
The Shared Device Settings interface currently displays the Username field from the Privilege Login Table as the key identifier, even when the Username field is blank for the majority of entries that instead rely on an Alias. This makes it difficult for users to identify which login credential set is in use at a glance. This enhancement would allow the Alias field to be displayed in place of, or alongside, the Username field so that the identifying label is populated consistently. Customers using alias-based credential naming would gain improved visibility and reduce the risk of misconfiguration when managing shared device settings.
NetBrain's device list import wizard does not provide feedback when an import fails, leaving users unable to determine which line or device caused the failure, including cases involving duplicate entries. This enhancement would add a detailed error message to the import process that identifies the specific line, device, or condition (such as a duplicate) causing the failure. Customers would be able to correct import issues directly rather than manually checking each device one by one, reducing troubleshooting time and improving the reliability of bulk device onboarding.
NetBrain currently requires administrators to update device credentials one domain or device group at a time, with no mechanism to apply a credential change across multiple domains or device groups in a single action. This is time-consuming for organizations that must periodically rotate credentials, particularly service or automation accounts, across a large number of domains. This enhancement proposes a bulk credential update capability that allows administrators to select multiple domains or device groups and apply a credential change to all of them in one operation. Customers managing large environments with frequent credential rotation requirements would benefit from reduced manual effort and lower risk of missed or inconsistent updates during rotation cycles.
NetBrain currently does not provide a way for administrators to designate a default Runbook that automatically displays for all users when a map is opened. Each user must manually select or locate the appropriate Runbook, which can lead to inconsistent behavior across teams working on the same maps. This enhancement would introduce an administrator-configurable setting that assigns a default Runbook to a map, so that the designated Runbook is automatically presented to any user who opens that map, regardless of individual user preferences. This would ensure consistent Runbook usage across teams, reduce the risk of users selecting an incorrect or outdated Runbook, and streamline the change execution workflow for organizations with standardized processes.
NetBrain's ACI discovery process currently identifies active APIC controllers within a fabric but does not detect or display standby APIC controllers in the network tree, even when a fabric spans multiple pods with a designated standby node. This enhancement would extend SDN discovery logic to recognize standby APIC controllers and represent them alongside active controllers in the topology view. Full visibility into APIC redundancy status helps customers confirm fabric resiliency and quickly identify controller-level issues without relying on manual verification outside NetBrain.
NetBrain currently creates user accounts automatically upon first successful TACACS+ login, but it provides no corresponding mechanism to remove or deactivate those accounts when the associated user is deleted from TACACS+. Administrators must identify and remove unused accounts manually. This enhancement would introduce a scheduled process that checks NetBrain user accounts against TACACS+ to confirm continued existence, and automatically deactivates or removes accounts that are no longer present after a configurable inactivity period. This would reduce the administrative burden of manual account audits and lower the security risk associated with orphaned or stale user accounts.
L2 topology maps currently display the configured interface alias (such as a firewall nameif value like 'inside') rather than the underlying physical interface name. This makes it difficult to correlate the L2 map with physical cabling and hardware-level troubleshooting, since the alias does not reveal which physical port is in use. This enhancement would allow L2 topology to render the physical interface name (e.g., ge0/1, ge0/2) alongside or in place of the interface alias, without requiring any change to L3 topology behavior. Providing accurate physical interface labeling in L2 maps would improve troubleshooting efficiency and give customers clearer visibility into physical connectivity, particularly for devices that use custom or logical interface naming conventions.
NetBrain currently sends discovery task alerts as a single combined notification, covering both task execution failures and newly discovered devices. Teams that only need visibility into new device additions cannot separate that information from operational error alerts, and both alert types are routed to the same recipients. This enhancement would allow administrators to configure discovery alerts as two independent notification types: one for task execution failures and one for newly added device reports, each with its own enable/disable toggle and its own recipient email list. This would let organizations route alerts to the appropriate audience, reducing irrelevant notifications and improving response efficiency for teams with different monitoring responsibilities.
NetBrain currently requires administrators to manually configure External Authentication settings, such as Active Directory group-to-role mappings, each time a new Tenant or Domain is created. This becomes burdensome for organizations that provision large numbers of Tenants or Domains on an ongoing basis. This enhancement would allow administrators to define a default External Authentication template that automatically applies to newly created Tenants or Domains, including group-based access assignments. Customers managing large-scale, frequently changing multi-tenant environments would benefit from reduced manual configuration effort and consistent, immediate access for authorized users upon Tenant or Domain creation.
NetBrain currently does not provide an email notification when a scheduled plugin fails to execute successfully. This enhancement would add an email alert option to the plugin scheduler that triggers automatically upon a failed run. Customers would gain timely visibility into scheduling failures without needing to manually check plugin status, improving operational reliability.
Today, the version or history list for a device displays every captured snapshot regardless of whether meaningful changes were detected between versions, requiring users to manually scan through entries to find relevant ones. This enhancement would add a button or toggle that filters the list to show only the versions where changes were actually discovered. Customers reviewing device history would save time and reduce noise by focusing only on versions that reflect real configuration or state changes.
NetBrain currently requires administrators to manually export the Vendor Model Table from one tenant and import it into each additional tenant or domain to keep OID mappings consistent, which becomes time-consuming as the number of tenants grows. This enhancement would introduce a built-in capability to replicate or synchronize Vendor Model Table changes across multiple tenants directly within the platform, removing the need for manual export and import steps. Customers managing large multi-tenant environments would save administrative effort and reduce the risk of configuration drift between tenants.
NetBrain currently requires an open map and manual runbook execution to view ongoing health status, which limits practical long-term monitoring for users outside the network team. This enhancement would introduce a continuous, always-on health monitoring view that runs indefinitely on a small map without requiring an open session or manual triggers, and would present progress through graphs accessible to non-technical stakeholders. Historical logs of the monitoring output should be retained to support after-action review and root-cause analysis following an outage. This capability would give organizations a simple, persistent way to observe landscape health over time without relying on network specialists to initiate or interpret each check.
NetBrain currently exports the full site map, including the NBR page, whenever a scheduled task updates and exports the map to Visio, and there is no option to exclude specific pages that contain no usable content for the customer's network. This enhancement would allow users to select which pages to include when configuring a scheduled site map export to Visio, or provide a setting to suppress the NBR page from the output. Customers running recurring Visio export tasks would save time by not having to manually remove unwanted pages after each scheduled run.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.