Skip to main content
💡

Open

Browse open ideas available for voting, feedback, and discussion.
🛣️

On the Roadmap

View ideas that are planned for future product development.
🛠️

In Development

Explore ideas that are currently being developed by the product team.
✅

Available

Explore ideas that are now available in the product.
🚫

Not Planned

View ideas that are not currently planned for product development.

Filter by idea status

Filter by features

1146 Ideas

NetBrain Idea GroupCommunity Manager

Display Alias for Privilege Credentials in Shared Device SettingsOn the Roadmap

When a device is configured with only a Privilege password and no Privilege Username, the Privilege Username field in Shared Device Settings displays as empty, giving users no visual confirmation of which credential alias is currently selected. This enhancement would display the associated Alias in the Privilege Username field whenever no explicit username is configured, so the selected credential set remains visible. Customers troubleshooting device connectivity would gain clarity on which credentials are active without needing to modify shared settings that could affect other devices using the same profile.

0
Forum|Forum|1 month ago
NetBrain Idea GroupCommunity Manager

Correct leaf switch selection across ACI multi-datacenter pods in path calculationOn the Roadmap

NetBrain path calculation for Cisco ACI fabrics can currently include leaf switches from a data center or pod that is not part of the actual traffic path, producing a calculated path that does not reflect real forwarding behavior across multi-site or multi-pod ACI deployments. This enhancement would extend the path calculation logic to recognize pod and site boundaries within an ACI fabric, ensuring that only leaf switches within the correct data center are included in the calculated path. Customers operating multi-DC ACI environments would gain accurate path visibility, reducing confusion during troubleshooting and eliminating the need to manually verify which data center the calculated path actually traverses.

0
Forum|Forum|1 month ago
NetBrain Idea GroupCommunity Manager

Detailed Platform Usage Analytics and ReportingOpen

NetBrain currently does not provide detailed usage reporting that shows how individual users interact with the platform, including which QApps, Runbooks, DVTs, or features are being used, how many users rely on a given tool, or how frequently specific devices are accessed. The existing Automation Usage overview on the Domain page also lacks clarity, as it does not explain what its figures represent or how they are calculated. This enhancement would introduce detailed usage analytics and reporting covering per-user, per-feature, and per-device activity, including QApp, Runbook, DVT, and automation/diagnosis execution statistics with clearly defined metrics. This capability would help administrators demonstrate platform value to management, identify unused artifacts for cleanup, and compare usage of overlapping functionality against unique capabilities to better guide automation strategy.

0
Forum|Forum|1 month ago
Anand SNew Participant

Pre-Upgrade Antivirus and Endpoint Protection Detection CheckOpen

NetBrain's UI upgrade process does not currently detect whether antivirus or endpoint protection software is actively running on the server before an upgrade begins. Because such software can block file replacement, executable installation, DLL updates, or Windows service operations, upgrades may fail partway through with permission or access-denied errors that are only discovered after the process has started. This enhancement would add a pre-upgrade check that detects active antivirus or endpoint protection software and displays a warning before the upgrade proceeds, giving the user the option to cancel or continue after acknowledging the risk. Providing this early visibility would help customers proactively adjust their security software settings, reducing upgrade failures, troubleshooting effort, and related support cases while improving overall upgrade reliability.

0
Forum|Forum|1 month ago
nareshkumar.gnanakrishnanNew Participant

Tag-Based Filtering for VNet/VHub Discovery in Public CloudOpen

NetBrain currently does not support filtering VNet and VHub discovery by resource tags within public cloud environments. This enhancement would allow users to specify tag-based criteria when discovering VNets and VHubs, so that only resources matching the defined tags are included in the discovery scope. Customers managing large or multi-tenant Azure environments would benefit from more targeted discovery, reducing unnecessary resource inclusion and improving the efficiency of cloud network mapping.

0
Forum|Forum|1 month ago
Sankar SagiNew Participant

Include Loopback Interface IP Addresses in OneIP TableOpen

