Hi Justin,
In your reply to scalability question, you answered that we can modify the
limit of 2K MAC addresses to any value by changing a #define at openvswitch
code.
Can you please let me know the file name where I can modify this limit?
Thanks & Regards,Sachin Sharma
> ? What is the sca
The plan is to support both models.
--Justin
On Sep 7, 2011, at 10:54 PM, Holger Winkelmann wrote:
> Sounds good to me too. To clarify, you 'just' Plan to support the
> encapsulation format and control will be still the OF controller ?
>
> --
>
> Holger Winkelmann
> Travelping GmbH
> +49-171
Sounds good to me too. To clarify, you 'just' Plan to support the encapsulation
format and control will be still the OF controller ?
--
Holger Winkelmann
Travelping GmbH
+49-171-5594745
On 08.09.2011, at 07:36, Justin Pettit wrote:
> Right, I agree. I was just referring to the ability to use
Right, I agree. I was just referring to the ability to use its UDP tunneling
format to get through devices that don't like GRE. We're also planning to
support a mode where VXLAN is a virtual port, like GRE, and traffic that is
sent out it will be encapsulated (and decapsulated on receive).
--
Having the "switchport mode trunk" does not automatically mean that
the switch will carry traffic for that vlan. The vlan needs to be
created in the vlan database of the switch. Only then that vlan will
be "operational" on the trunk ports.
https://learningnetwork.cisco.com/thread/29967
show vlan c
Yeah, I think that's right. Of course, Open vSwitch will be able to
support both eventually. But for large deployments, managing the edge
MAC tables, as well as tunneling and tagging rules (and any other
filtering or QoS policy) will almost certainly require a centralized
component. Also, as
On Wed, Sep 07, 2011 at 08:05:59PM -0700, David Erickson wrote:
> On 9/7/2011 7:02 PM, Ben Pfaff wrote:
> >On Wed, Sep 07, 2011 at 06:54:27PM -0700, David Erickson wrote:
> >>I am seeing the following in the ovs-vswitchd.log when sending LLDP
> >>packets using OpenFlow's Packet Out on OVS 1.2.1:
>
Yes, VXLAN tunnel header is a good proposal, but for control plane
there is serve limitation: it depend on physical network multicast for
MAC learning. In OVS, central ovsdb controlled MAC address propagation
is a better choice.
On Wed, Sep 7, 2011 at 9:09 AM, Justin Pettit wrote:
> On Sep 7, 201
Hi Jen-Wei,
My understanding was that if you want to simply pass all VLANs through
the switch, you can make all the relevant ports (in your case, the two
connected to the servers) trunk ports. Try putting something like
switch trunk port configuration
(or the equivalent) into your favorite
As far as I know.
If you are sending vlan tagged traffic yes. (If it's untagged no).
Aaron
On Wed, Sep 7, 2011 at 11:47 PM, Jen-Wei Hu wrote:
> Hi,
> It works well if the cisco switch contains the Vlan IDs which used in VMs.
> So, we have to manually add all Vlan IDs (which will be used in VMs)
Hi,
It works well if the cisco switch contains the Vlan IDs which used in VMs.
So, we have to manually add all Vlan IDs (which will be used in VMs) in
advance?
Thanks,
Jen-Wei
On Thu, Sep 8, 2011 at 11:30 AM, Aaron Rosen wrote:
> Is the trunk port on the cisco switch set to be the same vlan id t
Is the trunk port on the cisco switch set to be the same vlan id that
is coming out of the VMs?
Aaron
On Wed, Sep 7, 2011 at 10:34 PM, Ben Pfaff wrote:
> I only know how to configure OVS.
>
> On Thu, Sep 08, 2011 at 10:31:38AM +0800, Jen-Wei Hu wrote:
>> Thanks for your quick reply. Could you ki
On 9/7/2011 7:02 PM, Ben Pfaff wrote:
On Wed, Sep 07, 2011 at 06:54:27PM -0700, David Erickson wrote:
I am seeing the following in the ovs-vswitchd.log when sending LLDP
packets using OpenFlow's Packet Out on OVS 1.2.1:
Sep 07 21:47:08|00151|dpif|WARN|system@xenbr0: execute 1 failed
(Invalid ar
I only know how to configure OVS.
On Thu, Sep 08, 2011 at 10:31:38AM +0800, Jen-Wei Hu wrote:
> Thanks for your quick reply. Could you kindly share and describe how other
> brands switch must configure when creating new VLAN ID on OVS?
>
> On Thu, Sep 8, 2011 at 10:01 AM, Ben Pfaff wrote:
>
> >
Hi Ben,
Thanks for your quick reply. Could you kindly share and describe how other
brands switch must configure when creating new VLAN ID on OVS?
Thanks,
Jen-Wei
On Thu, Sep 8, 2011 at 10:01 AM, Ben Pfaff wrote:
> No, I don't know how to configure a Cisco switch. I hope that someone
> else can
On Sep 7, 2011, at 5:29 PM, David Erickson wrote:
> Is there a specific procedure for moving between OVS versions in XenServer?
> I've done this a few times, and frequently I find myself in a situation where
> the xenbr0 device has completely disappeared, and I couldn't find a way to
> restore
On Wed, Sep 07, 2011 at 06:54:27PM -0700, David Erickson wrote:
> I am seeing the following in the ovs-vswitchd.log when sending LLDP
> packets using OpenFlow's Packet Out on OVS 1.2.1:
>
> Sep 07 21:47:08|00151|dpif|WARN|system@xenbr0: execute 1 failed
> (Invalid argument) on packet 00:00:00:00:0
No, I don't know how to configure a Cisco switch. I hope that someone
else can suggest how to do this.
On Thu, Sep 08, 2011 at 09:39:44AM +0800, Jen-Wei Hu wrote:
> Sorry for the poor English. I try to describe my problem clearly. Currently,
> we could configure the VLAN function of OVS successfu
On Wed, Sep 07, 2011 at 05:29:31PM -0700, David Erickson wrote:
> Is there a specific procedure for moving between OVS versions in
> XenServer? I've done this a few times, and frequently I find myself
> in a situation where the xenbr0 device has completely disappeared,
> and I couldn't find a way
Hi-
I am seeing the following in the ovs-vswitchd.log when sending LLDP
packets using OpenFlow's Packet Out on OVS 1.2.1:
Sep 07 21:47:08|00151|dpif|WARN|system@xenbr0: execute 1 failed (Invalid
argument) on packet 00:00:00:00:00:02 > 01:80:c2:00:00:0e, ethertype
Unknown (0x88cc), length 48:
Hi Ben,
Sorry for the poor English. I try to describe my problem clearly. Currently,
we could configure the VLAN function of OVS successfully and work well when
our two servers (installed OVS) directly connected via a network cable. But
when we deploy these two servers to our physical switch, we m
Hi all-
Is there a specific procedure for moving between OVS versions in
XenServer? I've done this a few times, and frequently I find myself in
a situation where the xenbr0 device has completely disappeared, and I
couldn't find a way to restore it other than re-installing Xen. In
particular
2011/9/7 Sébastien Riccio :
> On 07.09.2011 17:12, Ben Pfaff wrote:
>>
>> On Wed, Sep 07, 2011 at 01:28:16PM +0200, S?bastien Riccio wrote:
>>>
>>> I just did a test to see how openvswitch handle a flood from a
>>> virtual machine on a xen
>>> host using it as the networking layer.
>>>
>>> I just i
On Sep 7, 2011, at 9:01 AM, Nicky Fatr wrote:
> I don't think that TRILL/802.1AQ L2 over L2 is a good option for large
> scale deployment. L2 over L3 instead is more scalable, eliminating
> comlexity of physical network.
>
> maybe we can expect L2 over UDP in some future release, for UDP is
> mor
I don't think that TRILL/802.1AQ L2 over L2 is a good option for large
scale deployment. L2 over L3 instead is more scalable, eliminating
comlexity of physical network.
maybe we can expect L2 over UDP in some future release, for UDP is
more friendly than GRE in some networking configuration.
On
On Wed, Sep 07, 2011 at 05:11:58PM +0800, Jen-Wei Hu wrote:
> Recently, we would like to let our deployed VMs that could be separated by
> VLAN. In this link (
> http://openvswitch.org/support/config-cookbooks/vlan-configuration-cookbook/),
> it mentions that we should set up trunking ports on phys
On Wed, Sep 07, 2011 at 01:28:16PM +0200, S?bastien Riccio wrote:
> I just did a test to see how openvswitch handle a flood from a
> virtual machine on a xen
> host using it as the networking layer.
>
> I just issued a :
>
> vm1# hping3 -S -L 0 -p 80 -i u100 192.168.1.1
>
> options I used are:
Hi,
I just did a test to see how openvswitch handle a flood from a virtual
machine on a xen
host using it as the networking layer.
I just issued a :
vm1# hping3 -S -L 0 -p 80 -i u100 192.168.1.1
options I used are:
-S set SYN tcp flag
-L set ACK tcp flag
-p destination port
-i u100 = interv
Hi all,
Recently, we would like to let our deployed VMs that could be separated by
VLAN. In this link (
http://openvswitch.org/support/config-cookbooks/vlan-configuration-cookbook/),
it mentions that we should set up trunking ports on physical switches. Our
switch is a port-based to set VLAN ID, s
29 matches
Mail list logo
