Lefthand OIDs still not working

7 messages Options
Embed this post
Permalink
Dennis Crandall

Lefthand OIDs still not working

Reply Threaded More More options
Print post
Permalink
I have:

1) Created a new snmp-collection section in the
datacollection-config.xml file.  Its name is: Lefthand
2) Added the appropriate graph entries into snmp-graph
3) Created a new collectd-configuration section in
collectd-configuration.xml file looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<collectd-configuration
    xmlns="http://xmlns.opennms.org/xsd/config/collectd" threads="50">
    <package name="Lefthand1">
        <filter>IPADDR != '0.0.0.0'</filter>
        <include-range begin="172.20.50.201" end="172.20.50.201"/>
        <service name="SNMP" interval="300000" user-defined="false" status="on">
            <parameter key="collection" value="Lefthand"/>
            <parameter key="thresholding-enabled" value="true"/>
        </service>
    </package>
    <package name="example1">
        <filter>IPADDR != '0.0.0.0'</filter>
        <include-range begin="1.1.1.1" end="254.254.254.254"/>
        <service name="SNMP" interval="300000" user-defined="false" status="on">
            <parameter key="collection" value="default"/>
            <parameter key="thresholding-enabled" value="true"/>
        </service>
    </package>
    <collector service="SNMP"
class-name="org.opennms.netmgt.collectd.SnmpCollector"/>
</collectd-configuration>

My problem is that this node still shows up with it's old OIDs in the
GUI.  And the graphs are not showing up as well.

Any thoughts on how I could troubleshoot this further?

Thanks!

Dennis Crandall

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Jeff Gehlbach

Re: Lefthand OIDs still not working

Reply Threaded More More options
Print post
Permalink
On Nov 4, 2009, at 12:40 PM, Dennis Crandall wrote:

> 1) Created a new snmp-collection section in the
> datacollection-config.xml file.  Its name is: Lefthand
> 2) Added the appropriate graph entries into snmp-graph
> 3) Created a new collectd-configuration section in
> collectd-configuration.xml file

Dennis, this is all good information, thanks for providing it.  Could  
you reply with your collectd-configuration.xml and datacollection-
config.xml in their entirety, perhaps zipped up to keep the size  
down?  I know you posted snippets of these before, but seeing them  
whole and with any changes you've made since the last go-round can  
make all the difference.  Also helpful would be a screenshot of the  
node detail page for the Lefthand node in the OpenNMS web UI.

I notice that this post isn't threaded under your previous messages on  
this topic.  There's a classic article with some excellent tips on,  
among other things, maintaining threading on mailing lists as a way to  
get your questions answered on lists like this one:

http://catb.org/~esr/faqs/smart-questions.html

-jeff

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Dennis Crandall

Re: Lefthand OIDs still not working

Reply Threaded More More options
Print post
Permalink
On Wed, Nov 4, 2009 at 23:44, Jeff Gehlbach <[hidden email]> wrote:

> On Nov 4, 2009, at 12:40 PM, Dennis Crandall wrote:
>
>> 1) Created a new snmp-collection section in the
>> datacollection-config.xml file.  Its name is: Lefthand
>> 2) Added the appropriate graph entries into snmp-graph
>> 3) Created a new collectd-configuration section in
>> collectd-configuration.xml file
>
> Dennis, this is all good information, thanks for providing it.  Could
> you reply with your collectd-configuration.xml and datacollection-
> config.xml in their entirety, perhaps zipped up to keep the size
> down?  I know you posted snippets of these before, but seeing them
> whole and with any changes you've made since the last go-round can
> make all the difference.  Also helpful would be a screenshot of the
> node detail page for the Lefthand node in the OpenNMS web UI.
>
> I notice that this post isn't threaded under your previous messages on
> this topic.  There's a classic article with some excellent tips on,
> among other things, maintaining threading on mailing lists as a way to
> get your questions answered on lists like this one:
>
> http://catb.org/~esr/faqs/smart-questions.html
>
> -jeff
Yes, I was subscribed to this list with digest-mode on and it messed me up.

I have attached the files.

Thanks!

Dennis




------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

