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

Transcription

1 Alcatel-Lucent Converged Backbone Transformation (CBT) Release.0 Provisioning Reference 3MM-0100-ADAB-GAZZZA ISSUE 1 November 010

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 011 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. ii 3MM-0100-ADAB-GAZZZA Issue 1 November 010

3 Content About this document iv Purpose... iv Reason for revision... iv Intended audience... iv Assumptions... v 1 Murray Hill Solution Validation Interworking... 1 Introduction 3 Purpose... 3 Scope of Testing... 3 Test Environment 5 Test Lab Components... 5 Representative Test Configurations... 5 Test Case Summary 8 Interoperability Test Cases 15 CFP Interoperability XFP/SFP+ Muxponder Interoperability Performance (Transponder)... 0 Performance (Muxponder)... Fast Reroute Network Resiliency (Transponder)... 4 Fast Reroute Network Resiliency (Muxponder)... 6 Network Element Restoration (Transponder)... 8 Network Element Restoration (Muxponder) Synchronous Ethernet (Transponder)... 3 Synchronous Ethernet (Muxponder) Glossary 36 3MM-0100-ADAB-GAZZZA Issue 1 November 010 iii

4 About this document Purpose This document is intended to provide details around the validation configurations used for Alcatel-Lucent Converged Backbone Transformation Release.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 R.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-0100-ADAB-GAZZZA Issue 1 November 010 iv

5 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-0100-ADAB-GAZZZA Issue 1 November 010 v

6

7 1 Murray Hill Solution Validation Interworking 3MM-0100-ADAB-GAZZZA 1 Issue 1 November 010

8 Converged Backbone Transformation R.0 Port Level Grooming ( 7750 SR) Alcatel-Lucent NAR IPTC Integration Lab 3MM-0100-ADAB-GAZZZA Issue 1 November 010

9 Introduction Purpose This document identifies the lab environment and test cases in support of Interoperability Testing for Converged Backbone Transformation (CBT) R.0 Port Level Grooming. It is based on the initial test cases identified for interoperability tests and augmented by the requirements defined in the CBT_R_0_Requirement_Validation_Coverage_Matrix [1]. Testing will verify interoperability between the 7750SR and 1830PSS. The port level grooming tests will be performed by personnel in Murray Hill, NJ and will leverage the use of equipment from both NAR IPTC and the Optical 1830 R&D/NPI labs. Additional information is available in the other references listed. Scope of Testing The interoperability testing for port level grooming will focus on the functionality and operations of Alcatel-Lucent products. The test cases address basic interoperability and functionality The scope of testing is constrained by the following items: 1. Test case configurations will include epipes only.. FRR test cases limited to single configuration (FRR/primary/standby) with multiple failure points configuration will be via CLI. 560 SAM requirements will not be tested at this time. 4. Only resilience testing will be for R-RES-F1 Fast Reroute and no Optical Layer protection. 5. Link failures will be tested with each of the following scenarios: a. Disconnect TX fiber b. Disconnect RX fiber c. Disconnect TX/RX fibers NOTE: Time permitting and if possible, disabling interfaces as well as component resets(e.g. MDA, IOM, OT, and OM) will also be tested. 3MM-0100-ADAB-GAZZZA 3 Issue 1 November 010

10 6. Testing of interfaces will depend on availability of CFPs, XFPs, and SPF+s. Testing will primarily focus on: Verifying basic interoperability 100 Gbps interfaces with BASE-LR4 CFP Verifying basic interoperability 100 Gbps interfaces with BASE-LR10 CFP Verifying basic interoperability 10 Gbps interfaces with 10GBASE-LR SFP+ Verifying network resiliency using Add/Drop shelf LOS alarm propagation, MPLS Fast Reroute failover and revert Verifying network resiliency using Muxponder shelf LOS alarm propagation, MPLS Fast Reroute failover and revert Verifying operation of and need for 80.3ah Verifying operation of and need for BFD with millisecond timers Verifying synchronous ethernet capability Measuring latency and jitter for select traffic streams 4 3MM-0100-ADAB-GAZZZA Issue 1 November 010

