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.
In Fine Tune, there is a section called Devices Exceeding License (0), below that are Foundation (0) and WAP (0). What is missing here are the exceeded licenses for ACI.I know I can find that information under the Current Domain but this should be added in this section as well.
I would like to see front server redundancy in case one server has connectivity or life issues, maintenance etc. Idea: start with a (semi)-intelligent assignment of devices to FS by calculating a priority based on values like latency or features (tags) like region, SNMP info (e.g. contact), NB tags, FS overload, line of business. All available FS matching certain criteria will be added to the device according to their priority. Latency will give you the best connectivity and tags let you select specific FS to prevent all devices being assigned to one FS. If one FS is not able to reach the device, the next FS will take over. A daily task could be created to re-evaluate priorities and assignments.
We used inventory report quite much to share network information within the team and with other teams. But right now we can only export those reports and share them manually. One issue with this process is that, people cannot get up-to-dated reports. When receiving a report from others, we cannot make sure if this is the latest one. So people have to export reports regularly to get the latest information. If we can share a report with link which can automatically refresh, that would be super helpful for collaboration.
our Firewall peer-A and firewall peer-B are using the same cluster group# for redundancy, hence the same MAC. In order to address the miscalculation in L2 topology, NetBrain should not only look at the MAC table, but also do routing table and ARP table correlation.
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.