close
keyboard_arrow_left
Table of Contents
- play_arrow OpenFlow Basic Configuration
- Configuring Support for OpenFlow on MX Series Routers
- Example: Enabling OpenFlow on MX Series Routers
- Configuring Support for OpenFlow on EX9200 Switches
- Example: Enabling OpenFlow on EX9200 Switches
- Configuring Support for OpenFlow on QFX5100 and EX4600 Switches
- Example: Enabling OpenFlow on QFX5100 and EX4600 Switches
- Configuring Support for OpenFlow on EX4550 Switches
- Example: Enabling OpenFlow on EX4550 Switches
- play_arrow Configuring OpenFlow Hybrid Interfaces
- Understanding OpenFlow Hybrid Interfaces on Devices Running Junos OS
- Configuring OpenFlow Hybrid Interfaces on MX Series Routers
- Example: Configuring OpenFlow Hybrid Interfaces on MX Series Routers
- Configuring OpenFlow Hybrid Interfaces on EX9200 Switches
- Example: Configuring OpenFlow Hybrid Interfaces on EX9200 Switches
- play_arrow Configuring OpenFlow Traffic Steering Across MPLS Networks
- play_arrow Configuration Statements and Operational Commands
list Table of Contents
Understanding OpenFlow Multipart Messages on Devices Running Junos OS
date_range
22-Nov-23
Note:
Multipart messages are supported only on Juniper Networks devices running OpenFlow v1.3.1 or later.
To more efficiently process large OpenFlow data responses, OpenFlow v1.3.1 introduces support for multipart messages.
The OpenFlow controller can use a multipart request message to request the following information:
Switch, group, or port descriptions
Single-flow, aggregate-flow, flow table, port, or group statistics
Group or table features
In response, a Juniper Networks device can send one or more multipart response messages wherein each message includes the same request identifier. In addition, each message in the sequence, except the last message, includes a flag that indicates more messages are to follow.
