[pox-dev] executing the ip_loadbalancer

[Murphy McCauley]

Ah, see inline.

On Apr 23, 2014, at 11:02 PM, Murphy McCauley <murphy.mccauley at gmail.com> wrote:

> And you're running the iperf server on 10.0.0.1 and 10.0.0.2?  And where are you running the client from?  With what commandline?
> 
> -- Murphy
> 
> On Apr 23, 2014, at 10:49 PM, shads s <shasi0625 at gmail.com> wrote:
> 
>> Hello all,
>> 
>> Actually from last few days I am trying to run ip_loadbalancer example using POX and mininet. 
>> After introducing TCP flow using iperf in mininet, it is showing "DEBUG:iplb.00-00-00-00-00-01:No client for (IPAddr('10.0.0.2'), IPAddr('10.0.0.6'), 56422, 5001)".
>> Even tcpdump shows only ARP request packets.
>> 
>> It will be great help if you send me the steps to run ip_loadbalancer. 
>> 
>> Below is the mininet topology:
>> mininet> net
>> h1 h1-eth0:s1-eth1
>> h2 h2-eth0:s1-eth2
>> h3 h3-eth0:s1-eth3
>> h4 h4-eth0:s1-eth4
>> h5 h5-eth0:s1-eth5
>> h6 h6-eth0:s1-eth6
>> s1 lo:  s1-eth1:h1-eth0 s1-eth2:h2-eth0 s1-eth3:h3-eth0 s1-eth4:h4-eth0 s1-eth5:h5-eth0 s1-eth6:h6-eth0
>> c0
>> 
>> Below is the POX output when TCP flow start using "iperf h2 h6" in Mininet:

I don't think that makes any sense.  Do you mean "h2 iperf h6"?  That doesn't make any sense either.  h2 is one of the *servers* in this case.  You want to be running the iperf client from somewhere *else* and have it *access* the servers.  And you don't want to be using one of the servers' actual addresses anyway -- you want to be using the "virtual" load balancer address -- 10.1.2.3.

I just fired up Mininet with single,3 topology, opened xterms for all three hosts, and ran the servers in h1 and h2 with iperf -s.  Then I ran iperf -c 10.1.2.3 in h3 several times and saw it go to both h1 and h2.  Seems to work fine for me.  Could also have probably run that as "h3 iperf 10.1.2.3" from the mininet prompt, but I already was opening xterms anyway.

-- Murphy


>> [root at localhost pox]# ./pox.py log.level --DEBUG misc.ip_loadbalancer --ip=10.1.2.3 --servers=10.0.0.1,10.0.0.2
>> POX 0.2.0 (carp) / Copyright 2011-2013 James McCauley, et al.
>> DEBUG:core:POX 0.2.0 (carp) going up...
>> DEBUG:core:Running on CPython (2.7.5/Feb 19 2014 13:47:40)
>> DEBUG:core:Platform is Linux-3.13.10-200.fc20.i686+PAE-i686-with-fedora-20-Heisenbug
>> INFO:core:POX 0.2.0 (carp) is up.
>> DEBUG:openflow.of_01:Listening on 0.0.0.0:6633
>> INFO:openflow.of_01:[00-00-00-00-00-01 1] connected
>> INFO:iplb:IP Load Balancer Ready.
>> INFO:iplb:Load Balancing on [00-00-00-00-00-01 1]
>> INFO:iplb.00-00-00-00-00-01:Server 10.0.0.2 up
>> INFO:iplb.00-00-00-00-00-01:Server 10.0.0.1 up
>> DEBUG:iplb.00-00-00-00-00-01:No client for (IPAddr('10.0.0.2'), IPAddr('10.0.0.6'), 56422, 5001)
>> DEBUG:iplb.00-00-00-00-00-01:No client for (IPAddr('10.0.0.2'), IPAddr('10.0.0.6'), 56422, 5001)
>> DEBUG:iplb.00-00-00-00-00-01:No client for (IPAddr('10.0.0.2'), IPAddr('10.0.0.6'), 56422, 5001)
>> DEBUG:iplb.00-00-00-00-00-01:No client for (IPAddr('10.0.0.2'), IPAddr('10.0.0.6'), 56422, 5001)
>> DEBUG:iplb.00-00-00-00-00-01:No client for (IPAddr('10.0.0.2'), IPAddr('10.0.0.6'), 56422, 5001)
>> DEBUG:iplb.00-00-00-00-00-01:No client for (IPAddr('10.0.0.2'), IPAddr('10.0.0.6'), 56422, 5001)
>> 
>> 
>> TCPDUMP output:
>> 
>> 17:52:29.244757 ARP, Request who-has 10.0.0.1 (Broadcast) tell 10.1.2.3, length 28
>> 17:52:31.760936 ARP, Request who-has 10.0.0.2 (Broadcast) tell 10.1.2.3, length 28
>> 17:52:32.067594 IP6 fe80::dc3a:bdff:feb7:4b58 > ff02::2: ICMP6, router solicitation, length 8
>> 17:52:34.293540 ARP, Request who-has 10.0.0.1 (Broadcast) tell 10.1.2.3, length 28
>> 17:52:36.809811 ARP, Request who-has 10.0.0.2 (Broadcast) tell 10.1.2.3, length 28
>> 17:52:39.355686 ARP, Request who-has 10.0.0.1 (Broadcast) tell 10.1.2.3, length 28
>> 17:52:41.886370 ARP, Request who-has 10.0.0.2 (Broadcast) tell 10.1.2.3, length 28
>> 
>> Thanks & Regards,
>> Shads
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.noxrepo.org/pipermail/pox-dev-noxrepo.org/attachments/20140423/c68f6922/attachment-0002.htm>