1. DSR Automated Test Suite Installation and User Guide
  2. Prerequisites for Test Case Execution

3.1 Prerequisites for Test Case Execution

This section provides information about the prerequisites that must be achieved in the following sequence before executing test cases:

  1. Ensure no hyphen is present in the stack name of NOAM and SOAM while deploying the VDSR stack through VNFM.
  2. Location of the Test Cases
    • The Cust-Roaming-Suite directory path is /var/lib/jenkins/workspace/Regression/Cust-Roaming-Suite.
    • The Cust-Core-DSR directory path is /var/lib/jenkins/workspace/Regression/Cust-Core-DSR.
    • The New-Features are located in /var/lib/jenkins/workspace/New-Features
    • The Performance test cases are located in /var/lib/jenkins/workspace/Performance/Radius_Traffic
    • All Cleanup pipeline test cases are located in /var/lib/jenkins/workspace/Cleanup/Cust-Cleanup-DSR
    • All vSTP test cases are divided into four different suites:

      /var/lib/jenkins/workspace/vSTP_Regression/behave_test_framework/vSTP-Suite1/

      /var/lib/jenkins/workspace/vSTP_Regression/behave_test_framework/Cust-vSTP-Suite2/

      /var/lib/jenkins/workspace/vSTP_Regression/behave_test_framework/Cust-vSTP-Suite3/

      /var/lib/jenkins/workspace/vSTP_Regression/behave_test_framework/Cust-vSTP-Suite4/

  3. SUT Requirements

    Table 3-1 DSR and SDS SUT Details

    Server Quantity
    DSR SUT
    DSR NOAM Active 1
    DSR NOAM Standby 1
    DSR Signaling SOAM Active 1
    DSR Signaling SOAM Standby 1
    DA-MP 2
    IPFE 2
    SDS SUT
    SDS NOAM Active 1
    SDS NOAM Standby 1
    Query Server 1
    SDS Signaling SOAM Active 1
    SDS Signaling SOAM Standby 1
    DP Server 1

    Table 3-2 vSTP SUT Details

    Server Quantity
    vSTP SUT
    vSTP NOAM Active 1
    vSTP NOAM Standby 1
    vSTP Signaling SOAM Active 1
    vSTP Signaling SOAM Standby 1
    MP 2

    Note:

    Ensure that when the SUT is created using VNFM, then Mediation, FABR, and RBAR features are enabled.
  4. Update SUT Information in ATS
    Following are mandatory tasks for Cleanup, New-Features, Performance, Regression, VDSR-HealthCheck suites:
    1. Update /home/cloud-user/Verizon-drop1/dsr-atsV2/dut.yaml with the SUT details. The same will be automatically copied to the required location when the execution starts from Jenkins. Edit the dut.yaml file.

      Update the dut.yaml file by referring to the following file: 

      DSRVIP:
  - name: DSRNOVIP
    IP: 2606:b400:605:b919:86b8:2ff:fe60:6278
  - name: DSRSOVIP
    IP: 2606:b400:605:b919:86b8:2ff:fe60:62ab
    SIGNALING_IPs:
      - IP: 2004:db8:1116::24
        type: LocalIp
      - IP: 2004:db8:1116::e
        type: LocalIp
      - IP: 2004:db8:1116::10
        type: IpfeTsa
      - IP:
        type: IpfeTsa
    ipfeInitiatorDampIp:
      - IP: 2004:db8:1116::24
    MP_XMI:
      - IP: 2606:b400:605:b919:86b8:02ff:fe60:629e
        type: LocalIp
      - IP: 2606:b400:605:b919:86b8:02ff:fe60:6298
        type: LocalIp
SDSVIP:
  - name: SDSNOVIP
    IP: 2606:b400:605:b919:86b8:2ff:fe60:6295
  - name: SDSSOVIP
    IP: 2606:b400:605:b919:86b8:2ff:fe60:627c
  - name: SDSQS
    IP: 2606:b400:605:b919:86b8:02ff:fe60:6242

LOCAL:
  - SIGNALING_IPs:
      - 2004:db8:1116::11
      - 2004:db8:1116::11
  - RERUN_COUNT: 1
    SDS_ENABLE: N
