Debian Codegraph @

rfc5815.html

raw
1 <pre>Internet Engineering Task Force (IETF) T. Dietz, Ed.
2 Request for Comments: 5815 NEC Europe, Ltd.
3 Category: Standards Track A. Kobayashi
4 ISSN: 2070-1721 NTT PF Labs.
5 B. Claise
6 Cisco Systems, Inc.
7 G. Muenz
8 Technische Universitaet Muenchen
9 April 2010
10
11
12 <span class="h1">Definitions of Managed Objects for IP Flow Information Export</span>
13
14 Abstract
15
16 This document defines managed objects for IP Flow Information eXport
17 (IPFIX). These objects provide information for monitoring IPFIX
18 Exporters and IPFIX Collectors including the basic configuration
19 information.
20
21 Status of This Memo
22
23 This is an Internet Standards Track document.
24
25 This document is a product of the Internet Engineering Task Force
26 (IETF). It represents the consensus of the IETF community. It has
27 received public review and has been approved for publication by the
28 Internet Engineering Steering Group (IESG). Further information on
29 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
30
31 Information about the current status of this document, any errata,
32 and how to provide feedback on it may be obtained at
33 <a href="http://www.rfc-editor.org/info/rfc5815">http://www.rfc-editor.org/info/rfc5815</a>.
34
35 Copyright Notice
36
37 Copyright (c) 2010 IETF Trust and the persons identified as the
38 document authors. All rights reserved.
39
40 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
41 Provisions Relating to IETF Documents
42 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
43 publication of this document. Please review these documents
44 carefully, as they describe your rights and restrictions with respect
45 to this document. Code Components extracted from this document must
46 include Simplified BSD License text as described in Section 4.e of
47 the Trust Legal Provisions and are provided without warranty as
48 described in the Simplified BSD License.
49
50
51
52 <span class="grey">Dietz, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
60 <a href="#section-2">2</a>. IPFIX Documents Overview ........................................<a href="#page-3">3</a>
61 <a href="#section-3">3</a>. The Internet-Standard Management Framework ......................<a href="#page-4">4</a>
62 <a href="#section-4">4</a>. Terminology .....................................................<a href="#page-4">4</a>
63 <a href="#section-5">5</a>. Structure of the IPFIX MIB ......................................<a href="#page-4">4</a>
64 <a href="#section-5.1">5.1</a>. The Transport Session Table ................................<a href="#page-4">4</a>
65 <a href="#section-5.2">5.2</a>. The Template Table .........................................<a href="#page-7">7</a>
66 <a href="#section-5.3">5.3</a>. The Template Definition Table ..............................<a href="#page-9">9</a>
67 <a href="#section-5.4">5.4</a>. The Export Table ..........................................<a href="#page-11">11</a>
68 <a href="#section-5.5">5.5</a>. The Metering Process Table ................................<a href="#page-12">12</a>
69 <a href="#section-5.6">5.6</a>. The Observation Point Table ...............................<a href="#page-13">13</a>
70 <a href="#section-5.7">5.7</a>. The Selection Process Table ...............................<a href="#page-14">14</a>
71 <a href="#section-5.8">5.8</a>. The Statistical Tables ....................................<a href="#page-15">15</a>
72 <a href="#section-5.8.1">5.8.1</a>. The Transport Session Statistical Table ............<a href="#page-15">15</a>
73 <a href="#section-5.8.2">5.8.2</a>. The Template Statistical Table .....................<a href="#page-15">15</a>
74 <a href="#section-5.8.3">5.8.3</a>. The Metering Process Statistical Table .............<a href="#page-15">15</a>
75 <a href="#section-5.8.4">5.8.4</a>. The Selection Process Statistical Table ............<a href="#page-15">15</a>
76 <a href="#section-6">6</a>. Structure of the IPFIX SELECTOR MIB ............................<a href="#page-15">15</a>
77 <a href="#section-6.1">6.1</a>. The Selector Functions ....................................<a href="#page-16">16</a>
78 <a href="#section-7">7</a>. Relationship to Other MIB Modules ..............................<a href="#page-18">18</a>
79 <a href="#section-7.1">7.1</a>. Relationship to the ENTITY MIB and IF MIB .................<a href="#page-18">18</a>
80 <a href="#section-7.2">7.2</a>. MIB Modules Required for IMPORTS ..........................<a href="#page-18">18</a>
81 <a href="#section-8">8</a>. MIB Definitions ................................................<a href="#page-18">18</a>
82 <a href="#section-8.1">8.1</a>. IPFIX MIB Definition ......................................<a href="#page-19">19</a>
83 <a href="#section-8.2">8.2</a>. IPFIX SELECTOR MIB Definition .............................<a href="#page-56">56</a>
84 <a href="#section-9">9</a>. Security Considerations ........................................<a href="#page-60">60</a>
85 <a href="#section-10">10</a>. IANA Considerations ...........................................<a href="#page-61">61</a>
86 <a href="#section-11">11</a>. Acknowledgments ...............................................<a href="#page-61">61</a>
87 <a href="#section-12">12</a>. References ....................................................<a href="#page-62">62</a>
88 <a href="#section-12.1">12.1</a>. Normative References .....................................<a href="#page-62">62</a>
89 <a href="#section-12.2">12.2</a>. Informative References ...................................<a href="#page-63">63</a>
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Dietz, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 This document defines two MIB modules for monitoring IP Flow
116 Information eXport (IPFIX) Devices including Exporters and
117 Collectors. Most of the objects defined by the IPFIX MIB module MUST
118 be implemented. Some objects MAY be implemented corresponding to the
119 functionality implemented in the equipment. Since the IPFIX
120 architecture [<a href="./rfc5470" title="&quot;Architecture for IP Flow Information Export&quot;">RFC5470</a>] foresees the possibility of using Filtering
121 and/or Sampling functions to reduce the data volume, this document
122 also provides the IPFIX SELECTOR MIB module, which contains the
123 standardized selection methods and is controlled by IANA. The full
124 configuration of the IPFIX Metering Process is out of the scope of
125 these MIB modules.
126
127 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
128 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
129 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
130
131 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IPFIX Documents Overview</span>
132
133 The IPFIX protocol provides network administrators with access to IP
134 Flow information. The architecture for the export of measured IP
135 Flow information out of an IPFIX Exporting Process to a Collecting
136 Process is defined in [<a href="./rfc5470" title="&quot;Architecture for IP Flow Information Export&quot;">RFC5470</a>], per the requirements defined in
137 [<a href="./rfc3917" title="&quot;Requirements for IP Flow Information Export (IPFIX)&quot;">RFC3917</a>]. The protocol document [<a href="./rfc5101" title="&quot;Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information&quot;">RFC5101</a>] specifies how IPFIX Data
138 Records and Templates are carried via a congestion-aware transport
139 protocol from IPFIX Exporting Processes to IPFIX Collecting
140 Processes. IPFIX has a formal description of IPFIX Information
141 Elements, their name, type and additional semantic information, as
142 specified in [<a href="./rfc5102" title="&quot;Information Model for IP Flow Information Export&quot;">RFC5102</a>]. Finally, [<a href="./rfc5472" title="&quot;IP Flow Information Export (IPFIX) Applicability&quot;">RFC5472</a>] describes what type of
143 applications can use the IPFIX protocol and how they can use the
144 information provided. It furthermore shows how the IPFIX framework
145 relates to other architectures and frameworks.
146
147 It is assumed that Flow metering, export, and collection is performed
148 according to the IPFIX architecture defined in [<a href="./rfc5470" title="&quot;Architecture for IP Flow Information Export&quot;">RFC5470</a>]. The
149 monitored configuration parameters of the export and collection of
150 Flow Templates and Data Records is modeled according to [<a href="./rfc5101" title="&quot;Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information&quot;">RFC5101</a>].
151 Packet selection methods that may be optionally used by the IPFIX
152 Metering Process are not considered in this MIB module. They are
153 defined in the Packet Sampling (PSAMP) framework [<a href="./rfc5474" title="&quot;A Framework for Packet Selection and Reporting&quot;">RFC5474</a>] and
154 Sampling techniques [<a href="./rfc5475" title="&quot;Sampling and Filtering Techniques for IP Packet Selection&quot;">RFC5475</a>] documents. Nevertheless, the basis for
155 defining Sampling and Filtering functions is given with the IPFIX
156 SELECTOR MIB module. Since the PSAMP export protocol [<a href="./rfc5476" title="&quot;Packet Sampling (PSAMP) Protocol Specifications&quot;">RFC5476</a>] is
157 based on the IPFIX protocol, the Sampling and Filtering functions can
158 be added to the IPFIX SELECTOR MIB module as needed.
159
160
161
162
163
164 <span class="grey">Dietz, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
167
168
169 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The Internet-Standard Management Framework</span>
170
171 For a detailed overview of the documents that describe the current
172 Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section&nbsp;7 of
173 RFC 3410</a> [<a href="./rfc3410" title="&quot;Introduction and Applicability Statements for Internet- Standard Management Framework&quot;">RFC3410</a>].
174
175 Managed objects are accessed via a virtual information store, termed
176 the Management Information Base or MIB. MIB objects are generally
177 accessed through the Simple Network Management Protocol (SNMP).
178 Objects in the MIB are defined using the mechanisms defined in the
179 Structure of Management Information (SMI). This memo specifies MIB
180 modules that are compliant to the SMIv2, which is described in STD
181 58, <a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>], STD 58, <a href="./rfc2579">RFC 2579</a> [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>] and STD 58, <a href="./rfc2580">RFC</a>
182 <a href="./rfc2580">2580</a> [<a href="./rfc2580" title="&quot;Conformance Statements for SMIv2&quot;">RFC2580</a>].
183
184 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Terminology</span>
185
186 The definitions of the basic terms like IP Traffic Flow, Exporting
187 Process, Collecting Process, Observation Points, etc. can be found in
188 the IPFIX protocol document [<a href="./rfc5101" title="&quot;Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information&quot;">RFC5101</a>].
189
190 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Structure of the IPFIX MIB</span>
191
192 The IPFIX MIB module consists of seven main tables, the Transport
193 Session table, the Template table and the corresponding Template
194 Definition table, the Export table, the Metering Process table, the
195 Observation Point table, and the Selection Process table. Since the
196 IPFIX architecture [<a href="./rfc5470" title="&quot;Architecture for IP Flow Information Export&quot;">RFC5470</a>] foresees the possibility of using
197 Filtering and/or Sampling functions to reduce the data volume, the
198 MIB module provides the basic objects for these functions with the
199 Selection Process table. The IPFIX SELECTOR MIB module defined in
200 the next section provides the standard Filtering and Sampling
201 functions that can be referenced in the ipfixSelectionProcessTable.
202
203 All remaining objects contain statistical values for the different
204 tables contained in the MIB module.
205
206 The following subsections describe all tables in the IPFIX MIB
207 module.
208
209 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. The Transport Session Table</span>
210
211 The Transport Session is the basis of the MIB module. The Transport
212 Session table (ipfixTransportSessionTable) contains all Transport
213 Sessions between Exporter and Collector. The table specifies the
214 transport layer protocol of the Transport Session and, depending on
215 that protocol, further parameters for the Transport Session. In the
216 case of UDP and TCP, these are the source and destination address as
217
218
219
220 <span class="grey">Dietz, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
223
224
225 well as the source and destination port. For Stream Control
226 Transmission Protocol (SCTP), the table contains the SCTP Assoc Id,
227 which is the index for the SCTP association in the SCTP MIB module
228 [<a href="./rfc3873" title="&quot;Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)&quot;">RFC3873</a>]. The mode of operation of the device, i.e., if the
229 Transport Session is used for collecting or exporting is given in the
230 ipfixTransportSessionDeviceMode object. Further on, it contains the
231 configured refresh parameters for Templates and Options Templates
232 that are used across unreliable connections as UDP. Finally, the
233 IPFIX version that is exported or collected by this Transport Session
234 and a status of the Transport Session is given in the table.
235
236 To illustrate the use of the above tables, let us assume the
237 following scenario: we have an Exporter on IP address 192.0.2.22 and
238 a Collector on IP address 192.0.2.37. The Exporter uses TCP to
239 export Templates and Data Records. The same Exporter also exports,
240 with UDP, to a Collector with the IP address of 192.0.2.44. This
241 would lead to the following Transport Session table on the Exporter:
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Dietz, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
279
280
281 ipfixTransportSessionTable (1)
282 |
283 +- ipfixTransportSessionEntry (1)
284 |
285 +- index (5) (ipfixTransportSessionIndex)
286 | +- ipfixTransportSessionIndex (1) = 5
287 | +- ipfixTransportSessionProtocol (2) = 6 (TCP)
288 | +- ipfixTransportSessionSourceAddressType (3) = 1 (ipv4)
289 | +- ipfixTransportSessionSourceAddress (4) = 192.0.2.22
290 | +- ipfixTransportSessionDestinationAddressType (5) = 1 (ipv4)
291 | +- ipfixTransportSessionDestinationAddress (6) = 192.0.2.37
292 | +- ipfixTransportSessionSourcePort (7) = 7653
293 | +- ipfixTransportSessionDestinationPort (8) = 4739
294 | +- ipfixTransportSessionSctpAssocId (9) = 0
295 | +- ipfixTransportSessionDeviceMode (10) = exporting(1)
296 | +- ipfixTransportSessionTemplateRefreshTimeout (11) = 0
297 | +- ipfixTransportSessionOptionTemplateRefreshTimeout (12) = 0
298 | +- ipfixTransportSessionTemplateRefreshPacket (13) = 0
299 | +- ipfixTransportSessionOptionTemplateRefreshPacket (14) = 0
300 | +- ipfixTransportSessionIpfixVersion (15) = 10
301 | +- ipfixTransportSessionStatus (16) = 2 (active)
302 .
303 .
304 .
305 +- index (11) (ipfixTransportSessionIndex)
306 +- ipfixTransportSessionIndex (1) = 11
307 +- ipfixTransportSessionProtocol (2) = 17 (UDP)
308 +- ipfixTransportSessionSourceAddressType (3) = 1 (ipv4)
309 +- ipfixTransportSessionSourceAddress (4) = 192.0.2.22
310 +- ipfixTransportSessionDestinationAddressType (5) = 1 (ipv4)
311 +- ipfixTransportSessionDestinationAddress (6) = 192.0.2.44
312 +- ipfixTransportSessionSourcePort (7) = 14287
313 +- ipfixTransportSessionDestinationPort (8) = 4739
314 +- ipfixTransportSessionSctpAssocId (9) = 0
315 +- ipfixTransportSessionDeviceMode (10) = exporting(1)
316 +- ipfixTransportSessionTemplateRefreshTimeout (11) = 100
317 +- ipfixTransportSessionOptionTemplateRefreshTimeout (12)
318 | = 100
319 +- ipfixTransportSessionTemplateRefreshPacket (13) = 10
320 +- ipfixTransportSessionOptionTemplateRefreshPacket (14) = 10
321 +- ipfixTransportSessionIpfixVersion (15) = 10
322 +- ipfixTransportSessionStatus (16) = 2 (active)
323
324 The values in brackets are the OID numbers. The Collectors would
325 then have the same entry except that the index would most likely
326 differ and the ipfixTransportSessionDeviceMode would be
327 collecting(2).
328
329
330
331
332 <span class="grey">Dietz, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
335
336
337 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. The Template Table</span>
338
339 The Template table lists all Templates (including Options Templates)
340 that are sent (by an Exporter) or received (by a Collector). The
341 (Options) Templates are unique per Transport Session, which also
342 gives the device mode (Exporter or Collector) and Observation Domain;
343 thus, the table is indexed by:
344
345 o the Transport Session Index (ipfixTransportSessionIndex)
346
347 o and the Observation Domain Id (ipfixTemplateObservationDomainId).
348
349 It contains the Set Id and an access time denoting the time when the
350 (Options) Template was last sent or received.
351
352 To resume the above example, the Exporter may want to export a
353 Template and an Options Template for each Transport Session defined
354 above. This leads to the following Template table defining Template
355 and Options Template:
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Dietz, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
391
392
393 ipfixTemplateTable (3)
394 |
395 +- ipfixTemplateEntry (1)
396 |
397 +- index (5) (ipfixTransportSessionIndex)
398 | +- index (3) (ipfixTemplateObservationDomainId)
399 | + index (257) (ipfixTemplateId)
400 | | +- ipfixTemplateObservationDomainId (1) = 3
401 | | +- ipfixTemplateId (2) = 257
402 | | +- ipfixTemplateSetId (3) = 2
403 | | +- ipfixTemplateAccessTime (4)
404 | | = 2008-7-1,12:49:11.2,+2:0
405 | |
406 | + index (264) (ipfixTemplateId)
407 | +- ipfixTemplateObservationDomainId (1) = 3
408 | +- ipfixTemplateId (2) = 264
409 | +- ipfixTemplateSetId (3) = 3
410 | +- ipfixTemplateAccessTime (4)
411 . = 2008-7-1,12:47:04.8,+2:0
412 .
413 .
414 .
415 +- index (11) (ipfixTransportSessionIndex)
416 +- index (3) (ipfixTemplateObservationDomainId)
417 + index (273) (ipfixTemplateId)
418 | +- ipfixTemplateObservationDomainId (1) = 3
419 | +- ipfixTemplateId (2) = 273
420 | +- ipfixTemplateSetId (3) = 2
421 | +- ipfixTemplateAccessTime (4)
422 | = 2008-7-1,12:49:11.2,+2:0
423 |
424 + index (289) (ipfixTemplateId)
425 +- ipfixTemplateObservationDomainId (1) = 3
426 +- ipfixTemplateId (2) = 289
427 +- ipfixTemplateSetId (3) = 3
428 +- ipfixTemplateAccessTime (4)
429 = 2008-7-1,12:47:04.8,+2:0
430
431 We assume that the Transport Session that is stored with index 5 in
432 the Transport Session table of the Exporter is stored with index 17
433 in the Transport Session table of the (corresponding) Collector.
434 Then, the Template table would look as follows:
435
436
437
438
439
440
441
442
443
444 <span class="grey">Dietz, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
447
448
449 ipfixTemplateTable (3)
450 |
451 +- ipfixTemplateEntry (1)
452 |
453 +- index (17) (ipfixTransportSessionIndex)
454 +- index (3) (ipfixTemplateObservationDomainId)
455 + index (257) (ipfixTemplateId)
456 | +- ipfixTemplateObservationDomainId (1) = 3
457 | +- ipfixTemplateId (2) = 257
458 | +- ipfixTemplateSetId (3) = 2
459 | +- ipfixTemplateAccessTime (4)
460 | = 2008-7-1,12:49:11.8,+2:0
461 |
462 + index (264) (ipfixTemplateId)
463 +- ipfixTemplateObservationDomainId (1) = 3
464 +- ipfixTemplateId (2) = 264
465 +- ipfixTemplateSetId (3) = 3
466 +- ipfixTemplateAccessTime (4)
467 = 2008-7-1,12:47:05.3,+2:0
468
469 The table on the second Collector would be analogous to the one shown
470 above.
471
472 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. The Template Definition Table</span>
473
474 The Template Definition table lists all the Information Elements
475 contained in a Template or Options Template. Therefore, it has the
476 same indexes as the corresponding Template table plus the Template
477 Id. Its own index denotes the order of the Information Element
478 inside the Template. Besides the Information Element Id and the
479 length of the encoded value, the table contains the enterprise number
480 for enterprise-specific Information Elements and flags for each
481 Information Element. The flags indicate if the Information Element
482 is used for scoping or as a Flow Key.
483
484 To resume the above example again, the Exporter is configured to
485 export the octets received and dropped at the Observation Point since
486 the last export of these values. In addition, it exports the start
487 and end time of the Flow relative to the timestamp contained in the
488 IPFIX header. This leads to the following Template Definition table
489 on the Exporter:
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">Dietz, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
503
504
505 ipfixTemplateDefinitionTable (4)
506 |
507 +- ipfixTemplateDefinitionEntry (1)
508 |
509 +- index (5) (ipfixTransportSessionIndex)
510 +- index (3) (ipfixTemplateObservationDomainId)
511 + index (257) (ipfixTemplateId)
512 +- index (1) (ipfixTemplateDefinitionIndex)
513 | +- ipfixTemplateDefinitionIndex (1) = 1
514 | +- ipfixTemplateDefinitionIeId (2) = 158
515 | | (flowStartDeltaMicroseconds)
516 | +- ipfixTemplateDefinitionIeLength (3) = 4
517 | +- ipfixTemplateDefinitionEnterprise (4) = 0
518 | +- ipfixTemplateDefinitionFlags (5) = 0
519 |
520 +- index (2) (ipfixTemplateDefinitionIndex)
521 | +- ipfixTemplateDefinitionIndex (1) = 2
522 | +- ipfixTemplateDefinitionIeId (2) = 159
523 | | (flowEndDeltaMicroseconds)
524 | +- ipfixTemplateDefinitionIeLength (3) = 4
525 | +- ipfixTemplateDefinitionEnterprise (4) = 0
526 | +- ipfixTemplateDefinitionFlags (5) = 0
527 |
528 +- index (3) (ipfixTemplateDefinitionIndex)
529 | +- ipfixTemplateDefinitionIndex (1) = 3
530 | +- ipfixTemplateDefinitionIeId (2) = 1
531 | | (octetDeltaCount)
532 | +- ipfixTemplateDefinitionIeLength (3) = 8
533 | +- ipfixTemplateDefinitionEnterprise (4) = 0
534 | +- ipfixTemplateDefinitionFlags (5) = 0
535 |
536 +- index (4) (ipfixTemplateDefinitionIndex)
537 +- ipfixTemplateDefinitionIndex (1) = 4
538 +- ipfixTemplateDefinitionIeId (2) = 132
539 | (droppedOctetDeltaCount)
540 +- ipfixTemplateDefinitionIeLength (3) = 8
541 +- ipfixTemplateDefinitionEnterprise (4) = 0
542 +- ipfixTemplateDefinitionFlags (5) = 0
543
544 The corresponding table entry on the Collector is the same except
545 that it would have another ipfixTransportSessionIndex, e.g., 17 as in
546 the previous example.
547
548
549
550
551
552
553
554
555
556 <span class="grey">Dietz, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
559
560
561 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. The Export Table</span>
562
563 On Exporters, the Export table (ipfixExportTable) can be used to
564 support features like failover, load-balancing, duplicate export to
565 several Collectors, etc. The table has three indexes that link an
566 entry with:
567
568 o the Metering Process table (ipfixMeteringProcessCacheId, see
569 below)
570
571 o and the Transport Session table (ipfixTransportSessionIndex).
572
573 Those entries with the same ipfixExportIndex and the same
574 ipfixMeteringProcessCacheId define a Transport Session group. The
575 member type for each group member describes its functionality. All
576 Transport Sessions referenced in this table MUST have the
577 ipfixTransportSessionDeviceMode exporting(1).
578
579 If the Exporter does not use Transport Session grouping, then each
580 ipfixExportIndex contains a single ipfixMeteringProcessCacheId, and
581 thus a singe Transport Session (ipfixTransportSessionIndex) and this
582 session MUST have the member type primary(1).
583
584 For failover, a Transport Session group can contain one Transport
585 Session with member type "primary" and several Transport Sessions
586 with type secondary(2). Entries with other member types are not
587 allowed for that type of group. For load-balancing or parallel
588 export, all Transport Sessions in the group MUST have the same member
589 type, either loadBalancing(4) or parallel(3).
590
591 The algorithms used for failover or load-balancing are out of the
592 scope of this document.
593
594 To continue the example, we assume that the Exporter uses the two
595 connections shown in the examples above as one primary Transport
596 Session protected by a secondary Transport Session. The Exporter
597 then has the following entries in the ipfixExportTable:
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Dietz, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
615
616
617 ipfixExportTable (5)
618 |
619 +- ipfixExportEntry (1)
620 |
621 +- index (7) (ipfixExportIndex)
622 | +- index (9) (ipfixMeteringProcessCacheId)
623 | | +- index (5) (ipfixTransportSessionIndex)
624 | | +- ipfixExportIndex (1) = 7
625 | | +- ipfixExportMemberType (2) = 1 (primary)
626 | |
627 | +- index (11) (ipfixTransportSessionIndex)
628 | +- ipfixExportIndex (1) = 7
629 | +- ipfixExportMemberType (2) = 2 (secondary)
630 |
631 +- index (8) (ipfixExportIndex)
632 +- index (9) (ipfixMeteringProcessCacheId)
633 +- index (5) (ipfixTransportSessionIndex)
634 | +- ipfixExportIndex (1) = 8
635 | +- ipfixExportMemberType (2) = 2 (secondary)
636 +- index (11) (ipfixTransportSessionIndex)
637 +- ipfixExportIndex (1) = 8
638 +- ipfixExportMemberType (2) = 1 (primary)
639
640 The example shows that the Exporter uses the Metering Process Cache
641 9, explained below, to export IPFIX Data Records for the Transport
642 Sessions 5 and 11. The Templates 257 and 264 defined above are
643 exported within Transport Session 5, and the Templates 273 and 289
644 are exported within Transport Session 11. If we assume that
645 Templates 257 and 264 are identical, then the Collector that receives
646 Transport Session 11 is a backup for the Collector of Transport
647 Session 5.
648
649 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. The Metering Process Table</span>
650
651 The Metering Process, as defined in [<a href="./rfc5101" title="&quot;Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information&quot;">RFC5101</a>], consists of a set of
652 functions. Maintaining the Flow Records is one of them. This
653 function is responsible for passing the Flow Records to the Exporting
654 Process and also for detecting Flow expiration. The Flow Records
655 that are maintained by the Metering Process can be grouped by the
656 Observation Points at which they are observed. The instance that
657 maintains such a group of Flow Records is a kind of cache. For this
658 reason, the Metering Process table (ipfixMeteringProcessTable) is
659 indexed by cache Ids (ipfixMeteringProcessCacheId). Each cache can
660 be maintained by a separate instance of the Metering Process. To
661 specify the Observation Point(s) where the Flow Records are gathered,
662 the ipfixMeteringProcessObservationPointGroupRef may contain an
663 ipfixObservationPointGroupId from the Observation Point table
664 (ipfixObservationPointTable) described in the next section. If an
665
666
667
668 <span class="grey">Dietz, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
671
672
673 Observation Point is not specified for the Flow Records, the
674 ipfixMeteringProcessObservationPointGroupRef MUST be zero(0). The
675 timeouts (ipfixMeteringProcessCacheActiveTimeout and
676 ipfixMeteringProcessCacheInactiveTimeout) specify when Flows are
677 expired.
678
679 ipfixMeteringProcessTable (6)
680 |
681 +- ipfixMeteringProcessEntry (1)
682 |
683 +- index (9) (ipfixMeteringProcessCacheId)
684 +- ipfixMeteringProcessCacheId (1) = 9
685 +- ipfixMeteringProcessObservationPointGroupRef (2) = 17
686 +- ipfixMeteringProcessCacheActiveTimeout (3) = 100
687 +- ipfixMeteringProcessCacheInactiveTimeout (4) = 100
688
689 <span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. The Observation Point Table</span>
690
691 The Observation Point table (ipfixObservationPointTable) groups
692 Observation Points with the ipfixObservationPointGroupId. Each entry
693 contains the Observation Domain Id in which the Observation Point is
694 located and a reference to the ENTITY MIB module [<a href="./rfc4133" title="&quot;Entity MIB (Version 3)&quot;">RFC4133</a>] or the IF
695 MIB module [<a href="./rfc2863" title="&quot;The Interfaces Group MIB&quot;">RFC2863</a>]. The objects in the ENTITY MIB module
696 referenced by ipfixObservationPointPhysicalEntity or IF MIB module
697 referenced by ipfixObservationPointPhysicalInterface denote the
698 Observation Point. If no such index can be given in those modules,
699 the references MUST be 0. If a reference is given in both object
700 ipfixObservationPointPhysicalEntity and
701 ipfixObservationPointPhysicalInterface, then both MUST point to the
702 same physical interface. In addition, a direction can be given to
703 render more specifically which Flow to monitor.
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">Dietz, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
727
728
729 ipfixObservationPointTable (7)
730 |
731 +- ipfixObservationPointEntry (1)
732 |
733 +- index (17) (ipfixObservationPointGroupId)
734 +- index (1) (ipfixObservationPointIndex)
735 | +- ipfixObservationPointGroupId (1) = 17
736 | +- ipfixObservationPointIndex (2) = 1
737 | +- ipfixObservationPointObservationDomainId (3) = 3
738 | +- ipfixObservationPointPhysicalEntity (4) = 6
739 | +- ipfixObservationPointPhysicalInterface(5) = 0
740 | +- ipfixObservationPointPhysicalEntityDirection (6)
741 = 3 (both)
742 |
743 +- index (2) (ipfixObservationPointIndex)
744 +- ipfixObservationPointGroupId (1) = 17
745 +- ipfixObservationPointIndex (2) = 2
746 +- ipfixObservationPointObservationDomainId (3) = 3
747 +- ipfixObservationPointPhysicalEntity (4) = 0
748 +- ipfixObservationPointPhysicalInterface (5) = 0
749 +- ipfixObservationPointPhysicalEntityDirection (6)
750 = 1 (ingress)
751
752 <span class="h3"><a class="selflink" id="section-5.7" href="#section-5.7">5.7</a>. The Selection Process Table</span>
753
754 This table supports the usage of Filtering and Sampling functions, as
755 described in [<a href="./rfc5470" title="&quot;Architecture for IP Flow Information Export&quot;">RFC5470</a>]. It contains lists of functions per Metering
756 Process cache (ipfixMeteringProcessCacheId). The selection process
757 index ipfixSelectionProcessIndex forms groups of selection methods
758 that are applied to an observed packet stream. The selection process
759 selector index (ipfixSelectionProcessSelectorIndex) indicates the
760 order in which the functions are applied to the packets observed at
761 the Observation Points associated with the Metering Process cache.
762 The selection methods are applied in increasing order, i.e.,
763 selection methods with a lower ipfixSelectionProcessSelectorIndex are
764 applied first. The functions are referred by object identifiers
765 pointing to the function with its parameters. If the selection
766 method does not use parameters, then it MUST point to the root of the
767 function subtree (see also <a href="#section-6">Section 6</a>). If the function uses
768 parameters, then it MUST point to an entry in the parameter table of
769 the selection method. If no Filtering or Sampling function is used
770 for a Metering Process, then an entry for the Metering Process SHOULD
771 be created pointing to the Select All function (ipfixFuncSelectAll).
772
773
774
775
776
777
778
779
780 <span class="grey">Dietz, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
783
784
785 <span class="h3"><a class="selflink" id="section-5.8" href="#section-5.8">5.8</a>. The Statistical Tables</span>
786
787 For the ipfixTransportSessionTable, the ipfixTemplateTable, the
788 ipfixMeteringProcessTable, and the ipfixSelectionProcessTable
789 statistical tables are defined that augment those tables. All the
790 statistical tables contain a discontinuity object that holds a
791 timestamp that denotes the time when a discontinuity event occurred
792 to notify the management system that the counters contained in those
793 tables might not be continuous anymore.
794
795 <span class="h4"><a class="selflink" id="section-5.8.1" href="#section-5.8.1">5.8.1</a>. The Transport Session Statistical Table</span>
796
797 The Transport Session Statistical table
798 (ipfixTransportSessionStatsTable) augments the
799 ipfixTransportSessionTable with statistical values. It contains the
800 rate (in bytes per second) with which it receives or sends out IPFIX
801 Messages, the number of bytes, packets, messages, Records, Templates
802 and Options Templates received or sent and the number of messages
803 that were discarded.
804
805 <span class="h4"><a class="selflink" id="section-5.8.2" href="#section-5.8.2">5.8.2</a>. The Template Statistical Table</span>
806
807 This table contains a statistical value for each Template. It
808 augments the Template table (ipfixTemplateTable) and specifies the
809 number of Data Records exported or collected for the Template.
810
811 <span class="h4"><a class="selflink" id="section-5.8.3" href="#section-5.8.3">5.8.3</a>. The Metering Process Statistical Table</span>
812
813 This table augments the Metering Process table
814 (ipfixMeteringProcessTable). It contains the statistical values for
815 the exported Data Records and the number of unused cache entries.
816
817 <span class="h4"><a class="selflink" id="section-5.8.4" href="#section-5.8.4">5.8.4</a>. The Selection Process Statistical Table</span>
818
819 This table augments the Selection Process table
820 (ipfixSelectionProcessTable) and introduces two generic statistical
821 values, the number of packets observed and the number of packets
822 dropped by the selection method.
823
824 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Structure of the IPFIX SELECTOR MIB</span>
825
826 The IPFIX SELECTOR MIB module defined in this section provides the
827 standard Filtering and Sampling functions that can be referenced in
828 the ipfixSelectionProcessTable. The subtree ipfixSelectorFunctions
829 is a placeholder where all standard Filtering and Sampling functions
830 should be located. It currently contains the Select All function
831 (ipfixFuncSelectAll). The IPFIX SELECTOR MIB module is maintained by
832 IANA and can be extended through Expert Review [<a href="./rfc5226" title="">RFC5226</a>], i.e.,
833
834
835
836 <span class="grey">Dietz, et al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
839
840
841 review by one of a group of experts designated by an IETF Area
842 Director. The group of experts MUST check the requested MIB objects
843 for completeness and accuracy of the description. Requests for MIB
844 objects that duplicate the functionality of existing objects SHOULD
845 be declined. The smallest available OID SHOULD be assigned to a new
846 MIB objects. The specification of new MIB objects SHOULD follow the
847 structure specified in the next Section and MUST be published using a
848 well-established and persistent publication medium. The experts will
849 initially be drawn from the Working Group Chairs and document editors
850 of the IPFIX and PSAMP Working Groups.
851
852 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. The Selector Functions</span>
853
854 The following figure shows what the MIB tree usually should look
855 like. It already contains the ipfixFuncSelectAll. The subtree in
856 ipfixFuncF2 gives the basic structure that all selection methods
857 SHOULD follow.
858
859 ipfixSelectorFunctions
860 |
861 +- ipfixFuncSelectAll
862 | |
863 | +- ipfixFuncSelectAllAvail (is the function available?)
864 |
865 +- ipfixFuncF2
866 | |
867 | +- ipfixFuncF2Avail (is the function F2 available?)
868 | |
869 | +- ipfixFuncF2Parameters (a table with parameters)
870 ...
871 |
872 +- ipfixFunFn...
873
874 The selection method SHOULD be designed as a MIB subtree introduced
875 by an object with the name ipfixFunc appended by a function name.
876 The objects in this subtree SHOULD be prefixed by this name. If the
877 function is named Fx, then we would start a subtree with an OID named
878 ipfixFuncFx. This subtree should contain an object ipfixFuncFxAvail
879 that has the type TruthValue. If a selection method takes
880 parameters, the MIB should contain a table named
881 ipfixFuncFxParameters, which should contain all the parameters that
882 the selection method specifies. An entry in this table will be
883 referenced by the IPFIX MIB module if the selection method with the
884 parameters is used.
885
886
887
888
889
890
891
892 <span class="grey">Dietz, et al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
895
896
897 To illustrate the structure defined above, the following contains an
898 example of a function MyFunc that holds three integer parameters
899 Param1, Param2, and Param3. In the example, there are currently two
900 instances of the parameters set defined with indexes 1 and 4.
901
902 ipfixSelectorFunctions (1)
903 |
904 +- ipfixFuncMyFunc (?)
905 |
906 +- ipfixFuncMyFuncAvail (1) = true
907 +- ipfixFuncMyFuncParameters (2)
908 |
909 +- ipfixFuncMyFuncParametersEntry (1)
910 |
911 +- index (1) (ipfixFuncMyFuncParametersIndex)
912 | +- ipfixFuncMyFuncParam1 (1) = 47
913 | +- ipfixFuncMyFuncParam2 (2) = -128
914 | +- ipficFuncMyFuncParam3 (3) = 19
915 |
916 +- index(4) (ipfixFuncMyFuncParametersIndex)
917 +- ipfixFuncMyFuncParam1 (1) = 19
918 +- ipfixFuncMyFuncParam2 (2) = -1
919 +- ipficFuncMyFuncParam3 (3) = 728
920
921 If the function defined above is referenced in the IPFIX MIB module,
922 the ipfixSelectionProcessTable would look as follows:
923
924 ipfixSelectionProcessTable (8)
925 |
926 +- ipfixSelectionProcessEntry (1)
927 |
928 +- index (9) (ipfixMeteringProcessCacheId)
929 +- index (1) (ipfixSelectionProcessIndex)
930 +- index (1) (ipfixSelectionProcessSelectorIndex)
931 | +- ipfixSelectionProcessSelectorFunction (3)
932 | = ipfixSelectorFunctions.?.2.1.4
933 +- index (2) (ipfixSelectionProcessSelectorIndex)
934 +- ipfixSelectionProcessSelectorFunction (3)
935 = ipfixSelectorFunctions.?.2.1.1
936
937 This means that for the ipfixMeteringProcessCacheId(9), a Selection
938 Process with index 1 is created that applies two times the same
939 function but with different parameter sets. First, the function
940 MyFunc is applied with the parameters of the set with index 4 and the
941 with the parameters of the set with index 1.
942
943
944
945
946
947
948 <span class="grey">Dietz, et al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
951
952
953 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Relationship to Other MIB Modules</span>
954
955 Besides the usual imports from the SNMP Standards [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>],
956 [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>], and [<a href="./rfc2580" title="&quot;Conformance Statements for SMIv2&quot;">RFC2580</a>], the IPFIX MIB module references the ENTITY
957 MIB module [<a href="./rfc4133" title="&quot;Entity MIB (Version 3)&quot;">RFC4133</a>] and the IF MIB module [<a href="./rfc2863" title="&quot;The Interfaces Group MIB&quot;">RFC2863</a>].
958
959 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Relationship to the ENTITY MIB and IF MIB</span>
960
961 The Observation Point table (ipfixObservationPointTable) contains a
962 reference to the ENTITY MIB module[RFC4133]
963 (ipfixObservationPointPhysicalEntity) or the IF MIB module [<a href="./rfc2863" title="&quot;The Interfaces Group MIB&quot;">RFC2863</a>]
964 (ipfixObservationPointPhysicalInterface). If the implementors of the
965 IPFIX MIB module want to specify the physical entity where Flows are
966 observed, then they SHOULD also implement the ENTITY MIB and/or the
967 IF MIB module. The implementation of the ENTITY MIB and/or IF MIB
968 module is OPTIONAL. If one of them is not implemented, then all
969 values of the respective column ipfixObservationPointPhysicalEntity
970 or ipfixObservationPointPhysicalInterface in the Observation Point
971 table are zero and the values of the
972 ipfixObservationPointPhysicalEntityDirection columns are unknown(0),
973 if none of them are defined.
974
975 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. MIB Modules Required for IMPORTS</span>
976
977 The IPFIX MIB module requires the modules SNMPv2-SMI [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>],
978 SNMPv2-TC [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>], and SNMPv2-CONF [<a href="./rfc2580" title="&quot;Conformance Statements for SMIv2&quot;">RFC2580</a>]. Further on, it
979 imports the textual conventions InetAddressType and InetAddress from
980 the INET ADDRESS MIB module [<a href="./rfc4001" title="&quot;Textual Conventions for Internet Network Addresses&quot;">RFC4001</a>].
981
982 The IPFIX SELECTOR MIB module also requires the modules SNMPv2-SMI
983 [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>], SNMPv2-TC [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>], and SNMPv2-CONF [<a href="./rfc2580" title="&quot;Conformance Statements for SMIv2&quot;">RFC2580</a>].
984
985 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. MIB Definitions</span>
986
987 This section contains the definitions of the IPFIX-MIB module and the
988 IPFIX-SELECTOR-MIB module. There are different mandatory groups
989 defined for Collector and Exporter implementations. The statistical
990 objects are made OPTIONAL.
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004 <span class="grey">Dietz, et al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1007
1008
1009 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. IPFIX MIB Definition</span>
1010
1011 IPFIX-MIB DEFINITIONS ::= BEGIN
1012
1013 IMPORTS
1014 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32, Counter64,
1015 Gauge32
1016 FROM SNMPv2-SMI -- <a href="./rfc2578">RFC2578</a>
1017 TimeStamp, DateAndTime
1018 FROM SNMPv2-TC -- <a href="./rfc2579">RFC2579</a>
1019 MODULE-COMPLIANCE, OBJECT-GROUP
1020 FROM SNMPv2-CONF -- <a href="./rfc2580">RFC2580</a>
1021 InterfaceIndexOrZero
1022 FROM IF-MIB -- <a href="./rfc2863">RFC2863</a>
1023 InetAddressType, InetAddress, InetPortNumber
1024 FROM INET-ADDRESS-MIB -- <a href="./rfc4001">RFC4001</a>
1025 PhysicalIndexOrZero
1026 FROM ENTITY-MIB; -- <a href="./rfc4133">RFC4133</a>
1027
1028 ipfixMIB MODULE-IDENTITY
1029 LAST-UPDATED "201004190000Z" -- 19 April 2010
1030 ORGANIZATION "IETF IPFIX Working Group"
1031 CONTACT-INFO
1032 "WG charter:
1033 <a href="http://www.ietf.org/html.charters/ipfix-charter.html">http://www.ietf.org/html.charters/ipfix-charter.html</a>
1034
1035 Mailing Lists:
1036 General Discussion: [email protected]
1037 To Subscribe: <a href="http://www1.ietf.org/mailman/listinfo/ipfix">http://www1.ietf.org/mailman/listinfo/ipfix</a>
1038 Archive:
1039 <a href="http://www1.ietf.org/mail-archive/web/ipfix/current/index.html">http://www1.ietf.org/mail-archive/web/ipfix/current/index.html</a>
1040
1041 Editor:
1042 Thomas Dietz
1043 NEC Europe Ltd.
1044 NEC Laboratories Europe
1045 Network Research Division
1046 Kurfuersten-Anlage 36
1047 69115 Heidelberg
1048 Germany
1049 Phone: +49 6221 4342-128
1050 Email: [email protected]
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Dietz, et al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1063
1064
1065 Atsushi Kobayashi
1066 NTT Information Sharing Platform Laboratories
1067 3-9-11 Midori-cho
1068 Musashino-shi
1069 180-8585
1070 Japan
1071 Phone: +81-422-59-3978
1072 Email: [email protected]
1073
1074 Benoit Claise
1075 Cisco Systems, Inc.
1076 De Kleetlaan 6a b1
1077 Degem 1831
1078 Belgium
1079 Phone: +32 2 704 5622
1080 Email: [email protected]
1081
1082 Gerhard Muenz
1083 Technische Universitaet Muenchen
1084 Department of Informatics
1085 Chair for Network Architectures and Services (I8)
1086 Boltzmannstr. 3
1087 85748 Garching
1088 Germany
1089 Phone: +49 89 289-18008
1090 Email: [email protected]
1091 URI: <a href="http://www.net.in.tum.de/~muenz">http://www.net.in.tum.de/~muenz</a>"
1092 DESCRIPTION
1093 "The IPFIX MIB defines managed objects for IP Flow
1094 Information eXport. These objects provide information about
1095 managed nodes supporting the IPFIX protocol,
1096 for Exporters as well as for Collectors.
1097
1098 Copyright (c) 2010 IETF Trust and the persons identified as
1099 authors of the code. All rights reserved.
1100
1101 Redistribution and use in source and binary forms, with or
1102 without modification, is permitted pursuant to, and subject
1103 to the license terms contained in, the Simplified BSD
1104 License set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's
1105 Legal Provisions Relating to IETF Documents
1106 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>)."
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Dietz, et al. Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1119
1120
1121 -- Revision history
1122
1123 REVISION "201004190000Z" -- 19 April 2010
1124 DESCRIPTION
1125 "Initial version, published as <a href="./rfc5815">RFC 5815</a>."
1126
1127 ::= { mib-2 193 }
1128
1129
1130 --******************************************************************
1131 -- Top Level Structure of the MIB
1132 --******************************************************************
1133
1134 ipfixObjects OBJECT IDENTIFIER ::= { ipfixMIB 1 }
1135 ipfixConformance OBJECT IDENTIFIER ::= { ipfixMIB 2 }
1136
1137 ipfixMainObjects OBJECT IDENTIFIER ::= { ipfixObjects 1 }
1138 ipfixStatistics OBJECT IDENTIFIER ::= { ipfixObjects 2 }
1139
1140 --==================================================================
1141 -- 1.1: Objects used by all IPFIX implementations
1142 --==================================================================
1143 --------------------------------------------------------------------
1144 -- 1.1.1: Transport Session Table
1145 --------------------------------------------------------------------
1146 ipfixTransportSessionTable OBJECT-TYPE
1147 SYNTAX SEQUENCE OF IpfixTransportSessionEntry
1148 MAX-ACCESS not-accessible
1149 STATUS current
1150 DESCRIPTION
1151 "This table lists the currently established Transport
1152 Sessions between an Exporting Process and a Collecting
1153 Process."
1154 ::= { ipfixMainObjects 1 }
1155
1156 ipfixTransportSessionEntry OBJECT-TYPE
1157 SYNTAX IpfixTransportSessionEntry
1158 MAX-ACCESS not-accessible
1159 STATUS current
1160 DESCRIPTION
1161 "Defines an entry in the ipfixTransportSessionTable."
1162 INDEX { ipfixTransportSessionIndex }
1163 ::= { ipfixTransportSessionTable 1 }
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Dietz, et al. Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1175
1176
1177 IpfixTransportSessionEntry ::=
1178 SEQUENCE {
1179 ipfixTransportSessionIndex Unsigned32,
1180 ipfixTransportSessionProtocol Unsigned32,
1181 ipfixTransportSessionSourceAddressType InetAddressType,
1182 ipfixTransportSessionSourceAddress InetAddress,
1183 ipfixTransportSessionDestinationAddressType InetAddressType,
1184 ipfixTransportSessionDestinationAddress InetAddress,
1185 ipfixTransportSessionSourcePort InetPortNumber,
1186 ipfixTransportSessionDestinationPort InetPortNumber,
1187 ipfixTransportSessionSctpAssocId Unsigned32,
1188 ipfixTransportSessionDeviceMode INTEGER,
1189 ipfixTransportSessionTemplateRefreshTimeout Unsigned32,
1190 ipfixTransportSessionOptionsTemplateRefreshTimeout Unsigned32,
1191 ipfixTransportSessionTemplateRefreshPacket Unsigned32,
1192 ipfixTransportSessionOptionsTemplateRefreshPacket Unsigned32,
1193 ipfixTransportSessionIpfixVersion Unsigned32,
1194 ipfixTransportSessionStatus INTEGER
1195 }
1196
1197 ipfixTransportSessionIndex OBJECT-TYPE
1198 SYNTAX Unsigned32 (1..4294967295)
1199 MAX-ACCESS not-accessible
1200 STATUS current
1201 DESCRIPTION
1202 "Locally arbitrary, but unique identifier of an entry in
1203 the ipfixTransportSessionTable. The value is expected to
1204 remain constant from a re-initialization of the entity's
1205 network management agent to the next re-initialization."
1206 ::= { ipfixTransportSessionEntry 1 }
1207
1208 ipfixTransportSessionProtocol OBJECT-TYPE
1209 SYNTAX Unsigned32 (1..255)
1210 MAX-ACCESS read-only
1211 STATUS current
1212 DESCRIPTION
1213 "The transport protocol used for receiving or transmitting
1214 IPFIX Messages. Protocol numbers are assigned by IANA. A
1215 current list of all assignments is available from
1216 &lt;<a href="http://www.iana.org/">http://www.iana.org/</a>&gt;."
1217 REFERENCE
1218 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow
1219 Information Export (IPFIX) Protocol for the Exchange of IP
1220 Traffic Flow Information, <a href="#section-10">Section 10</a>."
1221 ::= { ipfixTransportSessionEntry 2 }
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Dietz, et al. Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1231
1232
1233 ipfixTransportSessionSourceAddressType OBJECT-TYPE
1234 SYNTAX InetAddressType
1235 MAX-ACCESS read-only
1236 STATUS current
1237 DESCRIPTION
1238 "The type of address used for the source address,
1239 as specified in <a href="./rfc4001">RFC 4001</a>. This object is used with protocols
1240 (specified in ipfixTransportSessionProtocol) like TCP (6)
1241 and UDP (17) that have the notion of addresses. SCTP (132)
1242 should use the ipfixTransportSessionSctpAssocId instead.
1243 If SCTP (132) or any other protocol without the notion of
1244 addresses is used, the object MUST be set to unknown(0)."
1245 ::= { ipfixTransportSessionEntry 3 }
1246
1247 ipfixTransportSessionSourceAddress OBJECT-TYPE
1248 SYNTAX InetAddress
1249 MAX-ACCESS read-only
1250 STATUS current
1251 DESCRIPTION
1252 "The source address of the Exporter of the IPFIX Transport
1253 Session. This value is interpreted according to the value of
1254 ipfixTransportSessionAddressType as specified in <a href="./rfc4001">RFC 4001</a>.
1255 This object is used with protocols (specified in
1256 ipfixTransportSessionProtocol) like TCP (6) and UDP (17) that
1257 have the notion of addresses. SCTP (132) should use the
1258 ipfixTransportSessionSctpAssocId instead. If SCTP (132) or
1259 any other protocol without the notion of addresses is used,
1260 the object MUST be set to a zero-length string."
1261 ::= { ipfixTransportSessionEntry 4 }
1262
1263 ipfixTransportSessionDestinationAddressType OBJECT-TYPE
1264 SYNTAX InetAddressType
1265 MAX-ACCESS read-only
1266 STATUS current
1267 DESCRIPTION
1268 "The type of address used for the destination address,
1269 as specified in <a href="./rfc4001">RFC 4001</a>. This object is used with protocols
1270 (specified in ipfixTransportSessionProtocol) like TCP (6)
1271 and UDP (17) that have the notion of addresses. SCTP (132)
1272 should use the ipfixTransportSessionSctpAssocId instead.
1273 If SCTP (132) or any other protocol without the notion of
1274 addresses is used, the object MUST be set to unknown(0)."
1275 ::= { ipfixTransportSessionEntry 5 }
1276
1277 ipfixTransportSessionDestinationAddress OBJECT-TYPE
1278 SYNTAX InetAddress
1279 MAX-ACCESS read-only
1280 STATUS current
1281
1282
1283
1284 <span class="grey">Dietz, et al. Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1287
1288
1289 DESCRIPTION
1290 "The destination address of the Collector of the IPFIX
1291 Transport Session. This value is interpreted according to
1292 the value of ipfixTransportSessionAddressType, as specified
1293 in <a href="./rfc4001">RFC 4001</a>. This object is used with protocols
1294 (specified in ipfixTransportSessionProtocol) like TCP (6)
1295 and UDP (17) that have the notion of addresses. SCTP (132)
1296 should use the ipfixTransportSessionSctpAssocId instead.
1297 If SCTP (132) or any other protocol without the notion of
1298 addresses is used, the object MUST be set to a zero-length
1299 string"
1300 ::= { ipfixTransportSessionEntry 6 }
1301
1302 ipfixTransportSessionSourcePort OBJECT-TYPE
1303 SYNTAX InetPortNumber
1304 MAX-ACCESS read-only
1305 STATUS current
1306 DESCRIPTION
1307 "The transport protocol port number of the Exporter.
1308 This object is used with protocols (specified in
1309 ipfixTransportSessionProtocol) like TCP (6)
1310 and UDP (17) that have the notion of ports. SCTP (132)
1311 should copy the value of sctpAssocLocalPort if the
1312 Transport Session is in collecting mode or
1313 sctpAssocRemPort if the Transport Session is in
1314 exporting mode. The association is referenced
1315 by the ipfixTransportSessionSctpAssocId.
1316 If any other protocol without the notion of
1317 ports is used, the object MUST be set to zero."
1318 ::= { ipfixTransportSessionEntry 7 }
1319
1320 ipfixTransportSessionDestinationPort OBJECT-TYPE
1321 SYNTAX InetPortNumber
1322 MAX-ACCESS read-only
1323 STATUS current
1324 DESCRIPTION
1325 "The transport protocol port number of the Collector. The
1326 default value is 4739 for all currently defined transport
1327 protocol types. This object is used with protocols
1328 (specified in ipfixTransportSessionProtocol) like TCP (6)
1329 and UDP (17) that have the notion of ports. SCTP (132)
1330 should copy the value of sctpAssocRemPort if the
1331 Transport Session is in collecting mode or
1332 sctpAssocLocalPort if the Transport Session is in
1333 exporting mode. The association is referenced
1334 by the ipfixTransportSessionSctpAssocId.
1335 If any other protocol without the notion of
1336 ports is used, the object MUST be set to zero."
1337
1338
1339
1340 <span class="grey">Dietz, et al. Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1343
1344
1345 ::= { ipfixTransportSessionEntry 8 }
1346
1347 ipfixTransportSessionSctpAssocId OBJECT-TYPE
1348 SYNTAX Unsigned32
1349 MAX-ACCESS read-only
1350 STATUS current
1351 DESCRIPTION
1352 "The association id used for the SCTP session between the
1353 Exporter and the Collector of the IPFIX Transport Session.
1354 It is equal to the sctpAssocId entry in the sctpAssocTable
1355 defined in the SCTP MIB. This object is only valid if
1356 ipfixTransportSessionProtocol has the value 132 (SCTP). In
1357 all other cases, the value MUST be zero."
1358 REFERENCE
1359 "<a href="./rfc3873">RFC 3873</a>, Stream Control Transmission Protocol (SCTP)
1360 Management Information Base (MIB)."
1361 ::= { ipfixTransportSessionEntry 9 }
1362
1363 ipfixTransportSessionDeviceMode OBJECT-TYPE
1364 SYNTAX INTEGER {
1365 exporting(1),
1366 collecting(2)
1367 }
1368 MAX-ACCESS read-only
1369 STATUS current
1370 DESCRIPTION
1371 "The mode of operation of the device for the given Transport
1372 Session. This object can have the following values:
1373
1374 exporting(1)
1375 This value MUST be used if the Transport Session is
1376 used for exporting Records to other IPFIX Devices,
1377 i.e., this device acts as Exporter.
1378
1379 collecting(2)
1380 This value MUST be used if the Transport Session is
1381 used for collecting Records from other IPFIX Devices,
1382 i.e., this device acts as Collector."
1383 ::= { ipfixTransportSessionEntry 10 }
1384
1385 ipfixTransportSessionTemplateRefreshTimeout OBJECT-TYPE
1386 SYNTAX Unsigned32
1387 UNITS "seconds"
1388 MAX-ACCESS read-only
1389 STATUS current
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Dietz, et al. Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1399
1400
1401 DESCRIPTION
1402 "On Exporters, this object contains the time in seconds
1403 after which IPFIX Templates are resent by the
1404 Exporter.
1405
1406 On Collectors, this object contains the lifetime in seconds
1407 after which a Template becomes invalid when it is not
1408 received again within this lifetime.
1409
1410 This object is only valid if ipfixTransportSessionProtocol
1411 has the value 17 (UDP). In all other cases, the value MUST
1412 be zero."
1413 REFERENCE
1414 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1415 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1416 Information, Sections <a href="#section-10.3.6">10.3.6</a> and <a href="#section-10.3.7">10.3.7</a>."
1417 ::= { ipfixTransportSessionEntry 11 }
1418
1419 ipfixTransportSessionOptionsTemplateRefreshTimeout OBJECT-TYPE
1420 SYNTAX Unsigned32
1421 UNITS "seconds"
1422 MAX-ACCESS read-only
1423 STATUS current
1424 DESCRIPTION
1425 "On Exporters, this object contains the time in seconds
1426 after which IPFIX Options Templates are resent by the
1427 Exporter.
1428
1429 On Collectors, this object contains the lifetime in seconds
1430 after which an Options Template becomes invalid when it is
1431 not received again within this lifetime.
1432
1433 This object is only valid if ipfixTransportSessionProtocol
1434 has the value 17 (UDP). In all other cases the value MUST
1435 be zero."
1436 REFERENCE
1437 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1438 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1439 Information, Sections <a href="#section-10.3.6">10.3.6</a> and <a href="#section-10.3.7">10.3.7</a>."
1440 ::= { ipfixTransportSessionEntry 12 }
1441
1442 ipfixTransportSessionTemplateRefreshPacket OBJECT-TYPE
1443 SYNTAX Unsigned32
1444 UNITS "packets"
1445 MAX-ACCESS read-only
1446 STATUS current
1447
1448
1449
1450
1451
1452 <span class="grey">Dietz, et al. Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1455
1456
1457 DESCRIPTION
1458 "On Exporters, this object contains the number of exported
1459 IPFIX Messages after which IPFIX Templates are resent
1460 by the Exporter.
1461
1462 On Collectors, this object contains the lifetime in number
1463 of exported IPFIX Messages after which a Template becomes
1464 invalid when it is not received again within this lifetime.
1465
1466 This object is only valid if ipfixTransportSessionProtocol
1467 has the value 17 (UDP). In all other cases the value MUST
1468 be zero."
1469 REFERENCE
1470 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1471 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1472 Information, Sections <a href="#section-10.3.6">10.3.6</a> and <a href="#section-10.3.7">10.3.7</a>."
1473 ::= { ipfixTransportSessionEntry 13 }
1474
1475 ipfixTransportSessionOptionsTemplateRefreshPacket OBJECT-TYPE
1476 SYNTAX Unsigned32
1477 UNITS "packets"
1478 MAX-ACCESS read-only
1479 STATUS current
1480 DESCRIPTION
1481 "On Exporters, this object contains the number of exported
1482 IPFIX Messages after which IPFIX Options Templates are
1483 resent by the Exporter.
1484
1485 On Collectors, this object contains the lifetime in number
1486 of exported IPFIX Messages after which an Options Template
1487 becomes invalid when it is not received again within this
1488 lifetime.
1489
1490 This object is only valid if ipfixTransportSessionProtocol
1491 has the value 17 (UDP). In all other cases the value MUST
1492 be zero."
1493 REFERENCE
1494 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1495 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1496 Information, Sections <a href="#section-10.3.6">10.3.6</a> and <a href="#section-10.3.7">10.3.7</a>."
1497 ::= { ipfixTransportSessionEntry 14 }
1498
1499 ipfixTransportSessionIpfixVersion OBJECT-TYPE
1500 SYNTAX Unsigned32 (0..65535)
1501 MAX-ACCESS read-only
1502 STATUS current
1503
1504
1505
1506
1507
1508 <span class="grey">Dietz, et al. Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1511
1512
1513 DESCRIPTION
1514 "On Exporters the object contains the version number of the
1515 IPFIX protocol that the Exporter uses to export its data in
1516 this Transport Session.
1517
1518 On Collectors the object contains the version number of the
1519 IPFIX protocol it receives for this Transport Session.
1520
1521 If IPFIX Messages of different IPFIX protocol versions are
1522 transmitted or received in this Transport Session, this
1523 object contains the maximum version number."
1524 REFERENCE
1525 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1526 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1527 Information, <a href="#section-3.1">Section 3.1</a>."
1528 ::= { ipfixTransportSessionEntry 15 }
1529
1530 ipfixTransportSessionStatus OBJECT-TYPE
1531 SYNTAX INTEGER {
1532 unknown(0),
1533 inactive(1),
1534 active(2)
1535 }
1536 MAX-ACCESS read-only
1537 STATUS current
1538 DESCRIPTION
1539 "The status of a Transport Session. This object can have the
1540 following values:
1541
1542 unknown(0)
1543 This value MUST be used if the status of the
1544 Transport Session cannot be detected by the equipment.
1545 This value should be avoided as far as possible.
1546
1547 inactive(1)
1548 This value MUST be used for Transport Sessions that
1549 are specified in the system but are not currently active.
1550 The value can be used, e.g., for Transport Sessions that
1551 are backup (secondary) sessions in a Transport Session
1552 group.
1553
1554 active(2)
1555 This value MUST be used for Transport Sessions that are
1556 currently active and transmitting or receiving data."
1557 ::= { ipfixTransportSessionEntry 16 }
1558
1559
1560
1561
1562
1563
1564 <span class="grey">Dietz, et al. Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1567
1568
1569 --------------------------------------------------------------------
1570 -- 1.1.2: Template Table
1571 --------------------------------------------------------------------
1572 ipfixTemplateTable OBJECT-TYPE
1573 SYNTAX SEQUENCE OF IpfixTemplateEntry
1574 MAX-ACCESS not-accessible
1575 STATUS current
1576 DESCRIPTION
1577 "This table lists the Templates and Options Templates that
1578 are transmitted by the Exporting Process or received by the
1579 Collecting Process.
1580
1581 The table contains the Templates and Options Templates that
1582 are received or used for exporting data for a given
1583 Transport Session group and Observation Domain.
1584
1585 Withdrawn or invalidated (Options) Template MUST be removed
1586 from this table."
1587 ::= { ipfixMainObjects 2 }
1588
1589 ipfixTemplateEntry OBJECT-TYPE
1590 SYNTAX IpfixTemplateEntry
1591 MAX-ACCESS not-accessible
1592 STATUS current
1593 DESCRIPTION
1594 "Defines an entry in the ipfixTemplateTable."
1595 INDEX {
1596 ipfixTransportSessionIndex,
1597 ipfixTemplateObservationDomainId,
1598 ipfixTemplateId
1599 }
1600 ::= { ipfixTemplateTable 1 }
1601
1602 IpfixTemplateEntry ::=
1603 SEQUENCE {
1604 ipfixTemplateObservationDomainId Unsigned32,
1605 ipfixTemplateId Unsigned32,
1606 ipfixTemplateSetId Unsigned32,
1607 ipfixTemplateAccessTime DateAndTime
1608 }
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620 <span class="grey">Dietz, et al. Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1623
1624
1625 ipfixTemplateObservationDomainId OBJECT-TYPE
1626 SYNTAX Unsigned32 (0..4294967295)
1627 MAX-ACCESS not-accessible
1628 STATUS current
1629 DESCRIPTION
1630 "The Id of the Observation Domain for which this Template
1631 is defined. This value is used when sending IPFIX Messages.
1632
1633 The special value of 0 indicates that the Data Records
1634 exported with this (Option Template) cannot be applied to a
1635 single Observation Domain."
1636 REFERENCE
1637 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1638 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1639 Information, <a href="#section-3.1">Section 3.1</a>."
1640 ::= { ipfixTemplateEntry 1 }
1641
1642 ipfixTemplateId OBJECT-TYPE
1643 SYNTAX Unsigned32 (256..65535)
1644 MAX-ACCESS not-accessible
1645 STATUS current
1646 DESCRIPTION
1647 "This number indicates the Template Id in the IPFIX
1648 Message. Values from 0 to 255 are not allowed for Template
1649 Ids."
1650 REFERENCE
1651 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1652 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1653 Information, <a href="#section-3.4.1">Section 3.4.1</a>."
1654 ::= { ipfixTemplateEntry 2 }
1655
1656 ipfixTemplateSetId OBJECT-TYPE
1657 SYNTAX Unsigned32 (1..65535)
1658 MAX-ACCESS read-only
1659 STATUS current
1660 DESCRIPTION
1661 "This number indicates the Set Id of the Template. This
1662 object allows to easily retrieve the Template type.
1663
1664 Currently, there are two values defined. The value 2 is
1665 used for Sets containing Template definitions. The value 3
1666 is used for Sets containing Options Template definitions."
1667 REFERENCE
1668 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1669 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1670 Information, <a href="#section-3.3.2">Section 3.3.2</a>."
1671 ::= { ipfixTemplateEntry 3 }
1672
1673
1674
1675
1676 <span class="grey">Dietz, et al. Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1679
1680
1681 ipfixTemplateAccessTime OBJECT-TYPE
1682 SYNTAX DateAndTime
1683 MAX-ACCESS read-only
1684 STATUS current
1685 DESCRIPTION
1686 "If the Transport Session is in exporting mode
1687 (ipfixTransportSessionDeviceMode) the time when this
1688 (Options) Template was last sent to the Collector(s).
1689
1690 In the specific case of UDP as transport protocol, this
1691 time is used to know when a retransmission of the
1692 (Options) Template is needed.
1693
1694 If it is in collecting mode, this object contains the
1695 time when this (Options) Template was last received from
1696 the Exporter. In the specific case of UDP as transport
1697 protocol, this time is used to know when this (Options)
1698 Template times out and thus is no longer valid."
1699 ::= { ipfixTemplateEntry 4 }
1700
1701 --------------------------------------------------------------------
1702 -- 1.1.3: Exported Template Definition Table
1703 --------------------------------------------------------------------
1704 ipfixTemplateDefinitionTable OBJECT-TYPE
1705 SYNTAX SEQUENCE OF IpfixTemplateDefinitionEntry
1706 MAX-ACCESS not-accessible
1707 STATUS current
1708 DESCRIPTION
1709 "On Exporters, this table lists the (Options) Template fields
1710 of which a (Options) Template is defined. It defines the
1711 (Options) Template given in the ipfixTemplateId specified in
1712 the ipfixTemplateTable.
1713
1714 On Collectors, this table lists the (Options) Template fields
1715 of which a (Options) Template is defined. It defines the
1716 (Options) Template given in the ipfixTemplateId specified in
1717 the ipfixTemplateTable."
1718 ::= { ipfixMainObjects 3 }
1719
1720 ipfixTemplateDefinitionEntry OBJECT-TYPE
1721 SYNTAX IpfixTemplateDefinitionEntry
1722 MAX-ACCESS not-accessible
1723 STATUS current
1724 DESCRIPTION
1725 "Defines an entry in the ipfixTemplateDefinitionTable."
1726
1727
1728
1729
1730
1731
1732 <span class="grey">Dietz, et al. Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1735
1736
1737 INDEX {
1738 ipfixTransportSessionIndex,
1739 ipfixTemplateObservationDomainId,
1740 ipfixTemplateId,
1741 ipfixTemplateDefinitionIndex
1742 }
1743 ::= { ipfixTemplateDefinitionTable 1 }
1744
1745 IpfixTemplateDefinitionEntry ::=
1746 SEQUENCE {
1747 ipfixTemplateDefinitionIndex Unsigned32,
1748 ipfixTemplateDefinitionIeId Unsigned32,
1749 ipfixTemplateDefinitionIeLength Unsigned32,
1750 ipfixTemplateDefinitionEnterpriseNumber Unsigned32,
1751 ipfixTemplateDefinitionFlags BITS
1752 }
1753
1754 ipfixTemplateDefinitionIndex OBJECT-TYPE
1755 SYNTAX Unsigned32 (1..65535)
1756 MAX-ACCESS not-accessible
1757 STATUS current
1758 DESCRIPTION
1759 "The ipfixTemplateDefinitionIndex specifies the order in
1760 which the Information Elements are used in the (Options)
1761 Template Record.
1762
1763 Since a Template Record can contain a maximum of 65535
1764 Information Elements, the index is limited to this value."
1765 REFERENCE
1766 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1767 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1768 Information, Sections <a href="#section-3.4.1">3.4.1</a> and <a href="#section-3.4.2">3.4.2</a>."
1769 ::= { ipfixTemplateDefinitionEntry 1 }
1770
1771 ipfixTemplateDefinitionIeId OBJECT-TYPE
1772 SYNTAX Unsigned32 (1..65535)
1773 MAX-ACCESS read-only
1774 STATUS current
1775 DESCRIPTION
1776 "This indicates the Information Element Id at position
1777 ipfixTemplateDefinitionIndex in the (Options) Template
1778 ipfixTemplateId. This implicitly specifies the data type
1779 of the Information Element. The elements are registered
1780 at IANA. A current list of assignments can be found at
1781 &lt;<a href="http://www.iana.org/assignments/ipfix">http://www.iana.org/assignments/ipfix</a>&gt;"
1782
1783
1784
1785
1786
1787
1788 <span class="grey">Dietz, et al. Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1791
1792
1793 REFERENCE
1794 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1795 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1796 Information, <a href="#section-3.2">Section 3.2</a>.
1797
1798 <a href="./rfc5102">RFC 5102</a>, Information Model for IP Flow Information Export."
1799 ::= { ipfixTemplateDefinitionEntry 2 }
1800
1801 ipfixTemplateDefinitionIeLength OBJECT-TYPE
1802 SYNTAX Unsigned32 (0..65535)
1803 MAX-ACCESS read-only
1804 STATUS current
1805 DESCRIPTION
1806 "This indicates the length of the Information Element Id at
1807 position ipfixTemplateDefinitionIndex in the (Options)
1808 Template ipfixTemplateId."
1809 REFERENCE
1810 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1811 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1812 Information, <a href="#section-3.2">Section 3.2</a>.
1813
1814 <a href="./rfc5102">RFC 5102</a>, Information Model for IP Flow Information Export."
1815 ::= { ipfixTemplateDefinitionEntry 3 }
1816
1817 ipfixTemplateDefinitionEnterpriseNumber OBJECT-TYPE
1818 SYNTAX Unsigned32
1819 MAX-ACCESS read-only
1820 STATUS current
1821 DESCRIPTION
1822 "IANA enterprise number of the authority defining the
1823 Information Element identifier in this Template Record.
1824 Enterprise numbers are assigned by IANA. A current list of
1825 all assignments is available from
1826 &lt;<a href="http://www.iana.org/assignments/enterprise-numbers/">http://www.iana.org/assignments/enterprise-numbers/</a>&gt;.
1827
1828 This object must be zero(0) for all standard Information
1829 Elements registered with IANA. A current list of these
1830 elements is available from
1831 &lt;<a href="http://www.iana.org/assignments/ipfix/ipfix.xhtml">http://www.iana.org/assignments/ipfix/ipfix.xhtml</a>&gt;."
1832 REFERENCE
1833 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
1834 (IPFIX) Protocol for the Exchange of IP Traffic Flow
1835 Information, <a href="#section-3.2">Section 3.2</a>.
1836
1837 <a href="./rfc5102">RFC 5102</a>, Information Model for IP Flow Information Export."
1838 ::= { ipfixTemplateDefinitionEntry 4 }
1839
1840
1841
1842
1843
1844 <span class="grey">Dietz, et al. Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1847
1848
1849 ipfixTemplateDefinitionFlags OBJECT-TYPE
1850 SYNTAX BITS {
1851 scope(0),
1852 flowKey(1)
1853 }
1854 MAX-ACCESS read-only
1855 STATUS current
1856 DESCRIPTION
1857 "This bitmask indicates special attributes for the
1858 Information Element:
1859
1860 scope(0)
1861 This Information Element is used for scope.
1862
1863 flowKey(1)
1864 This Information Element is a Flow Key.
1865
1866 Thus, we get the following values for an Information Element:
1867
1868 If neither bit scope(0) nor bit flowKey(1) are set
1869 The Information Element is neither used for scoping nor
1870 as Flow Key.
1871 If only bit scope(0) is set
1872 The Information Element is used for scoping.
1873 If only bit flowKey(1) is set
1874 The Information Element is used as Flow Key.
1875
1876 Both bit scope(0) and flowKey(1) MUST NOT be set at the same
1877 time. This combination is not allowed."
1878 REFERENCE
1879 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information
1880 Export (IPFIX) Protocol for the Exchange of IP Traffic Flow
1881 Information, Sections <a href="#section-2">2</a> and <a href="#section-3.4.2.1">3.4.2.1</a>.
1882
1883 <a href="./rfc5102">RFC 5102</a>, Information Model for IP Flow Information Export."
1884 ::= { ipfixTemplateDefinitionEntry 5 }
1885
1886 --------------------------------------------------------------------
1887 -- 1.1.4: Export Table
1888 --------------------------------------------------------------------
1889 ipfixExportTable OBJECT-TYPE
1890 SYNTAX SEQUENCE OF IpfixExportEntry
1891 MAX-ACCESS not-accessible
1892 STATUS current
1893 DESCRIPTION
1894 "This table lists all exports of an IPFIX device.
1895
1896
1897
1898
1899
1900 <span class="grey">Dietz, et al. Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1903
1904
1905 On Exporters, this table contains all exports grouped by
1906 Transport Session, Observation Domain Id, Template Id, and
1907 Metering Process represented by the
1908 ipfixMeteringProcessCacheId. Thanks to the ipfixExportIndex,
1909 the exports can group one or more Transport Sessions to
1910 achieve a special functionality like failover management,
1911 load-balancing, etc. The entries with the same
1912 ipfixExportIndex, ipfixObservationDomainId,
1913 and ipfixMeteringProcessCacheId define a Transport
1914 Session group. If the Exporter does not use Transport
1915 Session grouping, then each ipfixExportIndex contains a
1916 single ipfixMeteringProcessCacheId and thus a singe
1917 Transport Session, and this session MUST have the member
1918 type primary(1). Transport Sessions referenced in this
1919 table MUST have the ipfixTransportSessionDeviceMode
1920 exporting(1).
1921
1922 On Collectors, this table is not needed."
1923 ::= { ipfixMainObjects 4 }
1924
1925 ipfixExportEntry OBJECT-TYPE
1926 SYNTAX IpfixExportEntry
1927 MAX-ACCESS not-accessible
1928 STATUS current
1929 DESCRIPTION
1930 "Defines an entry in the ipfixExportTable."
1931 INDEX {
1932 ipfixExportIndex,
1933 ipfixMeteringProcessCacheId,
1934 ipfixTransportSessionIndex
1935 }
1936 ::= { ipfixExportTable 1 }
1937
1938 IpfixExportEntry ::=
1939 SEQUENCE {
1940 ipfixExportIndex Unsigned32,
1941 ipfixExportMemberType INTEGER
1942 }
1943
1944 ipfixExportIndex OBJECT-TYPE
1945 SYNTAX Unsigned32 (1..4294967295)
1946 MAX-ACCESS not-accessible
1947 STATUS current
1948 DESCRIPTION
1949 "Locally arbitrary, but unique identifier of an entry in
1950 the ipfixExportTable. The value is expected
1951 to remain constant from a re-initialization of the entity's
1952 network management agent to the next re-initialization.
1953
1954
1955
1956 <span class="grey">Dietz, et al. Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
1959
1960
1961 A common ipfixExportIndex between two entries from this
1962 table expresses that there is a relationship between the
1963 Transport Sessions in ipfixTransportSessionIndex. The type
1964 of relationship is expressed by the value of
1965 ipfixExportMemberType."
1966 ::= { ipfixExportEntry 1 }
1967
1968 ipfixExportMemberType OBJECT-TYPE
1969 SYNTAX INTEGER {
1970 unknown(0),
1971 primary(1),
1972 secondary(2),
1973 parallel(3),
1974 loadBalancing(4)
1975 }
1976 MAX-ACCESS read-only
1977 STATUS current
1978 DESCRIPTION
1979 "The type of a member Transport Session in a Transport
1980 Session group (identified by the value of ipfixExportIndex,
1981 ipfixObservationDomainId, and ipfixMeteringProcessCacheId).
1982 The following values are valid:
1983
1984 unknown(0)
1985 This value MUST be used if the status of the group
1986 membership cannot be detected by the equipment. This
1987 value should be avoided as far as possible.
1988
1989 primary(1)
1990 This value is used for a group member that is used as
1991 the primary target of an Exporter. Other group members
1992 (with the same ipfixExportIndex and
1993 ipfixMeteringProcessCacheId) MUST NOT have the value
1994 primary(1) but MUST have the value secondary(2).
1995 This value MUST also be specified if the Exporter does
1996 not support Transport Session grouping. In this case,
1997 the group contains only one Transport Session.
1998
1999 secondary(2)
2000 This value is used for a group member that is used as a
2001 secondary target of an Exporter. The Exporter will use
2002 one of the targets specified as secondary(2) within the
2003 same Transport Session group when the primary target is
2004 not reachable.
2005
2006
2007
2008
2009
2010
2011
2012 <span class="grey">Dietz, et al. Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2015
2016
2017 parallel(3)
2018 This value is used for a group member that is used for
2019 duplicate exporting, i.e., all group members identified
2020 by the ipfixExportIndex are exporting the same Records
2021 in parallel. This implies that all group members MUST
2022 have the same membertype parallel(3).
2023
2024 loadBalancing(4)
2025 This value is used for a group member that is used
2026 as one target for load-balancing. This means that a
2027 Record is sent to one of the group members in this
2028 group identified by ipfixExportIndex.
2029 This implies that all group members MUST have the same
2030 membertype loadBalancing(4)."
2031 ::= { ipfixExportEntry 2 }
2032
2033 --------------------------------------------------------------------
2034 -- 1.1.5: Metering Process Table
2035 --------------------------------------------------------------------
2036 ipfixMeteringProcessTable OBJECT-TYPE
2037 SYNTAX SEQUENCE OF IpfixMeteringProcessEntry
2038 MAX-ACCESS not-accessible
2039 STATUS current
2040 DESCRIPTION
2041 "This table lists so-called caches used at the Metering
2042 Process to store the metering data of Flows observed at
2043 the Observation Points given in the
2044 ipfixObservationPointGroupReference. The table lists the
2045 timeouts that specify when the cached metering data is
2046 expired.
2047
2048 On Collectors, the table is not needed."
2049 ::= { ipfixMainObjects 5 }
2050
2051 ipfixMeteringProcessEntry OBJECT-TYPE
2052 SYNTAX IpfixMeteringProcessEntry
2053 MAX-ACCESS not-accessible
2054 STATUS current
2055 DESCRIPTION
2056 "Defines an entry in the ipfixMeteringProcessTable."
2057 INDEX { ipfixMeteringProcessCacheId }
2058 ::= { ipfixMeteringProcessTable 1 }
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068 <span class="grey">Dietz, et al. Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2071
2072
2073 IpfixMeteringProcessEntry ::=
2074 SEQUENCE {
2075 ipfixMeteringProcessCacheId Unsigned32,
2076 ipfixMeteringProcessObservationPointGroupRef Unsigned32,
2077 ipfixMeteringProcessCacheActiveTimeout Unsigned32,
2078 ipfixMeteringProcessCacheInactiveTimeout Unsigned32
2079 }
2080
2081 ipfixMeteringProcessCacheId OBJECT-TYPE
2082 SYNTAX Unsigned32 (1..4294967295)
2083 MAX-ACCESS not-accessible
2084 STATUS current
2085 DESCRIPTION
2086 "Locally arbitrary, but unique identifier of an entry in the
2087 ipfixMeterinProcessTable. The value is expected to remain
2088 constant from a re-initialization of the entity's network
2089 management agent to the next re-initialization."
2090 ::= { ipfixMeteringProcessEntry 1 }
2091
2092 ipfixMeteringProcessObservationPointGroupRef OBJECT-TYPE
2093 SYNTAX Unsigned32
2094 MAX-ACCESS read-only
2095 STATUS current
2096 DESCRIPTION
2097 "The Observation Point Group Id that links this table entry
2098 to the ipfixObservationPointTable. The matching
2099 ipfixObservationPointGroupId in that table gives the
2100 Observation Points used in that cache. If the Observation
2101 Points are unknown, the
2102 ipfixMeteringProcessObservationPointGroupRef MUST be zero."
2103 ::= { ipfixMeteringProcessEntry 2 }
2104
2105 ipfixMeteringProcessCacheActiveTimeout OBJECT-TYPE
2106 SYNTAX Unsigned32
2107 UNITS "seconds"
2108 MAX-ACCESS read-only
2109 STATUS current
2110 DESCRIPTION
2111 "On the Exporter, this object contains the time after which a
2112 Flow is expired (and a Data Record for the template is sent)
2113 even though packets matching this Flow are still received by
2114 the Metering Process. If this value is 0, the Flow is not
2115 prematurely expired."
2116 REFERENCE
2117 "<a href="./rfc5470">RFC 5470</a>, Architecture for IP Flow Information Export,
2118 <a href="#section-5.1.1">Section 5.1.1</a>, item 3."
2119 ::= { ipfixMeteringProcessEntry 3 }
2120
2121
2122
2123
2124 <span class="grey">Dietz, et al. Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2127
2128
2129 ipfixMeteringProcessCacheInactiveTimeout OBJECT-TYPE
2130 SYNTAX Unsigned32
2131 UNITS "seconds"
2132 MAX-ACCESS read-only
2133 STATUS current
2134 DESCRIPTION
2135 "On the Exporter. this object contains the time after which a
2136 Flow is expired (and a Data Record for the template is sent)
2137 when no packets matching this Flow are received by the
2138 Metering Process for the given number of seconds. If this
2139 value is zero, the Flow is expired immediately, i.e., a Data
2140 Record is sent for every packet received by the Metering
2141 Process."
2142 REFERENCE
2143 "<a href="./rfc5470">RFC 5470</a>, Architecture for IP Flow Information Export,
2144 <a href="#section-5.1.1">Section 5.1.1</a>, item 1"
2145 ::= { ipfixMeteringProcessEntry 4 }
2146
2147 --------------------------------------------------------------------
2148 -- 1.1.6: Observation Point Table
2149 --------------------------------------------------------------------
2150 ipfixObservationPointTable OBJECT-TYPE
2151 SYNTAX SEQUENCE OF IpfixObservationPointEntry
2152 MAX-ACCESS not-accessible
2153 STATUS current
2154 DESCRIPTION
2155 "This table lists the Observation Points used within an
2156 Exporter by the Metering Process. The index
2157 ipfixObservationPointGroupId groups Observation Points
2158 and is referenced in the Metering Process table.
2159
2160 On Collectors this table is not needed."
2161 ::= { ipfixMainObjects 6 }
2162
2163 ipfixObservationPointEntry OBJECT-TYPE
2164 SYNTAX IpfixObservationPointEntry
2165 MAX-ACCESS not-accessible
2166 STATUS current
2167 DESCRIPTION
2168 "Defines an entry in the ipfixObservationPointTable."
2169 INDEX {
2170 ipfixObservationPointGroupId,
2171 ipfixObservationPointIndex
2172 }
2173 ::= { ipfixObservationPointTable 1 }
2174
2175
2176
2177
2178
2179
2180 <span class="grey">Dietz, et al. Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2183
2184
2185 IpfixObservationPointEntry ::=
2186 SEQUENCE {
2187 ipfixObservationPointGroupId Unsigned32,
2188 ipfixObservationPointIndex Unsigned32,
2189 ipfixObservationPointObservationDomainId Unsigned32,
2190 ipfixObservationPointPhysicalEntity PhysicalIndexOrZero,
2191 ipfixObservationPointPhysicalInterface InterfaceIndexOrZero,
2192 ipfixObservationPointPhysicalEntityDirection INTEGER
2193 }
2194
2195 ipfixObservationPointGroupId OBJECT-TYPE
2196 SYNTAX Unsigned32 (1..4294967295)
2197 MAX-ACCESS not-accessible
2198 STATUS current
2199 DESCRIPTION
2200 "Locally arbitrary, but unique identifier of an entry in the
2201 ipfixObservationPointTable. The value is expected to remain
2202 constant from a re-initialization of the entity's network
2203 management agent to the next re-initialization.
2204
2205 This index represents a group of Observation Points.
2206
2207 The special value of 0 MUST NOT be used within this table
2208 but is reserved for the usage in the
2209 ipfixMeteringProcessTable. An index of 0 for the
2210 ipfixObservationPointGroupReference index in that table
2211 indicates that an Observation Point is unknown or
2212 unspecified for a Metering Process cache."
2213 ::= { ipfixObservationPointEntry 1 }
2214
2215 ipfixObservationPointIndex OBJECT-TYPE
2216 SYNTAX Unsigned32 (1..4294967295)
2217 MAX-ACCESS not-accessible
2218 STATUS current
2219 DESCRIPTION
2220 "Locally arbitrary, but unique identifier of an entry in the
2221 ipfixObservationPointTable. The value is expected to remain
2222 constant from a re-initialization of the entity's network
2223 management agent to the next re-initialization.
2224
2225 This index represents a single Observation Point in an
2226 Observation Point group."
2227 ::= { ipfixObservationPointEntry 2 }
2228
2229 ipfixObservationPointObservationDomainId OBJECT-TYPE
2230 SYNTAX Unsigned32
2231 MAX-ACCESS read-only
2232 STATUS current
2233
2234
2235
2236 <span class="grey">Dietz, et al. Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2239
2240
2241 DESCRIPTION
2242 "The Id of the Observation Domain in which this
2243 Observation Point is included.
2244
2245 The special value of 0 indicates that the Observation
2246 Points within this group cannot be applied to a single
2247 Observation Domain."
2248 REFERENCE
2249 "<a href="./rfc5101">RFC 5101</a>, Specification of the IP Flow Information Export
2250 (IPFIX) Protocol for the Exchange of IP
2251 Traffic Flow Information, <a href="#section-3.1">Section 3.1</a>."
2252 ::= { ipfixObservationPointEntry 3 }
2253
2254 ipfixObservationPointPhysicalEntity OBJECT-TYPE
2255 SYNTAX PhysicalIndexOrZero
2256 MAX-ACCESS read-only
2257 STATUS current
2258 DESCRIPTION
2259 "This object contains the index of a physical entity in
2260 the ENTITY MIB. This physical entity is the given
2261 Observation Point. If such a physical entity cannot be
2262 specified or is not known, then the object is zero."
2263 ::= { ipfixObservationPointEntry 4 }
2264
2265 ipfixObservationPointPhysicalInterface OBJECT-TYPE
2266 SYNTAX InterfaceIndexOrZero
2267 MAX-ACCESS read-only
2268 STATUS current
2269 DESCRIPTION
2270 "This object contains the index of a physical interface in
2271 the IF MIB. This physical interface is the given
2272 Observation Point. If such a physical interface cannot be
2273 specified or is not known, then the object is zero.
2274
2275 This object MAY be used stand alone or in addition to
2276 ipfixObservationPointPhysicalEntity. If
2277 ipfixObservationPointPhysicalEntity is not zero, this object
2278 MUST point to the same physical interface that is
2279 referenced in ipfixObservationPointPhysicalEntity.
2280 Otherwise, it may reference any interface in the IF MIB."
2281 ::= { ipfixObservationPointEntry 5 }
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292 <span class="grey">Dietz, et al. Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2295
2296
2297 ipfixObservationPointPhysicalEntityDirection OBJECT-TYPE
2298 SYNTAX INTEGER {
2299 unknown(0),
2300 ingress(1),
2301 egress(2),
2302 both(3)
2303 }
2304 MAX-ACCESS read-only
2305 STATUS current
2306 DESCRIPTION
2307 "The direction of the Flow that is monitored on the given
2308 physical entity. The following values are valid:
2309
2310 unknown(0)
2311 This value MUST be used if a direction is not
2312 known for the given physical entity.
2313
2314 ingress(1)
2315 This value is used for monitoring incoming Flows on the
2316 given physical entity.
2317
2318 egress(2)
2319 This value is used for monitoring outgoing Flows on the
2320 given physical entity.
2321
2322 both(3)
2323 This value is used for monitoring incoming and outgoing
2324 Flows on the given physical entity."
2325 ::= { ipfixObservationPointEntry 6 }
2326
2327 --------------------------------------------------------------------
2328 -- 1.1.7: Selection Process Table
2329 --------------------------------------------------------------------
2330 ipfixSelectionProcessTable OBJECT-TYPE
2331 SYNTAX SEQUENCE OF IpfixSelectionProcessEntry
2332 MAX-ACCESS not-accessible
2333 STATUS current
2334 DESCRIPTION
2335 "This table contains Selector Functions connected to a
2336 Metering Process by the index ipfixMeteringProcessCacheId.
2337 The Selector Functions are grouped into Selection Processes
2338 by the ipfixSelectionProcessIndex. The Selector Functions
2339 are applied within the Selection Process to the packets
2340 observed for the given Metering Process cache in increasing
2341 order implied by the ipfixSelectionProcessSelectorIndex.
2342 This means Selector Functions with lower
2343 ipfixSelectionProcessSelectorIndex are applied first. The
2344 remaining packets are accounted for in Flow Records.
2345
2346
2347
2348 <span class="grey">Dietz, et al. Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2351
2352
2353 Since IPFIX does not define any Selector Function (except
2354 selecting every packet), this is a placeholder for future
2355 use and a guideline for implementing enterprise-specific
2356 Selector Function objects.
2357
2358 The following object tree should visualize how the
2359 Selector Function objects should be implemented:
2360
2361 ipfixSelectorFunctions
2362 |
2363 +- ipfixFuncSelectAll
2364 | |
2365 | +- ipfixFuncSelectAllAvail (is the function available?)
2366 |
2367 +- ipfixFuncF2
2368 | |
2369 | +- ipfixFuncF2Avail (is the function F2 available?)
2370 | |
2371 | +- ipfixFuncF2Parameters (a table with parameters)
2372 ...
2373 |
2374 +- ipfixFunFn...
2375
2376 If a Selector Function takes parameters, the MIB should
2377 contain a table with an entry for each set of parameters
2378 used at the Exporter."
2379 ::= { ipfixMainObjects 7 }
2380
2381 ipfixSelectionProcessEntry OBJECT-TYPE
2382 SYNTAX IpfixSelectionProcessEntry
2383 MAX-ACCESS not-accessible
2384 STATUS current
2385 DESCRIPTION
2386 "Defines an entry in the ipfixSelectionProcessTable."
2387 INDEX {
2388 ipfixMeteringProcessCacheId,
2389 ipfixSelectionProcessIndex,
2390 ipfixSelectionProcessSelectorIndex
2391 }
2392 ::= { ipfixSelectionProcessTable 1 }
2393
2394 IpfixSelectionProcessEntry ::= SEQUENCE {
2395 ipfixSelectionProcessIndex Unsigned32,
2396 ipfixSelectionProcessSelectorIndex Unsigned32,
2397 ipfixSelectionProcessSelectorFunction OBJECT IDENTIFIER
2398 }
2399
2400
2401
2402
2403
2404 <span class="grey">Dietz, et al. Standards Track [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2407
2408
2409 ipfixSelectionProcessIndex OBJECT-TYPE
2410 SYNTAX Unsigned32 (1..4294967295)
2411 MAX-ACCESS not-accessible
2412 STATUS current
2413 DESCRIPTION
2414 "Locally arbitrary, but unique identifier of an entry in the
2415 ipfixSelectionProcessTable. The value is expected to remain
2416 constant from a re-initialization of the entity's network
2417 management agent to the next re-initialization."
2418 ::= { ipfixSelectionProcessEntry 1 }
2419
2420 ipfixSelectionProcessSelectorIndex OBJECT-TYPE
2421 SYNTAX Unsigned32 (1..4294967295)
2422 MAX-ACCESS not-accessible
2423 STATUS current
2424 DESCRIPTION
2425 "Index specifying the order in which the referenced
2426 ipfixSelctionProcessSelectorFunctions are applied to the
2427 observed packet stream within the given Selection Process
2428 (identified by the ipfixSelectionProcessIndex). The
2429 Selector Functions are applied in increasing order, i.e.,
2430 Selector Functions with lower index are applied first."
2431 ::= { ipfixSelectionProcessEntry 2 }
2432
2433 ipfixSelectionProcessSelectorFunction OBJECT-TYPE
2434 SYNTAX OBJECT IDENTIFIER
2435 MAX-ACCESS read-only
2436 STATUS current
2437 DESCRIPTION
2438 "The pointer to the Selector Function used at position
2439 ipfixSelectionProcessSelectorIndex in the list of Selector
2440 Functions for the Metering Process cache specified by the
2441 index ipfixMeteringProcessCacheId and for the given
2442 Selection Process (identified by the
2443 ipfixSelectionProcessIndex).
2444
2445 This usually points to an object in the IPFIX SELECTOR MIB.
2446 If the Selector Function does not take parameters, then it
2447 MUST point to the root of the function subtree. If the
2448 function takes parameters, then it MUST point to an entry
2449 in the parameter table of the Selector Function."
2450 ::= { ipfixSelectionProcessEntry 3 }
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460 <span class="grey">Dietz, et al. Standards Track [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2463
2464
2465 --------------------------------------------------------------------
2466 -- 1.2.1: Transport Session Statistics Table
2467 --------------------------------------------------------------------
2468 ipfixTransportSessionStatsTable OBJECT-TYPE
2469 SYNTAX SEQUENCE OF IpfixTransportSessionStatsEntry
2470 MAX-ACCESS not-accessible
2471 STATUS current
2472 DESCRIPTION
2473 "This table lists Transport Sessions statistics between
2474 Exporting Processes and Collecting Processes."
2475 ::= { ipfixStatistics 1 }
2476
2477 ipfixTransportSessionStatsEntry OBJECT-TYPE
2478 SYNTAX IpfixTransportSessionStatsEntry
2479 MAX-ACCESS not-accessible
2480 STATUS current
2481 DESCRIPTION
2482 "Defines an entry in the ipfixTransportSessionStatsTable."
2483 AUGMENTS { ipfixTransportSessionEntry }
2484 ::= { ipfixTransportSessionStatsTable 1 }
2485
2486 IpfixTransportSessionStatsEntry ::=
2487 SEQUENCE {
2488 ipfixTransportSessionRate Gauge32,
2489 ipfixTransportSessionPackets Counter64,
2490 ipfixTransportSessionBytes Counter64,
2491 ipfixTransportSessionMessages Counter64,
2492 ipfixTransportSessionDiscardedMessages Counter64,
2493 ipfixTransportSessionRecords Counter64,
2494 ipfixTransportSessionTemplates Counter64,
2495 ipfixTransportSessionOptionsTemplates Counter64,
2496 ipfixTransportSessionDiscontinuityTime TimeStamp
2497 }
2498
2499 ipfixTransportSessionRate OBJECT-TYPE
2500 SYNTAX Gauge32
2501 UNITS "bytes/second"
2502 MAX-ACCESS read-only
2503 STATUS current
2504 DESCRIPTION
2505 "The number of bytes per second received by the
2506 Collector or transmitted by the Exporter. A
2507 value of zero (0) means that no packets were sent or
2508 received, yet. This object is updated every second."
2509 ::= { ipfixTransportSessionStatsEntry 1 }
2510
2511
2512
2513
2514
2515
2516 <span class="grey">Dietz, et al. Standards Track [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2519
2520
2521 ipfixTransportSessionPackets OBJECT-TYPE
2522 SYNTAX Counter64
2523 UNITS "packets"
2524 MAX-ACCESS read-only
2525 STATUS current
2526 DESCRIPTION
2527 "The number of packets received by the Collector
2528 or transmitted by the Exporter.
2529 Discontinuities in the value of this counter can occur at
2530 re-initialization of the management system and at other
2531 times as indicated by the value of
2532 ipfixTransportSessionDiscontinuityTime."
2533 ::= { ipfixTransportSessionStatsEntry 2 }
2534
2535 ipfixTransportSessionBytes OBJECT-TYPE
2536 SYNTAX Counter64
2537 UNITS "bytes"
2538 MAX-ACCESS read-only
2539 STATUS current
2540 DESCRIPTION
2541 "The number of bytes received by the Collector
2542 or transmitted by the Exporter.
2543 Discontinuities in the value of this counter can occur at
2544 re-initialization of the management system and at other
2545 times as indicated by the value of
2546 ipfixTransportSessionDiscontinuityTime."
2547 ::= { ipfixTransportSessionStatsEntry 3 }
2548
2549 ipfixTransportSessionMessages OBJECT-TYPE
2550 SYNTAX Counter64
2551 MAX-ACCESS read-only
2552 STATUS current
2553 DESCRIPTION
2554 "The number of IPFIX Messages received by the
2555 Collector or transmitted by the Exporter.
2556 Discontinuities in the value of this counter can occur at
2557 re-initialization of the management system and at other
2558 times as indicated by the value of
2559 ipfixTransportSessionDiscontinuityTime."
2560 ::= { ipfixTransportSessionStatsEntry 4 }
2561
2562 ipfixTransportSessionDiscardedMessages OBJECT-TYPE
2563 SYNTAX Counter64
2564 MAX-ACCESS read-only
2565 STATUS current
2566
2567
2568
2569
2570
2571
2572 <span class="grey">Dietz, et al. Standards Track [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2575
2576
2577 DESCRIPTION
2578 "The number of received IPFIX Message that are malformed,
2579 cannot be decoded, are received in the wrong order, or are
2580 missing according to the sequence number.
2581
2582 If used at the Exporter, the number of messages that could
2583 not be sent due to, e.g., internal buffer overflows, network
2584 congestion, or routing issues.
2585 Discontinuities in the value of this counter can occur at
2586 re-initialization of the management system and at other
2587 times as indicated by the value of
2588 ipfixTransportSessionDiscontinuityTime."
2589 ::= { ipfixTransportSessionStatsEntry 5 }
2590
2591 ipfixTransportSessionRecords OBJECT-TYPE
2592 SYNTAX Counter64
2593 MAX-ACCESS read-only
2594 STATUS current
2595 DESCRIPTION
2596 "The number of Data Records received by the Collector or
2597 transmitted by the Exporter.
2598 Discontinuities in the value of this counter can occur at
2599 re-initialization of the management system and at other
2600 times as indicated by the value of
2601 ipfixTransportSessionDiscontinuityTime."
2602 ::= { ipfixTransportSessionStatsEntry 6 }
2603
2604 ipfixTransportSessionTemplates OBJECT-TYPE
2605 SYNTAX Counter64
2606 MAX-ACCESS read-only
2607 STATUS current
2608 DESCRIPTION
2609 "The number of Templates received or transmitted.
2610 Discontinuities in the value of this counter can occur at
2611 re-initialization of the management system and at other
2612 times as indicated by the value of
2613 ipfixTransportSessionDiscontinuityTime."
2614 ::= { ipfixTransportSessionStatsEntry 7 }
2615
2616 ipfixTransportSessionOptionsTemplates OBJECT-TYPE
2617 SYNTAX Counter64
2618 MAX-ACCESS read-only
2619 STATUS current
2620
2621
2622
2623
2624
2625
2626
2627
2628 <span class="grey">Dietz, et al. Standards Track [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2631
2632
2633 DESCRIPTION
2634 "The number of Options Templates received or transmitted.
2635 Discontinuities in the value of this counter can occur at
2636 re-initialization of the management system and at other
2637 times as indicated by the value of
2638 ipfixTransportSessionDiscontinuityTime."
2639 ::= { ipfixTransportSessionStatsEntry 8 }
2640
2641 ipfixTransportSessionDiscontinuityTime OBJECT-TYPE
2642 SYNTAX TimeStamp
2643 MAX-ACCESS read-only
2644 STATUS current
2645 DESCRIPTION
2646 "The value of sysUpTime at the most recent occasion at which
2647 one or more of the Transport Session counters suffered a
2648 discontinuity.
2649 A value of zero indicates no such discontinuity has
2650 occurred since the last re-initialization of the local
2651 management subsystem."
2652 ::= { ipfixTransportSessionStatsEntry 9 }
2653
2654 --------------------------------------------------------------------
2655 -- 1.2.2: Template Statistics Table
2656 --------------------------------------------------------------------
2657 ipfixTemplateStatsTable OBJECT-TYPE
2658 SYNTAX SEQUENCE OF IpfixTemplateStatsEntry
2659 MAX-ACCESS not-accessible
2660 STATUS current
2661 DESCRIPTION
2662 "This table lists statistics objects per Template."
2663 ::= { ipfixStatistics 2 }
2664
2665 ipfixTemplateStatsEntry OBJECT-TYPE
2666 SYNTAX IpfixTemplateStatsEntry
2667 MAX-ACCESS not-accessible
2668 STATUS current
2669 DESCRIPTION
2670 "Defines an entry in the ipfixTemplateStatsTable."
2671 AUGMENTS { ipfixTemplateEntry }
2672 ::= { ipfixTemplateStatsTable 1 }
2673
2674 IpfixTemplateStatsEntry ::=
2675 SEQUENCE {
2676 ipfixTemplateDataRecords Counter64,
2677 ipfixTemplateDiscontinuityTime TimeStamp
2678 }
2679
2680
2681
2682
2683
2684 <span class="grey">Dietz, et al. Standards Track [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2687
2688
2689 ipfixTemplateDataRecords OBJECT-TYPE
2690 SYNTAX Counter64
2691 MAX-ACCESS read-only
2692 STATUS current
2693 DESCRIPTION
2694 "The number of Data Records that are transmitted or received
2695 per Template.
2696 Discontinuities in the value of this counter can occur at
2697 re-initialization of the management system, and at other
2698 times as indicated by the value of
2699 ipfixTemplateDiscontinuityTime."
2700 ::= { ipfixTemplateStatsEntry 1 }
2701
2702 ipfixTemplateDiscontinuityTime OBJECT-TYPE
2703 SYNTAX TimeStamp
2704 MAX-ACCESS read-only
2705 STATUS current
2706 DESCRIPTION
2707 "The value of sysUpTime at the most recent occasion at which
2708 the Template counter suffered a discontinuity.
2709 A value of zero indicates no such discontinuity has
2710 occurred since the last re-initialization of the local
2711 management subsystem."
2712 ::= { ipfixTemplateStatsEntry 2 }
2713
2714 --------------------------------------------------------------------
2715 -- 1.2.3: Metering Process Statistics Table
2716 --------------------------------------------------------------------
2717 ipfixMeteringProcessStatsTable OBJECT-TYPE
2718 SYNTAX SEQUENCE OF IpfixMeteringProcessStatsEntry
2719 MAX-ACCESS not-accessible
2720 STATUS current
2721 DESCRIPTION
2722 "This table lists statistic objects that have data per
2723 Metering Process cache.
2724
2725 On Collectors, this table is not needed."
2726 ::= { ipfixStatistics 3 }
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740 <span class="grey">Dietz, et al. Standards Track [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2743
2744
2745 ipfixMeteringProcessStatsEntry OBJECT-TYPE
2746 SYNTAX IpfixMeteringProcessStatsEntry
2747 MAX-ACCESS not-accessible
2748 STATUS current
2749 DESCRIPTION
2750 "Defines an entry in the ipfixMeteringProcessStatsTable."
2751 AUGMENTS { ipfixMeteringProcessEntry }
2752 ::= { ipfixMeteringProcessStatsTable 1 }
2753
2754 IpfixMeteringProcessStatsEntry ::=
2755 SEQUENCE {
2756 ipfixMeteringProcessCacheActiveFlows Gauge32,
2757 ipfixMeteringProcessCacheUnusedCacheEntries Gauge32,
2758 ipfixMeteringProcessCacheDataRecords Counter64,
2759 ipfixMeteringProcessCacheDiscontinuityTime TimeStamp
2760 }
2761
2762 ipfixMeteringProcessCacheActiveFlows OBJECT-TYPE
2763 SYNTAX Gauge32
2764 MAX-ACCESS read-only
2765 STATUS current
2766 DESCRIPTION
2767 "The number of Flows currently active at this cache."
2768 ::= { ipfixMeteringProcessStatsEntry 1 }
2769
2770 ipfixMeteringProcessCacheUnusedCacheEntries OBJECT-TYPE
2771 SYNTAX Gauge32
2772 MAX-ACCESS read-only
2773 STATUS current
2774 DESCRIPTION
2775 "The number of unused cache entries."
2776 ::= { ipfixMeteringProcessStatsEntry 2 }
2777
2778 ipfixMeteringProcessCacheDataRecords OBJECT-TYPE
2779 SYNTAX Counter64
2780 MAX-ACCESS read-only
2781 STATUS current
2782 DESCRIPTION
2783 "The number of Data Records generated.
2784 Discontinuities in the value of this counter can occur at
2785 re-initialization of the management system and at other
2786 times as indicated by the value of
2787 ipfixTemplateDiscontinuityTime."
2788 ::= { ipfixMeteringProcessStatsEntry 3 }
2789
2790
2791
2792
2793
2794
2795
2796 <span class="grey">Dietz, et al. Standards Track [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2799
2800
2801 ipfixMeteringProcessCacheDiscontinuityTime OBJECT-TYPE
2802 SYNTAX TimeStamp
2803 MAX-ACCESS read-only
2804 STATUS current
2805 DESCRIPTION
2806 "The value of sysUpTime at the most recent occasion at which
2807 the Metering Process counter suffered a discontinuity.
2808 A value of zero indicates no such discontinuity has
2809 occurred since the last re-initialization of the local
2810 management subsystem."
2811 ::= { ipfixMeteringProcessStatsEntry 4 }
2812
2813 --------------------------------------------------------------------
2814 -- 1.2.4: Selection Process Statistics Table
2815 --------------------------------------------------------------------
2816 ipfixSelectionProcessStatsTable OBJECT-TYPE
2817 SYNTAX SEQUENCE OF IpfixSelectionProcessStatsEntry
2818 MAX-ACCESS not-accessible
2819 STATUS current
2820 DESCRIPTION
2821 "This table contains statistics for the Selector Functions
2822 connected to Metering Process by the index
2823 ipfixMeteringProcessCacheId.
2824
2825 The indexes MUST match an entry in the
2826 ipfixSelectionProcessTable."
2827 ::= { ipfixStatistics 4 }
2828
2829 ipfixSelectionProcessStatsEntry OBJECT-TYPE
2830 SYNTAX IpfixSelectionProcessStatsEntry
2831 MAX-ACCESS not-accessible
2832 STATUS current
2833 DESCRIPTION
2834 "Defines an entry in the ipfixSelectionProcessStatsTable."
2835 AUGMENTS { ipfixSelectionProcessEntry }
2836 ::= { ipfixSelectionProcessStatsTable 1 }
2837
2838 IpfixSelectionProcessStatsEntry ::= SEQUENCE {
2839 ipfixSelectionProcessStatsPacketsObserved Counter64,
2840 ipfixSelectionProcessStatsPacketsDropped Counter64,
2841 ipfixSelectionProcessStatsDiscontinuityTime TimeStamp
2842 }
2843
2844 ipfixSelectionProcessStatsPacketsObserved OBJECT-TYPE
2845 SYNTAX Counter64
2846 MAX-ACCESS read-only
2847 STATUS current
2848
2849
2850
2851
2852 <span class="grey">Dietz, et al. Standards Track [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2855
2856
2857 DESCRIPTION
2858 "The number of packets observed at the entry point of the
2859 function. The entry point may be the Observation Point or
2860 the exit point of another Selector Function.
2861 Discontinuities in the value of this counter can occur at
2862 re-initialization of the management system and at other
2863 times as indicated by the value of
2864 ipfixSelectionProcessStatsDiscontinuityTime."
2865 ::= { ipfixSelectionProcessStatsEntry 1 }
2866
2867 ipfixSelectionProcessStatsPacketsDropped OBJECT-TYPE
2868 SYNTAX Counter64
2869 MAX-ACCESS read-only
2870 STATUS current
2871 DESCRIPTION
2872 "The number of packets dropped while selecting packets.
2873 Discontinuities in the value of this counter can occur at
2874 re-initialization of the management system and at other
2875 times as indicated by the value of
2876 ipfixSelectionProcessStatsDiscontinuityTime."
2877 ::= { ipfixSelectionProcessStatsEntry 2 }
2878
2879 ipfixSelectionProcessStatsDiscontinuityTime OBJECT-TYPE
2880 SYNTAX TimeStamp
2881 MAX-ACCESS read-only
2882 STATUS current
2883 DESCRIPTION
2884 "The value of sysUpTime at the most recent occasion at which
2885 one or more of the Selector counters suffered a
2886 discontinuity.
2887 A value of zero indicates no such discontinuity has
2888 occurred since the last re-initialization of the local
2889 management subsystem."
2890 ::= { ipfixSelectionProcessStatsEntry 3 }
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908 <span class="grey">Dietz, et al. Standards Track [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2911
2912
2913 --==================================================================
2914 -- 2: Conformance Information
2915 --==================================================================
2916 ipfixCompliances OBJECT IDENTIFIER ::= { ipfixConformance 1 }
2917 ipfixGroups OBJECT IDENTIFIER ::= { ipfixConformance 2 }
2918
2919 --------------------------------------------------------------------
2920 -- 2.1: Compliance Statements
2921 --------------------------------------------------------------------
2922 ipfixCollectorCompliance MODULE-COMPLIANCE
2923 STATUS current
2924 DESCRIPTION
2925 "An implementation that builds an IPFIX Collector
2926 that complies to this module MUST implement the objects
2927 defined in the mandatory group ipfixCommonGroup.
2928
2929 The implementation of all objects in the other groups is
2930 optional and depends on the corresponding functionality
2931 implemented in the equipment.
2932
2933 An implementation that is compliant to this MIB module
2934 is limited to use only the values TCP (6), UDP (17), and
2935 SCTP (132) in the ipfixTransportSessionProtocol object
2936 because these are the only protocol currently specified
2937 for usage within IPFIX (see <a href="./rfc5101">RFC 5101</a>)."
2938 MODULE -- this module
2939 MANDATORY-GROUPS {
2940 ipfixCommonGroup
2941 }
2942
2943 GROUP ipfixCommonStatsGroup
2944 DESCRIPTION
2945 "These objects should be implemented if the statistics
2946 function is implemented in the equipment."
2947 ::= { ipfixCompliances 1 }
2948
2949 ipfixExporterCompliance MODULE-COMPLIANCE
2950 STATUS current
2951 DESCRIPTION
2952 "An implementation that builds an IPFIX Exporter that
2953 complies to this module MUST implement the objects defined
2954 in the mandatory group ipfixCommonGroup. The implementation
2955 of all other objects depends on the implementation of the
2956 corresponding functionality in the equipment."
2957 MODULE -- this module
2958
2959
2960
2961
2962
2963
2964 <span class="grey">Dietz, et al. Standards Track [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
2967
2968
2969 MANDATORY-GROUPS {
2970 ipfixCommonGroup,
2971 ipfixExporterGroup
2972 }
2973
2974 GROUP ipfixCommonStatsGroup
2975 DESCRIPTION
2976 "These objects should be implemented if the statistics
2977 function is implemented in the equipment."
2978
2979 GROUP ipfixExporterStatsGroup
2980 DESCRIPTION
2981 "These objects MUST be implemented if statistical functions
2982 are implemented on the equipment."
2983 ::= { ipfixCompliances 2 }
2984
2985 --------------------------------------------------------------------
2986 -- 2.2: MIB Grouping
2987 --------------------------------------------------------------------
2988 ipfixCommonGroup OBJECT-GROUP
2989 OBJECTS {
2990 ipfixTransportSessionProtocol,
2991 ipfixTransportSessionSourceAddressType,
2992 ipfixTransportSessionSourceAddress,
2993 ipfixTransportSessionDestinationAddressType,
2994 ipfixTransportSessionDestinationAddress,
2995 ipfixTransportSessionSourcePort,
2996 ipfixTransportSessionDestinationPort,
2997 ipfixTransportSessionSctpAssocId,
2998 ipfixTransportSessionDeviceMode,
2999 ipfixTransportSessionTemplateRefreshTimeout,
3000 ipfixTransportSessionOptionsTemplateRefreshTimeout,
3001 ipfixTransportSessionTemplateRefreshPacket,
3002 ipfixTransportSessionOptionsTemplateRefreshPacket,
3003 ipfixTransportSessionIpfixVersion,
3004 ipfixTransportSessionStatus,
3005
3006 ipfixTemplateSetId,
3007 ipfixTemplateAccessTime,
3008
3009 ipfixTemplateDefinitionIeId,
3010 ipfixTemplateDefinitionIeLength,
3011 ipfixTemplateDefinitionEnterpriseNumber,
3012 ipfixTemplateDefinitionFlags
3013 }
3014 STATUS current
3015
3016
3017
3018
3019
3020 <span class="grey">Dietz, et al. Standards Track [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3023
3024
3025 DESCRIPTION
3026 "The main IPFIX objects."
3027 ::= { ipfixGroups 1 }
3028
3029 ipfixCommonStatsGroup OBJECT-GROUP
3030 OBJECTS {
3031 ipfixTransportSessionRate,
3032 ipfixTransportSessionPackets,
3033 ipfixTransportSessionBytes,
3034 ipfixTransportSessionMessages,
3035 ipfixTransportSessionDiscardedMessages,
3036 ipfixTransportSessionRecords,
3037 ipfixTransportSessionTemplates,
3038 ipfixTransportSessionOptionsTemplates,
3039 ipfixTransportSessionDiscontinuityTime,
3040
3041 ipfixTemplateDataRecords,
3042 ipfixTemplateDiscontinuityTime
3043 }
3044 STATUS current
3045 DESCRIPTION
3046 "Common statistical objects."
3047 ::= { ipfixGroups 2 }
3048
3049 ipfixExporterGroup OBJECT-GROUP
3050 OBJECTS {
3051 ipfixExportMemberType,
3052
3053 ipfixMeteringProcessObservationPointGroupRef,
3054 ipfixMeteringProcessCacheActiveTimeout,
3055 ipfixMeteringProcessCacheInactiveTimeout,
3056
3057 ipfixObservationPointObservationDomainId,
3058 ipfixObservationPointPhysicalEntity,
3059 ipfixObservationPointPhysicalInterface,
3060 ipfixObservationPointPhysicalEntityDirection,
3061
3062 ipfixSelectionProcessSelectorFunction
3063 }
3064 STATUS current
3065 DESCRIPTION
3066 "The main objects for Exporters."
3067 ::= { ipfixGroups 3 }
3068
3069
3070
3071
3072
3073
3074
3075
3076 <span class="grey">Dietz, et al. Standards Track [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3079
3080
3081 ipfixExporterStatsGroup OBJECT-GROUP
3082 OBJECTS {
3083 ipfixMeteringProcessCacheActiveFlows,
3084 ipfixMeteringProcessCacheUnusedCacheEntries,
3085 ipfixMeteringProcessCacheDataRecords,
3086 ipfixMeteringProcessCacheDiscontinuityTime,
3087
3088 ipfixSelectionProcessStatsPacketsObserved,
3089 ipfixSelectionProcessStatsPacketsDropped,
3090 ipfixSelectionProcessStatsDiscontinuityTime
3091 }
3092 STATUS current
3093 DESCRIPTION
3094 "The statistical objects for Exporters."
3095 ::= { ipfixGroups 4 }
3096
3097 END
3098
3099 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. IPFIX SELECTOR MIB Definition</span>
3100
3101
3102 IPFIX-SELECTOR-MIB DEFINITIONS ::= BEGIN
3103
3104 IMPORTS
3105 MODULE-IDENTITY, OBJECT-TYPE, mib-2
3106 FROM SNMPv2-SMI -- <a href="./rfc2578">RFC2578</a>
3107 TruthValue
3108 FROM SNMPv2-TC -- <a href="./rfc2579">RFC2579</a>
3109 MODULE-COMPLIANCE, OBJECT-GROUP
3110 FROM SNMPv2-CONF; -- <a href="./rfc2580">RFC2580</a>
3111
3112 ipfixSelectorMIB MODULE-IDENTITY
3113 LAST-UPDATED "201003150000Z" -- 15 March 2010
3114 ORGANIZATION "IETF IPFIX Working Group"
3115 CONTACT-INFO
3116 "WG charter:
3117 <a href="http://www.ietf.org/html.charters/ipfix-charter.html">http://www.ietf.org/html.charters/ipfix-charter.html</a>
3118
3119 Mailing Lists:
3120 General Discussion: [email protected]
3121 To Subscribe: <a href="http://www1.ietf.org/mailman/listinfo/ipfix">http://www1.ietf.org/mailman/listinfo/ipfix</a>
3122 Archive:
3123 <a href="http://www1.ietf.org/mail-archive/web/ipfix/current/index.html">http://www1.ietf.org/mail-archive/web/ipfix/current/index.html</a>
3124
3125
3126
3127
3128
3129
3130
3131
3132 <span class="grey">Dietz, et al. Standards Track [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3135
3136
3137 Editor:
3138 Thomas Dietz
3139 NEC Europe Ltd.
3140 NEC Laboratories Europe
3141 Network Research Division
3142 Kurfuersten-Anlage 36
3143 69115 Heidelberg
3144 Germany
3145 Phone: +49 6221 4342-128
3146 Email: [email protected]
3147
3148 Atsushi Kobayashi
3149 NTT Information Sharing Platform Laboratories
3150 3-9-11 Midori-cho
3151 Musashino-shi
3152 180-8585
3153 Japan
3154 Phone: +81-422-59-3978
3155 Email: [email protected]
3156
3157 Benoit Claise
3158 Cisco Systems, Inc.
3159 De Kleetlaan 6a b1
3160 Degem 1831
3161 Belgium
3162 Phone: +32 2 704 5622
3163 Email: [email protected]
3164
3165 Gerhard Muenz
3166 Technische Universitaet Muenchen
3167 Department of Informatics
3168 Chair for Network Architectures and Services (I8)
3169 Boltzmannstr. 3
3170 85748 Garching
3171 Germany
3172 Phone: +49 89 289-18008
3173 Email: [email protected]
3174 URI: <a href="http://www.net.in.tum.de/~muenz">http://www.net.in.tum.de/~muenz</a>"
3175 DESCRIPTION
3176 "The IPFIX SELECTOR MIB module defines the standard
3177 filtering and sampling functions that can be referenced in
3178 the ipfixSelectorTable of the IPFIX MIB. The subtree
3179 ipfixSelectorFunctions is a placeholder where all standard
3180 filtering and sampling functions should be located.
3181
3182 The IPFIX SELECTOR MIB module is maintained by IANA and can
3183 be extended through Expert Review [<a href="./rfc5226" title="">RFC5226</a>], i.e., review by
3184 one of a group of experts designated by an IETF Area
3185
3186
3187
3188 <span class="grey">Dietz, et al. Standards Track [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3191
3192
3193 Director. The group of experts MUST check the requested MIB
3194 objects for completeness and accuracy of the description.
3195 Requests for MIB objects that duplicate the functionality of
3196 existing objects SHOULD be declined. The smallest available
3197 OID SHOULD be assigned to a new MIB objects. The
3198 specification of new MIB objects SHOULD follow the structure
3199 specified in <a href="./rfc5815">RFC 5815</a> and MUST be published using a
3200 well-established and persistent publication medium. The
3201 experts will initially be drawn from the Working Group
3202 Chairs and document editors of the IPFIX and PSAMP Working
3203 Groups.
3204
3205 Copyright (c) 2010 IETF Trust and the persons identified as
3206 authors of the code. All rights reserved.
3207
3208 Redistribution and use in source and binary forms, with or
3209 without modification, is permitted pursuant to, and subject
3210 to the license terms contained in, the Simplified BSD
3211 License set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's
3212 Legal Provisions Relating to IETF Documents
3213 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>)."
3214
3215 -- Revision history
3216
3217 REVISION "201003150000Z" -- 15 March 2010
3218 DESCRIPTION
3219 "Initial version, published as <a href="./rfc5815">RFC 5815</a>."
3220
3221 ::= { mib-2 194 }
3222
3223 --******************************************************************
3224 -- Top Level Structure of the MIB
3225 --******************************************************************
3226
3227 ipfixSelectorObjects OBJECT IDENTIFIER
3228 ::= { ipfixSelectorMIB 1 }
3229 ipfixSelectorConformance OBJECT IDENTIFIER
3230 ::= { ipfixSelectorMIB 2 }
3231
3232 --==================================================================
3233 -- 1: Objects used by all IPFIX implementations
3234 --==================================================================
3235 --------------------------------------------------------------------
3236 -- 1.1: Packet Selector Functions for IPFIX
3237 --------------------------------------------------------------------
3238 ipfixSelectorFunctions OBJECT IDENTIFIER
3239 ::= { ipfixSelectorObjects 1 }
3240
3241
3242
3243
3244 <span class="grey">Dietz, et al. Standards Track [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3247
3248
3249 --------------------------------------------------------------------
3250 -- 1.1.1: Function 1: Selecting All Packets
3251 --------------------------------------------------------------------
3252 ipfixFuncSelectAll OBJECT IDENTIFIER
3253 ::= { ipfixSelectorFunctions 1 }
3254
3255 ipfixFuncSelectAllAvail OBJECT-TYPE
3256 SYNTAX TruthValue
3257 MAX-ACCESS read-only
3258 STATUS current
3259 DESCRIPTION
3260 "This object indicates the availability of the trivial
3261 function of selecting all packets. This function is always
3262 available."
3263 ::= { ipfixFuncSelectAll 1 }
3264
3265 --==================================================================
3266 -- 2: Conformance Information
3267 --==================================================================
3268 ipfixSelectorCompliances OBJECT IDENTIFIER
3269 ::= { ipfixSelectorConformance 1 }
3270 ipfixSelectorGroups OBJECT IDENTIFIER
3271 ::= { ipfixSelectorConformance 2 }
3272
3273 --------------------------------------------------------------------
3274 -- 2.1: Compliance Statements
3275 --------------------------------------------------------------------
3276 ipfixSelectorBasicCompliance MODULE-COMPLIANCE
3277 STATUS current
3278 DESCRIPTION
3279 "An implementation that builds an IPFIX Exporter that
3280 complies to this module MUST implement the objects defined
3281 in the mandatory group ipfixBasicGroup. The implementation
3282 of all other objects depends on the implementation of the
3283 corresponding functionality in the equipment."
3284 MODULE -- this module
3285 MANDATORY-GROUPS {
3286 ipfixSelectorBasicGroup
3287 }
3288 ::= { ipfixSelectorCompliances 1 }
3289
3290 --------------------------------------------------------------------
3291 -- 2.2: MIB Grouping
3292 --------------------------------------------------------------------
3293 ipfixSelectorBasicGroup OBJECT-GROUP
3294 OBJECTS {
3295 ipfixFuncSelectAllAvail
3296 }
3297
3298
3299
3300 <span class="grey">Dietz, et al. Standards Track [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3303
3304
3305 STATUS current
3306 DESCRIPTION
3307 "The main IPFIX objects."
3308 ::= { ipfixSelectorGroups 1 }
3309
3310 END
3311
3312 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
3313
3314 There are no management objects defined in this MIB module that have
3315 a MAX-ACCESS clause of read-write and/or read-create. So, if these
3316 MIB modules are implemented correctly, then there is no risk that an
3317 intruder can alter or create any management objects of these MIB
3318 modules via direct SNMP SET operations.
3319
3320 Some of the readable objects in these MIB modules (i.e., objects with
3321 a MAX-ACCESS other than not-accessible) may be considered sensitive
3322 or vulnerable in some network environments. It is thus important to
3323 control even GET and/or NOTIFY access to these objects and possibly
3324 to even encrypt the values of these objects when sending them over
3325 the network via SNMP. These are the tables and objects and their
3326 sensitivity/vulnerability:
3327
3328 o ipfixTransportSessionTable - contains configuration data that
3329 might be sensitive because objects in this table may reveal
3330 information about the network infrastructure
3331
3332 o ipfixExportTable - contains configuration data that might be
3333 sensitive because object in this table may reveal information
3334 about the network infrastructure as well
3335
3336 o ipfixMeteringProcessTable - contains configuration data that might
3337 be sensitive because objects in this table may reveal information
3338 about the IPFIX Device itself
3339
3340 o ipfixObservationPointTable - contains configuration data that
3341 might be sensitive because objects in this table may reveal
3342 information about the IPFIX Device itself and the network
3343 infrastructure
3344
3345 o ipfixSelectorFunctions - currently contains no sensitive data but
3346 might want to be secured anyway since it may contain sensitive
3347 data in a future version
3348
3349 All other objects and tables contain no data that is considered
3350 sensitive.
3351
3352
3353
3354
3355
3356 <span class="grey">Dietz, et al. Standards Track [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3359
3360
3361 SNMP versions prior to SNMPv3 did not include adequate security.
3362 Even if the network itself is secure (for example by using IPsec),
3363 even then, there is no control as to who on the secure network is
3364 allowed to access and GET/SET (read/change/create/delete) the objects
3365 in these MIB modules.
3366
3367 It is RECOMMENDED that implementers consider the security features as
3368 provided by the SNMPv3 framework (see <a href="./rfc3410#section-8">[RFC3410] Section&nbsp;8</a>), including
3369 full support for the SNMPv3 cryptographic mechanisms (for
3370 authentication and privacy).
3371
3372 Further, deployment of SNMP versions prior to SNMPv3 is NOT
3373 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
3374 enable cryptographic security. It is then a customer/operator
3375 responsibility to ensure that the SNMP entity giving access to an
3376 instance of these MIB modules is properly configured to give access
3377 to the objects only to those principals (users) that have legitimate
3378 rights to indeed GET or SET (change/create/delete) them.
3379
3380 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span>
3381
3382 The MIB module in this document uses the following IANA-assigned
3383 OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
3384
3385 Descriptor OBJECT IDENTIFIER value
3386 ---------- -----------------------
3387 ipfixMIB { mib-2 193 }
3388 ipfixSelectorMIB { mib-2 194 }
3389
3390 Further on, the whole IPFIX SELECTOR MIB module is maintained by
3391 IANA. Additions to this MIB module are subject to Expert Review
3392 [<a href="./rfc5226" title="">RFC5226</a>], i.e., review by one of a group of experts designated by an
3393 IETF Area Director. The group of experts MUST check the requested
3394 MIB objects for completeness and accuracy of the description.
3395 Requests for MIB objects that duplicate the functionality of existing
3396 objects SHOULD be declined. The smallest available OID SHOULD be
3397 assigned to new MIB objects. The specification of new MIB objects
3398 SHOULD follow the structure specified in <a href="#section-6">Section 6</a> and MUST be
3399 published using a well-established and persistent publication medium.
3400 The experts will initially be drawn from the Working Group Chairs and
3401 document editors of the IPFIX and PSAMP Working Groups.
3402
3403 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgments</span>
3404
3405 This document is a product of the IPFIX Working Group. The authors
3406 would like to thank the following persons: Paul Aitken for his
3407 detailed review, Dan Romascanu and the MIB doctors, and many more,
3408 for the technical reviews and feedback.
3409
3410
3411
3412 <span class="grey">Dietz, et al. Standards Track [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3415
3416
3417 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span>
3418
3419 <span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span>
3420
3421 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
3422 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
3423
3424 [<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J.
3425 Schoenwaelder, Ed., "Structure of Management Information
3426 Version 2 (SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999.
3427
3428 [<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J.
3429 Schoenwaelder, Ed., "Textual Conventions for SMIv2",
3430 STD 58, <a href="./rfc2579">RFC 2579</a>, April 1999.
3431
3432 [<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
3433 "Conformance Statements for SMIv2", STD 58, <a href="./rfc2580">RFC 2580</a>,
3434 April 1999.
3435
3436 [<a id="ref-RFC4001">RFC4001</a>] Daniele, M., Haberman, B., Routhier, S., and J.
3437 Schoenwaelder, "Textual Conventions for Internet Network
3438 Addresses", <a href="./rfc4001">RFC 4001</a>, February 2005.
3439
3440 [<a id="ref-RFC2863">RFC2863</a>] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
3441 MIB", <a href="./rfc2863">RFC 2863</a>, June 2000.
3442
3443 [<a id="ref-RFC3873">RFC3873</a>] Pastor, J. and M. Belinchon, "Stream Control Transmission
3444 Protocol (SCTP) Management Information Base (MIB)",
3445 <a href="./rfc3873">RFC 3873</a>, September 2004.
3446
3447 [<a id="ref-RFC4133">RFC4133</a>] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)",
3448 <a href="./rfc4133">RFC 4133</a>, August 2005.
3449
3450 [<a id="ref-RFC5101">RFC5101</a>] Claise, B., "Specification of the IP Flow Information
3451 Export (IPFIX) Protocol for the Exchange of IP Traffic
3452 Flow Information", <a href="./rfc5101">RFC 5101</a>, January 2008.
3453
3454 [<a id="ref-RFC5102">RFC5102</a>] Quittek, J., Bryant, S., Claise, B., Aitken, P., and J.
3455 Meyer, "Information Model for IP Flow Information Export",
3456 <a href="./rfc5102">RFC 5102</a>, January 2008.
3457
3458 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
3459 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
3460 May 2008.
3461
3462
3463
3464
3465
3466
3467
3468 <span class="grey">Dietz, et al. Standards Track [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3471
3472
3473 <span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span>
3474
3475 [<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D., and B. Stewart,
3476 "Introduction and Applicability Statements for Internet-
3477 Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, December 2002.
3478
3479 [<a id="ref-RFC3917">RFC3917</a>] Quittek, J., Zseby, T., Claise, B., and S. Zander,
3480 "Requirements for IP Flow Information Export (IPFIX)",
3481 <a href="./rfc3917">RFC 3917</a>, October 2004.
3482
3483 [<a id="ref-RFC5470">RFC5470</a>] Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek,
3484 "Architecture for IP Flow Information Export", <a href="./rfc5470">RFC 5470</a>,
3485 March 2009.
3486
3487 [<a id="ref-RFC5472">RFC5472</a>] Zseby, T., Boschi, E., Brownlee, N., and B. Claise, "IP
3488 Flow Information Export (IPFIX) Applicability", <a href="./rfc5472">RFC 5472</a>,
3489 March 2009.
3490
3491 [<a id="ref-RFC5474">RFC5474</a>] Duffield, N., Chiou, D., Claise, B., Greenberg, A.,
3492 Grossglauser, M., and J. Rexford, "A Framework for Packet
3493 Selection and Reporting", <a href="./rfc5474">RFC 5474</a>, March 2009.
3494
3495 [<a id="ref-RFC5475">RFC5475</a>] Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F.
3496 Raspall, "Sampling and Filtering Techniques for IP Packet
3497 Selection", <a href="./rfc5475">RFC 5475</a>, March 2009.
3498
3499 [<a id="ref-RFC5476">RFC5476</a>] Claise, B., Johnson, A., and J. Quittek, "Packet Sampling
3500 (PSAMP) Protocol Specifications", <a href="./rfc5476">RFC 5476</a>, March 2009.
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524 <span class="grey">Dietz, et al. Standards Track [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc5815">RFC 5815</a> IPFIX MIB April 2010</span>
3527
3528
3529 Authors' Addresses
3530
3531 Thomas Dietz (editor)
3532 NEC Europe, Ltd.
3533 NEC Laboratories Europe
3534 Network Research Division
3535 Kurfuersten-Anlage 36
3536 Heidelberg 69115
3537 DE
3538
3539 Phone: +49 6221 4342-128
3540 EMail: [email protected]
3541
3542
3543 Atsushi Kobayashi
3544 NTT Information Sharing Platform Laboratories
3545 3-9-11 Midori-cho
3546 Musashino-shi, Tokyo 180-8585
3547 JA
3548
3549 Phone: +81-422-59-3978
3550 EMail: [email protected]
3551
3552
3553 Benoit Claise
3554 Cisco Systems, Inc.
3555 De Kleetlaan 6a b1
3556 Degem 1831
3557 BE
3558
3559 Phone: +32 2 704 5622
3560 EMail: [email protected]
3561
3562
3563 Gerhard Muenz
3564 Technische Universitaet Muenchen
3565 Department of Informatics
3566 Chair for Network Architectures and Services (I8)
3567 Boltzmannstr. 3
3568 Garching 85748
3569 DE
3570
3571 Phone: +49 89 289-18008
3572 EMail: [email protected]
3573 URI: <a href="http://www.net.in.tum.de/~muenz">http://www.net.in.tum.de/~muenz</a>
3574
3575
3576
3577
3578
3579
3580 Dietz, et al. Standards Track [Page 64]
3581 </pre>