idnits 2.17.1 draft-vikjac-bmwg-evpnmultest-03.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 20 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 date (December 13, 2019) is 1596 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2544' is defined on line 740, but no explicit reference was found in the text == Unused Reference: 'RFC2899' is defined on line 745, but no explicit reference was found in the text == Unused Reference: 'RFC7432' is defined on line 751, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 4 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: Informational Juniper Networks 5 Expires: June 15, 2020 December 13, 2019 7 Benchmarking Methodology for EVPN Multicasting 8 draft-vikjac-bmwg-evpnmultest-03 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 June 15, 2020. 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 55 1.2. Terminologies . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Test Topology . . . . . . . . . . . . . . . . . . . . . . . . 4 57 3. Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . 6 58 3.1. Learning Rate . . . . . . . . . . . . . . . . . . . . . . 6 59 3.2. Flush Rate . . . . . . . . . . . . . . . . . . . . . . . 7 60 3.3. Leave Latency . . . . . . . . . . . . . . . . . . . . . . 7 61 3.4. Join Latency . . . . . . . . . . . . . . . . . . . . . . 8 62 3.5. Flush Rate of N vlans in DUT . . . . . . . . . . . . . . 8 63 3.6. Leave Latency of N Vlans in DUT . . . . . . . . . . . . . 9 64 3.7. Join Latency of N vlans in DUT working EVPN AA mode . . . 10 65 3.8. Flush Rate of DUT working EVPN AA . . . . . . . . . . . . 10 66 3.9. Leave Latency of DUT operating in EVPN AA . . . . . . . . 11 67 3.10. Join Latency with reception of Type 6 route . . . . . . . 11 68 4. Link Flap . . . . . . . . . . . . . . . . . . . . . . . . . . 12 69 4.1. Packet Loss measurement in DUT due to CE link Failure . . 12 70 4.2. Core Link Failure in EVPN AA . . . . . . . . . . . . . . 13 71 4.3. Routing Failure in DUT operating in EVPN-VXLAN AA . . . . 13 72 5. Scale Convergence . . . . . . . . . . . . . . . . . . . . . . 14 73 5.1. Core Link Failure. . . . . . . . . . . . . . . . . . . . 14 74 6. High Availability . . . . . . . . . . . . . . . . . . . . . . 15 75 6.1. Routing Engine Fail over. . . . . . . . . . . . . . . . . 15 76 7. SOAK Test . . . . . . . . . . . . . . . . . . . . . . . . . . 15 77 7.1. Stability of the DUT with traffic. . . . . . . . . . . . 15 78 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 79 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 80 10. Security Considerations . . . . . . . . . . . . . . . . . . . 16 81 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 82 11.1. Normative References . . . . . . . . . . . . . . . . . . 17 83 11.2. Informative References . . . . . . . . . . . . . . . . . 17 84 Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 17 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 87 1. Introduction 89 IGMP proxy over EVPN-VXLAN is defined in draft-ietf-bess-evpn-IGMP- 90 mld-proxy-02,and is being deployed in data center networks. 91 Specifically this document defines the methodologies for benchmarking 92 IGMP proxy convergence,leave latency Scale,Core isolation, high 93 availability and longevity. 95 1.1. Requirements Language 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in RFC 2119 [RFC2119]. 101 1.2. Terminologies 103 All-Active Redundancy Mode: When all PEs attached to an Ethernet 104 segment are allowed to forward known unicast traffic to/from that 105 Ethernet segment for a given VLAN, then the Ethernet segment is 106 defined to be operating in All-Active redundancy mode. 108 AA: All Active mode 110 CE: Customer Router/Devices/Switch. 112 DF: Designated Forwarder 114 DUT: Device under test. 116 EBGP: Exterior Border Gateway Protocol. 118 Ethernet Segment (ES): When a customer site (device or network) is 119 connected to one or more PEs via a set of Ethernet links, then that 120 set of links is referred to as an 'Ethernet segment'. 122 EVI: An EVPN instance spanning the leaf,spine devices participating 123 in that EVPN. 125 EVPN: Ethernet Virtual Private Network 127 Ethernet Segment Identifier (ESI): A unique non-zero identifier that 128 identifies an Ethernet segment is called an 'Ethernet Segment 129 Identifier'. 131 Ethernet Tag: An Ethernet tag identifies a particular broadcast 132 domain, e.g., a VLAN. An EVPN instance consists of one or more 133 broadcast domains. 135 Interface: Physical interface of a router/switch. 137 IGMP: Internet Group Management Protocol 139 IBGP: Interior Border Gateway Protocol 141 IRB: Integrated routing and bridging interface 142 MAC: Media Access Control addresses on a PE. 144 MLD: Multicast Listener Discovery 146 NVO: Network Virtualization Overlay 148 RT Traffic Generator. 150 Sub Interface Each physical Interfaces is subdivided into Logical 151 units. 153 SA Single Active 155 Single-Active Redundancy Mode: When only a single PE, among all the 156 PEs attached to an Ethernet segment, is allowed to forward traffic 157 to/from that Ethernet segment for a given VLAN, then the Ethernet 158 segment is defined to be operating in Single-Active redundancy mode. 160 VXLAN: Virtual Extensible LAN 162 2. Test Topology 164 EVPN Overlay Network running on leaf1, leaf2 leaf3,spine1 and spine 2 165 : 167 Topology Diagram 168 RT 169 +--------------+ +--------------+ 170 RT | | | +-------------------+ 171 +---------+ spine1 +----------------------------------+ 172 | | | spine2 | | 173 | | | | | 174 +----+---------+---------+ +----+----+----+------------------+ 175 | | | | | | 176 | | | | | | 177 | | | | | | 178 | | | | | | 179 | | | | | | 180 RT +---------+-----+---------+---+-------+----++ +--+-----------+----+ 181 +-------------+ | | | | leaf3 | 182 ++ leaf1 | | leaf2 | | | 183 | DUT | | | | | 184 +----+----------+ +---+--------+----+ +--------+----------+ 185 | | | | 186 | | | | 187 | | | | 188 | | | | 189 +-+-----------------+------+ | | 190 | | +--+ RT ++ RT 191 | CE | RT 192 | +-------+ 193 +-------------------+ 194 CE connected to leaf1 and leaf2 in EVPN-VXLAN Active-Active mode. 196 Topology 1 198 Topology Diagram 200 Figure 1 202 There are six routers in the topology. Leaf1,leaf2, 203 leaf3,spine1,spine2 emulating a data center network. CE is a 204 customer device connected to leaf1 and leaf2, it is configured with 205 bridge domains in different vlans. The traffic generator is 206 connected to CE,leaf1,leaf2,leaf3,spine1 and spine 2 to emulate 207 multicast source and host generating IGMP join/leave. 209 All routers except CE are configured with EBGP for the underlay 211 All router are configured with EVPN-VXLAN overlay 213 All leaves and spine must be configured "N" EVPN-VXLAN EVI's 215 Leaf1 and Leaf2 must be configured with ESI per vlan or ESI on 216 Interface. 218 Leaf1 and leaf2 are running Active Active mode of EVPN-VXLAN. 220 CE is acting as bridge configured with vlans 222 Depends up on the test multicast traffic/host will be emulated by RT 224 The above configuration will serve as base configuration for all the 225 test cases. 227 3. Test Cases 229 The following tests are conducted to measure the learning rate,leave 230 rate,leave latency of IGMP messages which propagates in leaf and 231 spine. 233 3.1. Learning Rate 235 Objective: 237 To Record the time taken to learn X1...Xn IGMP join generated by 238 host/hosts. 240 Topology : Topology 1 242 Procedure: 244 Configure "N" EVPN-VXLAN EVI in leaf1,leaf2,leaf3,spine1 and 245 spine2.Leaf1 and leaf2 are connected to CE which are working in EVPN- 246 VXLAN AA mode. Send IGMP membership report for groups X1... Xn from 247 RT to one vlan present in leaf1 which is a part of EVPN-VLXAN EVI. 248 Measure the time taken to learn X1..Xn (*,G) entries in the DUT. 250 Measurement : 252 Measure the time taken to learn the X1....Xn groups creating (*,G) 253 entries in the DUT. 255 The test is repeated for "N" times and the values are collected. The 256 time is calculated by averaging the values obtained from "N" samples. 258 Learning Rate = (T1+T2+..Tn)/N 260 3.2. Flush Rate 262 Objective: 264 To Record the time taken to clear the X1... Xn (*,G) entries in DUT. 266 Topology : Topology 1 268 Procedure: 270 Configure "N" EVPN-VXLAN EVI in leaf1,leaf2,leaf3,spine1 and spine2. 271 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 272 mode. Send IGMP membership report for groups ranging from X1...Xn 273 from RT to one vlan present in leaf1 which is a part of EVPN-VXLAN 274 EVI. Then stop these IGMP membership report from RT. 276 Measurement : 278 Measure the time taken to flush these X1...Xn (*,G) entries in DUT. 280 The test is repeated for "N" times and the values are collected. The 281 time is calculated by averaging the values obtained from "N" samples. 283 Flush Rate = (T1+T2+..Tn)/N 285 3.3. Leave Latency 287 Objective: 289 To Record the time taken by the DUT to stop forwarding the multicast 290 traffic during the receipt of IGMP leave from RT. 292 Topology : Topology 1 294 Procedure: 296 Configure "N" EVPN-VXLAN EVI in leaf1,leaf2,leaf3,spine1 and spine2. 297 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 298 mode. Send IGMP membership report for groups ranging from "X1....Xn" 299 from RT to a vlan present in leaf1 which is a part of EVPN-VXLAN EVI. 300 Then send traffic to these groups from spine1. Traffic flows from 301 spine1 to leaf1. Send IGMP leave messages for these groups from RT 302 to leaf1. Measure the time taken by the DUT to stop these multicast 303 traffic to RT. This can be measure by the time taken to clear the 304 (*,G) entries from the DUT. 306 Measurement : 308 Measure the time taken by DUT to clear the (*,G) entries and stop 309 forwarding the traffic. 311 The test is repeated for "N" times and the values are collected. The 312 time is calculated by averaging the values obtained from "N" samples. 314 Leave Latency = (T1+T2+..Tn)/N 316 3.4. Join Latency 318 Objective: 320 To Record the time taken by the DUT to create IGMP entries for N 321 vlans. 323 Topology : Topology 1 325 Procedure: 327 Configure "N" EVPN-VXLAN EVI's in leaf1,leaf2,leaf3,spine1 and 328 spine2. Leaf1 and leaf2 are connected to CE which are working in 329 EVPN AA mode. Send IGMP membership report for groups ranging from 330 X1...Xn for each vlan configured in leaf1 EVPN-VXLAN EVI's from 331 RT.Measure the time taken to learn these X1..Xn (*,G) entries in the 332 DUT for N vlans. 334 Measurement : 336 Measure the time taken to learn the X1....Xn groups creating (*,G) 337 entries in the DUT for N vlans. 339 The test is repeated for "N" times and the values are collected. The 340 time is calculated by averaging the values obtained from "N" samples. 342 Join Latency = (T1+T2+..Tn)/N 344 3.5. Flush Rate of N vlans in DUT 346 Objective: 348 To Record the time taken to clear the X1... Xn (*,G) entries in DUT 349 for N vlans. 351 Topology : Topology 1 353 Procedure: 355 Configure "N" EVPN-VXLAN EVI in leaf1,leaf2,leaf3,spine1 and spine2. 356 Leaf1 and leaf2 are connected to CE which are working in EVPN-VXLAN 357 AA mode. Send IGMP membership report for groups ranging from X1...Xn 358 for each vlan configured in leaf1 EVPN-VXLAN EVI's from RT.Stop the 359 IGMP membership report. Measure the time taken to flush these X1..Xn 360 (*,G) entries in the DUT for N vlans 362 Measurement : 364 Measure the time taken to flush these X1...Xn (*,G) entries in DUT. 366 The test is repeated for "N" times and the values are collected. The 367 time is calculated by averaging the values obtained from "N" samples. 369 Flush rate for N vlans = (T1+T2+..Tn)/N 371 3.6. Leave Latency of N Vlans in DUT 373 Objective: 375 To Record the time taken by the DUT to stop forwarding the multicast 376 traffic to N vlans during the receipt of IGMP leave messages from RT. 378 Topology : Topology 1 380 Procedure: 382 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 383 and leaf2 are connected to CE which are working in EVPN AA mode. 384 Send IGMP membership report for groups ranging from X1...Xn for each 385 vlan configured in leaf1 EVPN-VXLAN EVI's from RT. Then send traffic 386 to these groups from spine1. Traffic flows from spine1 to leaf1. 387 Send the IGMP leave messages for these groups in all vlans. Measure 388 the time taken by the DUT to stop the multicast traffic. 390 Measurement : 392 Measure the time taken by DUT to stop the multicast traffic flowing 393 towards RT. 395 The test is repeated for "N" times and the values are collected. The 396 time is calculated by averaging the values obtained from "N" samples. 398 Leave Latency = (T1+T2+..Tn)/N 400 3.7. Join Latency of N vlans in DUT working EVPN AA mode 402 Objective: 404 To Record the time taken to learn X1...Xn IGMP join generated by 405 host/hosts located in N vlans in DUT operating in EVPN AA mode. 407 Topology : Topology 1 409 Procedure: 411 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2. 412 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 413 mode. Configure N vlans in RT, these vlans must be present in 414 leaf1,leaf2, then send IGMP membership report for the groups ranging 415 from X1...Xn for these N vlans from RT to CE connected to leaf1 and 416 leaf2 working EVPN AA mode.Measure the time taken to learn these 417 X1..Xn (*,G) entries in the DUT for N vlans. 419 Measurement : 421 Measure the time taken to learn the X1....Xn groups by creating (*,G) 422 entries in the DUT for N vlans. 424 The test is repeated for "N" times and the values are collected. The 425 time is calculated by averaging the values obtained from "N" samples. 427 Join Latency = (T1+T2+..Tn)/N 429 3.8. Flush Rate of DUT working EVPN AA 431 Objective: 433 To Record the time taken to clear the X1... Xn (*,G) entries in DUT 434 for N vlans. 436 Topology : Topology 1 438 Procedure: 440 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2. 441 Leaf1 and leaf2 are connected to CE which are working in AA mode. 442 Configure N vlans in RT, these vlans must be present in leaf1, then 443 send IGMP join messages for groups ranging from X1...Xn for these N 444 vlans from RT to CE which is connected to leaf1 and leaf2 working in 445 EVPN AA mode.Then stop these IGMP messages. 447 Measurement : 449 Measure the time taken to flush these X1...Xn (*,G) entries in DUT. 451 The test is repeated for "N" times and the values are collected. The 452 time is calculated by averaging the values obtained from "N" samples. 454 Flush Rate= (T1+T2+..Tn)/N 456 3.9. Leave Latency of DUT operating in EVPN AA 458 Objective: 460 To Record the time taken by the DUT to stop forwarding the multicast 461 traffic to N vlans during the receipt of IGMP leave messages from RT. 463 Topology : Topology 1 465 Procedure: 467 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 468 and leaf2 are connected to CE which are working in EVPN AA mode. 469 Configure N vlans in RT which are present in leaf1, then send IGMP 470 join messages from RT connected to CE for groups ranging from X1...Xn 471 to these vlans. The CE in turn forwards the IGMP messages to leaf1 472 and leaf2 operating in EVPN AA mode. Then send traffic to these 473 groups from spine1. Traffic flows from spine1 to CE. Send the IGMP 474 leave messages for these groups in all vlans from RT connected to CE. 475 Measure the time taken by the DUT to stop the traffic for these group 476 flowing towards RT. 478 Measurement : 480 Measure the time taken by DUT to stop the multicast traffic flowing 481 towards RT. 483 Repeat these test and plot the data. The test is repeated for "N" 484 times and the values are collected. The time is calculated by 485 averaging the values obtained from "N" samples. 487 Leave Latency = (T1+T2+..Tn/N) 489 3.10. Join Latency with reception of Type 6 route 491 Objective: 493 To record the time takes for forwarding the traffic by DUT after the 494 receipt of type 6 join from peer MHPE in same ESI. 496 Topology : Topology 1 497 Procedure: 499 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 500 and leaf2 are connected to CE which are working in EVPN AA mode. 501 Configure N vlans in RT which are present in leaf1, then send IGMP 502 join messages from RT connected to CE for groups ranging from X1...Xn 503 to these vlans. The CE in turn forwards the IGMP messages to leaf2 504 operating in EVPN AA mode. leaf2 and leaf1 are working EVPN AA mode. 505 Leaf 2 will send the type 6 join to the DUT(leaf 1).Then send traffic 506 to these groups from spine1. Traffic flows from spine1 to CE. 507 Measure the time taken by DUT to forward the traffic after the 508 receipt of type 6 join from leaf1. 510 Measurement : 512 Measure the time taken by DUT to forward the multicast traffic 513 flowing towards RT. 515 Repeat these test and plot the data. The test is repeated for "N" 516 times and the values are collected. The time is calculated by 517 averaging the values obtained from "N" samples. 519 Time taken by DUT to forward the traffic towards RT in sec = 520 (T1+T2+..Tn/N) 522 4. Link Flap 524 4.1. Packet Loss measurement in DUT due to CE link Failure 526 Objective: 528 To measure the packet loss during the CE to DF link failure. 530 Topology : Topology 1 532 Procedure: 534 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 535 and leaf2 are connected to CE which are working in EVPN AA mode. 536 Configure N vlans in RT which are present in leaf1, then send IGMP 537 join messages from RT connected to CE for groups ranging from X1...Xn 538 to these vlans. The CE in turn forwards the IGMP messages to leaf1 539 and leaf2 operating in EVPN AA mode. Then send traffic to these 540 groups from spine1. Traffic flows from spine1 to CE. Fail the DF-CE 541 link. The NON DF now will act as DF and start forwarding the 542 multicast traffic. 544 Measurement : 546 Measure the multicast packet loss during the link failure.Repeat the 547 test "N" times and plot the data.The packet loss is calculated by 548 averaging the values obtained from "N" samples. 550 Packet loss in sec = (T1+T2+..Tn)/N 552 4.2. Core Link Failure in EVPN AA 554 Objective: 556 To measure the packet loss during the DF core failure 558 Topology : Topology 1 560 Procedure: 562 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 563 and leaf2 are connected to CE which are working in EVPN AA mode. 564 Configure N vlans in RT which are present in leaf1, then send IGMP 565 join messages from RT connected to CE for groups ranging from X1...Xn 566 to these vlans. The CE in turn forwards the IGMP messages to leaf1 567 and leaf2 operating in EVPN AA mode. Then send traffic to these 568 groups from spine1. Traffic flows from spine1 to CE. Fail the DF 569 core link. The NON DF now will act as the DF and starts forwarding 570 the multicast traffic. 572 Measurement : 574 Measure the multicast packet loss during the link failure.Repeat the 575 test "N" times and plot the data.The packet loss is calculated by 576 averaging the values obtained from "N" samples. 578 Packet loss in sec = (T1+T2+..Tn)/N 580 4.3. Routing Failure in DUT operating in EVPN-VXLAN AA 582 Objective: 584 To measure the packet loss during the DF routing failure 586 Topology : Topology 1 588 Procedure: 590 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 591 and leaf2 are connected to CE which are working in EVPN AA mode. 592 Configure N vlans in RT which are present in leaf1, then send IGMP 593 join messages from RT connected to CE for groups ranging from X1...Xn 594 to these vlans. The CE in turn forwards the IGMP messages to leaf1 595 and leaf2 operating in EVPN AA mode. Then send traffic to these 596 groups from spine1. Traffic flows from spine1 to CE. Fail the DF by 597 restart routing. The NON DF now will act as the DF and starts 598 forwarding the multicast traffic. 600 Measurement : 602 Measure the multicast packet loss during the link failure.Repeat the 603 test "N" times and plot the data.The packet loss is calculated by 604 averaging the values obtained from "N" samples. 606 Packet loss in sec = (T1+T2+..Tn)/N 608 5. Scale Convergence 610 5.1. Core Link Failure. 612 Objective: 614 To Measure the convergence at a higher number of vlans and IGMP 615 membership reports. 617 Topology : Topology 1 619 Procedure: 621 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 622 and leaf2 are connected to CE which are working in EVPN AA mode. 623 Configure N vlans in RT which are present in leaf1, then send IGMP 624 membership report from RT connected to CE for groups ranging from 625 X1...Xn to these vlans. The CE in turn forwards the IGMP messages to 626 leaf1 and leaf2 operating in EVPN AA mode. Then send traffic to 627 these groups from spine1. Traffic flows from spine1 to CE. Fail the 628 core link of DF. The NON DF now will act as DF and start forwarding 629 the multicast traffic.The vlans and the multicast groups must be a 630 higher value of N taken at random. 632 Measurement : 634 Measure the packet loss in seconds once the core link is 635 restored.Repeat the test "N" times and plot the data.The packet loss 636 is calculated by averaging the values obtained from "N" samples. 638 Packet loss in sec = (T1+T2+..Tn/N) 640 6. High Availability 642 6.1. Routing Engine Fail over. 644 Objective: 646 To record traffic loss during routing engine failover. 648 Topology : Topology 3 650 Procedure: 652 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 653 and leaf2 are connected to CE which are working in EVPN AA mode. 654 Configure N vlans in RT which are present in leaf1, then send IGMP 655 membership report from RT connected to CE for groups ranging from 656 X1...Xn to these vlans. The CE in turn forwards the IGMP messages to 657 leaf1 and leaf2 operating in EVPN AA mode. Then send traffic to 658 these groups from spine1. Traffic flows from spine1 to CE. Then 659 perform a routing engine failure. 661 Measurement : 663 The expectation of the test is 0 traffic loss with no change in the 664 DF role. DUT should not withdraw any routes.But in cases where the 665 DUT is not property synchronized between master and standby,due to 666 that packet loss are observed. In that scenario the packet loss is 667 measured.The test is repeated for "N" times and the values are 668 collected.The packet loss is calculated by averaging the values 669 obtained by "N" samples. 671 Packet loss in sec = (T1+T2+..Tn)/N 673 7. SOAK Test 675 This is measuring the performance of DUT running with scaled 676 configuration with traffic over a peroid of time "T'". In each 677 interval "t1" the parameters measured are CPU usage, memory usage, 678 crashes. 680 7.1. Stability of the DUT with traffic. 682 Objective: 684 To measure the stability of the DUT in a scaled environment with 685 traffic. 687 Topology : Topology 3 689 Procedure: 691 Configure "N" EVPN-VXLAN in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 692 and leaf2 are connected to CE which are working in EVPN AA mode. 693 Configure N vlans in RT which are present in leaf1, then send IGMP 694 membership report from RT connected to CE for groups ranging from 695 X1...Xn to these vlans. The CE in turn forwards the IGMP messages to 696 leaf1 and leaf2 operating in EVPN AA mode. Then send traffic to 697 these groups from spine1. Traffic flows from spine1 to CE. 699 Measurement : 701 Take the hourly reading of CPU, process memory.There should not be 702 any leak, crashes, CPU spikes. Th CPU spike is determined as the CPU 703 usage which shoots at 40 to 50 percent of the average usage. The 704 average value vary from device to device. Memory leak is determined 705 by increase usage of the memory for EVPN-VPWS process. The 706 expectation is under steady state the memory usage for EVPN- 707 VXLAN,IGMP processes should not increase. 709 8. Acknowledgments 711 We would like to thank Al and Sarah for the support. 713 9. IANA Considerations 715 This memo includes no request to IANA. 717 10. Security Considerations 719 The benchmarking tests described in this document are limited to the 720 performance characterization of controllers in a lab environment with 721 isolated networks. The benchmarking network topology will be an 722 independent test setup and MUST NOT be connected to devices that may 723 forward the test traffic into a production network or misroute 724 traffic to the test management network. Further, benchmarking is 725 performed on a "black-box" basis, relying solely on measurements 726 observable external to the controller. Special capabilities SHOULD 727 NOT exist in the controller specifically for benchmarking purposes. 728 Any implications for network security arising from the controller 729 SHOULD be identical in the lab and in production networks. 731 11. References 733 11.1. Normative References 735 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 736 Requirement Levels", BCP 14, RFC 2119, 737 DOI 10.17487/RFC2119, March 1997, 738 . 740 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 741 Network Interconnect Devices", RFC 2544, 742 DOI 10.17487/RFC2544, March 1999, 743 . 745 [RFC2899] Ginoza, S., "Request for Comments Summary RFC Numbers 746 2800-2899", RFC 2899, DOI 10.17487/RFC2899, May 2001, 747 . 749 11.2. Informative References 751 [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., 752 Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based 753 Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February 754 2015, . 756 Appendix A. Appendix 758 Authors' Addresses 760 Sudhin Jacob (editor) 761 Juniper Networks 762 Bangalore, Karnataka 560103 763 India 765 Phone: +91 8061212543 766 Email: sjacob@juniper.net 768 Vikram Nagarajan 769 Juniper Networks 770 Bangalore, Karnataka 560103 771 India 773 Phone: +91 8061212543 774 Email: vikramna@juniper.net