In this example, you will learn how to run a test on Safire to measure the performance of your firewall.
When opening a test case, Safire will first verify that the test ports are connected by checking whether the ports are able to detect sync signals. If the ports are not connected to the firewall or themselves (back-to-back connection), Safire will ask you to connect the ports and wait to proceed until it can detect the port sync signal. If the ports are already connected, Safire will directly enter the page below.
Test case opened and ready to run the test
Select Traffic Profile for Performance Test
Choose a traffic profile from the drop-down list. You can read more information about the traffic profile by hovering your mouse over the question mark icon.
Select a traffic profile for performance test
Click the Run Test button to start the test.
Click button Run Test to start testing
A dialog window will pop up asking for the SSH login credential to the firewall under test. It is recommended you enter the information. Safire will use the credential to clear firewall session table during the test and monitor firewall’s CPU usage and memory usage. Before each test iteration, Safire will use the information to SSH log into the firewall and clear the session table and immediately continue.
Enter firewall SSH login credential
Set Waiting Time
If you don’t have the firewall’s SSH login credential, you can click SET WAITING TIME and enter the waiting time (by default it is set to 15 seconds) between test iterations. Safire will wait the configured time before continuing to the next test iteration.
Enter waiting time between iterations if firewall SSH access is unavailable
Each test iteration consists of a ramp-up phase, a sustain phase, and a ramp-down phase. You can click TEST DURATION to customize the sustain phase duration of test iterations. The ramp-up and ramp-down durations are automatically adjusted based on the number of sessions of the test iteration.
The default and the minimum allowed sustain phase duration is 30 seconds. Use the three sliders to modify the sustain phase duration.
You can find the estimated overall test duration at the bottom. It is calculated on the fly based on the test sustain phase duration, the number of iterations, and the waiting time between iterations.
Safire runs a simple connectivity test prior to the performance test to validate the test case configuration by checking if a TCP connection can be established between the two test ports. Once the connectivity test is successful, the Run Test button will turn green, and Safire will continue to run the performance test. The green Run Test button indicates that the connectivity is already validated and if you run the test again, Safire will skip the connectivity test. But if you disconnect the ports or exit the test case, the Run Test button will resume back to original state.
By default, Safire runs ten performance test iterations. It starts with 10% of the total users defined by the selected traffic profile, and increases this by 10% for each the following iterations.
Alternatively, you can configure the test to run a different number of iterations from one upwards. This will affect the duration of the test, plus the more times you run the test, the more detailed the results.
Blue button executes connectivity test + performance test. Green button skips connectivity test and only runs the performance test.
Customize Test Iterations
To customize test iterations, click CUSTOMIZE ITERATIONS, and then click button + to create your own test iterations.
The number of users (client IPs) you can define is the sum of all applications of the traffic profile. The number of users of each application changes in proportion to their own percentage in the traffic profile. To check number of users per application, you can click the info icon next to the value.
Customize test iterations