openflow-spec-v1.1.0资源-CSDN文库

需积分: 9 191 浏览量 2012-08-25 10:43:31 上传评论收藏 663KB PDF 举报

标题：openflow-spec-v1.1.0 描述与关键词：OpenFlow技术是网络领域的一项重要创新，旨在实现网络的可编程性和灵活性。OpenFlow协议允许控制器直接与网络设备（如交换机）通信，从而控制数据包的转发路径。这份文档详细介绍了OpenFlow版本1.1.0的规范，包括其架构、组件、表格结构、匹配机制以及消息处理流程等关键知识点。 ### 开放流交换机规范概览 #### 引言 OpenFlowSwitchSpecificationVersion1.1.0实施于2011年2月28日，该版本引入了对网络资源更精细的控制能力，以及增强了安全性和性能方面的特性。通过定义一套标准化的接口和协议，OpenFlow使得网络硬件可以被软件控制器统一管理，极大地提高了网络的敏捷性和效率。 #### 交换机组件在OpenFlow架构中，交换机被视为一种可编程的中间件，它包含多个组件，如流表、组表、匹配字段、计数器、指令集、动作集合等，这些组件协同工作，实现数据包的高效转发和处理。 #### OpenFlow表格 - **流表**：流表是OpenFlow的核心组件之一，用于存储流条目。每个流条目都包含一组匹配规则和对应的处理动作，当数据包到达时，会根据这些规则进行匹配，并执行相应的动作。 - **组表**：组表用于实现更复杂的流量处理策略，如负载均衡、冗余备份等。组表中的条目包含一组动作桶，每个动作桶可以指向不同的动作或下一跳地址。 - **匹配字段**：定义了数据包中哪些字段可用于匹配，包括源MAC地址、目标MAC地址、IP地址、TCP/UDP端口等。 - **计数器**：用于统计流表和组表中条目的数据包数量和字节数，为网络监控和分析提供依据。 - **指令集**：定义了如何处理匹配到的流条目，包括写入头部字段、设置队列属性等。 - **动作集合**：规定了当数据包匹配成功后，可以执行的一系列操作，如转发、丢弃、修改头信息等。 #### OpenFlow通道 OpenFlow通道是控制器与交换机之间的通信渠道，采用TCP/IP协议，确保了高可靠性和安全性。该章节详细描述了连接建立、中断处理、加密机制以及消息处理流程等内容。 #### 消息处理 OpenFlow协议定义了多种消息类型，包括控制消息、异步消息和对称消息。控制消息用于初始化、配置和修改交换机状态；异步消息用于通知控制器网络事件，如数据包到达、流表变化等；对称消息用于握手、回显请求/响应等通信控制。 ### OpenFlow协议细节 - **OpenFlowHeader**：所有OpenFlow消息都以一个标准的头开始，包含了消息长度、类型、事务ID等信息。 - **PortStructures**：描述了端口相关的数据结构，包括端口状态、统计信息等。 - **QueueStructures**：定义了队列的配置和管理，用于控制数据包的排队和传输速率。 - **FlowMatchStructures**：描述了用于匹配数据包的流条目结构。 - **ActionStructures**：详细说明了数据包匹配后的动作数据结构。《OpenFlowSwitchSpeciﬁcationVersion1.1.0》是一份详尽的技术文档，深入解析了OpenFlow协议的各项特性和设计原则，对于理解现代网络架构、实现软件定义网络（SDN）具有重要意义。无论是网络工程师还是科研人员，掌握这份规范都是理解和应用OpenFlow技术的基础。

资源推荐

资源详情

资源评论

OpenFlow Switch Speciﬁcation

Version 1.1.0 Implemented ( Wire Protocol 0x02 )

February 28, 2011

Contents

1 Introduction 3

2 Switch Components 3

3 Glossary 4

4 OpenFlow Tables 5

