Created attachment 1555946 [details] PVP Results for Open vSwitch with DPDK Datapath L2 10hrs This bug will serve as a landing spot for the latest Broadcom PVP test results on RHEL8.0
Created attachment 1555947 [details] PVP Results for Open vSwitch with DPDK Datapath L3 10hrs
Created attachment 1555948 [details] PVP Results for Open vSwitch Kernel Datapath L3 10hrs
Created attachment 1555951 [details] PVP Results for Open vSwitch with DPDK Datapath L2 1hrs
Created attachment 1556350 [details] PVP Results for Open vSwitch with DPDK Datapath L3 1hrs
Created attachment 1556351 [details] PVP Results for Open vSwitch with Kernel Datapath L2 1hrs
Created attachment 1558209 [details] PVP Results for Open vSwitch Kernel Datapath L3 1hrs
Created attachment 1560830 [details] OVS FUnctional verification RHEL8.0 Client result
Created attachment 1560833 [details] OVS Functional verification RHEL8.0 Server Result log
Hello the client side of functional tests all report failures. Can you please provide the rh_nic_cert.sh from both the client and server side so I can see how it was configured? Thanks,
We have seen in the past where if all tests fail then the switch could be a problem. You can also try by doing the test with a back to back connection. The bonding tests will fail, but we can deal with that after.
From log below in attachment 1560830 [details], the port on host wsfd-netdev85.ntdv.lab.eng.bos.redhat.com is in state NO-CARRIER. Please check the connection between enp5s0f0np0 and the switch port. 100: enp5s0f0np0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master ovs-system state DOWN mode DEFAULT group default qlen 1000 link/ether 00:0a:f7:b6:e0:c0 brd ff:ff:ff:ff:ff:ff promiscuity 1 openvswitch_slave addrgenmode none numtxqueues 74 numrxqueues 74 gso_max_size 65536 gso_max_segs 65535 portname p0
Created attachment 1567727 [details] OVS Functional verification RHEL8.0 Client Rerun Result log OVS Functional verification RHEL8.0 Client Rerun Result log
Can you please let me know how can i upload a zip file more than 30MB???
from log in attachment 1567727 [details] in comment#12, they're all test for multicast, but only vlan related test failed. Because I don't see switch configuration, please check if switch has the correct setting. And please note that usually several tagged frames will be used and keep 3~100 vlan IDs are permitted.
Hi, The test suite is hanging at 'ovs-vlan test 9000 ' from the past 2days, So i did CTRL+C after that it executed some test , I collected the logs and shared to this BZ. Could you please tell me is there any way to run the failed test cases individually. Regards, Raghav
(In reply to raghavendrachari.kamsali from comment #15) > Hi, > > The test suite is hanging at 'ovs-vlan test 9000 ' from the past 2days, > So i did CTRL+C after that it executed some test , I collected the logs and > shared to this BZ. > Could you please tell me is there any way to run the failed test cases > individually. > With the example for running only ovs_test_vlan which is in code topo.sh. export QE_TEST=ovs_test_vlan in rh_nic_cert.sh or the running shell on both machines And please find the script file rh_nic_cert.sh and go to the bottom, the code below can be found, then comment out lines of 130 and 132 129 pushd openvswitch 130 grep 'bz1468631' <<<"${QE_SKIP_TEST}" || . bz1468631.sh |& tee -a ${test_log} 131 . topo.sh |& tee -a ${test_log} 132 . mcast_snoop.sh |& tee -a ${test_log} 133 popd &>/dev/null 134
Hi, I followed the above comment & rerun the test , but same isse happened , test hangs at ovs_vlan_test 9000 . Regards, Raghav
(In reply to raghavendrachari.kamsali from comment #17) > Hi, > > I followed the above comment & rerun the test , but same isse happened , > test hangs at ovs_vlan_test 9000 . if ovs_vlan_test passed and only "ovs_vlan_test 9000" failed, please check if you have set mtu to 9216 in switch.
hi Raghav, looking at the logs, we noticed: 07:52:36[DEBUG ][dutSh.10.13.241.98]: STDOUT: >>ovs-vswitchd (Open vSwitch) 2.10.0 DPDK 17.11.4 probably the test was done using a brew build of openvswitch that included the fix for IOVA VA mode (bz1645523). Since RHEL8 will be using openvswitch2.11 (and dpdk 18.11), can you please provide results for the PVP using an official RPM (e.g. the one released with RHEA-2019:40489-02 https://errata.devel.redhat.com/advisory/40366)? thanks you in advance! -- davide
Created attachment 1576921 [details] PVP Results for OpenvSwitch 2.11 with DPDK datapath PVP Results for OpenvSwitch 2.11 with DPDK datapath
(In reply to qding from comment #18) > (In reply to raghavendrachari.kamsali from comment #17) > > Hi, > > > > I followed the above comment & rerun the test , but same isse happened , > > test hangs at ovs_vlan_test 9000 . > > if ovs_vlan_test passed and only "ovs_vlan_test 9000" failed, please check > if you have set mtu to 9216 in switch. hello Qi Jun Ding / Christian, I tried this on netdev84 / 85, the MTU to 9216 on the Virtual Chassis, but the following command # ping 192.0.2.255 -b -c1 -Mdo -s$SZ -I enp5s0f0np0 it's possible to see forwarded packets only when $SZ is less or equal to 1490. Do we have a command reference for srtting up VSPERF on Virtual Chassis? thanks a lot! -- davide
(In reply to Davide Caratti from comment #24) > (In reply to qding from comment #18) > > (In reply to raghavendrachari.kamsali from comment #17) > Do we have a command reference for srtting up VSPERF on Virtual Chassis? (eraly shot) the question is: do we have a command reference for preconfiguring the Virtual Chassis with the Functional Testsuite? thanks! -- davide
(In reply to Davide Caratti from comment #25) > (In reply to Davide Caratti from comment #24) > > (In reply to qding from comment #18) > > > (In reply to raghavendrachari.kamsali from comment #17) > > Do we have a command reference for srtting up VSPERF on Virtual Chassis? > > (eraly shot) the question is: do we have a command reference for > preconfiguring the Virtual Chassis with the Functional Testsuite? > You're talking Virtual Chassis for JunOS, right? No preconfiguration for it.
Created attachment 1580589 [details] server results
Created attachment 1580590 [details] client results
Created attachment 1599991 [details] PVP Results for Open vSwitch with DPDK for ovs2.11
(In reply to raghavendrachari.kamsali from comment #29) > Created attachment 1599991 [details] > PVP Results for Open vSwitch with DPDK for ovs2.11 apparently the test was interrupted before running the 10-hours batch, both for L2 and L3 cases. Looking at the logs, I see this: 13:29:53[DEBUG ][dutSh.10.13.241.98]: STDOUT: >>EAL: Probing VFIO support... EAL: VFIO support initialized EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles ! EAL: PCI device 0000:00:02.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 1af4:1000 net_virtio EAL: using IOMMU type 8 (No-IOMMU) EAL: Ignore mapping IO port bar(0) PANIC in main(): Empty set of forwarding logical cores - check the core mask supplied in the command parameters 5: [testpmd(_start+0x2e) [0x42f48e]] 4: [/lib64/libc.so.6(__libc_start_main+0xf3) [0x7f690b250813]] 3: [testpmd() [0x42e6c8]] 2: [/lib64/librte_eal.so.9(__rte_panic+0xc1) [0x7f690c456f37]] 1: [/lib64/librte_eal.so.9(rte_dump_stack+0x32) [0x7f690c463752]] <<END 13:29:53[DEBUG ][dutSh.10.13.241.98]: STDERR: >>Warning: Permanently added '192.168.122.210' (ECDSA) to the list of known hosts. EAL: Detected 4 lcore(s) EAL: Detected 1 NUMA nodes EAL: RTE Version: 'DPDK 18.11.0' EAL: Multi-process socket /var/run/dpdk/rte/mp_socket <<END 13:29:53[INFO ][script]: - Get OpenFlow and DataPath port numbers.. so it seems that testpmd is doing segmentation fault in the guest (probably because of wrong CPU pinning?)
Now Provided cpu cores on same numa node on which interface installed.