The OneIP Table currently does not include loopback interface IP addresses, even though it includes other IP types such as Load Balancer Virtual IPs. This creates an incomplete view of all IP addresses present in the environment. This enhancement proposes updating the OneIP Table to include loopback interface IP addresses alongside existing supported IP types, so that the table represents all IP addresses in the system. Customers rely on the OneIP Table as a comprehensive reference for IP address data, and closing this gap would improve accuracy for troubleshooting, auditing, and inventory reporting.

0
Forum|Forum|1 month ago
adoNew Participant

Include Public Cloud Resource IP Associations in OneIP TableOpen

The OneIP Table does not currently include IP addresses associated with public cloud resources, even when those IP addresses are visible within the resource's own detail view. This creates a gap for users who only have an IP address and need to identify the corresponding cloud resource. This enhancement would extend OneIP Table data collection to capture and display name-to-IP associations for public cloud resources, such as those in Azure, AWS, and GCP environments. Customers managing public cloud infrastructure would benefit from consistent IP-based lookup across their environment, reducing the need for manual cross-referencing when only an IP address is available.

0
Forum|Forum|1 month ago
Prabu_RNew Participant

Scenario and Device-Type Scoped CLI Command Restriction RulesOpen

NetBrain currently enforces CLI command data retrieval rules (include, exclude, startWith) through a single global configuration that applies uniformly across all scenarios and all device types. This means administrators cannot permit a command in one context, such as Change Management, while restricting the same command in another context, such as Runbook or Deep Diagnosis, and cannot apply a restriction to one device type without unintentionally affecting others. This enhancement would introduce a rule structure that allows command permissions to be defined and overridden at the scenario level and the device-type level, rather than through a single global rule. Customers with diverse operational workflows and mixed device environments would gain more precise control over which commands are permitted in each context, reducing the risk of unintended restrictions or overly permissive access.

0
Forum|Forum|1 month ago
tomas.minovskyNew Participant

API Parity for Path Calculation Failure DetailsOn the Roadmap

NetBrain's path calculation API currently returns only a general failure reason and the IP pair between which a path failed, without exposing the specific security group, checkpoint rule, or other blocking detail that the Web UI displays for the same failed path. This creates a gap between the level of diagnostic detail available through the UI and what is accessible programmatically. The API should be enhanced to return the same detailed blocking information available in the UI, including the specific rule or object that caused the failure at the relevant hop. Customers automating path validation and troubleshooting through the API would gain the ability to pinpoint the exact cause of a path failure without needing to cross-reference results in the Web UI, improving efficiency for automated network verification workflows.

0
Forum|Forum|1 month ago
wclaffeyNew Participant

Automated Zero-Downtime Platform Upgrade ProcessOpen

NetBrain platform upgrades currently require a single upgrade execution path that can result in service downtime while components are brought offline and updated. Achieving zero downtime today requires customers to manually perform a server-by-server upgrade sequence, which is time-consuming and dependent on manual coordination. This enhancement would introduce an automated rolling upgrade capability that sequences the upgrade across servers in a multi-server deployment, keeping the platform available throughout the process. Automating this workflow would reduce the operational burden of manual upgrade coordination and allow customers running critical, high-availability environments to upgrade without service interruption.

0
Forum|Forum|1 month ago
gxsdNew Participant

Display Device IP or Range in Discovery History Selection WindowOpen

When reviewing prior discovery results, the selection window presented after clicking Select currently displays only Start Time, User, Task Result, and Duration, with no indication of the IP address or range associated with each discovery run. This enhancement would add an IP address or IP range column to the Discovery History selection popup, allowing users to identify the correct historical discovery entry without opening each record individually. This change would reduce the time and effort required to locate specific discovery results, particularly in environments with a high volume of discovery history entries.

0
Forum|Forum|1 month ago
guillermo.r.lozanoNew Participant

Dynamic Group Reference for Device Group Exclusion CriteriaOpen

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.

0
Forum|Forum|1 month ago
gxsdNew Participant

On-Demand Path Decoding for Map Intent on Ad Hoc PathsOpen

NetBrain currently limits Map Intent and Path Intent health-check execution to devices and interfaces that have already been loaded into the Path Browser or an Automated Data Table (ADT). When a user runs an ad hoc path, the intent does not decode or assess devices and interfaces outside of that pre-loaded set, requiring additional path-loading or ADT-rebuild steps before a full assessment can complete. This enhancement would allow Map Intent to decode and assess all devices and interfaces associated with a selected ad hoc path directly, regardless of whether that path has been previously loaded into the Path Browser or ADT. Removing this dependency would reduce the time required for real-time troubleshooting and improve the effectiveness of on-demand health checks during application-performance investigations.

