Thanks. I was able to add the table to an existing custom probe along with adding a threshold to monitor the AC power supply. I've got another question though. When I build the table Intermapper translates the numeric data into labels (presumably via the MIB). However when I probe the OID for the AC supply directly it just outputs a number. Is there a way I can get it to translate that value like it does with the table?
-- Thank You Jefferson Cowart Network and Systems Administrator Claremont University Consortium > -----Original Message----- > From: [email protected] [mailto:InterMapper- > [email protected]] On Behalf Of Richard E. Brown > Sent: Sunday, April 25, 2010 05:08 > To: [email protected] > Subject: RE: [IM-Talk] RPS Monitoring on Cisco 28xx ISRs > > Jefferson, > > --- You wrote: > > Thos directions got me back some valid data. It looks like that > > OID sub-tree returns a table showing all the power supplies. > > From other probes I have I see how to put that table into the probe > output. > > Excellent. I'm glad you got it see what you expect. > > > ... What I > > don't see is how to alert based on those table values. I believe I > > remember seeing that's not possible. Is that correct? > > You cannot apply a threshold to *every* row of a table. > > However, it's quite straightforward to use the OID of a single value > (taken from > the SNMPWalk window) in a <snmp-device-threshold> comparison. > > Please get back to me if you have further questions. Thanks. > > Rich Brown [email protected] > Dartware, LLC http://www.intermapper.com > 66-7 Benning Street Telephone: 603-643-9600 > West Lebanon, NH 03784-3407 Fax: 603-643-2289 > ____________________________________________________________________ > List archives: > http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ > To unsubscribe: send email to: [email protected] ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
