Unable to get the packet on correct port ?

[yogeshmpandey]

Hi all,

I am working on HP 2920 switch in openflow 1.3 mode. After i write a flow with output action as another port, the flow gets written succesfully but the packet is not recieved on that particular port. Are there any additional changes that are needed to be done in the switch for the dataplane to work. And how can i debug the dataplane ports in the switch.

[piricchio72]

Hello,

We would need to understand if the flow actally matches traffic.

To which table did you add the flow?

can you see packet count increasing on the flow?

Please provide the flows for this instance (show openflow instance <name> flows)

Regards,

Antonio

SDN Team

[yogeshmpandey]

I have three machines connected to the HP switch and i am trying to ping each other using flows. The Flows are getting written but i am unable to ping from one to another. Am i missing something.

Flows in the switch :

 Flow 3
 Match
  Incoming Port : 3                     Ethernet Type    : IP
  Source MAC    : Any                   Destination MAC  : Any
  VLAN ID       : Any                   VLAN priority    : Any
  Source Protocol Address : Any
  Target Protocol Address : 192.168.1.25/32
  IP Protocol   : Any
  IP ECN        : Any                   IP DSCP          : Any
  Source Port   : Any                   Destination Port : Any
 Attributes
  Priority      : 32768                 Duration         : 5 seconds
  Hard Timeout  : 0 seconds             Idle Timeout     : 0 seconds
  Byte Count    : NA                    Packet Count     : 0
  Flow Table ID : 100                   Controller ID    : listen-port
  Activity Count: NA                    Cookie           : 0x0
  Hardware Index     : 17
 Instructions
   Apply Actions
     Output                      : 5

Flows :

dpctl tcp:192.168.3.160:6633 flow-mod cmd=add,table=100 in_port=3,eth_type=0x800,ip_dst=192.168.1.25, apply:output=5
dpctl tcp:192.168.3.160:6633 flow-mod cmd=add,table=100 in_port=5,eth_type=0x800,ip_dst=192.168.1.30, apply:output=3
dpctl tcp:192.168.3.160:6633 flow-mod cmd=add,table=100 in_port=7,eth_type=0x800,ip_dst=192.168.1.25, apply:output=5
dpctl tcp:192.168.3.160:6633 flow-mod cmd=add,table=100 in_port=5,eth_type=0x800,ip_dst=192.168.1.22, apply:output=7

[Northbound]

It may be because you are macthing on eth_type 0x800 which is IP and you would need to forward ARP requests also, try removing the eth_type.

[ShaunWackerly]

Rather than wildcarding eth_type, I think you'd need to specify a separate flow which would match ARP traffic and forward to the same port. The switch firmware will likely reject a request to match an IP in a packet for all ethernet types (even non-IP packets).

Alternately, you could specify a "match ALL" or "match ALL ARP" flow which would forward to the NORMAL port. I'm assuming that you are using the controller with hybrid.mode=false?