11 Test Environment Test Lab Components Table 1 represents the basic equipment to be available to support the interoperability testing. Product Release 7750 SR R5 R3.0 Spirent TestCenter (STC) BITS Clock N/A ANT-0 (for MTIE analysis) or equivalent N/A Table 1 CBT R.0 Port Grooming Interoperability Test Components Representative Test Configurations The testing will use basic configurations. The 7750 SR-1s will be installed in the 1830 R&D/NPI lab. Single mode fiber patches are available between the NAR IPTC lab and the Optical 1830 area for connections to the Spirent TestCenter and 7750 SR-7 required for MPLS Fast Reroute. The first configuration, show in Figure 1, will test 100 GigE interface interoperability with the Add/Drop Transponder. 3MM-0100-ADAB-GAZZZA 5 Issue 1 November 010

12 Test Set be be AD AD 7750 SR 7750 SR 7750 SR Figure 1 CBT R.0 Port Grooming Add/Drop Transponder Configuration 6 3MM-0100-ADAB-GAZZZA Issue 1 November 010

13 The second configuration, show in Figure, will test 100 GigE interface interoperability with the Muxponder. Test Set Test Set Mux Mux 7750 SR 7750 SR 7750 SR Figure CBT R.0 Port Grooming Muxponder Configuration 3MM-0100-ADAB-GAZZZA 7 Issue 1 November 010

14 Test Case Summary The following table is a detailed view of the test cases to be executed. Execution Priority Area/Test Case # Description CFP Interoperability # of Related Tests CFP-001 BASE-LR4 (4λx5G) CFP Verify link active between 7750SR ports via optical core with OT-4. 1 CFP Verify bi-directional data flow across link (patterns: incrementing, fixed 0x00, PRBS). CFP Break TX from 7750 to OT-4 and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. CFP Break RX to 7750 from OT-4 and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. CFP Break TX and RX between 7750 and OT-4 and verify failure alarm CFP Break TX from OT-4 to OM and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. CFP Break RX to OT-4 from OD and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. CFP Break TX and RX between OT-4 and OM/OD and verify failure alarm CFP Break TX from OM to OD between optical NEs and verify failure alarm CFP Break RX to OM from OD between optical NEs and verify failure alarm CFP Break TX and RX between OM/ODs and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. CFP-00 BASE-LR10 (10λx10G) 1 CFP Verify link active between 7750SR ports via optical core with OT CFP Verify bi-directional data flow across link (patterns: incrementing, fixed 0x00, PRBS). 1 CFP Break TX from 7750 to OT-4 and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 CFP Break RX to 7750 from OT-4 and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 CFP Break TX and RX between 7750 and OT-4 and verify failure alarm MM-0100-ADAB-GAZZZA Issue 1 November 010

15 1 CFP Break TX from OT-4 to OM and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 CFP Break RX to OT-4 from OD and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 CFP Break TX and RX between OT-4 and OM/OD and verify failure alarm 1 CFP Break TX from OM to OD between optical NEs and verify failure alarm 1 CFP Break RX to OM from OD between optical NEs and verify failure alarm 1 CFP Break TX and RX between OM/ODs and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. CFP-003 BASE-LR4 (4λx5G) and BASE-LR10 (10λx10G) 1 CFP Verify link active between 7750SR ports via optical core with OT CFP Verify bi-directional data flow across link (patterns: incrementing, fixed 0x00, PRBS). 1 CFP Break TX from 7750 to OT-4 (BASE-LR4) and verify failure alarm 1 CFP Break RX to 7750 from OT-4 (BASE-LR4) and verify failure alarm 1 CFP Break TX and RX between 7750 (BASE-LR4) and OT-4 and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 CFP Break TX from OT-4 (BASE-LR4) to OM and verify failure alarm CFP Break RX to OT-4 (BASE-LR4) from OD and verify failure alarm CFP Break TX and RX between OT-4 (BASE-LR4) and OM/OD and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. CFP Break TX from OM to OD between optical NEs and verify failure alarm CFP Break RX to OM from OD between optical NEs and verify failure alarm CFP Break TX and RX between OM/ODs and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. CFP Break TX from 7750 to OT-4 (BASE-LR10) and verify failure alarm CFP Break RX to 7750 from OT-4 (BASE-LR10) and verify failure alarm CFP Break TX and RX between 7750 and OT-4 (BASE-LR10) and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. CFP Break TX from OT-4 (BASE-LR10) to OM and verify failure alarm CFP Break RX to OT-4 (BASE-LR10) from OD and verify failure alarm 1 CFP Break TX and RX between OT-4 (BASE-LR10) and OM/OD and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. XFP-001 XFP Muxponder Interoperability (XFP Tests will be executed if SFP+ equipment is unavailable) 7750SR (10GBASE-LR 1310 nm) and 10x10G Muxponder (10GBASE- LR 1310 nm) 3MM-0100-ADAB-GAZZZA 9 Issue 1 November 010 3

