Skip to main content

Filter by idea status

Filter by features

102 Ideas

pedrozacNew Participant

There are two different methods for accessing the Network Settings that are inconsistentOpen

We have identified an inconsistency within the application's Network Settings interface. Although the application provides two distinct methods for accessing Network Settings, the functionality presented through each method is not aligned.Method 1: Network Settings via Navigation MenuAccessing Network Settings through the navigation menu displays the following expected columns:Alias SNMP Version SNMP String Device CountDuring device discovery in this view, newly detected devices do not automatically sort to the top of the list. Users must manually right‑click a device and move it upward, which can significantly increase workload when handling a large number of discovered devices.Method 2: Network Settings via Discovery PageWhen navigating to the Discovery Page and selecting Networking under the Discover Devices via SNMP/CLI section, a pop‑up window is displayed. This pop‑up includes an Enable column that is not available in the interface accessed through the navigation menu. This additional column introduces functionality that is inconsistent with the first method. The two access points for Network Settings present differing layouts and capabilities. The absence of the Enable column in the first method and its exclusive presence in the second method creates usability gaps and may lead to inconsistent configuration of discovered devices. To ensure a unified and efficient user experience, alignment of functionality across both access methods is recommended. Recommended ActionsStandardize Interface Elements Across Both Access MethodsEnsure that both Network Settings interfaces display the same set of columns, including the Enable column, Alias, SNMP Version, SNMP String, and Device Count. This will reduce confusion and provide consistent configuration options regardless of entry point.Implement Automatic Device SortingIntroduce functionality that automatically sorts newly discovered devices to the top of the list in both methods. This enhancement will improve efficiency, especially when processing large numbers of devices during discovery.

simon.luiNew Participant

probe Windows and Unix endpoints and use their data for map calculations to support end-to-end troubleshootingOpen

It will be very helpful if NetBrain can probe endpoint devices similar to how it probe network switches/routes.Useful data from the endpoints will be things like Interface, Ipconfig/ifconfig, route table, etc.Utilization metrics is also good, but even if we only have configuration data, it will be very help for end-to-end troubleshooting.In one of the recent incident meeting I went to...we found that the server is missing static route and therefore, the specific application traffic is being send out the default route interface.   For this case, we will not be able to see that on NetBrain bcoz it doesn’t calculate the path considering the route table on the endpoints.Based on what I can see on NetBrain 101 and 102 class, I think all the basic data concept are there …. configuration, interface, route tables, etc etc…… if we can get NetBrain to SSH to Unix servers to run some CLI commands (and remote execute powershell CLI commands on Windows servers) … I think we can have all the necessary config/data on NetBrain.If NetBrain can extent the discovery and mapping to endpoints with some configuration details, I think it will become a even more popular tools for troubleshooting.   It will certainly be my go-to tools… and I will be recommending it to all the customer supporting by our company (Kyndryl).If you need a co-create / pilot account, let me know and I will be happy to participate.Thanks.