hi,guys
I am confused about the in-band control and out-of-band control
I noticed that in the FAQ:
“By default, Open vSwitch assumes that OpenFlow controllers are connected
"in-band", that is, that the controllers are actually part of the network that
is being controlled.”
On Wed, Nov 26, 2014 at 01:37:21PM +1100, joe salah wrote:
> Hi,
>
>
>
> I have an ALIX 3d3 router running Linux kernel 3.10.11.
>
>
>
> I am following the instructions on INSTALL.debain to install OpenVswitch on
> my system,
>
>
>
> under "Building Open vSwitch Debian packages" : after
On Thu, Dec 11, 2014 at 02:36:12PM -0800, Vinay Bannai wrote:
> Yes, our experience has been in regards to using active-tlb and active-slb
> across multiple switches with M-LAG on the switches and LACP.
Multiple switches with M-LAG essentially act like a single switch, so
you can use that setup wi
Thanks Scott.
Yes, our experience has been in regards to using active-tlb and active-slb
across multiple switches with M-LAG on the switches and LACP.
On Thu, Dec 11, 2014 at 12:14 PM, Scott Lowe
wrote:
> Vinay, some switches have support for multi-chassis link aggregation
> (often called MLAG)
Yes, I already read it :-)
Policy routing won't help in this case, number of routing tables can grow
to 256 routing tables,
i describe test environment and in real life server may provide service to
a much larger number
of networks... over 1000.
thanks, appreciate your help
raymundo
On Thu, Dec
Policy routing can help with this issue. I wrote a post about it a while ago.
I'm sitting on a plane and therefore can't paste the link directly, but do a
Google search for "policy routing site:scottlowe.org" and see what comes up.
Good luck!
--
Scott
Sent from my mobile device
> On Dec 11,
Hi all,
Apologies if this has come up before, but I were unable to find any useful
info yet.
Problem can be summarized like this. Two networks with IP addresses from
RFC1918 need
to be connected to a single Linux host, it is very possible that there is
IP overlapping on the
two networks, i tried
Vinay, some switches have support for multi-chassis link aggregation (often
called MLAG). For MLAG-capable switches, you should be able to use any
LACP-based bonding mechanism across multiple **correctly configured** switches.
However, in the absence of MLAG support, LACP-based bonding types can
Reading through the 'INTERNALS" document in vswitchd directory, I saw a
statement under "Active Backup Bonding" that I would like to get clarified.
Active Backup bonds send all traffic out one "active" slave until that
slave becomes unavailable. Since they are significantly less
complicated than
