RE: The elements of one table, their OID is discontinous.
"Mike Ayers" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <83E753BE7B6A324ABB336245BAF1DAAC073BB1AE@mailserver.metatv-ds.metatv.com> |
> From: [email protected] > [mailto:[email protected]] On > Behalf Of Jack Chen > Sent: Monday, October 08, 2007 8:09 PM > I get one MIB, the elements of one table, their OID is > discontinous, I can't to execute " walk " command. > Such a design has any special purpose? Many thanks. I'm not sure what you mean here. All MIB elements are discontinuous, because OIDs are discrete. I'm thinking you mean one of two things: 1) There is a "missing row". This is a routine situation, and you should not assume that row numbers will be strictly incrementing. 2) There is a "missing element". A row may not have all its elements, depending on the MIB definition. This is called a "sparse table", and is also valid SNMP> Neither case should prevent an snmpwalk from succeeding. HTH, Mike ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users