Alcatel-Lucent Converged Backbone Transformation (CBT) Release 1.0 Provisioning Reference

Transcription

1 e Alcatel-Lucent Converged Backbone Transformation (CBT) Release 1.0 Provisioning Reference 3MM T001-GAZZZA ISSUE 1 February 2010

2 Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. Copyright 2010 Alcatel-Lucent. All Rights Reserved. Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside Alcatel-Lucent without its written authorization. 2 3MM T001-GAZZZA

3 Content About this document vii Purpose... vii Reason for revision... vii Intended audience... vii Assumptions...viii 1 Murray Hill Solution Validation 1 Introduction... 3 Executive Summary... 3 Scope of Testing... 3 Test Environment... 4 Test Lab Components... 4 Representative Test Configurations... 5 Test Area Summary... 9 Interoperability Test Cases GigE and LAG Functionality GigE Port Interworking GigE Port Throughput LACP LAG Interworking Multi-card LACP LAG Interworking Multi-card Static LAG Interworking LAG Hashing LAG Resilience LAG Link Failure...22 LAG Link Failure...24 LAG Link Failure with 802.3ah LAG Link Failure with 802.3ah Test Area: LAG MPLS FRR Resilience MPLS FRR LER Link Failure MPLS FRR LSR Link Failure MPLS FRR LX Link Failure MM T001-GAZZZA iii

4 MPLS FRR LER Link Failure with BFD MPLS FRR LSR Link Failure with BFD MPLS FRR LX Link Failure with BFD Additional Interoperability Test Cases DiffServ Traffic Engineering Quality of Service Disaster Recovery Synchronous Ethernet OT-10G Overclocking Villarceaux Solution Validation 49 Sub-Port level grooming ( MCC) Scope MCC interworking TESTS Introduction Network Elements and test equipment Network Management Network Integration testing restrictions Scenarios description Sub-Port Grooming 7750SR MCCPSS: EVPL- ASON-GR NICBT_1_2: MCC 10GbE sub port grooming with 1678MCC ASON-GR and no 7750 protection NICBT_1_2: MCC 10GbE sub port grooming with 1678MCC ASON-GR and LSP FRR protection Sub Port Grooming 7750SR MCC: EVPL-ASON-PRC NICBT_1_2: MCC 10GbE sub port grooming with 1678MCC ASON-PRC and LSP no protection NICBT_2_2: MCC 10GbE sub port grooming with 1678MCC ASON-PRC and LSP FRR protection Sub Port Grooming 7750SR MCC: EVPL-ASON-GR + LCAS NICBT_3_1: MCC 10GbE sub port grooming with 1678MCC ASON- GR/LCAS and LSP no protection Sub Port Grooming 7750SR MCC: SNCP iv 3MM T001-GAZZZA

5 NICBT_4_1: MCC 10GbE sub port grooming with 1678MCC SDH SNCP protection and LSP no protection NICBT_4_1: MCC 10GbE sub port grooming with 1678MCC SDH SNCP protection and LSP FRR protection Sub Port Grooming 7750SR LAG NICBT_5_1: 10GbE LAG with no protection Villarceaux Solution Validation 68 Port level grooming ( PSS) Scope PSS interworking TESTS Introduction Network Elements and test equipment Network Management Network Integration testing restrictions Scenarios description Port Grooming 7750SR PSSR1.1: WDM unprotected B&W NICBT_1_1: PSS 10GbE with no WDM protection and no LSP protection NICBT_1_2: PSS 10GbE with no WDM protection and LSP FRR protection NICBT_1_3: PSS 10GbE with no WDM protection and Primary/secondary LSP Port Grooming 7750SR PSSR1.1: WDM O-SNCP protection NICBT_2_1: PSS 10GbE with WDM O-SNCP protection and no LSP protection NICBT_2_2: PSS 10GbE with WDM O-SNCP protection and LSP FRR protection NICBT_2_3: PSS 10GbE with WDM O-SNCP protection and Primary/secondary LSP Port Grooming 7750SR PSSR1.1: WDM OCH protection NICBT_3_1: PSS 10GbE with WDM Optical channel protection and no LSP protection NICBT_3_2: PSS 10GbE with WDM Optical channel protection and LSP FRR protection MM T001-GAZZZA v

6 NICBT_3_3: PSS 10GbE with Optical channel protection and Primary/secondary LSP Port Grooming 7750SR PSSR1.1 LAG NICBT_4_1: 10GbE LAG with no WDM protection NICBT_4_2: 10GbE LAG with WDM O-SNCP protection NICBT_4_3: 10GbE LAG with WDM Optical Channel protection Antwerp Solution Validation 90 Port level grooming ( PSS) Kanata Solution Validation 92 Lambda level grooming ( PSS) Introduction Purpose Scope of Testing Test Environment Test Lab Components Representative Test Configuration...95 Test Case Summary Interoperability Test Cases DWDM channel support Alien Wavelength Power Adjust Support km Test IP protection Mechanisms and LAG Fault Detection FEC/EFEC Tests Failover Testing Glossary 111 vi 3MM T001-GAZZZA

7 About this document Purpose This document is intended to provide details around the validation configurations used for Alcatel-Lucent Converged Backbone Transformation Release 1.0. The information included in this document consists of test plan steps, diagrams, and configurations used. This testing was done across four different Alcatel-Lucent facilities. Please note the content and procedures within this document are only applicable to the Blueprint solution validated and not any other permutations of this solution. Please refer to the CBT R1.0 Solution Release Description for more information on known problems or solution clarifications This document is mainly indented to offer a view of the validation work done and the configurations used for testing. Reason for revision This is the first version of this document. Intended audience This document is intended for individuals who are interested in understanding the configurations used for the validation of the solution. 3MM T001-GAZZZA vii

