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
