Re: [ovs-discuss] can I ping an OVS switch?

[Ashish Varma]

For every bridge created using ovs-vsctl command (ovs-vsctl add-br
), an internal port with the name same as  gets
created.
You can set the ip address of this interface on the host running mininet.

e.g. just running "sudo mn" creates a switch s1 and hosts h1 and h2 with h1
ip 10.0.0.1 and h2 with ip 10.0.0.2

On the mininet host:
sudo ifconfig s1 10.0.0.100/24 up (make sure the ip does not conflict
with any other physical ip on the host machine)

>From mininet prompt:
mininet> h1 ping 10.0.0.100




On Fri, Apr 27, 2018 at 8:27 AM, Haitham Ghalwash 
wrote:

> Hi,
>
> I am creating a mininet topology with open-flow switches. can I use xterm
> of a mininet host to ping a certain switch in the topology?
>
> How to set the IP for that switch?
>
>
> *Best wishes,*
>
> Haitham Ghalwash
>
>
>
>
>
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVN Database sizes - Auto compact feature

[Daniel Alvarez Sanchez]

Hi Ben,
After [0] got merged the compaction code is not there anymore. How is this
being done
now? Also, can we get the backport of [1][2] to 2.9 branch?

[0]
https://github.com/openvswitch/ovs/commit/1b1d2e6daa563cc91f974ffdc082fb3a8b424801
[1]
https://github.com/openvswitch/ovs/commit/1cfdc175ab1ecbc8f5d22f78d8e5f4344d55c5dc#diff-62fba9ea73e44f70aa9f56228bd4658c
[2]
https://github.com/openvswitch/ovs/commit/69f453713459c60e5619174186f94a0975891580

On Thu, Mar 8, 2018 at 11:21 PM, Daniel Alvarez Sanchez  wrote:

> Ok, I've just sent a patch and if you're not convinced we can
> just do the 2x change. Thanks a lot!
> Daniel
>
> On Thu, Mar 8, 2018 at 10:19 PM, Ben Pfaff  wrote:
>
>> I guess I wouldn't object.
>>
>> On Thu, Mar 08, 2018 at 10:11:11PM +0100, Daniel Alvarez Sanchez wrote:
>> > Thanks Ben and Mark. I'd be okay with 2x.
>> > Don't you think that apart from that it can still be good to compact
>> after
>> > a
>> > certain amount of time (like 1 day) if the number of transactions is > 0
>> > regardless of the size?
>> >
>> > On Thu, Mar 8, 2018 at 10:00 PM, Ben Pfaff  wrote:
>> >
>> > > It would be trivial to change 4x to 2x.  4x was just the suggestion in
>> > > the Raft thesis.  If 2x would make everyone a little more comfortable,
>> > > let's make that change.
>> > >
>>
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] could not add network device ovn-xxxxxx-0 to ofproto (Address family not supported by protocol)

[Paul Greenberg]

When IPv6 is disables in `/boot/grub2/grub.cfg`:

```
linux16 ... ipv6.disable=1
```

Then GENEVE interface does not come up properly.

```
# ovs-vsctl show
Port "ovn-14a54f-0"
Interface "ovn-14a54f-0"
type: geneve
options: {csum="true", key=flow, remote_ip="10.10.10.10"}
error: "could not add network device ovn-14a54f-0 to ofproto 
(Address family not supported by protocol)"
```

Additionally, run the following commands:

```
# cat /proc/version
Linux version 3.10.0-514.21.1.el7.x86_64 
(mockbu...@x86-020.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red 
Hat 4.8.5-11) (GCC) ) #1 SMP Sat Apr 22 02:41:35 EDT 2017

# ovs-vswitchd --version
ovs-vswitchd (Open vSwitch) 2.9.0
```

When IPv6 is enabled, then OVN works properly.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] how to let ovs kernel supports metering

[ali fahmy via discuss]

Hi,

I am working on ovs-kernel 2.8.0 with mininet and I would like to stay with
kernel version of OVS and not going to the userspace as ovs-userspace has
some performance issues, although it supports the metering feature.

Therefore I would like to ask how can I let ovs-kernel to support metering
feature? or other way to let support it in a away of tc in linux and
ovs-kernel?

Thanks
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] NSH related questions

