A high-speed "Ethernet switching fabric" vendor had built a high-performance switching fabric that could process about 1000 flows/second in each of its 10 GE port. They noticed that in the worst case scenario they had to send about 1000 flows/port every three seconds. Since the data that had to be transmitted became very large, they chose to use an IPFIX based notification (due to its low overhead) scheme for reporting their flow statistics. In order to reduce the overhead further, they also decided to send a group of flow statistics as part of each IPFIX packet.
Since the data that had to be processed was large and the end-users wanted the capability to drill-down from network-wide consolidated reports to flow-level granular reports, they decided to identify a proven vendor for their management system rather than doing it in-house. They realized that their management system should be capable of handling 20,000 IPFIX flow records per second for a network with 576 10 GE ports which became a key criterion in short-listing the vendors.
To meet customer requirements, Dhyan developed "IPFIX data collection and reporting component" to meet the demands of high performance computing marketplace and also provided a detailed walk through to the customer explaining to them that it is actually easy to receive the 20,000 IPFIX flow records. The real challenge however is in the processing engine, which has to process that many flow records and store them in a suitable relational database and generate the desired reports in real-time. Dhyan also went ahead and developed a proof-of-concept of the management system in a couple of weeks time to demonstrate its IPFIX expertise and the capability of their tool to offer both consolidated reports at the overall network level and also be able to drill-down to an individual flow level and also debug any congestion in the network.