Testing and Integration Process [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks

    • Differences

    This shows you the differences between two versions of the page.

    Link to this comparison view

    Next revision    		Previous revision
    en:dpi:dpi_brief:integration [2024/12/25 13:09] – created elena.krasnobryzhen:dpi:dpi_brief:integration [2025/06/11 07:17] (current) – elena.krasnobryzh
    Line 1: Line 1:
     {{indexmenu_n>3}} {{indexmenu_n>3}}
    -======Process of Integrating SSG into the Operator's Network====== +======Testing and Integration Process====== 
    -=====Step 1. Server Preparation===== +=====Stage 1. Preparing Servers and Virtual Machines===== 
    -**Client Responsibilities:** +**Responsibilities of the telecom operator or partner preparing the equipment for delivery:** 
    -  - Prepare the server according to the requirements. +  - Prepare a server or VM according to the requirements: 
    -  - Provide servers with VEOS installed. Pay attention to the preliminary VEOS configuration. +    * [[en:dpi:dpi_brief:dpi_requirements#recommended_requirements|Requirements for SSG (DPI, BRAS, NAT)]]. If using a [[en:dpi:dpi_brief:dpi_requirements#requirements_for_installation_on_a_virtual_machine|VM for SSG, follow the setup instructions]] 
    -  - Provide access. Two options are available: +    * [[en:dpi:dpi_components:dpiui:hardware_recommendations#recommended_requirements|Requirements for GUI]] 
    -    - Send login and password for SSH. +    * [[en:dpi:dpi_components:qoestor:hardware_recommendations#recommended_requirements_for_every_10gbps_peak_traffic_on_dpi|Requirements for QoE]]\\ **QoE must not be installed on the SSG server. \\ GUI may be installed on the SSG server only for testing purposes. For production, GUI must be deployed on a separate server or VM. \\ GUI and QoE may be installed on the same server; in this case, hardware requirements are cumulative.** 
    -    - Use a ready-made script to add servers to Teleport.+  - Install the [[en:veos:installation|VEOS]] operating system. Be sure to configure the [[en:veos:installation#pre-configuring_veos|Firewall for access restriction]] and use strong passwords. 
     +  - Ensure network connectivity between the designated servers or VMs. 
     +  - Provide SSH access (port ''22'') to each server over the internet or via VPN. GUI additionally requires HTTPS access (port ''443''). Each server must have internet access to install software. Check connectivity using the command: <code>ping vasexperts.com</code> Two access options are available: 
     +    - Provide login and password for SSH access. 
     +    - Use the ready-made script to add servers to Teleport. The script is available upon request via your account manager.
      
    -**VAS Experts Responsibilities:**+**Responsibilities of VAS Experts:**
       - Connect to the servers via SSH.   - Connect to the servers via SSH.
    -  - Add servers to Teleport.+  - Add servers to Teleport for further support.
      
    -=====Step 2. Component Installation===== +=====Stage 2. Component Installation===== 
    -The installation depends on the functionality being used.+Installation depends on the required functionality.
      
    -**VAS Experts Responsibilities:** +**Responsibilities of VAS Experts:** 
    -  - SSG: +  - SSG (BRAS, NAT, DPI): Install SSG software on the server or VM 
    -    - Install SSG on the server. +  - GUI (recommended): Install GUI (DPIUI2) on a separate server or VM. Add all components and verify accessibility. 
    -  - GUI (if required): +  - QoE (recommended for DPI functionality): Install QoE on a separate server or VM. Configure storage for DPI statistics 
    -    - Install GUI on a separate server. If necessary (e.g., in test environments), the GUI can be installed on the same server as SSG. +  - Set up interaction between the modules (DPI, GUI, QoE)
    -  - QoE (for DPI functionality): +
    -    - Prepare a separate server for QoE. +
    -    - Install QoE.+
      
    -=====Step 3. Component Configuration===== +**Self-installation options for the telecom operator/partner:** 
    -The configuration depends on the functionality being used.+  - SSG (BRAS, NAT, DPI): [[en:dpi:dpi_brief:instal_script|]] 
     +  - GUI (recommended): [[en:dpi:dpi_components:dpiui:install_and_update:install|]] 
     +  - QoE (recommended for DPI functionality): [[en:dpi:dpi_components:qoestor:install_and_update:install|]] 
     +  - Set up interaction between the modules (DPI, GUI, QoE)
      
    -**Client Responsibilities:**+=====Stage 3. Component Configuration===== 
     +Configuration depends on the required functionality. 
     + 
     +**Responsibilities of the telecom operator/partner:** 
     +Fill out the questionnaire provided by the VAS Experts manager
      
     For NAT: For NAT:
    -  - Complete the questionnaire provided by the VAS Experts manager. +  - Provide a pool of public and private IP addresses 
    -  - Provide a pool of public IP addresses. +  - Provide the receiver’s IP address for NAT flow export (if a third-party solution is used)
    -  - Specify which private networks need to be connected to the CG-NAT service. +
    -  - Provide a receiver for exporting NAT events (if using a third-party solution).+
      
     For BRAS: For BRAS:
    -  - Configure the RADIUS server using the provided attribute dictionary. +  - Configure the RADIUS server using the provided attribute dictionary 
    -  - Provide information about the type of BRAS (L2 or L3) and the authentication method. +  - Provide information about the BRAS type (L2 or L3) and the authentication method 
    -  - Configure billing logic.+  - Configure billing responses to match the implementation scenarios
      
    -**VAS Experts Responsibilities:**+**Responsibilities of VAS Experts:**
      
     For DPI: For DPI:
    -  - Configure the interaction between modules (DPI, GUI, QoE).+  - [[en:dpi:dpi_components:qoestor:configuration:dpi|Configure statistics export from DPI]] to QoE [[en:dpi:dpi_options:opt_statistics:statistics_description|(Full Flow, ClickStream, DNS Flow, NAT Flow, GTP Flow)]] 
     +  - Provide an account for [[en:dpi:dpi_components:dpiui:user_guide:vas_cloud_services:custom_protocols|VAS Cloud access to create custom signatures]] 
     +  - Provide an extended QoE version for full statistics access
      
     For NAT: For NAT:
    -  - Assign public IP addresses in SSG. +  - Create a NAT service and assign it to private IP addresses according to the scenario: [[en:dpi:dpi_brief:test_cases:nat|]] 
    -  - Configure the export of NAT events. Two options are available: +  - Configure NAT Flow export. Two options are available: 
    -    - To the client receiver. +    - To a client-side receiver 
    -    - Use the VAS Expert solution — QoE with NAT Flow functionality.+    - Use the QoE solution from VAS Experts with NAT Flow functionality. Example scenario: [[en:dpi:opt_cgnat:abuse_letters]]
      
     For BRAS: For BRAS:
    -  - Configure SSG based on the type of BRAS (L2 or L3). +  - Configure SSG based on the BRAS type (L2 or L3) 
    -  - Collaborate with the client on necessary attributes in the RADIUS server response. +  - Collaborate with the client to configure the necessary RADIUS response attributes 
    -  - Debug and test business cases (e.g., blocking, Captive Portal, financial blocking).+  - Perform debugging and testing of business scenarios (e.g., financial blocking with redirect to Captive Portal, plan changes, scheduled plans)
      
    -=====Step 4. Integration and Testing===== +=====Stage 4. Integration and Testing===== 
    -**Client Responsibilities:** +**Responsibilities of the telecom operator/partner:** 
    -  - Prepare a portion of traffic or a list of test subscribers for verification.+  - Prepare a portion of traffic or a list of test subscribers for verification
      
    -**VAS Experts Responsibilities:** +**Responsibilities of VAS Experts:** 
    -  - Integrate SSG with a portion of real traffic or subscribers. +  - Integrate SSG with real traffic or subscribers 
    -  - Test the system's functionality. +  - Test system operability 
    -  - Address any identified issues.+  - Fix identified issues, if any
      
    -=====Step 5. Transition to Operation===== +=====Stage 5. Transition to Production===== 
    -**Client Responsibilities:** +**Responsibilities of the telecom operator/partner:** 
    -  - Confirm that the system operates according to the requirements.+  - Confirm that the system is functioning as required
      
    -**VAS Experts Responsibilities:** +**Responsibilities of VAS Experts:** 
    -  - Finalize the configuration and transfer the system into operation. +  - Complete setup and hand over the system for production 
    -  - Provide support during the implementation phase.+  - Provide support during the rollout phase