Hi Ben,
Are you saying that VLAN splinters not apply on Virtual network interfaces
?
Then how to make Vlan work on virtual network like ovsbr0.4093 ?
Thanks
On Thu, Nov 7, 2013 at 11:37 AM, Ben Pfaff wrote:
> Your first message specifies the wrong command, you have to apply the
> splinter t
Thanks for the reply Andy,
Can you help me identify reason for
this behavior.
I only know that Xenserver was down and hard reset was required to bring it
back.
Recently we changed RAM from 2 Gb x 4 (1333 Mhz) to 8Gb x 1 (1600 MHz).
i have ovs 1.4.2 running on o
Hi!
I had faced a similar problem a few months back while moving from user
switch to openvswitch.
Andy had suggested this and is working as required:
VLOG_INFO (or similar) is only for user space programs. printk may work
better with kernel modules of OVS.
Check out syslog for log messages. I per
Your first message specifies the wrong command, you have to apply the
splinter to the physical port but you applied it to ovsbr0.
On Thu, Nov 07, 2013 at 11:30:00AM +0530, Linux user wrote:
> Hi Ben,
>
> Done like :
>other-config:enable-vlan-splinters=true
>
> But its not work out (please se
Hi Ben,
Done like :
other-config:enable-vlan-splinters=true
But its not work out (please see my starting mail thread) .
Thanks
On Thu, Nov 7, 2013 at 11:27 AM, Ben Pfaff wrote:
> On Thu, Nov 07, 2013 at 11:24:21AM +0530, Linux user wrote:
> > Hi Ben,
> >
> > Thanks for this info, but
On Thu, Nov 07, 2013 at 11:24:21AM +0530, Linux user wrote:
> Hi Ben,
>
> Thanks for this info, but I already know that ...
>
> My problem is that, Every time when system reboot then i use the command
> like:
>vs-vsctl set interface eth0 other-config:enable-vlan-splinters=true
>
> I want to
Hi Ben,
Thanks for this info, but I already know that ...
My problem is that, Every time when system reboot then i use the command
like:
vs-vsctl set interface eth0 other-config:enable-vlan-splinters=true
I want to integrate this command into network scripts
files(/etc/sysconfig/network-scri
Read the FAQ.
Q: VLANs don't work.
A: Many drivers in Linux kernels before version 3.3 had VLAN-related
bugs. If you are having problems with VLANs that you suspect to be
driver related, then you have several options:
- Upgrade to Linux 3.3 or later.
- Build and install a f
On Thu, Nov 7, 2013 at 12:32 AM, Gurucharan Shetty wrote:
>
> 1) Create 2 bridges. With a new bridge "br-int" having ports vm1 and
> t-gre1.
> Your bridge "br0" can retain "eth0" as a port.
>
I tried it, but the problem still remains. I think it's not a matter of
splitting datapath to "br-int" and
Hi,
I don't think , you can find any Configuration Cookbook for Vlan Splinters.
Not so much material available on Vlan Splinters user cases ( like
modification of network scripts for Vlan Splinters).
You may need to see ovs-vswitchd.conf.db.5.pdf.
May be Ben Pfaff or Jesse Gross help you in thi
Hi Ashish,
You are right, Its not work out.
If we have any Configuration Cookbook for Vlan Splinters or some sort of
user case shown ?
Thanks
On Wed, Nov 6, 2013 at 12:15 PM, ashish yadav wrote:
> Hi,
>
> I am not sure if this works, But if Vlan Splinters is allowed on Bridge
> Port ovsbr0
It does look like OVS related.
On Wed, Nov 6, 2013 at 3:42 AM, kevin parker wrote:
> Hello All,
>
> One of our xen server server stopped responding after few
> network tests,can some one please help me verify whether it is related to
> ovs.
> In stack trace i can see ovs process id
Update:
I have found that if you add a flow with dl_vlan the packet is sent to the
output port.
Then I looked at the packets generated by ofctl with vlan_vid and with
dl_vlan.
The vlan_vid value has not the cfi set, while the message sent with dl_vlan
had.
A quick search for vlan_vid into the co
On Tue, Nov 5, 2013 at 10:05 PM, Diego Rivero wrote:
> Unable to ping from vm1 to vm2 over GRE with the following settings. I
> confirmed that ping between host1(172.16.40.40) and host2(172.16.50.41) was
> successfully done without problems. Any help is welcome.
>
>
>
>
> host1# ovs-vsctl show
> 1
Hello All,
One of our xen server server stopped responding after few
network tests,can some one please help me verify whether it is related to
ovs.
In stack trace i can see ovs process id.
*ovs-vsctl -V*
ovs-vsctl (Open vSwitch) 1.4.6
Compiled Jun 14 2013 09:23:27
*From log:*
<4>[
15 matches
Mail list logo
