[ovs-discuss] need help with ovn
Hi. I need to setup simple test lab with ovn on two hosts. One host is gateway that have external ipv4 address and connected to upstream provider and the second host that have vm with two interfaces (libvirt created tap devices). I need to have one interfaces connected to external network (via gateway host) and autoassign it public ipv4 address via dhcp, and second interface connected to internal network (that can in feature have another vm). How can i do that via ovn commands?Thanks for any hint. -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] need help with ovn
On Sun, Nov 25, 2018 at 7:22 PM Vasiliy Tolstov wrote: > Hi. I need to setup simple test lab with ovn on two hosts. > One host is gateway that have external ipv4 address and connected to > upstream provider and the second host that have vm with two interfaces > (libvirt created tap devices). > I need to have one interfaces connected to external network (via > gateway host) and autoassign it public ipv4 address via dhcp, and > second interface connected to internal network (that can in feature > have another vm). > How can i do that via ovn commands?Thanks for any hint. > Hi Vasiliy, There are many resources which you can look into it. I would suggest a few - http://docs.openvswitch.org/en/latest/tutorials/ovn-openstack/ - Look into man pages of "ovn-*" - Look into ovn.at test file - https://github.com/openvswitch/ovs/blob/master/tests/ovn.at - This will give you the idea on how to use ovn commands - Few other external links - - http://blog.spinhirne.com/2016/09/a-primer-on-ovn.html - https://gist.github.com/russellb/4ab0a9641f12f8ac66fdd6822ee7789e - https://developers.redhat.com/blog/2018/09/03/ovn-dynamic-ip-address-management/ - https://developers.redhat.com/blog/2018/11/08/how-to-create-an-open-virtual-network-distributed-gateway-router/ Hope this helps. Thanks Numan > -- > Vasiliy Tolstov, > e-mail: v.tols...@selfip.ru > ___ > 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] need help with ovn
вс, 25 нояб. 2018 г. в 20:42, Numan Siddique : > > > Hi Vasiliy, > > There are many resources which you can look into it. > I would suggest a few > - http://docs.openvswitch.org/en/latest/tutorials/ovn-openstack/ > - Look into man pages of "ovn-*" > - Look into ovn.at test file - > https://github.com/openvswitch/ovs/blob/master/tests/ovn.at - This will give > you the idea on how to use ovn commands > - Few other external links - > - http://blog.spinhirne.com/2016/09/a-primer-on-ovn.html > - https://gist.github.com/russellb/4ab0a9641f12f8ac66fdd6822ee7789e > - > https://developers.redhat.com/blog/2018/09/03/ovn-dynamic-ip-address-management/ > - > https://developers.redhat.com/blog/2018/11/08/how-to-create-an-open-virtual-network-distributed-gateway-router/ > Thanks! I'm find some link to, but i need more like text description about in which cases i need to create logical router, what kinds of ports for which use-cases... But i'm try to read this additional links. -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Why PCP value is fixed to zero(0), how we can modify and generate different pcp valued packets
Thanks a lot. On Fri, Nov 23, 2018 at 8:22 PM Ben Pfaff wrote: > On Fri, Nov 23, 2018 at 10:43:30AM +0530, Vikas Kumar wrote: > > i had a doubt, why ovs has fixed the pcp value to zero(0), how i can > modify > > the pcp value? > > actually i wanted to generate packets based on different pcp values. > > > > it will be a great help if anyone suggest me any idea,how to modify the > pcp > > value of 802.1q header structure. > > Use the mod_vlan_pcp action. > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] 答复: A coredump cause by the race condition by handler、upcall and revalidation thread
Any ideas?Seemed like sevreral similar issures in earlier version, and several
patches fix them
发件人: Zhengjingzhou
发送时间: 2018年11月21日 19:02
收件人: 'ovs-discuss@openvswitch.org'
主题: A coredump cause by the race condition by handler、upcall and revalidation
thread
We've found a coredump in a daily testcase(ovs2.7.0+dpdk),
After a deep analyze we found it coredumped after a ovs service restart(with
birdges and ports), and the revalidator and upcall threads race at the
ukey_state. However ,it seems hard to reproduce the coredump.We conclude a
possiblity
1. handlerA deals the packet1, prepare to put a flow,wait(lock)
2. handlerB deals another packet2(same mac with packet1), find the device has
been deleted, generate a flow
3. handlerA meet a error(EEXIST, in function flow_put_on_pmd), prepare to
transition ukeystate to evicted(in function handle_upcalls), wait to aquire the
lock
for (i = 0; i < n_ops; i++) {
struct udpif_key *ukey = ops[i].ukey;
if (ukey) {
ovs_mutex_lock(&ukey->mutex);
if (ops[i].dop.error) {
transition_ukey(ukey, UKEY_EVICTED); ///doubt may be here
should add a state condition? as beflow
}
else if (ukey->state < UKEY_OPERATIONAL) {
transition_ukey(ukey, UKEY_OPERATIONAL);
}
4. revalidate thread C transitions the ukeystate to deleted(by expiration or
other deals), releases the ukey lock
5. handlerA accuires the ukey lock(step 3) ,finds the pre state is deleted,
abort
which the stack is
#0 0x7fba3737f417 in raise () from /usr/lib64/libc.so.6
#1 0x7fba37380b08 in abort () from /usr/lib64/libc.so.6
#2 0x005746be in ovs_abort_valist (err_no=err_no@entry=0,
format=format@entry=0x6b0028 "Invalid ukey transition %d->%d (last transitioned
from thread %u at %s)", args=args@entry=0x7fb995628ea0)
at lib/util.c:341
#3 0x0057b8b0 in vlog_abort_valist (function=,
line=, module_=,
message=0x6b0028 "Invalid ukey transition %d->%d (last transitioned from
thread %u at %s)", args=args@entry=0x7fb995628ea0) at lib/vlog.c:1229
#4 0x0057b93a in vlog_abort (function=function@entry=0x6b0d90
<__func__.28159> "transition_ukey_at", line=line@entry=1741,
module=module@entry=0x9ac220 ,
message=message@entry=0x6b0028 "Invalid ukey transition %d->%d (last
transitioned from thread %u at %s)") at lib/vlog.c:1243
#5 0x0049a85d in transition_ukey_at (ukey=ukey@entry=0x7fb97c005120,
dst=dst@entry=UKEY_EVICTED, where=where@entry=0x6b0648
"ofproto/ofproto_dpif_upcall.c:1467")
at ofproto/ofproto_dpif_upcall.c:1739
#6 0x0049da45 in handle_upcalls (n_upcalls=64, upcalls=0x7fb99564dc70,
udpif=) at ofproto/ofproto_dpif_upcall.c:1467
#7 recv_upcalls (handler=0x3339f90, handler=0x3339f90) at
ofproto/ofproto_dpif_upcall.c:887
#8 0x0049dc7a in udpif_upcall_handler (arg=0x3339f90) at
ofproto/ofproto_dpif_upcall.c:783
#9 0x00546e48 in ovsthread_wrapper (aux_=) at
lib/ovs_thread.c:682
#10 0x7fba38f97e45 in start_thread () from /usr/lib64/libpthread.so.0
#11 0x7fba37442afd in clone () from /usr/lib64/libc.so.6
and the relative log
2018-11-10T16:03:10.796061+08:00|warning|ovs-vswitchd[18219]|xlate_report_error[647]|1|ofproto_dpif_xlate(handler16)|:
received packet on unknown port 1 while processing
udp,in_port=1,vlan_tci=0x,dl_src=38:4c:4f:cb:62:5f,dl_dst=38:4c:4f:cb:62:53,nw_src=199.168.1.106,nw_dst=199.168.1.32,nw_tos=0,nw_ecn=0,nw_ttl=64,tp_src=53744,tp_dst=4789
on bridge br-1
2018-11-10T16:03:10.796497+08:00|warning|ovs-vswitchd[18219]|xlate_report_error[647]|2|ofproto_dpif_xlate(handler16)|:
received packet on unknown port 1 while processing
udp,in_port=1,vlan_tci=0x,dl_src=38:4c:4f:cb:62:5f,dl_dst=38:4c:4f:cb:62:53,nw_src=199.168.1.106,nw_dst=199.168.1.32,nw_tos=0,nw_ecn=0,nw_ttl=64,tp_src=53744,tp_dst=4789
on bridge br-1
2018-11-10T16:03:10.796871+08:00|warning|ovs-vswitchd[18219]|xlate_report_error[647]|1|ofproto_dpif_xlate(handler19)|:
received packet on unknown port 1 while processing
udp,in_port=1,vlan_tci=0x,dl_src=38:4c:4f:cb:62:5f,dl_dst=38:4c:4f:cb:62:53,nw_src=199.168.1.106,nw_dst=199.168.1.32,nw_tos=0,nw_ecn=0,nw_ttl=64,tp_src=41088,tp_dst=4789
on bridge br-1
2018-11-10T16:03:10.797261+08:00|info|ovs-vswitchd[18219]|recv_upcalls[848]|2|ofproto_dpif_upcall(handler19)|:
received packet on unassociated datapath port 5
2018-11-10T16:03:10.797616+08:00|info|ovs-vswitchd[18219]|recv_upcalls[848]|3|ofproto_dpif_upcall(handler19)|:
received packet on unassociated datapath port 5
2018-11-10T16:03:10.797833+08:00|info|ovs-vswitchd[18219]|recv_upcalls[848]|4|ofproto_dpif_upcall(handler19)|:
received packet on unassociated datapath port 5
2018-11-10T16:03:10.798202+08:00|info|ovs-vswitchd[18219]|recv_upcalls[848]|5|ofproto_dpif_upcall(handler19)|:
received packet on unassociated datapath port 5
2018-11-10T16:03:10.798434+08:00|info|ovs-vswitc
[ovs-discuss] install OVS on freebsd
Hey… I want install OVS based on netmap/vale on FreeBSD 11.1. for this purpose (install OVS that work with NETMAP/VALE technology) in first step should install OVS on FreeBSD and I can’t find any guide for “how to install OVS on FreeBSD” and can’t install it successfully . Can help me to install OVS on FreeBSD? ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
