Supported OpenFlow messages
OpenFlow messages
| Message type | Supported |
|---|---|
| OFPT_HELLO | Yes |
| OFPT_ERROR | Yes |
| OFPT_ECHO_REQUEST | Yes |
| OFPT_ECHO_REPLY | Yes |
| OFPT_EXPERIMENTER | No |
| OFPT_FEATURES_REQUEST | Yes |
| OFPT_FEATURES_REPLY | Yes |
| OFPT_GET_CONFIG_REQUEST | No |
| OFPT_GET_CONFIG_REPLY | No |
| OFPT_SET_CONFIG | No |
| OFPT_PACKET_IN | Yes |
| OFPT_FLOW_REMOVED | Yes |
| OFPT_PORT_STATUS | Yes |
| OFPT_PACKET_OUT | Yes |
| OFPT_FLOW_MOD | Yes |
| OFPT_GROUP_MOD | Yes |
| OFPT_PORT_MOD | No |
| OFPT_TABLE_MOD | No |
| OFPT_MULTIPART_REQUEST | Yes |
| OFPT_MULTIPART_REPLY | Yes |
| OFPT_BARRIER_REQUEST | Yes |
| OFPT_BARRIER_REPLY | Yes |
| OFPT_QUEUE_GET_CONFIG_REQUEST | No |
| OFPT_QUEUE_GET_CONFIG_REPLY | No |
| OFPT_ROLE_REQUEST | Yes |
| OFPT_ROLE_REPLY | Yes |
| OFPT_GET_ASYNC_REQUEST | Yes |
| OFPT_GET_ASYNC_REPLY | Yes |
| OFPT_SET_ASYNC | Yes |
| OFPT_METER_MOD | Yes |
Hello-reply message
When a connection is initiated, the controller sends a hello message with a transaction ID. When the switch receives the hello message sent by the controller, it replies with another hello message using the same transaction ID as the received hello message. There are two hello messages sent from the switch to the controller during the connection establishment. Use the following command to disable the second hello message for unexpected interruption to the connection to the controller.
device(config) # no openflow hello-reply disable
The second hello message is enabled by default.
Packet-in message
When the default action or flow is send-to-controller, traffic is sent to the controller through the packet-in message. The VLAN ID for the packet is included in the OFPXMT_OFB_VLAN_VID match field of the packet-in message. Packet-in messages are handled as described below: