idnits 2.17.1 draft-ietf-bmwg-evpntest-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 5 instances of too long lines in the document, the longest one being 62 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 222 has weird spacing: '... Tester sendi...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (September 12, 2018) is 2050 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2544' is defined on line 917, but no explicit reference was found in the text == Unused Reference: 'RFC2899' is defined on line 922, but no explicit reference was found in the text == Unused Reference: 'RFC7432' is defined on line 928, but no explicit reference was found in the text == Unused Reference: 'RFC7623' is defined on line 933, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2544 ** Downref: Normative reference to an Informational RFC: RFC 2899 Summary: 3 errors (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force S. Jacob, Ed. 3 Internet-Draft K. Tiruveedhula 4 Intended status: Standards Track Juniper Networks 5 Expires: March 16, 2019 September 12, 2018 7 Benchmarking Methodology for EVPN and PBB-EVPN 8 draft-ietf-bmwg-evpntest-00 10 Abstract 12 This document defines methodologies for benchmarking EVPN and PBB- 13 EVPN performance. EVPN is defined in RFC 7432, and is being deployed 14 in Service Provider networks. Specifically this document defines the 15 methodologies for benchmarking EVPN/PBB-EVPN convergence, data plane 16 performance, and control plane performance. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on March 16, 2019. 35 Copyright Notice 37 Copyright (c) 2018 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 54 1.2. Terminologies . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Test Topology . . . . . . . . . . . . . . . . . . . . . . . . 4 56 3. Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . 7 57 3.1. How long it takes to learn local mac address in EVPN . . 7 58 3.2. How long it takes to learn local mac address in PBB EVPN 8 59 3.3. How long it takes to learn the remote macs . . . . . . . 8 60 3.4. PBB-EVPN How long it takes to learn the mac from remote 61 peer . . . . . . . . . . . . . . . . . . . . . . . . . . 9 62 3.5. How long it takes to flush the local macs due to CE link 63 flap and measure the relearning rate of MACs . . . . . . 9 64 3.6. PBB-EVPN how long it takes to flush the local macs and 65 measure the relearning rate of macs during PE-CE link 66 flap . . . . . . . . . . . . . . . . . . . . . . . . . . 10 67 3.7. How long it takes to flush the remote macs, due to remote 68 link failure. . . . . . . . . . . . . . . . . . . . . . . 11 69 3.8. PBB-EVPN How long it takes to flush the remote macs due 70 to remote link failure . . . . . . . . . . . . . . . . . 11 71 3.9. To measure the MAC aging time. . . . . . . . . . . . . . 12 72 3.10. PBB-EVPN To measure the MAC aging time. . . . . . . . . . 12 73 3.11. How long it takes to age out the remote macs . . . . . . 13 74 3.12. PBB-EVPN How long it takes to age out the remote macs. . 13 75 3.13. How long it takes to learn both local and remote macs. . 14 76 3.14. PBB-EVPN How long it takes to learn both local and remote 77 macs . . . . . . . . . . . . . . . . . . . . . . . . . . 14 78 4. High Availability . . . . . . . . . . . . . . . . . . . . . . 15 79 4.1. To Record the whether there is traffic loss due to 80 routing engine failover for redundancy test. . . . . . . 15 81 4.2. PBB-EVPN To Record the whether there is traffic loss due 82 to routing engine failover for redundancy test . . . . . 16 83 5. ARP/ND Scale . . . . . . . . . . . . . . . . . . . . . . . . 16 84 5.1. To find ARP/ND scale . . . . . . . . . . . . . . . . . . 16 85 6. Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 86 6.1. To Measure the scale limit of DUT with trigger (Scale 87 without traffic) . . . . . . . . . . . . . . . . . . . . 17 88 6.2. PBB-EVPN To measure the scale limit with trigger. . . . . 17 89 6.3. To measure the convergence time of DUT with scale and 90 traffic. . . . . . . . . . . . . . . . . . . . . . . . . 18 91 6.4. .PBB-EVPN To measure the convergence time of DUT with 92 scale and traffic. . . . . . . . . . . . . . . . . . . . 18 93 7. SOAK Test . . . . . . . . . . . . . . . . . . . . . . . . . . 19 94 7.1. To Measure the stability of the DUT with scale and 95 traffic. . . . . . . . . . . . . . . . . . . . . . . . . 19 96 7.2. PBB-EVPN to measure the stability of DUT with scale and 97 traffic. . . . . . . . . . . . . . . . . . . . . . . . . 20 99 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 100 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 101 10. Security Considerations . . . . . . . . . . . . . . . . . . . 20 102 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 103 11.1. Normative References . . . . . . . . . . . . . . . . . . 21 104 11.2. Informative References . . . . . . . . . . . . . . . . . 21 105 Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 21 106 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 108 1. Introduction 110 EVPN is defined in RFC 7432, and describes BGP MPLS- based Ethernet 111 VPNs (EVPN). PBB-EVPN is defined in RFC 7623, discusses how Ethernet 112 Provider backbone Bridging can be combined with EVPNs to provide a 113 new/combined solution. This draft defines methodologies that can be 114 used to benchmark both RFC 7432 and RFC 7623 solutions. Further, 115 this draft provides methodologies for benchmarking the performance of 116 EVPN data and control planes, MAC learning, MAC flushing, MAC ageing, 117 convergence, high availability, and scale. 119 1.1. Requirements Language 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 1.2. Terminologies 127 MHPE Multi homed Provide Edge router. 129 RR Route Reflector. 131 P Provider Router. 133 CE Customer Router/Devices/Switch. 135 MHPE2 Multi homed Provider Edge router 2. 137 MHPE1 Multi homed Provider Edge router 1. 139 SHPE3 Single homed Provider Edge Router 3. 141 AA EVPN Terminologies AA All-Active. 143 SA EVPN Terminologies SA Single-Active. 145 RT Router Tester. 147 Sub Interface Each physical Interfaces is subdivided in to Logical 148 units. 150 EVI EVPN Instances which will be running on sub interface or physical 151 port of the provider Edge routers. 153 DF Designated Forwarder. 155 ESI Ethernet Segment Identifier. 157 2. Test Topology 159 EVPN/PBB-EVPN Services running on SHPE3, MHPE1 and MHPE2 in Single 160 Active Mode: 162 Topology Diagram 164 | [Traffic Generator ] Router Tester traffic receiver for layer 2 traffic from CE 165 +----------+ 166 | | 167 | SHPE3 | 168 | SHPE3 | 169 +----------+ 170 | 171 |Core link 172 +----------+ 173 | | 174 | RR | 175 | | Route Reflector/Core router 176 +----------+-------------| 177 | | 178 | Core links | 179 +----------+ +-----------+ 180 | | | MHPE2 | 181 | DUT | | | 182 | MHPE1 | | | 183 +----------+ +-----------+ 184 | PE-CE link | 185 +----------+------------ 186 | | 187 | CE | 188 | layer2 | 189 |bridge | 190 +----------+------------ [Traffic Generator](Router Tester sending layer 2 traffic with different VLAN ) 192 Topology 1 193 | [Traffic Generator ] Router Tester sending layer 2 traffic. 194 +----------+ 195 | | 196 | SHPE3 | 197 | SHPE3 | 198 +----------+ 199 | 200 |Core link 201 +----------+ 202 | | 203 | RR | 204 | | Route Reflector/Core router 205 +----------+-------------| 206 | | 207 | Core links | 208 +----------+ +-----------+ 209 | | | MHPE2 | 210 | DUT | | | 211 | MHPE1 | | | 212 +----------+ +-----------+ 213 | PE-CE link | 214 +----------+------------ 215 | | 216 | CE | 217 | layer2 | 218 |bridge | 219 +----------+------------ [Traffic Generator](Router Tester receiver for layer 2 traffic with different vlans.) 221 Topology 2 222 | [Traffic Generator ] Router Tester sending layer 2 bi directional traffic sender/receiver 223 +----------+ 224 | | 225 | SHPE3 | 226 | SHPE3 | 227 +----------+ 228 | 229 |Core link 230 +----------+ 231 | | 232 | RR | 233 | | Route Reflector/Core router 234 +----------+-------------| 235 | | 236 | Core links | 237 +----------+ +-----------+ 238 | | | MHPE2 | 239 | DUT | | | 240 | MHPE1 | | | 241 +----------+ +-----------+ 242 | PE-CE link | 243 +----------+------------ 244 | | 245 | CE | 246 | layer2 | 247 |bridge | 248 +----------+------------ [Traffic Generator](Router Tester sending bi directional layer 2 traffic with different VLAN sender/receiver) 250 Topology 3 252 Topology Diagram 254 Figure 1 256 There are five routers in the topology. SHPE3, RR/P, MHPE1 and MHPE2 257 emulating a service provider network. CE is a customer device 258 connected to MHPE1 and MHPE2, it is configured with bridge domains in 259 different vlans. The router tester is connected to CE and SHPE3.The 260 MHPE1 acts DUT.The RT will act as sender and receiver.The measurement 261 will be taken in DUT. 263 All routers except CE is configured with OSPF/IS-IS,LDP,MPLS,BGP with 264 EVPN address family. 266 All routers except CE must have IBGP configured with RR acting as 267 route reflector. 269 MHPE1,MHPE2,SHPE3 must be configured with "N" EVPN/PBB-EVPN instances 270 depends up on the cases. 272 MHPE1 and MHEPE2 must be configured with ESI per vlan or ESI on IFD. 274 MHPE1 and MHEPE2 are running Single Active mode of EVPN. 276 CE is acting as bridge configured with vlans that is configured on 277 MHPE1,MHPE2,SHPE3. 279 Depends up on the test traffic will be flowing uni directional or bi 280 directional depends on the topology mentioned above. 282 The above configuration will serve as base configuration for all the 283 test cases. 285 3. Test Cases 287 The following tests are conducted to measure the time taken to learn 288 the "X" number of MAC's locally in EVI . The data plane learning of 289 MAC will happen locally from connected interface. The control plane 290 learning of MAC is through BGP advertisements from the remote 291 PE(SHPE3). The control plane learning of "X" MAC. The data plane 292 MAC learning can be measured using the parameters defined in RFC 2889 293 section 5.8. 295 3.1. How long it takes to learn local mac address in EVPN 297 Objective: 299 To Record the time taken to learn the MAC address locally in DUT. 301 Topology : Topology 1 303 Procedure: 305 Send "X" unicast frames from CE to MHPE1(DUT) working in SA mode with 306 "X" different source and destination address from RT. The DUT must 307 learn these "X" macs in data plane. 309 Measurement : 311 Measure the time taken to learn "X" MACs in DUT evpn mac table. The 312 data plane measurement is taken by considering DUT as black box the 313 range of X MAC is known from RT and the same must be learned in DUT, 314 the time taken to learn "X" macs is measured. 316 Repeat these test and plot the data. The test is repeated for "N" 317 times and the values are collected. The mac learning time is 318 calculated by averaging the values obtained from "N" samples. 320 Mac learning in sec = (T1+T2+..Tn/N) 322 3.2. How long it takes to learn local mac address in PBB EVPN 324 Objective: 326 To Record the time taken to learn the MAC address locally. 328 Topology : Topology 1 330 Procedure: 332 Send "X" unicast frames from CE to MHPE1(DUT) working in SA mode with 333 "X" different source and destination address from RT. The DUT must 334 learn "X" macs in data plane. 336 Measurement : 338 Measure the time taken by the DUT to learn the "X" MACs in the data 339 plane. The data plane measurement is taken by considering DUT as 340 black box the range of "X" MAC is known from RT and the same must be 341 learned in DUT, the time taken to learn "X" MAC is measured. Repeat 342 these test and plot the data. The test is repeated for "N" times and 343 the values are collected. The mac learning time is calculated by 344 averaging the values obtained from "N" samples. 346 Mac learning in sec = (T1+T2+..Tn/N) 348 3.3. How long it takes to learn the remote macs 350 Objective: 352 To Record the time taken to learn the remote macs. 354 Topology : Topology 2 356 Procedure: 358 Send X frames with X different SA and DA to SHPE3 from RT. SHPE3 359 will advertise these locally learned macs to MHPE1 and MHPE2 via 360 control plane.Measure the time taken to learn these X MACs from 361 remote peer in DUT EVPN MAC address table.The DUT and MHPE2 are 362 running SA mode. 364 Measurement : 366 Measure the time taken by the DUT to learn the "X" MACs in the data 367 plane.Repeat these test and plot the data.The test is repeated for 368 "N" times and the values are collected.The mac learning time is 369 calculated by averaging the values obtained from "N" samples. 371 Mac learning in sec = (T1+T2+..Tn/N) 373 3.4. PBB-EVPN How long it takes to learn the mac from remote peer 375 Objective: 377 To Record the time taken to learn the remote macs. 379 Topology : Topology 2 381 Procedure: 383 Send X frames with X different SA and DA to SHPE3 from RT.These macs 384 will be flooded to MHPE1 and MHPE2 by SHPE3.The DUT and MHPE2 are 385 running SA mode. 387 Measurement : 389 Measure the time taken to learn X mac address in DUT mac table. 390 Repeat these test and plot the data.The test is repeated for "N" 391 times and the values are collected.The mac learning time is 392 calculated by averaging the values obtained by "N" samples. 394 Mac learning in sec = (T1+T2+..Tn/N) 396 3.5. How long it takes to flush the local macs due to CE link flap and 397 measure the relearning rate of MACs 399 Objective: 401 To record the time taken to flush the mac learned locally and the 402 time taken to relearn the same amount of macs. 404 Topology : Topology 1 405 Procedure: 407 Send X frames with X different SA and DA to DUT from CE using traffic 408 generator. Wait till the MHPE1 learns all X MAC address. Then fail 409 the MHPE1 CE link and measure the time taken to flush these X MACs 410 from the EVPN MAC table. Bring up the link which was made Down(the 411 link between MHPE1 and CE).Measure time taken to relearn it. The DUT 412 and MHPE2 are running SA mode. 414 Measurement : 416 Measure the time taken for flushing these X MAC address. Measure the 417 time taken to relearn the X MACs in DUT. Repeat these test and plot 418 the data. The test is repeated for "N" times and the values are 419 collected. The flush and the relearning time is calculated by 420 averaging the values obtained by "N" samples. 422 Flush time for X Macs in sec = (T1+T2+..Tn/N) Relearning time for X 423 macs in sec = (T1+T2+..Tn/N) 425 3.6. PBB-EVPN how long it takes to flush the local macs and measure the 426 relearning rate of macs during PE-CE link flap 428 Objective: 430 To record the time taken to flush the mac learned locally and the 431 time taken to relearn the same amount of macs. 433 Topology : Topology 1 435 Procedure: 437 Send X frames with X different SA and DA to DUT from CE using traffic 438 generator. Wait till the MHPE1 learn all X MAC address. Then fail 439 the MHPE1 CE link and measure the time taken to flush these X MACs 440 from the PBB-EVPN MAC table. Then bring up the link. Measure the 441 time taken to relearn X MACS. The DUT and MHPE2 are running SA mode. 443 Measurement : 445 Measure the time taken for flushing these X MAC address. Measure the 446 time taken to relearn the X MACs in DUT. Repeat these test and plot 447 the data. The test is repeated for "N" times and the values are 448 collected. The flush and the relearning time is calculated by 449 averaging the values obtained by "N" samples. 451 Flush time for X Macs in sec = (T1+T2+..Tn/N) Relearning time for X 452 macs in sec = (T1+T2+..Tn/N) 454 3.7. How long it takes to flush the remote macs, due to remote link 455 failure. 457 Objective: 459 To record the time taken to flush the remote mac learned in DUT 460 during remote link failure. 462 Topology : Topology 2 464 Procedure: 466 Send X frames with X different SA and DA to DUT from SHPE3 using 467 traffic generator. Bring down the link between SHPE3 and traffic 468 generator. Then measure the time taken to flush the DUT EVPN MAC 469 table. The DUT and MHPE2 are running SA mode. 471 Measurement : 473 Measure the time taken to flush X remote MACs from EVPN MAC table of 474 DUT. Repeat these test and plot the data. The test is repeated for 475 "N" times and the values are collected. The flush rate is calculated 476 averaging the values obtained by "N" samples. 478 Flush time for X Macs in sec = (T1+T2+..Tn/N) 480 3.8. PBB-EVPN How long it takes to flush the remote macs due to remote 481 link failure 483 Objective: 485 To record the time taken to flush the remote mac learned in DUT 486 during remote link failure. 488 Topology : Topology 2 490 Procedure: 492 Send X frames with X different SA and DA to DUT from SHPE3 using 493 traffic generator. Bring down the link between SHPE3 and traffic 494 generator. Then measure the time taken to flush the DUT PBB-EVPN MAC 495 address table. The remote MACs will be learned by Data plane, but 496 the B-MAC will be learned by control plane. The DUT and MHPE2 are 497 running SA mode. 499 Measurement : 501 Measure the time taken to flush X remote MACs from PBB-EVPN MAC table 502 of DUT. Repeat these test and plot the data. The test is repeated 503 for "N" times and the values are collected. The flush rate is 504 calculated by averaging the values obtained by "N" samples. 506 Flush time for X Macs in sec = (T1+T2+..Tn/N) 508 3.9. To measure the MAC aging time. 510 Objective: 512 To measure the mac aging time. 514 Topology : Topology 1 516 Procedure: 518 Send X frames with X different SA and DA to DUT from CE using traffic 519 generator. Wait till X MAC address are learned. Then stop the 520 traffic. Record the time taken to flush X MACS from DUT EVPN MAC 521 table due to aging. The DUT and MHPE2 are running SA mode 523 Measurement : 525 Measure the time taken to flush X MAC address due to aging. Repeat 526 these test and plot the data. The test is repeated for "N" times and 527 the values are collected. The aging is calculated averaging the 528 values obtained by "N" samples. 530 Aging time for X Macs in sec = (T1+T2+..Tn/N) 532 3.10. PBB-EVPN To measure the MAC aging time. 534 Objective: 536 To measure the mac aging time. 538 Topology : Topology 1 540 Procedure: 542 Send X frames with X different SA and DA to DUT from CE using traffic 543 generator. Wait till X MAC address are learned in DUT PBB- EVPN MAC 544 table. Then stop the traffic. Record the time taken to flush X MAC 545 entries due to aging. The DUT and MHPE2 running in SA mode 547 Measurement : 549 Measure the time taken to flush X MAC address due to aging. Repeat 550 these test and plot the data. The test is repeated for "N" times and 551 the values are collected. The aging is calculated by averaging the 552 values obtained by "N" samples. 554 Aging time for X Macs in sec = (T1+T2+..Tn/N) 556 3.11. How long it takes to age out the remote macs 558 Objective: 560 To measure the remote mac aging time. 562 Topology : Topology 2 564 Procedure: 566 Send X frames with X different SA and DA to DUT from SHPE3 using 567 traffic generator. Stop the traffic at remote PE SHPE3.Due to MAC 568 aging SHPE3 will withdraw its routes from DUT and MHPE2. Measure the 569 time taken to remove these MACs from DUT EVPN MAC table. DUT and 570 MHPE2 are running in SA mode 572 Measurement : 574 Measure the time taken to flush X remote MACs learned in DUT EVPN MAC 575 table due to aging. Repeat these test and plot the data. The test 576 is repeated for "N" times and the values are collected. The aging is 577 calculated by averaging the values obtained by "N" samples. 579 Aging time for X Macs in sec = (T1+T2+..Tn/N) 581 3.12. PBB-EVPN How long it takes to age out the remote macs. 583 Objective: 585 To measure the remote mac aging time. 587 Topology : Topology 2 588 Procedure: 590 Send X frames with X different SA and DA to DUT from SHPE3 using 591 traffic generator. Stop the traffic at remote PE(SHPE3).Measure the 592 time taken to remove these remote MACs from DUT PBB-EVPN MAC table. 593 The DUT and MHPE2 are running in SA mode. 595 Measurement : 597 Measure the time taken to flush the X remote MACs from DUT PBB-EVPN 598 MAC table due to aging Repeat these test and plot the data. The test 599 is repeated for "N" times and the values are collected. The aging is 600 calculated by averaging the values obtained by "N" samples. 602 Aging time for X Macs in sec = (T1+T2+..Tn/N) 604 3.13. How long it takes to learn both local and remote macs. 606 Objective: 608 To record the time taken to learn both local and remote macs. 610 Topology : Topology 3 612 Procedure: 614 Send X frames with X different SA and DA to DUT from SHPE3 using 615 traffic generator. Send X frames with different SA and DA from 616 traffic generator connected to CE. The SA and DA of flows must be 617 complimentary to have unicast flows. Measure the time taken by the 618 DUT to learn 2X in EVPN MAC. DUT and MHPE2 are running in SA mode. 620 Measurement : 622 Measure the time taken to learn 2X MAC address in DUT EVPN MAC table. 623 Repeat these test and plot the data. The test is repeated for "N" 624 times and the values are collected. The mac learning time is 625 calculated by averaging the values obtained by "N" samples. 627 Time to learn 2X Macs in sec = (T1+T2+..Tn/N) 629 3.14. PBB-EVPN How long it takes to learn both local and remote macs 631 Objective: 633 To record the time taken to learn both local and remote macs. 635 Topology : Topology 3 637 Procedure: 639 Send X frames with X different SA and DA to DUT from SHPE3 using 640 traffic generator. Send X frames with different SA and DA from 641 traffic generator connected to CE. The SA and DA of flows must be 642 complimentary to have unicast flows. Measure the time taken by the 643 DUT to learn 2X in MAC table. DUT and MHPE2 are running in SA mode. 645 Measurement : 647 Measure the time taken to learn 2X MAC address table in DUT PBB-EVPN 648 MAC table. Repeat these test and plot the data. The test is 649 repeated for "N" times and the values are collected. The mac 650 learning time is calculated by averaging the values obtained by "N" 651 samples. 653 Time to learn 2X Macs in sec = (T1+T2+..Tn/N) 655 4. High Availability 657 4.1. To Record the whether there is traffic loss due to routing engine 658 failover for redundancy test. 660 Objective: 662 To record traffic loss during routing engine failover. 664 Topology : Topology 3 666 Procedure: 668 Send X frames from CE to DUT from traffic generator withX different 669 SA and DA. Send X frames from traffic generator to SHPE3 with X 670 different SA and DA so that 2X MAC address will be learned in DUT. 671 There is a bi directional traffic flow with X pps in each direction. 672 Then do a routing engine fail-over. 674 Measurement : 676 There should be 0 traffic loss which is the ideal case, No change in 677 the DF role. DUT should not withdraw any routes.Repeat the test "N" 678 times and plot the data.The packet loss is calculated by averaging 679 the values obtained from "N" samples. 681 Packet loss in sec = (T1+T2+..Tn/N) 683 4.2. PBB-EVPN To Record the whether there is traffic loss due to 684 routing engine failover for redundancy test 686 Objective: 688 To record traffic loss during routing engine failover. 690 Topology : Topology 3 692 Procedure: 694 Send X frames to DUT with X different SA and DA from CE using the 695 traffic generator. Send X frames from traffic generator to SHPE3 696 with X different SA and DA so that 2X MAC address will be Learned in 697 DUT. There is a bi directional traffic flow with X pps in each 698 direction. Then do a routing engine fail-over. 700 Measurement : 702 There should be 0 traffic loss which is the ideal case, No change in 703 the DF role. DUT should not withdraw any routes.Repeat the test "N" 704 times and plot the data.The packet loss is calculated by averaging 705 the values obtained from "N" samples. 707 Packet loss in sec = (T1+T2+..Tn/N) 709 5. ARP/ND Scale 711 These tests are conducted to Record the scaling parameter of ARP/ND 712 of the DUT. 714 5.1. To find ARP/ND scale 716 Objective: 718 To Record the ARP/ND scale of the DUT. 720 Topology : Topology 1 722 Procedure: 724 Send X arp/icmpv6 request from RT to DUT with different sender ip/ 725 ipv6 address to the same target gateway ip address. Measure whether 726 X MAC+IPv4 address/MAC+IPv6 address of the hosts are learned in DUT. 728 Measurement : 730 The DUT must learn X MAC+IPV4/MAC+IPv6 and it must advertise the X 731 MAC+IPV4/MAC+IPV6 to the remote router. 733 6. Scale 735 This is to measure the performance of DUT in scaling to "X" EVPN 736 instances. The measured parameters are CPU usage, memory 737 leak,crashes. 739 6.1. To Measure the scale limit of DUT with trigger (Scale without 740 traffic) 742 Objective: 744 To measure the scale limit of DUT for EVPN. 746 Topology : Topology 3 748 Procedure: 750 The DUT,MHPE2 and SHPE3 are scaled to "N" EVI.Clear BGP neighbors of 751 the DUT. Once adjacency is established in the DUT. Measure the 752 routes received from MHPE2 and SHPE3 for "N" EVI in the DUT. 754 Measurement : 756 There should not be any loss of route types 1,2,3 and 4 in DUT. DUT 757 must relearn all type 1,2,3 and 4 from remote routers. The DUT must 758 be subjected to various values of N to find the optimal scale limit 760 6.2. PBB-EVPN To measure the scale limit with trigger. 762 Objective: 764 To measure the scale limit of DUT for PBB-EVPN. 766 Topology : Topology 3 768 Procedure: 770 The DUT,MHPE2 and SHPE3 are scaled to "N" PBB-EVPN instances. Clear 771 BGP neighbors in the DUT Once adjacency is established in DUT, check 772 routes received from SHPE3 and MHPE2. 774 Measurement : 776 There should not be any loss of route types 2,3 and 4 in DUT. The 777 DUT must relearn all type 2,3 and 4 routes from remote routers. The 778 DUT must be subjected to various values of N to find the optimal 779 scale limit. 781 6.3. To measure the convergence time of DUT with scale and traffic. 783 Objective: 785 To measure the convergence time of DUT when the DUT is scaled with 786 EVPN instance along with traffic. 788 Topology : Topology 3 790 Procedure: 792 Scale N EVIs in DUT,SHPE3 and MHPE2.Send F frames to DUT from CE 793 using traffic generator with X different SA and DA for N EVI's. Send 794 F frames from traffic generator to SHPE3 with X different SA and DA. 795 There will be 2X number of MAC address will be learned in DUT EVPN 796 MAC table. There is a bi directional traffic flow with F pps in each 797 direction. Then clear the BGP neighbors in the DUT. Once the 798 adjacency is restored in DUT. Measure the time taken to learn 2X MAC 799 address in DUT MAC table. 801 Measurement : 803 The DUT must learn 2X MAC address. Measure the time taken to learn 804 2X MAC in DUT. Repeat these test and plot the data.The test is 805 repeated for "N" times and the values are collected.The convergence 806 time is calculated by averaging the values obtained by "N" samples. 808 Convergence time in sec = (T1+T2+..Tn/N) 810 6.4. .PBB-EVPN To measure the convergence time of DUT with scale and 811 traffic. 813 Objective: 815 To measure the convergence time of DUT when the DUT is scaled with 816 PBB-EVPN instance along with traffic. 818 Topology : Topology 3 820 Procedure: 822 Scale N PBB-EVI's in DUT,SHPE3 and MHPE2.Send F frames to DUT from CE 823 using traffic generator with X different SA and DA for N EVI's. Send 824 F frames from traffic generator to SHPE3 with X different SA and DA. 825 There will be 2X number of MAC address will be learned in DUT PBB- 826 EVPN MAC table. There is a bi directional traffic flow with F pps in 827 each direction. Then clear the BGP neighbors in the DUT. Once the 828 adjacency is restored in DUT. Measure the time taken to learn 2X MAC 829 address in DUT PBB-MAC table. 831 Measurement : 833 The DUT must learn 2X MAC address. Measure the time taken to learn 834 2X MAC in DUT. Repeat these test and plot the data. The test is 835 repeated for "N" times and the values are collected. The convergence 836 time is calculated by averaging the values obtained by "N" samples. 838 Convergence time in sec = (T1+T2+..Tn/N) 840 7. SOAK Test 842 This is measuring the performance of DUT running with scaled 843 configuration with traffic over a peroid of time "T'". In each 844 interval "t1" the parameters measured are CPU usage, memory usage, 845 crashes. 847 7.1. To Measure the stability of the DUT with scale and traffic. 849 Objective: 851 To measure the stability of the DUT in a scaled environment with 852 traffic. 854 Topology : Topology 3 856 Procedure: 858 Scale N EVI's in DUT,SHPE3 and MHPE2.Send F frames to DUT from CE 859 using traffic generator with different X SA and DA for N EVI's. Send 860 F frames from traffic generator to SHPE3 with X different SA and DA. 861 There will be 2X number of MAC address will be learned in DUT EVPN 862 MAC table. There is a bi directional traffic flow with F pps in each 863 direction. The DUT must run with traffic for 24 hours, every hour 864 check for memory leak, crash. 866 Measurement : 868 Take the hourly reading of CPU, process memory. There should not be 869 any leak, crashes, CPU spikes. 871 7.2. PBB-EVPN to measure the stability of DUT with scale and traffic. 873 Objective: 875 To measure the stability of the DUT in a scaled environment with 876 traffic. 878 Topology : Topology 3 880 Procedure: 882 Scale N PBB-EVI's in DUT,SHPE3 and MHPE2.Send F frames to DUT from CE 883 using traffic generator with X different SA and DA for N EVI's. Send 884 F frames from traffic generator to SHPE3 with X different SA and DA. 885 There will be 2X number of MAC address will be learned in DUT PBB- 886 EVPN MAC table. There is a bi directional traffic flow with F pps in 887 Each direction. The DUT must run with traffic for 24 hours, every 888 hour check the memory leak, crashes. 890 Measurement : 892 Take the hourly reading of CPU process, memory usages. There should 893 not be any memory leak, crashes,CPU spikes. 895 8. Acknowledgements 897 We would like to thank Fioccola Giuseppe of Telecom Italia reviewing 898 our draft and commenting it. We would like to thank Sarah Banks for 899 guiding and mentoring us. 901 9. IANA Considerations 903 This memo includes no request to IANA. 905 10. Security Considerations 907 There is no additional consideration from RFC 6192. 909 11. References 910 11.1. Normative References 912 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 913 Requirement Levels", BCP 14, RFC 2119, 914 DOI 10.17487/RFC2119, March 1997, 915 . 917 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 918 Network Interconnect Devices", RFC 2544, 919 DOI 10.17487/RFC2544, March 1999, 920 . 922 [RFC2899] Ginoza, S., "Request for Comments Summary RFC Numbers 923 2800-2899", RFC 2899, DOI 10.17487/RFC2899, May 2001, 924 . 926 11.2. Informative References 928 [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., 929 Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based 930 Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February 931 2015, . 933 [RFC7623] Sajassi, A., Ed., Salam, S., Bitar, N., Isaac, A., and W. 934 Henderickx, "Provider Backbone Bridging Combined with 935 Ethernet VPN (PBB-EVPN)", RFC 7623, DOI 10.17487/RFC7623, 936 September 2015, . 938 Appendix A. Appendix 940 Authors' Addresses 942 Sudhin Jacob (editor) 943 Juniper Networks 944 Bangalore 945 India 947 Phone: +91 8061212543 948 Email: sjacob@juniper.net 949 Kishore Tiruveedhula 950 Juniper Networks 951 10 Technology Park Dr 952 Westford, MA 01886 953 USA 955 Phone: +1 9785898861 956 Email: kishoret@juniper.net