Configuring OpenFlow Software-Defined Networking (SDN) was developed to meet the growing requirements of virtualization technologies and data networks. SDN uses software to separate controlling functions from data forwarding, and provides simple, flexible device operations and high extensibility. OpenFlow is the communication interface between a controller and network devices to implement SDN.
OpenFlow supports the following types of ports: • Physical port—Corresponds to a hardware interface of a switch, such as an Ethernet interface. A physical port can be either an ingress port or an output port. • Logical port—Does not correspond to a hardware interface of a switch and might be defined by non-OpenFlow methods, such as an aggregate interface.
OpenFlow flow table An OpenFlow switch matches packets against one or more user-defined flow tables. A flow table contains flow entries, and packets are matched based on the matching precedence of flow entries. OpenFlow flow tables include the following types: •...
Page 8
(Required.) Output—The Output action forwards a packet to the specified OpenFlow port. OpenFlow switches must support forwarding packets to physical ports, logical ports, and reserved ports. (Required.) Drop—There is no explicit action to represent drops. Packets whose action sets have no output actions are dropped. Typically, packets are dropped due to empty instruction sets, empty action sets, or the executing a Clear-Actions instruction.
Group table The ability for a flow entry to point to a group enables OpenFlow to represent additional methods of forwarding. A group table contains group entries. Figure 4 Group entry components A group entry contains the following fields: • Group Identifier—A 32 bit unsigned integer uniquely identifying the group.
Page 10
The OpenFlow protocol supports the following message types: controller-to-switch, asynchronous, and symmetric. Each message type has its own subtypes. Controller-to-Switch messages IMPORTANT: Support for Controller-to-Switch messages varies by device mode. Controller-to-Switch messages are initiated by the controller and used to directly manage or inspect the state of the switch.
the buffer ID. Then, the controller sends a Packet-out message to direct the switch to process the packet. • Flow-Removed—Inform the controller about the removal of a flow entry from a flow table. These are generated due to a controller flow delete request or the switch flow expiry process when one of the flow timeouts is exceeded.
Tasks at a glance (Optional.) Enabling an OpenFlow instance to perform QinQ tagging for double-tagged packets passing an extensibility flow table (Optional.) Disabling logging for successful flow table modifications (Optional.) Refreshing all Layer 3 flow entries in the MAC-IP flow table for an OpenFlow instance Configuring OpenFlow instances Creating an OpenFlow instance Step...
Creating flow tables for an OpenFlow instance Step Command Remarks Enter system view. system-view Enter OpenFlow instance openflow instance instance-id view. By default, an OpenFlow instance contains one extensibility flow table with an ID of 0. An OpenFlow instance supports only one MAC-IP flow table and one extensibility flow table.
Step Command Remarks Enter OpenFlow instance view. openflow instance instance-id controller mode { multiple | By default, the controller mode Set the controller mode. single } is multiple. Setting the maximum number of flow entries for an extensibility flow table You can set the maximum number of flow entries that an extensibility flow table supports.
Configuring OpenFlow to forbid MAC address learning Step Command Remarks Enter system view. system-view Enter OpenFlow instance openflow instance instance-id view. By default, MAC address learning is allowed for VLANs associated Forbid address with an OpenFlow instance. learning VLANs mac-learning forbidden associated with The configuration does not take...
Step Command Remarks view. By default, the datapath ID of an OpenFlow instance contains the instance ID and the bridge MAC Set the datapath ID. datapath-id id address of the device. The upper 16 bits are the instance ID and the lower 48 bits are the bridge MAC address of the device.
Configuring controllers and main connections An OpenFlow switch supports up to 64 controllers. However, the OpenFlow channel between the OpenFlow switch and each controller can have only one main connection. The main connection processes control messages to complete tasks such as deploying entries, obtaining data, and sending information.
Step Command Remarks Enter system view. system-view Enter OpenFlow instance openflow instance instance-id view. default, connection detection interval is 5 seconds. Set the connection detection controller echo-request interval As a best practice to reduce the interval. interval-value CPU load, set the connection detection interval to a large value.
Enabling an OpenFlow instance to perform QinQ tagging for double-tagged packets passing an extensibility flow table IMPORTANT: This feature is available in Release 1121 and later. By default, a double-tagged packet becomes single-tagged after it passes an extensibility flow table. Perform this task to allow double-tagged packets to keep double-tagged after the packets pass an extensibility flow table.
To refresh all Layer 3 flow entries in the MAC-IP flow table for an OpenFlow instance: Step Command Enter system view system-view Enter OpenFlow instance view. openflow instance instance-id Refresh all Layer 3 flow entries in the MAC-IP refresh ip-flow flow table.
Appendixes Appendix A Application restrictions Matching restrictions VLAN matching Table 1 describes the VLAN matching restrictions when an OpenFlow instance is associated with VLANs. Table 1 VLAN matching VLAN Mask Matching packets All packets in the VLANs that are associated the OpenFlow instance.
Instruction type Restrictions The action list of the Apply-Actions instruction cannot include multiple Output actions. Apply-Actions When the action list of the Apply-Actions instruction includes only one Output action, the switch processes the action list as described in "Restrictions for merging the action list into the action set."...
Output port If the output port of a Packet-out packet is the Flood or All reserved port, the switch processes the packet as follows: • When the output port is the Flood reserved port: If the Packet-out packet has a VLAN tag, the switch broadcasts the packet within the VLAN. If the Packet-out packet has no VLAN tag and the ingress port is a physical or logical port, the switch tags the packet with the PVID of the ingress port.
The controller cannot modify the table-miss flow entry through the Modify request. The controller can only modify the table-miss flow entry through the Add request. The controller can modify or delete the table-miss flow entry only through the strict version of the Modify or Delete request.
Support items Capabilities address to the MAC address of the virtual interface of the VLAN to which the output port belongs. • Decrement TTL by one. • Goto-Table—When the switch has multiple tables, the switch adds this instruction by default if the controller does not deploy it. •...
• Drop—Drop the packet. • Controller—Send the packet to the controller. • Normal—Forward the packet to the normal pipeline. Dynamic aware On an OpenFlow switch that supports MAC-IP flow tables, you can configure OpenFlow to support querying and deleting dynamic MAC address flow entries. The controller can query and delete dynamic MAC address flow entries by specifying a VLAN, a MAC address, or the combination of a MAC address and a VLAN.
Appendix C VLAN tagging and untagging flow tables IMPORTANT: This feature is available in Release 1121 and later. Capabilities supported by the VLAN tagging flow table The controller must include the required match fields and actions and can include the optional match fields and actions in the flow entries deployed to the VLAN tagging flow table.
Page 30
Item Capabilities The VLAN untagging flow table can optionally support the inner vlan match field Optional match fields that matches the inner VLAN tag of double-tagged packets. The following actions in the action list of the Apply-Actions instruction must be applied immediately: Required actions •...
Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.
Network topology icons Convention Description Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...
For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,...
Page 35
part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
Need help?
Do you have a question about the FlexNetwork 5510 HI Series and is the answer not in the manual?
Questions and answers