LefthandConfFile.tgz (125K) Download Attachment
LefthandSanChooseGraphicsSnapshot.jpg.gz (27K) Download Attachment
LefthandSanUISnapshot.jpg.gz (98K) Download Attachment
Jeff Gehlbach

Re: Lefthand OIDs still not working

Reply Threaded More More options
Print post
Permalink
On Nov 5, 2009, at 8:24 AM, Dennis Crandall wrote:

> I have attached the files.

OK, from the node detail page screenshot I see that the ATXDEVSAN01's  
sysObjectID is .1.3.6.1.4.1.8072.3.2.10.  As I think you know already,  
that means "a Net-SNMP agent running on Linux", so you've created a  
custom SNMP collection in datacollection-config.xml called "Lefthand"  
and made a new package in collectd-configuration.xml that includes  
only the ATXDEVSAN01 node's primary interface.  One technicality  
that's probably not an issue: you used a "sysoidMask" in the systemDef  
you made in the new collection, but when you know the exact  
sysObjectID you should use "sysoid" instead since "sysoidMask" checks  
for a prefix match rather than an exact match.  Also, you mentioned  
you'd tried changing the "name" attribute of your systemDef; for the  
record, there's nothing magical about the name.  You could have called  
it "Jim" or "Glenn" if you wanted.

You created a set of custom resourceTypes in your new collection for  
the objects in the Lefthand MIB, but you never actually use these  
types -- normally the name of the appropriate resourceType would  
appear as the value of the "instance" attribute for all the mibObj  
elements in one group.  Instead, you have specified constant numeric  
instance IDs in all your mibObjs.   That's OK, but it's not doing what  
you wanted.

I think what you need to do is this.  In your "lhn-modules" collection  
group, change the "clusModStorStatus1" mibObj so that its alias is  
just "clusModStorStatus" and its instance is "clusModuleEntry" (the  
name of the resourceType you defined to represent a module in a  
cluster).  Kill the "clusModStorStatus2", "clusModStorStatus3", and  
"clusModStorStatus4" mibObjs.  Likewise, kill mibObjs  
"clusModStatsIOsRd2" through "clusModStatsIOsRd4" and change mibObj  
"clusModStatsIOsRd1" so that its alias is just "clusModStatsIOsRd" and  
its instance is "clusModuleEntry".  Do the same for each of the other  
"foo1-4" mibObjs in this group.  Finally, track down the OID for the  
"clusModuleName" object and add a mibObj for it to this group, with  
the same instance.  Without doing this last item, your resource labels  
will read literally "${clusModuleName} (index N)".

Also, since you're using OpenNMS 1.6.5, you need to add one more group  
to your "Lefthand" collection in order to work around bug 2447:

<group name="bug-2447-workaround" ifType="all">
   <mibObj oid=".1.3.6.1.2.1.2.2.1.2" instance="ifIndex"  
alias="obIfDescr" type="string" />
</group>

You need not reference this group anywhere; it just needs to be  
present inside your "Lefthand" collection.  After you upgrade to 1.6.6  
or later you can remove it.

At this point I would suggest restarting OpenNMS so that the changes  
to datacollection-config.xml will take effect.  Wait 10 minutes and  
then enter the resource graphs workflow for the ATXDEVSAN01 node.  If  
you've gotten everything right, you should now see a new pick-list in  
the "Choose Resource Graphs" page with a header of "LHN Cluster Module  
Name".  There should be one entry in the list for each cluster module  
in the SAN.  The graphs will still be broken, but the presence of this  
list is your indication that you've straightened out one of your  
collection groups.

If that worked, you'll move on to remediate the "lhn-cluster" and "lhn-
volume" groups in the same style as you did the "lhn-modules" group  
above.  I believe you'll have nine mibObjs in "lhn-cluster" (all with  
instance="clusClusterEntry") after you add the string one for  
clusClusterName.  And there should be ten mibObjs in lhn-volume, all  
with instance="clusVolumeEntry" once you've added the string one for  
clusVolumeName.

The last thing will be to remediate the graph definitions.  As a  
starter, your lefthand.modulestatsIOsRead definition should get the  
following changes:

report.lefthand.modulestatsIOsRead.columns=clusModStatsIOsRd
report.lefthand.modulestatsIOsRead.type=clusModuleEntry

