smilint output for ./RMON2-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| minor error | 1 |
| warning | 15 |
| fyi | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| group-unref (warning) | 2 |
| identifier-external-redefined (warning) | 2 |
| index-element-no-size (minor error) | 1 |
| index-exceeds-too-large (warning) | 8 |
| previous-definition (fyi) | 2 |
| type-without-format (warning) | 3 |
Messages:
/home/fenner/mibindex/latest2/RMON-MIB
1: -- extracted from rfc2819.txt
2: -- at Sat Jun 3 07:07:21 2000
20: LAST-UPDATED "200005110000Z" -- 11 May, 2000
21: ORGANIZATION "IETF RMON MIB Working Group"
22: CONTACT-INFO
23: "Steve Waldbusser
24: Phone: +1-650-948-6500
25: Fax: +1-650-745-0671
26: Email: waldbusser@nextbeacon.com"
27: DESCRIPTION
28: "Remote network monitoring devices, often called
29: monitors or probes, are instruments that exist for
30: the purpose of managing a network. This MIB defines
31: objects for managing remote network monitoring devices."
32:
33: REVISION "200005110000Z" -- 11 May, 2000
34: DESCRIPTION
35: "Reformatted into SMIv2 format.
36:
37: This version published as RFC 2819."
38:
39: REVISION "199502010000Z" -- 1 Feb, 1995
40: DESCRIPTION
41: "Bug fixes, clarifications and minor changes based on
42: implementation experience, published as RFC1757 [18].
43:
44: Two changes were made to object definitions:
45:
46: 1) A new status bit has been defined for the
47: captureBufferPacketStatus object, indicating that the
48: packet order within the capture buffer may not be identical to
49: the packet order as received off the wire. This bit may only
50: be used for packets transmitted by the probe. Older NMS
51: applications can safely ignore this status bit, which might be
52: used by newer agents.
53:
54: 2) The packetMatch trap has been removed. This trap was never
55: actually 'approved' and was not added to this document along
56: with the risingAlarm and fallingAlarm traps. The packetMatch
57: trap could not be throttled, which could cause disruption of
58: normal network traffic under some circumstances. An NMS should
59: configure a risingAlarm threshold on the appropriate
60: channelMatches instance if a trap is desired for a packetMatch
61: event. Note that logging of packetMatch events is still
62: supported--only trap generation for such events has been
63: removed.
64:
65: In addition, several clarifications to individual object
66: definitions have been added to assist agent and NMS
67: implementors:
68:
69: - global definition of 'good packets' and 'bad packets'
70:
71: - more detailed text governing conceptual row creation and
72: modification
73:
74: - instructions for probes relating to interface changes and
75: disruptions
76:
77: - clarification of some ethernet counter definitions
78:
79: - recommended formula for calculating network utilization
80:
81: - clarification of channel and captureBuffer behavior for some
82: unusual conditions
83:
84: - examples of proper instance naming for each table"
85:
86: REVISION "199111010000Z" -- 1 Nov, 1991
87: DESCRIPTION
88: "The original version of this MIB, published as RFC1271."
89: ::= { rmonConformance 8 }
90:
91: rmon OBJECT IDENTIFIER ::= { mib-2 16 }
91: fyi -
info: previous definition of `rmon'
92:
93:
94: -- textual conventions
95:
96: OwnerString ::= TEXTUAL-CONVENTION
97: STATUS current
98: DESCRIPTION
99: "This data type is used to model an administratively
100: assigned name of the owner of a resource. Implementations
101: must accept values composed of well-formed NVT ASCII
102: sequences. In addition, implementations should accept
103: values composed of well-formed UTF-8 sequences.
104:
105: It is suggested that this name contain one or more of
106: the following: IP address, management station name,
107: network manager's name, location, or phone number.
108: In some cases the agent itself will be the owner of
109: an entry. In these cases, this string shall be set
110: to a string starting with 'monitor'.
111:
112: SNMP access control is articulated entirely in terms
113: of the contents of MIB views; access to a particular
114: SNMP object instance depends only upon its presence
115: or absence in a particular MIB view and never upon
116: its value or the value of related object instances.
117: Thus, objects of this type afford resolution of
118: resource contention only among cooperating
119: managers; they realize no access control function
120: with respect to uncooperative parties."
121: SYNTAX OCTET STRING (SIZE (0..127))
122:
123: EntryStatus ::= TEXTUAL-CONVENTION
124: STATUS current
125: DESCRIPTION
126: "The status of a table entry.
127:
128: Setting this object to the value invalid(4) has the
129: effect of invalidating the corresponding entry.
130: That is, it effectively disassociates the mapping
131: identified with said entry.
132: It is an implementation-specific matter as to whether
133: the agent removes an invalidated entry from the table.
134: Accordingly, management stations must be prepared to
135: receive tabular information from agents that corresponds
136: to entries currently not in use. Proper
137: interpretation of such entries requires examination
138: of the relevant EntryStatus object.
139:
140: An existing instance of this object cannot be set to
141: createRequest(2). This object may only be set to
142: createRequest(2) when this instance is created. When
143: this object is created, the agent may wish to create
144: supplemental object instances with default values
145: to complete a conceptual row in this table. Because the
146: creation of these default objects is entirely at the option
147: of the agent, the manager must not assume that any will be
148: created, but may make use of any that are created.
...
203: }
204:
205: statistics OBJECT IDENTIFIER ::= { rmon 1 }
206: history OBJECT IDENTIFIER ::= { rmon 2 }
207: alarm OBJECT IDENTIFIER ::= { rmon 3 }
208: hosts OBJECT IDENTIFIER ::= { rmon 4 }
209: hostTopN OBJECT IDENTIFIER ::= { rmon 5 }
210: matrix OBJECT IDENTIFIER ::= { rmon 6 }
211: filter OBJECT IDENTIFIER ::= { rmon 7 }
212: capture OBJECT IDENTIFIER ::= { rmon 8 }
213: event OBJECT IDENTIFIER ::= { rmon 9 }
214: rmonConformance OBJECT IDENTIFIER ::= { rmon 20 }
214: fyi -
info: previous definition of `rmonConformance'
215:
216: -- The Ethernet Statistics Group
217: --
218: -- Implementation of the Ethernet Statistics group is optional.
219: -- Consult the MODULE-COMPLIANCE macro for the authoritative
220: -- conformance information for this MIB.
221: --
222: -- The ethernet statistics group contains statistics measured by the
223: -- probe for each monitored interface on this device. These
224: -- statistics take the form of free running counters that start from
225: -- zero when a valid entry is created.
226: --
227: -- This group currently has statistics defined only for
228: -- Ethernet interfaces. Each etherStatsEntry contains statistics
229: -- for one Ethernet interface. The probe must create one
230: -- etherStats entry for each monitored Ethernet interface
231: -- on the device.
232:
233: etherStatsTable OBJECT-TYPE
234: SYNTAX SEQUENCE OF EtherStatsEntry
235: MAX-ACCESS not-accessible
236: STATUS current
237: DESCRIPTION
238: "A list of Ethernet statistics entries."
239: ::= { statistics 1 }
240:
241: etherStatsEntry OBJECT-TYPE
242: SYNTAX EtherStatsEntry
243: MAX-ACCESS not-accessible
244: STATUS current
245: DESCRIPTION
246: "A collection of statistics kept for a particular
247: Ethernet interface. As an example, an instance of the
248: etherStatsPkts object might be named etherStatsPkts.1"
249: INDEX { etherStatsIndex }
250: ::= { etherStatsTable 1 }
251:
252: EtherStatsEntry ::= SEQUENCE {
253: etherStatsIndex Integer32,
254: etherStatsDataSource OBJECT IDENTIFIER,
255: etherStatsDropEvents Counter32,
256: etherStatsOctets Counter32,
257: etherStatsPkts Counter32,
258: etherStatsBroadcastPkts Counter32,
259: etherStatsMulticastPkts Counter32,
260: etherStatsCRCAlignErrors Counter32,
261: etherStatsUndersizePkts Counter32,
262: etherStatsOversizePkts Counter32,
263: etherStatsFragments Counter32,
264: etherStatsJabbers Counter32,
265: etherStatsCollisions Counter32,
266: etherStatsPkts64Octets Counter32,
267: etherStatsPkts65to127Octets Counter32,
268: etherStatsPkts128to255Octets Counter32,
269: etherStatsPkts256to511Octets Counter32,
270: etherStatsPkts512to1023Octets Counter32,
271: etherStatsPkts1024to1518Octets Counter32,
272: etherStatsOwner OwnerString,
273: etherStatsStatus EntryStatus
274: }
275:
276: etherStatsIndex OBJECT-TYPE
277: SYNTAX Integer32 (1..65535)
278: MAX-ACCESS read-only
279: STATUS current
280: DESCRIPTION
281: "The value of this object uniquely identifies this
282: etherStats entry."
283: ::= { etherStatsEntry 1 }
284:
285: etherStatsDataSource OBJECT-TYPE
286: SYNTAX OBJECT IDENTIFIER
287: MAX-ACCESS read-create
288: STATUS current
289: DESCRIPTION
290: "This object identifies the source of the data that
291: this etherStats entry is configured to analyze. This
292: source can be any ethernet interface on this device.
293: In order to identify a particular interface, this object
294: shall identify the instance of the ifIndex object,
295: defined in RFC 2233 [17], for the desired interface.
296: For example, if an entry were to receive data from
297: interface #1, this object would be set to ifIndex.1.
298:
299: The statistics in this group reflect all packets
300: on the local network segment attached to the identified
301: interface.
302:
303: An agent may or may not be able to tell if fundamental
304: changes to the media of the interface have occurred and
305: necessitate an invalidation of this entry. For example, a
306: hot-pluggable ethernet card could be pulled out and replaced
307: by a token-ring card. In such a case, if the agent has such
308: knowledge of the change, it is recommended that it
309: invalidate this entry.
310:
311: This object may not be modified if the associated
312: etherStatsStatus object is equal to valid(1)."
313: ::= { etherStatsEntry 2 }
314:
315: etherStatsDropEvents OBJECT-TYPE
316: SYNTAX Counter32
317: MAX-ACCESS read-only
318: STATUS current
319: DESCRIPTION
320: "The total number of events in which packets
321: were dropped by the probe due to lack of resources.
322: Note that this number is not necessarily the number of
323: packets dropped; it is just the number of times this
324: condition has been detected."
325: ::= { etherStatsEntry 3 }
326:
327: etherStatsOctets OBJECT-TYPE
328: SYNTAX Counter32
329: UNITS "Octets"
330: MAX-ACCESS read-only
331: STATUS current
332: DESCRIPTION
333: "The total number of octets of data (including
334: those in bad packets) received on the
335: network (excluding framing bits but including
336: FCS octets).
337: This object can be used as a reasonable estimate of
338: 10-Megabit ethernet utilization. If greater precision is
339: desired, the etherStatsPkts and etherStatsOctets objects
340: should be sampled before and after a common interval. The
341: differences in the sampled values are Pkts and Octets,
342: respectively, and the number of seconds in the interval is
343: Interval. These values are used to calculate the Utilization
344: as follows:
345:
346: Pkts * (9.6 + 6.4) + (Octets * .8)
347: Utilization = -------------------------------------
348: Interval * 10,000
349:
350: The result of this equation is the value Utilization which
351: is the percent utilization of the ethernet segment on a
352: scale of 0 to 100 percent."
353: ::= { etherStatsEntry 4 }
354:
355: etherStatsPkts OBJECT-TYPE
356: SYNTAX Counter32
357: UNITS "Packets"
358: MAX-ACCESS read-only
359: STATUS current
360: DESCRIPTION
361: "The total number of packets (including bad packets,
362: broadcast packets, and multicast packets) received."
363: ::= { etherStatsEntry 5 }
364:
365: etherStatsBroadcastPkts OBJECT-TYPE
366: SYNTAX Counter32
367: UNITS "Packets"
368: MAX-ACCESS read-only
369: STATUS current
370: DESCRIPTION
371: "The total number of good packets received that were
372: directed to the broadcast address. Note that this
373: does not include multicast packets."
374: ::= { etherStatsEntry 6 }
375:
376: etherStatsMulticastPkts OBJECT-TYPE
377: SYNTAX Counter32
378: UNITS "Packets"
379: MAX-ACCESS read-only
380: STATUS current
381: DESCRIPTION
382: "The total number of good packets received that were
383: directed to a multicast address. Note that this number
384: does not include packets directed to the broadcast
385: address."
386: ::= { etherStatsEntry 7 }
387:
388: etherStatsCRCAlignErrors OBJECT-TYPE
389: SYNTAX Counter32
390: UNITS "Packets"
391: MAX-ACCESS read-only
392: STATUS current
393: DESCRIPTION
394: "The total number of packets received that
395: had a length (excluding framing bits, but
396: including FCS octets) of between 64 and 1518
397: octets, inclusive, but had either a bad
398: Frame Check Sequence (FCS) with an integral
399: number of octets (FCS Error) or a bad FCS with
400: a non-integral number of octets (Alignment Error)."
401: ::= { etherStatsEntry 8 }
402:
403: etherStatsUndersizePkts OBJECT-TYPE
404: SYNTAX Counter32
405: UNITS "Packets"
RMON2-MIB
1: -- extracted from rfc4502.txt
2: -- at Sat May 20 06:06:27 2006
20:
21: rmon MODULE-IDENTITY
21: warning -
warning: redefinition of identifier `RMON-MIB::rmon'
22: LAST-UPDATED "200605020000Z" -- May 2, 2006
23: ORGANIZATION "IETF RMON MIB Working Group"
24: CONTACT-INFO
25: "Author:
26: Steve Waldbusser
27: Phone: +1-650-948-6500
28: Fax : +1-650-745-0671
29: Email: waldbusser@nextbeacon.com
30:
31: Working Group Chair:
32: Andy Bierman
33: E-mail: ietf@andybierman.com
34:
35: Working Group Mailing List: <rmonmib@ietf.org>
36: To subscribe send email to: <rmonmib-request@ietf.org> "
37: DESCRIPTION
38: "The MIB module for managing remote monitoring
39: device implementations. This MIB module
40: extends the architecture introduced in the original
41: RMON MIB as specified in RFC 2819.
42:
43: Copyright (C) The Internet Society (2006). This version of
44: this MIB module is part of RFC 4502; see the RFC itself for
45: full legal notices."
46:
47: REVISION "200605020000Z" -- May 2, 2006
48: DESCRIPTION
49: "This version updates the proposed-standard version of the
50: RMON2 MIB (published as RFC 2021) by adding 2 new
51: enumerations to the nlMatrixTopNControlRateBase object and
52: 4 new enumerations to the alMatrixTopNControlRateBase object.
53: These new enumerations support the creation of high-capacity
54: topN reports in the High Capacity RMON MIB [RFC3273].
55:
56: Additionally, the following objects have been deprecated, as
57: they have not had enough independent implementations to
58: demonstrate interoperability to meet the requirements of a
59: Draft Standard:
60:
61: probeDownloadFile
62: probeDownloadTFTPServer
63: probeDownloadAction
64: probeDownloadStatus
65: serialMode
66: serialProtocol
67: serialTimeout
68: serialModemInitString
69: serialModemHangUpString
70: serialModemConnectResp
71: serialModemNoConnectResp
72: serialDialoutTimeout
73: serialStatus
74: serialConnectDestIpAddress
75: serialConnectType
76: serialConnectDialString
77: serialConnectSwitchConnectSeq
78: serialConnectSwitchDisconnectSeq
79: serialConnectSwitchResetSeq
80: serialConnectOwner
81: serialConnectStatus
82: netConfigIPAddress
83: netConfigSubnetMask
84: netConfigStatus
85: netDefaultGateway
86: tokenRingMLStats2DroppedFrames
87: tokenRingMLStats2CreateTime
88: tokenRingPStats2DroppedFrames
89: tokenRingPStats2CreateTime
90: ringStationControl2DroppedFrames
91: ringStationControl2CreateTime
92: sourceRoutingStats2DroppedFrames
93: sourceRoutingStats2CreateTime
94: trapDestIndex
95: trapDestCommunity
96: trapDestProtocol
97: trapDestAddress
98: trapDestOwner
99: trapDestStatus
100:
101: In addition, two corrections were made. The LastCreateTime
102: Textual Convention had been defined with a base type of
103: another textual convention, which isn't allowed in SMIv2. The
104: definition has been modified to use TimeTicks as the base
105: type.
106:
107: Further, the SerialConfigEntry SEQUENCE definition included
108: sub-typing information that is not allowed in SMIv2. This
109: information has been deleted. Ranges were added to a number of
110: objects and textual-conventions to constrain their maximum
111: (and sometimes minimum) sizes. The addition of these ranges
112: documents existing practice for these objects. These objects
113: are:
114: ControlString
115: protocolDirID
116: protocolDirParameters
117: addressMapNetworkAddress
118: nlHostAddress
119: nlMatrixSDSourceAddress
120: nlMatrixSDDestAddress
121: nlMatrixDSSourceAddress
122: nlMatrixDSDestAddress
123: nlMatrixTopNSourceAddress
124: nlMatrixTopNDestAddress
125: alHostEntry
126: alMatrixSDEntry
127: alMatrixDSEntry
128: alMatrixTopNSourceAddress
129: alMatrixTopNDestAddress
130:
131: Finally, the TimeFilter TC has been updated to encourage agent
132: implementations that allow a MIB walk to behave well even when
133: performed by an application that is not aware of the special
134: TimeFilter semantics."
135:
136: REVISION "200207080000Z" -- 08 July, 2002
137: DESCRIPTION
138: "Added new enumerations to support the High-Capacity RMON
139: MIB as defined in RFC 3273. Also fixed some typos and
140: added clarifications."
141:
142: REVISION "199605270000Z" -- 27 May, 1996
143: DESCRIPTION
144: "Original version. Published as RFC 2021."
145: ::= { mib-2 16 }
146:
147: -- { rmon 1 } through { rmon 10 } are defined in RMON and
148: -- the Token Ring RMON MIB [RFC1513]
...
158: probeConfig OBJECT IDENTIFIER ::= { rmon 19 }
159: rmonConformance OBJECT IDENTIFIER ::= { rmon 20 }
159: warning -
warning: redefinition of identifier `RMON-MIB::rmonConformance'
160:
161: -- Textual Conventions
162:
163: ZeroBasedCounter32 ::= TEXTUAL-CONVENTION
163: warning -
warning: type `ZeroBasedCounter32' has no format specification
164: STATUS current
165: DESCRIPTION
166: "This TC describes an object that counts events with the
167: following semantics: objects of this type will be set to
168: zero(0) on creation and will thereafter count appropriate
169: events, wrapping back to zero(0) when the value 2^32 is
170: reached.
171:
172: Provided that an application discovers the new object within
173: the minimum time to wrap, it can use the initial value as a
174: delta since it last polled the table of which this object is
175: part. It is important for a management station to be aware of
176: this minimum time and the actual time between polls, and to
177: discard data if the actual time is too long or there is no
178: defined minimum time.
179:
180: Typically, this TC is used in tables where the INDEX space is
181: constantly changing and/or the TimeFilter mechanism is in use."
182: SYNTAX Gauge32
183:
184: LastCreateTime ::= TEXTUAL-CONVENTION
184: warning -
warning: type `LastCreateTime' has no format specification
185: STATUS current
186: DESCRIPTION
187: "This TC describes an object that stores the value of the
188: sysUpTime object at the last time its entry was created.
189:
190: This can be used for polling applications to determine that an
191: entry has been deleted and re-created between polls, causing
192: an otherwise undetectable discontinuity in the data.
193:
194: If sysUpTime is reset to zero as a result of a re-
195: initialization of the network management (sub)system, then
196: the values of all LastCreateTime objects are also reset.
197: However, after approximately 497 days without a re-
198: initialization, the sysUpTime object will reach 2^^32-1 and
199: then increment to zero; in this case, existing values
200: of TimeStamp objects do not change. This can lead to
201: ambiguities in the value of TimeStamp objects."
202: SYNTAX TimeTicks
203:
204: TimeFilter ::= TEXTUAL-CONVENTION
204: warning -
warning: type `TimeFilter' has no format specification
205: STATUS current
206: DESCRIPTION
207: "To be used for the index to a table. Allows an application
208: to download only those rows changed since a particular time.
209: Note that this is not a history mechanism. Only current values
210: of underlying objects are returned; saved instance values
211: associated with particular values of sysUpTime are not.
212:
213: An entry is considered changed if the value of any object in the
214: entry changes, if the row is created, or if any object in the
215: entry is created or deleted. Note that deleted entries cannot
216: be detected or downloaded.
217:
218: A time-filtered conceptual table is created by inserting a
219: single object of SYNTAX TimeFilter as the first INDEX component
220: in a copy of an existing basic conceptual table (i.e., any
221: SEQUENCE without a TimeFilter INDEX component). Thus, for
222: each conceptual entry 'I' in the basic table, there exists N
223: conceptual entries in the time-filtered version, indexed N.I,
224: where 'N' is equal to the value of sysUpTime.
225:
226: When an application retrieves conceptual instances from a
227: time-filtered table, and an INDEX value is provided for the
228: TimeFilter INDEX component 'N', the agent will only consider
229: returning basic conceptual entries (e.g., 'fooColumn.N.I') if
230: any column within the basic conceptual entry has changed since
231: sysUpTime 'N'. If not, the basic conceptual entry will
232: be ignored for the particular retrieval operation.
233:
234: When sysUpTime is equal to zero, this table shall be empty.
235:
236: One conceptual entry exists for each past value of sysUpTime,
237: except that the whole table is purged should sysUpTime wrap.
238:
239: As an entry in a time-filtered table is updated (i.e., one of
240: the columns in the basic conceptual table is changed), new
241: conceptual entries are also created in the time-filtered version
242: (which still shares the now updated object values with all other
243: instances). The number of unique time-filtered instances that
244: are created is determined by the value of sysUpTime at which the
245: basic entry was last updated. One unique instance will exist
246: for each value of sysUpTime at the last update time for the row.
247: However, a new TimeFilter index instance is created for each new
248: sysUpTime value. The TimeFilter index values not associated
249: with entry updates are called duplicate time-filtered instances.
250:
251: After some deployment experience, it has been determined that
252: a time-filtered table is more efficient if the agent
253: stops a MIB walk operation by skipping over rows with a
254: TimeFilter index value higher than the value in the received
255: GetNext/GetBulk request. That is, instead of incrementing a
256: TimeFilter index value, the agent will continue to the next
257: object or table. As a consequence, GetNext or GetBulk
258: operations will provide only one pass through a time-filtered
259: table.
260:
261: It is suggested that an agent implement a time-filtered table
262: in this manner to improve performance and avoid a MIB walk
263: getting stuck in time-filtered tables. It is, however, still
264: acceptable for an agent to implement a time-filtered table in
265: the traditional manner (i.e., every conceptual time-filtered
266: instance is returned in GetNext and GetBulk PDU responses), and
267: management applications must be able to deal with such
268: traditional implementations.
269:
270: See the appendix for further discussion of this textual
271: convention.
272:
273: The following example is provided to demonstrate TimeFilter
274: behavior:
275:
276: Consider the following basic conceptual table, basicFooTable.
277: (Note that the basic version of a time-filtered table may not
278: actually be defined.)
279:
280: basicFooTable:
281:
282: basicFooTable ...
283: INDEX { fooIndex }
284:
285: BasicFooEntry {
286: fooIndex Integer32,
287: fooCounts Counter32
288: }
289:
290: For this example, the basicFooTable contains two static
291: conceptual entries (fooIndex equals '1' and '2'), created at
292: time zero. It also contains one dynamic conceptual entry
293: (fooIndex equals '3'), which is created at time '3' and deleted
294: at time '7'.
295:
296: The time-filtered version of the basicFooTable could be defined
297: as follows:
298:
299: FooTable:
300:
301: fooTable ...
302: INDEX { fooTimeMark, fooIndex }
303:
304: FooEntry {
305: fooTimeMark TimeFilter,
306: fooIndex Integer32,
307: fooCounts Counter32
308: }
309:
310:
311: Note that entries exist in the time-filtered conceptual table
312: only if they actually exist in the underlying (basic) table.
313:
314: For this example, the fooTable will have three underlying
315: basic entries (fooIndex == 1, 2, and 3), with the following
316: activity (for sysUpTime equal 0 to 9):
317:
318: - fooEntry.N.1 is created at time '0' and most recently
319: updated at time '6' to the value '5'.
320: - fooEntry.N.2 is created at time '0' and most recently
321: updated at time '8' to the value '9'.
322: - fooEntry.N.3 is created at time '3', updated at time '5'
323: to the value '17', and deleted at time '7'.
324:
325: The following tables show the values that would be returned for
326: MIB walk operations with various TimeFilter values, done at
327: different times. An application issues a retrieval request at
328: time 'T', with a TimeFilter value, 'N' (typically set to a lower
329: value, such as the value of sysUpTime at the last polling cycle).
330:
331: The following values would be returned in a MIB walk of
332: fooCounts.N if T equals '0' and N equals '0':
333:
334: fooCounts.N.I Value
335: ==========================
336: fooCounts.0.1 0
337: fooCounts.0.2 0
338:
339: Note that nothing is returned for fooCounts.0.3, since that
340: entry does not exist at sysUpTime equals '0'.
341:
342: The following values would be returned in a full (traditional) MIB
343: walk of fooCounts.N if T equals '3' and N equals '0':
344:
345: fooCounts.N.I Value
346: =======================
347: fooCounts.0.1 0
348: fooCounts.0.2 0
349: fooCounts.0.3 0
350: fooCounts.1.3 0
351: fooCounts.2.3 0
352: fooCounts.3.3 0
353:
354: Note that there are no instances for T equals 1 or 2 for the
355: first two values of N, as these entries did not change
356: since they were created at time '0'.
357:
358: Note that the current value for 'fooCounts.N.3' is returned
359: here, even for values of N less than '3' (when the entry was
360: created). The agent only considers the current existence of an
361: entry in the TimeFilter algorithm, not the time when the entry
362: was created.
363:
364: Note that the instances 'fooCounts.0.3', 'fooCounts.1.3',
365: and 'fooCounts.2.3' are duplicates and can be suppressed by the
366: agent in a MIB walk.
367:
368: The following values would be returned in a full (traditional)
369: MIB walk of fooCounts.N if T equals '6' and N equals '3':
370:
371: fooCounts.N.I Value
372: =======================
373: fooCounts.3.1 5
374: fooCounts.3.3 17
375: fooCounts.4.1 5
376: fooCounts.4.3 17
377: fooCounts.5.1 5
378: fooCounts.5.3 17
379: fooCounts.6.1 5
380:
381: Note that no instances for entry 'fooCounts.N.2' are returned,
382: since it has not changed since time '3'.
383:
384: Note that all instances except 'fooCounts.5.3' and
385: 'fooCounts.6.1' are duplicates and can be suppressed by the
386: agent in a MIB walk.
387:
388: The following values would be returned in a full (traditional)
389: MIB walk of fooCounts.N if T equals '9' and N equals '6':
390:
391: fooCounts.N.I Value
392: =======================
393: fooCounts.6.1 5
394: fooCounts.6.2 9
395: fooCounts.7.2 9
396: fooCounts.8.2 9
397:
398: Note that no instances for entry 'fooCounts.N.3' are returned,
399: since it was deleted at time '7'.
400:
401: Note that instances 'fooCounts.6.2' and 'fooCounts.7.2'
402: are duplicates and can be suppressed by the agent in a MIB
403: walk."
404:
405: SYNTAX TimeTicks
...
457:
458: protocolDirEntry OBJECT-TYPE
458: warning -
warning: index of row `protocolDirEntry' can exceed OID size limit by 45 subidentifier(s)
459: SYNTAX ProtocolDirEntry
460: MAX-ACCESS not-accessible
461: STATUS current
462: DESCRIPTION
463: "A conceptual row in the protocolDirTable.
464:
465: An example of the indexing of this entry is
466: protocolDirLocalIndex.8.0.0.0.1.0.0.8.0.2.0.0, which is the
467: encoding of a length of 8, followed by 8 subids encoding the
468: protocolDirID of 1.2048, followed by a length of 2 and the
469: 2 subids encoding zero-valued parameters.
470:
471: Note that some combinations of index values may result in an
472: index that exceeds 128 sub-identifiers in length, which exceeds
473: the maximum for the SNMP protocol. Implementations should take
474: care to avoid such combinations."
475: INDEX { protocolDirID, protocolDirParameters }
476: ::= { protocolDirTable 1 }
477:
478: ProtocolDirEntry ::= SEQUENCE {
479: protocolDirID OCTET STRING,
480: protocolDirParameters OCTET STRING,
481: protocolDirLocalIndex Integer32,
482: protocolDirDescr DisplayString,
483: protocolDirType BITS,
484: protocolDirAddressMapConfig INTEGER,
485: protocolDirHostConfig INTEGER,
486: protocolDirMatrixConfig INTEGER,
487: protocolDirOwner OwnerString,
488: protocolDirStatus RowStatus
489: }
...
1159:
1160: addressMapEntry OBJECT-TYPE
1160: warning -
warning: index of row `addressMapEntry' can exceed OID size limit by 270 subidentifier(s)
1161: SYNTAX AddressMapEntry
1162: MAX-ACCESS not-accessible
1163: STATUS current
1164: DESCRIPTION
1165: "A conceptual row in the addressMapTable.
1166:
1167: The protocolDirLocalIndex in the index identifies the network
1168: layer protocol of the addressMapNetworkAddress.
1169: An example of the indexing of this entry is
1170: addressMapSource.783495.18.4.128.2.6.6.11.1.3.6.1.2.1.2.2.1.1.1.
1171:
1172: Note that some combinations of index values may result in an
1173: index that exceeds 128 sub-identifiers in length, which exceeds
1174: the maximum for the SNMP protocol. Implementations should take
1175: care to avoid such combinations."
1176: INDEX { addressMapTimeMark, protocolDirLocalIndex,
1177: addressMapNetworkAddress, addressMapSource }
1178: ::= { addressMapTable 1 }
1179:
1180: AddressMapEntry ::= SEQUENCE {
1181: addressMapTimeMark TimeFilter,
1182: addressMapNetworkAddress OCTET STRING,
1183: addressMapSource OBJECT IDENTIFIER,
1184: addressMapPhysicalAddress OCTET STRING,
1185: addressMapLastChange TimeStamp
1186: }
...
1214:
1215: addressMapSource OBJECT-TYPE
1215: minor error -
index element `addressMapSource' of row `addressMapEntry' should but cannot have a size restriction
1216: SYNTAX OBJECT IDENTIFIER
1217: MAX-ACCESS not-accessible
1218: STATUS current
1219: DESCRIPTION
1220: "The interface or port on which the associated network
1221: address was most recently seen.
1222:
1223: If this address mapping was discovered on an interface, this
1224: object shall identify the instance of the ifIndex
1225: object, defined in [RFC2863], for the desired interface.
1226: For example, if an entry were to receive data from
1227: interface #1, this object would be set to ifIndex.1.
1228:
1229: If this address mapping was discovered on a port, this
1230: object shall identify the instance of the rptrGroupPortIndex
1231: object, defined in [RFC2108], for the desired port.
1232: For example, if an entry were to receive data from
1233: group #1, port #1, this object would be set to
1234: rptrGroupPortIndex.1.1.
1235:
1236: Note that while the dataSource associated with this entry
1237: may only point to index objects, this object may at times
1238: point to repeater port objects. This situation occurs when
1239: the dataSource points to an interface that is a locally
1240: attached repeater and the agent has additional information
1241: about the source port of traffic seen on that repeater."
1242: ::= { addressMapEntry 3 }
...
1581:
1582: nlHostEntry OBJECT-TYPE
1582: warning -
warning: index of row `nlHostEntry' can exceed OID size limit by 142 subidentifier(s)
1583: SYNTAX NlHostEntry
1584: MAX-ACCESS not-accessible
1585: STATUS current
1586: DESCRIPTION
1587: "A conceptual row in the nlHostTable.
1588:
1589: The hlHostControlIndex value in the index identifies the
1590: hlHostControlEntry on whose behalf this entry was created.
1591: The protocolDirLocalIndex value in the index identifies the
1592: network layer protocol of the nlHostAddress.
1593:
1594: An example of the indexing of this entry is
1595: nlHostOutPkts.1.783495.18.4.128.2.6.6.
1596:
1597: Note that some combinations of index values may result in an
1598: index that exceeds 128 sub-identifiers in length, which exceeds
1599: the maximum for the SNMP protocol. Implementations should take
1600: care to avoid such combinations."
1601: INDEX { hlHostControlIndex, nlHostTimeMark,
1602: protocolDirLocalIndex, nlHostAddress }
1603: ::= { nlHostTable 1 }
1604:
1605: NlHostEntry ::= SEQUENCE {
1606: nlHostTimeMark TimeFilter,
1607: nlHostAddress OCTET STRING,
1608: nlHostInPkts ZeroBasedCounter32,
1609: nlHostOutPkts ZeroBasedCounter32,
1610: nlHostInOctets ZeroBasedCounter32,
1611: nlHostOutOctets ZeroBasedCounter32,
1612: nlHostOutMacNonUnicastPkts ZeroBasedCounter32,
1613: nlHostCreateTime LastCreateTime
1614: }
...
2055:
2056: nlMatrixSDEntry OBJECT-TYPE
2056: warning -
warning: index of row `nlMatrixSDEntry' can exceed OID size limit by 398 subidentifier(s)
2057: SYNTAX NlMatrixSDEntry
2058: MAX-ACCESS not-accessible
2059: STATUS current
2060: DESCRIPTION
2061: "A conceptual row in the nlMatrixSDTable.
2062:
2063: The hlMatrixControlIndex value in the index identifies the
2064: hlMatrixControlEntry on whose behalf this entry was created.
2065: The protocolDirLocalIndex value in the index identifies the
2066: network-layer protocol of the nlMatrixSDSourceAddress and
2067: nlMatrixSDDestAddress.
2068:
2069: An example of the indexing of this table is
2070: nlMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7.
2071:
2072: Note that some combinations of index values may result in an
2073: index that exceeds 128 sub-identifiers in length, which exceeds
2074: the maximum for the SNMP protocol. Implementations should take
2075: care to avoid such combinations."
2076: INDEX { hlMatrixControlIndex, nlMatrixSDTimeMark,
2077: protocolDirLocalIndex,
2078: nlMatrixSDSourceAddress, nlMatrixSDDestAddress }
2079: ::= { nlMatrixSDTable 1 }
2080:
2081: NlMatrixSDEntry ::= SEQUENCE {
2082: nlMatrixSDTimeMark TimeFilter,
2083: nlMatrixSDSourceAddress OCTET STRING,
2084: nlMatrixSDDestAddress OCTET STRING,
2085: nlMatrixSDPkts ZeroBasedCounter32,
2086: nlMatrixSDOctets ZeroBasedCounter32,
2087: nlMatrixSDCreateTime LastCreateTime
2088: }
...
2202:
2203: nlMatrixDSEntry OBJECT-TYPE
2203: warning -
warning: index of row `nlMatrixDSEntry' can exceed OID size limit by 398 subidentifier(s)
2204: SYNTAX NlMatrixDSEntry
2205: MAX-ACCESS not-accessible
2206: STATUS current
2207: DESCRIPTION
2208: "A conceptual row in the nlMatrixDSTable.
2209:
2210: The hlMatrixControlIndex value in the index identifies the
2211: hlMatrixControlEntry on whose behalf this entry was created.
2212: The protocolDirLocalIndex value in the index identifies the
2213: network-layer protocol of the nlMatrixDSSourceAddress and
2214: nlMatrixDSDestAddress.
2215:
2216: An example of the indexing of this table is
2217: nlMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6.
2218:
2219: Note that some combinations of index values may result in an
2220: index that exceeds 128 sub-identifiers in length, which exceeds
2221: the maximum for the SNMP protocol. Implementations should take
2222: care to avoid such combinations."
2223: INDEX { hlMatrixControlIndex, nlMatrixDSTimeMark,
2224: protocolDirLocalIndex,
2225: nlMatrixDSDestAddress, nlMatrixDSSourceAddress }
2226: ::= { nlMatrixDSTable 1 }
2227:
2228: NlMatrixDSEntry ::= SEQUENCE {
2229: nlMatrixDSTimeMark TimeFilter,
2230: nlMatrixDSSourceAddress OCTET STRING,
2231: nlMatrixDSDestAddress OCTET STRING,
2232: nlMatrixDSPkts ZeroBasedCounter32,
2233: nlMatrixDSOctets ZeroBasedCounter32,
2234: nlMatrixDSCreateTime LastCreateTime
2235: }
...
2761:
2762: alHostEntry OBJECT-TYPE
2762: warning -
warning: index of row `alHostEntry' can exceed OID size limit by 143 subidentifier(s)
2763: SYNTAX AlHostEntry
2764: MAX-ACCESS not-accessible
2765: STATUS current
2766: DESCRIPTION
2767: "A conceptual row in the alHostTable.
2768:
2769: The hlHostControlIndex value in the index identifies the
2770: hlHostControlEntry on whose behalf this entry was created.
2771: The first protocolDirLocalIndex value in the index identifies
2772: the network-layer protocol of the address.
2773: The nlHostAddress value in the index identifies the network-
2774: layer address of this entry.
2775: The second protocolDirLocalIndex value in the index identifies
2776: the protocol that is counted by this entry.
2777:
2778: An example of the indexing in this entry is
2779: alHostOutPkts.1.783495.18.4.128.2.6.6.34.
2780:
2781: Note that some combinations of index values may result in an
2782: index that exceeds 128 sub-identifiers in length, which exceeds
2783: the maximum for the SNMP protocol. Implementations should take
2784: care to avoid such combinations."
2785: INDEX { hlHostControlIndex, alHostTimeMark,
2786: protocolDirLocalIndex, nlHostAddress,
2787: protocolDirLocalIndex }
2788: ::= { alHostTable 1 }
2789:
2790: AlHostEntry ::= SEQUENCE {
2791: alHostTimeMark TimeFilter,
2792: alHostInPkts ZeroBasedCounter32,
2793: alHostOutPkts ZeroBasedCounter32,
2794: alHostInOctets ZeroBasedCounter32,
2795: alHostOutOctets ZeroBasedCounter32,
2796: alHostCreateTime LastCreateTime
2797: }
...
2910:
2911: alMatrixSDEntry OBJECT-TYPE
2911: warning -
warning: index of row `alMatrixSDEntry' can exceed OID size limit by 399 subidentifier(s)
2912: SYNTAX AlMatrixSDEntry
2913: MAX-ACCESS not-accessible
2914: STATUS current
2915: DESCRIPTION
2916: "A conceptual row in the alMatrixSDTable.
2917:
2918: The hlMatrixControlIndex value in the index identifies the
2919: hlMatrixControlEntry on whose behalf this entry was created.
2920: The first protocolDirLocalIndex value in the index identifies
2921: the network-layer protocol of the nlMatrixSDSourceAddress and
2922: nlMatrixSDDestAddress.
2923: The nlMatrixSDSourceAddress value in the index identifies the
2924: network-layer address of the source host in this conversation.
2925: The nlMatrixSDDestAddress value in the index identifies the
2926: network-layer address of the destination host in this
2927: conversation.
2928: The second protocolDirLocalIndex value in the index identifies
2929: the protocol that is counted by this entry.
2930:
2931: An example of the indexing of this entry is
2932: alMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7.34.
2933:
2934: Note that some combinations of index values may result in an
2935: index that exceeds 128 sub-identifiers in length, which exceeds
2936: the maximum for the SNMP protocol. Implementations should take
2937: care to avoid such combinations."
2938: INDEX { hlMatrixControlIndex, alMatrixSDTimeMark,
2939: protocolDirLocalIndex,
2940: nlMatrixSDSourceAddress, nlMatrixSDDestAddress,
2941: protocolDirLocalIndex }
2942: ::= { alMatrixSDTable 1 }
2943:
2944: AlMatrixSDEntry ::= SEQUENCE {
2945: alMatrixSDTimeMark TimeFilter,
2946: alMatrixSDPkts ZeroBasedCounter32,
2947: alMatrixSDOctets ZeroBasedCounter32,
2948: alMatrixSDCreateTime LastCreateTime
2949: }
...
3027:
3028: alMatrixDSEntry OBJECT-TYPE
3028: warning -
warning: index of row `alMatrixDSEntry' can exceed OID size limit by 399 subidentifier(s)
3029: SYNTAX AlMatrixDSEntry
3030: MAX-ACCESS not-accessible
3031: STATUS current
3032: DESCRIPTION
3033: "A conceptual row in the alMatrixDSTable.
3034:
3035: The hlMatrixControlIndex value in the index identifies the
3036: hlMatrixControlEntry on whose behalf this entry was created.
3037: The first protocolDirLocalIndex value in the index identifies
3038: the network-layer protocol of the alMatrixDSSourceAddress and
3039: alMatrixDSDestAddress.
3040: The nlMatrixDSDestAddress value in the index identifies the
3041: network-layer address of the destination host in this
3042: conversation.
3043: The nlMatrixDSSourceAddress value in the index identifies the
3044: network-layer address of the source host in this conversation.
3045: The second protocolDirLocalIndex value in the index identifies
3046: the protocol that is counted by this entry.
3047:
3048: An example of the indexing of this entry is
3049: alMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6.34.
3050:
3051: Note that some combinations of index values may result in an
3052: index that exceeds 128 sub-identifiers in length, which exceeds
3053: the maximum for the SNMP protocol. Implementations should take
3054: care to avoid such combinations."
3055: INDEX { hlMatrixControlIndex, alMatrixDSTimeMark,
3056: protocolDirLocalIndex,
3057: nlMatrixDSDestAddress, nlMatrixDSSourceAddress,
3058: protocolDirLocalIndex }
3059: ::= { alMatrixDSTable 1 }
3060:
3061: AlMatrixDSEntry ::= SEQUENCE {
3062: alMatrixDSTimeMark TimeFilter,
3063: alMatrixDSPkts ZeroBasedCounter32,
3064: alMatrixDSOctets ZeroBasedCounter32,
3065: alMatrixDSCreateTime LastCreateTime
3066: }
...
5613:
5614: probeConfigurationGroup OBJECT-GROUP
5614: warning -
warning: deprecated group `probeConfigurationGroup' is not referenced in this module
5615: OBJECTS { probeResetControl, probeDownloadFile,
5616: probeDownloadTFTPServer, probeDownloadAction,
5617: probeDownloadStatus,
5618: serialMode, serialProtocol, serialTimeout,
5619: serialModemInitString, serialModemHangUpString,
5620: serialModemConnectResp, serialModemNoConnectResp,
5621: serialDialoutTimeout, serialStatus,
5622: netConfigIPAddress, netConfigSubnetMask,
5623: netConfigStatus, netDefaultGateway,
5624: trapDestCommunity, trapDestProtocol, trapDestAddress,
5625: trapDestOwner, trapDestStatus,
5626: serialConnectDestIpAddress, serialConnectType,
5627: serialConnectDialString, serialConnectSwitchConnectSeq,
5628: serialConnectSwitchDisconnectSeq,
5629: serialConnectSwitchResetSeq,
5630: serialConnectOwner, serialConnectStatus }
5631: STATUS deprecated
5632: DESCRIPTION
5633: "This group controls the configuration of various operating
5634: parameters of the probe. This group is not referenced by any
5635: MODULE-COMPLIANCE macro because it is 'grandfathered' from
5636: more recent MIB review rules that would require it."
5637: ::= { rmon2MIBGroups 10 }
...
5658:
5659: rmon1TokenRingEnhancementGroup OBJECT-GROUP
5659: warning -
warning: deprecated group `rmon1TokenRingEnhancementGroup' is not referenced in this module
5660: OBJECTS { tokenRingMLStatsDroppedFrames,
5661: tokenRingMLStatsCreateTime,
5662: tokenRingPStatsDroppedFrames, tokenRingPStatsCreateTime,
5663: ringStationControlDroppedFrames,
5664: ringStationControlCreateTime,
5665: sourceRoutingStatsDroppedFrames,
5666: sourceRoutingStatsCreateTime }
5667: STATUS deprecated
5668: DESCRIPTION
5669: "This group adds some enhancements to RMON-1 that help
5670: management stations. This group is not referenced by any
5671: MODULE-COMPLIANCE macro because it is 'grandfathered' from
5672: more recent MIB review rules that would require it."
5673: ::= { rmon2MIBGroups 13 }
5674: END
5675:
5676: --
5677: -- Copyright (C) The Internet Society (2006).
5678: --
5679: -- This document is subject to the rights, licenses and restrictions
5680: -- contained in BCP 78, and except as set forth therein, the authors
5681: -- retain all their rights.
5682: --
5683: -- This document and the information contained herein are provided on an
5684: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
5685: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
5686: -- ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
5687: -- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
5688: -- INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
5689: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
5690: --
5691: -- Intellectual Property
5692: --
5693: -- The IETF takes no position regarding the validity or scope of any
5694: -- Intellectual Property Rights or other rights that might be claimed to
5695: -- pertain to the implementation or use of the technology described in
5696: -- this document or the extent to which any license under such rights
5697: -- might or might not be available; nor does it represent that it has
5698: -- made any independent effort to identify any such rights. Information
5699: -- on the procedures with respect to rights in RFC documents can be
5700: -- found in BCP 78 and BCP 79.
5701: --
5702: -- Copies of IPR disclosures made to the IETF Secretariat and any
5703: -- assurances of licenses to be made available, or the result of an
5704: -- attempt made to obtain a general license or permission for the use of
5705: -- such proprietary rights by implementers or users of this
5706: -- specification can be obtained from the IETF on-line IPR repository at
5707: -- http://www.ietf.org/ipr.
5708: --
5709: -- The IETF invites any interested party to bring to its attention any
5710: -- copyrights, patents or patent applications, or other proprietary
5711: -- rights that may cover technology that may be required to implement
5712: -- this standard. Please address the information to the IETF at
5713: -- ietf-ipr@ietf.org.
5714: --
5715: