For Information about performance management in the latest version please refer to:
opFlow 3 Scalability Features
| Info |
|---|
| Please note a lot of the below still applies in V3 and is still relevant to analysing the flow volumes you are or will be expecting to receive. |
| Table of Contents |
|---|
Flow Volume - sent from Cisco Device
Cisco devices will tell you the number of flows currently exported, no matter if they were successfully received by a server or not. This can be very useful to help calculate the amount of flow data that will come from a device before sending the flows to an opFlow server.
- Get the current time
- Get the number of flows
- Wait 2 minutesX minutes, for example 2 or 60
- Get the current time
- Get the number of flows
- Do some math, subtract second flow number from first flow number, that is the number of flows for 2 X minutes, divide by 120 X * 60 (so the number of seconds) and you have the number per second. Doing this over more time will give you a better idea of the overall number, it is suggested that you wait much more than 2 minutes
| Code Block |
|---|
router> show clock 11:57:51.155 AEST Wed Apr 2 2014 |
...
| Code Block |
|---|
meatball>sh ip flow export
Flow export v9 is enabled for main cache
Export source and destination details :
VRF ID : Default
Destination(1) 192.168.1.7 (12345)
Destination(2) 192.168.1.42 (12345)
Version 9 flow records
25717645 flows exported in 890173 udp datagrams
0 flows failed due to lack of export packet
0 export packets were sent up to process level
0 export packets were dropped due to no fib
1 export packets were dropped due to adjacency issues
0 export packets were dropped due to fragmentation failures
0 export packets were dropped due to encapsulation fixup failures
|
...
Our clock difference was almost exactly 2 minutes, so we will use that number in the example for our calculations.
To figure out flows / 2 min or flows / second:
...