16 1 XFP Verify link active between 7750SR ports via optical core with Muxponder 1 1 XFP Verify bi-directional data flow across link (patterns: incrementing, fixed 3 0x00, PRBS). 1 XFP Break TX from 7750 to Muxponder and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 XFP Break RX to 7750 from Muxponder and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 XFP Break TX and RX between 7750 and Muxponder and verify failure alarm 1 XFP Break TX from Muxponder to OM and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 XFP Break RX to Muxponder from OD and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 XFP Break TX and RX between Muxponder and OM/OD and verify failure alarm 1 XFP Break TX from OM to OD between optical NEs and verify failure alarm 1 XFP Break RX to OM from OD between optical NEs and verify failure alarm 1 XFP Break TX and RX between OM/ODs and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. XFP SR (10GBASE-LR 1310 nm) and 10x10G Muxponder (10GBASE- ER 1550 nm) 1 XFP Verify link active between 7750SR ports via optical core with Muxponder. 1 1 XFP Verify bi-directional data flow across link (patterns: incrementing, fixed 3 0x00, PRBS). 1 XFP Break TX from 7750 to Muxponder and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 XFP Break RX to 7750 from Muxponder and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 XFP Break TX and RX between 7750 and Muxponder and verify failure alarm 1 XFP Break TX from Muxponder to OM and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 XFP Break RX to Muxponder from OD and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 XFP Break TX and RX between Muxponder and OM/OD and verify failure alarm 1 XFP Break TX from OM to OD between optical NEs and verify failure alarm 1 XFP Break RX to OM from OD between optical NEs and verify failure alarm 1 XFP Break TX and RX between OM/ODs and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. SFP+ Muxponder Interoperability (SFP+ tests will be executed if equipment is available) 1 SFP SR SFP+ (10GBASE-LR 1310 nm) and 10x10G Muxponder XFP (10GBASE-LR 1310 nm) 1 SFP Verify link active between 7750SR ports via optical core with Muxponder 1 1 SFP Verify bi-directional data flow across link 1 1 SFP Break TX from 7750 to Muxponder and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 SFP Break RX to 7750 from Muxponder and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 SFP Break TX and RX between 7750 and Muxponder and verify failure alarm 1 SFP Break TX from Muxponder to OM and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 10 3MM-0100-ADAB-GAZZZA Issue 1 November 010

17 1 SFP Break RX to Muxponder from OD and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. 1 SFP Break TX and RX between Muxponder and OM/OD and verify failure alarm 1 SFP Break TX from OM to OD between optical NEs and verify failure alarm 1 SFP Break RX to OM from OD between optical NEs and verify failure alarm 1 SFP Break TX and RX between OM/ODs and verify failure alarm propagated. Verify port recovery when restored and data flow resumes. Performance Perf-001 BASE-LR4 (4λx5G) Perf Verify 10 Gbps data transfer. Measure latency and jitter. 1 Perf Verify 100 Gbps capability using daisy-chain. 1 4 Perf Perform RFC544 tests, if test set is available. 1 Perf-00 BASE-LR10 (10λx10G) Perf Verify 10 Gbps data transfer. Measure latency and jitter. 1 Perf Verify 100 Gbps capability using daisy-chain. 1 4 Perf Perform RFC544 tests, if test set is available. 1 Perf-003 BASE-LR4 (4λx5G) and BASE-LR10 (10λx10G) Perf Verify 10 Gbps data transfer. Measure latency and jitter. 1 Perf Verify 100 Gbps capability using daisy-chain. 1 4 Perf Perform RFC544 tests, if test set is available. 1 Perf x10G Muxponder CBR Transport Perf Verify 10 Gbps data transfer over 10x10G muxponder with CBR transport. Measure latency and jitter. Perf Verify 100 Gbps capability over 10x10G muxponder with CBR transport using daisy-chain. 4 Perf Perform RFC544 tests over 10x10G muxponder with CBR transport, if test set is available. Fast Reroute Network Resiliency FRR-001 BASE-LR4 (4λx5G) 3 FRR Break TX and RX between 7750 and OT-4 and verify failure < 50 msec. 1 3 FRR Restore TX and RX between 7750 and OT-4 and verify no frame loss for 1 revert. 3 FRR Break TX and RX between OT-4 and OM/OD and verify failover < 50 1 msec. 3 FRR Restore TX and RX between OT-4 and OM/OD and verify no frame loss for 1 revert. 3 FRR Break TX and RX between OM/ODs and verify failover < 50 msec. 1 3 FRR Restore TX and RX between OM/ODs and verify no frame loss for revert. 1 FRR-00 BASE-LR10 (10λx10G) FRR Break TX and RX between 7750 and OT-4 and verify failure < 50 msec. 1 FRR Restore TX and RX between 7750 and OT-4 and verify no frame loss for 1 revert. FRR Break TX and RX between OT-4 and OM/OD and verify failover < 50 1 msec. FRR Restore TX and RX between OT-4 and OM/OD and verify no frame loss for 1 revert. FRR Break TX and RX between OM/ODs and verify failover < 50 msec. 1 FRR Restore TX and RX between OM/ODs and verify no frame loss for revert. 1 FRR-003 BASE-LR4 (4λx5G) and BASE-LR10 (10λx10G) 3MM-0100-ADAB-GAZZZA 11 Issue 1 November

