Hi Dan,

My host is HP proliant with linux 2.6 running on it .
I will also look into OVS soon.

Also , I had a question regarding the version of oftest that had
test-cases called *FLOWS010 ( switch returning an error message for a
badport reference ) , FLOWS008 ( Verifying hardtime out ) , CTRLR001
..etc.*I cant find this version of oftest anywhere on github now. And
the updates
versions don't have these test-cases any more.
Does anyone have a copy of it on their local machines or know where can
they be found ?



Thanks,
Shreya


On Tue, Jun 26, 2012 at 12:03 AM, Dan Talayco <dan.tala...@bigswitch.com>wrote:

> As Zoltan pointed you, you should not use --platform=remote.  In fact with
> your veth settings you shouldn't need to specify --platform at all.
>
> Can you tell us a little more about your host?  What version of Linux, etc?
>
> You might have more luck running against OVS than the Stanford reference
> design.  Have you tried that?
>
> -Dan
>
>
> On Mon, Jun 25, 2012 at 11:08 AM, shreya pandita <shreya.pand...@gmail.com
> > wrote:
>
>> I made sure I killed the applications running on the port 6633 . It would
>> still give me this error after running certain 2 -3 tests .
>> Also, do I need to make changes to the remote.py?
>>
>>
>>
>> On Mon, Jun 25, 2012 at 2:05 PM, Zoltán Lajos Kis <
>> zoltan.lajos....@ericsson.com> wrote:
>>
>>> Hi,
>>>
>>> Address already used suggests that you have some application running,
>>> which already listens on port 6633 (e.g. NOX).
>>> You could also try using --platform=local instead of setting remote plus
>>> the host and port.
>>>
>>> Regards,
>>> Zoltan.
>>>
>>> ________________________________________
>>> From: openflow-discuss-boun...@lists.stanford.edu [
>>> openflow-discuss-boun...@lists.stanford.edu] On Behalf Of shreya
>>> pandita [shreya.pand...@gmail.com]
>>> Sent: Monday, June 25, 2012 8:00 PM
>>> To: openflow-discuss@lists.stanford.edu
>>> Subject: [openflow-discuss] Reference switch issues.
>>>
>>> Hie All,
>>>
>>> I am running the oftest against the reference switch. I face some
>>> troubles . If I run the tests at once, I see address already in use error .
>>> If I run them separately , they are fine . But so many basic tests are
>>> failing , which I think is not good.
>>>
>>> Do I need to make any changes to the port-mapping in the remote.py ???
>>>
>>> [root@dev2 tests]# ./run_switch.py
>>> Creating veth pair 0
>>> Creating veth pair 1
>>> Creating veth pair 2
>>> Creating veth pair 3
>>> Cmd: ['/sbin/ifconfig', 'veth0', '192.168.10.1', 'netmask',
>>> '255.255.255.0']
>>> Cmd: ['/sbin/ifconfig', 'veth1', '192.168.11.1', 'netmask',
>>> '255.255.255.0']
>>> Cmd: ['/sbin/ifconfig', 'veth2', '192.168.12.1', 'netmask',
>>> '255.255.255.0']
>>> Cmd: ['/sbin/ifconfig', 'veth3', '192.168.13.1', 'netmask',
>>> '255.255.255.0']
>>> Cmd: ['/sbin/ifconfig', 'veth4', '192.168.14.1', 'netmask',
>>> '255.255.255.0']
>>> Cmd: ['/sbin/ifconfig', 'veth5', '192.168.15.1', 'netmask',
>>> '255.255.255.0']
>>> Cmd: ['/sbin/ifconfig', 'veth6', '192.168.16.1', 'netmask',
>>> '255.255.255.0']
>>> Cmd: ['/sbin/ifconfig', 'veth7', '192.168.17.1', 'netmask',
>>> '255.255.255.0']
>>> ../../openflow/udatapath/ofdatapath
>>> ../../openflow/secchan/ofprotocol
>>> Starting ofprotocol in 2 seconds; ^C to quit
>>> Started ofdatapath on IFs veth0,veth2,veth4,veth6 with pid 11599
>>> Jun 25 17:09:32|00001|secchan|INFO|OpenFlow reference implementation
>>> version 1.0.0
>>> Jun 25 17:09:32|00002|secchan|INFO|OpenFlow protocol version 0x01
>>> Jun 25 17:09:32|00003|secchan|WARN|new management connection will
>>> receive asynchronous messages
>>> Jun 25 17:09:32|00004|rconn|INFO|unix:/tmp/ofd: connecting...
>>> Jun 25 17:09:32|00005|rconn|INFO|tcp:127.0.0.1:6633<
>>> http://127.0.0.1:6633>: connecting...
>>> Jun 25 17:09:32|00001|datapath|ERR|veth0 device has assigned IP address
>>> 192.168.10.1
>>> Jun 25 17:09:32|00002|datapath|ERR|veth0 device has assigned IPv6
>>> address fe80::e087:1eff:feef:f050
>>> Jun 25 17:09:32|00003|datapath|ERR|veth2 device has assigned IP address
>>> 192.168.12.1
>>> Jun 25 17:09:32|00004|datapath|ERR|veth2 device has assigned IPv6
>>> address fe80::30f5:5dff:fe36:6814
>>> Jun 25 17:09:32|00005|datapath|ERR|veth4 device has assigned IP address
>>> 192.168.14.1
>>> Jun 25 17:09:32|00006|datapath|ERR|veth4 device has assigned IPv6
>>> address fe80::70fc:25ff:fef4:f11f
>>> Jun 25 17:09:32|00007|datapath|ERR|veth6 device has assigned IP address
>>> 192.168.16.1
>>> Jun 25 17:09:32|00008|datapath|ERR|veth6 device has assigned IPv6
>>> address fe80::c4d1:5bff:fef3:ed8e
>>> Jun 25 17:09:32|00006|rconn|INFO|unix:/tmp/ofd: connected
>>> Jun 25 17:09:32|00007|port_watcher|INFO|Datapath id is 00232086c636
>>> Jun 25 17:09:32|00008|port_watcher|INFO|Identified data path local port
>>> as "tap2".
>>> Jun 25 17:09:33|00009|rconn|INFO|tcp:127.0.0.1:6633<
>>> http://127.0.0.1:6633>: connection timed out
>>> Jun 25 17:09:33|00010|rconn|INFO|tcp:127.0.0.1:6633<
>>> http://127.0.0.1:6633>: connection dropped
>>> Jun 25 17:09:33|00011|rconn|INFO|tcp:127.0.0.1:6633<
>>> http://127.0.0.1:6633>: waiting 1 seconds before reconnect
>>>
>>>
>>> [root@dev2 tests]# ./oft --platform=remote --host=127.0.0.1 --port=6633
>>> --verbose --test-spec=basic
>>> WARNING: No route found for IPv6 destination :: (no default route?)
>>> runTest (basic.DataPlaneOnly) ... ok
>>> runTest (basic.DescStatsGet) ... Controller startup failed (no switch
>>> addr); exiting
>>> ERROR
>>> runTest (basic.Echo) ... Exception in thread Thread-6:
>>> Traceback (most recent call last):
>>>  File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
>>>    self.run()
>>>  File "build/bdist.linux-x86_64/egg/oftest/controller.py", line 389, in
>>> run
>>>    self.listen_socket.bind((self.host, self.port))
>>>  File "<string>", line 1, in bind
>>> error: [Errno 98] Address already in use
>>>
>>>
>>>
>>>
>>> --
>>> warm regards,
>>>
>>> Shreya Pandita
>>>
>>>
>>>
>>
>> _______________________________________________
>> 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