ISPPlanet NMS Series - MG-SOFT NetInspector and MIB Browser

Network Discovery

We started by using NetInspector to discover our test network, creating a workspace. Objects in the workspace represent discovery apps, device monitors, and subnets. The default workspace (right) includes ICMP and SNMP discovery objects that automatically search NetInspector's own subnet for any device responding to a ping or public SNMP GET.

 

NetInspector's discovery interface is unusual. First, create a discovery object that identifies the IP range to search, the discovery protocol, and parameters like community string and timeout. Set the object's "Start" attribute "True" to start the search. Progress is shown two places: a generic event window and discovery object attributes. After the search, use the discovery object's menu to launch a Discovery Wizard (left).

The wizard creates a new object for every found device, populating an existing or new subnet map. We found this process awkward compared to other discovery widgets we've seen. We also uncovered an odd bug: If the IP range is extended beyond a single class C, only the original class C will be discovered -- even when the range is reset to a different class C. Create new discovery objects for every class C subnet to avoid this problem.

NetInspector discovery creates topology maps that monitor status via SNMP polling or traps, ICMP ping, UDP echo, or Internet services (see Network Monitoring). The workspace you'll create can be saved for later use; events are optionally logged and settings like window layout and size (but not scroll position) are retained for each workspace.

If you plan to use MIB Browser Professional Edition for device management, you'll need to repeat discovery using the browser's Remote SNMP Agent Discovery (right).

This simple tool quickly finds and displays all SNMP agents in any contiguous address range. Discovered agents can be added to the MIB Browser's pull-down IP menu or automatically polled (see Network Monitoring). We found the MIB Browser's discovery faster and easier to use than NetInspector's, but the browser does not produce a topo map like NetInspector. This example illustrates how the MIB Browser and NetInspector are two independent, slightly overlapping products. The ability to "drill down" from NetInspector map objects to the MIB Browser would create a stronger product duo.