18 FRR FRR FRR FRR Break TX and RX between 7750 and OT-4 (BASE-LR4) and verify failure < 50 msec. Restore TX and RX between 7750 and OT-4 (BASE-LR4) and verify no frame loss for revert. Break TX and RX between OT-4 (BASE-LR4) and OM/OD and verify failover < 50 msec. Restore TX and RX between OT-4 (BASE-LR4) and OM/OD and verify no frame loss for revert. FRR Break TX and RX between OM/ODs and verify failover < 50 msec. 1 FRR Restore TX and RX between OM/ODs and verify no frame loss for revert. 1 FRR Break TX and RX between 7750 and OT-4 (BASE-LR10) and verify 1 failure < 50 msec. FRR Restore TX and RX between 7750 and OT-4 (BASE-LR10) and verify 1 no frame loss for revert. FRR Break TX and RX between OT-4 (BASE-LR10) and OM/OD and 1 verify failover < 50 msec. FRR Restore TX and RX between OT-4 (BASE-LR10) and OM/OD and 1 verify no frame loss for revert. FRR x10G Muxponder CBR Transport FRR Break TX and RX between 7750 and OT-4 and verify failure < 50 msec. 1 FRR Restore TX and RX between 7750 and OT-4 and verify no frame loss for 1 revert. FRR Break TX and RX between OT-4 and OM/OD and verify failover < 50 1 msec. FRR Restore TX and RX between OT-4 and OM/OD and verify no frame loss for 1 revert. FRR Break TX and RX between OM/ODs and verify failover < 50 msec. 1 FRR Restore TX and RX between OM/ODs and verify no frame loss for revert. 1 FRR x10G Muxponder CBR Transport with 80.3ah FRR Break TX and RX between 7750 and OT-4 and verify failure < 50 msec. 1 FRR Restore TX and RX between 7750 and OT-4 and verify no frame loss for 1 revert. FRR Break TX and RX between OT-4 and OM/OD and verify failover < 50 1 msec. FRR Restore TX and RX between OT-4 and OM/OD and verify no frame loss for 1 revert. FRR Break TX and RX between OM/ODs and verify failover < 50 msec. 1 FRR Restore TX and RX between OM/ODs and verify no frame loss for revert. 1 FRR x10G Muxponder CBR Transport with BFD FRR Break TX and RX between 7750 and OT-4 and verify failure < 50 msec. 1 FRR Restore TX and RX between 7750 and OT-4 and verify no frame loss for 1 revert. FRR Break TX and RX between OT-4 and OM/OD and verify failover < 50 1 msec. FRR Restore TX and RX between OT-4 and OM/OD and verify no frame loss for 1 revert. FRR Break TX and RX between OM/ODs and verify failover < 50 msec. 1 FRR Restore TX and RX between OM/ODs and verify no frame loss for revert. 1 Network Element Restoration NER-001 BASE-LR4 (4λx5G) NER Reboot 7750SR and verify service recovers 1 NER Power off/on 7750SR and verify service recovers 1 NER Power off/on 1830 and verify service recovers 1 NER-00 BASE-LR10 (10λx10G) 1 3MM-0100-ADAB-GAZZZA Issue 1 November

