This is a discussion on Re: 'Inter-Tables indexing' and perl within the SNMP Users forums, part of the Networking and Network Related category; [ First - *please* don't mail me privately, without copying any responses to the mailing list. I don't have the ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time or inclination to offer private, unpaid, SNMP consultancy. Keep discussions to the list, where others can both learn and offer advice. Thanks. ] On Sat, 2005-10-22 at 10:46 +0200, Turbo Fredriksson wrote: > Oki, so: > * For all columns, get all rowX OID's > * For all returned values (rowX OID's), get the values > + 1:st rowX+1 OID > * Repeat (rowX+1). That's right. This also works with "partial rows". At each step, you can choose which subset of columns to retrieve. (useful with a wide table, where you're only interested in some of them). > >> > Walking an SNMP table would *not* (normally) display the index > >> > values. > I was more thinking that it would extract the client-, jobname > and the job ID and show that in the output from a 'snmptable' > command run. It should (assuming those are the index objects). I did say "normally" above :-) $ man snmptable -Ci This option prepends the index of the entry to all printed lines. > But I still get something wrong in the stats table. From what I can > see, I'm doing the right thing, but still I get a question mark in all > the FIRST indexes - the 'baculaStatsIndex' column (exept for the very > first line - with index '1.1.1'); See the README.txt above... OK - If I get the chance, I'll have a look at that, and see if I can spot anything wrong. > If I read your explanation correct above, you're not supposed to > see the index (baculaStatsIndex etc) AT ALL!? Correct. > I do (see the ...snmpwalk.txt file). Check the agent code - what does it return when asked for an OID that happens to belong to an index object? It ought to completely ignore such object - just as if they don't exist at all. > Or am I missunderstanding you again? > When you talk about 'indexes', what exactly do you mean then? The MIB objects referenced in the INDEX clause of the table definition. These would normally be defined as "not-accessible", and the agent shouldn't return values for these OIDs. Dave ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/...net-snmp-users |
![]() |
| Thread Tools | |
| Display Modes | |
|
|