And instead of four DEFs, four LINE2s, and twelve GPRINTs, you'll have  
one DEF:

DEF:clusModStatsIOsRd={rrd1}:clusModuleStatsIOsRd:AVERAGE

And you'll use that clusModStatsIOsRd token in the one LINE2 and three  
GPRINT statements.

I hope this helps.  I know it's a lot to digest.

-jeff

--
Jeff Gehlbach               mailto|sip:[hidden email]
The OpenNMS Group, Inc.     ph: +1 919.533.0160 x7754


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Dennis Crandall

Re: Lefthand OIDs still not working

Reply Threaded More More options
Print post
Permalink
On Thu, Nov 5, 2009 at 23:23, Jeff Gehlbach <[hidden email]> wrote:

> On Nov 5, 2009, at 8:24 AM, Dennis Crandall wrote:
>
>> I have attached the files.
>
> OK, from the node detail page screenshot I see that the ATXDEVSAN01's
> sysObjectID is .1.3.6.1.4.1.8072.3.2.10.  As I think you know already,
> that means "a Net-SNMP agent running on Linux", so you've created a
> custom SNMP collection in datacollection-config.xml called "Lefthand"
> and made a new package in collectd-configuration.xml that includes
> only the ATXDEVSAN01 node's primary interface.  One technicality
> that's probably not an issue: you used a "sysoidMask" in the systemDef
> you made in the new collection, but when you know the exact
> sysObjectID you should use "sysoid" instead since "sysoidMask" checks
> for a prefix match rather than an exact match.  Also, you mentioned
> you'd tried changing the "name" attribute of your systemDef; for the
> record, there's nothing magical about the name.  You could have called
> it "Jim" or "Glenn" if you wanted.
>
> You created a set of custom resourceTypes in your new collection for
> the objects in the Lefthand MIB, but you never actually use these
> types -- normally the name of the appropriate resourceType would
> appear as the value of the "instance" attribute for all the mibObj
> elements in one group.  Instead, you have specified constant numeric
> instance IDs in all your mibObjs.   That's OK, but it's not doing what
> you wanted.
>
> I think what you need to do is this.  In your "lhn-modules" collection
> group, change the "clusModStorStatus1" mibObj so that its alias is
> just "clusModStorStatus" and its instance is "clusModuleEntry" (the
> name of the resourceType you defined to represent a module in a
> cluster).  Kill the "clusModStorStatus2", "clusModStorStatus3", and
> "clusModStorStatus4" mibObjs.  Likewise, kill mibObjs
> "clusModStatsIOsRd2" through "clusModStatsIOsRd4" and change mibObj
> "clusModStatsIOsRd1" so that its alias is just "clusModStatsIOsRd" and
> its instance is "clusModuleEntry".  Do the same for each of the other
> "foo1-4" mibObjs in this group.  Finally, track down the OID for the
> "clusModuleName" object and add a mibObj for it to this group, with
> the same instance.  Without doing this last item, your resource labels
> will read literally "${clusModuleName} (index N)".
>
> Also, since you're using OpenNMS 1.6.5, you need to add one more group
> to your "Lefthand" collection in order to work around bug 2447:
>
> <group name="bug-2447-workaround" ifType="all">
>   <mibObj oid=".1.3.6.1.2.1.2.2.1.2" instance="ifIndex"
> alias="obIfDescr" type="string" />
> </group>
>
> You need not reference this group anywhere; it just needs to be
> present inside your "Lefthand" collection.  After you upgrade to 1.6.6
> or later you can remove it.
>
> At this point I would suggest restarting OpenNMS so that the changes
> to datacollection-config.xml will take effect.  Wait 10 minutes and
> then enter the resource graphs workflow for the ATXDEVSAN01 node.  If
> you've gotten everything right, you should now see a new pick-list in
> the "Choose Resource Graphs" page with a header of "LHN Cluster Module
> Name".  There should be one entry in the list for each cluster module
> in the SAN.  The graphs will still be broken, but the presence of this
> list is your indication that you've straightened out one of your
> collection groups.
>
> If that worked, you'll move on to remediate the "lhn-cluster" and "lhn-
> volume" groups in the same style as you did the "lhn-modules" group
> above.  I believe you'll have nine mibObjs in "lhn-cluster" (all with
> instance="clusClusterEntry") after you add the string one for
> clusClusterName.  And there should be ten mibObjs in lhn-volume, all
> with instance="clusVolumeEntry" once you've added the string one for
> clusVolumeName.
>
> The last thing will be to remediate the graph definitions.  As a
> starter, your lefthand.modulestatsIOsRead definition should get the
> following changes:
>
> report.lefthand.modulestatsIOsRead.columns=clusModStatsIOsRd
> report.lefthand.modulestatsIOsRead.type=clusModuleEntry
>
> And instead of four DEFs, four LINE2s, and twelve GPRINTs, you'll have
> one DEF:
>
> DEF:clusModStatsIOsRd={rrd1}:clusModuleStatsIOsRd:AVERAGE
>
> And you'll use that clusModStatsIOsRd token in the one LINE2 and three
> GPRINT statements.
>
> I hope this helps.  I know it's a lot to digest.
>
> -jeff