19 NER Reboot 7750SR and verify service recovers 1 NER Power off/on 7750SR and verify service recovers 1 NER Power off/on 1830 and verify service recovers 1 NER x10G Muxponder CBR Transport NER Reboot 7750SR and verify service recovers 1 NER Power off/on 7750SR and verify service recovers 1 NER Power off/on 1830 and verify service recovers 1 Synchronous Ethernet SyncE-001 BASE-LR4 (4λx5G) 3 SyncE Verify BITS clock is distributed. Measure jitter and wander. 1 3 SyncE Verify no frame loss for clock transition from Master Locked to Master 1 Holdover. 3 SyncE Verify no frame loss for clock transition from Master Holdover to Master 1 Locked. SyncE-00 BASE-LR10 (10λx10G) SyncE Verify BITS clock is distributed. Measure jitter and wander. 1 1 SyncE Verify no frame loss for clock transition from Master Locked to Master 1 Holdover. 1 SyncE Verify no frame loss for clock transition from Master Holdover to Master 1 Locked. SyncE-003 BASE-LR4 (4lx5G) and BASE-LR10 (10λx10G) 1 SyncE Verify BITS clock is distributed. Measure jitter and wander. 1 1 SyncE Verify no frame loss for clock transition from Master Locked to Master Holdover. 1 SyncE Verify no frame loss for clock transition from Master Holdover to Master Locked. SyncE x10G Muxponder CBR Transport 1 SyncE Verify BITS clock is distributed over 10x10G muxponder with GFP transport. Measure jitter and wander. 1 SyncE Verify no frame loss for clock transition from Master Locked to Master Holdover. 1 SyncE Verify no frame loss for clock transition from Master Holdover to Master Locked. Table Test Cases MM-0100-ADAB-GAZZZA 13 Issue 1 November 010

20 Key provisioning for 7750SR and 1830 systems The following embedded files contain the basic configurations for the 7750 SR-1s. Parameters were changed during testing, as required. 7750cfg-top.txt 7750cfg-bot.txt The -3s were configured as a 1-Degree FOADM, point-to-point, using filter channels 940 and 950. Each NE was equipped with mandatory packs (EC, Power Filters), one amplifier, one SFD5 filter, one Add/Drop card and one Mux card. Clients for the cards used LR10 CFPs on Add/Drop cards and 10G B&W XFPs on the Mux cards. The following embedded file contains screen captures of the configuration and setup for the -3 optical network. The configuration for each shelf was the same. 1830cfg.doc 14 3MM-0100-ADAB-GAZZZA Issue 1 November 010

21 Interoperability Test Cases The test cases will be included in the results document and are designed to be a guide in performing the required interoperability testing. Each test case may require multiple specific tests to be performed and the number of actual tests performed will vary based on testing results. Testing results will dictate the addition of test cases and/or tests as needed. The following indications will be used for the test result state: Test Result Definitions - The outcome of an executed test to represent the level to which the test met its exit criteria. o P (Passed) - All of the exit criteria of the test have been met under the scheduled release. o B (Blocked) - Test case blocked. o P/E (Passed with Exceptions) - All of the exit criteria have been met, but an issue was identified. o F (Fail) - One or more of the exit criteria for a test has not been met. The test cases will reuse the procedures identified for the CBT R1.0 port level grooming, as applicable. Refer to the Converged Backbone Transformation Port Level Grooming ( ) Test Plan 5, Version 1.1 and the Converged Backbone Transformation Port Level Grooming ( ) Test Results, Version The following sections describe the high level test cases. 3MM-0100-ADAB-GAZZZA 15 Issue 1 November 010

22 CFP Interoperability Test Case Area: CFP-001 CFP-00 CFP-003 Equipment: () 7750SR-1 () (1) Spirent STC Objective: To verify interoperability between ige ports. Notes: The connection between the 7750 and 1830 will be via 100 GigE CFPs. Data will be forwarded via epipe connections. The 10 Gbps epipe connections on the 7750 SR-1s will be daisy-chained to provide a 100 Gbps connection to the. There is no resiliency configured. Configuration: Test Set be be AD AD 7750 SR 7750 SR 7750 SR Procedure: 1. Verify that the links between the 7750SR and 1830PSS is up.. Generate bi-directional data at 10 Gbps using the STC for a period of 1 minute. 16 3MM-0100-ADAB-GAZZZA Issue 1 November 010

23 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. 6. Generate continuous bi-directional data at 10 Gbps using the STC. 7. Introduce a failure on the connection between the 7750s. 8. Verify that the 7750s at each end of the connection recognize the failure. 9. Verify that data transport has stopped. 10. Repair the failure. 11. Verify that the 7750s at each end of the connection recognize the link is up. 1. Verify that data transport resumes. 13. Repeat for multiple failure conditions. Expected Results: The 100 GigE ports are active and transfer data. Failures are recognized and reported. Alarms are cleared when the failure is repaired and data transfer resumes. 3MM-0100-ADAB-GAZZZA 17 Issue 1 November 010

