NNM dotted its I's and crossed its T's with the mapping and autodiscovery process. It wasn't perfect (none are) but the inclusion of seed files kept it under control, and the fact that NNM didn't try to discover every ARP entry it met made it better than most. An additional feature that turns off autoplacement of newly discovered devices also helped us keep control over what we were managing.
The discovery process is short and painless, mapping all devices in a nice, organized structure. The rediscovery process is excellent as well; the frequency of polling for new nodes decreases as fewer devices are discovered in each polling cycle. Also, when we turned off the autolayout function, NNM placed newly found objects in a holding area. That way we could control the placement and management of newly discovered devices.
The map hierarchy is represented in five levels--root, Internet, network, segment and node--but map navigation could have been better designed. Often NNM zeroed in on a particular section of the network or a blank portion of the map by default, so we became good friends with the pan and zoom options.
NNM shows its maturity in the number of devices and vendors it can discover and identify. It supports DMI, IP and IPX, and hundreds of enterprise MIBs, and it provides the ability to add more.
In OvLauncher, NNM's Web interface, we were like bulls in a china shop; we couldn't decide what to break next. Canned NNM reports include availability, exception, inventory and performance. We ran them all and then modified them to create new reports. Availability reports showed daily, month-to-date and general availability. Inventory reports broke down devices by type; for example, routers, switches, workstations, printers, segments and networks. Canned performance reports included Cisco Router TopTalkers and Top SNMP Interface Utilization, which are reported daily and month-to-date.