Supported switches and OpenFlow compatibility

Supported switches and OpenFlow compatibility
prev	Chapter 1 Introduction	next

For information about supported network switches, OpenFlow versions, and switch configuration requirements, see the HP VAN SDN Controller and Applications Support Matrix.



	CAUTION: OpenFlow switches in a controller domain should not be connected in a loop topology with switches outside the domain. Allowing such connections can create broadcast loops inside the OpenFlow network. For more on packet-forwarding decisions, see “Hybrid mode for controlling packet-forwarding”.

OpenFlow requirements

The controller must be connected to a network that includes one or more switches configured to run OpenFlow. HP recommends that you plan and implement the switch OpenFlow configurations before connecting the controller to the network.



	NOTE: OpenFlow switches in the network must be configured to allow control by the HP VAN SDN Controller. In a controller domain, including a switch that does not support OpenFlow or allow control by the HP VAN SDN Controller creates separate clusters of OpenFlow networks. Running the OpenFlow control mode on a specified switch VLAN disrupts the traffic on that VLAN until the controller configures the required flow rules in the switch using the OpenFlow controller API. You should create a separate VLAN for an OpenFlow control plane. For information on configuring OpenFlow, see the latest OpenFlow Administration Guide for your switch.

IPv6 traffic

IPv6 traffic running in the data plane of an OpenFlow network is supported when the controller is operating with hybrid mode set to “true” (the default). In this state the controller is not aware of the IPv6 traffic. However, with hybrid mode set to “false” (all packets sent to the controller), the controller drops IPv6 packets, and they do not reach their destinations. For more information, see the release notes.