1 / 7

Methodology for IP Flow Information Export Benchmarking

This document presents a comprehensive methodology for benchmarking IP Flow Information Export. It focuses on characterizing flow monitoring performance through defined metrics based on an architectural model. Key standards referenced include RFC 5740 for benchmarking conditions in network devices, RFC 2544 for IPv4, and RFC 5180 for IPv6. The methodology includes tests to assess the handling rate of flow records and the throughput of the forwarding plane while monitoring flows, ensuring data integrity during extensive flow information handling.

eliana-maldonado
Download Presentation

Methodology for IP Flow Information Export Benchmarking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IP Flow Information Accounting and Export Benchmarking Methodologyhttp://www.ietf.org/id/draft-ietf-bmwg-ipflow-meth-00.txtJan NovakCisco Systems Presenting to BMWG @ IETF80 draft-ietf-bmwg-ipflow-meth-00.txt

  2. Document Goal Defines metrics to characterise Flow Monitoring performance based on: - Architecture Model for IP Flow Information Export: RFC5740 Defines conditions to perform Network Devices benchmarking in the presence of Flow Monitoring IPv4 Benchmarking Methodology: RFC2544 IPv6 Benchmarking Methodology: RFC5180 draft-ietf-bmwg-ipflow-meth-00.txt

  3. Test Topology +-----------+ | | | Collector | | | +-----------+ | | +----------+ +-------------+ +----------+ | | | | | | | sender |------->| |-------->| receiver | | | | DUT | | | | | | | | | | receiver |<-------| |<--------| sender | | | | | | | +----------+ +-------------+ +----------+ 30/11/2014 draft-ietf-bmwg-ipflow-meth-00.txt 3

  4. The Concept – DUT IPFIX | Netflow | Others Flow Export Metric: Flow Record rate Flow Monitoring Plane Traffic information Metric: packet rate Forwarding Plane packets 30/11/2014 draft-ietf-bmwg-ipflow-meth-00.txt 4

  5. What are the Benchmarks Flow Monitoring Plane: How many Flow Records the DUT can handle per second without dropping any Flow information and packets – Flow Monitoring Throughput Data Forwarding Plane: RFC2544 Throughput measured in the presence of Flow Monitoring draft-ietf-bmwg-ipflow-meth-00.txt

  6. Pending Changes Remove references to Sflow Remove section 3.5 – 3.6 (SW and HW platforms discussion) draft-ietf-bmwg-ipflow-meth-00.txt

  7. Do we need a separate terminology document ??? draft-ietf-bmwg-ipflow-meth-00.txt

More Related