8 Assumptions This document assumes that users have an understanding of the following: Broad knowledge of the ALU systems mentioned within the document Basic principles of telecommunication transmission Common telecommunication and system terminology (a glossary is provided in this document to assist you) Test sets and tools used in the telecommunication industry Local operations and functional procedures of your company Personal computer (PC) operation, common PC terminology, and navigational procedures in a windows-style user interface 3MM T001-GAZZZA viii

9 1 Murray Hill Solution Validation Port level grooming ( LX) 3MM T001-GAZZZA 1

10 DOCUMENT CHANGE RECORD VERSION DATE CHANGE DESCRIPTION v0.1 12/02/2009 Initial draft v0.2 12/10/2009 Updates test areas, and minor comments V1.0 12/10/2009 Baseline version, inserted e2e 3MM T001-GAZZZA 2

11 Introduction Executive Summary This document provides the test results for the Interoperability Testing for Converged Backbone Transformation (CBT) Port Level Grooming performed in the Alcatel-Lucent NAR IPTC Integration Lab and completed 11/20/09. Testing was based on the Converged Backbone Transformation Port Level Grooming ( ) Test Plan Version 1.1 [1]. Testing was performed to verify interoperability between the 7750SR and 1625LX as related to CBT Phase 1 Architecture [2]. Additional information is available in the other references listed. Scope of Testing The interoperability testing for port level grooming focused on the functionality and operations of Alcatel-Lucent products. The test cases were limited to a subset of the overall requirements and addressed basic interoperability and functionality. The scope of testing was constrained by the following items: 1. Test case configurations included epipes only. Service implementation, e.g., VLANs, epipes, QoS, priorities, marking, etc. were not defined in the requirements. 2. Various FRR scenarios (primary/secondary, primary/standby, etc.) were tested including basic FRR/SRLG. The FRR test cases included multiple failure points ah capabilities such as loopback validated at the product level. This is not in the scope of solution level validation. The only testing performed was for remote failure indication. 4. QoS test cases were added following completion of the initial interoperability test cases. The traffic distribution was assumed to be Voice (G.711 = 222 and/or G.729a = 82) 5%, Video (1518) 50%, and Internet (Imix) 45%. The reference bandwidth was 80% of the link rate, i.e., 8 Gbps. 5. QoS mappings were based on 802.1p marking. Voice traffic had the P-bit set to 5 which mapped to forwarding class EF which mapped to queue 6. Video traffic had the P-bit set to 4 which mapped to forwarding class H2 which mapped to queue 5. Internet traffic had the P-bit set to 0 which mapped to forwarding class BE which mapped to queue 1. These values were defined for sap-ingress and sap-egress and permitted using default network queue configurations. 6. Threshold failures were validated at the product level. This is not in the scope of solution level validation. Test cases measured detection plus failover. Test case passed if the failover time was less than 60 milliseconds, i.e.; the sum of the 10 milliseconds for detection and 50 milliseconds for switchover configuration was via the CLI SAM requirements were not tested at this time. This was however tested in other test facilities. 8. Only resilience testing was for Fast Reroute and no Optical Layer protection. 3 3MM T001-GAZZZA

12 9. Link failures tested included the following scenarios: a. Disconnect TX fiber b. Disconnect RX fiber c. Disconnect TX/RX fibers d. Disable interface 1 e. Disable interface 2 Note: Specific component (i.e. MDA, IOM, OT, OM, etc.) hardware failures were not tested. This is not in the scope of solution level validation. 10. The requirements do not discuss the type of XFPs. XFP-LRs (10GBASE-LR 1310 nm) were used in the 7750s for connections to the 1625s. XFP-SR1s (10GBASE-LR 1310 nm) and XFP- IR2s (10GBASE-ER 1550 nm) were used in the 1625s. The 7750 XFP-LRs support receive wavelengths to 1550 nm and interworked with the 1625 XFP-IR2s. XFP-SRs (10GBASE-SR 850 nm) were used for some connections between 7750s. Other XFPs were not tested. Test Environment Test Lab Components Table 1 represents the basic equipment used to support the interoperability testing. Tests performed after October 23 rd used 1625LX R Product Release 7750SR-7 7.0R4 1625LX R9.0.0_62 R9.0.1_2* *upgraded during tests Spirent Test Center (STC) V Table 1 CBT Port Grooming Interoperability Test Components The 7750SR-7s were equipped with Integrated Media Modules (IMMs), Input/Output Modules (IOMs) and Media Dependent Adapters (MDAs) to provide the required 10GigE interfaces. The following equipment was used: Quantity Description 2 IMM8-10GB-XFP 3 IMM4-10GB-XFP 2 M1-10GB-XFP Table G Components Depending on the configuration required for the test cases, the modules were installed in the appropriate 7750s. For example, in Figure 3 below, SR-A and SR-B each used an IMM8, SR-C and SR-MH each used an IMM4, and SR-CO used an IMM4 and two M20-10GB MDAs. 3MM T001-GAZZZA 4

13 The 1625s used Optical Translators (OTs) consisting of both 10G transponders and 40G muxponders to connect to the 7750s. These were OT (10G XFP ADD-DROP Tunable) and OT (40G XFP MUX Tunable). Configurations were modified for the test cases to maximize the interoperability between the different 7750 and 1625 components. Note: Failover tests with the OT-10G failed. Based on these results, the existing OT-10Gs (WWCL01) were replaced with the new OT-10Gs (WWCL03). The WWCL03 version can be configured for overclocking. Additional tests were performed with these modules. With this configuration the failover tests passed. Representative Test Configurations The testing used 3 basic configurations. The 7750SR-7s are designated with the SR prefix and the 1625LX with the LX prefix in the diagrams. The following diagrams represent the 3 base configurations which were used in testing. The last diagram shows the actual system setup being provided in the optical labs for testing. It provides a detailed view of the 1625 components represented by the generic LX-A/LX-B unit diagrams shown in the configurations and also used throughout the document. The first configuration, show in Figure 1, was used to test 10GigE interface interoperability and basic LAG functionality. Nxλ EAST SR-A LX-A LX-B SR-B LAG Nx10GigE N = 1 to 5 Nxλ WEST LAG Nx10GigE N = 1 to 5 STC Figure 1 10GigE Interface and LAG Functionality The following embedded files contain basic sample configurations used for tests cases associated with the first configuration. Parameters were changed during testing, as required. See appendix A-1: Configuration #1 CLI files for Node A and NodeB 5 3MM T001-GAZZZA

