Greetings Xu,

Yes seems like I have had used only one port - let me re-run by making the necessary changes in ports.cfg and get back with the observations.

@ Lijuan Tu,

Please find the answers in-line.

Thanks & Regards,
Chengappa

From: Xu, GangX [mailto:gangx.xu@intel.com]
Sent: Tuesday, May 22, 2018 7:12 AM
To: M R, Chengappa (Network Function Virtualization) <cm-r@hpe.com>; dts@dpdk.org
Subject: RE: low pass rate executing dts complete test suite

Hi Chengappa:
How many ports do you use?
In the information you provided, I think you used only one port.
Many of the case in dts need two ports or more.
e.g. test suite pmd_bonded need 4 ports, you provide 1, it failed at set_up_all show "blocked set_up_all failed" issue.

Xu gang


From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Tu, Lijuan
Sent: Monday, May 21, 2018 9:49 PM
To: M R, Chengappa (Network Function Virtualization) <cm-r@hpe.com<mailto:cm-r@hpe.com>>; dts@dpdk.org<mailto:dts@dpdk.org>
Subject: Re: [dts] low pass rate executing dts complete test suite

Hi chengappa,
         Here are my points:
1, the link might have some issues, such as link down
         From the result "receive 0 , expect 64", I think , the link is down
         You can check your link first before running dts.
          [Chengappa] sure, will check on this, thank you for the inputs.

2, DPDK will change during different version , so DTS will change with it.
         Which DPDK and DTS 's version do you use?
         From the failed result "set up failed" and timeout , I think your testpmd started failed.
         Logs in output, you can check them to find the real reason, maybe testpmd's parameters changed.
          [Chengappa]
Am using DPDK 18.02 with DTS 17.08.0, kindly let me know if there are any issues with the combination am using or version mismatch here?
With the log traces I was able to see that the testpmd failed to start - is there anything that I need to tweak to change the testpmd's parameters to be changed?


From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of M R, Chengappa (Network Function Virtualization)
Sent: Monday, May 21, 2018 7:28 PM
To: dts@dpdk.org<mailto:dts@dpdk.org>
Subject: [dts] low pass rate executing dts complete test suite

Hello DTS community,

As we were investigation on DTS for Niantic (Intel Corporation 82599ES 10-Gigabit) platform and we are seeing very less pass rate.

We were under the assumption if we take care of the initial pre-requisites for TESTER and TARGET DUT as described here - https://dpdk.org/doc/dts/gsg/sys_reqs.html the DTS framework help us achieve a good pass rate.

Could you please help me by letting know if there are any fine tuning for the TARGET DUT so that I can see a better numbers than the current pass rate of 12.4%

[root@tester dts]# cat output/statistics.txt
Passed     = 17
Failed     = 45
Blocked    = 68
Pass rate  = 12.4



Some of the specification on the TARGET DUT and current running configuration are as follows


[root@targetdut ~]# lspci | egrep -i --color 'network|ethernet'
04:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Skyhawk) (rev 10)
04:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Skyhawk) (rev 10)
05:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
05:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)




[root@tester dts]# cat conf/ports.cfg
# DUT Port Configuration
# [DUT IP]
# ports=
#     pci=Pci BDF,intf=Kernel interface;
#     pci=Pci BDF,mac=Mac address,peer=Tester Pci BDF,numa=Port Numa
#     pci=Pci BDF,peer=IXIA:card.port
#     pci=Pci BDF,peer=Tester Pci BDF,tp_ip=$(IP),tp_path=$({PERL_PATH);
#     pci=Pci BDF,peer=Tester Pci BDF,sec_port=yes,first_port=Pci BDF;
# [VM NAME] virtual machine name; This section is for virutal scenario
# ports =
#     dev_idx=device index of ports info, peer=Tester Pci BDF
[10.70.2.6]
ports =
    pci=05:00.0,intf=ens2f0;
    pci=05:00.1,intf=ens2f1;



[root@tester dts]# cat executions/execution.cfg
[Execution1]
crbs=10.70.2.6
drivername=igb_uio
test_suites=hello_world
test_suites=
    cmdline,
    hello_world
targets=x86_64-native-linuxapp-gcc
parameters=nic_type=niantic:func=true



[root@tester dts]# cat conf/crbs.cfg
#DUT crbs Configuration
#[DUT IP]
#  dut_ip: DUT ip address
#  dut_user: Login DUT username
#  dut_passwd: Login DUT password
#  os: operation system type linux or freebsd
#  tester_ip: Tester ip address
#  tester_passwd: Tester password
#  ixia_group: IXIA group name
#  channels: Board channel number
#  bypass_core0: Whether by pass core0
[10.70.2.6]
dut_ip=10.70.2.6
dut_user=root
dut_passwd=HP1nvent
os=linux
tester_ip=10.70.2.5
tester_passwd=HP1nvent
channels=4


Snippet of the current results

[cid:image001.png@01D3F1A6.300ADDC0]
[cid:image002.png@01D3F1A6.300ADDC0]
[cid:image003.png@01D3F1A6.300ADDC0]
[cid:image004.png@01D3F1A6.300ADDC0]

Thanking in advance,
Chengappa

If everyone is moving forward together, then success takes care of itself....!!