Bugs in your network? We'll help you catch them.

We know that the smallest bugs are often the hardest to catch. And that they will not appear often, which makes them hard to catch. But if they escape until the network goes live, they will emerge at the most inconvenient time. With Rude, our network impairment emulator, you can do locate them quickly, easily and with repeatability.


Some examples:

1. Simple way of setting up a complex scenario

The most annoying problems are the ones that require very specific circumstances to surface. The problem with specific circumstances is that they can be difficult to reproduce, which makes them hard to test for. However, by using Data content modification it is possible to modify the traffic and create complex settings easily.

For example, you may encounter a problem only when certain rare IP packet priorities coincide. The quick way to test if this is the root cause is to simply modify the priority value in the data, without actually setting the priorities. This way, you can test rare scenarios quickly avoiding any bad surprises later.


2. Precise packet drop

Packet drop is the most common and most tested impairment and is often quite straightforward. However, at times there are problems occurring randomly, even though the drop ratio remains the same. The root cause may well be the fact that all packets are not equal. Dropping some of the less critical packets causes no issues, but dropping one of the critical ones causes serious issues.

By using Predefined pattern repeater it is possible to create a drop pattern and decide exactly the packets to be dropped. And the same pattern can be repeated constantly, in the same testing session or in later test rounds. This will lead you precisely to the problem root cause.


3. Finding thresholds for system robustness

A service runs well as long as it is getting the input as expected, in the right sequence with valid contents. However, packets do get corrupted along the way. In order to know how robust the service is, it is best to test. Again, by using Data content modification it is possible to modify the traffic to create invalid packets and see what it does to the service. What is the threshold of valid vs. invalid packets that the service can take?


These are just a few examples of how Rude lets you dig deeper into the details of IP traffic. Talk to us at MWC17 to find out more ways our tools can help your testing work.


+ Leave a comment
Your name:



Let's work out the right solution for you.
Request a trial use or more information.
If you'd like us to call you, leave us your phone number.


Subscribe to our mailing list

* indicates required