Dear Aneesh, I'm also using HP3500 and HP3800 with ryu controller. I used them only with OpenFlow1.3 and I have modified a bith simple_switch script to work with the HP pipeline.
Till now I never worked with rest_router, but if can better explain which is your problem I can try to help. Also I have a question for you... The HP switches supports OpenFlow13, so they should support matches indluding MPLS fields. I red in the HP3500 OpenFlow guide that some mpls actions are not supported... However I have problem in installing a simple flow with a match on the mpls_label and a simple out_port action. Did you never try using mpls match? Best Regards, alessio Il 26/05/2016 11:37, Aneesh Dogra ha scritto: > Hello, > > I am using a HP 3500yl openflow 1.3 capable sdn switch. I am trying to > get a basic topology working, I have created 2 VLANS one vlan for the > controller and another for the hosts. The second vlan containing the > hosts is driven by the controller. > > I have tried running simple_switch and rest_router example scripts with > openflow version set to 1.0 on the switch and everything works as it > should: the flows are being pushed and the hosts can ping each other. > But I need pipeline support, which was only added in openflow 1.3. The > rest_router example with openflow 1.3 doesn't seem to work. On the > contrary, the simple_switch example seems to work on 1.3 as well: I can > see the flows are pushed down to the switch and the hosts can ping each > other. > > Is any of you aware of running into problems with rest_router running on > openflow 1.3, or anything I could try to make this work? > > *HP-3500yl-24G-PoEP(of-inst-test01)# show openflow instance test01 flows* > OpenFlow Flow Table > > Flow 1 > Match > Incoming Port : 5 Ethernet Type : Any > Source MAC : Any Destination MAC : 0021cc-bfe85f > VLAN ID : Any VLAN priority : Any > Source Protocol Address : Any > Target Protocol Address : Any > IP Protocol : Any IP ToS Bits : Any > Source Port : Any Destination Port : Any > Attributes > Priority : 32768 Duration : 30 seconds > Hard Timeout : 0 seconds Idle Timeout : 0 seconds > Byte Count : 282 Packet Count : 4 > Controller ID : 1 Cookie : 0x0 > Flow Location : Software > Hardware Index : NA > Reason Code : 15 > Reason Description : Rule cannot be accelerated in hardware > Actions > Output : 3 > > Flow 2 > Match > Incoming Port : 3 Ethernet Type : Any > Source MAC : Any Destination MAC : f0761c-19e473 > VLAN ID : Any VLAN priority : Any > Source Protocol Address : Any > Target Protocol Address : Any > IP Protocol : Any IP ToS Bits : Any > Source Port : Any Destination Port : Any > Attributes > Priority : 32768 Duration : 30 seconds > Hard Timeout : 0 seconds Idle Timeout : 0 seconds > Byte Count : 356 Packet Count : 5 > Controller ID : 1 Cookie : 0x0 > Flow Location : Software > Hardware Index : NA > Reason Code : 15 > Reason Description : Rule cannot be accelerated in hardware > Actions > Output : 5 > > > But when I try to get the rest_router example to work. No flows are > pushed and none of the hosts can ping themselves: > > *HP-3500yl-24G-PoEP(of-inst-test01)# show openflow instance test01 flows* > OpenFlow Flow Table > > Flow 1 > Match > Incoming Port : Any Ethernet Type : Any > Source MAC : Any Destination MAC : Any > VLAN ID : Any VLAN priority : Any > Source Protocol Address : Any > Target Protocol Address : Any > IP Protocol : Any > IP ECN : Any IP DSCP : Any > Source Port : Any Destination Port : Any > Attributes > Priority : 0 Duration : 29 seconds > Hard Timeout : 0 seconds Idle Timeout : 0 seconds > Byte Count : 0 Packet Count : NA > Flow Table ID : 0 Controller ID : NA > Activity Count: NA Cookie : 0x0 > Hardware Index : NA > Instructions > Goto Table ID : 100 > > Flow 2 > Match > Incoming Port : Any Ethernet Type : Any > Source MAC : Any Destination MAC : Any > VLAN ID : Any VLAN priority : Any > Source Protocol Address : Any > Target Protocol Address : Any > IP Protocol : Any > IP ECN : Any IP DSCP : Any > Source Port : Any Destination Port : Any > Attributes > Priority : 0 Duration : 29 seconds > Hard Timeout : 0 seconds Idle Timeout : 0 seconds > Byte Count : NA Packet Count : 214 > Flow Table ID : 100 Controller ID : NA > Activity Count: NA Cookie : 0x0 > Hardware Index : NA > Instructions > Drop > > Flow 3 > Match > Incoming Port : Any Ethernet Type : Any > Source MAC : Any Destination MAC : Any > VLAN ID : Any VLAN priority : Any > Source Protocol Address : Any > Target Protocol Address : Any > IP Protocol : Any > IP ECN : Any IP DSCP : Any > Source Port : Any Destination Port : Any > Attributes > Priority : 0 Duration : 29 seconds > Hard Timeout : 0 seconds Idle Timeout : 0 seconds > Byte Count : 0 Packet Count : 0 > Flow Table ID : 200 Controller ID : NA > Activity Count: NA Cookie : 0x0 > Hardware Index : NA > Instructions > Drop > > *Here's the switch's running configuration: > * > ; J9310A Configuration Editor; Created on release #K.15.15.0012 > untagged 1-2,6-24 > hostname "HP-3500yl-24G-PoEP" > module 1 type j93xxa > ip routing > snmp-server community "public" unrestricted > openflow > controller-id 1 ip 192.168.2.2 controller-interface vlan 1 > instance "test01" > listen-port 8080 > member vlan 30 > controller-id 1 > version 1.3 > enable > exit > enable > exit > vlan 1 > name "openflow" > no untagged 3-5 > ip address 192.168.2.1 255.255.255.0 > exit > vlan 30 > name "VLAN30" > untagged 3-5 > ip address 192.168.3.1 255.255.255.0 > exit > > > For my experiment, I need to make changes on top of rest_router, hence > need that example to work. > > -- > Regardless, I hope you're well and happy - > Aneesh > > > ------------------------------------------------------------------------------ > Mobile security can be enabling, not merely restricting. Employees who > bring their own devices (BYOD) to work are irked by the imposition of MDM > restrictions. Mobile Device Manager Plus allows you to control only the > apps on BYO-devices by containerizing them, leaving personal data untouched! > https://ad.doubleclick.net/ddm/clk/304595813;131938128;j > > > > _______________________________________________ > Ryu-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ryu-devel > ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
