Re: [Devmon] Change Primary Alias midway through Table

[Schwimmer, E. E *H. <EE...@hs...>]

Acknowledged.  This should be an easy fix (a .pri tag that would switch
the primary oid to whatever oid you applied it against).  I've got the
devmon RRD collector code done (both for devmon and hobbit) and I'm
testing it against our devmon cluster here.  I hope to have a new
release out sometime this week.

-Eric

> -----Original Message-----
> From: dev...@li...
[mailto:devmon-support-
> bo...@li...] On Behalf Of Aiello, Steve (GE,
Corporate,
> consultant)
> Sent: Friday, November 03, 2006 2:06 PM
> To: dev...@li...
> Subject: Re: [Devmon] Change Primary Alias midway through Table
>=20
> --- Resending, not sure if it made it to the Mailing List ---
> Hello All,
>=20
> In the tread of my last question, I will go over a different example
of
> needing an improvement on how Primary Alias is dealt with. This
example
> seems to show the need for nested primary aliases.
>=20
> Senario:
>=20
> Still working on my cisco IOS 6509 template. I am trying to put
together
> a report, listing the envirormental sensors and their values. With
this
> SNMP device it is possible to set the thresholds within the device
> itself. Which is great, since I am not on the network team, and just
> wish to report on the health of the device. Ideally I would like to
feed
> off the thresholds configured on the device, instead of hardcoding my
> own thresholds in devmon. That way there is only one group of
thresholds
> set, and false-positive alerts are not sent.
>=20
> So here are the OIDS of the sensors:
> sensorStatus    : .1.3.6.1.4.1.9.9.91.1.1.1.1.5 : branch
> sensorValue     : .1.3.6.1.4.1.9.9.91.1.1.1.1.4 : branch
> sensorType      : .1.3.6.1.4.1.9.9.91.1.1.1.1.1 : branch
> sensorDesc      : .1.3.6.1.2.1.47.1.1.1.1.2     : branch
>=20
> And this is where the thresholds are stored:
> sensorThreshServerity	: .1.3.6.1.4.1.9.9.91.1.2.1.1.2	: branch
> sensorThreshConditional	: .1.3.6.1.4.1.9.9.91.1.2.1.1.3	: branch
> sensorThreshValue		: .1.3.6.1.4.1.9.9.91.1.2.1.1.4	: branch
> sensorThreshEval		: .1.3.6.1.4.1.9.9.91.1.2.1.1.5	: branch
>=20
> So, starting with sensorStatus (primary Alias) the leafs underneath
for
> example are; 28,29,30,31,1001,1002.... This primary alias will work
> great with the first grouping of OIDS. The second set, the threshold
> set, have one more level of depth to them. They would be: 28.1 28.2
29.1
> 29.2 30.1 31.2
>=20
> In the case of the cisco switch, .1 is Panic level & .2 is Warn level
> thresholds. Currently under devmon there isn't an easy way to display
> data with this kind of nested relation, is there ?
>=20
> So this brings up a second point, with devices that have this ability
to
> store thresholds, it would be great to use this in the thresholds
file.
> An example:
>=20
> sensorValue	: {sensorThreshServerity}	:
> {sensorThreshConditional} {sensorThreshValue}
>=20
> Which the transforms file would probably be needed to convert the
store
> threshold data into devmon ones, not a big problem.
>=20
> Another thought I had, was to use {sensorThreshEval}. This field is
True
> or False if a threshold has been reached. I could then use the
> exceptions file to filter out only True values. The only problem with
> this is that I have no way to link that threshold with the sensor
> decription one level up.
>=20
> .1.3.6.1.4.1.9.9.91.1.2.1.1.5.1001.2 =3D=3D true
> .1.3.6.1.2.1.47.1.1.1.1.2.1001 =3D=3D Sensor description
>=20
> So to end a long winded email, Any thoughts on this senario or the
> previous one ? Are there many SNMP devices like this, i.e. is the need
> great enough update devmon to deal with nested oid values ? Am I just
> crazy ? ;)  ~ Steve
>=20
> > -----Original Message-----
> > From: Aiello, Steve (GE, Corporate, consultant)
> > Sent: Tuesday, October 31, 2006 8:03 PM
> > To: 'dev...@li...'
> > Subject: Change Primary Alias midway through Table
> >
> >
> > All,
> >
> > I am trying to write a template for a Cisco WS-6509 IOS
> > switch. A single report to list the status/information on
> > each port is just massive. So I would like to split the
> > report up by card, basically I will have a card1, card2,
> > card3, etc, report with only that card's ports displayed.
> >
> > So I start with the following OIDS for the card3 report:
> >
> > portIndex: .1.3.6.1.4.1.9.5.1.4.1.1.2.3
> > portName: .1.3.6.1.4.1.9.5.1.4.1.1.4.3
> > portIfIndex: .1.3.6.1.4.1.9.5.1.4.1.1.11.3
> >
> > Now, I need to change the Primary alias to the value of
> > portIfIndex and pull data from another set of OIDs.
> >
> > ifBps: .1.3.6.1.2.1.2.2.1.5
> > ifInOctets: .1.3.6.1.2.1.2.2.1.10
> > ifOutOctets: .1.3.6.1.2.1.2.2.1.16
> > ifInErrors: .1.3.6.1.2.1.2.2.1.14
> > ifOutErrors: .1.3.6.1.2.1.2.2.1.20
> >
> > Now I know this presently possible, but was curious if there
> > was interest in this being added. I know I am. Thoughts ?
> >
> >  ~Steve
> >
>=20
>
------------------------------------------------------------------------
-
> Using Tomcat but need to do more? Need to support web services,
security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
>
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support