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.
L2 topology maps currently do not apply consistent logic for where a wire-connector attaches to a device based on the target device's layer or relative position. As a result, connectors can attach at arbitrary points on a device, producing maps that appear cluttered or inconsistently organized. This enhancement would introduce directional connector placement rules: when the target device resides on a different layer and is positioned south, the connector would attach to the south side of the device; when the target device is on the same layer and is a direct neighbor positioned west or east, the connector would attach to the corresponding west or east side. Applying these rules would produce cleaner, more predictable map layouts, improving readability and reducing the need for manual connector adjustment on large topologies.
NetBrain currently supports integration with the classic Aruba Central platform, but does not support the newer Aruba Central platform, which uses a different authentication method and returns API output in a different structure. This enhancement would add a dedicated integration path for the new Aruba Central platform, including its updated authentication flow and API response handling, so that discovery and monitoring can function correctly against it. Customers who have migrated or are migrating to the new Aruba Central platform would gain continued visibility and management capability without being blocked by the underlying platform change.
NetBrain inventory does not currently include a criticality attribute that can be assigned to and displayed for each asset. This enhancement would add a criticality field available across all assets in the inventory, allowing values to be set and viewed consistently within inventory reports. Customers would benefit from the ability to classify assets by importance, supporting prioritization in monitoring, troubleshooting, and change management workflows.
NetBrain currently does not provide a way to consolidate table data collected from multiple devices, such as MAC address tables, into a single spreadsheet that identifies the source device for each row. Users must manually combine separate per-device outputs and add the hostname themselves before the data is usable for analysis. This enhancement proposes adding a capability to select multiple devices from a site map, collect a specified data table across those devices, and export the combined results into a single Excel sheet with the device hostname included as a column alongside the existing table fields. Customers managing multiple switches would benefit from reduced manual effort when compiling cross-device table data for network analysis and reporting.
NetBrain does not always correctly calculate Layer 3 links between devices that share a common subnet, even when each device has a properly discovered interface and IP address. In some cases no link is drawn between devices in the same subnet despite other L3 links existing for that subnet, and in other cases a link is drawn but fails to attach to the existing link group for that subnet. This enhancement would improve the L3 link calculation logic to reliably identify and connect all devices sharing a common subnet into a single, accurate link representation on the topology map. Customers relying on automated L3 topology mapping would gain more complete and trustworthy network diagrams, reducing the need for manual link correction and improving confidence in troubleshooting and documentation.
NetBrain currently does not support Aruba Fabric Composer (AFC) as an API source type, which prevents discovery of devices managed through that platform. This enhancement would add Aruba Fabric Composer as a selectable API source type within API Server Manager, enabling discovery and modeling of associated devices alongside other supported platforms. Customers running Aruba Fabric Composer-managed environments would gain complete device visibility without relying on manual workarounds.
NetBrain currently requires A-B path scheduling through AAM/Benchmark tasks to include all path devices within an existing Benchmark scope. Organizations with multiple Benchmarks already configured for different parts of their network find this setup cumbersome, since new A-B path requirements often do not align cleanly with existing Benchmark boundaries. This enhancement proposes introducing a distinct Path Task type within Domain Management/Schedule Tasks, positioned alongside the existing Benchmark Task and Discovery Task options, that links to AAM without requiring path devices to fall within a single Benchmark scope. This would give administrators a more flexible and organized way to schedule A-B path monitoring, reducing setup complexity for networks with multiple, independently scoped Benchmarks.
NetBrain currently models Layer 2 topology links as point-to-point connections between two interfaces. When a single interface, such as a LAN interface on an SD-WAN device, is physically or logically connected to multiple neighboring devices through shared media, the platform cannot accurately represent this as a single multipoint connection, resulting in incomplete or misleading L2 topology diagrams. This enhancement would introduce support for point-to-multipoint L2 link rendering, allowing a shared interface to connect to a bus or shared-media object that in turn links to multiple downstream devices. Customers operating environments where a single interface serves multiple connected devices would gain accurate, automated L2 topology visibility that reflects actual network design, reducing the need for manual link correction.
NetBrain currently requires devices to be accessible via CLI or API to be fully onboarded and managed within the platform; devices reachable only through SNMP and a web-based GUI cannot be fully supported and are limited to partial data collection. This enhancement would introduce a supported access method that allows NetBrain to interact with devices through their web GUI when CLI and API access are unavailable. Customers using devices that expose only SNMP and web management interfaces would gain more complete device visibility and management capability without relying on manual workarounds.
NetBrain's API Server Manager currently does not include SonicWall Firewall as a supported API source type, which prevents customers from configuring SonicWall devices for API-based discovery. This enhancement would add SonicWall Firewall as a selectable source type in API Server Manager, allowing discovery and modeling of SonicWall devices alongside other supported platforms. Customers running SonicWall infrastructure would gain complete device visibility and audit-ready inventories without relying on manual workarounds.
NetBrain currently does not support Ubiquiti as an API source type within the API Server Manager, which prevents discovery of Ubiquiti devices through the platform's API-based discovery methods. This enhancement would add Ubiquiti as a selectable API source type so that Ubiquiti devices can be configured and discovered alongside other supported device types. Customers running Ubiquiti infrastructure would gain full device visibility within NetBrain without relying on manual workarounds.
NetBrain currently expects devices to be reachable via SNMP or CLI to be fully onboarded and maintained in Live Access status, with ICMP-only reachability generally resulting in incomplete or excluded device records. This enhancement proposes a supported discovery and Live Access mode that allows devices to be discovered and tracked using ICMP (ping) only, without requiring SNMP or CLI credentials to establish a valid device record. Customers operating in environments where SNMP and CLI access are restricted or unavailable for certain devices would benefit from broader and more accurate network visibility, rather than having those devices excluded or misrepresented in the domain inventory.
NetBrain does not currently provide a way to import a spreadsheet of IP addresses and resolve DNS hostnames for entries that are not yet discovered devices in the domain. Users must rely on devices already present in the OneIP Table to obtain hostname resolution, which limits usefulness when planning hardware upgrades or replacements that will reuse existing IP addresses and DNS names. This enhancement proposes allowing users to import a spreadsheet of IP addresses into the OneIP Table workflow so that NetBrain performs DNS resolution against that imported list, independent of device discovery status. Customers preparing for hardware upgrades or IP reassignment would benefit from validating DNS hostname mappings in advance, reducing manual lookup effort and improving planning accuracy.
NetBrain's Change Management workflow currently supports only a single internal approval step and does not support chaining an additional approval through an external privileged access management system after the initial change request approval. Additionally, when credentials must be retrieved from a privileged access management system to complete a device or network setting update, there is no supported way to invoke multiple related plugins in sequence within a single Runbook. This enhancement would allow a Change Management workflow to route through a secondary external approval step after the primary approval, and would support chaining plugin calls within a Runbook so that an approved access link can be used to retrieve credentials and apply them directly to device or network settings. Customers using privileged access management systems alongside change approval processes would benefit from an automated, end-to-end workflow that reduces manual handoffs and strengthens compliance with credential governance requirements.
NetBrain does not currently offer a native or certified adapter for integrating with ManageEngine OPManager, a widely used network monitoring platform. This enhancement would add a supported integration that allows NetBrain to exchange device and monitoring data with OPManager, such as pulling end-system details or cross-referencing discovered devices. Customers running OPManager alongside NetBrain would benefit from consolidated visibility and reduced manual effort in correlating data between the two platforms.
NetBrain audit logs currently capture only login activity for Smart CLI sessions, without recording which domain or device was accessed during the session. This enhancement would expand Smart CLI audit logging to include the domain and device information associated with each session. Capturing this detail would support security and compliance requirements by giving administrators full visibility into user activity across domains and devices.
NetBrain currently does not show neighbor device information when a user expands a device to view its sub-interfaces on a topology map; neighbor data is only visible at the physical interface level. This enhancement would extend neighbor discovery and display logic so that sub-interfaces show their connected neighbor devices in the same way physical interfaces do. Customers who model both physical and logical sub-interface connections on their maps would gain complete topology visibility, reducing manual investigation when tracing logical connections.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.