| Next revision | Previous revision |
| en:dpi:dpi_brief:test_cases:dpi [2024/12/19 13:56] – created elena.krasnobryzh | en:dpi:dpi_brief:test_cases:dpi [2026/04/03 12:49] (current) – [Test 3. Uplink Speed Limitation Without Deteriorating Critical Service Quality] elena.krasnobryzh |
|---|
| **Let's check it in tests:** | **Let's check it in tests:** |
| |
| [[en:dpi:dpi_brief:test_cases:dpi#тест_1_обзор_статистики_dpiданные_о_структуре_трафика_и_сетевых_метриках|Test 1. DPI Statistics Overview: Traffic Structure and Network Metrics Data]]\\ | [[en:dpi:dpi_brief:test_cases:dpi#test_1_dpi_statistics_overviewtraffic_structure_and_network_metrics_data|Test 1. DPI Statistics Overview: Traffic Structure and Network Metrics Data]]\\ |
| [[en:dpi:dpi_brief:test_cases:dpi#тест_2_настройка_приоритизации_и_блокировки_по_прикладному_протоколу_для_общей_полосы|Test 2. Prioritization and Blocking Setup by Application Protocol for Shared Bandwidth]]\\ | [[en:dpi:dpi_brief:test_cases:dpi#test_2_prioritization_and_blocking_setup_by_application_protocol_for_shared_bandwidth|Test 2. Prioritization and Blocking Setup by Application Protocol for Shared Bandwidth]]\\ |
| [[en:dpi:dpi_brief:test_cases:dpi#тест_3_ограничение_скорости_аплинка_без_ухудшения_качества_критичных_сервисов|Test 3. Uplink Speed Limitation Without Deteriorating Critical Service Quality]] | [[en:dpi:dpi_brief:test_cases:dpi#test_3_uplink_speed_limitation_without_deteriorating_critical_service_quality|Test 3. Uplink Speed Limitation Without Deteriorating Critical Service Quality]] |
| |
| <note tip>**Test Conditions:**\\ | <note tip>**Test Conditions:**\\ |
| - Open the QoE Analytics/Dashboard section. Here, you can display and configure all necessary metrics for easy control as numeric indicators or charts. In the top menu, you can select the statistics period, defaulting to 2 hours.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img1.png?nolink&900|}} | - Open the QoE Analytics/Dashboard section. Here, you can display and configure all necessary metrics for easy control as numeric indicators or charts. In the top menu, you can select the statistics period, defaulting to 2 hours.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img1.png?nolink&900|}} |
| - Navigate to the "Netflow" section. In the right part of the screen, find the "Reports" section, and expand the "Traffic Speed" list\\ {{:en:dpi:dpi_brief:test_cases:dpi_img2.png?nolink&900|}} | - Navigate to the "Netflow" section. In the right part of the screen, find the "Reports" section, and expand the "Traffic Speed" list\\ {{:en:dpi:dpi_brief:test_cases:dpi_img2.png?nolink&900|}} |
| - Analyze traffic by application protocols, highlighting the most popular protocols by speed and traffic volume:\\ {{:en:dpi:dpi_brief:test_cases:dpi_img3.png?nolink&900|}}\\ //The top list and graphs display the most important protocols, showing their "weight" and activity periods.// | - Analyze traffic by application protocols, highlighting the most popular protocols by bandwidth and traffic volume:\\ {{:en:dpi:dpi_brief:test_cases:dpi_img3.png?nolink&900|}}\\ //The top list and graphs display the most important protocols, showing their "weight" and activity periods.// |
| - Analyze traffic by groups of application protocols. The system identifies thousands of protocols. To avoid analyzing and configuring each separately, our developers grouped them.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img4.png?nolink&900|}}\\ //The idea is similar to individual protocols but works with entire groups (categories).// | - Analyze traffic by groups of application protocols. The system identifies thousands of protocols. To avoid analyzing and configuring each separately, our developers grouped them.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img4.png?nolink&900|}}\\ //The idea is similar to individual protocols but works with entire groups (categories).// |
| - Analyze traffic by autonomous systems.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img5.png?nolink&900|}}\\ //This analysis is essential for optimizing network routes and deciding on peering with systems with the most active traffic exchange.// | - Analyze traffic by autonomous systems.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img5.png?nolink&900|}}\\ //This analysis is essential for optimizing network routes and deciding on peering with systems with the most active traffic exchange.// |
| * Play 4K video on YouTube\\ //The video may lag due to torrents consuming the bandwidth.// | * Play 4K video on YouTube\\ //The video may lag due to torrents consuming the bandwidth.// |
| - Configure priorities. Go to DPI Management → Protocol Prioritization\\ {{:en:dpi:dpi_brief:test_cases:dpi_img11.png?nolink&500|}} | - Configure priorities. Go to DPI Management → Protocol Prioritization\\ {{:en:dpi:dpi_brief:test_cases:dpi_img11.png?nolink&500|}} |
| - Add the protocols from the test service list (WhatsApp, Bittorrent, YouTube in the "Protocol" column). Assign a class in the "DSCP Value" column when adding each protocol. Classes range from cs0 (highest priority) to cs7 (lowest), with "drop" blocking the protocol.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img12.png?nolink&500|}} | - Add signatures for the test scenario to the **"Protocol"** column. When adding each protocol, assign it a class in the **"DSCP Value"** column: |
| - **<color #ed1c24>After configuration, save and "update hot parameters"</color>.**\\ {{:en:dpi:dpi_brief:test_cases:dpi_img13.png?nolink&500|}} | * dns – cs0 |
| | * youtube – cs1 |
| | * default – cs2 |
| | * whatsapp – drop |
| | * whatsapp_voice – drop\\ \\ You can assign a class from cs0 to cs7, or drop: |
| | * cs0 — highest priority class |
| | * cs7 — lowest priority class |
| | * drop — blocks the protocol traffic\\ \\ In this configuration, DNS services will have the highest priority, YouTube will have medium priority, and all other traffic (default) will have the lowest priority, while WhatsApp (both calls and other app functions) will be unavailable.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img12.png?nolink&700|}} |
| | - **<color #ed1c24>After configuration, save and "update hot parameters"</color>.**\\ {{:en:dpi:dpi_brief:test_cases:dpi_img13.png?nolink&700|}} |
| |
| //The prioritization or blocking configuration by application protocol for shared bandwidth is complete.// | //The protocol prioritization by common channel is completed.// |
| |
| **Result:**\\ | **Result:**\\ |
| **Preparation:** | **Preparation:** |
| - Remove or disable all SSG policy settings from previous tests, eliminating prioritization and bandwidth limitations. | - Remove or disable all SSG policy settings from previous tests, eliminating prioritization and bandwidth limitations. |
| - Simultaneously enable several “heavy” internet applications, e.g.: | - Simultaneously enable several "heavy" internet applications, e.g.: |
| * Multiple torrent downloads. | * Multiple torrent downloads. |
| * 4K YouTube video playback. | * 4K YouTube video playback. |
| * Download large files from file hosting services. | * Perform large downloads from file hosting services (you may use test files on Wiki: [[https://wiki.vasexperts.ru/test/10mb.bin|10MB]], [[https://wiki.vasexperts.ru/test/50mb.bin|50MB]], [[https://wiki.vasexperts.ru/test/100mb.bin|100MB]], [[https://wiki.vasexperts.ru/test/500mb.bin|500MB]]) |
| * Perform several Speedtest measurements. | * Perform several Speedtest measurements. |
| - Measure traffic peaks. This can be done using any tool, including the QoE module in SSG, which has a corresponding dashboard chart. Running applications will occupy the entire physical bandwidth, potentially working poorly due to channel contention.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img14.png?nolink&500|}} | - Measure traffic peaks. This can be done using any tool, including the QoE module in SSG, which has a corresponding dashboard chart. Running applications will occupy the entire physical bandwidth, potentially working poorly due to channel contention.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img14.png?nolink&500|}} |
| - Prioritize critical protocols; test the function of protocol group management. | - Prioritize critical protocols; test the function of protocol group management. |
| - Go to DPI Management → Protocol Prioritization\\ {{:en:dpi:dpi_brief:test_cases:dpi_img11.png?nolink&700|}} | - Go to DPI Management → Protocol Prioritization\\ {{:en:dpi:dpi_brief:test_cases:dpi_img11.png?nolink&700|}} |
| - Assign classes to protocol groups in the "DSCP Value" column. Classes range from cs0 (highest priority) to cs7 (lowest), with "drop" blocking the protocol. Assign high priority (cs0) to IP telephony, VPN, Video, and messenger groups, and low priority (cs7) to the P2P group.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img15.png?nolink&700|}} | - Assign classes to protocol groups in the column "The value of DSCP". Classes range from cs0 (highest priority) to cs7 (lowest), with "drop" blocking the protocol. Assign high priority (cs0) to VoIP applications, Video, and messenger groups, and low priority (cs7) to the P2P group.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img15.png?nolink&400|}} |
| - Save and “update hot parameters.” | - Save and "update hot parameters."\\ {{:en:dpi:dpi_brief:test_cases:dpi_img15_1.png?nolink&700|}} |
| - Enable the "Peak bandwidth limit" checkbox and set the bandwidth in Mbps (e.g., 20).\\ {{:en:dpi:dpi_brief:test_cases:dpi_img16.png?nolink&700|}} | - Set an upper bandwidth limit of 30 Mbps for all users: |
| | * Go to Main Menu → SSG control → Configuration → External channels’ usage optimization; |
| | * Use the "Autocomplete" button and set the limit to 30 Mbps.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img16.png?nolink&700|}} |
| |
| Testing is conducted similarly to Test 2. Torrents should not affect YouTube playback quality. Measure their speed before and during playback. | //Configuration of protocol group prioritization for the total bandwidth is complete.// |
| |
| | **Result:**\\ |
| | Perform tests: \\ |
| | * Repeat the action — run several "heavy" internet applications simultaneously, for example: |
| | * multiple torrent downloads |
| | * 4K video on Rutube |
| | * perform large downloads from file hosting services (you may use test files on Wiki: [[https://wiki.vasexperts.ru/test/10mb.bin|10MB]], [[https://wiki.vasexperts.ru/test/50mb.bin|50MB]], [[https://wiki.vasexperts.ru/test/100mb.bin|100MB]], [[https://wiki.vasexperts.ru/test/500mb.bin|500MB]]) |
| | * run multiple speed tests in Yandex Internetometer |
| | * Measure traffic peaks. Peaks should not exceed the configured maximum value. Measurement can be done using an external service or the built-in "Traffic speed" widget in the QoE dashboard.\\ {{:en:dpi:dpi_brief:test_cases:dpi_img17.png?nolink&500|}} |
| | * Despite bandwidth limitation, video and communication services should operate normally. When starting Rutube video, you can check BitTorrent downloads — their speed should decrease. |