24 XFP/SFP+ Muxponder Interoperability Test Case Area: XFP-001 XFP-00 SFP+-001 Equipment: () 7750SR-1 () (1) Spirent STC Objective: To verify interoperability between 10GigE ports over Muxponder. Notes: The connection between the 7750 and 1830 will be via 10 GigE SFP+ on 7750 and XFP-LR on Data will be forwarded via an epipe connection. There is no resiliency configured. The muxponder ports will be daisy-chained to provide 100 Gbps traffic. Configuration: Test Set Test Set Mux Mux 7750 SR 7750 SR 7750 SR Procedure: 1. Verify that the links between the 7750SR and 1830PSS is up.. Generate bi-directional data at 10 Gbps using the STC for a period of 1 minute. 3. Verify that the data is flowing over the path. 4. Verify that no data is lost. 18 3MM-0100-ADAB-GAZZZA Issue 1 November 010

25 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. 6. Generate continuous bi-directional data at 10 Gbps using the STC. 7. Introduce a failure on the connection between the 7750s. 8. Verify that the 7750s at each end of the connection recognize the failure. 9. Verify that data transport has stopped. 10. Repair the failure. 11. Verify that the 7750s at each end of the connection recognize the link is up. 1. Verify that data transport resumes. 13. Repeat for multiple failure conditions. Expected Results: The 10 GigE ports are active and transfer data. Failures are recognized and reported. Alarms are cleared when the failure is repaired and data transfer resumes. 3MM-0100-ADAB-GAZZZA 19 Issue 1 November 010

26 Performance (Transponder) Test Case Area: Perf-001 Perf-00 Perf-003 Equipment: () 7750SR-1 () (1) Spirent STC Objective: To verify performance of ige ports. Notes: The connection between the 7750 and 1830 will be via 100 GigE CFPs. Data will be forwarded via epipe connections. The 10 Gbps epipe connections on the 7750 SR-1s will be daisy-chained to provide a 100 Gbps connection to the. There is no resiliency configured. Configuration: Test Set be be AD AD 7750 SR 7750 SR 7750 SR Procedure: 1. Verify that the links between the 7750SR and 1830PSS is up.. Generate bi-directional data at 10 Gbps using the STC for a period of 1 minute. 3. Verify that 100 Gbps data rate via statistics. 0 3MM-0100-ADAB-GAZZZA Issue 1 November 010

27 4. Verify that no data is lost. 5. Measure latency and jitter. 6. Perform RFC 544 tests, if test set available, Expected Results: The 100 GigE ports are active and transfer data. No data is lost. 3MM-0100-ADAB-GAZZZA 1 Issue 1 November 010

28 Performance (Muxponder) Test Case Area: Perf-004 Equipment: () 7750SR-1 () (1) Spirent STC Objective: To verify performance of ige ports. Notes: The connection between the 7750 and 1830 will be via 10 GigE XFPs and/or SFP+s. Data will be forwarded via an epipe connection. There is no resiliency configured. The muxponder ports will be daisy-chained to provide 100 Gbps traffic. Configuration: Test Set Test Set Mux Mux 7750 SR 7750 SR 7750 SR Procedure: 1. Verify that the links between the 7750SR and 1830PSS is up.. Generate bi-directional data at 10 Gbps using the STC for a period of 1 minute. 3. Verify that 100 Gbps data rate via statistics. 4. Verify that no data is lost. 5. Measure latency and jitter. 3MM-0100-ADAB-GAZZZA Issue 1 November 010

29 6. Perform RFC 544 tests, if test set available, Expected Results: The 100 GigE ports are active and transfer data. No data is lost. 3MM-0100-ADAB-GAZZZA 3 Issue 1 November 010

30 Fast Reroute Network Resiliency (Transponder) Test Case Area: FRR-001 FRR-00 FRR-003 Equipment: () 7750SR-1 (1) 7750SR-7 () (1) Spirent STC Objective: To verify failover and restoration times. Notes: The connection between the 7750 and 1830 will be via 100 GigE CFPs. Data will be forwarded via epipe connections. The 10 Gbps epipe connections on the 7750 SR-1s will be daisy-chained to provide a 100 Gbps connection to the. Fast reroute resiliency is configured with primary/standby. Configuration: Test Set be be AD AD 7750 SR 7750 SR 7750 SR Procedure: 1. Generate bi-directional data at 1000 pps using the STC.. Verify that the data is flowing over the path. 3. Verify that detours have been established. 4 3MM-0100-ADAB-GAZZZA Issue 1 November 010

