Benchmarking Methodology for EVPN and PBB-EVPN
draft-kishjac-bmwg-evpntest-07
|
| Document |
Type |
|
Active Internet-Draft (candidate for bmwg WG)
|
|
Last updated |
|
2017-06-05
(latest revision 2017-05-01)
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Call For Adoption By WG Issued
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
INTERNET-DRAFT Kishore Tiruveedhula
Intended Status:Standard Sudhin Jacob
Expires: October 1,2017 Juniper Networks
May 1,2017
Benchmarking Methodology for EVPN and PBB-EVPN
draft-kishjac-bmwg-evpntest-07
Abstract
This document defines the methodologies for benchmarking performance
of EVPN and PBB-EVPN.EVPN is defined in RFC 7432.It is being deployed
in provider network.This document provides the benchmarking
methodologies for EVPN/PBB-EVPN convergence,data plane,control plane
learning of mac.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 1,2017.
Copyright and License Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<Jacob&Kishore> Expires <October 1,2017> [Page 1]
INTERNET DRAFT <draft-kishjac-bmwg-evpntest-06> <May 1,2017>
Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
2.Test Topology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Terminologies . . . . . . . . . . . . . . . . . . . . . . . 5
3. Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 PBB-EVPN Network Setup . . . . . . . . . . . . . . . . . . 5
4. Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . 6
5 Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1.1 To check the time taken to learn the mac address in
DUT . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1.2. To check the time taken to learn X macs from remote
peer by DUT . . . . . . . . . . . . . . . . . . . . . 9
5.1.3. To check the time taken to flush the local entry due
to CE link failure . . . . . . . . . . . . . . . . . . 10
5.1.4. To check the time taken by DUT to flush X routes
learned from remote PE after R1 traffic generator
link failure . ........................................11
5.1.5. To measure the mac ageing time. . . . . . . . . . . . 12
5.1.6. To check the time taken by DUT to age X routes
learned from remote PE after stopping the traffic at
remote PE. ...........................................14
5.1.7. To check the time taken by DUT to learn X routes
from local and X from remote and measure the time
of flood from DUT .................................. . 15
5.1.8. To measure the time taken to elect a new DF by
adding a a MHPE. . . . . . . . . . . . . . . . . . . . 16
5.2 High Availability . . . . . . . . . . . . . . . . . . . 18
5.2.1 To check the whether there is traffic loss due to
routing engine failover for redundancy test. . . . . . 18
5.3 ARP/ND Scaling . . . . . . . . . . . . . . . . . . . . . . 19
5.4 Type 5 Route scaling . . . . . . . . . . . . . . . . . . . 20
6. Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1. To Scale the DUT to N EVI and clear bgp in DUT with out
traffic. . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.2. To Scale the DUT to N EVI and clear bgp in DUT with
Show full document text