idnits 2.17.1 draft-kishjac-bmwg-evpntest-09.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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 1112 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 10 instances of too long lines in the document, the longest one being 11 characters in excess of 72. ** There are 28 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 28 has weird spacing: '... at any time...' == Line 29 has weird spacing: '...ference mate...' == Line 132 has weird spacing: '...in this docu...' == Line 328 has weird spacing: '...s taken by c...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2544' is defined on line 881, but no explicit reference was found in the text == Unused Reference: 'RFC2889' is defined on line 886, but no explicit reference was found in the text == Unused Reference: 'RFC7432' is defined on line 891, but no explicit reference was found in the text == Unused Reference: 'RFC7623' is defined on line 897, but no explicit reference was found in the text Summary: 2 errors (**), 0 flaws (~~), 11 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Kishore Tiruveedhula 2 Intended Status: Informational Sudhin Jacob 3 Expires: October 7,2018 Juniper Networks 4 February 26,2018 6 Benchmarking Methodology for EVPN and PBB-EVPN 7 draft-kishjac-bmwg-evpntest-09 9 Abstract 11 This document defines methodologies for benchmarking EVPN and PBB-EVPN performance. 12 EVPN is defined in RFC 7432, and is being deployed in Service Provider networks. 13 This document specifically covers methodologies for benchmarking EVPN/PBB-EVPN 14 convergence, data plane performance, control plane performance. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet-Drafts 29 as reference material or to cite them other than as "work in 30 progress." 32 This Internet-Draft will expire on October 7, 2018. 34 Copyright and License Notice 36 Copyright (c) 2017 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with 44 respect to this document. Code Components extracted from this 45 document must include Simplified BSD License text as described in 46 Section 4.e of the Trust Legal Provisions and are provided without 47 warranty as described in the Simplified BSD License. 49 Contents 50 1. Introduction ............................................... 4 52 1.1 Terminologies ............................................... 5 54 2. Test Topology................................................. 6 56 3. Network....................................................... 8 58 4. PBB-EVPN Network Setup........................................ 8 60 5 Test Cases..................................................... 10 62 5.1.1 To Record the time taken to learn the MAC address in DUT... 10 64 5.1.2. To Record the time taken to learn remote MACs in DUT which is 65 advertised by remote peer........................................ 13 67 5.1.3. To Record the time taken to flush the local entry 68 due to CE link Failure and measure the relearning rate of MACs... 15 70 5.1.4. To Record the time taken by DUT to flush MACs learned from 71 R1 during R1 traffic generator link failure ........................17 73 5.1.5. To measure the MAC aging time...............................19 75 5.1.6. To Record the time taken by DUT to age X routes learned from 76 remote PE after stopping the traffic at remote PE.................. 20 78 5.1.7. To Record the time taken by DUT to learn routes from 79 local and remote................................................... 23 81 5.2 High Availability ........................................ 25 83 5.2.1 To Record the whether there is traffic loss due to 84 routing engine fail-over for redundancy test....................... 25 86 5.3 ARP/ND Scaling 27 88 6. Scale 28 90 6.1. To Scale the DUT to N EVI and clear BGP in DUT without traffic. .28 92 6.2. To Scale the DUT to N EVI and clear BGP in DUT with traffic. 93 Measure the convergence time........................................ 29 95 7. Soak Test 31 97 7.1. To Scale the DUT to N EVI in DUT with traffic and 98 run the set up for 24hrs ........................................... 31 100 8. Acknowledgments 33 102 9. IANA Considerations............................................ 33 104 10. Security Considerations 33 106 11 References 33 108 11.1 Normative References 33 110 11.2 Informative References 34 112 Authors' Addresses 35 114 1. Introduction 116 EVPN is defined in RFC7432 which describes procedures for 117 BGP MPLS-based Ethernet VPNs(EVPN).This document defines the 118 methodologies for benchmarking performance of EVPN. The scope of 119 this document is to provide methodologies for benchmarking EVPN 120 data, control plane MAC learning, MAC flush ,MAC aging, 121 convergence, high availability, scale. 122 The methodologies defined for EVPN can be used for benchmarking the 123 performance of PBB-EVPN.PBB-EVPN is defined in RFC 7623.It is 124 being deployed in provider network. The difference between PBB-EVPN 125 and EVPN is the former learns the customer MAC in data plane the 126 later learns in control plane. 128 Conventions used in this document 130 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 131 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 132 in this document are to be interpreted as described in RFC 2119 133 [RFC2119]. 135 1.1 Terminologies 137 MHPE Multi homed Provide Edge router. 139 RR Route Reflector 141 P Provider Router 143 CE Customer Router/Devices/Switch 145 MHPE2 Multi homed Provider Edge router 2 147 MHPE1 Multi homed Provider Edge router 1 149 SHPE3 Single homed Provider Edge Router 3 151 AA EVPN Terminologies AA All-Active 153 SA EVPN Terminologies SA Single-Active 155 RT Router Tester 157 Sub Interface Each physical Interfaces is subdivided in to 158 Logical units. 160 EVI EVPN Instances which will be running on sub interface or 161 physical port of the provider Edge routers. 163 DF Designated Forwarder 165 ESI Ethernet Segment Identifier 167 2. Test Topology 169 EVPN/PBB-EVPN Running in SA mode: 170 Figure 1 172 +-------------+ 173 | | 174 | | 175 | R1(SHPE1)| 176 | | + sub interfaces 177 | | +---------------------------------+ 178 +-----+-------+ Router Tester (IXIA/Spirent) sending 179 | layer 2 bi directional traffic which acts as sender/receiver 180 | 181 | 182 | 183 +-------------+ 184 | ++ | 185 | | 186 | RR/P | 187 | | 188 | | 189 +---+-------------+----+ 190 | | 191 | | 192 | | 193 +-----+-------+ +-----+-------+ 194 | | | | 195 | MHPE1(DUT) | | 196 | | | MHPE2 | 197 | | | | 198 | | | | 199 | | +------+------+ 200 +-------------+ | 201 | | 202 | +---------+ 203 +-------+-------------+ 204 | | 205 | CE1 | 206 | bridge domain | sub interfaces 207 | +-------------------------------+ 208 | | 209 +---------------------+ Router Tester (IXIA/Spirent) Sending bi 210 directional layer 2 traffic with different VLAN acts as sender/receiver 212 3. Network 214 The network consists of 5 routers and 2 traffic generator ports. 215 The traffic generator ports are connected to R1 and CE, these RT port 216 will be sending uni directional or bi directional for different vlans 217 depends on the test scenario.R1 is also termed as SHPE3 which is a 218 single homed router is running EVPN services. DUT(MHPE1) and MHPE2 are 219 running multihoming EVPN services, the CE acts as a bridge which will 220 send the layer 2 traffic to both DUT and MHPE2. RR is the router 221 reflector which is also acting as provider router. All four 222 routers(MHPE1,MHPE2,RR,R1) except CE are running MPLS,BGP emulating a 223 Service provider scenario. CE is a dual home connected to DUT and 224 MHPE2.The testing will be done on DUT in order to bench mark the EVPN 225 service. DUT and the MHPE2 are running EVPN with SA/AA, In AA EVPN 226 service there will be LAG running between interfaces of CE, DUT and 227 MHPE2 .The DUT and other PE's will be running N EVI's (EVPN instances) 228 on sub interfaces. 230 4. PBB-EVPN Network Setup 232 The network consists of 5 routers and 2 traffic generator ports. 233 The traffic generator ports are connected to R1 and CE, these ports 234 will be sending bi directional or uni directional layer 2 traffic for 235 different vlans depending up on the various test scenarios. 236 R1 is also termed as SHPE3 which is a single homed router is running 237 PBB-EVPN services. DUT(MHPE1) and MHPE2 are running multihoming PBB- 238 EVPN services ,the CE acts as a bridge which will send the layer 2 239 traffic to both DUT and MHPE2. RR is the router reflector which is 240 also acting as provider router. All four routers(MHPE1,MHPE2,RR,R1) 241 except CE are running MPLS,BGP emulating a Service provider 242 scenarios. CE is a dual home connected to DUT and MHPE2.The testing will 243 be done on DUT in order to bench mark the PBB-EVPN service. DUT and 244 the MHPE2 are running PBB-EVPN with SA/AA, In AA PBB-EVPN service 245 there will be LAG running between the interfaces of CE, DUT and MHPE2. 246 The DUT and other PE's will be running EVI's (PBB-EVPN instances) 247 on sub interfaces. 249 5 Test Cases 251 The following tests are conducted to measure the time taken to learn 252 the number of MAC's locally in EVI is "T"sec. The data plane 253 learning of MAC will happen locally from connected interface. The 254 control plane learning of MAC is through BGP advertisements from the 255 remote PE(SHPE3). The control plane learning of MAC, the time 256 taken will be "T'". The data plane MAC learning can be measured using 257 the parameters defined in RFC 2889 section 5.8. 259 5.1.1 To Record the time taken to learn the MAC address in DUT 261 Objective: 263 To Record the time taken to learn the MAC address locally and 264 time taken to send these local learned MAC routes to peers. 266 a. Send unicast frames from CE to MHPE1(DUT) working in SA 267 mode with different source and destination address. Measure the time 268 taken to learn these MAC in forwarding table and in control plane. 269 The data plane learning is measured using RFC 2889 section 5.8. 270 Sending frames to the limit of bridge domain of particular EVI. 271 Measure the time taken to learn all MAC in data plane/hardware. 272 The Range of MAC is known from RT and this is verified in DUT. 274 b. Measure the time taken to send these type 2 routes from 275 DUT to its peers. 277 Procedure: 279 Configure EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 280 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 281 DUT.For MH PE ESI must be configured per IFD/Interface. Using RT 282 (traffic generator)to send the traffic to the CE. The traffic is 283 unidirectional. Since CE is working in bridge mode, frames will be 284 send to ingress sub interface of DUT. The BGP must be established in 285 R1,MHPE1(DUT),RR,MHPE2. 287 Measurement 289 The DUT EVPN MAC table must learn the MACs in data plane in T 290 Time frame. The DUT must send type 2 routes to remote router in T' 291 Time frame. Repeat the test and plot the data. The data plane 292 measurement is taken by considering DUT as black box the range 293 of X MAC is known from RT and the same is learned in DUT, the time 294 to learn that is measured. 296 The test is repeated for "N" times and the value is taken by 297 averaging the values. 299 PBB-EVPN To Record the time taken to learn the MAC address in DUT 301 Objective: 303 To Record the time taken to learn the MAC address locally. 305 a. Send unicast frames from CE to MHPE1(DUT) working in SA 306 mode with different source and destination address. Measure the time 307 taken to learn these MACs in forwarding table. The data plane 308 learning is measured using RFC 2889 section 5.8.Sending frames to 309 the limit of bridge domain of particular EVI. Measure the time 310 taken to learn all MAC in data plane/hardware. The Range of 311 MAC is known from RT and this is verified in DUT. 313 Procedure: 315 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE 316 are running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 317 and DUT. Once the BGP comes up. Record the DUT PBB-EVPN table. For MH 318 PE ESI must be configured per IFD/Interface. From RT (traffic 319 generator) send the traffic to the DUT. The BGP must be established in 320 R1,MHPE1(DUT),RR,MHPE2. The traffic is unidirectional. Since CE is 321 working in bridge mode, frames will be send to ingress sub interface 322 of DUT. 324 Measurement 326 The DUT MAC table must learn the MACs in data plane in T time 327 frame. Repeat the test and plot the data. The data plane measurement 328 is taken by considering DUT as black box the range of MAC is 329 known from RT and the same is learned in DUT, the time to learn 330 MAC is measured. The test is repeated for "N" times and the value 331 is taken by averaging the values. 333 5.1.2. To Record the time taken to learn remote MACs in DUT 334 which is advertised by remote peer 336 Objective: 338 Send frames with different SA and DA to R1 from RT 339 Measure the time taken to learn these MACs from remote peer in 340 DUT and program the EVPN MAC address table. The DUT and MHPE2 are 341 running SA mode. 343 Procedure: 345 Configure EVPN EVI in R1,MHPE2,DUT. All 4 routers except CE are 346 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 347 DUT. Record the DUT EVPN table. For MH PE ESI must be configured 348 per IFD/Interface. Using RT(traffic generator) send the traffic to 349 R1.The traffic is uni directional. There wont be any traffic flow from 350 CE to DUT during this test. The BGP must be in established state. The 351 MACS learned in R1 will be advertised to DUT by BGP. 353 Measurement: 355 The DUT MAC table must learn the MAC address in T time frame. 356 Repeat these test and plot the data. The test is repeated for "N" 357 times and the value is taken by averaging the values. 359 PBB-EVPN To Record the time taken to learn MAC's from remote 360 peer by DUT. 362 Objective: 364 Send frames with different SA and DA to R1 from RT. Measure the 365 time taken to learn these MACs from remote peer and program the 366 MAC address table of the DUT. DUT and MHPE2 are running SA mode. 368 Procedure: 370 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 371 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 372 DUT. Record the DUT PBB-EVPN table. For MHPE ESI must be configured 373 per IFD/Interface. Using RT(traffic generator) send the traffic to R1. 374 The traffic is uni directional. There wont be any traffic flow from CE 375 to DUT during this test. The BGP must be in established state. 377 Measurement: 379 The DUT MAC table must learn the MAC address in T time frame. 380 Repeat these test and plot the data. The test is repeated for "N" 381 times and the value is taken by averaging the values. 383 5.1.3. To Record the time taken to flush the local entry due to CE link 384 Failure and measure the relearning rate of MACs 386 Objective: 388 Send frames with different SA and DA to DUT from CE using 389 traffic generator. Wait till the MHPE2 learns all MAC address. 390 Then fail the MHPE2 CE link and measure the time taken to flush these 391 MACs from the EVPN MAC table and the time taken to relearn it. 392 The DUT and MHPE2 are running SA mode. In this scenario MHPE2 is the 393 Designated forwarder which learns mac and advertises to DUT. 395 Procedure: 397 Configure EVPN EVI in R1,MHPE2,DUT. All 4 routers except CE are 398 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and DUT. 399 Once the BGP is established. Record the DUT EVPN table. For MH PE ESI 400 must be configured per IFD/Interface. Using RT(traffic generator) 401 send the traffic. In this scenario traffic will be only send from CE 402 side. 404 Measurement: 406 Measure the time taken for flushing these MAC address. Measure 407 the time taken to relearn the MACs in DUT. Repeat the test 408 and plot the data. 410 PBB-EVPN To Record the time taken to flush the local entry due to CE link failure 412 Objective: 414 Send frames with different SA and DA to DUT from CE using 415 traffic generator. Wait till the MHPE2 learn all MAC address. Then 416 fail the MHPE2 CE link and measure the time taken to flush these 417 MACs from the PBB-EVPN MAC table. Measure the time taken to relearn 418 MACS. The DUT and MHPE2 are running SA mode. 420 Procedure: 422 Configure PBB-EVPN EVI in R1,MHPE2,DUT. All 4 routers except CE are 423 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 424 DUT. Once the BGP is established. Record the DUT PBB-EVPN table. 425 For MH PE ESI must be configured per IFD/Interface. Using RT(traffic 426 generator) send the traffic to the CE. The traffic is uni 427 directional 429 Measurement: 431 The DUT MAC table must learn the MAC address and measure the 432 time taken for flushing these X MAC address. Measure the time taken 433 to relearn these MACs in DUT. Repeat the test and plot the data. 435 5.1.4. To Record the time taken by DUT to flush MACs learned from R1 during R1 436 traffic generator link failure 438 Objective: 440 Send frames with different SA and DA to DUT from R1 using traffic 441 generator. Bring down the link between R1 and traffic generator. Then 442 measure the time taken to flush the DUT EVPN MAC table. The DUT and 443 MHPE2 are running SA mode. 445 Procedure: 447 Configure EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 448 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 449 DUT. Once the BGP is established Record the DUT EVPN table. For MHPE 450 ESI must be configured per IFD/Interface. Using RT(traffic generator) 451 send the traffic to R1.There wont be any traffic flowing to CE from 452 RT. 454 Measurement: 456 Measure the time taken to flush remote MACs from EVPN MAC table 457 of DUT. Repeat the test and plot the data. 459 PBB-EVPN To Record the time taken by DUT to flush MACs learned 460 from R1 during R1 traffic generator link failure 462 Objective: 464 Send frames with different SA and DA to DUT from R1 using 465 traffic generator. Bring down the link between R1 and traffic 466 generator. Then measure the time taken to flush the DUT PBB-EVPN MAC 467 address table. The remote MACs will be learned by Data plane, but the 468 B-MAC will be learned by control plane. The DUT and MHPE2 are running 469 SA mode. 471 Procedure: 473 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 474 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 475 DUT. Once the BGP is established Record the DUT PBB-EVPN MAC table. 476 For MHPE ESI must be configured per IFD/Interface. Using RT(traffic 477 generator) send the traffic to R1.In this scenario traffic will 478 be flowing only from R1. 480 Measurement: 482 Measure the time taken to flush remote MACs from PBB-EVPN MAC 483 table of DUT. Repeat the test and plot the data. 485 5.1.5. To measure the MAC ageing time. 487 Objective: 489 Send frames with different SA and DA to DUT from CE using 490 traffic generator. Wait till MAC address are learned. Then stop 491 the traffic. Record the time taken to flush MACS from DUT EVPN 492 MAC table due to ageing. The DUT and MHPE2 are running SA mode. 494 Procedure: 496 Configure EVPN EVI in R1,MHPE2,DUT. All 4 routers except CE are 497 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 498 DUT .Once the BGP is established. Record the DUT EVPN table. For MHPE 499 ESI must be configured per IFD/Interface. Using RT(traffic generator), 500 send the traffic to the DUT. The traffic will be flowing from CE 501 to DUT. There wont be any traffic from R1. 503 Measurement: 505 Measure the time taken to flush MAC address due to ageing. Repeat 506 the test and plot the data. 508 PBB-EVPN To measure the MAC ageing time. 510 Objective: 512 Send X frames with different SA and DA to DUT from CE using 513 traffic generator. Wait till MAC address are learned in DUT PBB- 514 EVPN MAC table. Then stop the traffic. Record the time taken to flush 515 MAC entries due to ageing. The DUT and MHPE2 running in SA mode 517 Procedure: 519 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 520 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 521 DUT.Once the BGP is established. Record the DUT PBB-EVPN MAC table. 522 For MH PE ESI must be configured per IFD/Interface. Using RT(traffic 523 generator) send the traffic to the DUT. The traffic is uni directional 524 flowing from CE to DUT. 526 Measurement: 528 Measure the time taken to flush MAC address due to ageing. Repeat 529 the test and plot the data. 531 5.1.6. To Record the time taken by DUT to age X routes learned from 532 remote PE after stopping the traffic at remote PE. 534 Objective: 536 Send X frames with different SA and DA to DUT from R1 using 537 traffic generator. Stop the traffic at remote PE R1. 538 Due to MAC ageing R1 will withdraw its routes from DUT and MHPE2. 539 Measure the time taken to remove these MACs from DUT EVPN MAC 540 table. DUT and MHPE2 are running in SA mode 542 Procedure: 544 Configure EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 545 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 546 DUT. Once the BGP is established. Record the DUT EVPN table. For MH 547 PE ESI must be configured per IFD/Interface. Using RT(traffic 548 generator) send the traffic to R1.There wont be any traffic from 549 CE. 551 Measurement: 553 Measure the time taken to flush remote MACs learned in DUT EVPN 554 MAC table due to ageing. Repeat the test and plot the data. 556 PBB-EVPN To Record the time taken by DUT to age MAC from remote 557 PE after stopping the traffic at remote PE. 559 Objective: 561 Send frames with different SA and DA to DUT from R1 using 562 traffic generator. Stop the traffic at remote PE(R1).Measure the 563 time taken to remove these remote MACs from DUT PBB-EVPN MAC 564 table. The DUT and MHPE2 are running in SA mode. 566 Procedure: 568 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 569 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 570 DUT. Once the BGP is established. Record the DUT MAC table. For MH 571 PE ESI must be configured per IFD/Interface. Using RT(traffic 572 Generator) send the traffic to R1. There is no traffic from CE side. 574 Measurement: 576 Measure the time taken to flush the remote MACs from DUT PBB- 577 EVPN MAC table due to ageing. Repeat the test and plot the data. 579 5.1.7. To Record the time taken by DUT to learn routes from local and remote. 581 Objective: 583 Send frames with different SA and DA to DUT from R1 using 584 traffic generator. Send frames with different SA and DA from 585 traffic generator connected to CE. The SA and DA of flows must be 586 complimentary to have unicast flows. Measure the time taken by 587 the DUT to learn 2X in EVPN MAC. DUT and MHPE2 are running in 588 SA mode. 590 Procedure: 592 Configure EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 593 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 594 DUT. Once the BGP is established. Record the DUT EVPN table. For MH 595 PE ESI must be configured per IFD/Interface. Using RT(traffic 596 generator) send the traffic to the routers. The traffic is bi 597 directional. 599 Measurement: 601 Measure the time taken to learn <2X> MAC address in DUT EVPN MAC 602 table. Repeat the test and plot the data. 604 PBB-EVPN To Record the time taken by DUT to learn MACs from 605 local and from remote. 607 Objective: 609 Send X frames with different SA and DA to DUT from R1 using 610 traffic generator. Send frames with different SA and DA from 611 traffic generator connected to CE. The SA and DA of flows must be 612 complimentary to have unicast flows. Measure the time taken by the 613 DUT to learn 2X in MAC table. DUT and MHPE2 are running in SA mode. 615 Procedure: 617 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 618 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 619 DUT. Once the BGP is established. Record the DUT EVPN table.For MH 620 PE ESI must be configured per IFD/Interface. Using RT(traffic 621 generator) send the traffic to the routers. 623 Measurement: 625 Measure the time taken to learn 2X MAC address table in DUT PBB-EVPN 626 MAC table. Repeat the test and plot the data. 628 5.2 High Availability 630 5.2.1 To Record the whether there is traffic loss due to routing engine 631 failover for redundancy test. 633 Objective: 635 Send frames from CE to DUT from traffic generator with different 636 SA and DA. Send frames from traffic generator to R1 with different 637 SA and DA so that <2X> MAC address will be learned in DUT. There is a 638 bi directional traffic flow with X pps in each direction. Then do a 639 routing engine failover. 641 Procedure: 643 Configure EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 644 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 645 DUT. Once the BGP is established. Record the DUT EVPN table. For MH PE 646 ESI must be configured per IFD/Interface. Using RT(traffic generator) 647 Send bi directional to the routers. 649 Measurement: 651 There should be 0 traffic loss which is the ideal case, No change in 652 the DF role. DUT should not withdraw any routes. Repeat the test and 653 plot the graph. 655 PBB-EVPN To Record the whether there is traffic loss due to routing 656 engine failover for redundancy test. 658 Objective: 660 Send frames to DUT with different SA and DA from CE using 661 the traffic generator. Send frames from traffic generator to 662 R1 with different SA and DA so that <2X> MAC address will be learned 663 in DUT. There is a bi directional traffic flow with pps in each 664 direction. Then do a routing engine failover. 666 Procedure: 668 Configure PBB-EVPN EVI in R1,MHPE2,DUT. All 4 routers except CE are 669 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 670 DUT. Once the BGP is established. Record the DUT PBB-EVPN table. For 671 MH PE ESI must be configured per IFD/Interface. Using RT(traffic 672 generator) send the traffic to the routers. 674 Measurement: 676 There should be 0 packet loss which is the ideal case, No change 677 in the DF role. There should not be any withdraw of routes from DUT. 679 5.3 ARP/ND Scaling 681 These tests are conducted to Record the scaling parameter of arp/ND 682 of the DUT. 684 EVPN: To Record the ARP/ND scale of the DUT with gateway IRB 685 configured. 687 Objective: 689 Send arp/icmpv6 request from RT to DUT with different sender 690 ip/ipv6 address to the same target gateway ip address. Measure whether 691 MAC+IPv4 address/MAC+IPv6 address of the hosts are learned in DUT. 693 Procedure: 695 Configure EPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 696 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 697 DUT. Once the BGP is established. Record the DUT EVPN table. For MH PE 698 ESI must be configured per IFD/Interface. Using RT(traffic 699 generator) send arp/ICMPv6 request to the DUT which has gateway 700 configured. 702 Measurement: 704 The DUT must learn MAC+IPV4/MAC+IPv6 and it must advertise the X 705 MAC+IPV4/MAC+IPV6 to the remote router. 707 6. Scale 709 6.1. To Scale the DUT to N EVI and clear BGP in DUT without traffic. 711 Objective: 713 The DUT, MHPE2 and R1 are scaled to "N" EVI. Clear BGP neighbors of 714 the DUT. Once the adjacency is established in DUT. Measure the routes 715 received from remote routers MHPE2 and R1 for EVIs in the DUT. 717 Procedure: 719 Configure EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 720 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 721 DUT. Once the BGP is established. Record the DUT EVPN table. For 722 MHPE,DUT ESI must be configured per IFD/Interface. 724 Measurement 726 There should not be any loss of route types 1,2,3 and 4 in DUT. DUT 727 Must relearn all type 1,2,3 and 4 from remote routers. 729 PBB-EVPN To Scale the DUT to N PBB-EVPN instances and clear BGP in 730 DUT without traffic. 732 Objective: 734 The DUT, MHPE2 and R1 are scaled to "N" PBB-EVI. Clear BGP 735 neighbors of the DUT. Once the adjacency is established in DUT. 736 Measure the routes received from remote routers MHPE2 and R1 for 737 EVIs in the DUT. 739 Procedure: 741 Configure "N" PBB-EVPN instances in R1,MHPE2,DUT.All 4 routers except 742 CE are running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 743 and DUT. Once is established. Record the DUT PBB-EVPN table. For MH 744 PE ESI must be configured per IFD/Interface. 746 Measurement 748 There should not be any loss of route types 2,3 and 4 in DUT. The DUT 749 must relearn all type 2,3 and 4 routes from remote routers. 751 6.2. To Scale the DUT to N EVI and clear BGP in DUT with traffic. 752 Measure the convergence time 754 Objective: 756 Scale EVI's in DUT,R1 and MHPE2.Send F frames to DUT from CE using 757 traffic generator with different SA and DA for N EVI's. Send 758 frames from traffic generator to R1 with different SA and DA. 759 There will be <2F> number of MAC address will be learned in DUT EVPN 760 MAC table. There is a bi directional traffic flow with F pps in each 761 direction. Then clear the BGP neighbors in the DUT. Once the adjacency 762 is restored in DUT. Measure the time taken to learn all <2F> MAC 763 address in DUT MAC table. 765 Procedure: 767 Configure EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 768 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 769 DUT. Once the BGP is established. Record the DUT EVPN table. For MH 770 PE ESI must be configured per IFD/Interface. Using RT(traffic 771 generator)send the traffic to the routers. 773 Measurement: 775 The DUT must learn all <2F> MAC address. Measure the time taken to 776 learn 2F MAC in DUT, measure the flood traffic time "t" of DUT 778 PBB-EVPN To Scale the DUT to "N" PBB-EVPN instances and clear BGP 779 in DUT with traffic. Measure the convergence time 781 Objective: 783 Scale PBB-EVI's in DUT,R1 and MHPE2.Send frames to DUT from CE 784 using traffic generator with different SA and DA for N EVI's. Send 785 frames from traffic generator to R1 with different SA and DA. 786 There will be <2F> number of MAC address will be learned in DUT PBB- 787 EVPN MAC table. There is a bi directional traffic flow with F pps in 788 each direction. Then clear the BGP neighbors in the DUT. Once the 789 adjacency is restored in DUT. Measure the time taken to learn all <2F> 790 MAC address in DUT PBB-MAC table. 792 Procedure: 794 Configure PBB-EVPN instances in R1,MHPE2,DUT.All 4 routers except 795 CE are running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 796 and DUT. Once BGP is established. Record the DUT EVPN table. For MH 797 PE ESI must be configured per IFD/Interface. Using RT(traffic 798 generator) send the traffic to the routers. 800 Measurement: 802 The DUT must learn all 2F MAC address. Measure the time taken 803 to learn 2F MAC in DUT, measure the flood traffic time "t" of DUT 805 7. Soak Test 807 7.1. To Scale the DUT to N EVI in DUT with traffic and run the set up for 24hrs 809 Objective: 811 Scale EVIs in DUT,R1 and MHPE2.Send F frames to DUT from CE using 812 traffic generator with different SA and DA for N EVI's. Send 813 frames from traffic generator to R1 with different SA and DA. 814 There will be <2F> number of MAC address will be learned in DUT EVPN 815 MAC table. There is a bi directional traffic flow with F pps in each 816 direction. The DUT must run with traffic for 24 hours, every hour 817 check for memory leak, crash. 818 . 820 Procedure: 822 Configure EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 823 running MPLS,BGP,RR is acting as route reflector to R1,MHPE2 and 824 DUT. Once the BGP is established. Record the DUT EVPN table. For MH 825 PE ESI must be configured per IFD/Interface. Using RT(traffic 826 generator) send the traffic to the routers. 828 Measurement: 830 Take the hourly reading of CPU, process memory. There should not be 831 any leak, crashes, CPU spikes. 833 PBB-EVPN To Scale the DUT to N PBB-EVPN instances in DUT with traffic 834 and run the set up for 24hrs 836 Objective: 838 Scale PBB-EVI's in DUT,R1 and MHPE2.Send frames to DUT from CE 839 using traffic generator with different SA and DA for N EVI's. Send 840 frames from traffic generator to R1 with different SA and DA. There 841 will be <2F> number of MAC address will be learned in DUT PBB-EVPN MAC 842 table. There is a bi directional traffic flow with pps in each 843 direction. The DUT must run with traffic for 24 hours, every hour 844 check the memory leak, crashes. 846 Procedure: 848 Configure PBB-EVPN instances in R1, MHPE2, DUT. All 4 routers 849 except CE are running MPLS,BGP,RR is acting as route reflector to 850 R1,MHPE2 and DUT. Once the BGP comes up Record the DUT EVPN table. 851 for MH PE ESI must be configured per IFD/Interface. Using RT(traffic 852 generator)send the traffic to the routers. 854 Measurement: 856 Take the hourly reading of CPU process, memory usages. There should 857 not be any memory leak, crashes, CPU spikes. 859 8. Acknowledgments 861 We would like to thank Fioccola Giuseppe of Telecom Italia 862 reviewing our draft and commenting it. We would like to thank Sarah 863 Banks, the work group chair for guiding us in this draft. 865 9. IANA Considerations 867 This memo includes no request to IANA. 868 10. Security Considerations 870 There is no additional consideration from RFC 6192. 872 11 References 874 11.1 Normative References 876 [RFC2119] Bradner, S., "Key words for use in RFCs to 877 Indicate Requirement Levels", BCP 14, RFC 2119, 878 DOI 10.17487/RFC2119, June 1997,. 881 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking 882 Methodology for Network Interconnect Devices", RFC 883 2544,DOI 10.17487/RFC2544, June 1999,. 886 [RFC2889] R.Mandeville and J. Perser "Benchmarking 887 Methodology for LAN Switching Devices" 889 11.2 Informative References 891 [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., 892 Isaac, A.,Uttaro, J., Drake, J., and W.Henderickx, 893 "BGP MPLS-Based Ethernet VPN", 894 RFC 7432, DOI 10.17487/RFC7432, February 895 2015, . 897 [RFC7623] Sajassi, A., Ed., Aggarwal, R., Bitar, N., 898 Isaac, A.,J., Drake, J., and W. Henderickx, 899 " Provider Backbone Bridging Combined with Ethernet 900 VPN(PBB-EVPN)",RFC 7623,10.17487/RFC7623,September 2015 901 . 903 Authors' Addresses 905 Appendix A. Appendix 907 Authors' Addresses 909 Sudhin Jacob (editor) 910 Juniper Networks 911 Bangalore 912 India 914 Phone: +91 8061212543 915 Email: sjacob@juniper.net 916 sudhinjacob@rediffmail.com 918 Kishore Tiruveedhula 919 Juniper Networks 920 10 Technology Park Dr 921 Westford, MA 01886 922 USA 924 Phone: +1 9785898861 925 Email: kishoret@juniper.net