Thanks very much for the information you provided. The weird thing is, I just run "show openflow instance test flows" then I found one entry on HP OFS. But there is not install information in DEBUG information on POX. I have the following debug information but only till the first flood message I highlighted.
[pox]$ ./pox.py log.level --DEBUG forwarding.l2_learning POX 0.1.0 (betta) / Copyright 2011-2013 James McCauley, et al. DEBUG:core:POX 0.1.0 (betta) going up... DEBUG:core:Running on CPython (2.7.1/Jul 31 2011 19:30:53) DEBUG:core:Platform is Darwin-11.4.2-x86_64-i386-64bit INFO:core:POX 0.1.0 (betta) is up. DEBUG:openflow.of_01:Listening on 0.0.0.0:6633 INFO:openflow.of_01:[00-00-00-00-00-02 1] connected DEBUG:forwarding.l2_learning:Connection [00-00-00-00-00-02 1] INFO:openflow.of_01:[00-00-00-00-00-01 2] connected DEBUG:forwarding.l2_learning:Connection [00-00-00-00-00-01 2] DEBUG:forwarding.l2_learning:Port for [mac of destination host] unknown -- flooding And I just restarted the POX, debug information shows it connects to HP OFS, so I use ssh instead of ping from host 1 to host 2. No debug information and no flow entry in HP OFS again. but probably 3 mins later, there is one entry in flow table of HP SW. I know POX should have debug information like incoming packet and etc. It seems like my setup works sometimes but not fully functional. Any thought ? Highly appreciate your kind help On Fri, Feb 22, 2013 at 2:29 PM, Murphy McCauley <murphy.mccau...@gmail.com>wrote: > I think the interesting messages aren't the connection messages but the > flow install messages from l2_learning: > > [pox]$ ./pox.py log.level --DEBUG forwarding.l2_learning > POX 0.1.0 (betta) / Copyright 2011-2013 James McCauley, et al. > DEBUG:core:POX 0.1.0 (betta) going up... > DEBUG:core:Running on CPython (2.7.1/Jul 31 2011 19:30:53) > DEBUG:core:Platform is Darwin-11.4.2-x86_64-i386-64bit > INFO:core:POX 0.1.0 (betta) is up. > DEBUG:openflow.of_01:Listening on 0.0.0.0:6633 > INFO:openflow.of_01:[00-00-00-00-00-02 1] connected > DEBUG:forwarding.l2_learning:Connection [00-00-00-00-00-02 1] > INFO:openflow.of_01:[00-00-00-00-00-01 2] connected > DEBUG:forwarding.l2_learning:Connection [00-00-00-00-00-01 2] > DEBUG:forwarding.l2_learning:Port for 00:00:00:00:00:02 unknown -- flooding > DEBUG:forwarding.l2_learning:Port for 00:00:00:00:00:02 unknown -- flooding > DEBUG:forwarding.l2_learning:installing flow for 00:00:00:00:00:02.1 -> > 00:00:00:00:00:01.2 > DEBUG:forwarding.l2_learning:installing flow for 00:00:00:00:00:02.2 -> > 00:00:00:00:00:01.1 > DEBUG:forwarding.l2_learning:installing flow for 00:00:00:00:00:01.1 -> > 00:00:00:00:00:02.2 > > Your log should look very much like that. If you're not seeing the flow > installation messages when you try to ping across those ports, then the > switch is apparently not treating them as OpenFlow ports. (Alternately, > you could run Wireshark on the control connection or run the openflow.debug > module in POX which will create a pcap trace -- you should see > ofp_packet_in messages). > > -- Murphy > > On Feb 22, 2013, at 12:42 PM, terryxing wrote: > > Thanks, > > Yes, I used the fail-standalone mode. When they are connected, the debug > information shows in the POX say connect to blabla. I think they are > indeed connected. > > I just switched to the fail-secure mode. The problem is still the same, > host 1 can still ping host 2 even I use "ctrl-D" to stop the controller. > BTW, I run forwarding.l2_learning component in POX. > > What I want to see is, when I run the openflow swtich, without running > application in POX controller, the HP OFS can not even work. But they work > without POX application running and there is not flow table entry can be > shown on HP switch. > > Any thought ? Thanks very much for your kind help. > > > On Fri, Feb 22, 2013 at 12:32 PM, Murphy McCauley < > murphy.mccau...@gmail.com> wrote: > >> Butting in... >> >> It looks like you may be in fail-standalone mode, where the switch >> becomes a normal switch if it can't connect to the controller. Switching >> to fail-secure may help clear things up. >> >> Also, when the switch *is* connected, do you see flow install messages >> from POX? (You probably have to turn up the log level with log.level >> --DEBUG). >> >> -- Murphy >> >> On Feb 22, 2013, at 11:02 AM, terryxing wrote: >> >> Hi Dear Steven, >> >> I have one more question. After I successfully connect my controller and >> HP openflow switch. I run forwarding.l2_learning component on POX >> controller. I use both aggregate mode and virtualization mode. But I can >> not see any flow on the HP swtich by typing show openflow instance >> aggregate flows. >> >> Also, for testing traffic from host 1 (connecting to port 1) to host 2( >> connecting to port 2), they can always ping each other no matter if I run >> controller or not. >> >> Thanks, >> >> On Fri, Feb 22, 2013 at 9:45 AM, Steven Noble <sno...@sonn.com> wrote: >> >>> No problem! I am cling back in the openflow-discuss list so that there >>> is an archive of this issue for others to search on. >>> >>> On Feb 22, 2013, at 8:57 AM, terryxing <xingtia...@gmail.com> wrote: >>> >>> Hi Steven, >>> >>> It worked. Highly appreciate your kind help !!!! >>> >>> On Thu, Feb 21, 2013 at 8:19 PM, terryxing <xingtia...@gmail.com> wrote: >>> >>>> Thanks very much >>>> >>>> So you set IP address on that vlan3 to talk to controller. This ip is >>>> different from management ip right ？ >>>> >>>> I did not set ip on vlan before. Hope that is the problem. Thanks >>>> >>>> >>>> On Thursday, February 21, 2013, Steven Noble wrote: >>>> >>>>> Hi Terry, >>>>> >>>>> Here is the exact configuration I used for NOX (RouteFlow). My >>>>> controller was 192.168.1.17, my ip was 192.168.1.100. >>>>> >>>>> >>>>> openflow >>>>> enable >>>>> controller-id 2 ip 192.168.1.17 controller-interface vlan 3 >>>>> instance "routeflow" >>>>> listen-port >>>>> member vlan 1 >>>>> controller-id 2 >>>>> connection-interruption-mode fail-standalone >>>>> enable >>>>> exit >>>>> >>>>> vlan 1 >>>>> name "DEFAULT_VLAN" >>>>> no untagged 1-2 >>>>> untagged 3-24 >>>>> ip address dhcp-bootp >>>>> exit >>>>> vlan 3 >>>>> name "CNTL_VLAN" >>>>> untagged 2 >>>>> ip address 192.168.1.100 255.255.255.0 >>>>> exit >>>>> >>>>> On Feb 21, 2013, at 8:11 PM, terryxing <xingtia...@gmail.com> wrote: >>>>> >>>>> thanks Noble >>>>> >>>>> do you have to add that port into vlan 10? untagged or tagged ? >>>>> >>>>> Thanks >>>>> On Feb 21, 2013 11:09 PM, "Steve Noble" <sno...@sonn.com> wrote: >>>>> >>>>> I think you cannot. I think i used vlan 10. >>>>> On Feb 21, 2013 12:14 PM, "terryxing" <xingtia...@gmail.com> wrote: >>>>> >>>>> BTW, I can understand that controller communication >>>>> needs separate VLAN. Can I use VLAN 1 as the VLAN to communicate with >>>>> controller from OFS ? >>>>> >>>>> The controller use port 12 to connect to the HP OFS. Should I add the >>>>> port into the specific VLAN ? like vlan 1 ? Port 12 should be added as >>>>> untagged or tagged ? >>>>> >>>>> I just wanna make controller and OFS connected first. >>>>> >>>>> Thanks very much. >>>>> >>>>> On Thu, Feb 21, 2013 at 9:57 AM, terryxing <xingtia...@gmail.com>wrote: >>>>> >>>>> Thanks very much for your timely reply. >>>>> >>>>> The thing is, I use port 12 as the port for communicating with >>>>> controller. I need to specify a vlan for communication betwee OFS and POX. >>>>> I used VLAN 1, but the status is still disconnected. They can ping each >>>>> other but can not connected. >>>>> >>>>> Another weird thing is that I use port 1 and 2 for connecting two >>>>> physical servers so that VMs can talk to each other. As I tested >>>>> yesterday, the weird thing is, even I did not run the openflow, two VMs >>>>> can >>>>> still ping each other through port 1 and 2. Based on my understanding, if >>>>> I enabled openflow on the HP switch, without running application on >>>>> controller, like l2_learning switch, the traffic of port 1 and 2 can not >>>>> be >>>>> forwarded. >>>>> >>>>> Any thought ? >>>>> >>>>> Thanks very much. >>>>> >>>>> >>>>> On Wed, Feb 20, 2013 at 7:09 PM, Steve Noble <sno...@sonn.com> wrote: >>>>> >>>>> Hi Terry, >>>>> >>>>> When I did my testing I used the configuration outlined in this post >>>>> >>>>> >>>>> http://www.routeranalysis.com/state-of-openflow-2012-day-56-notes-on-hp/ >>>>> >>>>> Let me know of that helps. >>>>> On Feb 20, 2013 4:01 PM, "terryxing" <xingtia...@gmail.com> wrote: >>>>> >>>>> Dear All, >>>>> >>>>> I am configuring the HP 3500yl openflow switch. I already burn the >>>>> firmware K15.10 version into the secondary OS of the HP openflow switch >>>>> and >>>>> boot as the secondary OS. I think the openflow is already successfully >>>>> installed on the HP switch since I can use openflow CLI to configure. The >>>>> thing is , I can not make my openflow swtich talk to the controller. >>>>> >>>>> I configure the 192.168.1.66 as the ip of HP OFS and 192.168.1.60 for >>>>> the POX controller as a virtual machine (the physical server is connected >>>>> to HP OFS) They can ping each other which means the connection is good. >>>>> >>>>> But when I configure the OFS by following the manual for K15.10 >>>>> version. I can not make OFS and POX connected. I configure the instance as >>>>> aggregate mode but I dont know how can I specific >>>>> >>>>> >>>> >>>> -- >>>> Best regards, >>>> >>>> Tianyi Xing (邢天翼) >>>> >>>> PhD Student, Research & Teaching Associate >>>> SNAC:Secure Networking and Computing group >>>> School of Computing, Informatics, and Decision Systems Engineering >>>> Ira A. Fulton School of Engineering, >>>> Arizona State University >>>> Tempe, AZ 85281, USA >>>> >>>> >>>> >>> >>> >>> -- >>> Best regards, >>> >>> Terry >>> >>> >>> >> >> >> -- >> Best regards, >> >> Terry >> >> _______________________________________________ >> openflow-discuss mailing list >> openflow-discuss@lists.stanford.edu >> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >> >> >> > >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
