From the course: Practical Software-Defined Networking: 1 SDN and OpenFlow Quick Start

Unlock this course with a free trial

Join today to access over 22,600 courses taught by industry experts.

OpenFlow captures using Wireshark, part 2

OpenFlow captures using Wireshark, part 2

From the course: Practical Software-Defined Networking: 1 SDN and OpenFlow Quick Start

Start my 1-month free trial Buy for my team

OpenFlow captures using Wireshark, part 2

“

(wooshing thrum) - [David] This is one of multiple videos discussing OpenDaylight, Docker, and software-defined networking. One of the great things about being able to virtualize an OpenFlow network in GNS3 is that you can use WireShark to see what's going on. Next message is a BARRIER_REQUEST message. In the OpenFlow specification, we can see that a barrier request reply message, are used by the controller to ensure that message dependencies have been met or to receive notifications for completed operations. The controller wants to make sure that the switch has done what it's been told to do. So it sends a BARRIER_REQUEST, and we get a barrier response. Now we've got a ROLE_REQUEST from the controller to the switch, Role-Request messages are used by the controller to set the role of its OpenFlow channel, or to query that role. This is mostly useful when the switch connects to multiple controllers. So notice what the switch replies with? ROLE_EQUAL, and now we have a multipart…

Contents