[ovs-discuss] dpif(handler_85)|WARN|system at ovs-system: failed to put[create][modify] (Invalid argument)

Arun Sharma arun.sharma at calsoftinc.com
Fri Apr 11 11:51:40 UTC 2014


Hello,

I was trying to use mininet using source build OVS (from master) + pox
controller. Found ovs-dpctl command does not return any output when node 1
tries to ping node 2.

deb7:~/work$ sudo ovs-dpctl show
system at ovs-system:
lookups: hit:0 missed:4776 lost:0
flows: 0
port 0: ovs-system (internal)
port 1: s1 (internal)
port 2: s1-eth1
port 3: s1-eth2
deb7:~/work$ 
deb7:~/work$ sudo ovs-dpctl dump-flows
<<<< No output here >>>>>
deb7:~/work$ 

After analysing found below errors in switched log.

2014-04-11T11:33:23.166Z|00056|ofproto_dpif|INFO|system at ovs-system: MPLS
label stack length probed as 0
2014-04-11T11:33:23.170Z|00057|bridge|INFO|bridge s1: added interface s1 on
port 65534
2014-04-11T11:33:23.171Z|00058|bridge|INFO|bridge s1: using datapath ID
0000362786ce1742
2014-04-11T11:33:23.171Z|00059|connmgr|INFO|s1: added service controller
"punix:/usr/local/var/run/openvswitch/s1.mgmt"
2014-04-11T11:33:23.183Z|00060|bridge|INFO|bridge s1: using datapath ID
0000000000000001
2014-04-11T11:33:23.205Z|00061|bridge|INFO|bridge s1: added interface
s1-eth1 on port 1
2014-04-11T11:33:23.223Z|00062|bridge|INFO|bridge s1: added interface
s1-eth2 on port 2
2014-04-11T11:33:23.243Z|00063|connmgr|INFO|s1: added primary controller
"tcp:127.0.0.1:6633"
2014-04-11T11:33:23.243Z|00064|rconn|INFO|s1<->tcp:127.0.0.1:6633:
connecting...
2014-04-11T11:33:23.243Z|00065|connmgr|INFO|s1: added service controller
"ptcp:6634"
2014-04-11T11:33:23.253Z|00066|rconn|INFO|s1<->tcp:127.0.0.1:6633: connected
2014-04-11T11:33:23.295Z|00067|ofp_util|INFO|normalization changed
ofp_match, details:
2014-04-11T11:33:23.295Z|00068|ofp_util|INFO| pre:
nw_src=0.0.0.0,nw_dst=0.0.0.0,nw_proto=0,nw_tos=0,tp_src=0,tp_dst=0
2014-04-11T11:33:23.295Z|00069|ofp_util|INFO|post:
2014-04-11T11:33:23.478Z|00001|dpif(handler_85)|WARN|system at ovs-system:
failed to put[create][modify] (Invalid argument)
in_port(2),eth(src=7a:91:db:bb:2a:59/00:00:00:00:00:00,dst=33:33:ff:bb:2a:59
/00:00:00:00:00:00),eth_type(0x86dd),ipv6(src=::/::,dst=ff02::1:ffbb:2a59/::
,label=0/0,proto=58/0,tclass=0/0,hlimit=255/0,frag=no/0xff),icmpv6(type=135/
0,code=0/0),nd(target=fe80::7891:dbff:febb:2a59/::),
actions:userspace(pid=4294962942,slow_path(controller))


What is wrong?


--Other details --

arun at deb7:~/work$ sudo mn --controller remote,ip=127.0.0.1
*** Creating network
*** Adding controller
*** Adding hosts:
h1 h2 
*** Adding switches:
s1 
*** Adding links:
(h1, s1) (h2, s1) 
*** Configuring hosts
h1 h2 
*** Starting controller
*** Starting 1 switches
s1 
*** Starting CLI:
mininet> h1 ping h2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_req=1 ttl=64 time=134 ms
64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.900 ms
ŠŠ..
ŠŠ..
ŠŠ..



deb7:~/work/openvswitch$ ps -ef | grep ovs
root     11848     1  0 16:19 ?        00:00:00 ./ovsdb/ovsdb-server
/usr/local/etc/openvswitch/conf.db
--remote=punix:/usr/local/var/run/openvswitch/db.sock
--remote=db:Open_vSwitch,Open_vSwitch,manager_options
--private-key=db:Open_vSwitch,SSL,private_key
--certificate=db:Open_vSwitch,SSL,certificate
--bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert --pidfile --detach
-vfile:dbg --log-file=/usr/local/var/log/openvswitch/ovsdb-server.log
root     11856     1  0 16:19 ?        00:00:07 ./vswitchd/ovs-vswitchd
--pidfile --detach 
--log-file=/usr/local/var/log/openvswitch/ovs-vswitchd.log
deb7:~/work/openvswitch$
deb7:~/work/openvswitch$ ps -ef | grep pox
arun     14211 22963  0 17:03 pts/4    00:00:02 python2.7 -u ./pox.py
forwarding.l2_learning
arun     14508 22652  0 17:18 pts/3    00:00:00 grep pox

deb7:~/work/openvswitch$ netstat -na | grep 6633
tcp        0      0 0.0.0.0:6633            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:6633          127.0.0.1:56440
ESTABLISHED
tcp        0      0 127.0.0.1:56440         127.0.0.1:6633
ESTABLISHED

deb7:~/work/openvswitch$ sudo lsmod | grep open
openvswitch            62685  0
gre                    12531  1 openvswitch

deb7:~/work/openvswitch$ sudo ovs-vsctl list bridge
_uuid               : ce862735-19d2-4217-812b-696687459b23
controller          : [0e12708f-f98b-4bc8-a623-a1d400fd0d41,
4822855d-e210-4c29-a468-a1f366b4446d]
datapath_id         : "0000000000000001"
datapath_type       : ""
external_ids        : {}
fail_mode           : secure
flood_vlans         : []
flow_tables         : {}
ipfix               : []
mirrors             : []
name                : "s1"
netflow             : []
other_config        : {datapath-id="0000000000000001",
disable-in-band="true"}
ports               : [aeef1ca3-d7c7-46d4-8fb8-f14314ce5f36,
d97370ee-8f78-45b9-82fc-8324e3708377, f5d2653d-71d6-4476-b8a8-67081c8d51be]
protocols           : []
sflow               : []
status              : {}
stp_enable          : false


deb7:~/work/openvswitch$ sudo ovs-vsctl list controller
_uuid               : 4822855d-e210-4c29-a468-a1f366b4446d
connection_mode     : []
controller_burst_limit: []
controller_rate_limit: []
enable_async_messages: []
external_ids        : {}
inactivity_probe    : []
is_connected        : false
local_gateway       : []
local_ip            : []
local_netmask       : []
max_backoff         : 1000
other_config        : {}
role                : []
status              : {}
target              : "ptcp:6634"

_uuid               : 0e12708f-f98b-4bc8-a623-a1d400fd0d41
connection_mode     : []
controller_burst_limit: []
controller_rate_limit: []
enable_async_messages: []
external_ids        : {}
inactivity_probe    : []
is_connected        : true
local_gateway       : []
local_ip            : []
local_netmask       : []
max_backoff         : 1000
other_config        : {}
role                : other
status              : {sec_since_connect="1042", state=ACTIVE}
target              : "tcp:127.0.0.1:6633"


~~ Arun


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140411/02c2f513/attachment-0002.html>


More information about the discuss mailing list