[ovs-discuss] OVS 2.9.0: priority=0 actions=CONTROLLER flow counts but doesn't output packets to the controller
Hello, Hoping I'm missing something obvious! I have a flow like this: $ grep CONTROLLER sab-dump-flows.log cookie=0x5adc15c0, duration=63.446s, table=3, n_packets=60, n_bytes=3436, priority=0 actions=CONTROLLER:96 I can cause packets to match it, but no packets are output ot the controller. faucet@faucet:/var/tmp/faucet-tests-1KL3eg/FaucetUntaggedTestZeroPriorityFlowsTest-test_untagged$ tshark -l -n -Q -d tcp.port==40649,openflow -O openflow_v4 -Y "openflow_v4.packet_in.total_len>0" -r fa*cap|wc -l 0 If I specify any priority other than 0, it works (packets are output to controller via packet in messages). Is there something special about priority=0 flows and the CONTROLLER action? Thanks, ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] The discrepancy in the Monitor request composition.
Hi,
The RFC7047 states below about the Monitor request.
The request object has the
following members:
o "method": "monitor"
o "params": [, , ]
o "id":
The parameter is used to match subsequent update
notifications (see below) to this request.
The object maps the name of the table to be monitored
to an array of objects. Each is an
object with the following members:
"columns": [*]optional
"select": optional
The columns, if present, define the columns within the table to be monitored.
is an object with the following members:
"initial": optional
"insert":optional
"delete":optional
"modify":optional
The contents of this object specify how the columns or table are to be
monitored,
as explained in more detail below.
However, when I look at some of the legitimate samples of the Monitor
requests, they are encoded as below.
{
"id": "c5c09c07-11c1-449b-8f04-016fefe15844",
"method": "monitor",
"params": [
"hardware_vtep",
"91c9eed4-00bb-48e3-b2d9-51e0364bbdc2",
{
"Physical_Locator": {
"columns": [
"dst_ip",
"encapsulation_type",
"_uuid"
],
"select": {
"initial": true,
"insert": true,
"delete": true,
"modify": true
}
},
"Physical_Locator_Set": {
"columns": [
"_uuid",
"locators"
],
"select": {
"initial": true,
"insert": true,
"delete": true,
"modify": true
}
}
}
]
}
If we go by the RFC encoding rules, "params" contains the
, which maps the "Table name" to an array of
object. So IMHO, the table names comes only once in the
message. Correct?
Also, it is explicitly mentioned that (as below) and it does NOT contain
the "Table name" in it.
Each is an
object with the following members:
"columns": [*]optional
"select": optional
However, in the message payload that I have, shows the tuple, which
contains "Table : Columns : Select". This list of constitute
the as per the RFC definition.
I see this as the discrepancy between the RFC definition and how the
message is actually sent by the controller.
Can you please review and confirm this discrepancy?
Thanks,
/anil.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] tap ports...
Can OVS create tap ports like OpenVPN or KVM (Qemu) or User Mode Linux use? I.e. an Ethernet interface inside OVS and a socket that applications can glom onto and use. I think I can create the tap interfaces manually (via tunctl or ip tuntap…) and then add them to a bridge. However I feel like this is unnecessary and may very well be something that OVS can do without the separate devices. Hence my question if OVS can create (internal) tap interfaces, much the same way that it can create (internal) vEth (like) interfaces. -- Grant. . . . unix || die smime.p7s Description: S/MIME Cryptographic Signature ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] openvswitch userspace mode can not use iperf send packet??whatever tcp and udp
ovs userspace mode how to install in centos7, datapath-type=netdev ??What does ??netdev?? stand for? as well as with the meter table relation ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] Fedora 27 Update Clobbers my Previous From-Source OpenvSwitch Install
When I successfully build openvswitch 2.5.4 on Fedora 27 server, Fedora then detects openvswitch and wants to apply a security update 2.8.1-1.fc27 to the 2.5.4 ovs. This update clobbers my openvswitch database and even after rebuilding db fresh, switches do not come up on reboot. [orabuntu@localhost anylinux]$ sudo dnf update Last metadata expiration check: 0:06:27 ago on Mon 05 Mar 2018 01:08:30 PM CST. Dependencies resolved. === Package Arch Version Repository Size === Upgrading: openvswitch x86_64 2.8.1-1.fc27 fedora 6.5 M Transaction Summary === Upgrade 1 Package Total download size: 6.5 M Is this ok [y/N]: N Operation aborted. [orabuntu@localhost anylinux]$ For now I am using a band-aid because I've not yet had time to code up an after-this-update fix. [orabuntu@localhost dnf]$ cat dnf.conf [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=True exclude=openvswitch* [orabuntu@localhost dnf]$ ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] openvswitch userspace iperf server can not receive packet
Can u run tcpdump on the iprf server to check if there are cksm error From: ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of ?? Sent: Monday, 05 March, 2018 10:05 AM To: ovs-discuss Subject: [ovs-discuss] openvswitch userspace iperf server can not receive packet ovs userspace mode, set datapath_type = netdev, virtual host ping normal, iperf server can not receive the udp or tcp packets received Has anyone encountered a similar problem? How to solve? ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] bond control syntax
Thank you, I’ll try it. On Mon, Mar 5, 2018 at 11:58 AM Ben Pfaff wrote: > On Sun, Mar 04, 2018 at 12:34:53PM -0500, Chris Boley wrote: > > Hi, > > I worked on this more and found that this worked. If anyone is actually > > interested. > > > > sudo touch /etc/network/if-up.d/vbond0_tune > > sudo nano /etc/network/if-up.d/vbond0_tune > > > > ##Pasted this in### > > > > ovs-vsctl set port vbond0 other_config:lacp-system-priority=50 > > other_config:bond-rebalance-interval=5000 other_config: > > bond-detect-mode=miimon other_config:bond-miimon-interval=100 > > other_config:bond_updelay=200 other_config:bond_downdelay=200 > > exit > > > > ##save file and exit## > > > > sudo chmod a+x /etc/network/if-up.d/vbond0_tune > > > > modify interfaces file to look this way: > > allow-vbridge0 vbond0 > > iface vbond0 inet manual > >ovs_bridge vbridge0 > >ovs_type OVSBond > >ovs_bonds eth1 eth2 > >ovs_options bond_mode=balance-slb lacp=active > >post-up /etc/network/if-up.d/vbond0_tune > > > > After that I could run: > > foo@VMHOST:~$ sudo ovs-vsctl list port vbond0 > > > > And I could see all the "other_options" > > > > The ovs-appctl bond/show vbond0 isn't really reflecting my up and down > > delay. I'm not sure though if that's because the Cisco Switch ports are > > taking priority or what's going on. > > bond_updelay and bond_downdelay are columns rather than keys within > other_config, so you should be able to just remove "other_config:" from > those settings to make them work. > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] mtu_request
Thanks!! I hadn’t found that in my searching. I appreciate that Ben. On Mon, Mar 5, 2018 at 12:05 PM Ben Pfaff wrote: > On Sat, Mar 03, 2018 at 08:32:17AM -0500, Chris Boley wrote: > > OVS: > > foo@VMHOST:~$ sudo ovs-vsctl show > > 126a4b57-4837-42a9-95d6-d818b35e95bd > >Bridge "vbridge0" > >Port "vnet0" > >tag: 2 > >Interface "vnet0" > >Port "vbond0" > >Interface "eth2" > >Interface "eth1" > >Port "vbridge0" > >Interface "vbridge0" > >type: internal > >ovs_version: "2.5.2" > > > > I've tried changing MTU parameters on my internal vbridge0 interface: > > > > sudo ovs-vsctl set interface vbridge0 mtu=1520 > > > > This command runs, but does nothing to the MTU of my internal bridge > > interface. > > > > There's supposed to be a separate command: > > ovs-vsctl set int vbridge0 mtu_request=1520 > > mtu_request was introduced in OVS 2.6.0 but you are using 2.5.2. > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] mtu_request
On Sat, Mar 03, 2018 at 08:32:17AM -0500, Chris Boley wrote: > OVS: > foo@VMHOST:~$ sudo ovs-vsctl show > 126a4b57-4837-42a9-95d6-d818b35e95bd >Bridge "vbridge0" >Port "vnet0" >tag: 2 >Interface "vnet0" >Port "vbond0" >Interface "eth2" >Interface "eth1" >Port "vbridge0" >Interface "vbridge0" >type: internal >ovs_version: "2.5.2" > > I've tried changing MTU parameters on my internal vbridge0 interface: > > sudo ovs-vsctl set interface vbridge0 mtu=1520 > > This command runs, but does nothing to the MTU of my internal bridge > interface. > > There's supposed to be a separate command: > ovs-vsctl set int vbridge0 mtu_request=1520 mtu_request was introduced in OVS 2.6.0 but you are using 2.5.2. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] bond control syntax
On Sun, Mar 04, 2018 at 12:34:53PM -0500, Chris Boley wrote: > Hi, > I worked on this more and found that this worked. If anyone is actually > interested. > > sudo touch /etc/network/if-up.d/vbond0_tune > sudo nano /etc/network/if-up.d/vbond0_tune > > ##Pasted this in### > > ovs-vsctl set port vbond0 other_config:lacp-system-priority=50 > other_config:bond-rebalance-interval=5000 other_config: > bond-detect-mode=miimon other_config:bond-miimon-interval=100 > other_config:bond_updelay=200 other_config:bond_downdelay=200 > exit > > ##save file and exit## > > sudo chmod a+x /etc/network/if-up.d/vbond0_tune > > modify interfaces file to look this way: > allow-vbridge0 vbond0 > iface vbond0 inet manual >ovs_bridge vbridge0 >ovs_type OVSBond >ovs_bonds eth1 eth2 >ovs_options bond_mode=balance-slb lacp=active >post-up /etc/network/if-up.d/vbond0_tune > > After that I could run: > foo@VMHOST:~$ sudo ovs-vsctl list port vbond0 > > And I could see all the "other_options" > > The ovs-appctl bond/show vbond0 isn't really reflecting my up and down > delay. I'm not sure though if that's because the Cisco Switch ports are > taking priority or what's going on. bond_updelay and bond_downdelay are columns rather than keys within other_config, so you should be able to just remove "other_config:" from those settings to make them work. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] ISSUE with IPERF in OVS - GRE Setup
Hi,
I am having the following topology with gre tunnel. Whenever I start iperf
with the BR1 IPs, I am 0 packets reaching the other side.
Topology
-
(10.0.0.10)BR1 BR0(192.168.1.10)-(phyical link)---(192.168.1.11)BR0
BR1(10.0.0.11)
OVS logs
-
192.168.1.11
-
# ovs-vsctl show
28ec0ec0-4d41-4ee0-a688-59363e990be2
Bridge "br1"
Port "gre1"
Interface "gre1"
type: gre
options: {remote_ip="192.168.1.10"}
Port "br1"
Interface "br1"
type: internal
Bridge "br0"
Port "br0"
Interface "br0"
type: internal
Port "eth2"
Interface "eth2"
ovs_version: "2.0.2"
# ovs-ofctl dump-ports br1
OFPST_PORT reply (xid=0x2): 2 ports
port 1: rx pkts=191, bytes=16192, drop=0, errs=0, frame=0, over=0, crc=0
tx pkts=324, bytes=218080, drop=0, errs=0, coll=0
port LOCAL: rx pkts=205, bytes=13834, drop=0, errs=0, frame=0, over=0,
crc=0
tx pkts=277, bytes=186885, drop=0, errs=0, coll=0
# ovs-ofctl dump-ports br0
OFPST_PORT reply (xid=0x2): 2 ports
port 1: rx pkts=1756592, bytes=2469177682, drop=0, errs=60, frame=0,
over=0, crc=0
tx pkts=2523136, bytes=3696929018, drop=0, errs=0, coll=0
port LOCAL: rx pkts=228910, bytes=2358163654, drop=0, errs=0, frame=0,
over=0, crc=0
tx pkts=146232, bytes=3529991526, drop=0, errs=0, coll=0
root@ubuntu:/home/sanctum#
192.168.1.10
-
# ovs-vsctl show
3e0b4065-425b-4f76-b0b9-00ff062ca2b1
Bridge "br1"
Port "br1"
Interface "br1"
type: internal
Port "gre1"
Interface "gre1"
type: gre
options: {remote_ip="192.168.1.11"}
Bridge "br0"
Port "eth2"
Interface "eth2"
Port "br0"
Interface "br0"
type: internal
ovs_version: "2.5.2"
# ovs-ofctl dump-ports br1
OFPST_PORT reply (xid=0x2): 2 ports
port LOCAL: rx pkts=218, bytes=72490, drop=0, errs=0, frame=0, over=0,
crc=0
tx pkts=217, bytes=18021, drop=0, errs=0, coll=0
port 2: rx pkts=247, bytes=20414, drop=0, errs=0, frame=0, over=0, crc=0
tx pkts=268, bytes=103812, drop=0, errs=0, coll=0
root@ubuntusoekris3:/home/sanctumsoekris3#
# ovs-ofctl dump-ports br0
OFPST_PORT reply (xid=0x2): 2 ports
port LOCAL: rx pkts=172401, bytes=2357681766, drop=0, errs=0, frame=0,
over=0, crc=0
tx pkts=229444, bytes=3535382058, drop=0, errs=0, coll=0
port 1: rx pkts=5355249, bytes=7469372659, drop=0, errs=70, frame=0,
over=0, crc=0
tx pkts=3193175, bytes=4052911200, drop=0, errs=0, coll=0
root@ubuntusoekris3:/home/sanctumsoekris3#
IPERF OUTPUT
=
Client-Side
-
# iperf3 -c 10.0.0.11
Connecting to host 10.0.0.11, port 5201
[ 4] local 10.0.0.10 port 51633 connected to 10.0.0.11 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 84.8 KBytes 694 Kbits/sec2 1.41
KBytes
[ 4] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec1 1.41 KBytes
[ 4] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec0 1.41 KBytes
[ 4] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec1 1.41 KBytes
[ 4] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec0 1.41 KBytes
[ 4] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec0 1.41 KBytes
[ 4] 6.00-7.00 sec 0.00 Bytes 0.00 bits/sec1 1.41 KBytes
[ 4] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec0 1.41 KBytes
[ 4] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec0 1.41 KBytes
[ 4] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec0 1.41 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 84.8 KBytes 69.5 Kbits/sec5 sender
[ 4] 0.00-10.00 sec 0.00 Bytes 0.00 bits/sec receiver
Server
---
# iperf3 -s
---
Server listening on 5201
---
Accepted connection from 10.0.0.10, port 51632
[ 5] local 10.0.0.11 port 5201 connected to 10.0.0.10 port 51633
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 6.00-7.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 10.00-10.03 sec 0.00 Bytes 0.00 bits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval
[ovs-discuss] openvswitch userspace iperf server can not receive packet
ovs userspace mode, set datapath_type = netdev, virtual host ping normal, iperf server can not receive the udp or tcp packets received Has anyone encountered a similar problem? How to solve?___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
