-
Notifications
You must be signed in to change notification settings - Fork 37
/
Copy pathipfixcol-nfdump-output.dbk
431 lines (422 loc) · 12.2 KB
/
ipfixcol-nfdump-output.dbk
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
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
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
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
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
<?xml version="1.0" encoding="utf-8"?>
<refentry
xmlns:db="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/1999/xlink http://docbook.org/xml/5.0/xsd/xlink.xsd
http://docbook.org/ns/docbook http://docbook.org/xml/5.0/xsd/docbook.xsd"
version="5.0" xml:lang="en">
<info>
<copyright>
<year>2008-2015</year>
<holder>CESNET, z.s.p.o.</holder>
</copyright>
<date>13 April 2012</date>
<authorgroup>
<author>
<personname>
<firstname>Petr</firstname>
<surname>Kramolis</surname>
</personname>
<email>[email protected]</email>
<contrib>developer</contrib>
</author>
</authorgroup>
<orgname>The Liberouter Project</orgname>
</info>
<refmeta>
<refentrytitle>ipfixcol-nfdump-output</refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo otherclass="manual" class="manual">NFDUMP output plugin for IPFIXcol.</refmiscinfo>
</refmeta>
<refnamediv>
<refname>ipfixcol-nfdump-output</refname>
<refpurpose>NFDUMP output plugin for IPFIXcol.</refpurpose>
</refnamediv>
<refsect1>
<title>Description</title>
<simpara>
The <command>ipfixcol-nfdump-output.so</command> is output plugin for ipfixcol (ipfix collector).
</simpara>
</refsect1>
<refsect1>
<title>Supported IPFIX elements</title>
<simpara>NFDUMP file format is designed to store only certain flow information. So this plug-in
can't store all IPFIX elements to NFDUMP files. There are few elements which MUST be present in IPFIX
record otherwise WHOLE record is ignored and NOT stored at all(this usually means all data records for certain template).
Rest of supported IPFIX elements is optional. IPFIX records can contain unsupported elements too (these elements
are simply ignored). See below for supported IPFIX elements (identified by numbers assigned by IANA)</simpara>
</refsect1>
<refsect1>
<title>Necessary elements</title>
<para>1 - delta byte count</para>
<para>2 - delta packet count</para>
<para>4 - protocol nuber</para>
<para>8, 27 - IPv4 or IPv6 source address</para>
<para>12, 28 - IPv4 or IPv6 destination address</para>
<para>150, 152, 154, 156 - one of these elements to with flow start time-stamp</para>
<para>151, 153, 155 ,157 - one of these elements to with flow end time-stamp</para>
</refsect1>
<refsect1>
<title>Optional elements</title>
<para>3 - Agrregated flows</para>
<para>5 - class of service </para>
<para>6 - TCP flags </para>
<para>7 - source port</para>
<para>9, 29 - IPv4 or IPv6 source address prefix length</para>
<para>10 - ingress interface </para>
<para>11 - destination port </para>
<para>13, 30 - IPv4 or IPv6 destination address prefix length</para>
<para>14 - egress interface</para>
<para>15 - IPv4 next hop</para>
<para>16 - source autonomous system</para>
<para>17 - destination autonomous system</para>
<para>18 - BGP IPv4 next hop</para>
<para>23 - POST delta byte count</para>
<para>24 - POST packet byte count</para>
<para>32 - ICMP type </para>
<para>55 - POST class of service</para>
<para>56 -source MAC</para>
<para>57 - POST destination MAC</para>
<para>58 - VLAN identifier</para>
<para>59 - POST VLAN identifier</para>
<para>61 - flow direction</para>
<para>62 - IPv6 next hop</para>
<para>63 - BGP IPv6 next hop</para>
<para>70-79 - one or more of MPLS labels</para>
<para>80 -destination MAC</para>
<para>81 - POST source MAC</para>
<para>89 - forward status (this is NetFlow element in IPFIX it's only as reserved)</para>
</refsect1>
<refsect1>
<title>Configuration</title>
<simpara>The collector must be configured to use nfdump output plugin in startup.xml configuration (<filename>/etc/ipfixcol/startup.xml</filename>).
The configuration specifies which plugins (destinations) are used by the collector to store data and provides configuration for the plugins themselves.
</simpara>
<simpara><filename>startup.xml</filename> nfdump example</simpara>
<programlisting>
<![CDATA[
<destination>
<name>store data records in NFDUMP file format</name>
<fileWriter>
<fileFormat>nfdump</fileFormat>
<path>storagePath/%o/%Y/%m/%d/</path>
<prefix>nfcapd.</prefix>
<ident>file ident</ident>
<compression>yes</compression>
<dumpInterval>
<timeWindow>300</timeWindow>
<timeAlignment>yes</timeAlignment>
<bufferSize>50000</bufferSize>
</dumpInterval>
</fileWriter>
</destination>
]]>
</programlisting>
<para>
<variablelist>
<varlistentry>
<term>
<command>path</command>
</term>
<listitem>
<simpara>the path element specifies storage direcotry for data
collected by nfdump plugin. Path can contain
format tokens for day, month, obervation id ect. This allows you to
create direcotry hierarchy basedon format tokens.
</simpara>
<variablelist>
<varlistentry>
<term>
<command>%a</command>
</term>
<listitem>
<simpara>Abbreviated weekday name (local-depended). Example: Thu
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%A</command>
</term>
<listitem>
<simpara>Full weekday name (local-depended). Example: Thursday
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%b</command>
</term>
<listitem>
<simpara>Abbreviated month name (local-depended). Example: Aug
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%B</command>
</term>
<listitem>
<simpara>Full month name (local-depended). Example: August
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%c</command>
</term>
<listitem>
<simpara>Date and time representation (local-depended). Example:
Thu Aug 23 14:55:02 2001</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%d</command>
</term>
<listitem>
<simpara>Day of the month (01-31). Example: 23</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%H</command>
</term>
<listitem>
<simpara>Hour in 24h format (00-23). Example: 14</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%I</command>
</term>
<listitem>
<simpara>Hour in 12h format (01-12). Example: 02</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%j</command>
</term>
<listitem>
<simpara>Day of the year (001-366). Example: 235</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%m</command>
</term>
<listitem>
<simpara>Month as a decimal number (01-12). Example: 08
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%M</command>
</term>
<listitem>
<simpara>Minute (00-59). Example: 55</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%o</command>
</term>
<listitem>
<simpara>Observation Domain Id. Example: 1</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%p</command>
</term>
<listitem>
<simpara>AM or PM designation. Example: PM</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%S</command>
</term>
<listitem>
<simpara>Second (00-61). Example: 02</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%U</command>
</term>
<listitem>
<simpara>Week number with the first Sunday as the first day of
week one (00-53). Example: 33</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%w</command>
</term>
<listitem>
<simpara>Weekday as a decimal number with Sunday as 0 (0-6).
Example: 4</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%W</command>
</term>
<listitem>
<simpara>Week number with the first Monday as the first day of
week one (00-53). Example: 34</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%x</command>
</term>
<listitem>
<simpara>Date representation (local-depended). Example: '08/23/01'. This creates 3 subdirectories.
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%X</command>
</term>
<listitem>
<simpara>Time representation (local-depended). Example: 14:55:02</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%y</command>
</term>
<listitem>
<simpara>Year, last two digits (00-99). Example: 01</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%Y</command>
</term>
<listitem>
<simpara>Year. Example: 2001</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%Z</command>
</term>
<listitem>
<simpara>Timezone name or abbreviation. Example: CDT</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>%%</command>
</term>
<listitem>
<simpara>A % sign. Example: %</simpara>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>prefix</command>
</term>
<listitem>
<simpara>Specifies name prefix for output files.</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>ident</command>
</term>
<listitem>
<simpara>Specifies name identification line for nfdump files.</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>compression</command>
</term>
<listitem>
<simpara>LZO compression for data (yes/no)</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>dumpInterval - timeWindow</command>
</term>
<listitem>
<simpara>timeWindow is interval for rotation of NFDUMP files(seconds)</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>dumpInterval - timeAlignment</command>
</term>
<listitem>
<simpara>Align flush time according to timeWindow. For example when
is collector started at 12:43 with 5 min
timeWindow than next flush time is 12:48 but with alignment next flush time
is 12:45. (yes/no)
</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<command>dumpInterval - bufferSize</command>
</term>
<listitem>
<simpara>Specifies how internal buffer size (bytes).
</simpara>
</listitem>
</varlistentry>
</variablelist>
</para>
</refsect1>
<refsect1>
<title>See Also</title>
<para></para>
<para>
<variablelist>
<varlistentry>
<term>
<citerefentry><refentrytitle>ipfixcol</refentrytitle><manvolnum>1</manvolnum></citerefentry>
</term>
<listitem>
<simpara>Man pages</simpara>
</listitem>
</varlistentry>
<varlistentry>
<term>
<link xlink:href="http://www.liberouter.org/technologies/ipfixcol/">http://www.liberouter.org/technologies/ipfixcol/</link>
</term>
<listitem>
<para>IPFIXcol Project Homepage</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<link xlink:href="http://www.liberouter.org">http://www.liberouter.org</link>
</term>
<listitem>
<para>Liberouter web page</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<email>[email protected]</email>
</term>
<listitem>
<para>Support mailing list</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</refsect1>
</refentry>