14 The second configuration, Figure 2, was used to test LAG failover scenarios. Nxλ EAST SR-CO PE SR-A P LAG Nx10GigE N = 1 to 5 LX-A Nxλ WEST LX-B LAG Nx10GigE N = 1 to 5 SR-B P SR-MH PE STC Figure 2 LAG Failover The following embedded files contain basic sample configurations used for tests cases associated with the second configuration. Parameters were changed during testing, as required. See appendix A-2: Configuration #2 CLI files for Nodes CO, A, B, and MH 3MM T001-GAZZZA 6

15 The final configuration, Figure 3, was used to test MPLS Fast Reroute (FRR) behavior. SR-A P 40GigE LAG Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P 20GigE LAG LX-A Nxλ WEST LX-B 20GigE LAG SR-C P STC Figure 3 MPLS Fast Reroute The following embedded files contain basic sample configurations used for tests cases associated with the third configuration. Parameters were changed during testing, as required. See appendix A-3: Configuration #3 CLI files for Nodes CO, A, B, MH, and C 7 3MM T001-GAZZZA

16 Figure Component Detailed View The following embedded file contains screen captures of the configuration and setup for the 1625 System 6 optical network. As indicated previously, the system was upgraded from Release to Release during testing. Tests completed using were not repeated with Also, additional tests were added using OT (10G XFP ADD-DROP Tunable) circuit packs with Apparatus Code (WWCL03). This component supports overclocking and is required to meet the 60 millisecond failover requirement. See appendix A-4: Configuration #4 CIT provisioning for the 1625 system See appendix A-6: TL1 level provisioning of the systems used for testing The following embedded file contains an overall detailed view of the end-to-end setup. It represents the end-to-end setup used for some of the QOS testing. See appendix A-5: End to end connectivity schematic 3MM T001-GAZZZA 8

17 Test Area Summary Table 3 provides a summary listing of the 16 test areas described in the test plan. Based on these test areas, detailed test cases were performed for three major areas: 10GigE and LAG Functionality, LAG Resilience, and MPLS LSP Resilience. Priorities were assigned to the test areas. A priority with an asterisk indicates that it is dependent on the results of a previous test area. Test cases in all test areas were executed. Test Plan Test Case Areas Test Area ID Priority Description 10GigE and LAG Functionality FUNC Interworking 001 High 10 GigE Port Interworking 002 High 10 GigE Port Throughput 003 Medium LACP LAG Interworking 004 High Multi-card LACP LAG Interworking 005 Low Multi-card Static LAG Interworking 006 High LAG Hashing LAG Resilience LAG LAG Link Failure 001 High LAG Link Failure 002 High LAG Link Failure 003 High* LAG Link Failure with 802.3ah 004 High* LAG Link Failure with 802.3ah MPLS LSP Resilience FRR MPLS FRR Link Failure 001 High MPLS FRR LER Link Failure 002 High MPLS FRR LSR Link Failure 003 High MPLS FRR LX Link Failure 004 High* MPLS FRR LER Link Failure with BFD 005 High* MPLS FRR LSR Link Failure with BFD 006 High* MPLS FRR LX Link Failure with BFD Table 3 Test Area Summary 9 3MM T001-GAZZZA

18 Time permitted adding test areas for DiffServ Traffic Engineering, Quality of Service, Disaster Recovery, Synchronous Ethernet, as well as additional tests for MPLS LSP failovers using a new OT-10G card configured for overclocking. These additional test cases are summarized in Table 4. Additional Test Areas Test Case ID Priority Description DiffServ Traffic Engineering TE 001 DS-TE Preemption Quality of Service QoS 001 Latency, Jitter, and Frame Loss Disaster Recovery DR 001 Node Failure Synchronous Ethernet SYNC 001 Clock distribution 1625 OT-10G Overclocking OTCLK 001 LSP Failover Table 4 Additional Test Area Summary Interoperability Test Cases The test cases per test area described in this section were designed to be a guide in performing the required interoperability testing. Each test case could require multiple specific tests to be performed and the number of actual tests performed varied based on testing results. Testing results dictated the addition of test cases and/or tests as needed. 3MM T001-GAZZZA 10

19 11 3MM T001-GAZZZA

20 10 GigE and LAG Functionality 10GigE Port Interworking Test Area: FUNC-001 Equipment: (2) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify that data can be exchanged between 10GigE ports Notes: Testing will be performed using XFP-LR for 7750SR and XFP-SR1 for 1625LX. XFP compatibility should be identified by comparing product specifications. The connection between the 7750 and 1625 will be a single 10 GigE LAG interface only. Data will be forwarded via local epipe services. Configuration: Nxλ EAST SR-A LX-A LX-B SR-B LAG Nx10GigE N = 1 to 5 Nxλ WEST LAG Nx10GigE N = 1 to 5 STC Procedure: 1. Verify that the links between the 7750SR and 1625LX is up. 2. Generate bi-directional data at 10 Gbps using the STC for a period of 1 minute. The data is transported through 7750SR-7A, 1625-LXA, 1625-LXB, and 7750SR-7B. 3. Verify that the data is flowing over the path. 4. Verify that no data is lost. 5. Investigate using random payload sizes and random data to verify transparent forwarding. If capabilities exist repeat steps 1 through 4 for a 15-minute test interval. Expected Results: 3MM T001-GAZZZA 12

