Debian Codegraph @

rfc1271.html

raw
1 <pre>Network Working Group S. Waldbusser
2 Request for Comments: 1271 Carnegie Mellon University
3 November 1991
4
5
6 <span class="h1">Remote Network Monitoring Management Information Base</span>
7
8 Status of this Memo
9
10 This memo is an extension to the SNMP MIB. This RFC specifies an IAB
11 standards track protocol for the Internet community, and requests
12 discussion and suggestions for improvements. Please refer to the
13 current edition of the "IAB Official Protocol Standards" for the
14 standardization state and status of this protocol. Distribution of
15 this memo is unlimited.
16
17 Table of Contents
18
19 <a href="#section-1">1</a>. Abstract .............................................. <a href="#page-2">2</a>
20 <a href="#section-2">2</a>. The Network Management Framework....................... <a href="#page-2">2</a>
21 <a href="#section-3">3</a>. Objects ............................................... <a href="#page-2">2</a>
22 <a href="#section-3.1">3.1</a> Format of Definitions ................................ <a href="#page-3">3</a>
23 <a href="#section-4">4</a>. Overview .............................................. <a href="#page-3">3</a>
24 <a href="#section-4.1">4.1</a> Remote Network Management Goals ...................... <a href="#page-3">3</a>
25 <a href="#section-4.2">4.2</a> Textual Conventions .................................. <a href="#page-5">5</a>
26 <a href="#section-4.3">4.3</a> Structure of MIB ..................................... <a href="#page-5">5</a>
27 <a href="#section-4.3.1">4.3.1</a> The Statistics Group ............................... <a href="#page-6">6</a>
28 <a href="#section-4.3.2">4.3.2</a> The History Group .................................. <a href="#page-6">6</a>
29 <a href="#section-4.3.3">4.3.3</a> The Alarm Group .................................... <a href="#page-6">6</a>
30 <a href="#section-4.3.4">4.3.4</a> The Host Group ..................................... <a href="#page-6">6</a>
31 <a href="#section-4.3.5">4.3.5</a> The HostTopN Group ................................. <a href="#page-6">6</a>
32 <a href="#section-4.3.6">4.3.6</a> The Matrix Group ................................... <a href="#page-7">7</a>
33 <a href="#section-4.3.7">4.3.7</a> The Filter Group ................................... <a href="#page-7">7</a>
34 <a href="#section-4.3.8">4.3.8</a> The Packet Capture Group ........................... <a href="#page-7">7</a>
35 <a href="#section-4.3.9">4.3.9</a> The Event Group .................................... <a href="#page-7">7</a>
36 <a href="#section-5">5</a>. Control of Remote Network Monitoring Devices .......... <a href="#page-7">7</a>
37 <a href="#section-5.1">5.1</a> Resource Sharing Among Multiple Management Stations .. <a href="#page-8">8</a>
38 <a href="#section-5.2">5.2</a> Row Addition Among Multiple Management Stations ...... <a href="#page-9">9</a>
39 <a href="#section-6">6</a>. Definitions ........................................... <a href="#page-10">10</a>
40 <a href="#section-7">7</a>. Acknowledgments ....................................... <a href="#page-80">80</a>
41 <a href="#section-8">8</a>. References ............................................ <a href="#page-80">80</a>
42 Security Considerations................................... <a href="#page-81">81</a>
43 Author's Address.......................................... <a href="#page-81">81</a>
44
45
46
47
48
49
50
51
52 <span class="grey">Remote Network Monitoring Working Group [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Abstract</span>
58
59 This memo defines a portion of the Management Information Base (MIB)
60 for use with network management protocols in TCP/IP-based internets.
61 In particular, it defines objects for managing remote network
62 monitoring devices.
63
64 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Network Management Framework</span>
65
66 The Internet-standard Network Management Framework consists of three
67 components. They are:
68
69 <a href="./rfc1155">RFC 1155</a> which defines the SMI, the mechanisms used for describing
70 and naming objects for the purpose of management. <a href="./rfc1212">RFC 1212</a>
71 defines a more concise description mechanism, which is wholly
72 consistent with the SMI.
73
74 <a href="./rfc1156">RFC 1156</a> which defines MIB-I, the core set of managed objects for
75 the Internet suite of protocols. <a href="./rfc1213">RFC 1213</a>, defines MIB-II, an
76 evolution of MIB-I based on implementation experience and new
77 operational requirements.
78
79 <a href="./rfc1157">RFC 1157</a> which defines the SNMP, the protocol used for network
80 access to managed objects.
81
82 The Framework permits new objects to be defined for the purpose of
83 experimentation and evaluation.
84
85 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Objects</span>
86
87 Managed objects are accessed via a virtual information store, termed
88 the Management Information Base or MIB. Objects in the MIB are
89 defined using the subset of Abstract Syntax Notation One (ASN.1) [<a href="#ref-7" title=" International Organization for Standardization">7</a>]
90 defined in the SMI. In particular, each object has a name, a syntax,
91 and an encoding. The name is an object identifier, an
92 administratively assigned name, which specifies an object type. The
93 object type together with an object instance serves to uniquely
94 identify a specific instantiation of the object. For human
95 convenience, we often use a textual string, termed the OBJECT
96 DESCRIPTOR, to also refer to the object type.
97
98 The syntax of an object type defines the abstract data structure
99 corresponding to that object type. The ASN.1 language is used for
100 this purpose. However, the SMI [<a href="#ref-3" title="&quot;Structure and Identification of Management Information for TCP/IP-based internets&quot;">3</a>] purposely restricts the ASN.1
101 constructs which may be used. These restrictions are explicitly made
102 for simplicity.
103
104 The encoding of an object type is simply how that object type
105
106
107
108 <span class="grey">Remote Network Monitoring Working Group [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
111
112
113 is represented using the object type's syntax. Implicitly
114 tied to the notion of an object type's syntax and encoding is
115 how the object type is represented when being transmitted on
116 the network.
117
118 The SMI specifies the use of the basic encoding rules of ASN.1 [<a href="#ref-8" title=" International Standard 8825">8</a>],
119 subject to the additional requirements imposed by the SNMP.
120
121 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Format of Definitions</span>
122
123 <a href="#section-6">Section 6</a> contains the specification of all object types
124 contained in this MIB module. The object types are defined
125 using the conventions defined in the SMI, as amended by the
126 extensions specified in [<a href="#ref-9" title="&quot;Concise MIB Definitions&quot;">9</a>,<a href="#ref-10" title="&quot;A Convention for Defining Traps for use with the SNMP&quot;">10</a>].
127
128 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Overview</span>
129
130 Remote network monitoring devices are instruments that exist for the
131 purpose of managing a network. Often these remote probes are
132 stand-alone devices and devote significant internal resources for the
133 sole purpose of managing a network. An organization may employ many
134 of these devices, one per network segment, to manage its internet. In
135 addition, these devices may be used for a network management service
136 provider to access a client network, often geographically remote.
137
138 While many of the objects in this document are suitable for the
139 management of any type of network, there are some which are specific
140 to managing Ethernet networks. The design of this MIB allows similar
141 objects to be defined for other network types. It is intended that
142 future versions of this document will define extensions for other
143 network types such as Token Ring and FDDI.
144
145 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Remote Network Management Goals</span>
146
147 o Offline Operation
148 There are sometimes conditions when a management
149 station will not be in constant contact with its
150 remote monitoring devices. This is sometimes by
151 design in an attempt to lower communications costs
152 (especially when communicating over a WAN or
153 dialup link), or by accident as network failures
154 affect the communications between the management
155 station and the probe.
156
157 For this reason, this MIB allows a probe to be
158 configured to perform diagnostics and to collect
159 statistics continuously, even when communication with
160 the management station may not be possible or
161
162
163
164 <span class="grey">Remote Network Monitoring Working Group [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
167
168
169 efficient. The probe may then attempt to notify
170 the management station when an exceptional condition
171 occurs. Thus, even in circumstances where
172 communication between management station and probe is
173 not continuous, fault, performance, and configuration
174 information may be continuously accumulated and
175 communicated to the management station conveniently
176 and efficiently.
177
178 o Preemptive Monitoring
179 Given the resources available on the monitor, it
180 is potentially helpful for it continuously to run
181 diagnostics and to log network performance. The
182 monitor is always available at the onset of any
183 failure. It can notify the management station of the
184 failure and can store historical statistical
185 information about the failure. This historical
186 information can be played back by the management
187 station in an attempt to perform further diagnosis
188 into the cause of the problem.
189
190 o Problem Detection and Reporting
191 The monitor can be configured to recognize
192 conditions, most notably error conditions, and
193 continuously to check for them. When one of these
194 conditions occurs, the event may be logged, and
195 management stations may be notified in a number of
196 ways.
197
198 o Value Added Data
199 Because a remote monitoring device represents a
200 network resource dedicated exclusively to network
201 management functions, and because it is located
202 directly on the monitored portion of the network, the
203 remote network monitoring device has the opportunity
204 to add significant value to the data it collects.
205 For instance, by highlighting those hosts on the
206 network that generate the most traffic or errors, the
207 probe can give the management station precisely the
208 information it needs to solve a class of problems.
209
210 o Multiple Managers
211 An organization may have multiple management stations
212 for different units of the organization, for different
213 functions (e.g. engineering and operations), and in an
214 attempt to provide disaster recovery. Because
215 environments with multiple management stations are
216 common, the remote network monitoring device has to
217
218
219
220 <span class="grey">Remote Network Monitoring Working Group [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
223
224
225 deal with more than own management station,
226 potentially using its resources concurrently.
227
228 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Textual Conventions</span>
229
230 Two new data types are introduced as a textual convention in this MIB
231 document. These textual conventions enhance the readability of the
232 specification and can ease comparison with other specifications if
233 appropriate. It should be noted that the introduction of the these
234 textual conventions has no effect on either the syntax nor the
235 semantics of any managed objects. The use of these is merely an
236 artifact of the explanatory method used. Objects defined in terms of
237 one of these methods are always encoded by means of the rules that
238 define the primitive type. Hence, no changes to the SMI or the SNMP
239 are necessary to accommodate these textual conventions which are
240 adopted merely for the convenience of readers and writers in pursuit
241 of the elusive goal of clear, concise, and unambiguous MIB documents.
242
243 The new data types are: OwnerString and EntryStatus.
244
245 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Structure of MIB</span>
246
247 The objects are arranged into the following groups:
248
249 - statistics
250
251 - history
252
253 - alarm
254
255 - host
256
257 - hostTopN
258
259 - matrix
260
261 - filter
262
263 - packet capture
264
265 - event
266
267 These groups are the basic unit of conformance. If a remote
268 monitoring device implements a group, then it must implement all
269 objects in that group. For example, a managed agent that implements
270 the host group must implement the hostControlTable, the hostTable and
271 the hostTimeTable.
272
273
274
275
276 <span class="grey">Remote Network Monitoring Working Group [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
279
280
281 All groups in this MIB are optional. Implementations of this MIB
282 must also implement the system and interfaces group of MIB-II [<a href="#ref-6" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">6</a>].
283 MIB-II may also mandate the implementation of additional groups.
284
285 These groups are defined to provide a means of assigning object
286 identifiers, and to provide a method for managed agents to know which
287 objects they must implement.
288
289 <span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>. The Statistics Group</span>
290
291 The statistics group contains statistics measured by the probe for
292 each monitored interface on this device. This group currently
293 consists of the etherStatsTable but in the future will contain tables
294 for other media types including Token Ring and FDDI.
295
296 <span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a>. The History Group</span>
297
298 The history group records periodic statistical samples from a network
299 and stores them for later retrieval. This group currently consists
300 of the historyControlTable and the etherHistoryTable. In future
301 versions of the MIB, this group may contain tables for other media
302 types including Token Ring and FDDI.
303
304 <span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a>. The Alarm Group</span>
305
306 The alarm group periodically takes statistical samples from variables
307 in the probe and compares them to previously configured thresholds.
308 If the monitored variable crosses a threshold, an event is generated.
309 A hysteresis mechanism is implemented to limit the generation of
310 alarms. This group consists of the alarmTable and requires the
311 implementation of the event group.
312
313 <span class="h4"><a class="selflink" id="section-4.3.4" href="#section-4.3.4">4.3.4</a>. The Host Group</span>
314
315 The host group contains statistics associated with each host
316 discovered on the network. This group discovers hosts on the network
317 by keeping a list of source and destination MAC Addresses seen in
318 good packets promiscuously received from the network. This group
319 consists of the hostControlTable, the hostTable, and the
320 hostTimeTable.
321
322 <span class="h4"><a class="selflink" id="section-4.3.5" href="#section-4.3.5">4.3.5</a>. The HostTopN Group</span>
323
324 The hostTopN group is used to prepare reports that describe the hosts
325 that top a list ordered by one of their statistics. The available
326 statistics are samples of one of their base statistics over an
327 interval specified by the management station. Thus, these statistics
328 are rate based. The management station also selects how many such
329
330
331
332 <span class="grey">Remote Network Monitoring Working Group [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
335
336
337 hosts are reported. This group consists of the hostTopNControlTable
338 and the hostTopNTable, and requires the implementation of the host
339 group.
340
341 <span class="h4"><a class="selflink" id="section-4.3.6" href="#section-4.3.6">4.3.6</a>. The Matrix Group</span>
342
343 The matrix group stores statistics for conversations between sets of
344 two addresses. As the device detects a new conversation, it creates
345 a new entry in its tables. This group consists of the
346 matrixControlTable, the matrixSDTable and the matrixDSTable.
347
348 <span class="h4"><a class="selflink" id="section-4.3.7" href="#section-4.3.7">4.3.7</a>. The Filter Group</span>
349
350 The filter group allows packets to be matched by a filter equation.
351 These matched packets form a data stream that may be captured or may
352 generate events. This group consists of the filterTable and the
353 channelTable.
354
355 <span class="h4"><a class="selflink" id="section-4.3.8" href="#section-4.3.8">4.3.8</a>. The Packet Capture Group</span>
356
357 The Packet Capture group allows packets to be captured after they
358 flow through a channel. This group consists of the
359 bufferControlTable and the captureBufferTable, and requires the
360 implementation of the filter group.
361
362 <span class="h4"><a class="selflink" id="section-4.3.9" href="#section-4.3.9">4.3.9</a>. The Event Group</span>
363
364 The event group controls the generation and notification of events
365 from this device. This group consists of the eventTable and the
366 logTable.
367
368 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Control of Remote Network Monitoring Devices</span>
369
370 Due to the complex nature of the available functions in these
371 devices, the functions often need user configuration. In many cases,
372 the function requires parameters to be set up for a data collection
373 operation. The operation can proceed only after these parameters are
374 fully set up.
375
376 Many functional groups in this MIB have one or more tables in which
377 to set up control parameters, and one or more data tables in which to
378 place the results of the operation. The control tables are typically
379 read-write in nature, while the data tables are typically read-only.
380 Because the parameters in the control table often describe resulting
381 data in the data table, many of the parameters can be modified only
382 when the control entry is invalid. Thus, the method for modifying
383 these parameters is to invalidate the control entry, causing its
384 deletion and the deletion of any associated data entries, and then
385
386
387
388 <span class="grey">Remote Network Monitoring Working Group [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
391
392
393 create a new control entry with the proper parameters. Deleting the
394 control entry also gives a convenient method for reclaiming the
395 resources used by the associated data.
396
397 Some objects in this MIB provide a mechanism to execute an action on
398 the remote monitoring device. These objects may execute an action as
399 a result of a change in the state of the object. For those objects
400 in this MIB, a request to set an object to the same value as it
401 currently holds would thus cause no action to occur.
402
403 To facilitate control by multiple managers, resources have to be
404 shared among the managers. These resources are typically the memory
405 and computation resources that a function requires.
406
407 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Resource Sharing Among Multiple Management Stations</span>
408
409 When multiple management stations wish to use functions that compete
410 for a finite amount of resources on a device, a method to facilitate
411 this sharing of resources is required. Potential conflicts include:
412
413 o Two management stations wish to simultaneously use
414 resources that together would exceed the capability of
415 the device.
416
417 o A management station uses a significant amount of
418 resources for a long period of time.
419
420 o A management station uses resources and then crashes,
421 forgetting to free the resources so others may
422 use them.
423
424 A mechanism is provided for each management station initiated
425 function in this MIB to avoid these conflicts and to help resolve
426 them when they occur. Each function has a label identifying the
427 initiator (owner) of the function. This label is set by the
428 initiator to provide for the following possibilities:
429
430 o A management station may recognize resources it owns
431 and no longer needs.
432
433 o A network operator can find the management station that
434 owns the resource and negotiate for it to be freed.
435
436 o A network operator may decide to unilaterally free
437 resources another network operator has reserved.
438
439 o Upon initialization, a management station may recognize
440 resources it had reserved in the past. With this
441
442
443
444 <span class="grey">Remote Network Monitoring Working Group [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
447
448
449 information it may free the resources if it no longer
450 needs them.
451
452 Management stations and probes should support any format of the owner
453 string dictated by the local policy of the organization. It is
454 suggested that this name contain one or more of the following: IP
455 address, management station name, network manager's name, location,
456 or phone number. This information will help users to share the
457 resources more effectively.
458
459 There is often default functionality that the device wishes to set
460 up. The resources associated with this functionality are then owned
461 by the device itself. In this case, the device will set the relevant
462 owner object to a string starting with 'monitor'. Indiscriminate
463 modification of the monitor-owned configuration by network management
464 stations is discouraged. In fact, a network management station
465 should only modify these objects under the direction of the
466 administrator of the probe, often the network administrator.
467
468 When a network management station wishes to utilize a function in a
469 monitor, it is encouraged to first scan the control table of that
470 function to find an instance with similar parameters to share. This
471 is especially true for those instances owned by the monitor, which
472 can be assumed to change infrequently. If a management station
473 decides to share an instance owned by another management station, it
474 should understand that the management station that owns the instance
475 may indiscriminately modify or delete it.
476
477 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Row Addition Among Multiple Management Stations</span>
478
479 The addition of new rows is achieved using the method described in
480 [<a href="#ref-9" title="&quot;Concise MIB Definitions&quot;">9</a>]. In this MIB, rows are often added to a table in order to
481 configure a function. This configuration usually involves parameters
482 that control the operation of the function. The agent must check
483 these parameters to make sure they are appropriate given restrictions
484 defined in this MIB as well as any implementation specific
485 restrictions such as lack of resources. The agent implementor may be
486 confused as to when to check these parameters and when to signal to
487 the management station that the parameters are invalid. There are
488 two opportunities:
489
490 o When the management station sets each parameter object.
491
492 o When the management station sets the entry status object
493 to valid.
494
495 If the latter is chosen, it would be unclear to the management
496 station which of the several parameters was invalid and caused the
497
498
499
500 <span class="grey">Remote Network Monitoring Working Group [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
503
504
505 badValue error to be emitted. Thus, wherever possible, the
506 implementor should choose the former as it will provide more
507 information to the management station.
508
509 A problem can arise when multiple management stations attempt to set
510 configuration information simultaneously using SNMP. When this
511 involves the addition of a new conceptual row in the same control
512 table, the managers may collide, attempting to create the same entry.
513 To guard against these collisions, each such control entry contains a
514 status object with special semantics that help to arbitrate among the
515 managers. If an attempt is made with the row addition mechanism to
516 create such a status object and that object already exists, an error
517 is returned. When more than one manager simultaneously attempts to
518 create the same conceptual row, only the first will succeed. The
519 others will receive an error.
520
521 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Definitions</span>
522
523 <a href="./rfc1271">RFC1271</a>-MIB DEFINITIONS ::= BEGIN
524
525 IMPORTS
526 Counter FROM <a href="./rfc1155">RFC1155</a>-SMI
527 DisplayString FROM <a href="./rfc1158">RFC1158</a>-MIB
528 mib-2 FROM <a href="./rfc1213">RFC1213</a>-MIB
529 OBJECT-TYPE FROM <a href="./rfc1212">RFC-1212</a>;
530
531 -- This MIB module uses the extended OBJECT-TYPE macro as
532 -- defined in [<a href="#ref-9" title="&quot;Concise MIB Definitions&quot;">9</a>].
533
534
535 -- Remote Network Monitoring MIB
536
537 rmon OBJECT IDENTIFIER ::= { mib-2 16 }
538
539
540 -- textual conventions
541
542 OwnerString ::= DisplayString
543 -- This data type is used to model an administratively
544 -- assigned name of the owner of a resource. This
545 -- information is taken from the NVT ASCII character set.
546 -- It is suggested that this name contain one or more
547 -- of the following:
548 -- IP address, management station name, network manager's
549 -- name, location, or phone number.
550 -- In some cases the agent itself will be the owner of
551 -- an entry. In these cases, this string shall be set
552 -- to a string starting with 'monitor'.
553
554
555
556 <span class="grey">Remote Network Monitoring Working Group [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
559
560
561 --
562 -- SNMP access control is articulated entirely in terms of
563 -- the contents of MIB views; access to a particular SNMP
564 -- object instance depends only upon its presence or
565 -- absence in a particular MIB view and never upon its
566 -- value or the value of related object instances. Thus,
567 -- objects of this type afford resolution of resource
568 -- contention only among cooperating managers; they
569 -- realize no access control function with respect
570 -- to uncooperative parties.
571 --
572 -- By convention, objects with this syntax are declared
573 -- as having
574 --
575 -- SIZE (0..127)
576
577
578 EntryStatus ::= INTEGER
579 { valid(1),
580 createRequest(2),
581 underCreation(3),
582 invalid(4)
583 }
584
585 -- The status of a table entry.
586 --
587 -- Setting this object to the value invalid(4) has the
588 -- effect of invalidating the corresponding entry.
589 -- That is, it effectively disassociates the mapping
590 -- identified with said entry.
591 -- It is an implementation-specific matter as to whether
592 -- the agent removes an invalidated entry from the table.
593 -- Accordingly, management stations must be prepared to
594 -- receive tabular information from agents that corresponds
595 -- to entries currently not in use. Proper
596 -- interpretation of such entries requires examination
597 -- of the relevant EntryStatus object.
598 --
599 -- An existing instance of this object cannot be set to
600 -- createRequest(2). This object may only be set to
601 -- createRequest(2) when this instance is created. When
602 -- this object is created, the agent may wish to create
603 -- supplemental object instances to complete a conceptual
604 -- row in this table. Immediately after completing the
605 -- create operation, the agent must set this object to
606 -- underCreation(3).
607 --
608 -- Entries shall exist in the underCreation(3) state until
609
610
611
612 <span class="grey">Remote Network Monitoring Working Group [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
615
616
617 -- the management station is finished configuring the
618 -- entry and sets this object to valid(1) or aborts,
619 -- setting this object to invalid(4). If the agent
620 -- determines that an entry has been in the
621 -- underCreation(3) state for an abnormally long time,
622 -- it may decide that the management station has
623 -- crashed. If the agent makes this decision,
624 -- it may set this object to invalid(4) to reclaim the
625 -- entry. A prudent agent will understand that the
626 -- management station may need to wait for human input
627 -- and will allow for that possibility in its
628 -- determination of this abnormally long period.
629
630
631 statistics OBJECT IDENTIFIER ::= { rmon 1 }
632 history OBJECT IDENTIFIER ::= { rmon 2 }
633 alarm OBJECT IDENTIFIER ::= { rmon 3 }
634 hosts OBJECT IDENTIFIER ::= { rmon 4 }
635 hostTopN OBJECT IDENTIFIER ::= { rmon 5 }
636 matrix OBJECT IDENTIFIER ::= { rmon 6 }
637 filter OBJECT IDENTIFIER ::= { rmon 7 }
638 capture OBJECT IDENTIFIER ::= { rmon 8 }
639 event OBJECT IDENTIFIER ::= { rmon 9 }
640
641
642 -- The Statistics Group
643 --
644 -- Implementation of the Statistics group is optional.
645 --
646 -- The statistics group contains statistics measured by the
647 -- probe for each monitored interface on this device. These
648 -- statistics take the form of free running counters that
649 -- start from zero when a valid entry is created.
650 --
651 -- This group currently has statistics defined only for
652 -- Ethernet interfaces. Each etherStatsEntry contains
653 -- statistics for one Ethernet interface. The probe must
654 -- create one etherStats entry for each monitored Ethernet
655 -- interface on the device.
656
657 etherStatsTable OBJECT-TYPE
658 SYNTAX SEQUENCE OF EtherStatsEntry
659 ACCESS not-accessible
660 STATUS mandatory
661 DESCRIPTION
662 "A list of Ethernet statistics entries."
663 ::= { statistics 1 }
664
665
666
667
668 <span class="grey">Remote Network Monitoring Working Group [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
671
672
673 etherStatsEntry OBJECT-TYPE
674 SYNTAX EtherStatsEntry
675 ACCESS not-accessible
676 STATUS mandatory
677 DESCRIPTION
678 "A collection of statistics kept for a particular
679 Ethernet interface."
680 INDEX { etherStatsIndex }
681 ::= { etherStatsTable 1 }
682
683 EtherStatsEntry ::= SEQUENCE {
684 etherStatsIndex INTEGER (1..65535),
685 etherStatsDataSource OBJECT IDENTIFIER,
686 etherStatsDropEvents Counter,
687 etherStatsOctets Counter,
688 etherStatsPkts Counter,
689 etherStatsBroadcastPkts Counter,
690 etherStatsMulticastPkts Counter,
691 etherStatsCRCAlignErrors Counter,
692 etherStatsUndersizePkts Counter,
693 etherStatsOversizePkts Counter,
694 etherStatsFragments Counter,
695 etherStatsJabbers Counter,
696 etherStatsCollisions Counter,
697 etherStatsPkts64Octets Counter,
698 etherStatsPkts65to127Octets Counter,
699 etherStatsPkts128to255Octets Counter,
700 etherStatsPkts256to511Octets Counter,
701 etherStatsPkts512to1023Octets Counter,
702 etherStatsPkts1024to1518Octets Counter,
703 etherStatsOwner OwnerString,
704 etherStatsStatus INTEGER
705 }
706
707 etherStatsIndex OBJECT-TYPE
708 SYNTAX INTEGER (1..65535)
709 ACCESS read-only
710 STATUS mandatory
711 DESCRIPTION
712 "The value of this object uniquely identifies this
713 etherStats entry."
714 ::= { etherStatsEntry 1 }
715
716 etherStatsDataSource OBJECT-TYPE
717 SYNTAX OBJECT IDENTIFIER
718 ACCESS read-write
719 STATUS mandatory
720 DESCRIPTION
721
722
723
724 <span class="grey">Remote Network Monitoring Working Group [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
727
728
729 "This object identifies the source of the data that
730 this etherStats entry is configured to analyze. This
731 source can be any ethernet interface on this device.
732 In order to identify a particular interface, this
733 object shall identify the instance of the ifIndex
734 object, defined in [<a href="#ref-4" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">4</a>,<a href="#ref-6" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">6</a>], for the desired interface.
735 For example, if an entry were to receive data from
736 interface #1, this object would be set to ifIndex.1.
737
738 The statistics in this group reflect all packets
739 on the local network segment attached to the
740 identified interface.
741
742 This object may not be modified if the associated
743 etherStatsStatus object is equal to valid(1)."
744 ::= { etherStatsEntry 2 }
745
746 etherStatsDropEvents OBJECT-TYPE
747 SYNTAX Counter
748 ACCESS read-only
749 STATUS mandatory
750 DESCRIPTION
751 "The total number of events in which packets
752 were dropped by the probe due to lack of resources.
753 Note that this number is not necessarily the number of
754 packets dropped; it is just the number of times this
755 condition has been detected."
756 ::= { etherStatsEntry 3 }
757
758 etherStatsOctets OBJECT-TYPE
759 SYNTAX Counter
760 ACCESS read-only
761 STATUS mandatory
762 DESCRIPTION
763 "The total number of octets of data (including
764 those in bad packets) received on the
765 network (excluding framing bits but including
766 FCS octets)."
767 ::= { etherStatsEntry 4 }
768
769 etherStatsPkts OBJECT-TYPE
770 SYNTAX Counter
771 ACCESS read-only
772 STATUS mandatory
773 DESCRIPTION
774 "The total number of packets (including error packets)
775 received."
776 ::= { etherStatsEntry 5 }
777
778
779
780 <span class="grey">Remote Network Monitoring Working Group [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
783
784
785 etherStatsBroadcastPkts OBJECT-TYPE
786 SYNTAX Counter
787 ACCESS read-only
788 STATUS mandatory
789 DESCRIPTION
790 "The total number of good packets received that were
791 directed to the broadcast address."
792 ::= { etherStatsEntry 6 }
793
794 etherStatsMulticastPkts OBJECT-TYPE
795 SYNTAX Counter
796 ACCESS read-only
797 STATUS mandatory
798 DESCRIPTION
799 "The total number of good packets received that were
800 directed to a multicast address. Note that this
801 number does not include packets directed to the
802 broadcast address."
803 ::= { etherStatsEntry 7 }
804
805 etherStatsCRCAlignErrors OBJECT-TYPE
806 SYNTAX Counter
807 ACCESS read-only
808 STATUS mandatory
809 DESCRIPTION
810 "The total number of packets received that
811 had a length (excluding framing bits, but
812 including FCS octets) of between 64 and 1518
813 octets, inclusive, but were not an integral number
814 of octets in length or had a bad Frame Check
815 Sequence (FCS)."
816 ::= { etherStatsEntry 8 }
817
818 etherStatsUndersizePkts OBJECT-TYPE
819 SYNTAX Counter
820 ACCESS read-only
821 STATUS mandatory
822 DESCRIPTION
823 "The total number of packets received that were
824 less than 64 octets long (excluding framing bits,
825 but including FCS octets) and were otherwise well
826 formed."
827 ::= { etherStatsEntry 9 }
828
829 etherStatsOversizePkts OBJECT-TYPE
830 SYNTAX Counter
831 ACCESS read-only
832 STATUS mandatory
833
834
835
836 <span class="grey">Remote Network Monitoring Working Group [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
839
840
841 DESCRIPTION
842 "The total number of packets received that were
843 longer than 1518 octets (excluding framing bits,
844 but including FCS octets) and were otherwise
845 well formed."
846 ::= { etherStatsEntry 10 }
847
848 etherStatsFragments OBJECT-TYPE
849 SYNTAX Counter
850 ACCESS read-only
851 STATUS mandatory
852 DESCRIPTION
853 "The total number of packets received that were not an
854 integral number of octets in length or that had a bad
855 Frame Check Sequence (FCS), and were less than 64
856 octets in length (excluding framing bits but
857 including FCS octets)."
858 ::= { etherStatsEntry 11 }
859
860 etherStatsJabbers OBJECT-TYPE
861 SYNTAX Counter
862 ACCESS read-only
863 STATUS mandatory
864 DESCRIPTION
865 "The total number of packets received that were
866 longer than 1518 octets (excluding framing bits,
867 but including FCS octets), and were not an
868 integral number of octets in length or had
869 a bad Frame Check Sequence (FCS)."
870 ::= { etherStatsEntry 12 }
871
872 etherStatsCollisions OBJECT-TYPE
873 SYNTAX Counter
874 ACCESS read-only
875 STATUS mandatory
876 DESCRIPTION
877 "The best estimate of the total number of collisions
878 on this Ethernet segment."
879 ::= { etherStatsEntry 13 }
880
881 etherStatsPkts64Octets OBJECT-TYPE
882 SYNTAX Counter
883 ACCESS read-only
884 STATUS mandatory
885 DESCRIPTION
886 "The total number of packets (including error
887 packets) received that were 64 octets in length
888 (excluding framing bits but including FCS octets)."
889
890
891
892 <span class="grey">Remote Network Monitoring Working Group [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
895
896
897 ::= { etherStatsEntry 14 }
898
899 etherStatsPkts65to127Octets OBJECT-TYPE
900 SYNTAX Counter
901 ACCESS read-only
902 STATUS mandatory
903 DESCRIPTION
904 "The total number of packets (including error
905 packets) received that were between
906 65 and 127 octets in length inclusive
907 (excluding framing bits but including FCS octets)."
908 ::= { etherStatsEntry 15 }
909
910 etherStatsPkts128to255Octets OBJECT-TYPE
911 SYNTAX Counter
912 ACCESS read-only
913 STATUS mandatory
914 DESCRIPTION
915 "The total number of packets (including error
916 packets) received that were between
917 128 and 255 octets in length inclusive
918 (excluding framing bits but including FCS octets)."
919 ::= { etherStatsEntry 16 }
920
921 etherStatsPkts256to511Octets OBJECT-TYPE
922 SYNTAX Counter
923 ACCESS read-only
924 STATUS mandatory
925 DESCRIPTION
926 "The total number of packets (including error
927 packets) received that were between
928 256 and 511 octets in length inclusive
929 (excluding framing bits but including FCS octets)."
930 ::= { etherStatsEntry 17 }
931
932 etherStatsPkts512to1023Octets OBJECT-TYPE
933 SYNTAX Counter
934 ACCESS read-only
935 STATUS mandatory
936 DESCRIPTION
937 "The total number of packets (including error
938 packets) received that were between
939 512 and 1023 octets in length inclusive
940 (excluding framing bits but including FCS octets)."
941 ::= { etherStatsEntry 18 }
942
943
944
945
946
947
948 <span class="grey">Remote Network Monitoring Working Group [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
951
952
953 etherStatsPkts1024to1518Octets OBJECT-TYPE
954 SYNTAX Counter
955 ACCESS read-only
956 STATUS mandatory
957 DESCRIPTION
958 "The total number of packets (including error
959 packets) received that were between
960 1024 and 1518 octets in length inclusive
961 (excluding framing bits but including FCS octets)."
962 ::= { etherStatsEntry 19 }
963
964 etherStatsOwner OBJECT-TYPE
965 SYNTAX OwnerString
966 ACCESS read-write
967 STATUS mandatory
968 DESCRIPTION
969 "The entity that configured this entry and is
970 therefore using the resources assigned to it."
971 ::= { etherStatsEntry 20 }
972
973 etherStatsStatus OBJECT-TYPE
974 SYNTAX EntryStatus
975 ACCESS read-write
976 STATUS mandatory
977 DESCRIPTION
978 "The status of this etherStats entry."
979 ::= { etherStatsEntry 21 }
980
981
982 -- The History Group
983
984 -- Implementation of the History group is optional.
985 --
986 -- The history group records periodic statistical samples from
987 -- a network and stores them for later retrieval. The
988 -- historyControl table stores configuration entries that each
989 -- define an interface, polling period, and other parameters.
990 -- Once samples are taken, their data is stored in an entry
991 -- in a media-specific table. Each such entry defines one
992 -- sample, and is associated with the historyControlEntry that
993 -- caused the sample to be taken. Currently the only media-
994 -- specific table defined is the etherHistoryTable, for
995 -- Ethernet networks.
996 --
997 -- If the probe keeps track of the time of day, it should
998 -- start the first sample of the history at a time such that
999 -- when the next hour of the day begins, a sample is
1000 -- started at that instant. This tends to make more
1001
1002
1003
1004 <span class="grey">Remote Network Monitoring Working Group [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1007
1008
1009 -- user-friendly reports, and enables comparison of reports
1010 -- from different probes that have relatively accurate time
1011 -- of day.
1012 --
1013 -- The monitor is encouraged to add two history control entries
1014 -- per monitored interface upon initialization that describe
1015 -- a short term and a long term polling period. Suggested
1016 -- parameters are 30 seconds for the short term polling
1017 -- period and 30 minutes for the long term period.
1018
1019 historyControlTable OBJECT-TYPE
1020 SYNTAX SEQUENCE OF HistoryControlEntry
1021 ACCESS not-accessible
1022 STATUS mandatory
1023 DESCRIPTION
1024 "A list of history control entries."
1025 ::= { history 1 }
1026
1027 historyControlEntry OBJECT-TYPE
1028 SYNTAX HistoryControlEntry
1029 ACCESS not-accessible
1030 STATUS mandatory
1031 DESCRIPTION
1032 "A list of parameters that set up a periodic
1033 sampling of statistics."
1034 INDEX { historyControlIndex }
1035 ::= { historyControlTable 1 }
1036
1037 HistoryControlEntry ::= SEQUENCE {
1038 historyControlIndex INTEGER (1..65535),
1039 historyControlDataSource OBJECT IDENTIFIER,
1040 historyControlBucketsRequested INTEGER (1..65535),
1041 historyControlBucketsGranted INTEGER (1..65535),
1042 historyControlInterval INTEGER (1..3600),
1043 historyControlOwner OwnerString,
1044 historyControlStatus INTEGER
1045 }
1046
1047 historyControlIndex OBJECT-TYPE
1048 SYNTAX INTEGER (1..65535)
1049 ACCESS read-only
1050 STATUS mandatory
1051 DESCRIPTION
1052 "An index that uniquely identifies an entry in the
1053 historyControl table. Each such entry defines a
1054 set of samples at a particular interval for an
1055 interface on the device."
1056 ::= { historyControlEntry 1 }
1057
1058
1059
1060 <span class="grey">Remote Network Monitoring Working Group [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1063
1064
1065 historyControlDataSource OBJECT-TYPE
1066 SYNTAX OBJECT IDENTIFIER
1067 ACCESS read-write
1068 STATUS mandatory
1069 DESCRIPTION
1070 "This object identifies the source of the data for
1071 which historical data was collected and
1072 placed in a media-specific table on behalf of this
1073 historyControlEntry. This source can be any
1074 interface on this device. In order to identify
1075 a particular interface, this object shall identify
1076 the instance of the ifIndex object, defined
1077 in [<a href="#ref-4" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">4</a>,<a href="#ref-6" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">6</a>], for the desired interface. For example,
1078 if an entry were to receive data from interface #1,
1079 this object would be set to ifIndex.1.
1080
1081 The statistics in this group reflect all packets
1082 on the local network segment attached to the
1083 identified interface.
1084
1085 This object may not be modified if the associated
1086 historyControlStatus object is equal to valid(1)."
1087 ::= { historyControlEntry 2 }
1088
1089 historyControlBucketsRequested OBJECT-TYPE
1090 SYNTAX INTEGER (1..65535)
1091 ACCESS read-write
1092 STATUS mandatory
1093 DESCRIPTION
1094 "The requested number of discrete time intervals
1095 over which data is to be saved in the part of the
1096 media-specific table associated with this
1097 historyControl entry.
1098
1099 When this object is created or modified, the probe
1100 should set historyControlBucketsGranted as closely to
1101 this object as is possible for the particular probe
1102 implementation and available resources."
1103 DEFVAL { 50 }
1104 ::= { historyControlEntry 3 }
1105
1106 historyControlBucketsGranted OBJECT-TYPE
1107 SYNTAX INTEGER (1..65535)
1108 ACCESS read-only
1109 STATUS mandatory
1110 DESCRIPTION
1111 "The number of discrete sampling intervals
1112 over which data shall be saved in the part of
1113
1114
1115
1116 <span class="grey">Remote Network Monitoring Working Group [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1119
1120
1121 the media-specific table associated with this
1122 historyControl entry.
1123
1124 When the associated historyControlBucketsRequested
1125 object is created or modified, the probe
1126 should set this object as closely to the requested
1127 value as is possible for the particular
1128 probe implementation and available resources. The
1129 probe must not lower this value except as a result
1130 of a modification to the associated
1131 historyControlBucketsRequested object.
1132
1133 There will be times when the actual number of
1134 buckets associated with this entry is less than
1135 the value of this object. In this case, at the
1136 end of each sampling interval, a new bucket will
1137 be added to the media-specific table.
1138
1139 When the number of buckets reaches the value of
1140 this object and a new bucket is to be added to the
1141 media-specific table, the oldest bucket associated
1142 with this historyControlEntry shall be deleted by
1143 the agent so that the new bucket can be added.
1144
1145 When the value of this object changes to a value less
1146 than the current value, entries are deleted
1147 from the media-specific table associated with this
1148 historyControlEntry. Enough of the oldest of these
1149 entries shall be deleted by the agent so that their
1150 number remains less than or equal to the new value of
1151 this object.
1152
1153 When the value of this object changes to a value
1154 greater than the current value, the number of
1155 associated media-specific entries may be allowed
1156 to grow."
1157 ::= { historyControlEntry 4 }
1158
1159 historyControlInterval OBJECT-TYPE
1160 SYNTAX INTEGER (1..3600)
1161 ACCESS read-write
1162 STATUS mandatory
1163 DESCRIPTION
1164 "The interval in seconds over which the data is
1165 sampled for each bucket in the part of the
1166 media-specific table associated with this
1167 historyControl entry. This interval can
1168 be set to any number of seconds between 1 and
1169
1170
1171
1172 <span class="grey">Remote Network Monitoring Working Group [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1175
1176
1177 3600 (1 hour).
1178
1179 Because the counters in a bucket may overflow at their
1180 maximum value with no indication, a prudent manager
1181 will take into account the possibility of overflow
1182 in any of the associated counters. It is important
1183 to consider the minimum time in which any counter
1184 could overflow on a particular media type and set
1185 the historyControlInterval object to a value less
1186 than this interval. This is typically most
1187 important for the 'octets' counter in any
1188 media-specific table. For example, on an Ethernet
1189 network, the etherHistoryOctets counter could overflow
1190 in about one hour at the Ethernet's maximum
1191 utilization.
1192
1193 This object may not be modified if the associated
1194 historyControlStatus object is equal to valid(1)."
1195 DEFVAL { 1800 }
1196 ::= { historyControlEntry 5 }
1197
1198 historyControlOwner OBJECT-TYPE
1199 SYNTAX OwnerString
1200 ACCESS read-write
1201 STATUS mandatory
1202 DESCRIPTION
1203 "The entity that configured this entry and is therefore
1204 using the resources assigned to it."
1205 ::= { historyControlEntry 6 }
1206
1207 historyControlStatus OBJECT-TYPE
1208 SYNTAX EntryStatus
1209 ACCESS read-write
1210 STATUS mandatory
1211 DESCRIPTION
1212 "The status of this historyControl entry.
1213
1214 Each instance of the media-specific table associated
1215 with this historyControlEntry will be deleted by the
1216 agent if this historyControlEntry is not equal to
1217 valid(1)."
1218 ::= { historyControlEntry 7 }
1219
1220
1221 -- Ether History table
1222
1223 etherHistoryTable OBJECT-TYPE
1224 SYNTAX SEQUENCE OF EtherHistoryEntry
1225
1226
1227
1228 <span class="grey">Remote Network Monitoring Working Group [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1231
1232
1233 ACCESS not-accessible
1234 STATUS mandatory
1235 DESCRIPTION
1236 "A list of Ethernet history entries."
1237 ::= { history 2 }
1238
1239 etherHistoryEntry OBJECT-TYPE
1240 SYNTAX EtherHistoryEntry
1241 ACCESS not-accessible
1242 STATUS mandatory
1243 DESCRIPTION
1244 "An historical sample of Ethernet statistics on a
1245 particular Ethernet interface. This sample is
1246 associated with the historyControlEntry which set
1247 up the parameters for a regular collection of these
1248 samples."
1249 INDEX { etherHistoryIndex , etherHistorySampleIndex }
1250 ::= { etherHistoryTable 1 }
1251
1252 EtherHistoryEntry ::= SEQUENCE {
1253 etherHistoryIndex INTEGER (1..65535),
1254 etherHistorySampleIndex INTEGER,
1255 etherHistoryIntervalStart TimeTicks,
1256 etherHistoryDropEvents Counter,
1257 etherHistoryOctets Counter,
1258 etherHistoryPkts Counter,
1259 etherHistoryBroadcastPkts Counter,
1260 etherHistoryMulticastPkts Counter,
1261 etherHistoryCRCAlignErrors Counter,
1262 etherHistoryUndersizePkts Counter,
1263 etherHistoryOversizePkts Counter,
1264 etherHistoryFragments Counter,
1265 etherHistoryJabbers Counter,
1266 etherHistoryCollisions Counter,
1267 etherHistoryUtilization INTEGER (0..10000)
1268 }
1269
1270 etherHistoryIndex OBJECT-TYPE
1271 SYNTAX INTEGER (1..65535)
1272 ACCESS read-only
1273 STATUS mandatory
1274 DESCRIPTION
1275 "The history of which this entry is a part. The
1276 history identified by a particular value of this
1277 index is the same history as identified
1278 by the same value of historyControlIndex."
1279 ::= { etherHistoryEntry 1 }
1280
1281
1282
1283
1284 <span class="grey">Remote Network Monitoring Working Group [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1287
1288
1289 etherHistorySampleIndex OBJECT-TYPE
1290 SYNTAX INTEGER
1291 ACCESS read-only
1292 STATUS mandatory
1293 DESCRIPTION
1294 "An index that uniquely identifies the particular
1295 sample this entry represents among all samples
1296 associated with the same historyControlEntry.
1297 This index starts at 1 and increases by one
1298 as each new sample is taken."
1299 ::= { etherHistoryEntry 2 }
1300
1301 etherHistoryIntervalStart OBJECT-TYPE
1302 SYNTAX TimeTicks
1303 ACCESS read-only
1304 STATUS mandatory
1305 DESCRIPTION
1306 "The value of sysUpTime at the start of the interval
1307 over which this sample was measured. If the probe
1308 keeps track of the time of day, it should start
1309 the first sample of the history at a time such that
1310 when the next hour of the day begins, a sample is
1311 started at that instant. Note that following this
1312 rule may require the probe to delay collecting the
1313 first sample of the history, as each sample must be
1314 of the same interval. Also note that the sample which
1315 is currently being collected is not accessible in this
1316 table until the end of its interval."
1317 ::= { etherHistoryEntry 3 }
1318
1319 etherHistoryDropEvents OBJECT-TYPE
1320 SYNTAX Counter
1321 ACCESS read-only
1322 STATUS mandatory
1323 DESCRIPTION
1324 "The total number of events in which packets
1325 were dropped by the probe due to lack of resources
1326 during this interval. Note that this number is not
1327 necessarily the number of packets dropped, it is just
1328 the number of times this condition has been detected."
1329 ::= { etherHistoryEntry 4 }
1330
1331 etherHistoryOctets OBJECT-TYPE
1332 SYNTAX Counter
1333 ACCESS read-only
1334 STATUS mandatory
1335 DESCRIPTION
1336 "The total number of octets of data (including
1337
1338
1339
1340 <span class="grey">Remote Network Monitoring Working Group [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1343
1344
1345 those in bad packets) received on the
1346 network (excluding framing bits but including
1347 FCS octets)."
1348 ::= { etherHistoryEntry 5 }
1349
1350 etherHistoryPkts OBJECT-TYPE
1351 SYNTAX Counter
1352 ACCESS read-only
1353 STATUS mandatory
1354 DESCRIPTION
1355 "The number of packets (including error packets)
1356 received during this sampling interval."
1357 ::= { etherHistoryEntry 6 }
1358
1359 etherHistoryBroadcastPkts OBJECT-TYPE
1360 SYNTAX Counter
1361 ACCESS read-only
1362 STATUS mandatory
1363 DESCRIPTION
1364 "The number of good packets received during this
1365 sampling interval that were directed to the
1366 broadcast address."
1367 ::= { etherHistoryEntry 7 }
1368
1369 etherHistoryMulticastPkts OBJECT-TYPE
1370 SYNTAX Counter
1371 ACCESS read-only
1372 STATUS mandatory
1373 DESCRIPTION
1374 "The number of good packets received during this
1375 sampling interval that were directed to a
1376 multicast address. Note that this number does not
1377 include packets addressed to the broadcast address."
1378 ::= { etherHistoryEntry 8 }
1379
1380 etherHistoryCRCAlignErrors OBJECT-TYPE
1381 SYNTAX Counter
1382 ACCESS read-only
1383 STATUS mandatory
1384 DESCRIPTION
1385 "The number of packets received during this
1386 sampling interval that had a length (excluding
1387 framing bits but including FCS octets) between
1388 64 and 1518 octets, inclusive, but were not an
1389 integral number of octets in length or had a
1390 bad Frame Check Sequence (FCS)."
1391 ::= { etherHistoryEntry 9 }
1392
1393
1394
1395
1396 <span class="grey">Remote Network Monitoring Working Group [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1399
1400
1401 etherHistoryUndersizePkts OBJECT-TYPE
1402 SYNTAX Counter
1403 ACCESS read-only
1404 STATUS mandatory
1405 DESCRIPTION
1406 "The number of packets received during this
1407 interval that were less than 64 octets long
1408 (excluding framing bits but including FCS
1409 octets) and were otherwise well formed."
1410 ::= { etherHistoryEntry 10 }
1411
1412 etherHistoryOversizePkts OBJECT-TYPE
1413 SYNTAX Counter
1414 ACCESS read-only
1415 STATUS mandatory
1416 DESCRIPTION
1417 "The number of packets received during this
1418 interval that were longer than 1518 octets
1419 (excluding framing bits but including FCS
1420 octets) but were otherwise well formed."
1421 ::= { etherHistoryEntry 11 }
1422
1423 etherHistoryFragments OBJECT-TYPE
1424 SYNTAX Counter
1425 ACCESS read-only
1426 STATUS mandatory
1427 DESCRIPTION
1428 "The total number of packets received during this
1429 sampling interval that were not an integral
1430 number of octets in length or that
1431 had a bad Frame Check Sequence (FCS), and
1432 were less than 64 octets in length (excluding
1433 framing bits but including FCS octets)."
1434 ::= { etherHistoryEntry 12 }
1435
1436 etherHistoryJabbers OBJECT-TYPE
1437 SYNTAX Counter
1438 ACCESS read-only
1439 STATUS mandatory
1440 DESCRIPTION
1441 "The number of packets received during this
1442 interval that were longer than 1518 octets
1443 (excluding framing bits but including FCS octets),
1444 and were not an integral number of octets in
1445 length or had a bad Frame Check Sequence (FCS)."
1446 ::= { etherHistoryEntry 13 }
1447
1448
1449
1450
1451
1452 <span class="grey">Remote Network Monitoring Working Group [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1455
1456
1457 etherHistoryCollisions OBJECT-TYPE
1458 SYNTAX Counter
1459 ACCESS read-only
1460 STATUS mandatory
1461 DESCRIPTION
1462 "The best estimate of the total number of collisions
1463 on this Ethernet segment during this interval."
1464 ::= { etherHistoryEntry 14 }
1465
1466 etherHistoryUtilization OBJECT-TYPE
1467 SYNTAX INTEGER (0..10000)
1468 ACCESS read-only
1469 STATUS mandatory
1470 DESCRIPTION
1471 "The best estimate of the mean physical layer
1472 network utilization on this interface during this
1473 interval, in hundredths of a percent."
1474 ::= { etherHistoryEntry 15 }
1475
1476
1477 -- The Alarm Group
1478
1479 -- Implementation of the Alarm group is optional.
1480 --
1481 -- The Alarm Group requires the implementation of the Event
1482 -- group.
1483 --
1484 -- The Alarm group periodically takes statistical samples from
1485 -- variables in the probe and compares them to thresholds
1486 -- that have been configured. The alarm table stores
1487 -- configuration entries that each define a variable,
1488 -- polling period, and threshold parameters. If a sample is
1489 -- found to cross the threshold values, an event is
1490 -- generated. Only variables that resolve to an ASN.1
1491 -- primitive type of INTEGER (INTEGER, Counter,
1492 -- Gauge, or TimeTicks) may be monitored in this way.
1493 --
1494 -- This function has a hysteresis mechanism to limit the
1495 -- generation of events. This mechanism generates one event
1496 -- as a threshold is crossed in the appropriate direction.
1497 -- No more events are generated for that threshold until the
1498 -- opposite threshold is crossed.
1499 --
1500 -- In the case of a sampling a deltaValue, a probe may
1501 -- implement this mechanism with more precision if it takes
1502 -- a delta sample twice per period, each time comparing the
1503 -- sum of the latest two samples to the threshold. This
1504 -- allows the detection of threshold crossings
1505
1506
1507
1508 <span class="grey">Remote Network Monitoring Working Group [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1511
1512
1513 -- that span the sampling boundary. Note that this does not
1514 -- require any special configuration of the threshold value.
1515 -- It is suggested that probes implement this more precise
1516 -- algorithm.
1517
1518 alarmTable OBJECT-TYPE
1519 SYNTAX SEQUENCE OF AlarmEntry
1520 ACCESS not-accessible
1521 STATUS mandatory
1522 DESCRIPTION
1523 "A list of alarm entries."
1524 ::= { alarm 1 }
1525
1526 alarmEntry OBJECT-TYPE
1527 SYNTAX AlarmEntry
1528 ACCESS not-accessible
1529 STATUS mandatory
1530 DESCRIPTION
1531 "A list of parameters that set up a periodic checking
1532 for alarm conditions."
1533 INDEX { alarmIndex }
1534 ::= { alarmTable 1 }
1535
1536 AlarmEntry ::= SEQUENCE {
1537 alarmIndex INTEGER (1..65535),
1538 alarmInterval INTEGER,
1539 alarmVariable OBJECT IDENTIFIER,
1540 alarmSampleType INTEGER,
1541 alarmValue INTEGER,
1542 alarmStartupAlarm INTEGER,
1543 alarmRisingThreshold INTEGER,
1544 alarmFallingThreshold INTEGER,
1545 alarmRisingEventIndex INTEGER (1..65535),
1546 alarmFallingEventIndex INTEGER (1..65535),
1547 alarmOwner OwnerString,
1548 alarmStatus INTEGER
1549 }
1550
1551 alarmIndex OBJECT-TYPE
1552 SYNTAX INTEGER (1..65535)
1553 ACCESS read-only
1554 STATUS mandatory
1555 DESCRIPTION
1556 "An index that uniquely identifies an entry in the
1557 alarm table. Each such entry defines a
1558 diagnostic sample at a particular interval
1559 for an object on the device."
1560 ::= { alarmEntry 1 }
1561
1562
1563
1564 <span class="grey">Remote Network Monitoring Working Group [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1567
1568
1569 alarmInterval OBJECT-TYPE
1570 SYNTAX INTEGER
1571 ACCESS read-write
1572 STATUS mandatory
1573 DESCRIPTION
1574 "The interval in seconds over which the data is
1575 sampled and compared with the rising and falling
1576 thresholds. When setting this variable, care
1577 should be given to ensure that the variable being
1578 monitored will not exceed 2^31 - 1 and roll
1579 over the alarmValue object during the interval.
1580
1581 This object may not be modified if the associated
1582 alarmStatus object is equal to valid(1)."
1583 ::= { alarmEntry 2 }
1584
1585 alarmVariable OBJECT-TYPE
1586 SYNTAX OBJECT IDENTIFIER
1587 ACCESS read-write
1588 STATUS mandatory
1589 DESCRIPTION
1590 "The object identifier of the particular variable to
1591 be sampled. Only variables that resolve to an ASN.1
1592 primitive type of INTEGER (INTEGER, Counter, Gauge,
1593 or TimeTicks) may be sampled.
1594
1595 Because SNMP access control is articulated entirely
1596 in terms of the contents of MIB views, no access
1597 control mechanism exists that can restrict the value of
1598 this object to identify only those objects that exist
1599 in a particular MIB view. Because there is thus no
1600 acceptable means of restricting the read access that
1601 could be obtained through the alarm mechanism, the
1602 probe must only grant write access to this object in
1603 those views that have read access to all objects on
1604 the probe.
1605
1606 During a set operation, if the supplied variable
1607 name is not available in the selected MIB view, a
1608 badValue error must be returned. If at any time
1609 the variable name of an established alarmEntry is
1610 no longer available in the selected MIB view, the
1611 probe must change the status of this alarmEntry
1612 to invalid(4).
1613
1614 This object may not be modified if the associated
1615 alarmStatus object is equal to valid(1)."
1616 ::= { alarmEntry 3 }
1617
1618
1619
1620 <span class="grey">Remote Network Monitoring Working Group [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1623
1624
1625 alarmSampleType OBJECT-TYPE
1626 SYNTAX INTEGER {
1627 absoluteValue(1),
1628 deltaValue(2)
1629 }
1630 ACCESS read-write
1631 STATUS mandatory
1632 DESCRIPTION
1633 "The method of sampling the selected variable and
1634 calculating the value to be compared against the
1635 thresholds. If the value of this object is
1636 absoluteValue(1), the value of the selected variable
1637 will be compared directly with the thresholds at the
1638 end of the sampling interval. If the value of this
1639 object is deltaValue(2), the value of the selected
1640 variable at the last sample will be subtracted from
1641 the current value, and the difference compared with
1642 the thresholds.
1643
1644 This object may not be modified if the associated
1645 alarmStatus object is equal to valid(1)."
1646 ::= { alarmEntry 4 }
1647
1648 alarmValue OBJECT-TYPE
1649 SYNTAX INTEGER
1650 ACCESS read-only
1651 STATUS mandatory
1652 DESCRIPTION
1653 "The value of the statistic during the last sampling
1654 period. The value during the current sampling period
1655 is not made available until the period is completed."
1656 ::= { alarmEntry 5 }
1657
1658 alarmStartupAlarm OBJECT-TYPE
1659 SYNTAX INTEGER {
1660 risingAlarm(1),
1661 fallingAlarm(2),
1662 risingOrFallingAlarm(3)
1663 }
1664 ACCESS read-write
1665 STATUS mandatory
1666 DESCRIPTION
1667 "The alarm that may be sent when this entry is first
1668 set to valid. If the first sample after this entry
1669 becomes valid is greater than or equal to the
1670 risingThreshold and alarmStartupAlarm is equal to
1671 risingAlarm(1) or risingOrFallingAlarm(3), then a
1672 single rising alarm will be generated. If the first
1673
1674
1675
1676 <span class="grey">Remote Network Monitoring Working Group [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1679
1680
1681 sample after this entry becomes valid is less than
1682 or equal to the fallingThreshold and
1683 alarmStartupAlarm is equal to fallingAlarm(2) or
1684 risingOrFallingAlarm(3), then a single falling
1685 alarm will be generated.
1686
1687 This object may not be modified if the associated
1688 alarmStatus object is equal to valid(1)."
1689 ::= { alarmEntry 6 }
1690
1691 alarmRisingThreshold OBJECT-TYPE
1692 SYNTAX INTEGER
1693 ACCESS read-write
1694 STATUS mandatory
1695 DESCRIPTION
1696 "A threshold for the sampled statistic. When the
1697 current sampled value is greater than or equal to
1698 this threshold, and the value at the last sampling
1699 interval was less than this threshold, a single
1700 event will be generated.
1701 A single event will also be generated if the first
1702 sample after this entry becomes valid is greater
1703 than or equal to this threshold and the associated
1704 alarmStartupAlarm is equal to risingAlarm(1) or
1705 risingOrFallingAlarm(3).
1706
1707 After a rising event is generated, another such event
1708 will not be generated until the sampled value
1709 falls below this threshold and reaches the
1710 alarmFallingThreshold.
1711
1712 This object may not be modified if the associated
1713 alarmStatus object is equal to valid(1)."
1714 ::= { alarmEntry 7 }
1715
1716 alarmFallingThreshold OBJECT-TYPE
1717 SYNTAX INTEGER
1718 ACCESS read-write
1719 STATUS mandatory
1720 DESCRIPTION
1721 "A threshold for the sampled statistic. When the
1722 current sampled value is less than or equal to
1723 this threshold, and the value at the last sampling
1724 interval was greater than this threshold, a single
1725 event will be generated.
1726 A single event will also be generated if the first
1727 sample after this entry becomes valid is less than or
1728 equal to this threshold and the associated
1729
1730
1731
1732 <span class="grey">Remote Network Monitoring Working Group [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1735
1736
1737 alarmStartupAlarm is equal to fallingAlarm(2) or
1738 risingOrFallingAlarm(3).
1739
1740 After a falling event is generated, another such event
1741 will not be generated until the sampled value
1742 rises above this threshold and reaches the
1743 alarmRisingThreshold.
1744
1745 This object may not be modified if the associated
1746 alarmStatus object is equal to valid(1)."
1747 ::= { alarmEntry 8 }
1748
1749 alarmRisingEventIndex OBJECT-TYPE
1750 SYNTAX INTEGER (0..65535)
1751 ACCESS read-write
1752 STATUS mandatory
1753 DESCRIPTION
1754 "The index of the eventEntry that is
1755 used when a rising threshold is crossed. The
1756 eventEntry identified by a particular value of
1757 this index is the same as identified by the same value
1758 of the eventIndex object. If there is no
1759 corresponding entry in the eventTable, then
1760 no association exists. In particular, if this value
1761 is zero, no associated event will be generated, as
1762 zero is not a valid event index.
1763
1764 This object may not be modified if the associated
1765 alarmStatus object is equal to valid(1)."
1766 ::= { alarmEntry 9 }
1767
1768 alarmFallingEventIndex OBJECT-TYPE
1769 SYNTAX INTEGER (0..65535)
1770 ACCESS read-write
1771 STATUS mandatory
1772 DESCRIPTION
1773 "The index of the eventEntry that is
1774 used when a falling threshold is crossed. The
1775 eventEntry identified by a particular value of
1776 this index is the same as identified by the same value
1777 of the eventIndex object. If there is no
1778 corresponding entry in the eventTable, then
1779 no association exists. In particular, if this value
1780 is zero, no associated event will be generated, as
1781 zero is not a valid event index.
1782
1783 This object may not be modified if the associated
1784 alarmStatus object is equal to valid(1)."
1785
1786
1787
1788 <span class="grey">Remote Network Monitoring Working Group [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1791
1792
1793 ::= { alarmEntry 10 }
1794
1795 alarmOwner OBJECT-TYPE
1796 SYNTAX OwnerString
1797 ACCESS read-write
1798 STATUS mandatory
1799 DESCRIPTION
1800 "The entity that configured this entry and is
1801 therefore using the resources assigned to it."
1802 ::= { alarmEntry 11 }
1803
1804 alarmStatus OBJECT-TYPE
1805 SYNTAX EntryStatus
1806 ACCESS read-write
1807 STATUS mandatory
1808 DESCRIPTION
1809 "The status of this alarm entry."
1810 ::= { alarmEntry 12 }
1811
1812
1813 -- The Host Group
1814
1815 -- Implementation of the Host group is optional.
1816 --
1817 -- The host group discovers new hosts on the network by
1818 -- keeping a list of source and destination MAC Addresses seen
1819 -- in good packets. For each of these addresses, the host
1820 -- group keeps a set of statistics. The hostControlTable
1821 -- controls which interfaces this function is performed on,
1822 -- and contains some information about the process. On
1823 -- behalf of each hostControlEntry, data is collected on an
1824 -- interface and placed both the hostTable and the
1825 -- hostTimeTable. If the monitoring device finds itself
1826 -- short of resources, it may delete entries as needed. It
1827 -- is suggested that the device delete the least recently
1828 -- used entries first.
1829
1830 -- The hostTable contains entries for each address
1831 -- discovered on a particular interface. Each entry
1832 -- contains statistical data about that host. This table
1833 -- is indexed by the MAC address of the host, through
1834 -- which a random access may be achieved.
1835
1836 -- The hostTimeTable contains data in the same format as the
1837 -- hostTable, and must contain the same set of hosts, but is
1838 -- indexed using hostTimeCreationOrder rather than hostAddress.
1839 -- The hostTimeCreationOrder is an integer which reflects
1840 -- the relative order in which a particular entry was
1841
1842
1843
1844 <span class="grey">Remote Network Monitoring Working Group [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1847
1848
1849 -- discovered and thus inserted into the table. As this
1850 -- order, and thus index, is among those entries currently
1851 -- in the table, the index for a particular entry may change
1852 -- if an (earlier) entry is deleted. Thus the association
1853 -- between hostTimeCreationOrder and hostTimeEntry may be
1854 -- broken at any time.
1855
1856 -- The hostTimeTable has two important uses. The first is the
1857 -- fast download of this potentially large table. Because the
1858 -- index of this table runs from 1 to the size of the table,
1859 -- inclusive, its values are predictable. This allows very
1860 -- efficient packing of variables into SNMP PDU's and allows
1861 -- a table transfer to have multiple packets outstanding.
1862 -- These benefits increase transfer rates tremendously.
1863
1864 -- The second use of the hostTimeTable is the efficient
1865 -- discovery by the management station of new entries added
1866 -- to the table. After the management station has
1867 -- downloaded the entire table, it knows that new entries
1868 -- will be added immediately after the end of the current
1869 -- table. It can thus detect new entries there
1870 -- and retrieve them easily.
1871
1872 -- Because the association between hostTimeCreationOrder and
1873 -- hostTimeEntry may be broken at any time, the management
1874 -- station must monitor the related hostControlLastDeleteTime
1875 -- object. When the management station thus detects a deletion,
1876 -- it must assume that any such associations have been broken,
1877 -- and invalidate any it has stored locally. This includes
1878 -- restarting any download of the hostTimeTable that may have
1879 -- been in progress, as well as rediscovering the end of the
1880 -- hostTimeTable so that it may detect new entries. If the
1881 -- management station does not detect the broken association,
1882 -- it may continue to refer to a particular host by its
1883 -- creationOrder while unwittingly retrieving the data
1884 -- associated with another host entirely. If this happens
1885 -- while downloading the host table, the management station
1886 -- may fail to download all of the entries in the table.
1887
1888
1889 hostControlTable OBJECT-TYPE
1890 SYNTAX SEQUENCE OF HostControlEntry
1891 ACCESS not-accessible
1892 STATUS mandatory
1893 DESCRIPTION
1894 "A list of host table control entries."
1895 ::= { hosts 1 }
1896
1897
1898
1899
1900 <span class="grey">Remote Network Monitoring Working Group [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1903
1904
1905 hostControlEntry OBJECT-TYPE
1906 SYNTAX HostControlEntry
1907 ACCESS not-accessible
1908 STATUS mandatory
1909 DESCRIPTION
1910 "A list of parameters that set up the discovery of
1911 hosts on a particular interface and the collection
1912 of statistics about these hosts."
1913 INDEX { hostControlIndex }
1914 ::= { hostControlTable 1 }
1915
1916 HostControlEntry ::= SEQUENCE {
1917 hostControlIndex INTEGER (1..65535),
1918 hostControlDataSource OBJECT IDENTIFIER,
1919 hostControlTableSize INTEGER,
1920 hostControlLastDeleteTime TimeTicks,
1921 hostControlOwner OwnerString,
1922 hostControlStatus INTEGER
1923 }
1924
1925 hostControlIndex OBJECT-TYPE
1926 SYNTAX INTEGER (1..65535)
1927 ACCESS read-only
1928 STATUS mandatory
1929 DESCRIPTION
1930 "An index that uniquely identifies an entry in the
1931 hostControl table. Each such entry defines
1932 a function that discovers hosts on a particular
1933 interface and places statistics about them in the
1934 hostTable and the hostTimeTable on behalf of this
1935 hostControlEntry."
1936 ::= { hostControlEntry 1 }
1937
1938 hostControlDataSource OBJECT-TYPE
1939 SYNTAX OBJECT IDENTIFIER
1940 ACCESS read-write
1941 STATUS mandatory
1942 DESCRIPTION
1943 "This object identifies the source of the data for
1944 this instance of the host function. This source
1945 can be any interface on this device. In order
1946 to identify a particular interface, this object shall
1947 identify the instance of the ifIndex object, defined
1948 in [<a href="#ref-4" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">4</a>,<a href="#ref-6" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">6</a>], for the desired interface. For example,
1949 if an entry were to receive data from interface #1,
1950 this object would be set to ifIndex.1.
1951
1952 The statistics in this group reflect all packets
1953
1954
1955
1956 <span class="grey">Remote Network Monitoring Working Group [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
1959
1960
1961 on the local network segment attached to the
1962 identified interface.
1963
1964 This object may not be modified if the associated
1965 hostControlStatus object is equal to valid(1)."
1966 ::= { hostControlEntry 2 }
1967
1968 hostControlTableSize OBJECT-TYPE
1969 SYNTAX INTEGER
1970 ACCESS read-only
1971 STATUS mandatory
1972 DESCRIPTION
1973 "The number of hostEntries in the hostTable and the
1974 hostTimeTable associated with this hostControlEntry."
1975 ::= { hostControlEntry 3 }
1976
1977 hostControlLastDeleteTime OBJECT-TYPE
1978 SYNTAX TimeTicks
1979 ACCESS read-only
1980 STATUS mandatory
1981 DESCRIPTION
1982 "The value of sysUpTime when the last entry
1983 was deleted from the portion of the hostTable
1984 associated with this hostControlEntry. If no
1985 deletions have occurred, this value shall be zero."
1986 ::= { hostControlEntry 4 }
1987
1988 hostControlOwner OBJECT-TYPE
1989 SYNTAX OwnerString
1990 ACCESS read-write
1991 STATUS mandatory
1992 DESCRIPTION
1993 "The entity that configured this entry and is
1994 therefore using the resources assigned to it."
1995 ::= { hostControlEntry 5 }
1996
1997 hostControlStatus OBJECT-TYPE
1998 SYNTAX EntryStatus
1999 ACCESS read-write
2000 STATUS mandatory
2001 DESCRIPTION
2002 "The status of this hostControl entry.
2003
2004 If this object is not equal to valid(1), all
2005 associated entries in the hostTable,
2006 hostTimeTable, and the hostTopNTable shall be
2007 deleted by the agent."
2008 ::= { hostControlEntry 6 }
2009
2010
2011
2012 <span class="grey">Remote Network Monitoring Working Group [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2015
2016
2017 hostTable OBJECT-TYPE
2018 SYNTAX SEQUENCE OF HostEntry
2019 ACCESS not-accessible
2020 STATUS mandatory
2021 DESCRIPTION
2022 "A list of host entries."
2023 ::= { hosts 2 }
2024
2025 hostEntry OBJECT-TYPE
2026 SYNTAX HostEntry
2027 ACCESS not-accessible
2028 STATUS mandatory
2029 DESCRIPTION
2030 "A collection of statistics for a particular host
2031 that has been discovered on an interface of this
2032 device."
2033 INDEX { hostIndex, hostAddress }
2034 ::= { hostTable 1 }
2035
2036 HostEntry ::= SEQUENCE {
2037 hostAddress OCTET STRING,
2038 hostCreationOrder INTEGER (1..65535),
2039 hostIndex INTEGER (1..65535),
2040 hostInPkts Counter,
2041 hostOutPkts Counter,
2042 hostInOctets Counter,
2043 hostOutOctets Counter,
2044 hostOutErrors Counter,
2045 hostOutBroadcastPkts Counter,
2046 hostOutMulticastPkts Counter
2047 }
2048
2049 hostAddress OBJECT-TYPE
2050 SYNTAX OCTET STRING
2051 ACCESS read-only
2052 STATUS mandatory
2053 DESCRIPTION
2054 "The physical address of this host."
2055 ::= { hostEntry 1 }
2056
2057 hostCreationOrder OBJECT-TYPE
2058 SYNTAX INTEGER (1..65535)
2059 ACCESS read-only
2060 STATUS mandatory
2061 DESCRIPTION
2062 "An index that defines the relative ordering of
2063 the creation time of hosts captured for a
2064 particular hostControlEntry. This index shall
2065
2066
2067
2068 <span class="grey">Remote Network Monitoring Working Group [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2071
2072
2073 be between 1 and N, where N is the value of
2074 the associated hostControlTableSize. The ordering
2075 of the indexes is based on the order of each entry's
2076 insertion into the table, in which entries added
2077 earlier have a lower index value than entries added
2078 later.
2079
2080 It is important to note that the order for a
2081 particular entry may change as an (earlier) entry
2082 is deleted from the table. Because this order may
2083 change, management stations should make use of the
2084 hostControlLastDeleteTime variable in the
2085 hostControlEntry associated with the relevant
2086 portion of the hostTable. By observing
2087 this variable, the management station may detect
2088 the circumstances where a previous association
2089 between a value of hostCreationOrder
2090 and a hostEntry may no longer hold."
2091 ::= { hostEntry 2 }
2092
2093 hostIndex OBJECT-TYPE
2094 SYNTAX INTEGER (1..65535)
2095 ACCESS read-only
2096 STATUS mandatory
2097 DESCRIPTION
2098 "The set of collected host statistics of which
2099 this entry is a part. The set of hosts
2100 identified by a particular value of this
2101 index is associated with the hostControlEntry
2102 as identified by the same value of hostControlIndex."
2103 ::= { hostEntry 3 }
2104
2105 hostInPkts OBJECT-TYPE
2106 SYNTAX Counter
2107 ACCESS read-only
2108 STATUS mandatory
2109 DESCRIPTION
2110 "The number of packets without errors transmitted to
2111 this address since it was added to the hostTable."
2112 ::= { hostEntry 4 }
2113
2114 hostOutPkts OBJECT-TYPE
2115 SYNTAX Counter
2116 ACCESS read-only
2117 STATUS mandatory
2118 DESCRIPTION
2119 "The number of packets including errors transmitted
2120 by this address since it was added to the hostTable."
2121
2122
2123
2124 <span class="grey">Remote Network Monitoring Working Group [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2127
2128
2129 ::= { hostEntry 5 }
2130
2131 hostInOctets OBJECT-TYPE
2132 SYNTAX Counter
2133 ACCESS read-only
2134 STATUS mandatory
2135 DESCRIPTION
2136 "The number of octets transmitted to this address
2137 since it was added to the hostTable (excluding
2138 framing bits but including FCS octets), except for
2139 those octets in packets that contained errors."
2140 ::= { hostEntry 6 }
2141
2142 hostOutOctets OBJECT-TYPE
2143 SYNTAX Counter
2144 ACCESS read-only
2145 STATUS mandatory
2146 DESCRIPTION
2147 "The number of octets transmitted by this address
2148 since it was added to the hostTable (excluding
2149 framing bits but including FCS octets), including
2150 those octets in packets that contained errors."
2151 ::= { hostEntry 7 }
2152
2153 hostOutErrors OBJECT-TYPE
2154 SYNTAX Counter
2155 ACCESS read-only
2156 STATUS mandatory
2157 DESCRIPTION
2158 "The number of error packets transmitted by this
2159 address since this host was added to the hostTable."
2160 ::= { hostEntry 8 }
2161
2162 hostOutBroadcastPkts OBJECT-TYPE
2163 SYNTAX Counter
2164 ACCESS read-only
2165 STATUS mandatory
2166 DESCRIPTION
2167 "The number of good packets transmitted by this
2168 address that were directed to the broadcast address
2169 since this host was added to the hostTable."
2170 ::= { hostEntry 9 }
2171
2172 hostOutMulticastPkts OBJECT-TYPE
2173 SYNTAX Counter
2174 ACCESS read-only
2175 STATUS mandatory
2176 DESCRIPTION
2177
2178
2179
2180 <span class="grey">Remote Network Monitoring Working Group [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2183
2184
2185 "The number of good packets transmitted by this
2186 address that were directed to a multicast address
2187 since this host was added to the hostTable.
2188 Note that this number does not include packets
2189 directed to the broadcast address."
2190 ::= { hostEntry 10 }
2191
2192
2193 -- host Time Table
2194
2195 hostTimeTable OBJECT-TYPE
2196 SYNTAX SEQUENCE OF HostTimeEntry
2197 ACCESS not-accessible
2198 STATUS mandatory
2199 DESCRIPTION
2200 "A list of time-ordered host table entries."
2201 ::= { hosts 3 }
2202
2203 hostTimeEntry OBJECT-TYPE
2204 SYNTAX HostTimeEntry
2205 ACCESS not-accessible
2206 STATUS mandatory
2207 DESCRIPTION
2208 "A collection of statistics for a particular host
2209 that has been discovered on an interface of this
2210 device. This collection includes the relative
2211 ordering of the creation time of this object."
2212 INDEX { hostTimeIndex, hostTimeCreationOrder }
2213 ::= { hostTimeTable 1 }
2214
2215 HostTimeEntry ::= SEQUENCE {
2216 hostTimeAddress OCTET STRING,
2217 hostTimeCreationOrder INTEGER (1..65535),
2218 hostTimeIndex INTEGER (1..65535),
2219 hostTimeInPkts Counter,
2220 hostTimeOutPkts Counter,
2221 hostTimeInOctets Counter,
2222 hostTimeOutOctets Counter,
2223 hostTimeOutErrors Counter,
2224 hostTimeOutBroadcastPkts Counter,
2225 hostTimeOutMulticastPkts Counter
2226 }
2227
2228 hostTimeAddress OBJECT-TYPE
2229 SYNTAX OCTET STRING
2230 ACCESS read-only
2231 STATUS mandatory
2232 DESCRIPTION
2233
2234
2235
2236 <span class="grey">Remote Network Monitoring Working Group [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2239
2240
2241 "The physical address of this host."
2242 ::= { hostTimeEntry 1 }
2243
2244 hostTimeCreationOrder OBJECT-TYPE
2245 SYNTAX INTEGER (1..65535)
2246 ACCESS read-only
2247 STATUS mandatory
2248 DESCRIPTION
2249 "An index that uniquely identifies an entry in
2250 the hostTime table among those entries associated
2251 with the same hostControlEntry. This index shall
2252 be between 1 and N, where N is the value of
2253 the associated hostControlTableSize. The ordering
2254 of the indexes is based on the order of each entry's
2255 insertion into the table, in which entries added
2256 earlier have a lower index value than entries added
2257 later. Thus the management station has the ability
2258 to learn of new entries added to this table without
2259 downloading the entire table.
2260
2261 It is important to note that the index for a
2262 particular entry may change as an (earlier) entry
2263 is deleted from the table. Because this order may
2264 change, management stations should make use of the
2265 hostControlLastDeleteTime variable in the
2266 hostControlEntry associated with the relevant
2267 portion of the hostTimeTable. By observing
2268 this variable, the management station may detect
2269 the circumstances where a download of the table
2270 may have missed entries, and where a previous
2271 association between a value of hostTimeCreationOrder
2272 and a hostTimeEntry may no longer hold."
2273 ::= { hostTimeEntry 2 }
2274
2275 hostTimeIndex OBJECT-TYPE
2276 SYNTAX INTEGER (1..65535)
2277 ACCESS read-only
2278 STATUS mandatory
2279 DESCRIPTION
2280 "The set of collected host statistics of which
2281 this entry is a part. The set of hosts
2282 identified by a particular value of this
2283 index is associated with the hostControlEntry
2284 as identified by the same value of hostControlIndex."
2285 ::= { hostTimeEntry 3 }
2286
2287
2288
2289
2290
2291
2292 <span class="grey">Remote Network Monitoring Working Group [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2295
2296
2297 hostTimeInPkts OBJECT-TYPE
2298 SYNTAX Counter
2299 ACCESS read-only
2300 STATUS mandatory
2301 DESCRIPTION
2302 "The number of packets without errors transmitted to
2303 this address since it was added to the hostTimeTable."
2304 ::= { hostTimeEntry 4 }
2305
2306 hostTimeOutPkts OBJECT-TYPE
2307 SYNTAX Counter
2308 ACCESS read-only
2309 STATUS mandatory
2310 DESCRIPTION
2311 "The number of packets including errors transmitted
2312 by this address since it was added to the
2313 hostTimeTable."
2314 ::= { hostTimeEntry 5 }
2315
2316 hostTimeInOctets OBJECT-TYPE
2317 SYNTAX Counter
2318 ACCESS read-only
2319 STATUS mandatory
2320 DESCRIPTION
2321 "The number of octets transmitted to this address
2322 since it was added to the hostTimeTable (excluding
2323 framing bits but including FCS octets), except for
2324 those octets in packets that contained errors."
2325 ::= { hostTimeEntry 6 }
2326
2327 hostTimeOutOctets OBJECT-TYPE
2328 SYNTAX Counter
2329 ACCESS read-only
2330 STATUS mandatory
2331 DESCRIPTION
2332 "The number of octets transmitted by this address since
2333 it was added to the hostTimeTable (excluding framing
2334 bits but including FCS octets), including those
2335 octets in packets that contained errors."
2336 ::= { hostTimeEntry 7 }
2337
2338 hostTimeOutErrors OBJECT-TYPE
2339 SYNTAX Counter
2340 ACCESS read-only
2341 STATUS mandatory
2342 DESCRIPTION
2343 "The number of error packets transmitted by this
2344 address since this host was added to the
2345
2346
2347
2348 <span class="grey">Remote Network Monitoring Working Group [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2351
2352
2353 hostTimeTable."
2354 ::= { hostTimeEntry 8 }
2355
2356 hostTimeOutBroadcastPkts OBJECT-TYPE
2357 SYNTAX Counter
2358 ACCESS read-only
2359 STATUS mandatory
2360 DESCRIPTION
2361 "The number of good packets transmitted by this
2362 address that were directed to the broadcast address
2363 since this host was added to the hostTimeTable."
2364 ::= { hostTimeEntry 9 }
2365
2366 hostTimeOutMulticastPkts OBJECT-TYPE
2367 SYNTAX Counter
2368 ACCESS read-only
2369 STATUS mandatory
2370 DESCRIPTION
2371 "The number of good packets transmitted by this
2372 address that were directed to a multicast address
2373 since this host was added to the hostTimeTable.
2374 Note that this number does not include packets
2375 directed to the broadcast address."
2376 ::= { hostTimeEntry 10 }
2377
2378
2379 -- The Host Top "N" Group
2380
2381 -- Implementation of the Host Top N group is optional.
2382 --
2383 -- The Host Top N group requires the implementation of the
2384 -- host group.
2385 --
2386 -- The Host Top N group is used to prepare reports that
2387 -- describe the hosts that top a list ordered by one of
2388 -- their statistics. The available statistics are samples
2389 -- of one of their base statistics, over an interval
2390 -- specified by the management station. Thus, these
2391 -- statistics are rate based. The management
2392 -- station also selects how many such hosts are reported.
2393
2394 -- The hostTopNControlTable is used to initiate the generation
2395 -- of such a report. The management station may select the
2396 -- parameters of such a report, such as which interface,
2397 -- which statistic, how many hosts, and the start and stop
2398 -- times of the sampling. When the report is prepared,
2399 -- entries are created in the hostTopNTable associated with
2400 -- the relevant hostTopNControlEntry. These entries are
2401
2402
2403
2404 <span class="grey">Remote Network Monitoring Working Group [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2407
2408
2409 -- static for each report after it has been prepared.
2410
2411 hostTopNControlTable OBJECT-TYPE
2412 SYNTAX SEQUENCE OF HostTopNControlEntry
2413 ACCESS not-accessible
2414 STATUS mandatory
2415 DESCRIPTION
2416 "A list of top N host control entries."
2417 ::= { hostTopN 1 }
2418
2419 hostTopNControlEntry OBJECT-TYPE
2420 SYNTAX HostTopNControlEntry
2421 ACCESS not-accessible
2422 STATUS mandatory
2423 DESCRIPTION
2424 "A set of parameters that control the creation of a
2425 report of the top N hosts according to several
2426 metrics."
2427 INDEX { hostTopNControlIndex }
2428 ::= { hostTopNControlTable 1 }
2429
2430 HostTopNControlEntry ::= SEQUENCE {
2431 hostTopNControlIndex INTEGER (1..65535),
2432 hostTopNHostIndex INTEGER (1..65535),
2433 hostTopNRateBase INTEGER,
2434 hostTopNTimeRemaining INTEGER,
2435 hostTopNDuration INTEGER,
2436 hostTopNRequestedSize INTEGER,
2437 hostTopNGrantedSize INTEGER,
2438 hostTopNStartTime TimeTicks,
2439 hostTopNOwner OwnerString,
2440 hostTopNStatus INTEGER
2441 }
2442
2443 hostTopNControlIndex OBJECT-TYPE
2444 SYNTAX INTEGER (1..65535)
2445 ACCESS read-only
2446 STATUS mandatory
2447 DESCRIPTION
2448 "An index that uniquely identifies an entry
2449 in the hostTopNControl table. Each such
2450 entry defines one top N report prepared for
2451 one interface."
2452 ::= { hostTopNControlEntry 1 }
2453
2454 hostTopNHostIndex OBJECT-TYPE
2455 SYNTAX INTEGER (1..65535)
2456 ACCESS read-write
2457
2458
2459
2460 <span class="grey">Remote Network Monitoring Working Group [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2463
2464
2465 STATUS mandatory
2466 DESCRIPTION
2467 "The host table for which a top N report will be
2468 prepared on behalf of this entry. The host table
2469 identified by a particular value of this index is
2470 associated with the same host table as identified
2471 by the same value of hostIndex.
2472
2473 This object may not be modified if the associated
2474 hostTopNStatus object is equal to valid(1)."
2475 ::= { hostTopNControlEntry 2 }
2476
2477 hostTopNRateBase OBJECT-TYPE
2478 SYNTAX INTEGER {
2479 hostTopNInPkts(1),
2480 hostTopNOutPkts(2),
2481 hostTopNInOctets(3),
2482 hostTopNOutOctets(4),
2483 hostTopNOutErrors(5),
2484 hostTopNOutBroadcastPkts(6),
2485 hostTopNOutMulticastPkts(7)
2486 }
2487 ACCESS read-write
2488 STATUS mandatory
2489 DESCRIPTION
2490 "The variable for each host that the hostTopNRate
2491 variable is based upon.
2492
2493 This object may not be modified if the associated
2494 hostTopNStatus object is equal to valid(1)."
2495 ::= { hostTopNControlEntry 3 }
2496
2497 hostTopNTimeRemaining OBJECT-TYPE
2498 SYNTAX INTEGER
2499 ACCESS read-write
2500 STATUS mandatory
2501 DESCRIPTION
2502 "The number of seconds left in the report currently
2503 being collected. When this object is modified by
2504 the management station, a new collection is started,
2505 possibly aborting a currently running report. The
2506 new value is used as the requested duration of this
2507 report, which is loaded into the associated
2508 hostTopNDuration object.
2509
2510 When this object is set to a non-zero value, any
2511 associated hostTopNEntries shall be made
2512 inaccessible by the monitor. While the value of this
2513
2514
2515
2516 <span class="grey">Remote Network Monitoring Working Group [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2519
2520
2521 object is non-zero, it decrements by one per second
2522 until it reaches zero. During this time, all
2523 associated hostTopNEntries shall remain
2524 inaccessible. At the time that this object
2525 decrements to zero, the report is made
2526 accessible in the hostTopNTable. Thus, the hostTopN
2527 table needs to be created only at the end of the
2528 collection interval."
2529 DEFVAL { 0 }
2530 ::= { hostTopNControlEntry 4 }
2531
2532 hostTopNDuration OBJECT-TYPE
2533 SYNTAX INTEGER
2534 ACCESS read-only
2535 STATUS mandatory
2536 DESCRIPTION
2537 "The number of seconds that this report has collected
2538 during the last sampling interval, or if this
2539 report is currently being collected, the number
2540 of seconds that this report is being collected
2541 during this sampling interval.
2542
2543 When the associated hostTopNTimeRemaining object is
2544 set, this object shall be set by the probe to the
2545 same value and shall not be modified until the next
2546 time the hostTopNTimeRemaining is set.
2547
2548 This value shall be zero if no reports have been
2549 requested for this hostTopNControlEntry."
2550 DEFVAL { 0 }
2551 ::= { hostTopNControlEntry 5 }
2552
2553 hostTopNRequestedSize OBJECT-TYPE
2554 SYNTAX INTEGER
2555 ACCESS read-write
2556 STATUS mandatory
2557 DESCRIPTION
2558 "The maximum number of hosts requested for the top N
2559 table.
2560
2561 When this object is created or modified, the probe
2562 should set hostTopNGrantedSize as closely to this
2563 object as is possible for the particular probe
2564 implementation and available resources."
2565 DEFVAL { 10 }
2566 ::= { hostTopNControlEntry 6 }
2567
2568
2569
2570
2571
2572 <span class="grey">Remote Network Monitoring Working Group [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2575
2576
2577 hostTopNGrantedSize OBJECT-TYPE
2578 SYNTAX INTEGER
2579 ACCESS read-only
2580 STATUS mandatory
2581 DESCRIPTION
2582 "The maximum number of hosts in the top N table.
2583
2584 When the associated hostTopNRequestedSize object is
2585 created or modified, the probe should set this
2586 object as closely to the requested value as is
2587 possible for the particular implementation and
2588 available resources. The probe must not lower this
2589 value except as a result of a set to the associated
2590 hostTopNRequestedSize object.
2591
2592 Hosts with the highest value of hostTopNRate shall be
2593 placed in this table in decreasing order of this rate
2594 until there is no more room or until there are no more
2595 hosts."
2596 ::= { hostTopNControlEntry 7 }
2597
2598 hostTopNStartTime OBJECT-TYPE
2599 SYNTAX TimeTicks
2600 ACCESS read-only
2601 STATUS mandatory
2602 DESCRIPTION
2603 "The value of sysUpTime when this top N report was
2604 last started. In other words, this is the time that
2605 the associated hostTopNTimeRemaining object was
2606 modified to start the requested report."
2607 ::= { hostTopNControlEntry 8 }
2608
2609 hostTopNOwner OBJECT-TYPE
2610 SYNTAX OwnerString
2611 ACCESS read-write
2612 STATUS mandatory
2613 DESCRIPTION
2614 "The entity that configured this entry and is
2615 therefore using the resources assigned to it."
2616 ::= { hostTopNControlEntry 9 }
2617
2618 hostTopNStatus OBJECT-TYPE
2619 SYNTAX EntryStatus
2620 ACCESS read-write
2621 STATUS mandatory
2622 DESCRIPTION
2623 "The status of this hostTopNControl entry.
2624
2625
2626
2627
2628 <span class="grey">Remote Network Monitoring Working Group [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2631
2632
2633 If this object is not equal to valid(1), all
2634 associated hostTopNEntries shall be deleted by
2635 the agent."
2636 ::= { hostTopNControlEntry 10 }
2637
2638 hostTopNTable OBJECT-TYPE
2639 SYNTAX SEQUENCE OF HostTopNEntry
2640 ACCESS not-accessible
2641 STATUS mandatory
2642 DESCRIPTION
2643 "A list of top N host entries."
2644 ::= { hostTopN 2 }
2645
2646 hostTopNEntry OBJECT-TYPE
2647 SYNTAX HostTopNEntry
2648 ACCESS not-accessible
2649 STATUS mandatory
2650 DESCRIPTION
2651 "A set of statistics for a host that is part of a
2652 top N report."
2653 INDEX { hostTopNReport, hostTopNIndex }
2654 ::= { hostTopNTable 1 }
2655
2656 HostTopNEntry ::= SEQUENCE {
2657 hostTopNReport INTEGER (1..65535),
2658 hostTopNIndex INTEGER (1..65535),
2659 hostTopNAddress OCTET STRING,
2660 hostTopNRate INTEGER
2661 }
2662
2663 hostTopNReport OBJECT-TYPE
2664 SYNTAX INTEGER (1..65535)
2665 ACCESS read-only
2666 STATUS mandatory
2667 DESCRIPTION
2668 "This object identifies the top N report of which
2669 this entry is a part. The set of hosts
2670 identified by a particular value of this
2671 object is part of the same report as identified
2672 by the same value of the hostTopNControlIndex object."
2673 ::= { hostTopNEntry 1 }
2674
2675 hostTopNIndex OBJECT-TYPE
2676 SYNTAX INTEGER (1..65535)
2677 ACCESS read-only
2678 STATUS mandatory
2679 DESCRIPTION
2680 "An index that uniquely identifies an entry in
2681
2682
2683
2684 <span class="grey">Remote Network Monitoring Working Group [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2687
2688
2689 the hostTopN table among those in the same report.
2690 This index is between 1 and N, where N is the
2691 number of entries in this table. Increasing values
2692 of hostTopNIndex shall be assigned to entries with
2693 decreasing values of hostTopNRate until index N
2694 is assigned to the entry with the lowest value of
2695 hostTopNRate or there are no more hostTopNEntries."
2696 ::= { hostTopNEntry 2 }
2697
2698 hostTopNAddress OBJECT-TYPE
2699 SYNTAX OCTET STRING
2700 ACCESS read-only
2701 STATUS mandatory
2702 DESCRIPTION
2703 "The physical address of this host."
2704 ::= { hostTopNEntry 3 }
2705
2706 hostTopNRate OBJECT-TYPE
2707 SYNTAX INTEGER
2708 ACCESS read-only
2709 STATUS mandatory
2710 DESCRIPTION
2711 "The amount of change in the selected variable
2712 during this sampling interval. The selected
2713 variable is this host's instance of the object
2714 selected by hostTopNRateBase."
2715 ::= { hostTopNEntry 4 }
2716
2717
2718 -- The Matrix Group
2719
2720 -- Implementation of the Matrix group is optional.
2721 --
2722 -- The Matrix group consists of the matrixControlTable,
2723 -- matrixSDTable and the matrixDSTable. These tables
2724 -- store statistics for a particular conversation between
2725 -- two addresses. As the device detects a new conversation,
2726 -- including those to a non-unicast address, it creates a
2727 -- new entry in both of the matrix tables.
2728 -- It must only create new entries based on information
2729 -- received in good packets. If the monitoring device finds
2730 -- itself short of resources, it may delete entries as needed.
2731 -- It is suggested that the device delete the least recently
2732 -- used entries first.
2733
2734 matrixControlTable OBJECT-TYPE
2735 SYNTAX SEQUENCE OF MatrixControlEntry
2736 ACCESS not-accessible
2737
2738
2739
2740 <span class="grey">Remote Network Monitoring Working Group [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2743
2744
2745 STATUS mandatory
2746 DESCRIPTION
2747 "A list of information entries for the
2748 traffic matrix on each interface."
2749 ::= { matrix 1 }
2750
2751 matrixControlEntry OBJECT-TYPE
2752 SYNTAX MatrixControlEntry
2753 ACCESS not-accessible
2754 STATUS mandatory
2755 DESCRIPTION
2756 "Information about a traffic matrix on a
2757 particular interface."
2758 INDEX { matrixControlIndex }
2759 ::= { matrixControlTable 1 }
2760
2761 MatrixControlEntry ::= SEQUENCE {
2762 matrixControlIndex INTEGER (1..65535),
2763 matrixControlDataSource OBJECT IDENTIFIER,
2764 matrixControlTableSize INTEGER,
2765 matrixControlLastDeleteTime TimeTicks,
2766 matrixControlOwner OwnerString,
2767 matrixControlStatus INTEGER
2768 }
2769
2770 matrixControlIndex OBJECT-TYPE
2771 SYNTAX INTEGER (1..65535)
2772 ACCESS read-only
2773 STATUS mandatory
2774 DESCRIPTION
2775 "An index that uniquely identifies an entry in the
2776 matrixControl table. Each such entry defines
2777 a function that discovers conversations on a particular
2778 interface and places statistics about them in the
2779 matrixSDTable and the matrixDSTable on behalf of this
2780 matrixControlEntry."
2781 ::= { matrixControlEntry 1 }
2782
2783 matrixControlDataSource OBJECT-TYPE
2784 SYNTAX OBJECT IDENTIFIER
2785 ACCESS read-write
2786 STATUS mandatory
2787 DESCRIPTION
2788 "This object identifies the source of
2789 the data from which this entry creates a traffic matrix.
2790 This source can be any interface on this device. In
2791 order to identify a particular interface, this object
2792 shall identify the instance of the ifIndex object,
2793
2794
2795
2796 <span class="grey">Remote Network Monitoring Working Group [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2799
2800
2801 defined in [<a href="#ref-4" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">4</a>,<a href="#ref-6" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">6</a>], for the desired interface. For
2802 example, if an entry were to receive data from
2803 interface #1, this object would be set to ifIndex.1.
2804
2805 The statistics in this group reflect all packets
2806 on the local network segment attached to the
2807 identified interface.
2808
2809 This object may not be modified if the associated
2810 matrixControlStatus object is equal to valid(1)."
2811 ::= { matrixControlEntry 2 }
2812
2813 matrixControlTableSize OBJECT-TYPE
2814 SYNTAX INTEGER
2815 ACCESS read-only
2816 STATUS mandatory
2817 DESCRIPTION
2818 "The number of matrixSDEntries in the matrixSDTable
2819 for this interface. This must also be the value of
2820 the number of entries in the matrixDSTable for this
2821 interface."
2822 ::= { matrixControlEntry 3 }
2823
2824 matrixControlLastDeleteTime OBJECT-TYPE
2825 SYNTAX TimeTicks
2826 ACCESS read-only
2827 STATUS mandatory
2828 DESCRIPTION
2829 "The value of sysUpTime when the last entry
2830 was deleted from the portion of the matrixSDTable
2831 or matrixDSTable associated with this
2832 matrixControlEntry.
2833 If no deletions have occurred, this value shall be
2834 zero."
2835 ::= { matrixControlEntry 4 }
2836
2837 matrixControlOwner OBJECT-TYPE
2838 SYNTAX OwnerString
2839 ACCESS read-write
2840 STATUS mandatory
2841 DESCRIPTION
2842 "The entity that configured this entry and is
2843 therefore using the resources assigned to it."
2844 ::= { matrixControlEntry 5 }
2845
2846 matrixControlStatus OBJECT-TYPE
2847 SYNTAX EntryStatus
2848 ACCESS read-write
2849
2850
2851
2852 <span class="grey">Remote Network Monitoring Working Group [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2855
2856
2857 STATUS mandatory
2858 DESCRIPTION
2859 "The status of this matrixControl entry.
2860
2861 If this object is not equal to valid(1), all
2862 associated entries in the matrixSDTable and the
2863 matrixDSTable shall be deleted by the agent."
2864 ::= { matrixControlEntry 6 }
2865
2866 matrixSDTable OBJECT-TYPE
2867 SYNTAX SEQUENCE OF MatrixSDEntry
2868 ACCESS not-accessible
2869 STATUS mandatory
2870 DESCRIPTION
2871 "A list of traffic matrix entries indexed by
2872 source and destination MAC address."
2873 ::= { matrix 2 }
2874
2875 matrixSDEntry OBJECT-TYPE
2876 SYNTAX MatrixSDEntry
2877 ACCESS not-accessible
2878 STATUS mandatory
2879 DESCRIPTION
2880 "A collection of statistics for communications between
2881 two addresses on a particular interface."
2882 INDEX { matrixSDIndex,
2883 matrixSDSourceAddress, matrixSDDestAddress }
2884 ::= { matrixSDTable 1 }
2885
2886 MatrixSDEntry ::= SEQUENCE {
2887 matrixSDSourceAddress OCTET STRING,
2888 matrixSDDestAddress OCTET STRING,
2889 matrixSDIndex INTEGER (1..65535),
2890 matrixSDPkts Counter,
2891 matrixSDOctets Counter,
2892 matrixSDErrors Counter
2893 }
2894
2895 matrixSDSourceAddress OBJECT-TYPE
2896 SYNTAX OCTET STRING
2897 ACCESS read-only
2898 STATUS mandatory
2899 DESCRIPTION
2900 "The source physical address."
2901 ::= { matrixSDEntry 1 }
2902
2903
2904
2905
2906
2907
2908 <span class="grey">Remote Network Monitoring Working Group [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2911
2912
2913 matrixSDDestAddress OBJECT-TYPE
2914 SYNTAX OCTET STRING
2915 ACCESS read-only
2916 STATUS mandatory
2917 DESCRIPTION
2918 "The destination physical address."
2919 ::= { matrixSDEntry 2 }
2920
2921 matrixSDIndex OBJECT-TYPE
2922 SYNTAX INTEGER (1..65535)
2923 ACCESS read-only
2924 STATUS mandatory
2925 DESCRIPTION
2926 "The set of collected matrix statistics of which
2927 this entry is a part. The set of matrix statistics
2928 identified by a particular value of this index
2929 is associated with the same matrixControlEntry
2930 as identified by the same value of matrixControlIndex."
2931 ::= { matrixSDEntry 3 }
2932
2933 matrixSDPkts OBJECT-TYPE
2934 SYNTAX Counter
2935 ACCESS read-only
2936 STATUS mandatory
2937 DESCRIPTION
2938 "The number of packets transmitted from the source
2939 address to the destination address (this number
2940 includes error packets)."
2941 ::= { matrixSDEntry 4 }
2942
2943 matrixSDOctets OBJECT-TYPE
2944 SYNTAX Counter
2945 ACCESS read-only
2946 STATUS mandatory
2947 DESCRIPTION
2948 "The number of octets (excluding framing bits but
2949 including FCS octets) contained in all packets
2950 transmitted from the source address to the
2951 destination address."
2952 ::= { matrixSDEntry 5 }
2953
2954 matrixSDErrors OBJECT-TYPE
2955 SYNTAX Counter
2956 ACCESS read-only
2957 STATUS mandatory
2958 DESCRIPTION
2959 "The number of error packets transmitted from
2960 the source address to the destination address."
2961
2962
2963
2964 <span class="grey">Remote Network Monitoring Working Group [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
2967
2968
2969 ::= { matrixSDEntry 6 }
2970
2971
2972 -- Traffic matrix tables from destination to source
2973
2974 matrixDSTable OBJECT-TYPE
2975 SYNTAX SEQUENCE OF MatrixDSEntry
2976 ACCESS not-accessible
2977 STATUS mandatory
2978 DESCRIPTION
2979 "A list of traffic matrix entries indexed by
2980 destination and source MAC address."
2981 ::= { matrix 3 }
2982
2983 matrixDSEntry OBJECT-TYPE
2984 SYNTAX MatrixDSEntry
2985 ACCESS not-accessible
2986 STATUS mandatory
2987 DESCRIPTION
2988 "A collection of statistics for communications between
2989 two address on a particular interface."
2990 INDEX { matrixDSIndex,
2991 matrixDSDestAddress, matrixDSSourceAddress }
2992 ::= { matrixDSTable 1 }
2993
2994 MatrixDSEntry ::= SEQUENCE {
2995 matrixDSSourceAddress OCTET STRING,
2996 matrixDSDestAddress OCTET STRING,
2997 matrixDSIndex INTEGER (1..65535),
2998 matrixDSPkts Counter,
2999 matrixDSOctets Counter,
3000 matrixDSErrors Counter
3001 }
3002
3003 matrixDSSourceAddress OBJECT-TYPE
3004 SYNTAX OCTET STRING
3005 ACCESS read-only
3006 STATUS mandatory
3007 DESCRIPTION
3008 "The source physical address."
3009 ::= { matrixDSEntry 1 }
3010
3011 matrixDSDestAddress OBJECT-TYPE
3012 SYNTAX OCTET STRING
3013 ACCESS read-only
3014 STATUS mandatory
3015 DESCRIPTION
3016 "The destination physical address."
3017
3018
3019
3020 <span class="grey">Remote Network Monitoring Working Group [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3023
3024
3025 ::= { matrixDSEntry 2 }
3026
3027 matrixDSIndex OBJECT-TYPE
3028 SYNTAX INTEGER (1..65535)
3029 ACCESS read-only
3030 STATUS mandatory
3031 DESCRIPTION
3032 "The set of collected matrix statistics of which
3033 this entry is a part. The set of matrix statistics
3034 identified by a particular value of this index
3035 is associated with the same matrixControlEntry
3036 as identified by the same value of matrixControlIndex."
3037 ::= { matrixDSEntry 3 }
3038
3039 matrixDSPkts OBJECT-TYPE
3040 SYNTAX Counter
3041 ACCESS read-only
3042 STATUS mandatory
3043 DESCRIPTION
3044 "The number of packets transmitted from the source
3045 address to the destination address (this number
3046 includes error packets)."
3047 ::= { matrixDSEntry 4 }
3048
3049 matrixDSOctets OBJECT-TYPE
3050 SYNTAX Counter
3051 ACCESS read-only
3052 STATUS mandatory
3053 DESCRIPTION
3054 "The number of octets (excluding framing bits
3055 but including FCS octets) contained in all packets
3056 transmitted from the source address to the
3057 destination address."
3058 ::= { matrixDSEntry 5 }
3059
3060 matrixDSErrors OBJECT-TYPE
3061 SYNTAX Counter
3062 ACCESS read-only
3063 STATUS mandatory
3064 DESCRIPTION
3065 "The number of error packets transmitted from
3066 the source address to the destination address."
3067 ::= { matrixDSEntry 6 }
3068
3069
3070 -- The Filter Group
3071
3072 -- Implementation of the Filter group is optional.
3073
3074
3075
3076 <span class="grey">Remote Network Monitoring Working Group [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3079
3080
3081 --
3082 -- The Filter group allows packets to be captured with an
3083 -- arbitrary filter expression. A logical data and
3084 -- event stream or "channel" is formed by the packets
3085 -- that match the filter expression.
3086 --
3087 -- This filter mechanism allows the creation of an arbitrary
3088 -- logical expression with which to filter packets. Each
3089 -- filter associated with a channel is OR'ed with the others.
3090 -- Within a filter, any bits checked in the data and status are
3091 -- AND'ed with respect to other bits in the same filter. The
3092 -- NotMask also allows for checking for inequality. Finally,
3093 -- the channelAcceptType object allows for inversion of the
3094 -- whole equation.
3095 --
3096 -- The channel can be turned on or off, and can also
3097 -- generate events when packets pass through it.
3098
3099 filterTable OBJECT-TYPE
3100 SYNTAX SEQUENCE OF FilterEntry
3101 ACCESS not-accessible
3102 STATUS mandatory
3103 DESCRIPTION
3104 "A list of packet filter entries."
3105 ::= { filter 1 }
3106
3107 filterEntry OBJECT-TYPE
3108 SYNTAX FilterEntry
3109 ACCESS not-accessible
3110 STATUS mandatory
3111 DESCRIPTION
3112 "A set of parameters for a packet filter applied on a
3113 particular interface."
3114 INDEX { filterIndex }
3115 ::= { filterTable 1 }
3116
3117 FilterEntry ::= SEQUENCE {
3118 filterIndex INTEGER (1..65535),
3119 filterChannelIndex INTEGER (1..65535),
3120 filterPktDataOffset INTEGER,
3121 filterPktData OCTET STRING,
3122 filterPktDataMask OCTET STRING,
3123 filterPktDataNotMask OCTET STRING,
3124 filterPktStatus INTEGER,
3125 filterPktStatusMask INTEGER,
3126 filterPktStatusNotMask INTEGER,
3127 filterOwner OwnerString,
3128 filterStatus INTEGER
3129
3130
3131
3132 <span class="grey">Remote Network Monitoring Working Group [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3135
3136
3137 }
3138
3139 filterIndex OBJECT-TYPE
3140 SYNTAX INTEGER (1..65535)
3141 ACCESS read-only
3142 STATUS mandatory
3143 DESCRIPTION
3144 "An index that uniquely identifies an entry
3145 in the filter table. Each such entry defines
3146 one filter that is to be applied to every packet
3147 received on an interface."
3148 ::= { filterEntry 1 }
3149
3150 filterChannelIndex OBJECT-TYPE
3151 SYNTAX INTEGER (1..65535)
3152 ACCESS read-write
3153 STATUS mandatory
3154 DESCRIPTION
3155 "This object identifies the channel of which this
3156 filter is a part. The filters identified by a
3157 particular value of this object are associated
3158 with the same channel as identified by the same
3159 value of the channelIndex object."
3160 ::= { filterEntry 2 }
3161
3162 filterPktDataOffset OBJECT-TYPE
3163 SYNTAX INTEGER
3164 ACCESS read-write
3165 STATUS mandatory
3166 DESCRIPTION
3167 "The offset from the beginning of each packet where
3168 a match of packet data will be attempted. This offset
3169 is measured from the point in the physical layer
3170 packet after the framing bits, if any. For example,
3171 in an Ethernet frame, this point is at the beginning
3172 of the destination MAC address.
3173
3174 This object may not be modified if the associated
3175 filterStatus object is equal to valid(1)."
3176 DEFVAL { 0 }
3177 ::= { filterEntry 3 }
3178
3179 filterPktData OBJECT-TYPE
3180 SYNTAX OCTET STRING
3181 ACCESS read-write
3182 STATUS mandatory
3183 DESCRIPTION
3184 "The data that is to be matched with the input packet.
3185
3186
3187
3188 <span class="grey">Remote Network Monitoring Working Group [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3191
3192
3193 For each packet received, this filter and the
3194 accompanying filterPktDataMask and
3195 filterPktDataNotMask will be adjusted for the
3196 offset. The only bits relevant to this
3197 match algorithm are those that have the corresponding
3198 filterPktDataMask bit equal to one. The following
3199 three rules are then applied to every packet:
3200
3201 (1) If the packet is too short and does not have data
3202 corresponding to part of the filterPktData, the
3203 packet will fail this data match.
3204
3205 (2) For each relevant bit from the packet with the
3206 corresponding filterPktDataNotMask bit set to
3207 zero, if the bit from the packet is not equal to
3208 the corresponding bit from the filterPktData,
3209 then the packet will fail this data match.
3210
3211 (3) If for every relevant bit from the packet with the
3212 corresponding filterPktDataNotMask bit set to one,
3213 the bit from the packet is equal to the
3214 corresponding bit from the filterPktData, then
3215 the packet will fail this data match.
3216
3217 Any packets that have not failed any of the three
3218 matches above have passed this data match.
3219
3220 This object may not be modified if the associated
3221 filterStatus object is equal to valid(1)."
3222 ::= { filterEntry 4 }
3223
3224 filterPktDataMask OBJECT-TYPE
3225 SYNTAX OCTET STRING
3226 ACCESS read-write
3227 STATUS mandatory
3228 DESCRIPTION
3229 "The mask that is applied to the match process.
3230 After adjusting this mask for the offset, only those
3231 bits in the received packet that correspond to bits
3232 set in this mask are relevant for further processing
3233 by the match algorithm. The offset is applied to
3234 filterPktDataMask in the same way it is applied to
3235 the filter. For the purposes of the matching
3236 algorithm, if the associated filterPktData object
3237 is longer than this mask, this mask is conceptually
3238 extended with '1' bits until it reaches the
3239 length of the filterPktData object.
3240
3241
3242
3243
3244 <span class="grey">Remote Network Monitoring Working Group [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3247
3248
3249 This object may not be modified if the associated
3250 filterStatus object is equal to valid(1)."
3251 ::= { filterEntry 5 }
3252
3253 filterPktDataNotMask OBJECT-TYPE
3254 SYNTAX OCTET STRING
3255 ACCESS read-write
3256 STATUS mandatory
3257 DESCRIPTION
3258 "The inversion mask that is applied to the match
3259 process. After adjusting this mask for the offset,
3260 those relevant bits in the received packet that
3261 correspond to bits cleared in this mask must all
3262 be equal to their corresponding bits in the
3263 filterPktData object for the packet to be accepted.
3264 In addition, at least one of those relevant
3265 bits in the received packet that correspond to bits
3266 set in this mask must be different to its
3267 corresponding bit in the filterPktData object.
3268
3269 For the purposes of the matching algorithm, if
3270 the associated filterPktData object is longer than
3271 this mask, this mask is conceptually extended with
3272 '0' bits until it reaches the length of the
3273 filterPktData object.
3274
3275 This object may not be modified if the associated
3276 filterStatus object is equal to valid(1)."
3277 ::= { filterEntry 6 }
3278
3279 filterPktStatus OBJECT-TYPE
3280 SYNTAX INTEGER
3281 ACCESS read-write
3282 STATUS mandatory
3283 DESCRIPTION
3284 "The status that is to be matched with the input
3285 packet. The only bits relevant to this match
3286 algorithm are those that have the corresponding
3287 filterPktStatusMask bit equal to one.
3288
3289 The following two rules are then applied to every
3290 packet:
3291
3292 (1) For each relevant bit from the packet status
3293 with the corresponding filterPktStatusNotMask
3294 bit set to zero, if the bit from the packet
3295 status is not equal to the corresponding bit
3296 from the filterPktStatus, then the packet will
3297
3298
3299
3300 <span class="grey">Remote Network Monitoring Working Group [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3303
3304
3305 fail this status match.
3306
3307 (2) If for every relevant bit from the packet status
3308 with the corresponding filterPktStatusNotMask
3309 bit set to one, the bit from the packet status
3310 is equal to the corresponding bit from the
3311 filterPktStatus, then the packet will fail
3312 this status match.
3313
3314 Any packets that have not failed either of the two
3315 matches above have passed this status match.
3316
3317 The value of the packet status is a sum. This sum
3318 initially takes the value zero. Then, for each
3319 error, E, that has been discovered in this packet,
3320 2 raised to a value representing E is added to the sum.
3321 The errors and the bits that represent them are
3322 dependent on the media type of the interface that
3323 this channel is receiving packets from.
3324
3325 The errors defined for a packet captured off of an
3326 Ethernet interface are as follows:
3327
3328 bit # Error
3329 0 Packet is longer than 1518 octets
3330 1 Packet is shorter than 64 octets
3331 2 Packet experienced a CRC or Alignment
3332 error
3333
3334 For example, an Ethernet fragment would have a
3335 value of 6 (2^1 + 2^2).
3336
3337 As this MIB is expanded to new media types, this
3338 object will have other media-specific errors defined.
3339
3340 For the purposes of this status matching algorithm, if
3341 the packet status is longer than this
3342 object, filterPktStatus this object is conceptually
3343 extended with '0' bits until it reaches the size of
3344 the packet status.
3345
3346 This object may not be modified if the associated
3347 filterStatus object is equal to valid(1)."
3348 ::= { filterEntry 7 }
3349
3350 filterPktStatusMask OBJECT-TYPE
3351 SYNTAX INTEGER
3352 ACCESS read-write
3353
3354
3355
3356 <span class="grey">Remote Network Monitoring Working Group [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3359
3360
3361 STATUS mandatory
3362 DESCRIPTION
3363 "The mask that is applied to the status match process.
3364 Only those bits in the received packet that correspond
3365 to bits set in this mask are relevant for further
3366 processing by the status match algorithm. For the
3367 purposes of the matching algorithm, if the
3368 associated filterPktStatus object is longer than
3369 this mask, this mask is conceptually extended with
3370 '1' bits until it reaches the size of the
3371 filterPktStatus. In addition, if a packet status is
3372 longer than this mask, this mask is conceptually
3373 extended with '0' bits until it reaches the size of
3374 the packet status.
3375
3376 This object may not be modified if the associated
3377 filterStatus object is equal to valid(1)."
3378 ::= { filterEntry 8 }
3379
3380 filterPktStatusNotMask OBJECT-TYPE
3381 SYNTAX INTEGER
3382 ACCESS read-write
3383 STATUS mandatory
3384 DESCRIPTION
3385 "The inversion mask that is applied to the status match
3386 process. Those relevant bits in the received packet
3387 status that correspond to bits cleared in this mask
3388 must all be equal to their corresponding bits in the
3389 filterPktStatus object for the packet to be accepted.
3390 In addition, at least one of those relevant bits in the
3391 received packet status that correspond to bits set in
3392 this mask must be different to its corresponding bit
3393 in the filterPktStatus object for the packet to be
3394 accepted.
3395
3396 For the purposes of the matching algorithm, if the
3397 associated filterPktStatus object or a packet status
3398 is longer than this mask, this mask is conceptually
3399 extended with '0' bits until it reaches the longer of
3400 the lengths of the filterPktStatus object and the
3401 packet status.
3402
3403 This object may not be modified if the associated
3404 filterStatus object is equal to valid(1)."
3405 ::= { filterEntry 9 }
3406
3407 filterOwner OBJECT-TYPE
3408 SYNTAX OwnerString
3409
3410
3411
3412 <span class="grey">Remote Network Monitoring Working Group [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3415
3416
3417 ACCESS read-write
3418 STATUS mandatory
3419 DESCRIPTION
3420 "The entity that configured this entry and is
3421 therefore using the resources assigned to it."
3422 ::= { filterEntry 10 }
3423
3424 filterStatus OBJECT-TYPE
3425 SYNTAX EntryStatus
3426 ACCESS read-write
3427 STATUS mandatory
3428 DESCRIPTION
3429 "The status of this filter entry."
3430 ::= { filterEntry 11 }
3431
3432 channelTable OBJECT-TYPE
3433 SYNTAX SEQUENCE OF ChannelEntry
3434 ACCESS not-accessible
3435 STATUS mandatory
3436 DESCRIPTION
3437 "A list of packet channel entries."
3438 ::= { filter 2 }
3439
3440 channelEntry OBJECT-TYPE
3441 SYNTAX ChannelEntry
3442 ACCESS not-accessible
3443 STATUS mandatory
3444 DESCRIPTION
3445 "A set of parameters for a packet channel applied on a
3446 particular interface."
3447 INDEX { channelIndex }
3448 ::= { channelTable 1 }
3449
3450 ChannelEntry ::= SEQUENCE {
3451 channelIndex INTEGER (1..65535),
3452 channelIfIndex INTEGER (1..65535),
3453 channelAcceptType INTEGER,
3454 channelDataControl INTEGER,
3455 channelTurnOnEventIndex INTEGER (0..65535),
3456 channelTurnOffEventIndex INTEGER (0..65535),
3457 channelEventIndex INTEGER (0..65535),
3458 channelEventStatus INTEGER,
3459 channelMatches Counter,
3460 channelDescription DisplayString (SIZE (0..127)),
3461 channelOwner OwnerString,
3462 channelStatus INTEGER
3463 }
3464
3465
3466
3467
3468 <span class="grey">Remote Network Monitoring Working Group [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3471
3472
3473 channelIndex OBJECT-TYPE
3474 SYNTAX INTEGER (1..65535)
3475 ACCESS read-only
3476 STATUS mandatory
3477 DESCRIPTION
3478 "An index that uniquely identifies an entry
3479 in the channel table. Each such
3480 entry defines one channel, a logical data
3481 and event stream."
3482 ::= { channelEntry 1 }
3483
3484 channelIfIndex OBJECT-TYPE
3485 SYNTAX INTEGER (1..65535)
3486 ACCESS read-write
3487 STATUS mandatory
3488 DESCRIPTION
3489 "The value of this object uniquely identifies the
3490 interface on this remote network monitoring device
3491 to which the associated filters are applied to allow
3492 data into this channel. The interface identified by
3493 a particular value of this object is the same
3494 interface as identified by the same value of the
3495 ifIndex object, defined in [<a href="#ref-4" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">4</a>,<a href="#ref-6" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">6</a>]. The filters in
3496 this group are applied to all packets on the local
3497 network segment attached to the identified
3498 interface.
3499
3500 This object may not be modified if the associated
3501 channelStatus object is equal to valid(1)."
3502 ::= { channelEntry 2 }
3503
3504 channelAcceptType OBJECT-TYPE
3505 SYNTAX INTEGER {
3506 acceptMatched(1),
3507 acceptFailed(2)
3508 }
3509 ACCESS read-write
3510 STATUS mandatory
3511 DESCRIPTION
3512 "This object controls the action of the filters
3513 associated with this channel. If this object is equal
3514 to acceptMatched(1), packets will be accepted to this
3515 channel if they are accepted by both the packet data
3516 and packet status matches of an associated filter. If
3517 this object is equal to acceptFailed(2), packets will
3518 be accepted to this channel only if they fail either
3519 the packet data match or the packet status match of
3520 each of the associated filters.
3521
3522
3523
3524 <span class="grey">Remote Network Monitoring Working Group [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3527
3528
3529 This object may not be modified if the associated
3530 channelStatus object is equal to valid(1)."
3531 ::= { channelEntry 3 }
3532
3533 channelDataControl OBJECT-TYPE
3534 SYNTAX INTEGER {
3535 on(1),
3536 off(2)
3537 }
3538 ACCESS read-write
3539 STATUS mandatory
3540 DESCRIPTION
3541 "This object controls the flow of data through this
3542 channel. If this object is on(1), data, status and
3543 events flow through this channel. If this object is
3544 off(2), data, status and events will not flow through
3545 this channel."
3546 DEFVAL { off }
3547 ::= { channelEntry 4 }
3548
3549 channelTurnOnEventIndex OBJECT-TYPE
3550 SYNTAX INTEGER (0..65535)
3551 ACCESS read-write
3552 STATUS mandatory
3553 DESCRIPTION
3554 "The value of this object identifies the event
3555 that is configured to turn the associated
3556 channelDataControl from off to on when the event is
3557 generated. The event identified by a particular value
3558 of this object is the same event as identified by the
3559 same value of the eventIndex object. If there is no
3560 corresponding entry in the eventTable, then no
3561 association exists. In fact, if no event is intended
3562 for this channel, channelTurnOnEventIndex must be
3563 set to zero, a non-existent event index.
3564
3565 This object may not be modified if the associated
3566 channelStatus object is equal to valid(1)."
3567 ::= { channelEntry 5 }
3568
3569 channelTurnOffEventIndex OBJECT-TYPE
3570 SYNTAX INTEGER (0..65535)
3571 ACCESS read-write
3572 STATUS mandatory
3573 DESCRIPTION
3574 "The value of this object identifies the event
3575 that is configured to turn the associated
3576 channelDataControl from on to off when the event is
3577
3578
3579
3580 <span class="grey">Remote Network Monitoring Working Group [Page 64]</span></pre>
3581 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
3582 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3583
3584
3585 generated. The event identified by a particular value
3586 of this object is the same event as identified by the
3587 same value of the eventIndex object. If there is no
3588 corresponding entry in the eventTable, then no
3589 association exists. In fact, if no event is intended
3590 for this channel, channelTurnOffEventIndex must be
3591 set to zero, a non-existent event index.
3592
3593 This object may not be modified if the associated
3594 channelStatus object is equal to valid(1)."
3595 ::= { channelEntry 6 }
3596
3597 channelEventIndex OBJECT-TYPE
3598 SYNTAX INTEGER (0..65535)
3599 ACCESS read-write
3600 STATUS mandatory
3601 DESCRIPTION
3602 "The value of this object identifies the event
3603 that is configured to be generated when the
3604 associated channelDataControl is on and a packet
3605 is matched. The event identified by a particular value
3606 of this object is the same event as identified by the
3607 same value of the eventIndex object. If there is no
3608 corresponding entry in the eventTable, then no
3609 association exists. In fact, if no event is intended
3610 for this channel, channelEventIndex must be
3611 set to zero, a non-existent event index.
3612
3613 This object may not be modified if the associated
3614 channelStatus object is equal to valid(1)."
3615 ::= { channelEntry 7 }
3616
3617 channelEventStatus OBJECT-TYPE
3618 SYNTAX INTEGER {
3619 eventReady(1),
3620 eventFired(2),
3621 eventAlwaysReady(3)
3622 }
3623 ACCESS read-write
3624 STATUS mandatory
3625 DESCRIPTION
3626 "The event status of this channel.
3627
3628 If this channel is configured to generate events
3629 when packets are matched, a means of controlling
3630 the flow of those events is often needed. When
3631 this object is equal to eventReady(1), a single
3632 event may be generated, after which this object
3633
3634
3635
3636 <span class="grey">Remote Network Monitoring Working Group [Page 65]</span></pre>
3637 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
3638 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3639
3640
3641 will be set by the probe to eventFired(2). While
3642 in the eventFired(2) state, no events will be
3643 generated until the object is modified to
3644 eventReady(1) (or eventAlwaysReady(3)). The
3645 management station can thus easily respond to a
3646 notification of an event by re-enabling this object.
3647
3648 If the management station wishes to disable this
3649 flow control and allow events to be generated
3650 at will, this object may be set to
3651 eventAlwaysReady(3). Disabling the flow control
3652 is discouraged as it can result in high network
3653 traffic or other performance problems."
3654 DEFVAL { eventReady }
3655 ::= { channelEntry 8 }
3656
3657 channelMatches OBJECT-TYPE
3658 SYNTAX Counter
3659 ACCESS read-only
3660 STATUS mandatory
3661 DESCRIPTION
3662 "The number of times this channel has matched a packet.
3663 Note that this object is updated even when
3664 channelDataControl is set to off."
3665 ::= { channelEntry 9 }
3666
3667 channelDescription OBJECT-TYPE
3668 SYNTAX DisplayString (SIZE (0..127))
3669 ACCESS read-write
3670 STATUS mandatory
3671 DESCRIPTION
3672 "A comment describing this channel."
3673 ::= { channelEntry 10 }
3674
3675 channelOwner OBJECT-TYPE
3676 SYNTAX OwnerString
3677 ACCESS read-write
3678 STATUS mandatory
3679 DESCRIPTION
3680 "The entity that configured this entry and is therefore
3681 using the resources assigned to it."
3682 ::= { channelEntry 11 }
3683
3684 channelStatus OBJECT-TYPE
3685 SYNTAX EntryStatus
3686 ACCESS read-write
3687 STATUS mandatory
3688 DESCRIPTION
3689
3690
3691
3692 <span class="grey">Remote Network Monitoring Working Group [Page 66]</span></pre>
3693 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
3694 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3695
3696
3697 "The status of this channel entry."
3698 ::= { channelEntry 12 }
3699
3700
3701 -- The Packet Capture Group
3702
3703 -- Implementation of the Packet Capture group is optional.
3704 --
3705 -- The Packet Capture Group requires implementation of the
3706 -- Filter Group.
3707 --
3708 -- The Packet Capture group allows packets to be captured
3709 -- upon a filter match. The bufferControlTable controls
3710 -- the captured packets output from a channel that is
3711 -- associated with it. The captured packets are placed
3712 -- in entries in the captureBufferTable. These entries are
3713 -- associated with the bufferControlEntry on whose behalf they
3714 -- were stored.
3715
3716 bufferControlTable OBJECT-TYPE
3717 SYNTAX SEQUENCE OF BufferControlEntry
3718 ACCESS not-accessible
3719 STATUS mandatory
3720 DESCRIPTION
3721 "A list of buffers control entries."
3722 ::= { capture 1 }
3723
3724 bufferControlEntry OBJECT-TYPE
3725 SYNTAX BufferControlEntry
3726 ACCESS not-accessible
3727 STATUS mandatory
3728 DESCRIPTION
3729 "A set of parameters that control the collection of
3730 a stream of packets that have matched filters."
3731 INDEX { bufferControlIndex }
3732 ::= { bufferControlTable 1 }
3733
3734 BufferControlEntry ::= SEQUENCE {
3735 bufferControlIndex INTEGER (1..65535),
3736 bufferControlChannelIndex INTEGER (1..65535),
3737 bufferControlFullStatus INTEGER,
3738 bufferControlFullAction INTEGER,
3739 bufferControlCaptureSliceSize INTEGER,
3740 bufferControlDownloadSliceSize INTEGER,
3741 bufferControlDownloadOffset INTEGER,
3742 bufferControlMaxOctetsRequested INTEGER,
3743 bufferControlMaxOctetsGranted INTEGER,
3744 bufferControlCapturedPackets INTEGER,
3745
3746
3747
3748 <span class="grey">Remote Network Monitoring Working Group [Page 67]</span></pre>
3749 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
3750 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3751
3752
3753 bufferControlTurnOnTime TimeTicks,
3754 bufferControlOwner OwnerString,
3755 bufferControlStatus INTEGER
3756 }
3757
3758 bufferControlIndex OBJECT-TYPE
3759 SYNTAX INTEGER (1..65535)
3760 ACCESS read-only
3761 STATUS mandatory
3762 DESCRIPTION
3763 "An index that uniquely identifies an entry
3764 in the bufferControl table. The value of this
3765 index shall never be zero. Each such
3766 entry defines one set of packets that is
3767 captured and controlled by one or more filters."
3768 ::= { bufferControlEntry 1 }
3769
3770 bufferControlChannelIndex OBJECT-TYPE
3771 SYNTAX INTEGER (1..65535)
3772 ACCESS read-write
3773 STATUS mandatory
3774 DESCRIPTION
3775 "An index that identifies the channel that is the
3776 source of packets for this bufferControl table.
3777 The channel identified by a particular value of this
3778 index is the same as identified by the same value of
3779 the channelIndex object.
3780
3781 This object may not be modified if the associated
3782 bufferControlStatus object is equal to valid(1)."
3783 ::= { bufferControlEntry 2 }
3784
3785 bufferControlFullStatus OBJECT-TYPE
3786 SYNTAX INTEGER {
3787 spaceAvailable(1),
3788 full(2)
3789 }
3790 ACCESS read-only
3791 STATUS mandatory
3792 DESCRIPTION
3793 "This object shows whether the buffer has room to
3794 accept new packets or if it is full.
3795
3796 If the status is spaceAvailable(1), the buffer is
3797 accepting new packets normally. If the status is
3798 full(2) and the associated bufferControlFullAction
3799 object is wrapWhenFull, the buffer is accepting new
3800 packets by deleting enough of the oldest packets
3801
3802
3803
3804 <span class="grey">Remote Network Monitoring Working Group [Page 68]</span></pre>
3805 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
3806 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3807
3808
3809 to make room for new ones as they arrive. Otherwise,
3810 if the status is full(2) and the
3811 bufferControlFullAction object is lockWhenFull,
3812 then the buffer has stopped collecting packets.
3813
3814 When this object is set to full(2) the probe must
3815 not later set it to spaceAvailable(1) except in the
3816 case of a significant gain in resources such as
3817 an increase of bufferControlOctetsGranted. In
3818 particular, the wrap-mode action of deleting old
3819 packets to make room for newly arrived packets
3820 must not affect the value of this object."
3821 ::= { bufferControlEntry 3 }
3822
3823 bufferControlFullAction OBJECT-TYPE
3824 SYNTAX INTEGER {
3825 lockWhenFull(1),
3826 wrapWhenFull(2) -- FIFO
3827 }
3828 ACCESS read-write
3829 STATUS mandatory
3830 DESCRIPTION
3831 "Controls the action of the buffer when it
3832 reaches the full status. When in the lockWhenFull(1)
3833 state a packet is added to the buffer that
3834 fills the buffer, the bufferControlFullStatus will
3835 be set to full(2) and this buffer will stop capturing
3836 packets."
3837 ::= { bufferControlEntry 4 }
3838
3839 bufferControlCaptureSliceSize OBJECT-TYPE
3840 SYNTAX INTEGER
3841 ACCESS read-write
3842 STATUS mandatory
3843 DESCRIPTION
3844 "The maximum number of octets of each packet
3845 that will be saved in this capture buffer.
3846 For example, if a 1500 octet packet is received by
3847 the probe and this object is set to 500, then only
3848 500 octets of the packet will be stored in the
3849 associated capture buffer. If this variable is set
3850 to 0, the capture buffer will save as many octets
3851 as is possible.
3852
3853 This object may not be modified if the associated
3854 bufferControlStatus object is equal to valid(1)."
3855 DEFVAL { 100 }
3856 ::= { bufferControlEntry 5 }
3857
3858
3859
3860 <span class="grey">Remote Network Monitoring Working Group [Page 69]</span></pre>
3861 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
3862 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3863
3864
3865 bufferControlDownloadSliceSize OBJECT-TYPE
3866 SYNTAX INTEGER
3867 ACCESS read-write
3868 STATUS mandatory
3869 DESCRIPTION
3870 "The maximum number of octets of each packet
3871 in this capture buffer that will be returned in
3872 an SNMP retrieval of that packet. For example,
3873 if 500 octets of a packet have been stored in the
3874 associated capture buffer, the associated
3875 bufferControlDownloadOffset is 0, and this
3876 object is set to 100, then the captureBufferPacket
3877 object that contains the packet will contain only
3878 the first 100 octets of the packet.
3879
3880 A prudent manager will take into account possible
3881 interoperability or fragmentation problems that may
3882 occur if the download slice size is set too large.
3883 In particular, conformant SNMP implementations are not
3884 required to accept messages whose length exceeds 484
3885 octets, although they are encouraged to support larger
3886 datagrams whenever feasible."
3887 DEFVAL { 100 }
3888 ::= { bufferControlEntry 6 }
3889
3890 bufferControlDownloadOffset OBJECT-TYPE
3891 SYNTAX INTEGER
3892 ACCESS read-write
3893 STATUS mandatory
3894 DESCRIPTION
3895 "The offset of the first octet of each packet
3896 in this capture buffer that will be returned in
3897 an SNMP retrieval of that packet. For example,
3898 if 500 octets of a packet have been stored in the
3899 associated capture buffer and this object is set to
3900 100, then the captureBufferPacket object that
3901 contains the packet will contain bytes starting
3902 100 octets into the packet."
3903 DEFVAL { 0 }
3904 ::= { bufferControlEntry 7 }
3905
3906 bufferControlMaxOctetsRequested OBJECT-TYPE
3907 SYNTAX INTEGER
3908 ACCESS read-write
3909 STATUS mandatory
3910 DESCRIPTION
3911 "The requested maximum number of octets to be
3912 saved in this captureBuffer, including any
3913
3914
3915
3916 <span class="grey">Remote Network Monitoring Working Group [Page 70]</span></pre>
3917 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
3918 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3919
3920
3921 implementation-specific overhead. If this variable
3922 is set to -1, the capture buffer will save as many
3923 octets as is possible.
3924
3925 When this object is created or modified, the probe
3926 should set bufferControlMaxOctetsGranted as closely
3927 to this object as is possible for the particular probe
3928 implementation and available resources. However, if
3929 the object has the special value of -1, the probe
3930 must set bufferControlMaxOctetsGranted to -1."
3931 DEFVAL { -1 }
3932 ::= { bufferControlEntry 8 }
3933
3934 bufferControlMaxOctetsGranted OBJECT-TYPE
3935 SYNTAX INTEGER
3936 ACCESS read-only
3937 STATUS mandatory
3938 DESCRIPTION
3939 "The maximum number of octets that can be
3940 saved in this captureBuffer, including overhead.
3941 If this variable is -1, the capture buffer will save
3942 as many octets as possible.
3943
3944 When the bufferControlMaxOctetsRequested object is
3945 created or modified, the probe should set this object
3946 as closely to the requested value as is possible for
3947 the particular probe implementation and available
3948 resources. However, if the request object has the
3949 special value of -1, the probe must set this object
3950 to -1. The probe must not lower this value except
3951 as a result of a modification to the associated
3952 bufferControlMaxOctetsRequested object.
3953
3954 When this maximum number of octets is reached
3955 and a new packet is to be added to this
3956 capture buffer and the corresponding
3957 bufferControlFullAction is set to wrapWhenFull(2),
3958 enough of the oldest packets associated with this
3959 capture buffer shall be deleted by the agent so
3960 that the new packet can be added. If the
3961 corresponding bufferControlFullAction is set to
3962 lockWhenFull(1), the new packet shall be discarded.
3963 In either case, the probe must set
3964 bufferControlFullStatus to full(2).
3965
3966 When the value of this object changes to a value less
3967 than the current value, entries are deleted from
3968 the captureBufferTable associated with this
3969
3970
3971
3972 <span class="grey">Remote Network Monitoring Working Group [Page 71]</span></pre>
3973 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
3974 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
3975
3976
3977 bufferControlEntry. Enough of the
3978 oldest of these captureBufferEntries shall be
3979 deleted by the agent so that the number of octets
3980 used remains less than or equal to the new value of
3981 this object.
3982
3983 When the value of this object changes to a value greater
3984 than the current value, the number of associated
3985 captureBufferEntries may be allowed to grow."
3986 ::= { bufferControlEntry 9 }
3987
3988 bufferControlCapturedPackets OBJECT-TYPE
3989 SYNTAX INTEGER
3990 ACCESS read-only
3991 STATUS mandatory
3992 DESCRIPTION
3993 "The number of packets currently in this captureBuffer."
3994 ::= { bufferControlEntry 10 }
3995
3996 bufferControlTurnOnTime OBJECT-TYPE
3997 SYNTAX TimeTicks
3998 ACCESS read-only
3999 STATUS mandatory
4000 DESCRIPTION
4001 "The value of sysUpTime when this capture buffer was
4002 first turned on."
4003 ::= { bufferControlEntry 11 }
4004
4005 bufferControlOwner OBJECT-TYPE
4006 SYNTAX OwnerString
4007 ACCESS read-write
4008 STATUS mandatory
4009 DESCRIPTION
4010 "The entity that configured this entry and is therefore
4011 using the resources assigned to it."
4012 ::= { bufferControlEntry 12 }
4013
4014 bufferControlStatus OBJECT-TYPE
4015 SYNTAX EntryStatus
4016 ACCESS read-write
4017 STATUS mandatory
4018 DESCRIPTION
4019 "The status of this buffer Control Entry."
4020 ::= { bufferControlEntry 13 }
4021
4022 captureBufferTable OBJECT-TYPE
4023 SYNTAX SEQUENCE OF CaptureBufferEntry
4024 ACCESS not-accessible
4025
4026
4027
4028 <span class="grey">Remote Network Monitoring Working Group [Page 72]</span></pre>
4029 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span>
4030 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
4031
4032
4033 STATUS mandatory
4034 DESCRIPTION
4035 "A list of packets captured off of a channel."
4036 ::= { capture 2 }
4037
4038 captureBufferEntry OBJECT-TYPE
4039 SYNTAX CaptureBufferEntry
4040 ACCESS not-accessible
4041 STATUS mandatory
4042 DESCRIPTION
4043 "A packet captured off of an attached network."
4044 INDEX { captureBufferControlIndex, captureBufferIndex }
4045 ::= { captureBufferTable 1 }
4046
4047 CaptureBufferEntry ::= SEQUENCE {
4048 captureBufferControlIndex INTEGER (1..65535),
4049 captureBufferIndex INTEGER,
4050 captureBufferPacketID INTEGER,
4051 captureBufferPacketData OCTET STRING,
4052 captureBufferPacketLength INTEGER,
4053 captureBufferPacketTime INTEGER,
4054 captureBufferPacketStatus INTEGER
4055 }
4056
4057 captureBufferControlIndex OBJECT-TYPE
4058 SYNTAX INTEGER (1..65535)
4059 ACCESS read-only
4060 STATUS mandatory
4061 DESCRIPTION
4062 "The index of the bufferControlEntry with which
4063 this packet is associated."
4064 ::= { captureBufferEntry 1 }
4065
4066 captureBufferIndex OBJECT-TYPE
4067 SYNTAX INTEGER
4068 ACCESS read-only
4069 STATUS mandatory
4070 DESCRIPTION
4071 "An index that uniquely identifies an entry
4072 in the captureBuffer table associated with a
4073 particular bufferControlEntry. This index will
4074 start at 1 and increase by one for each new packet
4075 added with the same captureBufferControlIndex."
4076 ::= { captureBufferEntry 2 }
4077
4078 captureBufferPacketID OBJECT-TYPE
4079 SYNTAX INTEGER
4080 ACCESS read-only
4081
4082
4083
4084 <span class="grey">Remote Network Monitoring Working Group [Page 73]</span></pre>
4085 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span>
4086 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
4087
4088
4089 STATUS mandatory
4090 DESCRIPTION
4091 "An index that describes the order of packets
4092 that are received on a particular interface.
4093 The packetID of a packet captured on an
4094 interface is defined to be greater than the
4095 packetID's of all packets captured previously on
4096 the same interface. As the captureBufferPacketID
4097 object has a maximum positive value of 2^31 - 1,
4098 any captureBufferPacketID object shall have the
4099 value of the associated packet's packetID mod 2^31."
4100 ::= { captureBufferEntry 3 }
4101
4102 captureBufferPacketData OBJECT-TYPE
4103 SYNTAX OCTET STRING
4104 ACCESS read-only
4105 STATUS mandatory
4106 DESCRIPTION
4107 "The data inside the packet, starting at the beginning
4108 of the packet plus any offset specified in the
4109 associated bufferControlDownloadOffset, including any
4110 link level headers. The length of the data in this
4111 object is the minimum of the length of the captured
4112 packet minus the offset, the length of the associated
4113 bufferControlCaptureSliceSize minus the offset, and the
4114 associated bufferControlDownloadSliceSize. If this
4115 minimum is less than zero, this object shall have a
4116 length of zero."
4117 ::= { captureBufferEntry 4 }
4118
4119 captureBufferPacketLength OBJECT-TYPE
4120 SYNTAX INTEGER
4121 ACCESS read-only
4122 STATUS mandatory
4123 DESCRIPTION
4124 "The actual length (off the wire) of the packet stored
4125 in this entry, including FCS octets."
4126 ::= { captureBufferEntry 5 }
4127
4128 captureBufferPacketTime OBJECT-TYPE
4129 SYNTAX INTEGER
4130 ACCESS read-only
4131 STATUS mandatory
4132 DESCRIPTION
4133 "The number of milliseconds that had passed since
4134 this capture buffer was first turned on when this
4135 packet was captured."
4136 ::= { captureBufferEntry 6 }
4137
4138
4139
4140 <span class="grey">Remote Network Monitoring Working Group [Page 74]</span></pre>
4141 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span>
4142 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
4143
4144
4145 captureBufferPacketStatus OBJECT-TYPE
4146 SYNTAX INTEGER
4147 ACCESS read-only
4148 STATUS mandatory
4149 DESCRIPTION
4150 "A value which indicates the error status of this
4151 packet.
4152
4153 The value of this object is defined in the same way as
4154 filterPacketStatus. The value is a sum. This sum
4155 initially takes the value zero. Then, for each
4156 error, E, that has been discovered in this packet,
4157 2 raised to a value representing E is added to the sum.
4158
4159 The errors defined for a packet captured off of an
4160 Ethernet interface are as follows:
4161
4162 bit # Error
4163 0 Packet is longer than 1518 octets
4164 1 Packet is shorter than 64 octets
4165 2 Packet experienced a CRC or Alignment
4166 error
4167 3 First packet in this capture buffer after
4168 it was detected that some packets were
4169 not processed correctly.
4170
4171 For example, an Ethernet fragment would have a
4172 value of 6 (2^1 + 2^2).
4173
4174 As this MIB is expanded to new media types, this object
4175 will have other media-specific errors defined."
4176 ::= { captureBufferEntry 7 }
4177
4178
4179 -- The Event Group
4180
4181 -- Implementation of the Event group is optional.
4182 --
4183 -- The Event group controls the generation and notification
4184 -- of events from this device. Each entry in the eventTable
4185 -- describes the parameters of the event that can be triggered.
4186 -- Each event entry is fired by an associated condition located
4187 -- elsewhere in the MIB. An event entry may also be associated
4188 -- with a function elsewhere in the MIB that will be executed
4189 -- when the event is generated. For example, a channel may
4190 -- be turned on or off by the firing of an event.
4191 --
4192 -- Each eventEntry may optionally specify that a log entry
4193
4194
4195
4196 <span class="grey">Remote Network Monitoring Working Group [Page 75]</span></pre>
4197 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span>
4198 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
4199
4200
4201 -- be created on its behalf whenever the event occurs.
4202 -- Each entry may also specify that notification should
4203 -- occur by way of SNMP trap messages. In this case, the
4204 -- community for the trap message is given in the associated
4205 -- eventCommunity object. The enterprise and specific trap
4206 -- fields of the trap are determined by the condition that
4207 -- triggered the event. Three traps are defined in a companion
4208 -- document: risingAlarm, fallingAlarm, and packetMatch.
4209 -- If the eventTable is triggered by a condition specified
4210 -- elsewhere, the enterprise and specific trap fields
4211 -- must be specified for traps generated for that condition.
4212
4213 eventTable OBJECT-TYPE
4214 SYNTAX SEQUENCE OF EventEntry
4215 ACCESS not-accessible
4216 STATUS mandatory
4217 DESCRIPTION
4218 "A list of events to be generated."
4219 ::= { event 1 }
4220
4221 eventEntry OBJECT-TYPE
4222 SYNTAX EventEntry
4223 ACCESS not-accessible
4224 STATUS mandatory
4225 DESCRIPTION
4226 "A set of parameters that describe an event to be
4227 generated when certain conditions are met."
4228 INDEX { eventIndex }
4229 ::= { eventTable 1 }
4230
4231 EventEntry ::= SEQUENCE {
4232 eventIndex INTEGER (1..65535),
4233 eventDescription DisplayString (SIZE (0..127)),
4234 eventType INTEGER,
4235 eventCommunity OCTET STRING (SIZE (0..127)),
4236 eventLastTimeSent TimeTicks,
4237 eventOwner OwnerString,
4238 eventStatus INTEGER
4239 }
4240
4241 eventIndex OBJECT-TYPE
4242 SYNTAX INTEGER (1..65535)
4243 ACCESS read-only
4244 STATUS mandatory
4245 DESCRIPTION
4246 "An index that uniquely identifies an entry in the
4247 event table. Each such entry defines one event that
4248 is to be generated when the appropriate conditions
4249
4250
4251
4252 <span class="grey">Remote Network Monitoring Working Group [Page 76]</span></pre>
4253 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span>
4254 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
4255
4256
4257 occur."
4258 ::= { eventEntry 1 }
4259
4260 eventDescription OBJECT-TYPE
4261 SYNTAX DisplayString (SIZE (0..127))
4262 ACCESS read-write
4263 STATUS mandatory
4264 DESCRIPTION
4265 "A comment describing this event entry."
4266 ::= { eventEntry 2 }
4267
4268 eventType OBJECT-TYPE
4269 SYNTAX INTEGER {
4270 none(1),
4271 log(2),
4272 snmp-trap(3), -- send an SNMP trap
4273 log-and-trap(4)
4274 }
4275 ACCESS read-write
4276 STATUS mandatory
4277 DESCRIPTION
4278 "The type of notification that the probe will make
4279 about this event. In the case of log, an entry is
4280 made in the log table for each event. In the case of
4281 snmp-trap, an SNMP trap is sent to one or more
4282 management stations."
4283 ::= { eventEntry 3 }
4284
4285 eventCommunity OBJECT-TYPE
4286 SYNTAX OCTET STRING (SIZE (0..127))
4287 ACCESS read-write
4288 STATUS mandatory
4289 DESCRIPTION
4290 "If an SNMP trap is to be sent, it will be sent to
4291 the SNMP community specified by this octet string.
4292 In the future this table will be extended to include
4293 the party security mechanism. This object shall be
4294 set to a string of length zero if it is intended that
4295 that mechanism be used to specify the destination of
4296 the trap."
4297 ::= { eventEntry 4 }
4298
4299 eventLastTimeSent OBJECT-TYPE
4300 SYNTAX TimeTicks
4301 ACCESS read-only
4302 STATUS mandatory
4303 DESCRIPTION
4304 "The value of sysUpTime at the time this event
4305
4306
4307
4308 <span class="grey">Remote Network Monitoring Working Group [Page 77]</span></pre>
4309 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span>
4310 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
4311
4312
4313 entry last generated an event. If this entry has
4314 not generated any events, this value will be
4315 zero."
4316 ::= { eventEntry 5 }
4317
4318 eventOwner OBJECT-TYPE
4319 SYNTAX OwnerString
4320 ACCESS read-write
4321 STATUS mandatory
4322 DESCRIPTION
4323 "The entity that configured this entry and is therefore
4324 using the resources assigned to it.
4325
4326 If this object contains a string starting with 'monitor'
4327 and has associated entries in the log table, all
4328 connected management stations should retrieve those
4329 log entries, as they may have significance to all
4330 management stations connected to this device"
4331 ::= { eventEntry 6 }
4332
4333 eventStatus OBJECT-TYPE
4334 SYNTAX EntryStatus
4335 ACCESS read-write
4336 STATUS mandatory
4337 DESCRIPTION
4338 "The status of this event entry.
4339
4340 If this object is not equal to valid(1), all associated
4341 log entries shall be deleted by the agent."
4342 ::= { eventEntry 7 }
4343
4344 --
4345 logTable OBJECT-TYPE
4346 SYNTAX SEQUENCE OF LogEntry
4347 ACCESS not-accessible
4348 STATUS mandatory
4349 DESCRIPTION
4350 "A list of events that have been logged."
4351 ::= { event 2 }
4352
4353 logEntry OBJECT-TYPE
4354 SYNTAX LogEntry
4355 ACCESS not-accessible
4356 STATUS mandatory
4357 DESCRIPTION
4358 "A set of data describing an event that has been
4359 logged."
4360 INDEX { logEventIndex, logIndex }
4361
4362
4363
4364 <span class="grey">Remote Network Monitoring Working Group [Page 78]</span></pre>
4365 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span>
4366 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
4367
4368
4369 ::= { logTable 1 }
4370
4371 LogEntry ::= SEQUENCE {
4372 logEventIndex INTEGER (1..65535),
4373 logIndex INTEGER,
4374 logTime TimeTicks,
4375 logDescription DisplayString (SIZE (0..255))
4376 }
4377
4378 logEventIndex OBJECT-TYPE
4379 SYNTAX INTEGER (1..65535)
4380 ACCESS read-only
4381 STATUS mandatory
4382 DESCRIPTION
4383 "The event entry that generated this log
4384 entry. The log identified by a particular
4385 value of this index is associated with the same
4386 eventEntry as identified by the same value
4387 of eventIndex."
4388 ::= { logEntry 1 }
4389
4390 logIndex OBJECT-TYPE
4391 SYNTAX INTEGER
4392 ACCESS read-only
4393 STATUS mandatory
4394 DESCRIPTION
4395 "An index that uniquely identifies an entry
4396 in the log table amongst those generated by the
4397 same eventEntries. These indexes are
4398 assigned beginning with 1 and increase by one
4399 with each new log entry. The association
4400 between values of logIndex and logEntries
4401 is fixed for the lifetime of each logEntry.
4402 The agent may choose to delete the oldest
4403 instances of logEntry as required because of
4404 lack of memory. It is an implementation-specific
4405 matter as to when this deletion may occur."
4406 ::= { logEntry 2 }
4407
4408 logTime OBJECT-TYPE
4409 SYNTAX TimeTicks
4410 ACCESS read-only
4411 STATUS mandatory
4412 DESCRIPTION
4413 "The value of sysUpTime when this log entry was
4414 created."
4415 ::= { logEntry 3 }
4416
4417
4418
4419
4420 <span class="grey">Remote Network Monitoring Working Group [Page 79]</span></pre>
4421 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span>
4422 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
4423
4424
4425 logDescription OBJECT-TYPE
4426 SYNTAX DisplayString (SIZE (0..255))
4427 ACCESS read-only
4428 STATUS mandatory
4429 DESCRIPTION
4430 "An implementation dependent description of the
4431 event that activated this log entry."
4432 ::= { logEntry 4 }
4433
4434 END
4435
4436 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
4437
4438 This document was produced by the IETF Remote Network Monitoring
4439 Working Group.
4440
4441 In addition, the comments of the following individuals are also
4442 acknowledged:
4443
4444 Anne Ambler Spider Systems
4445 Steve Bostock Novell
4446 Gigi Chu Hewlett-Packard
4447 Chuck Davin MIT
4448 Gary Ellis Hewlett-Packard
4449 Mike Erlinger Lexcel
4450 Stephen Grau Novell
4451 Martin Gray Spider Systems
4452 Mark Hoerth Hewlett-Packard
4453 Tim Lee-Thorp Network General
4454 Anil Singhal Frontier Software
4455 David Stevens Network General
4456 Gerard White Concord Communications
4457
4458 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
4459
4460 [<a id="ref-1">1</a>] Cerf, V., "IAB Recommendations for the Development of Internet
4461 Network Management Standards", <a href="./rfc1052">RFC 1052</a>, NRI, April 1988.
4462
4463 [<a id="ref-2">2</a>] Cerf, V., "Report of the Second Ad Hoc Network Management Review
4464 Group", <a href="./rfc1109">RFC 1109</a>, NRI, August 1989.
4465
4466 [<a id="ref-3">3</a>] Rose M., and K. McCloghrie, "Structure and Identification of
4467 Management Information for TCP/IP-based internets", <a href="./rfc1155">RFC 1155</a>,
4468 Performance Systems International, Hughes LAN Systems, May 1990.
4469
4470 [<a id="ref-4">4</a>] McCloghrie K., and M. Rose, "Management Information Base for
4471 Network Management of TCP/IP-based internets", <a href="./rfc1156">RFC 1156</a>, Hughes
4472 LAN Systems, Performance Systems International, May 1990.
4473
4474
4475
4476 <span class="grey">Remote Network Monitoring Working Group [Page 80]</span></pre>
4477 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-81" ></span>
4478 <span class="grey"><a href="./rfc1271">RFC 1271</a> Remote Network Monitoring MIB November 1991</span>
4479
4480
4481 [<a id="ref-5">5</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
4482 Network Management Protocol", <a href="./rfc1157">RFC 1157</a>, SNMP Research,
4483 Performance Systems International, Performance Systems
4484 International, MIT Laboratory for Computer Science, May 1990.
4485
4486 [<a id="ref-6">6</a>] McCloghrie K., and M. Rose, Editors, "Management Information Base
4487 for Network Management of TCP/IP-based internets", <a href="./rfc1213">RFC 1213</a>,
4488 Performance Systems International, March 1991.
4489
4490 [<a id="ref-7">7</a>] Information processing systems - Open Systems Interconnection -
4491 Specification of Abstract Syntax Notation One (ASN.1),
4492 International Organization for Standardization, International
4493 Standard 8824, December 1987.
4494
4495 [<a id="ref-8">8</a>] Information processing systems - Open Systems Interconnection -
4496 Specification of Basic Encoding Rules for Abstract Notation One
4497 (ASN.1), International Organization for Standardization,
4498 International Standard 8825, December 1987.
4499
4500 [<a id="ref-9">9</a>] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
4501 <a href="./rfc1212">RFC 1212</a>, Performance Systems International, Hughes LAN Systems,
4502 March 1991.
4503
4504 [<a id="ref-10">10</a>] Rose, M., Editor, "A Convention for Defining Traps for use with
4505 the SNMP", <a href="./rfc1215">RFC 1215</a>, Performance Systems International, March
4506 1991.
4507
4508 Security Considerations
4509
4510 Security issues are not discussed in this memo.
4511
4512 Author's Address
4513
4514 Steven Waldbusser
4515 Carnegie Mellon University
4516 4910 Forbes Ave.
4517 Pittsburgh, PA 15213
4518
4519 Phone: (412) 268-6628
4520
4521 EMail: [email protected]
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532 Remote Network Monitoring Working Group [Page 81]
4533 </pre>