< draft-kishjac-bmwg-evpnvpwstest-00.txt   draft-kishjac-bmwg-evpnvpwstest-01.txt >
Internet Engineering Task Force S. Jacob, Ed. Internet Engineering Task Force S. Jacob, Ed.
Internet-Draft K. Tiruveedhula Internet-Draft K. Tiruveedhula
Intended status:Informational Juniper Networks Intended status: Standards Track Juniper Networks
Expires: April 11, 2019 October 8, 2018 Expires: August 8, 2019 February 4, 2019
Benchmarking Methodology for EVPN VPWS Benchmarking Methodology for EVPN VPWS
draft-kishjac-bmwg-evpnvpwstest-00 draft-kishjac-bmwg-evpnvpwstest-01
Abstract Abstract
This document defines methodologies for benchmarking EVPN-VPWS This document defines methodologies for benchmarking EVPN-VPWS
performance. EVPN-VPWS is defined in RFC 8214, and is being deployed performance. EVPN-VPWS is defined in RFC 8214, and is being deployed
in Service Provider networks. Specifically this document defines the in Service Provider networks. Specifically this document defines the
methodologies for benchmarking EVPN-VPWS Scale convergence, methodologies for benchmarking EVPN-VPWS Scale convergence,
Scale,Core isolation, high availability and longevity. Scale,Core isolation, high availability and longevity.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 11, 2019. This Internet-Draft will expire on August 8, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 24 skipping to change at page 2, line 24
3.2. How long it takes to remote PE to switch traffic from 3.2. How long it takes to remote PE to switch traffic from
primary to back up path during link failure in CE . . . . 8 primary to back up path during link failure in CE . . . . 8
3.3. How long it takes to remote PE to switch traffic from 3.3. How long it takes to remote PE to switch traffic from
primary to back up path during core failure . . . . . . . 8 primary to back up path during core failure . . . . . . . 8
3.4. How long it takes to primary PE to regain control after 3.4. How long it takes to primary PE to regain control after
the local link flap . . . . . . . . . . . . . . . . . . . 9 the local link flap . . . . . . . . . . . . . . . . . . . 9
4. Activate/deactivate AC's . . . . . . . . . . . . . . . . . . 10 4. Activate/deactivate AC's . . . . . . . . . . . . . . . . . . 10
4.1. To Add M number of attachment circuits. . . . . . . . . 10 4.1. To Add M number of attachment circuits. . . . . . . . . 10
4.2. Deactivate/Activate M number of attachment circuits. . . 10 4.2. Deactivate/Activate M number of attachment circuits. . . 10
5. Scale Convergence . . . . . . . . . . . . . . . . . . . . . . 11 5. Scale Convergence . . . . . . . . . . . . . . . . . . . . . . 11
5.1. To Record the whether there is traffic loss due to 5.1. To measure the packet loss during the core link failure. 11
routing engine failover for redundancy test. . . . . . . 11
6. High Availability . . . . . . . . . . . . . . . . . . . . . . 11 6. High Availability . . . . . . . . . . . . . . . . . . . . . . 11
6.1. To Record the whether there is traffic loss due to 6.1. To Record the whether there is traffic loss due to
routing engine failover for redundancy test. . . . . . . 12 routing engine failover for redundancy test. . . . . . . 12
7. SOAK Test . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. SOAK Test . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1. To Measure the stability of the DUT with scale and 7.1. To Measure the stability of the DUT with scale and
traffic. . . . . . . . . . . . . . . . . . . . . . . . . 12 traffic. . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
10. Security Considerations . . . . . . . . . . . . . . . . . . . 13 10. Security Considerations . . . . . . . . . . . . . . . . . . . 13
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
skipping to change at page 6, line 42 skipping to change at page 6, line 42
Topology 3 Topology 3
Topology Diagram Topology Diagram
Figure 1 Figure 1
There are five routers in the topology. SHPE3, RR/P, MHPE1 and MHPE2 There are five routers in the topology. SHPE3, RR/P, MHPE1 and MHPE2
emulating a service provider network. CE is a customer device emulating a service provider network. CE is a customer device
connected to MHPE1 and MHPE2, it is configured with bridge domains in connected to MHPE1 and MHPE2, it is configured with bridge domains in
different vlans. The router tester is connected to CE and SHPE3.The different vlans. The router tester is connected to CE and SHPE3.The
MHPE1 acts as DUT.The RT will act as sender and receiver.The measurement MHPE1 acts as DUT.The RT will act as sender and receiver.The
will be taken in DUT. measurement will be taken in DUT.
All routers except CE is configured with OSPF/IS-IS,LDP,MPLS,BGP with All routers except CE is configured with OSPF/IS-IS,LDP,MPLS,BGP with
EVPN address family. EVPN address family.
All routers except CE must have IBGP configured with RR acting as All routers except CE must have IBGP configured with RR acting as
route reflector. route reflector.
MHPE1,MHPE2,SHPE3 must be configured with "N" EVPN-VPWS instances MHPE1,MHPE2,SHPE3 must be configured with "N" EVPN-VPWS instances
depends up on the cases. depends up on the cases.
skipping to change at page 7, line 43 skipping to change at page 7, line 43
To Record the time taken to switch from primary to backup during To Record the time taken to switch from primary to backup during
local link failure. local link failure.
Topology : Topology 1 Topology : Topology 1
Procedure: Procedure:
Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA
mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast
packets from CE to MHPE2 AC's working in SA.Then shut the packets from CE to MHPE2 AC's working in SA. Then shut the MHPE2-CE
MHPE2-CE link, so that traffic from CE switches to DUT. link, so that traffic from CE switches to DUT.
Measurement : Measurement :
Measure the time taken to switch the traffic from active to backup, Measure the time taken to switch the traffic from active to backup,
the traffic will flow from MHPE1 to SHPE3. Measure the time taken to the traffic will flow from MHPE1 to SHPE3. Measure the time taken to
switch the traffic. switch the traffic.
Repeat these test and plot the data. The test is repeated for "N" Repeat these test and plot the data. The test is repeated for "N"
times and the values are collected. The switching time is calculated times and the values are collected. The switching time is calculated
by averaging the values obtained from "N" samples. by averaging the values obtained from "N" samples.
skipping to change at page 8, line 25 skipping to change at page 8, line 25
To Record the time taken by remote PE to switch traffic from primary To Record the time taken by remote PE to switch traffic from primary
to backup during CE link failure. to backup during CE link failure.
Topology : Topology 2 Topology : Topology 2
Procedure: Procedure:
Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA
mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast
packets from RT to SHPE3 Ac's.Then shut the MHPE2-CE link, packets from RT to SHPE3 Ac's.Then shut the MHPE2-CE link, this
this failure will be notified to remote PE and traffic switch to failure will be notified to remote PE and traffic switch to backup
backup path. path.
Measurement : Measurement :
Measure the time taken to switch the traffic from active to backup, Measure the time taken to switch the traffic from active to backup,
the traffic will flow from SHPE3 to MHPE1. Measure the time taken to the traffic will flow from SHPE3 to MHPE1. Measure the time taken to
switch the traffic. switch the traffic.
Repeat these test and plot the data. The test is repeated for "N" Repeat these test and plot the data. The test is repeated for "N"
times and the values are collected. The switching time is calculated times and the values are collected. The switching time is calculated
by averaging the values obtained from "N" samples. by averaging the values obtained from "N" samples.
skipping to change at page 9, line 7 skipping to change at page 9, line 7
To Record the time taken by remote PE to switch traffic from primary To Record the time taken by remote PE to switch traffic from primary
to backup during core link failure. to backup during core link failure.
Topology : Topology 2 Topology : Topology 2
Procedure: Procedure:
Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA
mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast
packets from RT to SHPE3 Ac's.Then shut the core link of packets from RT to SHPE3 Ac's.Then shut the core link of MHPE2,this
MHPE2,this failure will be notified to remote PE and traffic switch failure will be notified to remote PE and traffic switch to backup
to backup path. path.
Measurement : Measurement :
Measure the time taken to switch the traffic from active to backup, Measure the time taken to switch the traffic from active to backup,
the traffic will flow from SHPE3 to MHPE1. Measure the time taken to the traffic will flow from SHPE3 to MHPE1. Measure the time taken to
switch the traffic. switch the traffic.
Repeat these test and plot the data. The test is repeated for "N" Repeat these test and plot the data. The test is repeated for "N"
times and the values are collected. The switching time is calculated times and the values are collected. The switching time is calculated
by averaging the values obtained from "N" samples. by averaging the values obtained from "N" samples.
skipping to change at page 10, line 22 skipping to change at page 10, line 22
Objective: Objective:
To measure the performance of the DUT while adding M AC's on the fly. To measure the performance of the DUT while adding M AC's on the fly.
Topology : Topology 3 Topology : Topology 3
Procedure: Procedure:
Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA
mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast
packets from RT to SHPE3 Ac's and send "X" unicast packets packets from RT to SHPE3 to all Ac's and send "X" unicast packets
from CE to MHPE1(DUT),let the DUT is the active and the MHPE2 must be from CE to MHPE1(DUT),let the DUT is the active and the MHPE2 must be
standby. DUT will be forwarding the traffic to CE from SHPE3 and the standby. DUT will be forwarding the traffic to CE from SHPE3 and the
traffic from CE to SHPE3.Then add "M" AC's on SHPE1,DUT and MHPE2 on traffic from CE to SHPE3.Then add "M" AC's on SHPE1,DUT and MHPE2 on
the fly. these AC' must be in SA mode. the fly. these AC' must be in SA mode.
Measurement : Measurement :
There should be 0 traffic loss in existing services while addition of There should be 0 traffic loss in existing services while addition of
these ACs. these ACs.
skipping to change at page 11, line 9 skipping to change at page 11, line 9
packets from RT to SHPE3 to all Ac's and send "X" unicast packets packets from RT to SHPE3 to all Ac's and send "X" unicast packets
from CE to MHPE1(DUT),let the DUT is the active and the MHPE2 must be from CE to MHPE1(DUT),let the DUT is the active and the MHPE2 must be
standby.DUT will be forwarding the traffic to CE and from CE to standby.DUT will be forwarding the traffic to CE and from CE to
SHPE3.Then deactivate "M" AC's on SHPE1,DUT and MHPE2 on the fly. SHPE3.Then deactivate "M" AC's on SHPE1,DUT and MHPE2 on the fly.
these AC' must be removed from forwarding plane. Stop the traffic these AC' must be removed from forwarding plane. Stop the traffic
for these AC's. Activate the AC's in all PE's. then start the for these AC's. Activate the AC's in all PE's. then start the
traffic, measure the time taken by "M" AC's to forward the traffic. traffic, measure the time taken by "M" AC's to forward the traffic.
Measurement : Measurement :
Measure the time taken to forward the traffic.Repeat the test "N" Measure the packet loss in sec during this deactivating/activating
times and plot the data.The packet loss is calculated by averaging AC's.Repeat the test "N" times and plot the data.The packet loss is
the values obtained from "N" samples. calculated by averaging the values obtained from "N" samples.
Time taken by the "M" AC's to forward the traffic = (T1+T2+..Tn/N) packet loss in sec = (T1+T2+..Tn/N)
5. Scale Convergence 5. Scale Convergence
5.1. To Record the whether there is traffic loss due to routing engine 5.1. To measure the packet loss during the core link failure.
failover for redundancy test.
Objective: Objective:
To Measure the convergence at a higher number of AC's To Measure the convergence at a higher number of AC's
Topology : Topology 3 Topology : Topology 3
Procedure: Procedure:
Configure "N'" AC's in SHPE3 and MHPE1,MHPE2, working in SA mode.The Configure "N'" AC's in SHPE3 and MHPE1,MHPE2, working in SA mode.The
scale factor must be in the multiples of thousands. DF election must scale factor must be in the multiples of thousands. DF election must
be priority based. It should not be MOD based DF election. be priority based not on the default RFC 7432, it should not be MOD
Send "X" unicast packets from RT to SHPE3 to all Ac's and send "X" based DF election. Send "X" unicast packets from RT to SHPE3 to all
unicast packets from CE to MHPE1(DUT), let the DUT be the active Ac's and send "X" unicast packets from CE to MHPE1(DUT), let the DUT
and the MHPE2 is standby. DUT will be forwarding is the active and the MHPE2 must be standby. DUT will be forwarding
the traffic to CE and from the SHPE3 and from the CE to SHPE3. the traffic to CE from SHPE3 and from CE to SHPE3.Then flap the core
Then flap the core link of the DUT. link of the DUT.
Measurement : Measurement :
Measure the packet loss in seconds once the core link is Measure the packet loss in seconds once the core link is
restored.Repeat the test "N" times and plot the data.The packet loss restored.Repeat the test "N" times and plot the data.The packet loss
is calculated by averaging the values obtained from "N" samples. is calculated by averaging the values obtained from "N" samples.
Packet loss in sec = (T1+T2+..Tn/N) Packet loss in sec = (T1+T2+..Tn/N)
6. High Availability 6. High Availability
skipping to change at page 12, line 17 skipping to change at page 12, line 17
Objective: Objective:
To record traffic loss during routing engine failover. To record traffic loss during routing engine failover.
Topology : Topology 3 Topology : Topology 3
Procedure: Procedure:
Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA Configure "N" AC's in SHPE3 and MHPE1,MHPE2, working in SA
mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast mode.Ensure MHPE2 is active and DUT is backup PE.Send "X" unicast
packets from RT to SHPE3 to Ac's and send "X" unicast packets packets from RT to SHPE3 to all Ac's and send "X" unicast packets
from CE to MHPE1(DUT),let the DUT is the active and the MHPE2 is the from CE to MHPE1(DUT),let the DUT is the active and the MHPE2 must be
standby. DUT will be forwarding the traffic to CE and from CE to standby. DUT will be forwarding the traffic to CE and from CE to
SHPE3.Then do a routing engine fail-over. SHPE3.Then do a routing engine fail-over.
Measurement : Measurement :
There should be 0 traffic loss which is the ideal case, No change in There should be 0 traffic loss which is the ideal case, No change in
the DF role. DUT should not withdraw any routes.Repeat the test "N" the DF role. DUT should not withdraw any routes.Repeat the test "N"
times and plot the data.The packet loss is calculated by averaging times and plot the data.The packet loss is calculated by averaging
the values obtained from "N" samples. the values obtained from "N" samples.
Packet loss in sec = (T1+T2+..Tn/N) Packet loss in sec = (T1+T2+..Tn/N)
 End of changes. 15 change blocks. 
33 lines changed or deleted 31 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/