NetBrain R13 Is Now Available: Build Your Agentic NetOps Team
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 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.
NetBrain currently displays a Cisco Nexus switch and its attached Fabric Extender (FEX) as a single combined unit on the map, even though the FEX may be physically installed in a separate rack from the parent switch. This enhancement would allow the FEX to be rendered as a distinct device object on the map, separate from its parent Nexus switch, while preserving the logical association between them. Providing this level of granularity would give customers accurate physical topology representation, improving documentation and troubleshooting for environments where FEX units are not co-located with their parent switch.
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.
It would be very beneficial if Alerts Rules generated SNMP Traps, along with email notifications. If we received an SNMP Trap in Solarwinds, for example, we would then be able to generate a Service-now ticket. A Service-now ticket could also be created if the NetBrain servers themselves had issues.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.