Hide Forgot
Description of problem: Using 4.1-20161031 testkit version to test NIC that will be failed because “Error: could not bounce interface Version-Release number of selected component (if applicable): 4.1-20161031 How reproducible: Steps to Reproduce: 1. Install RHEL 7.3. 2. Install Testkit 3. Run NIC Test Actual results: Shutting down interface enp53s0f1 interface enp53s0f1 is down Bringing up interface enp53s0f1 ifup enp53s0f1 returned 0 Interface enp53s0f1 is UP Checking via ping to 192.168.0.118... Error: could not ping test server 192.168.0.118 Error: could not bounce interface enp53s0f1 Expected results: Additional info:
Please ssh into the SUT and try these commands, letting us know the results: ifdown enp53s0f1 ifup enp53s0f1 ping -I enp53s0f1 -Ac1 192.168.0.118
Please see the attachment.
Created attachment 1230676 [details] Ping -I enp53s0f1 -Ac1 192.168.0.118
[root@ele732016 Desktop]# ping -I enp53s0f1 -Ac1 192.168.0.118 PING 192.168.0.118 (192.168.0.118) from 192.168.0.142 enp53s0f1: 56(84) bytes of data. --- 192.168.0.118 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms Above is the problem. Try this. ssh into SUT, see what the ip address for enp53s0f1 is, go into the LTS web ui, remove any SUT associated, add that ip address you found for enp53s0f1, and run the ethernet test you tried to run on it.
Hi Brose, We could get passed result with following network environment. SUT Port1 connect to TestServer Port1 directly(Without any network device). And following this configuration to test each port.