The following examples show the contents of a modified FlowCloneDef.ini file for a single-NIC server and for a multiple-NIC server environment.
Example: Default Input NIC and Port
In this example, the Flow Cloner uses the first available NIC to send the cloned data to hosts 192.100.0.100 and 192.160.0.100. The destination hosts listen for the data on UDP port 9995.
The example has a line for each host that receives the cloned data. These lines begin with the /dest ip= token, followed by the host IP address. A semicolon precedes the comments at the end of the line.
/use defaults; take default setup
/dest ip=192.100.0.100; send cloned packets to ddev1
/dest ip=192.160.0.100; send cloned packets to gdev3
Example: Custom Input NIC and Port
In this example, the Flow Cloner uses a specified NIC (190.0.0.100) to send the cloned data to the hosts (10.0.0.000, 192.100.0.100, and 192.160.0.100). The Harvesters listen for the original incoming data on UDP port 9994.
Note: If you specify a custom /port value, it must match the harvester listening port and the destination port that you used to configure the flow. The port values must match or no flow data is cloned.
/listen ip=190.0.0.100; Use 190.0.0.100 to send the cloned packets /port=9994; Listen on port 9994 instead of the default port 9995
/dest ip=10.0.0.000 ; send cloned packets to 10.0.0.000
/dest ip=192.100.0.100; send cloned packets to ddev1
/dest ip=192.160.0.100; send cloned packets to gdev3
Example: Custom Input NIC and Destination Port
In this example, the Flow Cloner uses a specified NIC (190.0.0.100) to send the cloned data to host 10.0.0.000. The Harvesters that receive the cloned data listen on UDP port 9996.
/listen ip=190.0.0.100; Use 190.0.0.100 to send the cloned packets /dest port=9996; Listen for the cloned data on port 9996
/dest ip=10.0.0.000 ; send cloned packets to 10.0.0.000
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|