Chapter 2 Using the NetFlow Collector User Interface
Configuration
Customer Name
The Customer Name key builder resolves the customer name from the input interface field. It has the following attributes:
Attribute
Output name
Field
Allow null value
Description
Column name in output.
ID of the field to obtain from a flow.
If not selected, an error is logged if a flow does not contain the indicated field.
The Customer Name key builder requires configuration in the config/vpn.conf file. You must include one row to correspond to each PE device VPN interface that export NetFlow packets to this NFC server. The rows in this file contains five fields, in the following order: exporting device (PE) IP address, interface name, name of the site to which this interface is connected, CE to which this interface is connected, and customer name. These fields should be separated by commas. See the following example:
The exporting device (PE) IP address and interface name fields are required. You can include empty strings for the remaining fields in each row if those fields do not need to be resolved. For example, if you do not need to specify a site name, the site name fields can be left empty.
Note Each row must contain four commas. Empty fields must be separated with commas.
Egress PE
The Egress PE key builder resolves the egress PE from the BGP nexthop field. It has the following attributes:
Attribute
Output name
Field
Allow null value
Description
Column name in output.
ID of the field to obtain from a flow.
If not selected, an error is logged if a flow does not contain the indicated field.
This key builder requires configuration in the config/peList.conf file. This file should include the loopback addresses or hostnames of all PEs in the network. See the following sample:
#This file is for the
192.168.200.2
192.168.200.3
192.168.200.4
|
| Cisco NetFlow Collector User Guide |
|
| ||
|
|
| ||||
|
|
|
| |||
|
|
|
| |||
