Tellabs Internal and Confidential Implementing Soak Testing for an Access Network Solution Presented by: Timo Karttunen Supervisor: Raimo Kantola Instructor: Sami Larkimo

2 May 2, 2015 Contents  Objectives  Requirements for the System  Tellabs 8600 Managed Edge System  Tellabs 8000 Network Manager (NMS)  The Soak Testing Environment  Operating the Network  Monitoring Workstation  Detecting Failures  Overall Architecture  Conclusion and Further Research

3 May 2, 2015 Objectives  The objective of this thesis was to design and implement an automated testing environment for soak testing of Tellabs 8600 series routers.  Soak testing, also known as endurance testing, is a type of testing where the system will be run over a prolonged period of time in order to check the system’s stability under sustained use.  The purpose of this soak testing environment is to find problems that do not show up immediately in functional and regression testing but could manifest themselves in the service providers operating network.

4 May 2, 2015 Requirements for the System  Automatic operation of the network – We need some methods to be able to automatically create various operations to the network.  Automatic failure detection – We need to be able to automatically verify whether everything is working correctly or not.  Logging - We want to keep some kind of log file about the operations done in the network so that we are able to check afterwards that what has been done.

5 May 2, 2015 Tellabs 8600 Managed Edge System  Designed for access and regional networks  5 different IP/MPLS based routers  Optimized for mobile transport in 2G and 3G RAN  Supports technologies needed in 2G to 3G evolution  Ethernet, TDM, SDH, ATM, FR and IP/MPLS  Applicable also in fixed networks  L2 and L3 MPLS VPN services  NMS and CLI configuration

6 May 2, 2015 Tellabs 8000 Network Manager (NMS)  Powerful and scalable network and services management system  Enables element, network and service level configuration  Can manage several Tellabs router families (8600, 8100, 8800, …)  Tools for network building, service provisioning, performance and fault monitoring, testing...

7 May 2, 2015 The Soak Testing Environment  ~400 L2 PWs  L3 IP VPN  OSPF emulations  LDP emulations  RSVP emulations  BFD emulations

8 May 2, 2015 Operating the Network  Macro Manager - Command Line Interface  Independent of the GUI of NMS  Macro programs coded with NMS macro language  Java program used to run macro programs  Hierarchical architecture for macros  Easy to create new macros

9 May 2, 2015 Operating the Network  CLI configuration through telnet session  No macro support for every operation  Information directly from the network element  Java package handles the communication  Reply of the network element is saved into a file for further processing

10 May 2, 2015 Monitoring Workstation  One PC configured to be monitoring workstation  Configuration snapshots  Fault Management  Packet loop test  Performance data polling > Real-time > History

11 May 2, 2015 Failure Detection  Automatic failure detection is implemented by checking data streams  Data flows through most services  Measurement equipment has a Tcl API  Packet loss of certain streams is checked  Java program runs the Tcl script  Allows the detection of wide variety of defects  However, does not cover everything

12 May 2, 2015 Overall Architecture  Files describe the operations  Schedulers generate files  Agent picks and interpretes these  Sequential execution  Everything logged

13 May 2, 2015 Results  Currently everything is just written to a text file After every operation On regular intervals  Results will be gathered to a database  Same database with benchmark testing  MySQL and HTTP Simple

14 May 2, 2015 Conclusions  The system has been taken into use in the system testing of 8600 system  Satisfies the initial requirements  Has been effective  Easy to add more functionality  Debugging and fix verification is difficult  Another identical system has been implemented

15 May 2, 2015 Further Research  Expanding the coverage More network elements and load on the routers Several executing objects  Enhancement of the reporting More exact information to the designers More exact information to the managers  More automatic failure detection Detecting failures in NMS functionality Detecting failures in the network elements

16 May 2, 2015 Thank You Questions?