idnits 2.17.1 draft-vikjac-bmwg-evpnmultest-01.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 19 instances of too long lines in the document, the longest one being 15 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (February 27, 2019) is 1884 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 768, but no explicit reference was found in the text == Unused Reference: 'RFC2899' is defined on line 773, but no explicit reference was found in the text == Unused Reference: 'RFC7432' is defined on line 779, 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 (~~), 5 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 V. Nagarajan 4 Intended status: Standards Track Juniper Networks 5 Expires: August 31, 2019 February 27, 2019 7 Benchmarking Methodology for EVPN Multicasting 8 draft-vikjac-bmwg-evpnmultest-01 10 Abstract 12 This document defines methodologies for benchmarking IGMP proxy 13 performance over EVPN-VXLAN. IGMP proxy over EVPN is defined in 14 draft-ietf-bess-evpn-igmp-mld-proxy-02, and is being deployed in data 15 center networks. Specifically this document defines the 16 methodologies for benchmarking IGMP proxy convergence, leave latency 17 Scale,Core isolation, high availability and longevity. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on August 31, 2019. 36 Copyright Notice 38 Copyright (c) 2019 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 55 1.2. Terminologies . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Test Topology . . . . . . . . . . . . . . . . . . . . . . . . 4 57 3. Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . 6 58 3.1. How long it takes to learn ( X1...Xn) IGMP join messages 59 in DUT . . . . . . . . . . . . . . . . . . . . . . . . . 6 60 3.2. How long it takes to clear the (*,G) entries in the DUT . 7 61 3.3. How long it takes the DUT to stop forwarding the 62 traffic(Measuring the leave latency) . . . . . . . . . . 7 63 3.4. How long it takes to learn (X1...Xn) IGMP join messages 64 for N vlans in DUT . . . . . . . . . . . . . . . . . . . 8 65 3.5. How long it takes to clear the (*,G) entries in the DUT 66 for N vlans . . . . . . . . . . . . . . . . . . . . . . . 9 67 3.6. How long it takes the DUT to stop forwarding the traffic 68 for N vlans(Measuring the leave latency) . . . . . . . . 9 69 3.7. How long it takes to learn (X1...Xn) IGMP join messages 70 for N vlans in DUT working EVPN AA mode . . . . . . . . . 10 71 3.8. How long it takes to clear the (*,G) entries for N vlans 72 in DUT working EVPN AA . . . . . . . . . . . . . . . . . 11 73 3.9. How long it takes the DUT operating in EVPN AA to stop 74 forwarding the traffic for N vlans(Measuring the leave 75 latency) . . . . . . . . . . . . . . . . . . . . . . . . 11 76 3.10. How long does it take the DUT in EVPN AA to handle Join 77 Timeout and stop forwarding . . . . . . . . . . . . . . . 12 78 3.11. How long does it take an Ingress to learn a remote Type-6 79 join, create state and forwarding . . . . . . . . . . . . 13 80 4. Link Flap . . . . . . . . . . . . . . . . . . . . . . . . . . 13 81 4.1. To Measure the multicast packet loss in EVPN AA scenario 82 on a CE link failure . . . . . . . . . . . . . . . . . . 14 83 4.2. To Measure the multicast packet loss in EVPN AA scenario 84 on a core failure . . . . . . . . . . . . . . . . . . . . 14 85 4.3. To Measure the multicast packet loss in EVPN AA scenario 86 on a routing failure . . . . . . . . . . . . . . . . . . 15 87 5. Scale Convergence . . . . . . . . . . . . . . . . . . . . . . 15 88 5.1. To measure the packet loss during the core link failure. 16 89 6. High Availability . . . . . . . . . . . . . . . . . . . . . . 16 90 6.1. To Record the whether there is traffic loss due to 91 routing engine failover for redundancy test. . . . . . . 16 92 7. SOAK Test . . . . . . . . . . . . . . . . . . . . . . . . . . 17 93 7.1. To Measure the stability of the DUT with scale and 94 traffic. . . . . . . . . . . . . . . . . . . . . . . . . 17 95 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 96 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 97 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 98 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 99 11.1. Normative References . . . . . . . . . . . . . . . . . . 18 100 11.2. Informative References . . . . . . . . . . . . . . . . . 18 101 Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 18 102 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 104 1. Introduction 106 IGMP proxy over EVPN-VXLAN is defined in draft-ietf-bess-evpn-igmp- 107 mld-proxy-02,and is being deployed in data center networks. 108 Specifically this document defines the methodologies for benchmarking 109 IGMP proxy convergence,leave latency Scale,Core isolation, high 110 availability and longevity. 112 1.1. Requirements Language 114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 116 document are to be interpreted as described in RFC 2119 [RFC2119]. 118 1.2. Terminologies 120 Leaf A layer 2 or layer 3 capable device 122 Spine layer 3 capable device which is used to inter connect leaves 124 CE Customer Router/Devices/Switch. 126 AA EVPN Terminologies AA All-Active. 128 AC Attachment Circuit 130 RT Router Tester. 132 DUT Device under Test. 134 Sub Interface Each physical Interfaces is subdivided in to Logical 135 units. 137 EVI EVPN Instances which will be running on sub interface or physical 138 port of the provider Edge routers. 140 DF Designated Forwarder. 142 ESI Ethernet Segment Identifier. 144 2. Test Topology 146 EVPN Overlay Network running on leaf1, leaf2 leaf3,spine1 and spine 2 147 : 149 Topology Diagram 150 RT 151 +--------------+ +--------------+ 152 RT | | | +-------------------+ 153 +---------+ spine1 +----------------------------------+ 154 | | | spine2 | | 155 | | | | | 156 +----+---------+---------+ +----+----+----+------------------+ 157 | | | | | | 158 | | | | | | 159 | | | | | | 160 | | | | | | 161 | | | | | | 162 RT +---------+-----+---------+---+-------+----++ +--+-----------+----+ 163 +-------------+ | | | | leaf3 | 164 ++ leaf1 | | leaf2 | | | 165 | DUT | | | | | 166 +----+----------+ +---+--------+----+ +--------+----------+ 167 | | | | 168 | | | | 169 | | | | 170 | | | | 171 +-+-----------------+------+ | | 172 | | +--+ RT ++ RT 173 | CE | RT 174 | +-------+ 175 +-------------------+ 176 CE connected to leaf1 and leaf2 in EVPN AA mode. 178 Topology 1 180 Topology Diagram 182 Figure 1 184 There are six routers in the topology. Leaf1,leaf2, 185 leaf3,spine1,spine2 emulating a data center network. CE is a 186 customer device connected to leaf1 and leaf2, it is configured with 187 bridge domains in different vlans. The router tester is connected to 188 CE,leaf1,leaf2,leaf3,spine1 and spine 2 to emulate multicast source 189 and host generating igmp join/leave. 191 All routers except CE are configured with EBGP for the underlay 193 All router are configured with EVPN-VXLAN overlay 195 All leaves and spine must be configured "N" EVPN-VXLAN instances 196 depends up on the cases. 198 Leaf1 and Leaf2 must be configured with ESI per vlan or ESI on IFD. 200 Leaf1 and leaf2 are running Active Active mode of EVPN-VXLAN. 202 CE is acting as bridge configured with vlans 204 Depends up on the test multicast traffic/host will be emulated by RT 206 The above configuration will serve as base configuration for all the 207 test cases. 209 3. Test Cases 211 The following tests are conducted to measure the learning rate,leave 212 rate,leave latency of IGMP messages which propagates in leaf and 213 spine. 215 3.1. How long it takes to learn ( X1...Xn) IGMP join messages in DUT 217 Objective: 219 To Record the time taken to learn X1...Xn igmp join generated by 220 host/hosts. 222 Topology : Topology 1 224 Procedure: 226 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 227 and leaf2 are connected to CE which are working in EVPN AA mode. 228 Configure a vlan in RT which is present in leaf1 then send igmp join 229 messages for groups X1... Xn from RT to this vlan present in leaf1. 230 Measure the time taken to learn X1..Xn (*,G) entries in the DUT. 232 Measurement : 234 Measure the time taken to learn the X1....Xn groups creating (*,G) 235 entries in the DUT. 237 Repeat these test and plot the data. The test is repeated for "N" 238 times and the values are collected. The time is calculated by 239 averaging the values obtained from "N" samples. 241 Time taken by DUT to learn and create X1...Xn (*,G ) entries in DUT 242 which is measured in sec = (T1+T2+..Tn/N) 244 3.2. How long it takes to clear the (*,G) entries in the DUT 246 Objective: 248 To Record the time taken to clear the X1... Xn (*,G) entries in DUT. 250 Topology : Topology 1 252 Procedure: 254 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 255 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 256 mode. Configure a vlan in RT which is present in leaf1, then send 257 igmp join messages for groups ranging from X1...Xn from RT to this 258 vlan present in leaf1 Then stop these igmp join messages from RT. 260 Measurement : 262 Measure the time taken to flush these X1...Xn (*,G) entries in DUT. 264 Repeat these test and plot the data. The test is repeated for "N" 265 times and the values are collected. The time is calculated by 266 averaging the values obtained from "N" samples. 268 Time taken by DUT to flush these X1...Xn (*,G) entries in sec = 269 (T1+T2+..Tn/N) 271 3.3. How long it takes the DUT to stop forwarding the traffic(Measuring 272 the leave latency) 274 Objective: 276 To Record the time taken by the DUT to stop forwarding the multicast 277 traffic during the receipt of IGMP leave from RT. 279 Topology : Topology 1 281 Procedure: 283 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 284 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 285 mode. Configure a vlan in RT which is present in leaf1, then send 286 igmp join from RT for this vlan to leaf1 for groups ranging from 287 "X1....Xn". Then send traffic to these groups from spine1. Traffic 288 flows from spine1 to leaf1. Send IGMP leave messages for these 289 groups from RT to leaf1. Measure the time taken by the DUT to stop 290 these multicast traffic to RT. 292 Measurement : 294 Measure the time taken by DUT to stop the multicast traffic flowing 295 towards RT. 297 Repeat these test and plot the data. The test is repeated for "N" 298 times and the values are collected. The time is calculated by 299 averaging the values obtained from "N" samples. 301 Time taken by DUT to stop the traffic towards RT connected in leaf1 302 in sec = (T1+T2+..Tn/N) 304 3.4. How long it takes to learn (X1...Xn) IGMP join messages for N 305 vlans in DUT 307 Objective: 309 To Record the time taken to learn X1...Xn IGMP join generated by 310 host/hosts located in N vlans. 312 Topology : Topology 1 314 Procedure: 316 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 317 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 318 mode. Configure N vlans in RT, these vlans must be present in leaf1, 319 then send igmp join messages for the groups ranging from X1...Xn for 320 these N vlans from RT. Measure the time taken to learn these X1..Xn 321 (*,G) entries in the DUT for N vlans. 323 Measurement : 325 Measure the time taken to learn the X1....Xn groups creating (*,G) 326 entries in the DUT for N vlans. 328 Repeat these test and plot the data. The test is repeated for "N" 329 times and the values are collected. The time is calculated by 330 averaging the values obtained from "N" samples. 332 Time taken by DUT to learn and create X1...Xn (*,G ) entries for N 333 vlans in DUT which is measured in sec = (T1+T2+..Tn/N) 335 3.5. How long it takes to clear the (*,G) entries in the DUT for N 336 vlans 338 Objective: 340 To Record the time taken to clear the X1... Xn (*,G) entries in DUT 341 for N vlans. 343 Topology : Topology 1 345 Procedure: 347 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 348 Leaf1 and leaf2 are connected to CE which are working in AA mode. 349 Configure N vlans in RT, these vlans must be present in leaf1, then 350 send igmp join messages for groups ranging from X1...Xn for these N 351 vlans from RT. Then stop these IGMP messages. 353 Measurement : 355 Measure the time taken to flush these X1...Xn (*,G) entries in DUT. 357 Repeat these test and plot the data. The test is repeated for "N" 358 times and the values are collected. The time is calculated by 359 averaging the values obtained from "N" samples. 361 Time taken by DUT to flush these X1...Xn (*,G) entries in sec = 362 (T1+T2+..Tn/N) 364 3.6. How long it takes the DUT to stop forwarding the traffic for N 365 vlans(Measuring the leave latency) 367 Objective: 369 To Record the time taken by the DUT to stop forwarding the multicast 370 traffic to N vlans during the receipt of IGMP leave messages from RT. 372 Topology : Topology 1 374 Procedure: 376 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 377 and leaf2 are connected to CE which are working in EVPN AA mode. 378 Configure N vlans in RT which are present in leaf1, then send igmp 379 join messages from RT for groups ranging from X1...Xn to these vlans 380 present in leaf1. Then send traffic to these groups from spine1. 381 Traffic flows from spine1 to leaf1. Send the IGMP leave messages for 382 these groups in all vlans. Measure the time taken by the DUT to stop 383 the traffic for these group flowing towards RT. 385 Measurement : 387 Measure the time taken by DUT to stop the multicast traffic flowing 388 towards RT. 390 Repeat these test and plot the data. The test is repeated for "N" 391 times and the values are collected. The time is calculated by 392 averaging the values obtained from "N" samples. 394 Time taken by DUT to stop the traffic towards RT in sec = 395 (T1+T2+..Tn/N) 397 3.7. How long it takes to learn (X1...Xn) IGMP join messages for N 398 vlans in DUT working EVPN AA mode 400 Objective: 402 To Record the time taken to learn X1...Xn IGMP join generated by 403 host/hosts located in N vlans in DUT operating in EVPN AA mode. 405 Topology : Topology 1 407 Procedure: 409 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 410 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 411 mode. Configure N vlans in RT, these vlans must be present in 412 leaf1,leaf2, then send igmp join messages for the groups ranging from 413 X1...Xn for these N vlans from RT to CE connected to leaf1 and leaf2 414 working EVPN AA mode.Measure the time taken to learn these X1..Xn 415 (*,G) entries in the DUT for N vlans. 417 Measurement : 419 Measure the time taken to learn the X1....Xn groups by creating (*,G) 420 entries in the DUT for N vlans. 422 Repeat these test and plot the data. The test is repeated for "N" 423 times and the values are collected. The time is calculated by 424 averaging the values obtained from "N" samples. 426 Time taken by DUT to learn and create X1...Xn (*,G ) entries for N 427 vlans which is measured in sec = (T1+T2+..Tn/N) 429 3.8. How long it takes to clear the (*,G) entries for N vlans in DUT 430 working EVPN AA 432 Objective: 434 To Record the time taken to clear the X1... Xn (*,G) entries in DUT 435 for N vlans. 437 Topology : Topology 1 439 Procedure: 441 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 442 Leaf1 and leaf2 are connected to CE which are working in AA mode. 443 Configure N vlans in RT, these vlans must be present in leaf1, then 444 send igmp join messages for groups ranging from X1...Xn for these N 445 vlans from RT to CE which is connected to leaf1 and leaf2 working in 446 EVPN AA mode.Then stop these IGMP messages. 448 Measurement : 450 Measure the time taken to flush these X1...Xn (*,G) entries in DUT. 452 Repeat these test and plot the data. The test is repeated for "N" 453 times and the values are collected. The time is calculated by 454 averaging the values obtained from "N" samples. 456 Time taken by DUT to flush these X1...Xn (*,G) entries in sec = 457 (T1+T2+..Tn/N) 459 3.9. How long it takes the DUT operating in EVPN AA to stop forwarding 460 the traffic for N vlans(Measuring the leave latency) 462 Objective: 464 To Record the time taken by the DUT to stop forwarding the multicast 465 traffic to N vlans during the receipt of IGMP leave messages from RT. 467 Topology : Topology 1 469 Procedure: 471 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 472 and leaf2 are connected to CE which are working in EVPN AA mode. 473 Configure N vlans in RT which are present in leaf1, then send igmp 474 join messages from RT connected to CE for groups ranging from X1...Xn 475 to these vlans. The CE in turn forwards the igmp messages to leaf1 476 and leaf2 operating in EVPN AA mode. Then send traffic to these 477 groups from spine1. Traffic flows from spine1 to CE. Send the IGMP 478 leave messages for these groups in all vlans from RT connected to CE. 479 Measure the time taken by the DUT to stop the traffic for these group 480 flowing towards RT. 482 Measurement : 484 Measure the time taken by DUT to stop the multicast traffic flowing 485 towards RT. 487 Repeat these test and plot the data. The test is repeated for "N" 488 times and the values are collected. The time is calculated by 489 averaging the values obtained from "N" samples. 491 Time taken by DUT to stop the traffic towards RT in sec = 492 (T1+T2+..Tn/N) 494 3.10. How long does it take the DUT in EVPN AA to handle Join Timeout 495 and stop forwarding 497 Objective: 499 To record the time takes for handling of Type-7 withdrawal and 500 clearing the state and stop forwarding the traffic. 502 Topology : Topology 1 504 Procedure: 506 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 507 and leaf2 are connected to CE which are working in EVPN AA mode. 508 Configure N vlans in RT which are present in leaf1, then send igmp 509 join messages from RT connected to CE for groups ranging from X1...Xn 510 to these vlans. The CE in turn forwards the igmp messages to leaf1 511 and leaf2 operating in EVPN AA mode. Then send traffic to these 512 groups from spine1. Traffic flows from spine1 to CE. Send the IGMP 513 leave messages for these groups in all vlans from RT connected to CE. 514 The iGMP leave must reach the leaf1. It will send type 7 withdrawal 515 to DUT working in EVPN AA. Measure the time taken by the DUT to stop 516 the traffic flowing to CE.This time will give the leave latency due 517 to type 7 withdrawal. 519 Measurement : 521 Measure the time taken by DUT to stop the multicast traffic flowing 522 towards RT. 524 Repeat these test and plot the data. The test is repeated for "N" 525 times and the values are collected. The time is calculated by 526 averaging the values obtained from "N" samples. 528 Time taken by DUT to stop the traffic towards RT in sec = 529 (T1+T2+..Tn/N) 531 3.11. How long does it take an Ingress to learn a remote Type-6 join, 532 create state and forwarding 534 Objective: 536 To record the time takes for forwarding the traffic by DUT after the 537 receipt of type 6 join from peer MHPE in same ESI. 539 Topology : Topology 1 541 Procedure: 543 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 544 and leaf2 are connected to CE which are working in EVPN AA mode. 545 Configure N vlans in RT which are present in leaf1, then send igmp 546 join messages from RT connected to CE for groups ranging from X1...Xn 547 to these vlans. The CE in turn forwards the igmp messages to leaf2 548 operating in EVPN AA mode. leaf2 and leaf1 are working EVPN AA mode. 549 Leaf 2 will send the type 6 join to the DUT(leaf 1).Then send traffic 550 to these groups from spine1. Traffic flows from spine1 to CE. 551 Measure the time taken by DUT to forward the traffic after the 552 receipt of type 6 join from leaf1. 554 Measurement : 556 Measure the time taken by DUT to forward the multicast traffic 557 flowing towards RT. 559 Repeat these test and plot the data. The test is repeated for "N" 560 times and the values are collected. The time is calculated by 561 averaging the values obtained from "N" samples. 563 Time taken by DUT to forward the traffic towards RT in sec = 564 (T1+T2+..Tn/N) 566 4. Link Flap 567 4.1. To Measure the multicast packet loss in EVPN AA scenario on a CE 568 link failure 570 Objective: 572 To measure the packet loss during the CE to DF link failure. 574 Topology : Topology 1 576 Procedure: 578 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 579 and leaf2 are connected to CE which are working in EVPN AA mode. 580 Configure N vlans in RT which are present in leaf1, then send igmp 581 join messages from RT connected to CE for groups ranging from X1...Xn 582 to these vlans. The CE in turn forwards the igmp messages to leaf1 583 and leaf2 operating in EVPN AA mode. Then send traffic to these 584 groups from spine1. Traffic flows from spine1 to CE. Fail the DF-CE 585 link. The NON DF now will act as DF and start forwarding the 586 multicast traffic. 588 Measurement : 590 Measure the multicast packet loss during the link failure.Repeat the 591 test "N" times and plot the data.The packet loss is calculated by 592 averaging the values obtained from "N" samples. 594 Packet loss in sec = (T1+T2+..Tn/N) 596 4.2. To Measure the multicast packet loss in EVPN AA scenario on a core 597 failure 599 Objective: 601 To measure the packet loss during the DF core failure 603 Topology : Topology 1 605 Procedure: 607 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 608 and leaf2 are connected to CE which are working in EVPN AA mode. 609 Configure N vlans in RT which are present in leaf1, then send igmp 610 join messages from RT connected to CE for groups ranging from X1...Xn 611 to these vlans. The CE in turn forwards the igmp messages to leaf1 612 and leaf2 operating in EVPN AA mode. Then send traffic to these 613 groups from spine1. Traffic flows from spine1 to CE. Fail the DF 614 core link. The NON DF now will act as the DF and starts forwarding 615 the multicast traffic. 617 Measurement : 619 Measure the multicast packet loss during the link failure.Repeat the 620 test "N" times and plot the data.The packet loss is calculated by 621 averaging the values obtained from "N" samples. 623 Packet loss in sec = (T1+T2+..Tn/N) 625 4.3. To Measure the multicast packet loss in EVPN AA scenario on a 626 routing failure 628 Objective: 630 To measure the packet loss during the DF routing failure 632 Topology : Topology 1 634 Procedure: 636 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 637 and leaf2 are connected to CE which are working in EVPN AA mode. 638 Configure N vlans in RT which are present in leaf1, then send igmp 639 join messages from RT connected to CE for groups ranging from X1...Xn 640 to these vlans. The CE in turn forwards the igmp messages to leaf1 641 and leaf2 operating in EVPN AA mode. Then send traffic to these 642 groups from spine1. Traffic flows from spine1 to CE. Fail the DF by 643 restart routing. The NON DF now will act as the DF and starts 644 forwarding the multicast traffic. 646 Measurement : 648 Measure the multicast packet loss during the link failure.Repeat the 649 test "N" times and plot the data.The packet loss is calculated by 650 averaging the values obtained from "N" samples. 652 Packet loss in sec = (T1+T2+..Tn/N) 654 5. Scale Convergence 655 5.1. To measure the packet loss during the core link failure. 657 Objective: 659 To Measure the convergence at a higher number of vlans and igmp 660 joins. 662 Topology : Topology 1 664 Procedure: 666 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 667 and leaf2 are connected to CE which are working in EVPN AA mode. 668 Configure N vlans in RT which are present in leaf1, then send igmp 669 join messages from RT connected to CE for groups ranging from X1...Xn 670 to these vlans. The CE in turn forwards the igmp messages to leaf1 671 and leaf2 operating in EVPN AA mode. Then send traffic to these 672 groups from spine1. Traffic flows from spine1 to CE. Fail the core 673 link of DF. The NON DF now will act as DF and start forwarding the 674 multicast traffic. The vlans and the multicast groups must be a 675 higher value of N taken at random. 677 Measurement : 679 Measure the packet loss in seconds once the core link is 680 restored.Repeat the test "N" times and plot the data.The packet loss 681 is calculated by averaging the values obtained from "N" samples. 683 Packet loss in sec = (T1+T2+..Tn/N) 685 6. High Availability 687 6.1. To Record the whether there is traffic loss due to routing engine 688 failover for redundancy test. 690 Objective: 692 To record traffic loss during routing engine failover. 694 Topology : Topology 3 696 Procedure: 698 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 699 and leaf2 are connected to CE which are working in EVPN AA mode. 700 Configure N vlans in RT which are present in leaf1, then send igmp 701 join messages from RT connected to CE for groups ranging from X1...Xn 702 to these vlans. The CE in turn forwards the igmp messages to leaf1 703 and leaf2 operating in EVPN AA mode. Then send traffic to these 704 groups from spine1. Traffic flows from spine1 to CE. Then perform a 705 routing engine failure. 707 Measurement : 709 There should be 0 traffic loss which is the ideal case, No change in 710 the DF role. DUT should not withdraw any routes.Repeat the test "N" 711 times and plot the data.The packet loss is calculated by averaging 712 the values obtained from "N" samples. 714 Packet loss in sec = (T1+T2+..Tn/N) 716 7. SOAK Test 718 This is measuring the performance of DUT running with scaled 719 configuration with traffic over a peroid of time "T'". In each 720 interval "t1" the parameters measured are CPU usage, memory usage, 721 crashes. 723 7.1. To Measure the stability of the DUT with scale and traffic. 725 Objective: 727 To measure the stability of the DUT in a scaled environment with 728 traffic. 730 Topology : Topology 3 732 Procedure: 734 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 735 and leaf2 are connected to CE which are working in EVPN AA mode. 736 Configure N vlans in RT which are present in leaf1, then send igmp 737 join messages from RT connected to CE for groups ranging from X1...Xn 738 to these vlans. The CE in turn forwards the igmp messages to leaf1 739 and leaf2 operating in EVPN AA mode. Then send traffic to these 740 groups from spine1. Traffic flows from spine1 to CE. 742 Measurement : 744 Take the hourly reading of CPU, process memory. There should not be 745 any leak, crashes, CPU spikes. 747 8. Acknowledgements 749 We would like to thank Al and Sarah for the support. 751 9. IANA Considerations 753 This memo includes no request to IANA. 755 10. Security Considerations 757 There is no additional consideration from RFC 6192. 759 11. References 761 11.1. Normative References 763 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 764 Requirement Levels", BCP 14, RFC 2119, 765 DOI 10.17487/RFC2119, March 1997, 766 . 768 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 769 Network Interconnect Devices", RFC 2544, 770 DOI 10.17487/RFC2544, March 1999, 771 . 773 [RFC2899] Ginoza, S., "Request for Comments Summary RFC Numbers 774 2800-2899", RFC 2899, DOI 10.17487/RFC2899, May 2001, 775 . 777 11.2. Informative References 779 [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., 780 Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based 781 Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February 782 2015, . 784 Appendix A. Appendix 786 Authors' Addresses 788 Sudhin Jacob (editor) 789 Juniper Networks 790 Bangalore, Karnataka 560103 791 India 793 Phone: +91 8061212543 794 Email: sjacob@juniper.net 795 Vikram Nagarajan 796 Juniper Networks 797 Bangalore, Karnataka 560103 798 India 800 Phone: +91 8061212543 801 Email: vikramna@juniper.net