The loadbalancing runs on whatever is connected to the switch's ports.
It doesn't matter if it's either IDS hosts or web hosts. I am a bit
lost on how you intend to integrate the IU Measurement manager with the
FlowScale controller.
--Ali
I'm assuming you created the config file web_interface.properties ?
If so, can you change flowscalehttplistener.jettyListenerPort to
flowscaleHttpListener.jettyListenerPort
and let me know if it works
?
--Ali
> <http://www.cs.princeton.edu/%7Ejrex/papers/loadwild10.pdf> for more
> discussion on the problem and possible ways to work around it. With
> the load we currently put through the FlowScale (~10Gb/sec) it
> really isn't possible to use the techniques mentioned in the paper
> because the control channel will get saturated but they may be
> useful in other circumstances.
>
> Chris Small
> InCNTRE
> Indiana University
> chs...@indiana.edu <mailto:chs...@indiana.edu>
>
>
>
> On Mar 10, 2012, at 6:09 PM, Ali Khalfan wrote:
>
>>
>>
>> The loadbalancing runs on whatever is connected to the switch's
>> ports.
>> It doesn't matter if it's either IDS hosts or web hosts. I am a bit
>> lost on how you intend to integrate the IU Measurement manager
>> with the
>> FlowScale controller.
>>
>>
>>
>> --Ali
>>
>> -------- Original Message --------
>> Subject: FlowScale Evaluation With Web Hosts
>> From: William <william...@gmail.com
>> <mailto:william...@gmail.com>>
>> To: FlowScale Developers <flowsc...@googlegroups.com
> <http://www.cs.princeton.edu/%7Ejrex/papers/loadwild10.pdf> for more
> discussion on the problem and possible ways to work around it. With
> the load we currently put through the FlowScale (~10Gb/sec) it
> really isn't possible to use the techniques mentioned in the paper
> because the control channel will get saturated but they may be
> useful in other circumstances.
>
> Chris Small
> InCNTRE
> Indiana University
> chs...@indiana.edu <mailto:chs...@indiana.edu>
>
>
>
> On Mar 10, 2012, at 6:09 PM, Ali Khalfan wrote:
>
>>
>>
>> The loadbalancing runs on whatever is connected to the switch's
>> ports.
>> It doesn't matter if it's either IDS hosts or web hosts. I am a bit
>> lost on how you intend to integrate the IU Measurement manager
>> with the
>> FlowScale controller.
>>
>>
>>
>> --Ali
>>
>> -------- Original Message --------
>> Subject: FlowScale Evaluation With Web Hosts
>> From: William <william...@gmail.com
>> <mailto:william...@gmail.com>>
>> To: FlowScale Developers <flowsc...@googlegroups.com
Reply inline, let me know if you run into complications.
-------- Original Message --------
Subject: Re: FlowScale Evaluation With Web Hosts
From: William <william...@gmail.com>
To: flowsc...@googlegroups.com
Date: Tue Mar 13 2012 22:10:41 GMT-0400 (EDT)
> Hi Ali,
>
> I can run the flowscale controller binary with jetty listener port up
> (but if I run from Eclipse source the jetty listener is still not up)
Can you please attach the log here, the default port as specified in the
context.xml under META-INF in flowscalehttplistener file is 8080.
.
> And I can see from the Web UI the port information for the OVS. Now I
> want to add the flow rule under Admin->Group. After I add the rule from
> the panel, I find that the rules written to the OVS does not have the
> in_port value.
The input port is currently there for the sake of keeping track of the
input and output ports for future enhancements. Currently, FlowScale
will not add a flow with in_port specified. Having said that, not
selecting any input port may result in an error, while not selecting any
output port would result in a drop rule.
Is there a scenario that you would think in_port may help?
I notice some UI display issue under the add group panel
> (please see the attached screenshoot) that the input/output windows does
> not show properly (no display of MAC address)
>
The UI of the "Add group" panel will simply display the switch's name,
once it is selected the ports (input/output) will be shown for selection.
> The 2nd question I have is for the Group Type field. It seems that if I
> select "IP Address" or "ANY" field, I can't seem to add the rules
> afterward (It doesn't show under Statistics->By Switch). What group
> values should I input to make this rule proper? (an concrete numerical
> example would be nice)
For the IP address FlowScale will require a subnet rather than a value,
since FlowScale will further divide this subnets into more fine-grained
ones. If you would like to add a specific IP address simply add /32 to
the end.
e.g. to add 192.168.1.2 enter "192.168.1.2/32"
ANY should add a default rule, my guess is that since FlowScale already
adds a default rule when the switch connects you will not notice a
difference, though I will take a further look into this.
>
> Last question I have is regarding the traffic plot on the main page. I
> am getting error message because it says there is no rrd data, any
> pointer on how I can resolve this?
For the current code you would need to start collecting data from the
switch on a regular basis and storing it into an rrd (I believe in OVS
you can use something like ovs-dpctl). I would point you to the file
Graph.pm under lib/Flowscale. You need to setup a directory that hosts
rrds files for each port you are polling data for as well as a file
(e.g. of.db here) with the file names.
> > <http://www.cs.princeton.edu/%7Ejrex/papers/loadwild10.pdf
> <http://www.cs.princeton.edu/%7Ejrex/papers/loadwild10.pdf>> for more
> > discussion on the problem and possible ways to work around it.
> With
> > the load we currently put through the FlowScale (~10Gb/sec) it
> > really isn't possible to use the techniques mentioned in the paper
> > because the control channel will get saturated but they may be
> > useful in other circumstances.
> >
> > Chris Small
> > InCNTRE
> > Indiana University
> > chs...@indiana.edu <mailto:chs...@indiana.edu>
> <mailto:chs...@indiana.edu <mailto:chs...@indiana.edu>>
> >
> >
> >
> > On Mar 10, 2012, at 6:09 PM, Ali Khalfan wrote:
> >
> >>
> >>
> >> The loadbalancing runs on whatever is connected to the switch's
> >> ports.
> >> It doesn't matter if it's either IDS hosts or web hosts. I
> am a bit
> >> lost on how you intend to integrate the IU Measurement manager
> >> with the
> >> FlowScale controller.
> >>
> >>
> >>
> >> --Ali
> >>
> >> -------- Original Message --------
> >> Subject: FlowScale Evaluation With Web Hosts
> >> From: William <william...@gmail.com
> <mailto:william...@gmail.com>
> >> <mailto:william...@gmail.com
> <mailto:william...@gmail.com>>>
> >> To: FlowScale Developers <flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>
> > <http://www.cs.princeton.edu/%7Ejrex/papers/loadwild10.pdf
> <http://www.cs.princeton.edu/%7Ejrex/papers/loadwild10.pdf>> for more
> > discussion on the problem and possible ways to work around it.
> With
> > the load we currently put through the FlowScale (~10Gb/sec) it
> > really isn't possible to use the techniques mentioned in the paper
> > because the control channel will get saturated but they may be
> > useful in other circumstances.
> >
> > Chris Small
> > InCNTRE
> > Indiana University
> > chs...@indiana.edu <mailto:chs...@indiana.edu>
> <mailto:chs...@indiana.edu <mailto:chs...@indiana.edu>>
> >
> >
> >
> > On Mar 10, 2012, at 6:09 PM, Ali Khalfan wrote:
> >
> >>
> >>
> >> The loadbalancing runs on whatever is connected to the switch's
> >> ports.
> >> It doesn't matter if it's either IDS hosts or web hosts. I
> am a bit
> >> lost on how you intend to integrate the IU Measurement manager
> >> with the
> >> FlowScale controller.
> >>
> >>
> >>
> >> --Ali
> >>
> >> -------- Original Message --------
> >> Subject: FlowScale Evaluation With Web Hosts
> >> From: William <william...@gmail.com
> <mailto:william...@gmail.com>
> >> <mailto:william...@gmail.com
> <mailto:william...@gmail.com>>>
> >> To: FlowScale Developers <flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>
> <mailto:williamweichih@gmail.com>
> >> <mailto:williamweichih@gmail.com
> <mailto:williamweichih@gmail.com>>>
> >> To: FlowScale Developers <flowscale-dev@googlegroups.com
> <mailto:flowscale-dev@googlegroups.com>
> <mailto:williamweichih@gmail.com>
> >> <mailto:williamweichih@gmail.com
> <mailto:williamweichih@gmail.com>>>
> >> To: FlowScale Developers <flowscale-dev@googlegroups.com
> <mailto:flowscale-dev@googlegroups.com>
Thanks for the follow up.
Again, reply inline.
Let me know if you have more questions.
-------- Original Message --------
Subject: Re: FlowScale Evaluation With Web Hosts
From: William <william...@gmail.com>
To: flowsc...@googlegroups.com
Date: Wed Mar 14 2012 20:14:40 GMT-0400 (EDT)
> Hi Ali:
>
> Here's the follow up based on your comments.
>
> 1. The flowscale log running from Eclipse is attached.
>
The flowscalehttplistener bundle was missing from the running
configuration. I just pushed a patch for flowscaleproduct, which
include flowscalehttplistener as one of the running bundles.
> 2. I can now add the rule based on the "IP Address" for Group Type
> field. Using specific IP with /32, I find that this will create two
> rules in OVS, one each for the nw_src and nw_dst but both point to same
> output port. In this case if I want to send a request/reply packet such
> as ping, then this flow rule will not allow reply message back to the
> original client. Is there any workaround for this? The reason I ask this
> is that I want to have this work with web host, but I guess that the
> flowscale design is for one way traffic path so reply message does not
> apply here.
>
This scenario would not work. The reason nw_src and nw_dst are bound to
the same output port is to maintain the session information when packets
are directed to the sensors. Do you require the output port of the reply
to be the same as the input port of the request? If not, I believe
there may be a possibility to add this functionality in future releases.
> 3. For the dynamic load balancing intelligence, I can see that traffic
> is fail over or redistributed among ports based on the switch interface
> state. But based on the design document, it points out that the
> monitoring module will utilize the Nagios software to do health check
> and traffic utilization test, so how is the threshold value determined
> for traffic test and if this also triggers rules to be rewritten? I want
> to confirm that the Nagios component is built in to flowscale and if not
> then should I install the plugin on my own?
Threshold is currently not implemented. The current implementation
attempts to cover when a link fails or goes backup. Your question about
threshold is a really important one. A possible implementation would
have a Nagios component send a message that a certain threshold has been
reached and the switch should redistribute flows to other ports.
>
> Thanks,
> William
>
> On Tuesday, March 13, 2012 8:04:14 PM UTC-7, Ali Khalfan wrote:
>
> Hi William,
>
> Reply inline, let me know if you run into complications.
>
> -------- Original Message --------
> Subject: Re: FlowScale Evaluation With Web Hosts
> From: William <william...@gmail.com
> e.g. to add 192.168.1.2 enter "192.168.1.2/32 <http://192.168.1.2/32>"
> <mailto:william...@gmail.com>
> > <mailto:william...@gmail.com
> <mailto:william...@gmail.com>>>
> > To: flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>
> > <mailto:flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>>
> <mailto:william...@gmail.com>
> > <mailto:william...@gmail.com
> <mailto:william...@gmail.com>>
> > >> <mailto:william...@gmail.com
> <mailto:william...@gmail.com>
> > <mailto:william...@gmail.com
> <mailto:william...@gmail.com>>>>
> > >> To: FlowScale Developers
> <flowsc...@googlegroups.com <mailto:flowsc...@googlegroups.com>
> > <mailto:flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>>
> > >> <mailto:flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>
> > <mailto:flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>>>>
> <mailto:william...@gmail.com>
> > <mailto:william...@gmail.com
> <mailto:william...@gmail.com>>
> > >> <mailto:william...@gmail.com
> <mailto:william...@gmail.com>
> > <mailto:william...@gmail.com
> <mailto:william...@gmail.com>>>>
> > >> To: FlowScale Developers
> <flowsc...@googlegroups.com <mailto:flowsc...@googlegroups.com>
> > <mailto:flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>>
> > >> <mailto:flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>
> > <mailto:flowsc...@googlegroups.com
> <mailto:flowsc...@googlegroups.com>>>>