This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Rethink Server Load TestingGuidelines to measure the performance, security, and stability of application and web servers under real-world network conditions
Table of ContentsIntroduction .................................................................................................................................................................................................................... 3
Load Generator: HTTP Status Codes ...................................................................................................................................................................... 5
Load Generator: Sending and Retrieving Email using SMTP and IMAP .................................................................................................... 69
Load Generator: Sending and Retrieving Email using SMTP and POP3 .................................................................................................... 93
Load Generator: Using MS SQL to add and query a database ...................................................................................................................... 111
Load Generator: Using MySQL to add and query a database ....................................................................................................................... 128
About BreakingPoint ................................................................................................................................................................................................... 144
IntroductionWhat is the capacity of your data center? Will it withstand peak user load? What about attack? Will a simple distributed denial-of-service
attack disrupt critical business transactions? And what about those new high-performance enterprise servers you are evaluating? Will they
really live up to the promises promoted in the vendor’s data sheet?
If you cannot properly measure your servers’ performance, security and stability, you won’t have any defensible answers to these questions.
Your business performance and reputation are at risk, and it’s time to take a new approach to hardening your data center and establishing
server load resiliency.
Measuring server resiliency is about knowing how they will weather hostile conditions, including attack and extreme load, and optimizing
your overall performance to drive business results. Understanding the resiliency of your data center or cloud infrastructure, in the face of
high-stress traffic and cyberattack, requires the ability to simulate user behavior and load at incredibly high performance and throughput
levels. Software-based server load testing, developed more than a decade ago, no longer meets today’s mega-data-center requirements.
The BreakingPoint Server Load Resiliency Methodology provides a guideline for measuring server and data center resiliency in the face of
real-world application traffic, live security attacks and the stress from millions of users. With the ability to simulate these real-world hostile
conditions using the BreakingPoint Cyber Tomography Machine, you can pinpoint hidden stress fractures and calculate a defensible
resiliency score for the certainty you need to mitigate IT risks and drastically reduce costs.
With the breakthrough power of cyber tomography, BreakingPoint provides realistic network simulation of millions of simultaneous user
sessions with blended, realistic application traffic from a small footprint product, eliminating costly racks of servers and software licenses.
BreakingPoint products can help you stress and score your critical network infrastructure with real-world network conditions to:
• Reduce risks associated with data center consolidation or migration
• Improve availability and performance to reduce outages and prevent lost customers, revenue and productivity
• Measure and optimize capacity to deliver the right balance of performance, security and stability in the face of escalating traffic
volume
• Assess resiliency against attack and data loss to mitigate security breaches
• Make better IT investment decisions and eliminate the need for sprawling performance and security test labs
The BreakingPoint Server Load Resiliency Methodology includes the following simulations:
Load Generator: HTTP Status Codes
Determine the ability of the Web server to correctly respond to Web page requests. This will help validate the performance of the Web server and verify whether it is able to correctly handle the number of requests. A Client Simulator component will be used, along with Perl Regular Expressions, to determine the returned HTTP status codes from the Web server.
Load Generator: HTTP Client LoginDetermine the ability of the Web server to correctly handle restricted Web space and still be able to respond to Web page requests cor-rectly. This will help validate the performance of the Web server while it is also performing other tasks, and verify whether it is able to still handle a high volume of requests. A ClientSim component will be used, along with Perl Regular Expressions, to determine the returned HTTP status codes.
Load Generator: HTTP Verify PageThis verifies whether the Web server is correctly responding and whether the Web page is correctly being transmitted. A Web page that resides on the Web server will be uploaded to the BreakingPoint Storm CTM. The Client Simulator component will request this page and it will be verified as being either correct or incorrect.
Load Generator: SMB Login, Create, Read and Delete FilesThis determines the ability of an SMB share. The SMB share will be stressed by having multiple files created, read and deleted. If any of these actions fail, the SMB share is either not configured correctly or unable to support the required load. A Client Simulator component will be used and the SMB results will be verified.
Load Generator: Sending and Retrieving Email using SMTP and IMAPThis is a two-step process involving both SMTP and IMAP. This simulation will determine the ability of the SMTP server to successfully trans-mit emails. After emails have been sent to a valid email address, IMAP will be used to retrieve those newly received emails. To verify that the simulation was successful, the email server will be checked to make sure that the emails have been received and opened.
Load Generator: Sending and Retrieving Email using SMTP and POP3This is a two-step process involving both SMTP and POP3. This simulation will determine the ability of the SMTP server to successfully trans-mit emails. After emails have been sent to a valid email address, POP3 will be used to retrieve those newly received emails. To verify that the simulation was successful, the email server will be checked to make sure that the emails have been received and opened.
Load Generator: Using MS SQL to add and query a databaseThis will determine the ability and configuration of an MS SQL database. The simulation involves first adding new content to an empty data-base. Once new content has successfully been added, it will be queried. The database will be viewed to make sure that the data added to it is actually present in the database.
Load Generator: Using MySQL to add and query a databaseThis will determine the ability and configuration of a MySQL database. The simulation involves first adding new content to an empty data-base. Once new content has successfully been added, it will be queried. The database will be viewed to make sure that the data added to it is actually present in the database.
The following methodology was performed using BreakingPoint OS version 1.4.1 and ATI Pack 59235. For more information on BreakingPoint products, solutions and services visit www.breakingpoint.com.
7. Notice multiple Interface tabs are available for configuration. Only one is required for the tests. The first interface tab should be selected. Click the X to delete this interface. When prompted about removing the interface, click Yes. The remaining interfaces will be renamed. Repeat this process until only one interface remains.
8. With Interface 1 selected, click the Show subnet details button.
9. Configure the Network IP Address, Network Mask, Gateway IP Address (if required); use the Type drop-down menu to select Host, and then configure the Minimum IP Address, and the Maximum IP Address. Click Accept.
10. Select the External tab and then click the Delete range button.
17. Enter HTTP Status as the name of the new Super Flow and click Ok.
18. In the Define Flows section, use the Protocol drop-down menu and select HTTP. Click Add Flow once completed.
19. Make sure that the new flow has been selected in the Define Flows field. In the Define Actions field using the Action drop-down menu, select Client: GET.
23. Next, select the second action in the Define Actions section. Click the Edit the selected actions parameters button.
24. The Conditional Request window allows for regular expressions (regex). The syntax of the regex follows the Perl standard. This test is going to verify status codes sent by the server. The first Match field should contain a regex that will match a 200-page response, while the second Match should match any 300-page responses, and the third Match should match any 500-page responses. Make sure the Regex radio button is selected for each Match field. Click Apply Changes once completed.
28. In the Choose a device under test and network neighborhood window under the Device Under Test(s) section, verify that BreakingPoint Default is selected. Under Network Neighborhood(s), verify that the newly created one is selected. Click Accept.
29. When prompted about switching Network Neighborhoods because the current setup contains more interfaces, click Yes.
33. Select the Interfaces tab. Verify that only External Server and Interface 1 Client are enabled and click Apply Changes.
34. Select the Parameters tab. Several parameters will be changed in this section. The first parameter that needs to be updated is the Minimum data rate. Enter a value of 1000 (if your server supports gigabit Ethernet) and click Apply Changes.
35. The next parameter to be changed is the Steady-State Seconds. Update this to a run time of 5 minutes and click Apply Changes.
36. Next, both Maximum Simultaneous Sessions and Maximum Sessions Per Second will be updated. Enter values that your server is expected to be able to handle and click Apply Changes.
37. The last parameter that needs to be changed is selecting the Super Flow that was created earlier. Using the Super Flow drop-down menu select HTTP Status and click Apply Changes.
39. When prompted for a name to save the test as, enter Load Generator HTTP Status and click Save.
The Summary tab initially will be displayed. A great amount of information is seen on this screen, from the TCP Connection Rate to the Cumulative TCP Connections to the Bandwidth being used.
40. Select the Client tab. This displays information about the client’s connections and if they are successful or not. Verify that connections are successfully being made.
41. Once the test completes, a window will appear stating the test passed. Click Close to continue.
43. Expand the Test Results for HTTP Status Codes folder, and then expand the Details folder. Select Response Summary. Determine what code pages were sent. Every page should have responded with an HTTP/1.1 200.
7. In the Define Flows section, use the Protocol drop-down menu and select HTTP. Click Add Flow once completed.
8. Make sure the new flow has been selected in the Define Flows field. In the Define Actions field using the Action drop-down menu, select Client: GET (authenticated). Click the Add Action button once completed.
9. Again, using the Action drop-down menu, select Client: Conditional Request. Click the Add Action button once completed.
10. Select the first action in the Define Actions section. Click the Edit the selected actions parameters button.
11. Using the HTTP Auth Scheme drop-down menu, choose the correct type of authentication. Next, enable both Username and Password making sure to enter a valid username and password in those fields. Finally, enable Request path (e.g., /dir/page.htm) and enter a known Web page on your server and click Apply Changes once completed.
12. Next, select the second action in the Define Actions section. Click the Edit the selected actions parameters button.
13. The Conditional Request window allows for regular expressions. The syntax of the regular expressions follows the Perl standard. This test will verify status codes sent by the server. The first Match field should contain a regex that will match a 200-page response, while the second Match should match any 300-page responses, and the third Match should match any 500-page responses. Make sure the Regex radio button is selected for each Match field. Click Apply Changes once completed.
16. Under the Test Quick Steps, click Select the DUT/Network.
17. In the Choose a device under test and network neighborhood window under the Device Under Test(s) section, verify that BreakingPoint Default is selected. Under Network Neighborhood(s), verify that the newly created one is selected. Click Accept.
21. Under the Information tab, enter HTTP Login as the Name and click Apply Changes.
22. Select the Interfaces tab. Verify that only External Server and Interface 1 Client are enabled.
23. Select the Parameters tab. Several parameters will be changed in this section. The first parameter that needs to be updated is the Minimum data rate. Enter a value of 1000 (if your server supports gigabit Ethernet) and click Apply Changes.
24. The next parameter to be changed is the Steady-State Seconds. Update this to a run time of 5 minutes and click Apply Changes.
25. Next, both Maximum Simultaneous Sessions and Maximum Sessions Per Second will be updated. Enter values that your server is expected to be able to handle and click Apply Changes.
26. The last parameter that needs to be changed is selecting the Super Flow that was created earlier. Using the Super Flow drop-down menu select HTTP Client Login and click Apply Changes.
28. When prompted for a name to save the test as, enter Load Generator HTTP Login and click Save.
The Summary tab initially will be displayed. A great amount of information is seen on this screen, from the TCP Connection Rate to the Cumulative TCP Connections to the Bandwidth being used.
29. Select the Client tab. This displays information about the client’s connections and if they are successful or not. Verify that connections are successfully being made.
30. Once the test completes, a window will appear stating that the test passed. Click Close to continue.
32. Expand the Test Results for HTTP Login folder, and then expand the Details folder. Select Response Summary. Determine what code pages were sent—every page should have responded with an HTTP/1.1 200.
7. Make sure the flow has been selected in the Define Flows field. In the Define Actions field using the Action drop-down menu, select Server: Verify File.
Click the Add Action button once completed.
8. Select the newly added action in the Define Actions section. Click the Edit the selected actions parameters button.
14. Under the Test Quick Steps, click Select the DUT/Network.
15. In the Choose a device under test and network neighborhood window under the Device Under Test(s) section, verify that BreakingPoint Default is selected. Under Network Neighborhood(s), verify that the newly created one is selected. Click Accept.
19. Under the Information tab, enter HTTP Verify as the name and click Apply Changes.
20. Select the Interfaces tab. Verify that only External Server and Interface 1 Client are enabled.
21. Select the Parameters tab. Several parameters will be changed in this section. The first parameter that needs to be updated is the Minimum data rate. Enter a value of 1000 (if your server supports gigabit Ethernet) and click Apply Changes.
22. The next parameter to be changed is the Steady-State Seconds. Update this to a run time of 5 minutes and click Apply Changes.
23. Next, both Maximum Simultaneous Sessions and Maximum Sessions Per Second will be updated. Enter values that your server is expected to be able to handle and click Apply Changes.
24. The last parameter that needs to be changed is selecting the Super Flow that was created earlier. Using the Super Flow drop-down menu, select HTTP Verify File and click Apply Changes.
26. When prompted for a name to save the test as, enter Load Generator HTTP Verify and click Save.
The Summary tab initially will be displayed. A great amount of information is seen on this screen, from the TCP Connection Rate to the Cumulative TCP Connections to the Bandwidth being used.
27. Select the Client tab. This displays information about the client’s connections and if they are successful or not. Verify that connections are successfully being made.
28. Once the test completes, a window will appear, stating that the test either passed or failed. If the test failed, it is because not enough pages were verified as being correct. Click Close to continue.
30. Expand the Test Results for HTTP Verify folder, and then expand the Details folder. Select Response Summary. Determine what code pages were sent—every page should have been responded with an HTTP/1.1 200. This step is just a way to verify that pages were received with the correct status code.
7. In the Define Flows section use the Protocol drop-down menu and select SMB File Stress. Click Add Flow once completed.
8. Make sure the new flow has been selected in the Define Flows field. In the Define Actions field using the Action drop-down menu, select Client: Authenticate. Click the Add Action button once completed.
9. Using the Action drop-down menu select Client: Write file to share, Client: Read file from share, Client: Delete file from share, Client: Goto and Client: Disconnect. Click the Add Action button to add each one individually.
10. Select the Client: Authenticate action in the Define Actions section. Click the Edit the selected actions parameters button.
11. Enable Share Name, Username, and Password. Enter a valued share in the Share Name field. Also, enter a valid username and password in the respective fields. Make sure the user being used has full read and write permissions on the share. Finally, the Protocol Version drop-down menu can be used to select either SMB or SMBv2. Click Apply Changes once completed.
12. Select Client: Write file to share in the Define Actions section. Click the Edit the selected actions parameters button.
13. Enable File Name and enter smb-test%f-%g.txt. The %f is a wild card for the flow ID and the %g is a wild card for the Goto loop iteration number. If desired, enter values for the Minimum Random Filesize and the Maximum Random Filesize parameters. Once completed, click Apply Changes.
14. Select Client: Read file from share in the Define Actions section. Click the Edit the selected actions parameters button.
18. Select Client: Goto in the Define Actions section. Click the Edit the selected actions parameters button.
19. Using the Goto Action drop-down menu, select 2:Write file to share. Enter a value of 5 in the Iterations field. This will loop over the write, read and delete actions five times.
22. Under the Test Quick Steps, click Select the DUT/Network.
23. In the Choose a device under test and network neighborhood window under the Device Under Test(s) section, verify that BreakingPoint Default is selected. Under Network Neighborhood(s), verify that the newly created one is selected. Click Accept.
27. Under the Information tab, enter SMB File Stress as the name and click Apply Changes.
28. Select the Interfaces tab. Verify that only External Server and Interface 1 Client are enabled.
29. Select the Parameters tab. Several parameters will be changed in this section. The first parameter that needs to be updated is the Minimum data rate. Enter a value of 1000 (if your server supports gigabit Ethernet) and click Apply Changes.
30. The next parameter to be changed is the Steady-State Seconds. Update this to a run time of 5 minutes and click Apply Changes.
31. Next, both Maximum Simultaneous Sessions and Maximum Sessions Per Second will be updated. Enter values that your server is expected to be able to handle and click Apply Changes.
32. The last parameter that needs to be changed is selecting the Super Flow that was created earlier. Using the Super Flow drop-down menu select SMB Client Actions and click Apply Changes.
34. When prompted for a name to save the test as, enter Load Generator SMB and click Save.
The Summary tab initially will be displayed. A great amount of information is seen on this screen, from the TCP Connection Rate to the Cumulative TCP Connections to the Bandwidth being used.
35. Select the Client tab. This displays information about the client’s connections and if they are successful or not. Verify that connections are successfully being made.
36. Once the test completes, a window will appear, stating that the test passed. Click Close to continue.
38. Expand the Test Results for SMB File Stress Login folder. Select SMB Summary. Determine that files were successfully written, read and deleted. Also, log in to the share or check on the server that the files were deleted too.
7. In the Define Actions sections, select the first item and click the Edit the selected actions parameters button.
8. In the Conditional Request window, make sure that the first Match field is the only field that has data in it. Delete any other information. Also, make sure that the first Match field has Regex enabled. Once completed, click the Apply Changes button.
12. Using the Server drop-down menu, select SMTP Server. As the SMTP server and the IMAPv4 Server reside on the same system, another server does not need to be created. Using the Protocol drop-down menu, select IMAPv4-Advanced. Click Add Flow.
13. With the newly added flow selected in the Define Actions field using the Action drop-down menu, select Client: Conditional Request. Click Add Action.
20. Disable the Transaction Flag box and enter * OK in the first Match field and OK in the second. Scroll down to the Mismatch section. Locate Client: Goto in the Actions drop-down menu. Click Add Action.
24. Select the Client: Login action and click the Edit the select action parameters button.
25. Disable Transaction Flag and Starting Tag Value (0 == Random). Enable both Username and Password entering in the correct value for both. Click Apply Changes once completed.
26. Select the third item, Client: Conditional Request and click the Edit the select action parameters button.
41. In the Choose a device under test and network neighborhood window under the Device Under Test(s) section, verify that BreakingPoint Default is selected. Under Network Neighborhood(s), verify that the newly created one is selected. Click Accept.
42. When prompted about switching Network Neighborhoods because the current setup contains more interfaces, click Yes.
45. Under the Information tab enter SMTP IMAP as the name and click Apply Changes.
46. Select the Interfaces tab. Verify that only External Server and Interface 1 Client are enabled.
47. Select the Parameters tab. Several parameters will be changed in this section. The first parameter that needs to be updated is the Minimum data rate. Enter a value of 1000 (if your server supports gigabit Ethernet) and click Apply Changes.
48. The next parameter to be changed is the Steady-State Seconds. Update this to a run time of 2 minutes and click Apply Changes.
49. Next, both Maximum Simultaneous Sessions and Maximum Sessions Per Second will be updated. Enter values that your server is expected to be able to handle and click Apply Changes.
50. The last parameter that needs to be changed is selecting the Super Flow that was created earlier. Using the Super Flow drop-down menu, select Load Generator SMTPIMAP and click Apply Changes.
52. When prompted for a name to save the test as, enter Load Generator SMTP IMAP and click Save.
The Summary tab initially will be displayed. A great amount of information is seen on this screen, from the TCP Connection Rate to the Cumulative TCP Connections to the Bandwidth being used.
7. In the Define Actions sections select the first item and click the Edit the selected actions parameters button.
8. In the Conditional Request window, make sure that the first Match field is the only field that contains data. Delete any other information. Also, make sure that the first Match field has Regex enabled. Once completed, click the Apply Changes button.
12. Using the Server drop-down menu, select SMTP Server. Because the SMTP server and the POP3 Server reside on the same system, there is no need to create another server. Using the Protocol drop-down menu, select POP3-Advanced. Click Add Flow.
13. With the newly added flow selected in the Define Actions section, use the Action drop-down menu and select Client: Conditional Request. Click Add Action once completed.
17. In the Conditional Request window, disable the Transaction Flag and in the first Match field enter +OK. Using the Actions drop-down menu, select Client: Login. Click the Add Action button once completed.
18. Select the newly added action and click the Edit the selected action parameters button.
19. Enable both Username and Constant Password. Enter appropriate values for both. Click Apply Changes once completed.
22. In the RETR (Command Loop) window, make sure that only Transaction Flag and Number of Messages are enabled. Leave Transaction Flag set to Continue and enter a realistic value for Number of Messages. Click Apply Changes once completed.
23. Nothing needs to be changed with the Client: Quit action. Click Save Super Flow.
25. Under the Test Quick Steps, click Select the DUT/Network.
26. In the Choose a device under test and network neighborhood window under the Device Under Test(s) section, verify that BreakingPoint Default is selected. Under Network Neighborhood(s), verify that the newly created one is selected. Click Accept.
30. Under the Information tab, enter SMTP POP3 as the name and click Apply Changes.
31. Select the Interfaces tab. Verify that only External Server and Interface 1 Client are enabled.
32. Select the Parameters tab. Several parameters will be changed in this section. The first parameter that needs to be updated is the Minimum data rate. Enter a value of 1000 (if your server supports gigabit Ethernet) and click Apply Changes.
33. The next parameter to be changed is the Steady-State Seconds. Update this to a run time of 2 minutes and click Apply Changes.
34. Next, both Maximum Simultaneous Sessions and Maximum Sessions Per Second will be updated. Enter values that your server is expected to be able to handle and click Apply Changes.
35. The last parameter that needs to be changed is selecting the Super Flow that was created earlier. Using the Super Flow drop-down menu select Load Generator SMTPPOP3 and click Apply Changes.
37. When prompted for a name to save the test as, enter Load Generator SMTP POP3 and click Save.
The Summary tab initially will be displayed. A great amount of information is seen on this screen, from the TCP Connection Rate to the Cumulative TCP Connections to the Bandwidth being used.
40. As the mail was just retrieved and not deleted from the mail server, as is typical with POP3, mail should still reside on the server. Login and check the contents of the inbox and verify that new mail is present and has been opened.
7. Almost everything in this Super Flow has been configured. Changes will have to be made in the Define Actions sections to specify the database and add some new SQL statements. Select the first item, Client: Login Request, and click the Edit the selected actions parameters button.
8. In the Login Request window, update the Username, Password and Server Name to match your MS SQL configuration. Also, disable Client Name and Client Application. Click Apply Changes once completed.
9. Select the third item, Client: Conditional Request, and click the Edit the selected actions parameters button.
14. In the Conditional Request window, edit the Match field to include your database and then click the Edit the selected actions parameters button.
15. Change the SQL Query field to an SQL statement that will update the tables in the database. For example, INSERT INTO bpoint VALUES (‘Rams’, ‘Cardinals’). Once completed, click the Apply Changes button.
16. Using the Actions drop-down menu select Client: Query: Select Request and click the Add Action button.
17. Select the newly added item and click the Edit the selected actions parameters button.
18. Enable the SQL Query field and enter an SQL Select statement to select data from a table. For example: SELECT footballs_teams, baseball_teams FROM bpoint. Click the Apply Changes button once completed.
19. From the Conditional Request window, click the Apply Changes button.
20. From the main Super Flow configuration screen, select the sixth item in the Define Actions sections and click the Delete button. Once completed, click Save Super Flow.
22. Under the Test Quick Steps, click Select the DUT/Network.
23. In the Choose a device under test and network neighborhood window under the Device Under Test(s) section, verify that BreakingPoint Default is selected. Under Network Neighborhood(s), verify that the newly created one is selected. Click Accept.
27. Under the Information tab, enter MS SQL as the name and click Apply Changes.
28. Select the Interfaces tab. Verify that only External Server and Interface 1 Client are enabled.
29. Select the Parameters tab. Several parameters will be changed in this section. The first parameter that needs to be updated is the Minimum data rate. Enter a value of 1000 (if your server supports gigabit Ethernet) and click Apply Changes.
30. The next parameter to be changed is the Steady-State Seconds. Update this to a run time of 5 minutes and click Apply Changes.
31. Next, both Maximum Simultaneous Sessions and Maximum Sessions Per Second will be updated. Enter values that your server is expected to be able to handle and click Apply Changes.
32. The last parameter that needs to be changed is selecting the Super Flow that was created earlier. Using the Super Flow drop-down menu select Load Generator MS SQL and click Apply Changes.
34. When prompted for a name to save the test as, enter Load Generator MS SQL and click Save.
The Summary tab initially will be displayed. A great amount of information is seen on this screen, from the TCP Connection Rate to the Cumulative TCP Connections to the Bandwidth being used.
35. Select the Client tab. This displays information about the client’s connections and if they are successful or not. Verify that connections are successfully being made.
36. Once the test completes, a window will appear stating that the test passed. Click Close to continue.
38. Expand Test Results for MS SQL folder, and then expand the Details folder. Select Response Summary. Determine if the matches were successful or not.
39. On the MS SQL Server, verify that the database contains the data that was pushed to it. If the data is not present, check the SQL statements or the configuration of MS SQL.
40. If multiple tests are going to be performed in the Super Flow, add a delete SQL statement to remove the items from the database.
7. Almost everything in this Super Flow has been configured. Changes will have to be made in the Define Actions sections to specify the database and add some SQL statements. Select the first item, Client: Authenticate, and click the Edit the selected actions parameters button.
8. In the Authenticate window, enter the correct Database Username and Database Password that your MySQL server is configured to use. Click Apply Changes once completed.
9. Select the second item, Client: Conditional Request, and click the Edit the selected actions parameters button.
10. In the Conditional Request window, click the Edit the selected actions parameters button.
11. Change the SQL Statement field to an SQL statement that will update the tables in the database. For example, INSERT INTO test.bpoint VALUES (‘Giants’, ‘Mets’). Once completed click the Apply Changes button.
12. Using the Actions drop-down menu, select Client: Query and click the Add Action button.
13. Select the newly added item and click the Edit the selected actions parameters button.
14. Enable the SQL Statement field and enter an SQL Select statement to select data from a table. For example: SELECT * FROM test.bpoint. Click the Apply Changes button once completed.
18. Under the Test Quick Steps, click Select the DUT/Network.
19. In the Choose a device under test and network neighborhood window under the Device Under Test(s) section, verify that BreakingPoint Default is selected. Under Network Neighborhood(s), verify that the newly created one is selected. Click Accept.
23. Under the Information tab enter MySQL as the name and click Apply Changes.
24. Select the Interfaces tab. Verify that only External Server and Interface 1 Client are enabled.
25. Select the Parameters tab. Several parameters will be changed in this section. The first parameter that needs to be updated is the Minimum data rate. Enter a value of 1000 (if your server supports gigabit Ethernet) and click Apply Changes.
26. The next parameter to be changed is the Steady-State Seconds. Update this to a run time of 5 minutes and click Apply Changes.
27. Next, both Maximum Simultaneous Sessions and Maximum Sessions Per Second will be updated. Enter values that your server is expected to be able to handle and click Apply Changes.
28. The last parameter that needs to be changed is selecting the Super Flow that was created earlier. Using the Super Flow drop-down menu select Load Generator MS SQL and click Apply Changes.
30. When prompted for a name to save the test as, enter Load Generator MySQL and click Save.
The Summary tab initially will be displayed. A great amount of information is seen on this screen, from the TCP Connection Rate to the Cumulative TCP Connections to the Bandwidth being used.
31. Select the Client tab. This displays information about the client’s connections and if they are successful or not. Verify that connections are successfully being made.
32. Once the test completes, a window will appear stating that the test passed. Click Close to continue.
34. Expand Test Results for MySQL folder, then expand the Details folder. Select Response Summary. Determine if the matches were successful or not.
35. On the MySQL Server, verify that the database contains the data that was pushed to it. If the data is not present, check the SQL statements or the configuration of the MySQL server.