hey below is my setup for running oftest

oftest on VM(10.0.1.2) - interface - veth1,veth3,veth5,veth7

Switch under test is on host machine of VM(10.0.1.1) -
#ovs-ofctl show br0
veth0 index=1
veth2 index=2
veth4 index=4
veth6 index=6



remote.py on VM has following map=
{1:veth1
2:veth3
3:veth5
4:veth7
}
}

command on switch(Host machine-10.0.1.1)
#ovs-vsctl set-controller tcp:10.0.1.2:6633

now am running command from VM(10.0.1.2)
sudo ./oftest --platform=remote -H 10.0.1.2 -p 6633 --test-spec=ExactMatch

and am getting following error

16:40:01  controller: DEBUG   : Enqueuing pkt type OFPT_BARRIER_REPLY
16:40:01  pkt_act   : DEBUG   : Send packet: 1 to 2
16:40:01  dataplane : DEBUG   : Sending 100 bytes to port 1
16:40:02  dataplane : DEBUG   : Poll time out, no packet from 2
16:40:02  pkt_act   : ERROR   : ERROR: No packet received from 2
16:40:02  basic     : ERROR   : ** FAILED ASSERTION: Did not receive
packet port 2
16:40:02  basic     : INFO    : Teardown for simple dataplane test
16:40:02  basic     : INFO    : ** END TEST CASE runTest (pktact.ExactMatch)

What port mapping i need to use to run oftest on following setup.
Please let me know how can i run oftest from a VM to host machine switch.
Note: VM is running on same Host machine

On Wed, May 23, 2012 at 9:52 PM, Dan Talayco <dan.tala...@bigswitch.com> wrote:
>
> Assuming you're using veth interfaces to connect the parts together, you 
> should use local.py (which doesn't really do anything in the default case).  
> See the references to veth in oftest/tests/oft; you may need to use 
> --base-if-index.
>
> -Dan
>
>
> On Wed, May 23, 2012 at 1:11 AM, sonny sonny <sonny...@gmail.com> wrote:
>>
>> Hi,
>>
>> I am running OVS(software switch) on my host 10.0.15.1 (Linux ) and
>> oftest is run on virtual machine 10.0.15.2 (Ubuntu 10.0.4) on same
>> host.
>>
>> So should  I run oftest using local.py or remote.py ?
>>
>> If I use remote.py then how to map the ports between software switch
>> and VM(oftest).
>>
>> regards
>> sony
>> _______________________________________________
>> openflow-discuss mailing list
>> openflow-discuss@lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
>
_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss

Reply via email to