[Ashish Varma]

Appreciate your response to the questions Yi Yang. These are very helpful.

Would definitely going to try the ODL SFC demo as shown below (and maybe more 
queries around this..)


-Ashish



From: Yang, Yi Y 
Sent: Tuesday, April 24, 2018 5:52:11 PM
To: Ashish Varma; ovs-discuss@openvswitch.org; jan.scheur...@ericsson.com
Cc: Brady Johnson; Justin Pettit; Pierluigi Rolando; Raju Koganty; Kantesh 
Mundaragi; Niaz Khan
Subject: RE: NSH related questions


Also cc Brady Johnson who is Opendaylight SFC project lead, he can add more 
comments about your questions.



From: Yang, Yi Y
Sent: Wednesday, April 25, 2018 8:45 AM
To: 'Ashish Varma' ; ovs-discuss@openvswitch.org; 
jan.scheur...@ericsson.com
Cc: Justin Pettit ; Pierluigi Rolando 
; Raju Koganty ; Kantesh Mundaragi 
; Niaz Khan 
Subject: RE: NSH related questions



Sorry for late response, I’m busy doing other thing, so don’t check ovs mailing 
list. Replies inline.



From: Ashish Varma [mailto:ava...@vmware.com]
Sent: Tuesday, April 17, 2018 3:28 AM
To: ovs-discuss@openvswitch.org; 
jan.scheur...@ericsson.com; Yang, Yi Y 
>
Cc: Justin Pettit >; Pierluigi 
Rolando >; Raju Koganty 
>; Kantesh Mundaragi 
>; Niaz Khan 
>
Subject: NSH related questions



Hi Jan / Yi Yang,



We, at VMware, are working on integrating partner services on NSX using NSH 
support on OVS. It would be very helpful to understand the current NSH/SFC 
adaptation trend and deployment scenarios happening in the industry.

Regarding this, we have few questions and it would be very helpful to get any 
insight on these:



1. When the classifier classifies a packet (stream) to follow a particular 
Service Function Path, the path may consist of going to multiple Service 
Function Forwarders (e.g. to cover all the Service Functions which may be 
spread across the network or data center) The last SFF could be far from the 
classifier (assuming there is only one in this SFP) where the NSH header was 
added to the original packet.

How do packets generally go back on its original path? Are they sent back to 
the original classifier or there are cases where you see last SFF intelligent 
enough to know the next hop of the packet outside the SFC overlay?



[Yi] In Opendaylight SFC, we have ingress classifier and egress classifier for 
end-to-end traffic, we have two SFPs (called RSP rendered service path in ODL 
sfc) for an end-to-end traffic, a forward RSP, a reverse RSP, usually they are 
symmetric, it is also if they are asymmetric. We also have some tricky way to 
avoid egress classifier by openflow rules, in that case, NSH metadata (C1 to C4 
will save reverse SFP ID and original classifier source IP). Maybe written 
explanation is not enough to you, you can try Opendaylight SFC 103 and 104 demo 
(https://git.opendaylight.org/gerrit/gitweb?p=sfc.git;a=tree;f=sfc-demo;h=d8ff2d575b8eedb5e42b9696d9869303bad0be95;hb=HEAD
 ), you can dump flow tables once you run it successfully, those tables can 
help you understand how the traffic is steered to correct classifier and 
forwarders.



2. In your experience, have you seen SFC being deployed on an existing overlay 
network. e.g SFC on top of OVN where now there is an SFC overlay network over 
tunnel based OVN overlay network. Have you encountered any challenges with 
this? (e.g. increase in packet size)



[Yi] In China, Sangfor (an information security product vendor) is developing a 
product for security resources pool by using sfc to go through security 
services in resource pool, this is very typical solution in cloud environment, 
some other vendors are also doing similar thing.



3. Are there any third party Virtual Network Functions which are NSH/SFC 
compliant?



[Yi] F5 has such VNF, but I’m not sure how it handles NSH.



4. SFC proxy is supposed to de-capsulate the NSH header when sending the packet 
to Service Function and encapsulate NSH header back when sending back to SFF. 
The NSH header information (SPI/SI, context headers etc.) needs to be put back 
on the packet when going back to SFF. If this is to be done using OVS flows 
(without sending the