Wow!  I'll re-read this when I'm ready to work on this.  This is very
helpful!  Thanks for spending the time on it.

Dennis

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
Dennis Crandall

Re: Lefthand OIDs still not working

Reply Threaded More More options
Print post
Permalink
On Fri, Nov 6, 2009 at 10:10, Dennis Crandall <[hidden email]> wrote:

> On Thu, Nov 5, 2009 at 23:23, Jeff Gehlbach <[hidden email]> wrote:
>> On Nov 5, 2009, at 8:24 AM, Dennis Crandall wrote:
>>
>>> I have attached the files.
>>
>> OK, from the node detail page screenshot I see that the ATXDEVSAN01's
>> sysObjectID is .1.3.6.1.4.1.8072.3.2.10.  As I think you know already,
>> that means "a Net-SNMP agent running on Linux", so you've created a
>> custom SNMP collection in datacollection-config.xml called "Lefthand"
>> and made a new package in collectd-configuration.xml that includes
>> only the ATXDEVSAN01 node's primary interface.  One technicality
>> that's probably not an issue: you used a "sysoidMask" in the systemDef
>> you made in the new collection, but when you know the exact
>> sysObjectID you should use "sysoid" instead since "sysoidMask" checks
>> for a prefix match rather than an exact match.  Also, you mentioned
>> you'd tried changing the "name" attribute of your systemDef; for the
>> record, there's nothing magical about the name.  You could have called
>> it "Jim" or "Glenn" if you wanted.
>>
>> You created a set of custom resourceTypes in your new collection for
>> the objects in the Lefthand MIB, but you never actually use these
>> types -- normally the name of the appropriate resourceType would
>> appear as the value of the "instance" attribute for all the mibObj
>> elements in one group.  Instead, you have specified constant numeric
>> instance IDs in all your mibObjs.   That's OK, but it's not doing what
>> you wanted.
>>
>> I think what you need to do is this.  In your "lhn-modules" collection
>> group, change the "clusModStorStatus1" mibObj so that its alias is
>> just "clusModStorStatus" and its instance is "clusModuleEntry" (the
>> name of the resourceType you defined to represent a module in a
>> cluster).  Kill the "clusModStorStatus2", "clusModStorStatus3", and
>> "clusModStorStatus4" mibObjs.  Likewise, kill mibObjs
>> "clusModStatsIOsRd2" through "clusModStatsIOsRd4" and change mibObj
>> "clusModStatsIOsRd1" so that its alias is just "clusModStatsIOsRd" and
>> its instance is "clusModuleEntry".  Do the same for each of the other
>> "foo1-4" mibObjs in this group.  Finally, track down the OID for the
>> "clusModuleName" object and add a mibObj for it to this group, with
>> the same instance.  Without doing this last item, your resource labels
>> will read literally "${clusModuleName} (index N)".
>>
>> Also, since you're using OpenNMS 1.6.5, you need to add one more group
>> to your "Lefthand" collection in order to work around bug 2447:
>>
>> <group name="bug-2447-workaround" ifType="all">
>>   <mibObj oid=".1.3.6.1.2.1.2.2.1.2" instance="ifIndex"
>> alias="obIfDescr" type="string" />
>> </group>
>>
>> You need not reference this group anywhere; it just needs to be
>> present inside your "Lefthand" collection.  After you upgrade to 1.6.6
>> or later you can remove it.
>>
>> At this point I would suggest restarting OpenNMS so that the changes
>> to datacollection-config.xml will take effect.  Wait 10 minutes and
>> then enter the resource graphs workflow for the ATXDEVSAN01 node.  If
>> you've gotten everything right, you should now see a new pick-list in
>> the "Choose Resource Graphs" page with a header of "LHN Cluster Module
>> Name".  There should be one entry in the list for each cluster module
>> in the SAN.  The graphs will still be broken, but the presence of this
>> list is your indication that you've straightened out one of your
>> collection groups.
>>
>> If that worked, you'll move on to remediate the "lhn-cluster" and "lhn-
>> volume" groups in the same style as you did the "lhn-modules" group
>> above.  I believe you'll have nine mibObjs in "lhn-cluster" (all with
>> instance="clusClusterEntry") after you add the string one for
>> clusClusterName.  And there should be ten mibObjs in lhn-volume, all
>> with instance="clusVolumeEntry" once you've added the string one for
>> clusVolumeName.
>>
>> The last thing will be to remediate the graph definitions.  As a
>> starter, your lefthand.modulestatsIOsRead definition should get the
>> following changes:
>>
>> report.lefthand.modulestatsIOsRead.columns=clusModStatsIOsRd
>> report.lefthand.modulestatsIOsRead.type=clusModuleEntry
>>
>> And instead of four DEFs, four LINE2s, and twelve GPRINTs, you'll have
>> one DEF:
>>
>> DEF:clusModStatsIOsRd={rrd1}:clusModuleStatsIOsRd:AVERAGE
>>
>> And you'll use that clusModStatsIOsRd token in the one LINE2 and three
>> GPRINT statements.
>>
>> I hope this helps.  I know it's a lot to digest.
>>
>> -jeff
I made all of the changes that you suggested and retried this.  Still
no graphs.  I have attached the apropos sections of datacollect and
snmp-graph files plus screenshots.

