1) Setup opennms to discover and poll/scan dummy interfaces only, node has two dummy's and 1 ethernet 2) edit configs to discover and poll/scan ethernet ip on existing node
When going to Choose SNMP Interfaces for Data Collection you will see ifdesrciptions with null as value, yet not reflected in ipinterface or snmpinterface table.
This bug has been marked as a duplicate of 1058 ***
Ted Kaczmarek January 21, 2005 at 1:09 PM
This is definetly messed up. I also suspect this is related to the other bug, that shows up in KSC reports as well, .
The test case is Create two dummy interfaces on a node
Add that node to OpenNMS, but do not discover, scan or poll the ethernet interfaces IP address.
Change the OpenNMS config to now disc, scan and poll the ethernet IP address.
I don't think it is ok to have a row in the snmpinterface table for a valid ethernet ip interface with null values for snmpipadentnetmask, snmpphysaddr, snmpifspeed, snmpifadminstatus and snmpifoperstatus
Former user January 21, 2005 at 11:39 AM
Do you mean that this is not a bug after all? If its not then you can cancel it.
Matt
Ted Kaczmarek January 21, 2005 at 8:18 AM
My bad, their is a null entry in the snmpinterface table, but that should not be their
Ted Kaczmarek January 21, 2005 at 8:17 AM
This is with latest head, FC1 and Blackdown-1.4.2-01.
1) Setup opennms to discover and poll/scan dummy interfaces only, node has two
dummy's and 1 ethernet
2) edit configs to discover and poll/scan ethernet ip on existing node
When going to Choose SNMP Interfaces for Data Collection you will see
ifdesrciptions with null as value, yet not reflected in ipinterface or
snmpinterface table.