21 The 10 GigE ports are active and transfer data at 10 Gbps. No data is lost. No PRBS errors are recorded for the applicable test scenarios. 10 GigE Port Throughput Test Area: FUNC-002 Equipment: (2) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify the throughput of the 10 GigE interfaces per RFC2544. Notes The connection between the 7750 and 1625 will be a single 10 GigE LAG interface only. Data will be forwarded via local epipe services. Throughput of the STC back-to-back at 10 Gbps needs to be benchmarked. The throughput through a single 7750 can be benchmarked, if required. Configuration: Nxλ EAST SR-A LX-A LX-B SR-B LAG Nx10GigE N = 1 to 5 Nxλ WEST LAG Nx10GigE N = 1 to 5 STC Procedure: 1. Perform RFC2544 throughput tests at 10 Gbps for packet sizes of 64, 128, 256, 512, 1024, 1280, and The data is transported through 7750SR-7, 7750SR-12A, 1625-LXA, 1625-LXB, and 7750SR-12B. 2. Record results. Expected Results: The devices under test transfer data at line rate. 13 3MM T001-GAZZZA

22 LACP LAG Interworking Test Area: FUNC-003 Equipment: (2) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Objective: To verify that LACP LAG can be established through 1625 and data can be exchanged over the LAG. Configuration: Nxλ EAST SR-A LX-A LX-B SR-B LAG Nx10GigE N = 1 to 5 Nxλ WEST LAG Nx10GigE N = 1 to 5 STC Procedure: 1. Configure LACP LAG with 1 port between 7750SRs and verify status is active. 2. Generate bi-directional data at 10 Gbps using the STC. 3. Verify that the data is flowing over the LAG. 4. Stop the data. 5. Verify that no data is lost. 6. Generate bi-directional data at 10 Gbps using the STC. 7. Verify that the data is flowing over the LAG. 8. Grow the LAG to 2 ports. 9. Stop the data. 10. Verify that no data is lost. 11. Generate bi-directional data at 10 Gbps using the STC. 12. Verify that the data is flowing over the LAG. 13. Grow the LAG to 3 ports. 14. Stop the data. 15. Verify that no data is lost. 16. Generate bi-directional data at 10 Gbps using the STC. 17. Verify that the data is flowing over the LAG. 3MM T001-GAZZZA 14

23 18. Grow the LAG to 4 ports. 19. Stop the data. 20. Verify that no data is lost. 21. Generate bi-directional data at 10 Gbps using the STC. 22. Verify that the data is flowing over the LAG. 23. Grow the LAG to 5 ports. 24. Stop the data. 25. Verify that no data is lost. Expected Results: The LAG is active and transfers data at 10 Gbps. No data is lost when ports are added to the LAG. 15 3MM T001-GAZZZA

24 Multi-card LACP LAG Interworking Test Area: FUNC-004 Equipment: (2) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify that LACP LAG can be established with ports across multiple cards. Note: Additional tests may be run with different LACP options if requirements specify more precise configurations. Configuration: Nxλ EAST SR-A LX-A LX-B SR-B LAG Nx10GigE N = 1 to 5 Nxλ WEST LAG Nx10GigE N = 1 to 5 STC Procedure: 1. Configure LACP LAG with 1 port between 7750SRs and verify status is active. 2. Generate bi-directional data at 10 Gbps using the STC. 3. Verify that the data is flowing over the LAG. 4. Stop the data. 5. Verify that no data is lost. 6. Generate bi-directional data at 10 Gbps using the STC. 7. Verify that the data is flowing over the LAG. 8. Grow the LAG to 2 ports with the second port on a different card. 9. Stop the data. 10. Verify that no data is lost. 11. Generate bi-directional data at 10 Gbps using the STC. 12. Verify that the data is flowing over the LAG. 3MM T001-GAZZZA 16

25 Expected Results: The LAG is active and transfers data at 10 Gbps. No data is lost when ports are added to the LAG across multiple cards. 17 3MM T001-GAZZZA

26 Multi-card Static LAG Interworking Test Area: FUNC-005 Equipment: (2) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify that Static LAG can be established with ports across multiple cards. Configuration: Nxλ EAST SR-A LX-A LX-B SR-B LAG Nx10GigE N = 1 to 5 Nxλ WEST LAG Nx10GigE N = 1 to 5 STC Procedure: 1. Configure Static LAG with 1 port between 7750SRs and verify status is active. 2. Generate bi-directional data at 10 Gbps using the STC. 3. Verify that the data is flowing over the LAG. 4. Stop the data. 5. Verify that no data is lost. 6. Generate bi-directional data at 10 Gbps using the STC. 7. Verify that the data is flowing over the LAG. 8. Grow the LAG to 2 ports with the second port on a different card. 9. Stop the data. 10. Verify that no data is lost. 11. Generate bi-directional data at 10 Gbps using the STC. 12. Verify that the data is flowing over the LAG. 13. Grow the LAG to 3 ports with the third port on the first card. 14. Stop the data. 15. Verify that no data is lost. 16. Generate bi-directional data at 10 Gbps using the STC. 17. Verify that the data is flowing over the LAG. 3MM T001-GAZZZA 18

27 Expected Results: The LAG is active and transfers data at 10 Gbps. No data is lost when ports are added to the LAG across multiple cards. 19 3MM T001-GAZZZA

