Want to learn more about testing IP services? You don’t have to buy anything … yet.

 

Just start with a quick, easy-to-read summary of quality testing IP services, available on the Mu Dynamics test page. From its very inception, Mu’s Test Suite – used for testing IP services -- supported integration with a wide variety of test lab environments including load generation, functional testing, open and proprietary standards, a track record not all products have.

 

The Mu product controls other testing devices over serial console, Telnet or SSH channels and uses regular expressions to detect user-defined “events of interest” that are used to trigger fault isolation. And it’s controlled via a web-browser-based GUI with enough ease of use.

 

One of the best things about it, though, is that the Mu Test Suite is easy to integrate into larger lab automation frameworks where they exist. The suite “exposes its functionality via a Web Services Description Language document so it can integrate into Software Testing Automation Framework and other similar WSDL-based laboratory automation environments,” according to company officials.

 

The site itself, though, offers recommended practices for different device testing, lots of useful, helpful stuff here. For example, Mu Dynamics (News - Alert) has worked with Veraz Networks to define a set of comprehensive tests to which SBCs should be subjected. The Mu Test Suite can be deployed in a variety of ways to test a Session Border Controller for robustness and the ability to tolerate denial-of-service conditions and other real-world traffic scenarios.

 

The company offers a methodology paper to show how to test SBCs using Service-Level Traffic Variations, specifically targeting the many exposed protocols within SBCs, as well as denial-of-service simulation against these protocols.

There’s also a paper documenting the many ways that a router can be evaluated by the Mu Test Suite, including Service-Level Traffic Variation attacks in pass-through mode for services in which the router actively or passively participates.

 

Also possible, company officials said, are SLTV attacks in endpoint mode vs. the services running within the router (e.g., routing protocols, management protocols, or other critical applications like DHCP, etc.); “and finally Denial-of-Service attacks against any active services within the router.”