Configuration Mode Commands : SteelHead configuration commands : ip flow-export destination
  
ip flow-export destination
Configures data flow support. Data flow support enables you to collect traffic flow data.
Syntax
[no] ip flow-export destination {<ip-address> | <hostname>} <collector-port> {export-port {aux | primary} | filter ip <ip-address> {netmask <netmask> | port <port>} | filter-enable | template refresh-rate <packets> | template-timeout-rate <minutes> | version <version> | interface {<interface> [capture {all | optimized | passthrough} | lan-addrs {off | on} | rvbd-field-id enable}
Parameters
<ip-address>
Specifies the export IP address the data flow collector is listening on.
<hostname>
Specifies the hostname the data flow collector is listening on.
<collector-port>
Specifies the port the data flow collector is listening on. The default value is 2055.
export-port {aux | primary}
Specifies the interface used to send data flow packets to the collector.
filter ip <ip-address>
Specifies the IP address for filter rules. Optionally, you can configure the netmask or port.
• For IPv4 addresses, use this format: XXX.XXX.XXX.XXX
• For IPv6 addresses, use this format: X:X:X::X
netmask <netmask>
Specifies the IPv4 or IPv6 netmask for filter rules.
port <port>
Specifies the port for filter rules.
filter-enable
Enables filters on the specified collector.
template refresh-rate <packets>
Specifies the number of packets sent after which templates are resent. Applicable only to collector v9.
template-timeout-rate <minutes>
Specifies the duration after which templates are resent. Applicable only to collector v9.
version <version>
Specifies the data flow collector version:
• CascadeFlow - Specifies Cascade 8.4 or later.
• Cascade-comp - Specifies Cascade 8.34 or earlier.
• NetFlow-v5 - Enables ingress flow records (Collector v5).
• NetFlow-v9 - Enables ingress and egress flow records (Collector v9).
The CascadeFlow and CascadeFlow-comp options are enhanced versions of flow export to the SteelCentral. These versions allow automatic discovery and interface grouping for SteelHeads in the SteelCentral NetProfiler or SteelCentral Flow Gateway and support WAN and optimization reports in SteelCentral. For details, see the SteelCentral NetProfiler and NetExpress User’s Guide and the SteelCentral Flow Gateway User Guide.
interface <interface>
Specifies the interface used to capture packets. The data flow collector records sent from the SteelHead appear to be sent from the IP address of the selected interface.
capture {all | optimized | passthrough}
Specifies the type of traffic to capture:
• all - Exports both optimized and nonoptimized traffic.
• optimized - Exports optimized traffic.
• passthrough - Exports pass-through traffic.
lan-addrs {off | on}
Specifies whether the TCP IP addresses and ports reported for optimized flows should contain the original client and server IP addresses and not those of the SteelHead: off displays the SteelHead information; on displays the LAN address information.
The default is to display the IP addresses of the original client and server without the IP address of the SteelHeads.
This option is not applicable to collector v9.
rvbd-field-id enable
Allows collector to use Riverbed field IDs​.
Usage
Before you enable data flow support in your network, you should consider the following:
• Generating data-flow data can utilize large amounts of bandwidth, especially on low-bandwidth links, thereby impacting SteelHead performance.
• You can reduce the amount of data exported by data flow collectors if you export only optimized traffic.
• Data flow only tracks incoming packets (ingress). For collector v9 egress flows are also tracked always.
To troubleshoot your flow export settings:
• Make sure the port configuration matches on the SteelHead and the listening port of the collector.
• Ensure that you can reach the collector from the SteelHead (for example, ping 1.1.1.1 where 1.1.1.1 is the NetFlow collector).
• Verify that your capture settings are on the correct interface and that traffic is flowing through it.
amnesiac (config) # ip flow-export enable
amnesiac (config) # ip flow-export destination 10.2.2.2 2055 interface wan0_0
capture optimized
amnesiac (config) # ip flow-export destination 10.2.2.2 2055 export-port
primary
amnesiac (config) # ip flow-export destination 10.2.2.2 2055 lan-addrs on
amnesiac (config) # show ip flow-export
 
Prior to NetFlow v9, for virtual in-path deployments, because the traffic is arriving and leaving from the same WAN interface, when the SteelHead exports data to a NetFlow collector, all traffic has the WAN interface index. This is the correct behavior because the input interface is the same as the output interface. For NetFlow v9, LAN and WAN interfaces are reported for optimized flows.
For details, see the SteelHead Deployment Guide.
Example
amnesiac (config) # ip flow-export destination 10.2.2.2 2055 interface lan0_0
capture all
amnesiac (config) # ip flow-export destination 10.2.2.2 2055 export-port aux
amnesiac (config) # ip flow-export destination 10.2.2.2 2055 lan-addrs off
Product
SteelHead CX, SteelHead-v, SteelHead-c, Interceptor
Related Commands
show ip