28 LAG Hashing Test Area: FUNC-006 Equipment: (4) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify LAG hashing operation. Notes: The LAG hashing algorithm needs to be investigated to determine data streams and LSP configurations. The hashing algorithm for MPLS switched traffic is based on the whole label stack (up to 5 labels), along with the incoming port and system IP address. The EXP/TTL information in each label is not included in the hash algorithm. VLL traffic transmitted from a service access point (Etherpipe SAP) uses the service ID to pick one of the LAG paths. Configuration: Nxλ EAST SR-CO PE SR-A P LAG Nx10GigE N = 1 to 5 LX-A Nxλ WEST LX-B LAG Nx10GigE N = 1 to 5 SR-B P SR-MH PE STC Procedure: 1. Configure 8 VLAN epipes with control word. 2. Generate streams of bi-directional data over the VLANs using the STC. 3. Verify that the data is flowing over the LAG and record the physical interfaces used and the VLANs assigned. 4. Verify that no data is lost. 5. Disconnect one of the LAG ports. 3MM T001-GAZZZA 20

29 6. Verify that the data is flowing over the LAG and record the physical interface used and the VLANs assigned. 7. Verify that no data is lost. 8. Repeat steps 2 through 7 with step 5 reconnecting the LAG port. Expected Results: Data will be distributed over different physical interfaces based on the LAG hashing algorithm. 21 3MM T001-GAZZZA

30 LAG Resilience LAG Link Failure Test Area: LAG-001 Equipment: (4) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify LAG operation with a link failure between 7750 and Configuration: SR-CO PE SR-A P X LAG Nx10GigE N = 1 to 5 LX-A Nxλ EAST Nxλ WEST LX-B LAG Nx10GigE N = 1 to 5 SR-B P SR-MH PE STC Procedure: 1. Generate multiple streams of bi-directional data using the STC. 2. Verify that the data is flowing over different physical interfaces over the LAG. 3. Verify that no data is lost. 4. Break one of the LAG physical interfaces between SR-A and LX-A which is transporting data. 5. Verify that the 7750s at each end of the LAG recognize the failure. 6. Verify that the streams flowing over the LAG using the active physical interface do not lose any data. 7. Observe the behavior of the streams which had been flowing over the LAG using the physical interfaces which were not disconnected. 3MM T001-GAZZZA 22

31 8. Observe the behavior of the streams which had been flowing over the LAG using the physical interface which was disconnected. 9. Restore the LAG interface. 10. Verify that the 7750s at each end of the LAG recognize the restore. 11. Observe the behavior of the streams which had been flowing over the LAG using the physical interfaces which were not disconnected. 12. Observe the behavior of the streams which had been flowing over the LAG using the physical interface which was disconnected. 13. Repeat steps 1 through 12 for five failure scenarios: disconnect TX fiber, disconnect RX fiber, disconnect both fibers, disable 7750 interface, and disable 1625 interface. Expected Results: Both the local and remote 7750 recognize the LAG interface failure, i.e., the error indication is propagated end-to-end by the 1625s. Data streams, which were flowing over the active physical interface not failed, lose no data. Data streams flowing over the failed interface are reassigned to an active interface. When the interface is restored, no data should be lost. 23 3MM T001-GAZZZA

32 LAG Link Failure Test Area: LAG-002 Equipment: (4) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify LAG operation with a link failure between 1625s. Configuration: X Nxλ EAST SR-CO PE SR-A P LAG Nx10GigE N = 1 to 5 LX-A Nxλ WEST LX-B LAG Nx10GigE N = 1 to 5 SR-B P SR-MH PE STC Procedure: 1. Generate multiple streams of bi-directional data using the STC. 2. Verify that the data is flowing over different physical interfaces over the LAG. 3. Verify that no data is lost. 4. Break one of the LAG physical interfaces between LX-A and LX-B which is transporting data. 5. Verify that the 7750s at each end of the LAG recognize the failure. 6. Verify that the streams flowing over the LAG using the active physical interface do not lose any data. 7. Observe the behavior of the streams which had been flowing over the LAG using the physical interfaces which were not disconnected. 8. Observe the behavior of the streams which had been flowing over the LAG using the physical interface which was disconnected. 9. Restore the LAG interface. 10. Verify that the 7750s at each end of the LAG recognize the restore. 11. Observe the behavior of the streams which had been flowing over the LAG using the physical interfaces which were not disconnected. 3MM T001-GAZZZA 24

33 12. Observe the behavior of the streams which had been flowing over the LAG using the physical interface which was disconnected. 13. Repeat steps 1 through 12 for four failure scenarios: disconnect TX fiber, disconnect RX fiber, disconnect both fibers, and disable 1625 interface. 14. Perform the tests two times, failing/restoring a 40G OT port and failing/restoring a 10G OT port. Expected Results: Both the local and remote 7750 recognize the LAG interface failure, i.e., the error indication is propagated end-to-end by the 1625s. Data streams, which were flowing over the active physical interface not failed, lose no data. Data streams flowing over the failed interface are reassigned to an active interface. When the interface is restored, no data should be lost. 25 3MM T001-GAZZZA

34 LAG Link Failure with 802.3ah Test Area: LAG-003 The LAG connections will require a mechanism to determine link failure between 1625s and link failures between the 1625 and remote The LAG Failover test cases will determine if the 1625s propagate these failures ah can be enabled on the 7750 interfaces, but this will require the PDUs to be transparently forwarded by the 1625s. Equipment: (4) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify LAG operation with a link failure between 1625 s without 802.3ah enabled. Note: The default 802.3ah parameters are: transmit-interval 10 (in 100 milliseconds) with configurable values multiplier 5 with configurable values 2-5 Configuration: X Nxλ EAST SR-CO PE SR-A P LAG Nx10GigE N = 1 to 5 LX-A Nxλ WEST LX-B LAG Nx10GigE N = 1 to 5 SR-B P SR-MH PE STC Procedure: 1. Enable 802.3ah on the 7750 physical interfaces associated with the LAG. 2. Verify that 802.3ah PDUs are being received, the interfaces are active, and the LAG is up. 3. Generate multiple streams of bi-directional data using the STC. 4. Verify that the data is flowing over different physical interfaces over the LAG. 5. Verify that no data is lost. 3MM T001-GAZZZA 26

