hi,
One more query, Is this flow extraction typically done by a software module
even in hardware switches or it is perhaps performed by a specialized and
optimized hardware in hardware switches?
regards,
kalapriya.
From: Justin Pettit
To: K.Kalapriya
Cc
We are having performance issues with XEN as opposed to VMWARE.
Pls take a look at the following cases (OVS - open vswitch, Bridge - native
linux bridging)
Case 1 (no VM guest tagging):VM1 VNIC1 (no tag) --- OVS
---(vlan X) --- PNIC1--(vlan X)- PNIC2 (vlan
Instead connecting host1 and host2 via a router, I connected directly via eth0
interface and used the same net so that no explicit route entry is needed
Thanks
-Senthil
From: Ben Pfaff
To: senthil arumugam
Cc: ben...@gmail.com; pet...@nicira.com; discuss@open
On Thu, Jan 19, 2012 at 12:06:57PM -0800, senthil arumugam wrote:
> I tried to setup the same but did not work. The only difference is I have
> directly connected host1 and host2 over one ethernet card.
When you say "the same" and "the only difference," what are you
comparing against?
___
HiI tried to setup the same but did not work. The only difference is I have directly connected host1 and host2 over one ethernet card.Host1 (etho)-(eth0)Host2 10.193.1.1 10.193.1.2I could ping these IP addresses from both hosts- Cr
Hi there,
i am facing the following strange behavior (Open vSwitch 1.4.90 and 1.2.2).
*
Adding a GRE interface with GRE key value=1 to my OVS creates packets
with GRE key value equal to 0x30760001
*
root@ovs1:~# ovs-vsctl -- add-port br0 gre100_2 tag=2830 -- set
interface gre100_2 type=gre opti
On Wed, Jan 18, 2012 at 10:59:25PM -0500, Dushyant Arora wrote:
> After starting the VMs on H1 and H4, I configure the interfaces on
> them and give them IP addresses from private IPv4 address space. The
> VMs cannot ping each other. What am I doing wrong?
The usual way to debug this kind of probl
On Thu, Jan 19, 2012 at 02:21:07PM +0200, Heinonen, Johanna (NSN - FI/Espoo)
wrote:
> It seems that the problem is related to LLDP messages that come from
> "bad in-port" i.e. a port that is not connected to ovs.
Your controller is trying to send a packet with an in_port of
OFPP_CONTROLLER. Thi
Hi,
Attached is a logfile.
It seems that the problem is related to LLDP messages that come from
"bad in-port" i.e. a port that is not connected to ovs. My setup is the
following:
NOX linux1
| |
---192.168.4.0/24
|
linux3OVSlinux2
Open vSwitch doesn't support OpenFlow 1.1, but, regardless, flow extraction is
on the critical path. I can't think how to avoid that, since it must classify
the packets to determine which actions to apply. It does some smart caching to
make the lookup fast in software, but it still needs to ex
hi,
Just wanted to know if the flow extraction phase (page 9 of the openflow switch
specification 1.1.0) on the critical path of the switch performance?
regards,
kalapriya.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman
11 matches
Mail list logo