31 4. Verify that the standby path is active. 5. Introduce a failure in the primary path between the 7750s. 6. Verify that the data is flowing in both directions. The LSP will use the detours and then switch to the standby connection. 7. Stop the traffic and record the lost packets in each direction. 8. Restart the generators. 9. Repair the failures. 10. Verify that the data reverts to the primary path. 11. Stop the traffic and record the lost packets in each direction. 1. Repeat for multiple failure conditions. 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). 3MM-0100-ADAB-GAZZZA 5 Issue 1 November 010

32 Fast Reroute Network Resiliency (Muxponder) Test Case Area: FRR-004 FRR-005 FRR-006 Equipment: () 7750SR-1 () (1) Spirent STC Objective: To verify failover and restoration times. Notes: The connection between the 7750 and 1830 will be via 10 GigE XFPs and/or SFP+s. Data will be forwarded via an epipe connection. Fast reroute resiliency is configured with primary/standby. The muxponder ports will be daisy-chained to provide 100 Gbps traffic. Configuration: Test Set Test Set Mux Mux 7750 SR 7750 SR 7750 SR Procedure: 1. Generate bi-directional data at 1000 pps using the STC.. Verify that the data is flowing over the path. 3. Verify that detours have been established. 4. Verify that the standby path is active. 5. Introduce a failure in the primary path between the 7750s. 6 3MM-0100-ADAB-GAZZZA Issue 1 November 010

33 6. Verify that the data is flowing in both directions. The LSP will use the detours and then switch to the standby connection. 7. Stop the traffic and record the lost packets in each direction. 8. Restart the generators. 9. Repair the failures. 10. Verify that the data reverts to the primary path. 11. Stop the traffic and record the lost packets in each direction. 1. Repeat for multiple failure conditions. 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). 3MM-0100-ADAB-GAZZZA 7 Issue 1 November 010

34 Network Element Restoration (Transponder) Test Case Area: NER-001 NER-00 Equipment: () 7750SR-1 (1) 7750SR-7 () (1) Spirent STC Objective: To verify network element recovery. Notes: The connection between the 7750 and 1830 will be via 100 GigE CFPs. Data will be forwarded via epipe connections. The 10 Gbps epipe connections on the 7750 SR-1s will be daisy-chained to provide a 100 Gbps connection to the. Fast reroute resiliency is configured with primary/standby. Configuration: Test Set be be AD AD 7750 SR 7750 SR 7750 SR Procedure: 1. Generate continuous bi-directional data at 10 Gbps using the STC.. Reset a network element. 3. Verify that data transport has stopped. 4. Verify that the network elements recover. 8 3MM-0100-ADAB-GAZZZA Issue 1 November 010

35 5. Verify that the connections are up. 6. Verify that data transport resumes. 7. Repeat for multiple network element resets. Expected Results: The network element that is reset will recover, all connections will be reestablished, and data transport will resume without intervention. 3MM-0100-ADAB-GAZZZA 9 Issue 1 November 010

36 Network Element Restoration (Muxponder) Test Case Area: NER-003 Equipment: () 7750SR-1 (1) 7750SR-7 () (1) Spirent STC Objective: To verify network element recovery. Notes: The connection between the 7750 and 1830 will be via 10 GigE XFPs. Data will be forwarded via an epipe connection. Fast reroute resiliency is configured with primary/standby. The muxponder ports will be daisy-chained to provide 100 Gbps traffic. Configuration: Test Set Test Set Mux Mux 7750 SR 7750 SR 7750 SR Procedure: 1. Generate continuous bi-directional data at 10 Gbps using the STC.. Reset a network element. 3. Verify that data transport has stopped. 4. Verify that the network elements recover. 5. Verify that the connections are up. 6. Verify that data transport resumes. 30 3MM-0100-ADAB-GAZZZA Issue 1 November 010

37 7. Repeat for multiple network element resets. Expected Results: The network element that is reset will recover, all connections will be reestablished, and data transport will resume without intervention. 3MM-0100-ADAB-GAZZZA 31 Issue 1 November 010