35 6. Break one of the LAG physical interfaces between LX-A and LX-B which is transporting data. 7. Verify that the 7750s at each end of the LAG recognize the failure. 8. Verify that the streams flowing over the LAG using the active physical interfaces do not lose any data. 9. Observe the behavior of the streams which had been flowing over the LAG using the physical interfaces which were not disconnected. 10. Observe the behavior of the streams which had been flowing over the LAG using the physical interface which was disconnected. 11. Restore the LAG interface. 12. Verify that the 7750s at each end of the LAG recognize the restore. 13. Observe the behavior of the streams which had been flowing over the LAG using the physical interfaces which were not disconnected. 14. Observe the behavior of the streams which had been flowing over the LAG using the physical interface which was disconnected. 15. Repeat steps 3 through 14 for multiple failure scenarios. Expected Results: Both the local and remote 7750 recognize the LAG interface failure, i.e., the 802.3ah PDUs are forwarded end-to-end by the 1625s. Data streams, which were flowing over the active physical interface not failed, lose no data. Data streams flowing over the failed interface are reassigned to an active interface. When the interface is restored, no data should be lost. 27 3MM T001-GAZZZA

36 LAG Link Failure with 802.3ah Test Area: LAG-004 The LAG connections will require a mechanism to determine link failure between 1625s and link failures between the 1625 and remote The LAG Failover test cases will determine if the 1625s propagate these failures ah can be enabled on the 7750 interfaces, but this will require the PDUs to be transparently forwarded by the 1625s. Equipment: (4) 7750SR (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify LAG operation with a link failure between 7750 and 1625 with 802.3ah enabled. Note: The default 802.3ah parameters are: transmit-interval 10 (in 100 milliseconds) with configurable values multiplier 5 with configurable values 2-5 Configuration: SR-CO PE SR-A P X LAG Nx10GigE N = 1 to 5 LX-A Nxλ EAST Nxλ WEST LX-B LAG Nx10GigE N = 1 to 5 SR-B P SR-MH PE STC Procedure: 1. Enable 802.3ah on the 7750 physical interfaces associated with the LAG. 2. Verify that 802.3ah PDUs are being received, the interfaces are active, and the LAG is up. 3. Generate multiple streams of bi-directional data using the STC. 4. Verify that the data is flowing over different physical interfaces over the LAG. 5. Verify that no data is lost. 3MM T001-GAZZZA 28

37 6. Break one of the LAG physical interfaces between LX-A and LX-B which is transporting data. 7. Verify that the 7750s at each end of the LAG recognize the failure. 8. Verify that the streams flowing over the LAG using the active physical interface do not lose any data. 9. Observe the behavior of the streams which had been flowing over the LAG using the physical interfaces which were not disconnected. 10. Observe the behavior of the streams which had been flowing over the LAG using the physical interface which was disconnected. 11. Restore the LAG interface. 12. Verify that the 7750s at each end of the LAG recognize the restore. 13. Observe the behavior of the streams which had been flowing over the LAG using the physical interfaces which were not disconnected. 14. Observe the behavior of the streams which had been flowing over the LAG using the physical interface which was disconnected. 15. Repeat steps 3 through 14 for five failure scenarios: disconnect TX fiber, disconnect RX fiber, disconnect both fibers, disable 7750 interface, and disable 1625 interface. Expected Results: Both the local and remote 7750 recognize the LAG interface failure, i.e., the 802.3ah PDUs are forwarded end-to-end by the 1625s. Data streams, which were flowing over the active physical interface not failed, lose no data. Data streams flowing over the failed interface are reassigned to an active interface. When the interface is restored, no data should be lost. 29 3MM T001-GAZZZA

38 MPLS FRR Resilience MPLS FRR LER Link Failure Test Area: FRR-001 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.0) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify failover and restoration times. Note: This configuration can be used to test various MPLS/FRR configuration options, e.g., primary/secondary, primary/standby, SRLG. Configuration: SR-CO PE X SR-A P SR-MH P 40GigE LAG 20GigE LAG LX-A Nxλ EAST Nxλ WEST LX-B 40GigE LAG 20GigE LAG SR-B PE/P SR-C P STC Procedure: 1. Configure an epipe via an LSP between SR-CO (PE) and SR-B (PE/P) following the path SR-CO, SR-A, LX-A, LX-B, SR-B. Enable FRR. The LAG connections should be configured with a single port only to allow FRR to occur for a single link failure. 2. Generate bi-directional data at pps using the STC. 3. Verify that the data is flowing over the path. 4. Verify that detours have been established. 5. Break the link between SR-CO and SR-A. 6. Verify that the data is flowing over the detours in both directions. 7. Stop the traffic and record the lost packets in each direction. 3MM T001-GAZZZA 30

39 8. Restart the generators. 9. Restore the link. 10. Verify that the data reverts to the primary path. 11. Stop the traffic and record the lost packets in each direction. 12. Repeat steps 2 through 11 for four failure scenarios: disconnect TX fiber, disconnect RX fiber, disconnect both fibers, and disable 7750 interface. 13. Repeat procedure for various FRR parameters. Expected Results: The failover time is less than 60 msec (10 msec port failure detect time + 50 msec switching time). The revert time is 0 msec (make before break). 31 3MM T001-GAZZZA