UI_data:
  - name: UIData
    PassWordUI: tekware
    UserNameUI: guiadmin
    noamHost: http://[2606:b400:605:b919:86b8:2ff:fe60:6278]
    soamHost: http://[2606:b400:605:b919:86b8:2ff:fe60:62ab]
    StandBysoamHost: http://[2606:b400:605:b919:86b8:02ff:fe60:6290]
    StandBynoamHost: http://[2606:b400:605:b919:86b8:02ff:fe60:628f]
    sdsnoamHost: http://[2606:b400:605:b919:86b8:2ff:fe60:6295]
    sdssoamHost: http://[2606:b400:605:b919:86b8:2ff:fe60:627c]
    StandBysdssoamHost: http://[2606:b400:605:b919:86b8:02ff:fe60:629f]
    StandBysdsnoamHost: http://[2606:b400:605:b919:86b8:02ff:fe60:62c0]
    2. Update /home/cloud-user/Verizon-drop1/dsr-atsV2/auth.yaml. The same will be automatically copied to the required location when the execution starts from Jenkins. Server credentials, such as username and password, displayed in the following image can be updated if required.
    3. Verify using the command: 
      ps -eaf | grep jenkins
      Example Output:
      cloud-u+   524413     1  2 01:43 pts/0    00:01:10 java -Dhudson.model.WorkspaceCleanupThread.disabled=true -jar /usr/lib/jenkins/jenkins.war
      If not, then run the command:
      ./jenkins_start.sh
    4. The rerun functionality in the Roaming suite can be changed by updating the dut.yaml file. The values are:
      • RERUN_COUNT: 1
      • SDS_ENABLE: N
    Following are mandatory tasks for vSTP-Regression suite:
    1. Update /home/cloud-user/Verizon-drop1/vSTP-ats/vstp_signalling_ips.yaml with the SUT details for vSTP test cases. The same will be automatically copied to the required location when the execution starts from Jenkins. Edit the vstp_signalling_ips.yaml file. Update the vstp_signalling_ips.yaml file by referring to the following file:
      VSTP_SIGNALLING_IP:
# MP XSI IP on which traffic is to be run
  - name: XSI1
    IP: 121.131.152.209 
MEAT_SIGNALLING_IP:
# MEAT XSI IP from which traffic is to be run
  - name: meat1
    IP: 121.131.152.207
ACTIVE_SO_IPS:
#Current active SO XMI IP
  - name: so_sg1
    IP : 10.75.162.138
  - name: so_sg2
    IP : 10.75.162.245 
ACTIVE_NO_IP:
#Current active NO XMI IP
    IP: 10.75.162.199 
VSTP_TPCs:
#TPC not to be changed to be kept as such
  - vstp_tpc_itui: 3-45-4
    vstp_tpc_itun: '8734'
    vstp_tpc_ansi: 5-44-8
# XMI IP of meat machine from which traffic is to run
MEAT_IP: 10.75.162.228
UDR:
#UDR IP for future use
  - name: udr1
    IP: 10.75.218.250 
NUM_MP_PER_SITE: 2 
ALL_SITE_XSI1_IP:
# Name and XMI IP of all MP's present
  - name: so1mp1
    IP: 121.131.152.209
  - name: so1mp2
    IP: 121.131.152.140
    2. Update /home/cloud-user/Verizon-drop1/vSTP-ats/passwords/auth.yaml. The same will be automatically copied to the required location when the execution starts from Jenkins. Server credentials, such as username and password, displayed in the following image can be updated if required.
    3. Verify using the command: 
      ps -eaf | grep jenkins
      Example Output:
      cloud-u+   524413     1  2 01:43 pts/0    00:01:10 java -Dhudson.model.WorkspaceCleanupThread.disabled=true -jar /usr/lib/jenkins/jenkins.war
      If not, then run the command:
      ./jenkins_start.sh
    4. Disable firewall from an active SOAM of vSTP from the path shown in below figure.
      disable firewall

    5. In order to be able to access the MPs from the ATS machine, for VSTP Suite run we need to run the following command for all MP’s. <stp ip> to be replaced by XMI IP of one MP at a time: 
      cat ~/.ssh/id_rsa.pub | ssh admusr@<stp ip> "mkdir -p ~/.ssh && chmod 700 ~/.ssh && cat >> ~/.ssh/authorized_keys"
  5. Enabling the Feature on SUT

    Note:

    Ensure that there are no backup files in the /var/TKLC/db/filemgmt/backup location while executing the database restore test case on SOAM. If there are backup files, then the Mediation feature must be enabled in each backup file. Otherwise, sometimes the Mediation feature might get disabled while execution of this test case.
    • Ensure that RBAR and FABR are enabled as displayed in the following image:

      Figure 3-1 RBAR and FABR Enabled on the DSR GUI

      RBAR and FABR Enabled
    • Ensure that Mediation is enabled as displayed in the following image:

      Figure 3-2 Mediation Enabled on the DSR GUI

      Mediation Enabled
    • Ensure that DCA is enabled as displayed in the following image:

      Figure 3-3 DCA Enabled on the DSR GUI

      DCA Enabled
  6. Configure ComAgent connections on DSR by referring to the Diameter Signaling Router Cloud Installation Guide.

    Note:

    The DSR BUG 29035530 can cause ATS GUI case failure due to the "Security Violation" error when you perform any common GUI operation. This can be identified in /var/TKLC/appw/logs/Process/AppWorksGui.log by searching for the Security violation by a user keyword.