Version 1.3 includes port scanning (which can be disabled if that sort of thing makes you nervous), support for Cisco ISO base wireless access points, retrieval of Cisco configs, and SNMP data collection for Juniper and Enterasys devices. NetMRI analyzes network health and assigns a relative quantification of 1 through 10. In my case, I ended up at a 7.2 health index, which Netcordia says is good.
Product Roll Call
Dig Deeper (on-site search queries)
Read On
|
|
It took me about five minutes to set up the brick-sized NetMRI Campus 200 model, and five minutes more to define a couple of local subnets for it to monitor. I had to wait until the next day to see results. The box is not interactive; rather, it checks the network on an ongoing basis and issues daily reports, which are found on the easy-to-use administrative Web interface.
The reports are logically divided into four sections. The results section lists network performance and history. The network-information section includes route, subnet, OS, VLAN and port summaries. The performance section shows a quick glimpse into CPU, memory, and device and interface availability. The historical section shows device, route, subnet, VLAN, HSRP, reboot, and configuration changes and stability for the past 30 days.
The second morning of my tests, I had a list of concerns to begin addressing on, prioritized by severity, including weak security SNMP strings, open HTTP interfaces, mismatched full- and half-duplex switch connections and a version of IOS that had an SNMP memory leak. When I drilled down into the SNMP memory leak, I was given two references--Google and Cisco TAC--from which to pinpoint the problem and the fix.