About OpenFlow Group Type Select

[Ramzah_Rehman]

Hi,

I have aruba 2930F series switch JL253A. I have RYU controller and I'm using OpenFlow 1.3. I added a select group in switch. Then, I tried to add a flow that forwards packet to that group in hardware flow table i.e. policy table, id 100. I got OFPBAC_BAD_OUT_GROUP error which means there's Invalid group id in forward action. Is this error expected? Can a flow in hardware not forward a packet to a group in software or am I doing something wrong? 

I then tried to add the flow that forwards packet to select group in sw Table 1, table id 200. This did not give any error. But this way I observe too much delay and retransmissions. I was getting throughput in Kbps on 1G link. Please help

This is the config on switch:

show running-config
erase startup-config
config
max-vlans 2048
hostname leaf2
Openflow
Openflow enable
openflow instance l2
vlan 2
vlan 3
vlan 2 name c-vlan
vlan 3 name s-vlan
vlan 2 ip address 192.168.1.2/16
vlan 3 ip address 10.1.0.2/8
exit
openflow instance l2
openflow instance l2 table-num policy-table 100
openflow instance l2 table-num sw-table-1 200
openflow instance l2 version 1.3 only
openflow instance l2 member vlan 3
#no controller-id 1
#no openflow controller-id 1
openflow instance l2 listen-port 6633
openflow controller-id 1 ip 192.168.0.1 port 6633 controller-interface vlan 2
openflow instance l2 controller-id 1
openflow instance l2 controller-id 1 secure
openflow instance l2 override-protocol none
openflow instance l2 pipeline-model standard-match
vlan 2 untagged ethernet 24
vlan 3 untagged ethernet 1-2,11-13
max-backoff-interval 10
packet-in vlan-tagging input-form
openflow instance l2 enable
save
write mem
show running-config
boot system

[ShaunWackerly · Accepted solution]

I checked with the development team and they replied with the information below.

A group of type=SELECT is not supported in hardware on our switches. However it can be installed in software with certain limitations. Please refer the OpenFlow administrator guide for details. The admin guide for 16.06 can be found here (in Chapter 5):
    https://support.hpe.com/hpsc/doc/public/display?docId=a00050280en_us

As hardware flows cannot point to a software group, the FLOW_MOD is returned with OFPBAC_BAD_OUT_GROUP error as expected. Lower throughput should be expected when the Group is associated with a flow in table=200 (software table), since packets are copied to CPU (slow path).