You need to give the entire command in one line, e.g. sudo ovs-vsctl -- --id=@sflow create sflow agent=eth0 target=\"127.0.0.1:6343\" sampling=10 polling=20 -- -- set bridge s1 sflow=@sflow
or, if you have multiple bridges: sudo ovs-vsctl -- \ --id=@sflow create sflow agent=eth0 target=\"127.0.0.1:6343\" \ sampling=10 polling=20 -- \ -- set bridge s1 sflow=@sflow \ -- set bridge s2 sflow=@sflow \ -- set bridge s3 sflow=@sflow \ -- set bridge s4 sflow=@sflow I have just started playing around with sFlow on Mininet as well, you might find the following article useful: http://blog.sflow.com/2013/05/controlling-large-flows-with-openflow.html The article includes a script that maps sFlow agent and ifIndex numbers to OpenFlow dpid and ports - important if you want to tie the metrics to your OpenFlow policies. Peter On May 30, 2013, at 3:54 PM, mehmet fatih Aktaş <mfatihak...@gmail.com> wrote: > Hi, > > I am trying to use sFlow on ovs created in mininet. > Following the config cookbook for sFlow in: > http://openvswitch.org/support/config-cookbooks/sflow/ > > Here is the bridge log for ovs:s1 > -------------------------------------------------------------------------------------------- > _uuid : f0010812-fddb-4def-ae7d-6978ce3a4fb4 > controller : [10857ad2-36f5-4000-b865-9b281df6d718, > 1e1f2796-f91d-476a-b9ad-b1e71dc42e71] > datapath_id : "0000000000000001" > datapath_type : "" > external_ids : {} > fail_mode : secure > flood_vlans : [] > mirrors : [] > name : "s1" > netflow : [] > other_config : {datapath-id="0000000000000001"} > ports : [1b470cfd-cfde-42c6-85af-a7e88c9e21d1, > 71716454-c596-47df-ab31-363b31f94cec, 9c7e06a4-cd46-48d3-acd2-2f1a973a135c, > c9119ac7-05da-4682-9f6f-b56efffb751c, c9470155-f4c9-4504-9038-8c13775023ae, > e38f5087-94c7-4772-82d0-fc332ddca6dc] > sflow : [] > status : {} > stp_enable : false > -------------------------------------------------------------------------------------- > When I typed the command: > > sudo ovs-vsctl -- --id=@s create sFlow agent=s1-eth1 > > target=\"192.168.56.1:6343\" header=128 sampling=64 polling=10 > > It is giving the warning: > > May 30 15:46:48|00002|vsctl|WARN|row id "@s" was created but no reference > > to it was inserted, so it will not actually appear in the database > 2000e1bf-5af4-40b1-8fcd-ca382f550a5a > > and then if I continued by typing the command: > > sudo ovs-vsctl set bridge s1 sflow=@s > giving the error: > > ovs-vsctl: row id "@s" is referenced but never created (e.g. with "-- > > --id=@s create ...") > > I tried to workaround this by reading almost every related entry in the > discuss list of ovs and mininet but no solution found yet. Any help would be > very appreciated. > > Thanks. > > Mehmet Fatih Aktas > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