Thanks!

Dennis


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss

files20091108.tar.gz (141K) Download Attachment
Dennis Crandall

Re: Lefthand OIDs still not working

Reply Threaded More More options
Print post
Permalink
Okay, I found that I had the oid that I had added per your
instructions was off by 1. *rolling eyes*

Now i'm seeing the following error in collectd.log: 2009-11-11
15:55:57,870 WARN  [CollectdScheduler-50 Pool-fiber2] SnmpAttribute:
Unable to process data received for attribute
node[89].interfaceSnmp[eth0-001e4f263587].ifDescr
[.1.3.6.1.2.1.2.2.1.2] = eth0 maybe this is not a number? See bug 1473
for more information. Skipping.

Trying to find information on bug 1473 now but not having any luck.

Dennis

On Sun, Nov 8, 2009 at 10:12, Dennis Crandall <[hidden email]> wrote:

> On Fri, Nov 6, 2009 at 10:10, Dennis Crandall <[hidden email]> wrote:
>> On Thu, Nov 5, 2009 at 23:23, Jeff Gehlbach <[hidden email]> wrote:
>>> On Nov 5, 2009, at 8:24 AM, Dennis Crandall wrote:
>>>
>>>> I have attached the files.
>>>
>>> OK, from the node detail page screenshot I see that the ATXDEVSAN01's
>>> sysObjectID is .1.3.6.1.4.1.8072.3.2.10.  As I think you know already,
>>> that means "a Net-SNMP agent running on Linux", so you've created a
>>> custom SNMP collection in datacollection-config.xml called "Lefthand"
>>> and made a new package in collectd-configuration.xml that includes
>>> only the ATXDEVSAN01 node's primary interface.  One technicality
>>> that's probably not an issue: you used a "sysoidMask" in the systemDef
>>> you made in the new collection, but when you know the exact
>>> sysObjectID you should use "sysoid" instead since "sysoidMask" checks
>>> for a prefix match rather than an exact match.  Also, you mentioned
>>> you'd tried changing the "name" attribute of your systemDef; for the
>>> record, there's nothing magical about the name.  You could have called
>>> it "Jim" or "Glenn" if you wanted.
>>>
>>> You created a set of custom resourceTypes in your new collection for
>>> the objects in the Lefthand MIB, but you never actually use these
>>> types -- normally the name of the appropriate resourceType would
>>> appear as the value of the "instance" attribute for all the mibObj
>>> elements in one group.  Instead, you have specified constant numeric
>>> instance IDs in all your mibObjs.   That's OK, but it's not doing what
>>> you wanted.
>>>
>>> I think what you need to do is this.  In your "lhn-modules" collection
>>> group, change the "clusModStorStatus1" mibObj so that its alias is
>>> just "clusModStorStatus" and its instance is "clusModuleEntry" (the
>>> name of the resourceType you defined to represent a module in a
>>> cluster).  Kill the "clusModStorStatus2", "clusModStorStatus3", and
>>> "clusModStorStatus4" mibObjs.  Likewise, kill mibObjs
>>> "clusModStatsIOsRd2" through "clusModStatsIOsRd4" and change mibObj
>>> "clusModStatsIOsRd1" so that its alias is just "clusModStatsIOsRd" and
>>> its instance is "clusModuleEntry".  Do the same for each of the other
>>> "foo1-4" mibObjs in this group.  Finally, track down the OID for the
>>> "clusModuleName" object and add a mibObj for it to this group, with
>>> the same instance.  Without doing this last item, your resource labels
>>> will read literally "${clusModuleName} (index N)".
>>>
>>> Also, since you're using OpenNMS 1.6.5, you need to add one more group
>>> to your "Lefthand" collection in order to work around bug 2447:
>>>
>>> <group name="bug-2447-workaround" ifType="all">
>>>   <mibObj oid=".1.3.6.1.2.1.2.2.1.2" instance="ifIndex"
>>> alias="obIfDescr" type="string" />
>>> </group>
>>>
>>> You need not reference this group anywhere; it just needs to be
>>> present inside your "Lefthand" collection.  After you upgrade to 1.6.6
>>> or later you can remove it.
>>>
>>> At this point I would suggest restarting OpenNMS so that the changes
>>> to datacollection-config.xml will take effect.  Wait 10 minutes and
>>> then enter the resource graphs workflow for the ATXDEVSAN01 node.  If
>>> you've gotten everything right, you should now see a new pick-list in
>>> the "Choose Resource Graphs" page with a header of "LHN Cluster Module
>>> Name".  There should be one entry in the list for each cluster module
>>> in the SAN.  The graphs will still be broken, but the presence of this
>>> list is your indication that you've straightened out one of your
>>> collection groups.
>>>
>>> If that worked, you'll move on to remediate the "lhn-cluster" and "lhn-
>>> volume" groups in the same style as you did the "lhn-modules" group
>>> above.  I believe you'll have nine mibObjs in "lhn-cluster" (all with
>>> instance="clusClusterEntry") after you add the string one for
>>> clusClusterName.  And there should be ten mibObjs in lhn-volume, all
>>> with instance="clusVolumeEntry" once you've added the string one for
>>> clusVolumeName.
>>>
>>> The last thing will be to remediate the graph definitions.  As a
>>> starter, your lefthand.modulestatsIOsRead definition should get the
>>> following changes:
>>>
>>> report.lefthand.modulestatsIOsRead.columns=clusModStatsIOsRd
>>> report.lefthand.modulestatsIOsRead.type=clusModuleEntry
>>>
>>> And instead of four DEFs, four LINE2s, and twelve GPRINTs, you'll have
>>> one DEF:
>>>
>>> DEF:clusModStatsIOsRd={rrd1}:clusModuleStatsIOsRd:AVERAGE
>>>
>>> And you'll use that clusModStatsIOsRd token in the one LINE2 and three
>>> GPRINT statements.
>>>
>>> I hope this helps.  I know it's a lot to digest.
>>>
>>> -jeff
>
> I made all of the changes that you suggested and retried this.  Still
> no graphs.  I have attached the apropos sections of datacollect and
> snmp-graph files plus screenshots.
>
> Thanks!
>
> Dennis
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss