0% found this document useful (0 votes)
54 views2 pages

Openflow Messages

Uploaded by

Poonam Tiware
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
54 views2 pages

Openflow Messages

Uploaded by

Poonam Tiware
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

OpenFlow is a protocol used in Software-Defined Networking (SDN) that allows the SDN

controller to interact with the network devices (switches and routers). OpenFlow messages
facilitate communication between the controller and network devices, enabling centralized
control of the network.
Here are the primary types of OpenFlow messages:
1. Controller-to-Switch Messages
These messages are initiated by the controller to manage and monitor the switch.
• Hello: Used to establish communication between the controller and the switch
during the connection phase.
• Features Request/Reply: The controller sends a features request, and the switch
replies with its capabilities and configuration.
• Configuration: The controller can configure the switch, such as setting maximum
packet sizes or other configuration parameters.
• Modify-State: These messages are used to modify the state of the switch, such as
adding or removing flow entries in flow tables.
o Flow Mod: Adds, removes, or modifies flow table entries on the switch.
o Port Mod: Modifies port behavior (e.g., enabling/disabling ports).
• Packet-Out: Sends a packet directly from the controller to the switch to be forwarded
to a specific port.
• Barrier: Ensures message dependencies are handled correctly by waiting for
outstanding messages to be processed before continuing.
2. Asynchronous (Switch-to-Controller) Messages
These messages are initiated by the switch and sent to the controller, often to notify it of
events.
• Packet-In: Sent when a packet arrives at the switch that does not match any flow
table entries. The switch forwards the packet to the controller for further decision-
making.
• Flow Removed: Notifies the controller that a flow has been removed from the
switch's flow table, either due to timeout or explicit removal.
• Port Status: Informs the controller about changes in port status (e.g., a port being up
or down).

Prof. Poonam Tiware Department of Computer Science & Engineering-(AI&ML) |APSIT


• Error: Sent to notify the controller of any errors, such as malformed requests or
failed operations.
3. Symmetric Messages
These messages can be sent either by the controller or the switch.
• Hello: Used to establish a session between the switch and controller.
• Echo Request/Reply: Used to measure the latency between the controller and switch
or check the liveliness of the connection.
• Experimenter: Vendor-specific extensions to the OpenFlow protocol, allowing for
custom functionality not covered by the standard message types.
These messages form the communication backbone of an SDN environment using OpenFlow,
enabling dynamic and centralized control of the network by allowing the controller to
manage network traffic through the switches.

Prof. Poonam Tiware Department of Computer Science & Engineering-(AI&ML) |APSIT

You might also like