Considerations and limitations for group tables

You must take into account the following when you configure group tables for OpenFlow flows.

For configuring group table

  • Brocade devices support all group types in the OpenFlow 1.3 specification.
  • The only action allowed in an action bucket is an output port, other supported actions can be included before group table.
  • Each action bucket can have only one output port.
  • Each OpenFlow port can be a part of any number of groups.
  • A group entry can include ports from different slots and ports with different speed.
  • Group tables are not impacted based on the OpenFlow type on interface (Layer 2 or Layer 3 or Layer23 and hybrid interfaces).
  • In order to disabling OpenFlow on interfaces, the interface must be removed from any group entry first.

Limitations

For configuring OpenFlow, consider the following limitations.

  • Watch_group is not supported in Fast failover group type.
  • PBR or Transparent VLAN flooding cannot be configured along with the group table, when OpenFlow 1.3 is enabled and vice versa.

Following are the additional limitations for a specific group type.

For group All

To multicast flow matching traffic to all action buckets, all action buckets will be executed every time for the group All.

  • Packet is replicated for the output port in each bucket. Only one packet is processed for each bucket of the group.

For group Indirect

It executes one defined action bucket in a group. Only one action bucket can exist and it will be executed every time.

  • Group Indirect supports one and only one bucket in each group entry.

For group Select

To load balance flow-matching traffic to all action buckets, one of the action buckets is chosen each time for the group Select.

  • The only action allowed is output port.
  • Weighted load balancing for group Select is not supported.
  • Group chaining is not supported.
  • Individual bucket statistics is not supported.

For group Fast failover

It executes the first live bucket. Each action bucket associated with a specific port or group determines the liveness of the bucket.

  • The buckets are selected in the defined sequence.
  • On a stack unit Failover, traffic convergence will take up to 2.5 to 3 seconds.
  • If no buckets are live, packets are dropped.