0
Forum|Forum|1 month ago
Sankar SagiNew Participant

Surface MCP Server Audit Logs in System Management UIOpen

NetBrain currently stores MCP Server audit log data as a file on the web server, requiring administrators to access the file system directly to review it rather than viewing it within the product interface. This enhancement would surface MCP Server audit log content within the System Management page, either under the existing Audit Logs section or a dedicated sub-tab. Administrators would gain a consistent, in-application view of MCP Server activity alongside other system audit information, improving visibility and reducing the need for direct server access during troubleshooting or compliance review.

0
Forum|Forum|1 month ago
VinayKumarNew Participant

FQDN support for Smart CLI source address configurationOpen

NetBrain currently requires the Smart CLI source address to be entered as a static IP address, with no option to specify a fully qualified domain name. This enhancement would allow administrators to configure the Smart CLI source using an FQDN, which the system would resolve as needed for connections. Supporting FQDN would reduce maintenance overhead for customers whose source addresses change periodically, since the FQDN could remain constant while underlying IP assignments are updated independently.

0
Forum|Forum|1 month ago
joshchorbcNew Participant

Support for Retrieving Full Device Configuration via Generated Batch File CommandAvailable

NetBrain currently relies on a single consolidated command to retrieve full device configuration for supported models. For devices that do not offer such a command but instead can generate a batch file containing the complete configuration, there is no supported way to retrieve and parse that file through NetBrain. This enhancement would allow NetBrain to issue a command that triggers generation of a configuration batch file on the device and then retrieve that file for use in configuration checks and analysis. Supporting this retrieval method would extend certification coverage to device models that lack a single consolidated show command, giving customers consistent configuration visibility across a wider range of hardware.

0
Forum|Forum|1 month ago
ravish dangiNew Participant

Hosted Cloud MCP Connector Service for AI Assistant IntegrationOpen

NetBrain's current AI assistant integration requires each user to install and maintain a local Python wrapper, including a .env file, SSL certificate configuration, and library dependencies. This creates onboarding friction, as every user must replicate the same manual setup, which is time-consuming and prone to inconsistency across machines. This enhancement proposes a NetBrain-hosted, managed cloud MCP endpoint that AI assistant clients can connect to directly through a single URL, without requiring any local wrapper, configuration file, or per-machine setup. Users would authenticate once through OAuth to establish the connection. A hosted cloud MCP service would significantly reduce onboarding effort and allow the integration to scale reliably across teams, removing the maintenance burden associated with distributed local setups.

0
Forum|Forum|1 month ago
manojkumar26789New Participant

Restore right-click "Retrieve Live Data" option on map devicesOpen

NetBrain currently does not provide a right-click option on map devices to directly retrieve live data; users must navigate through multiple additional steps to achieve the same result. This enhancement would reinstate a direct right-click "Retrieve Live Data" action from the map context menu for individual devices. Restoring this streamlined workflow would improve efficiency for users who frequently need quick access to current device data without extra navigation.

0
Forum|Forum|1 month ago
Gerry.zhangNetBrain Employee

Automatic Email Notification for Published CBR PatchesOpen

NetBrain currently does not provide an automated way to notify customers when a patch has been published for their reported case, requiring customers to check manually or rely on other communication channels for updates. This is particularly limiting for customers operating in offline mode, who have no visibility into patch availability without proactive outreach. This enhancement would introduce an automatic email notification triggered upon patch publication, informing the affected customer that a patch is available for their case. Providing this notification would improve customer awareness of patch availability, reduce follow-up inquiries, and support a more responsive experience for customers, including those in offline environments.

0
Forum|Forum|1 month ago
gxsdNew Participant

Dedicated API role scoped to TAFlite-managed ADT accessOpen

