Fixed
Created: Jun 7, 2013
Updated: Mar 11, 2016
Resolved Date: Sep 2, 2013
Found In Version: 5.0.1
Fix Version: 5.0.1.7
Severity: Standard
Applicable for: Wind River Linux 5
Component/s: Kernel
The configuration will be permitted without errors or warnings.
Further symptoms as the usecase progresses are yet to be determined. (I intend to fill this in as I test and troubleshoot; you the reader are welcomed to contribute). The original defect WIND00420403 suggests the crossing of guest network traffic, breaking the segregation of vxlan overlay networks. This is not confirmed.
Each vxlan overlay network should be configured with it's own multicast address
i.e.,
51 with group 238.1.1.1
52 with group 238.1.1.2
Do not share multicast addresses between several vxlan overlay networks
1) Configure and build the kvm host:
configure --enable-kernel=preempt-rt \
--enable-addons=wr-ovp \
--enable-rootfs=ovp-kvm \
--enable-board=intel_xeon_core
make
2) boot the kvm host and configure two vxlan overlay networks with the same multicast address:
$ ip link add vxlan1 type vxlan id 51 group 238.1.1.1 dev eth0
$ ip link add vxlan2 type vxlan id 52 group 238.1.1.1 dev eth0
Detailed instructions for use of vxlan are in the ovp layer templates/feature/vxlan/README
