This sounds similar to my recollection of how Cisco represents SIP call states on a AS5300. First you have to find the timestamp for the beginning of the call and append that to your OID, then you can get detailed info.
-Ed -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, April 20, 2005 10:46 AM To: InterMapper Discussion Subject: Re: [IM-Talk] Iterating over a Table I recently went to write a probe for the Alteon ssl accelerator/load balancer but did't complete the probe because of this restriction. In this situation you first need to "walk" a branch to read the list of integer indexes (one for each row), and then you append these indexes to the OIDS for the specific rows to "get" the rows. In the Alteon case each index corresponds to a virtual load balancer instance that has been configured into the Alteon to service a specific application. Once you have the index for a particular virtual instance you can retrieve all kinds of good data specific to that virtual instance including name of the instance, packets in, packets out, etc. If you have gone to the effort to install ssl accelerators and load balancers, this is important data. At 9:25 AM -0400 4/20/05, Richard E. Brown wrote: >Folks: > >--- Steve Foster wrote: >One for the developers, custom probe writers..... > >Are there any plans to permit tables in custom probes? For example like >the storage status within the host resources probe. > >Has anyone got any reccomendations for how to implament a probe that >would extract useful information out of a table, where the the table is >ordered differently between hosts. >--- end of quote --- > >Yes, we're beginning to think seriously about tables in probes. We have >some general ideas about how to go about it, but it would help us >enormously to get a sense of what it would mean to have a custom SNMP >probe facility that "handles tables". > >Specifically, we are looking for examples of equipment that stores data >in tables, and how you'd like InterMapper to retrieve/compare/display >that information. If you've ever thought about making a probe that >processed tables, please tell us: > >- What equipment was involved? What tables and what fields of >those tables are >interesting? >- Should InterMapper process all the rows of the table identically? >- If not, how would InterMapper "know" which rows to process? >- Do you ever need to relate data from one table with data in >another table? >- Are there cases where you'd want to use data from one device >to retrieve a >value from another device? >- What computations/calculations/comparisons would you expect >the probe to >perform? >- Are there additional built-in functions that would help to >create the probe? >- How should the tabular data be formatted in the status window? >- What other facilities would you want to see? > >We would be pleased to hear your thoughts. It would be great if you >can specify >certain equipment/MIB/OIDs/etc. that you're familiar with. It would also be >useful to know about the "competition" - any other tools/programs that offer a >good way to do these things. Many thanks! > >Rich Brown [EMAIL PROTECTED] >Dartware, LLC http://www.dartware.com >10 Buck Road, PO Box 130 Telephone: 603-643-2268 >Hanover, NH 03755-0130 USA 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] ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