4.1 Flow Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4.1.1 Pipeline Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4.2 Group Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.2.1 Group Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.3 Match Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.4 Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.5 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.6 Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.7 Action Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.8 Action List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.9 Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.9.1 Default values for ﬁelds on push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5 OpenFlow Channel 16

5.1 OpenFlow Protocol Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5.1.1 Controller-to-Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.1.2 Asynchronous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.1.3 Symmetric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5.2 Connection Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5.3 Connection Interruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5.4 Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.5 Message Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.6 Flow Table Modiﬁcation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.7 Flow Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.8 Group Table Modiﬁcation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

A The OpenFlow Protocol 24

A.1 OpenFlow Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

A.2 Common Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

A.2.1 Port Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

A.2.2 Queue Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

A.2.3 Flow Match Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

OpenFlow Switch Speciﬁcation Version 1.1.0 Implemented

A.2.4 Flow Instruction Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

A.2.5 Action Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

A.3 Controller-to-Switch Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

A.3.1 Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

A.3.2 Switch Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

A.3.3 Flow Table Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

A.3.4 Modify State Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

A.3.5 Queue Conﬁguration Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

A.3.6 Read State Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

A.3.7 Packet-Out Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

A.3.8 Barrier Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

A.4 Asynchronous Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

A.4.1 Packet-In Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

A.4.2 Flow Removed Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

A.4.3 Port Status Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

A.4.4 Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

A.5 Symmetric Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

A.5.1 Hello . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

A.5.2 Echo Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

A.5.3 Echo Reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

A.5.4 Experimenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

B Credits 56

List of Tables

1 Main components of a ﬂow entry in a ﬂow table. . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 A group entry consists of a group identiﬁer, a group type, counters, and a list of action buckets. 7

3 Fields from packets used to match against ﬂow entries. . . . . . . . . . . . . . . . . . . . . . . 8

4 Field lengths and the way they must be applied to ﬂow entries. . . . . . . . . . . . . . . . . . 10

5 List of counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 Push/pop tag actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

7 Set-Field actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

8 Existing ﬁelds that may be copied into new ﬁelds on a push action. . . . . . . . . . . . . . . . 16

9 Match combinations for VLAN tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

List of Figures

1 An OpenFlow switch communicates with a controller over a secure connection using the Open-

Flow protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Packet ﬂow through the processing pipeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Flowchart detailing packet ﬂow through an OpenFlow switch. . . . . . . . . . . . . . . . . . . 8

4 Flowchart showing how match ﬁelds are parsed for matching. . . . . . . . . . . . . . . . . . . 9

OpenFlow Switch Speciﬁcation Version 1.1.0 Implemented

1 Introduction

This document describes the requirements of an OpenFlow Switch. We recommend that you read the latest

version of the OpenFlow whitepaper before reading this speciﬁcation. The whitepaper is available on the

