Print
this page
Email this topic
Feedback
View PDF
Download EPUBOpenFlow Constraints and Limitations
The following list identifies limitations in this release that are the
result of hardware restrictions:
- Supported platforms do not implement both packet and byte counters simultaneously on dynamic ACL entries. Only packet counters are supported in current implementation. Counters are not supported with FDB flows.
- IN_PORT, FLOOD, NORMAL, and TOS/DSCP editing actions are not supported.
- Flows implemented using ACL hardware have platform limitations on the simultaneous combinations of flow match conditions that can be supported. These limitations are described in each version of ExtremeXOS Release Notes under the ACL description section, and in the Flow Match combinations table later in this section. When receiving a flow match combination that cannot be supported with the platform‘s ACL hardware, the switch generates an OpenFlow error message to the controller.
- Flows implemented using FDB entries are subject to normal FDB constraints, including platform-dependent table sizes.
- FDB-based OpenFlow idle-timeout follows the configured FDB Aging Time.
- ExtremeXOS OpenFlow supports one physical table, and ingress table. The concept of an emergency flow table is not supported.
- OpenFlow 1.0 describes a “secure fail” model where a switch immediately removes all of its flows when it loses connectivity to its controller. ExtremeXOS implements an “open fail” mode. In this mode the switch maintains its existing flows after losing connectivity to a controller. The "open fail" model is required to support controller high availability solutions.
- High availability for controllers is available through the following two mechanisms:
- Some controller clusters present a single IP address. The switch treats the cluster as a single controller.
- Some controller clusters present multiple IP addresses. The switch connects simultaneously to primary and secondary controller targets and enables the controllers to manage failover.
- OpenFlow, XNV, and IDM are all features that enable an external agent to control resources
on a switch. Due to their interaction models and resource requirements, these features are
mutually exclusive. The ExtremeXOS OpenFlow implementation prevents these services from being
simultaneously configured on the same port.
Note
There are other ExtremeXOS features that may not perform optimally when configured on OpenFlow enabled VLANs, or switch ports with OpenFlow supported VLANS. We make no attempt to prevent you from configuring additional services on these interfaces. - MPLS and pseudowire instances are limited by platform capabilities.
- Failover not supported on stacks or chassis.