38 Synchronous Ethernet (Transponder) Test Case Area: SyncE-001 SyncE-00 SyncE-003 Equipment: () 7750SR-1 (1) 7750SR-7 () (1) Spirent STC () BITS clock ports (1) ANT-0 (for MTIE analysis) or equivalent Objective: To verify the functionality of synchronous ethernet. Notes: The connection between the 7750 and 1830 will be via 100 GigE CFPs. Data will be forwarded via epipe connections. The 10 Gbps epipe connections on the 7750 SR-1s will be daisy-chained to provide a 100 Gbps connection to the. Fast reroute resiliency is configured with primary/standby. Configuration: Test Set be be AD AD 7750 SR 7750 SR 7750 SR Procedure: 1. Connect a BITS clock to a 7750 SR MM-0100-ADAB-GAZZZA Issue 1 November 010

39 . Configure appropriate card for sync-e. 3. Enable bits sync-if-timing. 4. Verify that the Reference BITS is up, qualified for use, and the timing is Master Locked. 5. Configure appropriate cards on other 7750s for sync-e. 6. Configure ref1 sync-if-timing. 7. Verify that Reference Input 1 is up, qualified for use, and the timing is Master Locked. 8. Connect ANT-0 or equivalent to BITS clock ports on remote Record the clock frequency and jitter measurements. 10. Verify sync-e stability over 4-hour period. 11. Disconnect timing port and verify switching from Master Locked to Master Holdover does not affect data. 1. Reconnect timing port and verify switching from Master Holdover to Master Locked does not affect data. Expected Results: The 7750 SR-1 will synchronize to the BITS clock and distribute timing via sync-e to the other routers. The jitter and wander measurements meet requirements. Switching from Master Locked to Master Holdover and back during port failures does not affect data. 3MM-0100-ADAB-GAZZZA 33 Issue 1 November 010

40 Synchronous Ethernet (Muxponder) Test Case Area: SyncE-004 Equipment: () 7750SR-1 (1) 7750SR-7 () (1) Spirent STC () BITS clock ports (1) ANT-0 (for MTIE analysis) or equivalent Objective: To verify the functionality of synchronous ethernet. Notes: The connection between the 7750 and 1830 will be via 10 GigE XFPs. Data will be forwarded via an epipe connection. Fast reroute resiliency is configured with primary/standby. The muxponder ports will be daisy-chained to provide 100 Gbps traffic. Configuration: Test Set Test Set Mux Mux 7750 SR 7750 SR 7750 SR Procedure: 1. Connect a BITS clock to a 7750 SR-1.. Configure appropriate card for sync-e. 3. Enable bits sync-if-timing. 34 3MM-0100-ADAB-GAZZZA Issue 1 November 010

41 4. Verify that the Reference BITS is up, qualified for use, and the timing is Master Locked. 5. Configure appropriate cards on other 7750s for sync-e. 6. Configure ref1 sync-if-timing. 7. Verify that Reference Input 1 is up, qualified for use, and the timing is Master Locked. 8. Connect ANT-0 or equivalent to BITS clock ports on remote Record the clock frequency and jitter measurements. 10. Verify sync-e stability over 4-hour period. 11. Disconnect timing port and verify switching from Master Locked to Master Holdover does not affect data. 1. Reconnect timing port and verify switching from Master Holdover to Master Locked does not affect data. Expected Results: The 7750 SR-1 will synchronize to the BITS clock and distribute timing via sync-e to the other routers. The jitter and wander measurements meet requirements. Switching from Master Locked to Master Holdover and back during port failures does not affect data. 3MM-0100-ADAB-GAZZZA 35 Issue 1 November 010

42 Glossary A AIS Alarm Indication Signal I IGP Interior Gateway Protocol B BFD BIDIRECTIONNAL FORWARDING DETECTION ISIS Intermediate System-Intermediate System C CBR Constant Bit Rate L LAG Link Aggregation Group CBT Converged Backbone Solution LDP Link Discovery Protocol E EFM Ethernet in the First Mile LOS Loss Of Signal LSP Label Switch Path F G FRR Fast Reroute GFP Generic Framing Procedure GMPLS Generic- MPLS M O MPLS Multiple Path Label Switching OAM Operations, Administration, and Maintenance OCH Optical Channel O-SNCP Optical Sncp OSPF Open Short Path First 3MM-0100-ADAB-GAZZZA 36 Issue 1 November 010

43 Glossary R RSVP-TE Resource Reservation Protocol- Traffic Engineering S SDP Service Distribution Point SLA Service Level Agreement SR Service Router V VLL Virtual Leases Link VPLS Virtual Private LAN Service VPRN Virtual Private Routed Network 3MM-0100-ADAB-GAZZZA 37 Issue 1 November 010