NetBrain does not currently provide a clearly defined or dedicated role scoped to inbound API access for data sourced only from a TAFlite-managed ADT. Administrators lack guidance or a purpose-built permission set for this scenario, which can lead to over-provisioning broader roles just to enable this limited data access. This enhancement would introduce a distinct, assignable API role or permission scoped specifically to TAFlite-managed ADT data retrieval, separate from broader administrative or data access roles. Customers would benefit from tighter adherence to least-privilege access principles, allowing API integrations to retrieve TAFlite ADT data without granting unnecessary broader system access.

0
Forum|Forum|1 month ago
Prabu_RNew Participant

StatusCode-Based Stop Condition Filtering for Triggered Diagnosis LoopsOpen

Today, the Stop When condition for a Repeat Triggered Diagnosis loop can only halt execution based on a generic alert detection result. It cannot distinguish between different diagnosis outcomes using StatusCode-based filtering, so a loop cannot be configured to stop specifically on a SUCCESS result in addition to an ALERT result. This enhancement would allow the Stop When condition to filter on specific StatusCode values, enabling the loop to stop and trigger a Follow-up Triggered Diagnosis action whether the diagnosis returns ALERT or SUCCESS. Supporting both outcomes would let diagnostic logic and business notification actions remain cleanly separated, allowing tickets to be automatically escalated for human follow-up on critical conditions or closed automatically once conditions resolve, without manual intervention.

0
Forum|Forum|1 month ago
manojkumar26789New Participant

Global FQDN Trim Setting for CLI-Parsed HostnamesOpen

NetBrain currently applies FQDN trimming only to hostnames retrieved via SNMP, with no equivalent centralized option for hostnames retrieved via CLI. Each device driver implements its own CLI hostname parsing logic independently, requiring per-driver customization to strip domain suffixes. This enhancement would introduce a global setting, similar to the existing SNMP FQDN trim option, that enables or disables FQDN trimming uniformly for CLI-parsed hostnames across all drivers. Customers managing large, multi-vendor environments would benefit from consistent short-hostname formatting without maintaining custom logic for each driver.

0
Forum|Forum|1 month ago
robertbeumerNew Participant

Support for IP Unnumbered L3 Link MappingOpen

NetBrain currently cannot correctly map Layer 3 links between devices that use IP unnumbered interfaces, where a point-to-point interface borrows its address from a loopback rather than having its own unique subnet. Although the neighbor relationship may be detected in the neighbor discovery table, the platform is unable to resolve and place the correct point-to-point link on the topology map. This enhancement would add logic to identify and accurately map L3 links for IP unnumbered interfaces, using available neighbor and interface data to determine the correct link endpoints. Customers using IP unnumbered addressing to conserve address space would gain accurate, automated topology visibility without needing to manually add or correct links on the map.

0
Forum|Forum|1 month ago
manojkumar26789New Participant

Rebuild Option for ADT Created via Import from System TableOpen

NetBrain currently does not provide an option to rebuild an Automated Data Table (ADT) once it has been created using the 'Import from System Table' method, leaving the table static after initial creation. This enhancement would add a rebuild action for ADTs created this way, allowing the table to be refreshed against its system table source on demand. Customers relying on system table imports for their ADTs would be able to keep the data current without recreating the table manually.

0
Forum|Forum|1 month ago
Ivan Uribe
Ivan UribeNew Participant

Restrict Login Activity to Target Device During Single Device DiscoveryOpen

NetBrain currently does not guarantee that a single-device discovery operation limits authentication attempts strictly to the targeted device; login activity may extend to other previously discovered devices, triggering unrelated security alerts. This enhancement would introduce a discovery mode or setting that restricts login and authentication attempts to only the specified target device when a single-device discovery is initiated. Customers with active security monitoring on their network infrastructure would benefit from reduced false-positive alerts and clearer visibility into which operations initiate device authentication.

0
Ivan Uribe
Forum|Forum|1 month ago
Submit an Idea

Filter by features

  • All features
  • AI
  • Automation
  • Benchmark
  • Change Management
  • Data Management
  • Digital-Twin
  • Installation&Deployment
  • Integration
  • Live Access
  • Map
  • Multi-Vendor Support
  • NetBrain API
  • Others
  • Path
  • Runbook
  • System Health Monitoring
  • System Management
Terms & ConditionsAccessibility statement