40 MPLS FRR LSR Link Failure Test Area: FRR-002 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.1) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify failover and restoration times. Note: This configuration can be used to test various MPLS/FRR configuration options, e.g., primary/secondary, primary/standby, SRLG. Configuration: SR-A P 40GigE LAG X Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P LX-A 20GigE LAG Nxλ WEST LX-B 20GigE LAG SR-C P STC Procedure: 1. Configure an epipe via an LSP between SR-CO (PE) and SR-B (PE/P) following the path SR-CO, SR-A, LX-A, LX-B, SR-B. Enable FRR. The LAG connections should be configured with a single port only to allow FRR to occur for a single link failure. 2. Generate bi-directional data at pps using the STC. 3. Verify that the data is flowing over the path. 4. Verify that detours have been established. 5. Break the link between SR-A and LX-A. 6. Verify that the data is flowing over the detours in both directions. 7. Stop the traffic and record the lost packets in each direction. 8. Restart the generators. 9. Restore the link. 3MM T001-GAZZZA 32

41 10. Verify that the data reverts to the primary path. 11. Stop the traffic and record the lost packets in each direction. 12. Repeat steps 2 through 11 for various failure scenarios. Expected Results: The failover time is less than 60 msec (10 msec port failure detect time + 50 msec switching time). The revert time is 0 msec (make before break). 33 3MM T001-GAZZZA

42 MPLS FRR LX Link Failure Test Area: FRR-003 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.1) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify failover and restoration times. Note: This configuration can be used to test various MPLS/FRR configuration options, e.g., primary/secondary, primary/standby, SRLG. Configuration: SR-A P 40GigE LAG X Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P 20GigE LAG LX-A Nxλ WEST LX-B 20GigE LAG SR-C P STC Procedure: 1. Configure an epipe via an LSP between SR-CO (PE) and SR-B (PE/P) following the path SR-CO, SR-A, LX-A, LX-B, SR-B. Enable FRR. The LAG connections should be configured with a single port only to allow FRR to occur for a single link failure. 2. Generate bi-directional data at pps using the STC. 3. Verify that the data is flowing over the path. 4. Verify that detours have been established. 5. Break the link between LX-A and LX-B. 6. Verify that the data is flowing over the detours in both directions. 7. Stop the traffic and record the lost packets in each direction. 8. Restart the generators. 9. Restore the link. 10. Verify that the data reverts to the primary path. 11. Stop the traffic and record the lost packets in each direction. 3MM T001-GAZZZA 34

43 12. Repeat steps 2 through 11 for various failure scenarios. Expected Results: The failover time is less than 60 msec (10 msec port failure detect time + 50 msec switching time). The revert time is 0 msec (make before break). 35 3MM T001-GAZZZA

44 MPLS FRR LER Link Failure with BFD Test Area: FRR-004 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.1) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify failover and restoration times. Note: This configuration can be used to test various MPLS/FRR configuration options, e.g., primary/secondary, primary/standby, SRLG. The default BFD parameters are: transmit-interval 100 (in milliseconds) with configurable values receive-interval 100 (in milliseconds) with configurable values multiplier 3 with configurable values 3-20 Configuration: X SR-A P 40GigE LAG Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P 20GigE LAG LX-A Nxλ WEST LX-B 20GigE LAG SR-C P STC Procedure: 1. Configure BFD on the router interfaces associated with the LSP path, and enable BFD for OSPF and RSVP. 2. Configure an epipe via an LSP between SR-CO (PE) and SR-B (PE/P) following the path SR-CO, SR-A, LX-A, LX-B, SR-B. Enable FRR. The LAG connections should be configured with a single port only to allow FRR to occur for a single link failure. 3. Generate bi-directional data at pps using the STC. 4. Verify that the data is flowing over the path. 5. Verify that detours have been established. 3MM T001-GAZZZA 36

45 6. Break the link between SR-CO and SR-A. 7. Verify that the data is flowing over the detours in both directions. 8. Stop the traffic and record the lost packets in each direction. 9. Restart the generators. 10. Restore the link. 11. Verify that the data reverts to the primary path. 12. Stop the traffic and record the lost packets in each direction. 13. Repeat steps 2 through 11 for various failure scenarios. Expected Results: The failover time is less than 50 msec plus the BFD detect time. The revert time is 0 msec (make before break). 37 3MM T001-GAZZZA

46 MPLS FRR LSR Link Failure with BFD Test Area: FRR-005 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.1) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify failover and restoration times. Note: This configuration can be used to test various MPLS/FRR configuration options, e.g., primary/secondary, primary/standby, SRLG. The default BFD parameters are: transmit-interval 100 (in milliseconds) with configurable values receive-interval 100 (in milliseconds) with configurable values multiplier 3 with configurable values 3-20 Configuration: SR-A P 40GigE LAG X Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P LX-A 20GigE LAG Nxλ WEST LX-B 20GigE LAG SR-C P STC Procedure: 1. Configure BFD on the router interfaces associated with the LSP path, and enable BFD for OSPF and RSVP. 2. Configure an epipe via an LSP between SR-CO (PE) and SR-B (PE/P) following the path SR-CO, SR-A, LX-A, LX-B, SR-B. Enable FRR. The LAG connections should be configured with a single port only to allow FRR to occur for a single link failure. 3. Generate bi-directional data at pps using the STC. 4. Verify that the data is flowing over the path. 5. Verify that detours have been established. 3MM T001-GAZZZA 38

47 6. Break the link between SR-A and LX-A. 7. Verify that the data is flowing over the detours in both directions. 8. Stop the traffic and record the lost packets in each direction. 9. Restart the generators. 10. Restore the link. 11. Verify that the data reverts to the primary path. 12. Stop the traffic and record the lost packets in each direction. 13. Repeat steps 2 through 11 for various failure scenarios. Expected Results: The failover time is less than 50 msec plus the BFD detect time. The revert time is 0 msec (make before break). 39 3MM T001-GAZZZA