OpenFlow Consortium website (http://openflow.org). This speciﬁcation covers the components and the

basic functions of the switch, and the OpenFlow protocol to manage an OpenFlow switch from a remote

controller.

Controller

Flow

Table

Flow

Table

Secure

Channel

...

Pipeline

OpenFlow Switch

OpenFlow Protocol

Group

Table

Figure 1: An OpenFlow switch communicates with a controller over a secure connection using the OpenFlow

protocol.

2 Switch Components

An OpenFlow Switch consists of one or more ﬂow tables and a group table, which perform packet lookups

and forwarding, and an OpenFlow channel to an external controller (Figure 1). The controller manages

the switch via the OpenFlow protocol. Using this protocol, the controller can add, update, and delete ﬂow

entries, both reactively (in response to packets) and proactively.

Each ﬂow table in the switch contains a set of ﬂow entries; each ﬂow entry consists of match ﬁelds,

counters, and a set of instructions to apply to matching packets (see 4.1).

Matching starts at the ﬁrst ﬂow table and may continue to additional ﬂow tables (see 4.1.1). Flow

entries match packets in priority order, with the ﬁrst matching entry in each table being used (see 4.4). If a

matching entry is found, the instructions associated with the speciﬁc ﬂow entry are executed. If no match

is found in a ﬂow table, the outcome depends on switch conﬁguration: the packet may be forwarded to the

controller over the OpenFlow channel, dropped, or may continue to the next ﬂow table (see 4.1.1).

Instructions associated with each ﬂow entry describe packet forwarding, packet modiﬁcation, group

table processing, and pipeline processing (see 4.6). Pipeline processing instructions allow packets to be

sent to subsequent tables for further processing and allow information, in the form of metadata, to be

OpenFlow Switch Speciﬁcation Version 1.1.0 Implemented

communicated between tables. Table pipeline processing stops when the instruction set associated with a

matching ﬂow entry does not specify a next table; at this point the packet is usually modiﬁed and forwarded

(see 4.7).

Flow entries may forward to a port. This is usually a physical port, but it may also be a virtual

port deﬁned by the switch or a reserved virtual port deﬁned by this speciﬁcation. Reserved virtual ports

may specify generic forwarding actions such as sending to the controller, ﬂooding, or forwarding using

non-OpenFlow methods, such as “normal” switch processing (see 4.9), while switch-deﬁned virtual ports

may specify link aggregation groups, tunnels or loopback interfaces (see 4.9).

Flow entries may also point to a group, which speciﬁes additional processing (see 4.2). Groups rep-

resent sets of actions for ﬂooding, as well as more complex forwarding semantics (e.g. multipath, fast

reroute, and link aggregation). As a general layer of indirection, groups also enable multiple ﬂows to forward

to a single identiﬁer (e.g. IP forwarding to a common next hop). This abstraction allows common output

actions across ﬂows to be changed eﬃciently.

The group table contains group entries; each group entry contains a list of action buckets with spe-

ciﬁc semantics dependent on group type (see 4.2.1). The actions in one or more action buckets are applied

to packets sent to the group.

Switch designers are free to implement the internals in any way convenient, provided that correct

match and instruction semantics are preserved. For example, while a ﬂow may use an all group to forward

to multiple ports, a switch designer may choose to implement this as a single bitmask within the hardware

forwarding table. Another example is matching; the pipeline exposed by an OpenFlow switch may be

physically implemented with a diﬀerent number of hardware tables.

3 Glossary

This section describes key OpenFlow speciﬁcation terms:

• Byte: an 8-bit octet.

• Packet: an Ethernet frame, including header and payload.

• Pipeline: the set of linked tables that provide matching, forwarding, and packet modiﬁcations in an

OpenFlow switch.

• Port: where packets enter and exit the OpenFlow pipeline. May be a physical port, a virtual port

deﬁned by the switch, or a virtual port deﬁned by the OpenFlow protocol. Reserved virtual ports are

ports reserved by this speciﬁcation (see 4.9). Switch-deﬁned virtual ports are higher level abstractions

that may be deﬁned in the switch using non-OpenFlow methods (e.g. link aggregation groups, tunnels,

loopback interfaces).

• Match Field: a ﬁeld against which a packet is matched, including packet headers, the ingress port,

and the metadata value.

• Metadata: a maskable register value that is used to carry information from one table to the next.

• Instruction: an operation that either contains a set of actions to add to the action set, contains a list

of actions to apply immediately to the packet, or modiﬁes pipeline processing.

• Action: an operation that forwards the packet to a port or modiﬁes the packet, such as decrementing

the TTL ﬁeld. Actions may be speciﬁed as part of the instruction set associated with a ﬂow entry or

in an action bucket associated with a group entry.

OpenFlow Switch Speciﬁcation Version 1.1.0 Implemented

• Action Set: a set of actions associated with the packet that are accumulated while the packet is

processed by each table and that are executed when the instruction set instructs the packet to exit the

processing pipeline.

• Group: a list of action buckets and some means of choosing one or more of those buckets to apply on

a per-packet basis.

• Action Bucket: a set of actions and associated parameters, deﬁned for groups.

• Tag: a header that can be inserted or removed from a packet via push and pop actions.

• Outermost Tag: the tag that appears closest to the beginning of a packet.

4 OpenFlow Tables

This section describes the components of ﬂow tables and group tables, along with the mechanics of matching

and action handling.

4.1 Flow Table

A ﬂow table consists of ﬂow entries.

Match Fields Counters Instructions

Table 1: Main components of a ﬂow entry in a ﬂow table.

Each ﬂow table entry (see Table 1) contains:

• match ﬁelds: to match against packets. These consist of the ingress port and packet headers, and

optionally metadata speciﬁed by a previous table.

• counters: to update for matching packets

• instructions to modify the action set or pipeline processing

4.1.1 Pipeline Processing

OpenFlow-compliant switches come in two types: OpenFlow-only, and OpenFlow-hybrid. OpenFlow-only

switches support only OpenFlow operation, in those switches all packets are processed by the OpenFlow

pipeline, and can not be processed otherwise.

OpenFlow-hybrid switches support both OpenFlow operation and normal Ethernet switching op-

eration, i.e. traditional L2 Ethernet switching, VLAN isolation, L3 routing, ACL and QoS processing.

Those switches should provide a classiﬁcation mechanism outside of OpenFlow that routes traﬃc to either

the OpenFlow pipeline or the normal pipeline. For example, a switch may use the VLAN tag or input port

of the packet to decide whether to process the packet using one pipeline or the other, or it may direct all

packets to the OpenFlow pipeline. This classiﬁcation mechanism is outside the scope of this speciﬁcation.

An OpenFlow-hybrid switches may also allow a packet to go from the OpenFlow pipeline to the normal

pipeline through the NORMAL and FLOOD virtual ports (see 4.9).

The OpenFlow pipeline of every OpenFlow switch contains multiple ﬂow tables, each ﬂow table

containing multiple ﬂow entries. The OpenFlow pipeline processing deﬁnes how packets interact with those

ﬂow tables (see Figure 2). An OpenFlow switch with only a single ﬂow table is valid, in this case pipeline

processing is greatly simpliﬁed.

剩余55页未读，继续阅读

评论收藏

内容反馈

huobaozi

粉丝: 4
资源: 5

openflow-spec-v1.1.0

openflow 管理与配置协议 v1.1

openflow spec 1.00

openflow-spec-v1.0.0_CN.pdf

DisplayPort spec v1.1a

MTP spec v1.1

openflow-spec-v1.3

openflow-spec-1.3.0.pdf

openflow-spec-1.3.0.rar

openflow-spec-v1.3.0.zip

openflow-spec-v1.3.1

sdio spec v1.1

openflow spec 1.30

cdmi-spec:CDMI v1.0.2（这是一个 ISO 标准），v1.1 骨架服务器

openflow-spec-v1.2

wss-v1.1-spec-os-SOAPMessageSecurity

openflow-extensions-1.3.x-package.zip

openflow-switch-v1.5.0

openflow-master代码包

openflow协议v1.3.4

Go-openflow-是OpenFlow协议的纯Go实现

LoRaWAN-spec-v1.1.rar

openflow spec v1.3

mipi-i2c basic spec v1.1.1

openflow switch spec v1.5.1 (english version)

openflow-specification-v1.4.0-openflow协议规范

openflow-switch-v1.5.0.pdf

openflow-dmm:OpenfFlow-DMM 是 IPv6 分布式移动管理、rfc7333、rfc7429 的软件定义网络 (SDN) 实现。 OpenFlow-DMM 是使用 Ryu 作为基于组件的软件定义网络框架和 OpenFlow 1.3 作为 Southbound API 开发的

openflow 协议

MPLS-TP-OpenFlow-Protocol-Extensions-for-SPTN-1-0

OpenFlow-Enabling-Innovation-in-Campus-Network以及中文编程资料翻译.docx

最新资源