Hi,
If we are using cfm_interval while creating cfm mpid then--
1) Is that means it is for this particular Mpid.so it means we can
configure different interval for different MPids?
2) along with that I want to know how can I see the current timer value by
any show command for particular MPids, I
On Wed, Feb 15, 2012 at 6:41 PM, Aaron Rosen wrote:
> Would packets be sent to the controller with or without vlan tag?
> Either way the only action you should need is output I think (You
> shouldn't need to add OFPAT_SET_VLAN_VID before output)? One issue
> you could be running into here is that
Thanks Aaron, thats working!
Might be helpful for some:
ip link add type veth
tc qdisk add dev veth0 root tbf rate 10mbit buffer 10kb latency 50ms
tc qdisk add dev veth1 root tbf rate 10mbit buffer 10kb latency 50ms
ip link set veth0 up
ip link set veth1 up
ovs-vsctl add-port br0 veth0
ovs-vsctl
Would packets be sent to the controller with or without vlan tag?
Either way the only action you should need is output I think (You
shouldn't need to add OFPAT_SET_VLAN_VID before output)? One issue
you could be running into here is that pyswitch would not let you have
duplicate MAC addresses on t
On Wed, Feb 15, 2012 at 6:09 PM, James Chung wrote:
> Hi Experts,
>
> Does anyone has this experience to control XenServer OVS with NOX
> controller?
> I recently setup two OVS on two separate XensServer, and configure two VLANs
> on them (vlan100 and vlan200). Without any controller, the VLAN
> c
Hi Experts,
Does anyone has this experience to control XenServer OVS with NOX
controller?
I recently setup two OVS on two separate XensServer, and configure two
VLANs on them (vlan100 and vlan200). Without any controller, the VLAN
configuration is working perfectly. The VMs in vlan100 can only tal
Hi Janis,
I don't think you can do this with patch ports, but I've been able to
do this in OVS using veth.
Aaron
On Wed, Feb 15, 2012 at 8:29 PM, Janis Hamme
wrote:
> Hi,
> I connected br0 and br1 using a patch port. I tried to limit the rate on
> the link between br0 and br1 using this guide:
Hi,
I connected br0 and br1 using a patch port. I tried to limit the rate on
the link between br0 and br1 using this guide:
http://openvswitch.org/support/config-cookbooks/qos-rate-limiting/
While its working well with normal ports it doesn't seem to have any
impact on patch ports. Is that a bug o
OK. I'm glad it works with OVS 1.4.0. We are planning to keep OVS
scripts in sync with upstream XenServer from now on (mostly, by not
installing any scripts over the upstream XenServer versions), so with
luck the problem will not recur.
I imagine that there are few users of SR-IOV who install OV
The observation I had with the current XenServer 6.0 is, its working fine
with
default OVS-1.0.99. And not working with any new OVS, except OVS-1.4.0.
That's the reason, I posted my observation.
Thanks,
Ramana Reddy.
On Wed, Feb 15, 2012 at 11:39 PM, Ben Pfaff wrote:
> We do our best to backpo
We do our best to backport fixes to earlier release branches when they
are either important or easy to backport. The fact that this fix wasn't
backported demonstrates that it didn't fall into one of those
categories, or that we overlooked it. If you need the fix on an earlier
version, you are fre
Irrespective of the OVS version, it should work right?
On Wed, Feb 15, 2012 at 11:29 PM, Ben Pfaff wrote:
> On Wed, Feb 15, 2012 at 11:24:07PM +0530, Ramana Reddy wrote:
> > The function call_hook_script is missing in the file
> > etc_xensource_scripts_vif in xenserver folder
> > in all OVS re
On Feb 15, 2012, at 9:56 AM, Jesse Gross wrote:
> On Wed, Feb 15, 2012 at 9:52 AM, Salvatore Orlando
> wrote:
>> Hi Jesse,
>>
>> I apologise I did not configure correctly the vswitch on the Ubuntu machine
>> running 1.2.
>> The behaviour seems anyway confirmed in 1.0.99, but I suspect that's
>
On Wed, Feb 15, 2012 at 11:24:07PM +0530, Ramana Reddy wrote:
> The function call_hook_script is missing in the file
> etc_xensource_scripts_vif in xenserver folder
> in all OVS releases, except OVS-1.4.0. This is needed for xenserver for
> SRIOV support.
> Please update this issue.
Why don't you
On Wed, Feb 15, 2012 at 9:52 AM, Salvatore Orlando
wrote:
> Hi Jesse,
>
> I apologise I did not configure correctly the vswitch on the Ubuntu machine
> running 1.2.
> The behaviour seems anyway confirmed in 1.0.99, but I suspect that's
> unsupported now.
>
> Anyway, is the behaviour when the int
The function call_hook_script is missing in the file
etc_xensource_scripts_vif in xenserver folder
in all OVS releases, except OVS-1.4.0. This is needed for xenserver for
SRIOV support.
Please update this issue.
Regards,
Ramana Reddy.
___
discuss mailin
Hi Jesse,
I apologise I did not configure correctly the vswitch on the Ubuntu machine
running 1.2.
The behaviour seems anyway confirmed in 1.0.99, but I suspect that's
unsupported now.
Anyway, is the behaviour when the interface name exceeds the 16 character limit
documented?
Ovs-vsctl did no
On Wed, Feb 15, 2012 at 8:40 AM, Salvatore Orlando
wrote:
> An unexpected behaviour occurred while creating GRE tunnels with Open vSwitch.
> In a nutshell, GRE tunnels appear to be not working when the name of the
> tunnel interface exceeded 13 characters. The tunnel is stored in the
> database,
On Wed, Feb 15, 2012 at 04:40:53PM +, Salvatore Orlando wrote:
> An unexpected behaviour occurred while creating GRE tunnels with Open
> vSwitch. In a nutshell, GRE tunnels appear to be not working when the
> name of the tunnel interface exceeded 13 characters. The tunnel is
> stored in the da
On Wed, Feb 15, 2012 at 08:02:05PM +0530, sachin sharma wrote:
> I found the design of inband communication at openvswitch via DESIGN
> file in the openvswitch. However, i did not find the exact steps to
> configure this in our switches.
In-band control is enabled by default when you configure a c
An unexpected behaviour occurred while creating GRE tunnels with Open vSwitch.
In a nutshell, GRE tunnels appear to be not working when the name of the tunnel
interface exceeded 13 characters. The tunnel is stored in the database, but it
does not show up on the datapath.
This behaviour occurred o
Hi,
I found the design of inband communication at openvswitch via DESIGN file in
the openvswitch. However, i did not find the exact steps to configure this in
our switches.
I have a setup of following nodes linked in a linear way:
Server-OpenVswitch-A--OpenVswitch-B---
22 matches
Mail list logo
