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 represents Cisco Catalyst switches configured as Virtual Switching System (VSS) or StackWise Virtual as a single logical device on the map, even though the underlying chassis are physically separate and, in some deployments, installed in different locations connected only through standard front-panel ports. This enhancement would allow the two chassis in a VSS or StackWise Virtual pair to be displayed as two linked device representations on the map, connected via the inter-switch link, with data such as MAC, ARP, and routing information collected from the active member and mapped to the appropriate chassis based on module-specific port naming. Device naming would use a stable suffix indicating chassis membership rather than an active/standby designation that can change over time. This would give customers an accurate physical topology view for stacked switches, supporting correct link visualization and easier troubleshooting when chassis members reside in different physical locations.
Service Monitor currently displays a status banner indicating that the Service Monitor Agent has been stopped, and this banner is visible to all users regardless of role. Standard, non-administrative users who have no ability to act on this information may see the banner and mistakenly believe the application is malfunctioning. This enhancement would restrict visibility of the Service Monitor Agent status banner to administrator users only, or provide a configurable setting that allows administrators to control which user roles see this notification. Limiting banner visibility to users who can act on the information would reduce unnecessary support inquiries and prevent confusion among standard users when services are intentionally stopped for maintenance or performance reasons.
NetBrain currently displays a Virtual Switching System (VSS) or similarly stacked chassis configuration as a single device icon on the topology map, even though the underlying deployment consists of two or more physically stacked switches. This limits the accuracy of site topology visualization for customers who rely on the map to reflect actual physical device counts and connections. This enhancement would introduce a way to represent stacked chassis configurations more accurately on the map, either by rendering each member chassis as a separate connected device or by using a distinct icon that clearly indicates a device stack. Customers would benefit from improved topology accuracy, which supports better network documentation and troubleshooting for environments that rely on virtual switching stacks.
The upgrade guide currently does not instruct administrators to verify Service Monitor status before initiating an upgrade, leaving a gap in pre-upgrade preparation steps. This enhancement would add a dedicated section to the upgrade guide outlining how to check Service Monitor health and status prior to starting the upgrade process. Providing this guidance would help customers identify and resolve service issues beforehand, reducing the risk of complications during the upgrade.
NetBrain currently displays its tab on every ServiceNow incident once the integration is enabled, regardless of whether NetBrain has performed any automation or added diagnostic value to that incident. This enhancement would introduce logic to show the NetBrain tab only on incidents where NetBrain has executed automation or contributed relevant data. Limiting tab visibility to value-added incidents would reduce clutter for ServiceNow users and help teams quickly identify which incidents received NetBrain analysis.
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 consolidated way to export system-level details such as Tenants, Domains, Sites, Device access status categories, Scheduled tasks, and license information into a single spreadsheet. This enhancement proposes adding a system-level export capability that allows administrators to generate a CSV or Excel report containing this combined information. Customers managing large multi-tenant environments would benefit from a streamlined way to compile system-wide data for reporting and auditing purposes without manually gathering information from multiple screens.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.