wbrown

What are you really looking for? What you describe is available as soon as you install NCM and add some nodes.

We'd really like to see support for integration with Infoblox DHCP appliances.

NCM started in our environment as simply a way to backup configs. However it has become invaluable in keeping configs standardized. For example I can ensure that unneeded services are disabled, AAA configurations consistent, logging is configured at the correct levels with traps to the correct destinations, and updating…

It means that those interfaces hadn't been previously discovered and then imported or ignored by that polling engine. Discovery seems to keep its own table of what exists, completely independent of what has already been manually added, for each polling engine. Importing the discovered interfaces that were already monitored…

As I've mentioned in other posts I'm one of those paranoid people that doesn't like systems making automatic changes to my configs. However, the scenario postulated is valid and I've seen a similar example used for automatic provisioning of virtual servers. As I think about this I'm questioning my paranoia as I try to…

Scanning a /16 is REALLY not advised. Doing so requires 65,000 devices to either respond or time out. If most of those /16s are not densely populated then your discovery is going to be waiting for a whole bunch of multi-second timeouts before it can move to the next IP to scan. If you have the IPAM module then I'd suggest…

I've had a similar issue when adding network devices. In those cases the issue was due to the polling services on the assigned poller had failed. The services on the poller appeared to be running but restarting the services, or rebooting the poller in some instances, was required in order to add the node with the specified…

Cisco hasn't always been consistent across differing model lines when it comes to which OIDs represent power supplies and fans. Which chassis are you looking to monitor?

Have you tried disabling the discovery jobs? Or add the affected switches to the discovery ignore list?

I've got a poller and associated reports for 6500's and 4500's here:

The unwanted interfaces can be added to the ignore list after discovery, but this quickly becomes impractical as your number of access ports and VLANs increase. There is no way at this time to filter what interfaces are discovered. The approach I've taken is to unselect all ports when importing a node and then go back to…

Not trying to hijack the thread, but how is your CPU utilization monitoring? None of my 6500's show the correct CPU utilization when I compare NPM's graphs to the output from show proc cpu hist. I have this across all code versions: Adv Enterprise, modular, non-modular, 12.2(17), 12.2(18), 12.2(33), SXF, SXH, SXI. I don't…

I have a number of devices that get discovered as such, in addition to the actual host address. Running NPM 10.3.1 I haven't reported this as an issue because I recall someone else mentioning this in the forums and I think it was mentioned that this was fixed in 10.4