48 MPLS FRR LX Link Failure with BFD Test Area: FRR-006 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.1) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify failover and restoration times. Note: This configuration can be used to test various MPLS/FRR configuration options, e.g., primary/secondary, primary/standby, SRLG. The default BFD parameters are: transmit-interval 100 (in milliseconds) with configurable values receive-interval 100 (in milliseconds) with configurable values multiplier 3 with configurable values 3 20 Configuration: SR-A P 40GigE LAG X Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P 20GigE LAG LX-A Nxλ WEST LX-B 20GigE LAG SR-C P STC Procedure: 1. Configure BFD on the router interfaces associated with the LSP path, and enable BFD for OSPF and RSVP. 2. Configure an epipe via an LSP between SR-CO (PE) and SR-B (PE/P) following the path SR-CO, SR-A, LX-A, LX-B, SR-B. Enable FRR. The LAG connections should be configured with a single port only to allow FRR to occur for a single link failure. 3. Generate bi-directional data at pps using the STC. 4. Verify that the data is flowing over the path. 5. Verify that detours have been established. 3MM T001-GAZZZA 40

49 6. Break the link between LX-A and LX-B. 7. Verify that the data is flowing over the detours in both directions. 8. Stop the traffic and record the lost packets in each direction. 9. Restart the generators. 10. Restore the link. 11. Verify that the data reverts to the primary path. 12. Stop the traffic and record the lost packets in each direction. 13. Repeat steps 2 through 11 for various failure scenarios. Expected Results: The failover time is less than 50 msec plus the BFD detect time. The revert time is 0 msec (make before break). 41 3MM T001-GAZZZA

50 Additional Interoperability Test Cases DiffServ Traffic Engineering Test Area: TE-001 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.1) (1) Spirent STC (V3.30) Note: Combinations of IMMs, MDAs, and OTs will be tested. Objective: To verify DiffServ traffic engineering functionality and preemption. Configuration: SR-A P 40GigE LAG Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P 20GigE LAG LX-A Nxλ WEST LX-B 20GigE LAG SR-C P STC Procedure: 1. Configure RSVP for diffserv-te mam and te-class priorities. 2. Configure two LSPs of the same class-type with bandwidth and with different priorities. The sum of the bandwidth is greater than the bandwidth defined for the class-type. 3. Enable the LSP with the lower priority. 4. Generate uni-directional data at pps using the STC. 5. Verify that the data is flowing over the path. 6. Enable the LSP with the higher priority. 7. Verify that the higher priority LSP preempts the lower priority LSP. 8. Verify that the lower priority LSP re-computes it path. 9. Verify that the data on the lower priority LSP resumes and observe impact. Expected Results: 3MM T001-GAZZZA 42

51 For hard preemption (preemption-timer = 0), data should stop on the lower priority LSP until a new path is computed. For soft preemption, data should continue to flow over the original path until a new path is computed. 43 3MM T001-GAZZZA

52 Quality of Service Test Area: QoS-001 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.1) (1) Spirent STC (V3.30) Objective: To verify QoS behavior and measure latency, jitter, and frame loss. Configuration: SR-A P 40GigE LAG Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P 20GigE LAG LX-A Nxλ WEST LX-B 20GigE LAG SR-C P STC Procedure: 1. Configure sap-ingress and spa-egress policies and apply to epipe services. 2. Generate voice, video, and internet data for 60 seconds using the STC. The reference load is 80% of the link capacity, i.e. 8 Gbps. Load will be generated at 20, 40, 60, 80, 100, 120, and 140 percent of the reference load. The distribution of the traffic will be 5% voice, 50% video, and 45% internet data. 3. Record latency, jitter, and frame loss for all streams. 4. Repeat steps 2 and 3 for various loads. Expected Results: The latency is less than 10 milliseconds for voice and 32 milliseconds for video. Frame loss is less than 1x10-4 for voice and video (for the tests voice and video should have no frame loss). Internet traffic has the lowest priority and frames will be dropped during congestion. 3MM T001-GAZZZA 44

53 Disaster Recovery Test Area: DR-001 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.1) (1) Spirent STC (V3.30) Objective: To verify 7750SR recovers following warm reboot and power cycle. Configuration: SR-A P 40GigE LAG Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P 20GigE LAG LX-A Nxλ WEST LX-B 20GigE LAG SR-C P STC Procedure: 1. Generate bi-directional data at pps using the STC. 2. Reset Verify that the data recovers. 4. Repeat steps 1 through 3 for various resets. Expected Results: The router will recover and data traffic will resume. 45 3MM T001-GAZZZA

54 Synchronous Ethernet Test Area: SYNC-001 Equipment: (5) 7750SR-7 (7.0R4) (2) 1625 LX (R9.0.1) (1) Spirent STC (V3.30) Objective: To verify the functionality of synchronous ethernet. Configuration: SR-A P 40GigE LAG Nxλ EAST 40GigE LAG SR-B PE/P SR-CO PE SR-MH P 20GigE LAG LX-A Nxλ WEST LX-B 20GigE LAG SR-C P STC Procedure: 1. Connect a BITS clock to SR-CO. 2. Configure card 3 mda 2 for sync-e. 3. Enable bits sync-if-timing on SR-CO. 4. Verify that the Reference BITS is up, qualified for use, and the timing is Master Locked. 5. Configure SR-A and SR-B for sync-e. 6. Configure ref1 sync-if-timing on SR-A and SR-B. 7. Verify that Reference Input 1 is up, qualified for use, and the timing is Master Locked. 8. Connect a T-Berd to SR-A and SR-B BITS clock ports via a special connector for Rx only. 9. Record the clock frequency and jitter measurements. 10. Verify sync-e stability over 24-hour period. 11. Disconnect timing port and verify switching from Master Locked to Master Holdover does not affect data. 12. Reconnect timing port and verify switching from Master Holdover to Master Locked does not affect data. 3MM T001-GAZZZA 46