10-10-2010 03:12 AM
There are a few network devices discovered through seed file method.
When i see the device details post disovery, it Discovery device profile shows
When i do a Configuration poll on the device it get the below output.
Using timeout of 600 seconds.
Connecting to server for configuration poll.
10/10/10 2:53:16 PM **** Starting configuration poll of node sw39cr20 ****
10/10/10 2:53:16 PM Supports SNMP V2C
10/10/10 2:56:16 PM Get NodeInfo retrieved no data because this device does not support a way of collecting data.
10/10/10 2:56:16 PM Node analysis failed in analyzer NodeClassifier with an error status of No rule to collect DD.
10/10/10 2:56:16 PM **** End of configuration poll for node sw39cr20 ****
We checked with the network team and found SNMP agent is up and running, Communication string we are using is correct and NNMi server is permitted to access the device throug SNMP.
what could be the reason for Configuration poll to fail??
11-11-2011 12:20 AM
Same here with some nodes (Microsens devices - probably no supported device profiles).
Did someone find a solution (or soem more hints) for this issue?
03-08-2012 08:12 AM
So have you seen whats available via a mibwalk for the usual syspects like RFC 1213 (aka SYSTEM) and the Entity MIB ?
I've got some terminal servers that somewhat support SNMP, but have the very annoying habit of not providing any interface names or descriptions which makes alarms from them useless. Every NOC techniction wants to see Interface down Null Null traps.
Andy Kemp, CISSP
03-12-2012 08:21 AM
thank you for the reply.
Yes, the devices respond properly to snmp requests and deliver desired values via MIB browser as well as via snmpwalk.
But, they are not supported in the device support matrix, and I assume that some parts of their MIB is not so "standard compliant", so I created an Enhancement Request to extend the support matrix.
Have a good time.