Creating NetFlow Collector Data
This section describes the special requirements for creating NetFlow Collector data files that you can import into NetPlanner. To see if your version is supported by NetPlanner, go to http://support.riverbed.com, follow the links to NetPlanner documentation, and view the system requirements.
For more generation information about importing traffic flows, see "Importing Traffic Flows".
Note: For more information about configuring NetFlow export, go to www.cisco.com and refer to the specific documentation for the NetFlow Collector version you plan to use.
Procedure 2: Creating NetFlow Collector Data Files
-
Create one or more NetFlow Collector data files as described in step 2. (Netflow Collector versions 3.0 through 4.0) or step 3. (NetFlow Collector version 5.0).
For more information about NetFlow data file formats, see the Netflow documentation.
Note: You can configure NetPlanner to import socket, transport-protocol, or TOS information from NetFlow data files, and to create separate traffic flows for specific types of data. For more information, see Importing Socket, Transport Protocol, and TOS Data.
-
(NetFlow Collector versions 3.0 through 4.0 only): Generate the data files, based on the following requirements:
- The file must use one of the following aggregation schemes:
- RouterAS or RouterPrefix
- CallRecord or DetailCallRecord
- AsHostMatrix or DetailHostMatrix
- The file must be in either Format A or Format 2.
- The file must use one of the following aggregation schemes:
-
(NetFlow Collector version 5.0 or greater): Generate the data files, based on the following requirements:
- The file must use one of the following aggregation schemes:
- RouterAS or RouterPrefix
- CallRecord or DetailCallRecord
- AsHostMatrix or DetailHostMatrix
- The data file must be in CSV or mixed (XML and CSV) format. XML-only and compressed data files are not supported.
- The file must use one of the following aggregation schemes:
-
eXpress Data Import can import uncompressed ASCII files only. You might need to manually uncompress a file and/or convert it from binary to ASCII before you can import it.
-
After you create your data files, prepare for the traffic import as described in "Preparing for Import".
Importing Socket, Transport Protocol, and TOS Data
You can configure NetPlanner to import socket, transport-protocol, or TOS information from NetFlow data files, and to create separate traffic flows for specific types of data. The type of data you can import depends on the type of aggregation used in the Netflow data file, as listed in the following table.
Table 3: Supported Aggregation Options for NetFlow Collector Imports
| NetFlow Aggregation | Transport Protocol | Socket | Type of Service |
|---|---|---|---|
| CallRecord | X | X | X |
| DetailHostMatrix | X | X | |
| AsHostMatrix | |||
| DetailCallRecord | X | X | X |
| RouterAS | |||
| RouterPrefix |
For more information, see "Differentiating Traffic Flows".