Hi, Thanks for the details!
On Feb 5, 2014, at 11:34 AM, jcat <j...@nysasounds.co.uk> wrote:
> SELECT n.nodeid, n.foreignsource, n.foreignid, i.snmpifdescr, i.snmpifname,
> i.snmpphysaddr from node n, snmpinterface i where n.nodeid = i.nodeid and
> i.snmpcollect in ('C','UC') and i.snmpphysaddr is not null and
> i.snmpphysaddr='';
> ~~~8<~~~
> (115 rows)
>
> ..in other words, some of the snmpinterface entries are not null, but
> "nothing" or "blank".
Interesting ... Definitively, I should check if the values are blank or not,
maybe that could be related with the problem.
> I also noticed, and this may or may not be an issue, that snmpifname is
> sometimes null, even though snmpifdescr is populated:
>
> SELECT n.nodeid, n.foreignsource, n.foreignid, i.snmpifdescr, i.snmpifname,
> i.snmpphysaddr from node n, snmpinterface i where n.nodeid = i.nodeid and
> i.snmpcollect in ('C','UC') and i.snmpphysaddr is not null and snmpifname is
> null;
> ~~~8<~~~
> (456 rows)
In this case, it should not be a problem because the labeling rules for SNMP
Interfaces is: use ifName if exist. If not, use the ifDescr. Then if the
Physical Address exist, add it.
> If these unexpected results are the issue, I guess you could either update
> the query or add some more handling in your parsing logic.
>
> What do you think?
I agree. That's what I'm going to do.
Alejandro.
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
