Dell Force10 Software Defined Networking, Force10 S4810 Deployment Manual

Download

Page 1

Software-Defined Networking (SDN) Deployment Guide

Version 1.0

Page 2

Notes, Cautions, and Warnings

NOTE: A NOTE indicates important information that helps you make better use of your computer.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

Trademarks used in this text: Dell™, the Dell logo, Dell Boomi™, Dell Precision™ , OptiPlex™, Latitude™, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and Vostro™ are trademarks of Dell Inc. Intel®, Pentium®, Xeon®, Core® and Celeron® are registered trademarks of Intel Corporation in the U.S. and other countries. AMD

is a registered trademark and AMD Opteron™, AMD Phenom™ and AMD Sempron™ are trademarks of Advanced Micro Devices, Inc. Microsoft®, Windows®, Windows Server®, Internet Explorer®, MS-DOS®, Windows Vista® and Active Directory® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat® and Red Hat

Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell® and SUSE® are registered trademarks of Novell Inc. in the United States and other countries. Oracle® is a registered trademark of Oracle Corporation and/or its affiliates. Citrix®, Xen®, XenServer® and XenMotion® are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/or other countries. VMware

Virtual SMP

vMotion

vCenter

and

vSphere

are registered trademarks or

trademarks of VMware, Inc. in the United States or other countries.

IBM

is a registered trademark of International Business Machines

Corporation.

2013–01

Rev. A0X

Page 3

Contents

Notes, Cautions, and Warnings...................................................................................................2

1 OpenFlow 1.0 Support.................................................................................................................5

Unsupported OpenFlow Messages..........................................................................................................................5

Limitations.................................................................................................................................................................5

2 Exceptions....................................................................................................................................7

ACL Flow Exceptions................................................................................................................................................7

L3 Flow Exceptions...................................................................................................................................................7

L2 Flow Exceptions...................................................................................................................................................8

Learning Bridge (LB) Flow Exceptions .....................................................................................................................8

3 Flow Types....................................................................................................................................9

ACL Flows.................................................................................................................................................................9

L3 Flows....................................................................................................................................................................9

L2 Flows..................................................................................................................................................................10

Learning Bridge (LB) Flows.....................................................................................................................................10

Max Limits...............................................................................................................................................................10

4 Flow Setup..................................................................................................................................13

Sample Topology....................................................................................................................................................13

ACL Flows...............................................................................................................................................................14

L3 Flows..................................................................................................................................................................15

L2 Flows..................................................................................................................................................................16

Learning Bridge (LB) Flows.....................................................................................................................................17

Packet Trace...........................................................................................................................................................17

5 Configuring ACL CAM Carving on S4810...............................................................................19

6 Configuring ACL CAM Carving on Z9000...............................................................................21

7 OpenFlow Instances.................................................................................................................23

8 OpenFlow Interfaces................................................................................................................25

OF Ports...................................................................................................................................................................25

OF VLANs................................................................................................................................................................25

9 SDN Commands.........................................................................................................................27

Page 4

connect retry-interval.............................................................................................................................................27

Z-Series, S4810.................................................................................................................................................27

controller ................................................................................................................................................................28

Z-Series, S4810.................................................................................................................................................28

debug openflow packets........................................................................................................................................28

Z-Series, S4810.................................................................................................................................................28

flow-map.................................................................................................................................................................30

Z-Series, S4810.................................................................................................................................................30

interface-type.........................................................................................................................................................30

Z-Series, S4810.................................................................................................................................................30

learning-switch-assist............................................................................................................................................31

Z-Series, S4810.................................................................................................................................................31

multiple-fwd-table enable.......................................................................................................................................31

Z-Series, S4810.................................................................................................................................................31

of-instance (Interface)............................................................................................................................................32

Z-Series, S4810.................................................................................................................................................32

openflow of-instance..............................................................................................................................................33

Z-Series, S4810.................................................................................................................................................33

show openflow.......................................................................................................................................................34

Z-Series, S4810.................................................................................................................................................34

show openflow flows..............................................................................................................................................35

Z-Series, S4810.................................................................................................................................................35

shutdown (OpenFlow Instance)..............................................................................................................................35

Z-Series, S4810.................................................................................................................................................35

Page 5

OpenFlow 1.0 Support

OpenFlow (OF) 1.0 [STD-1] is supported on the S4810 and Z9000 platforms.

Unsupported OpenFlow Messages

The following section provides a list of OpenFlow messages that are not supported.

Table 1. Unsupported OpenFlow Messages

Message System Response

OFPT_SET_CONFIG

This message is ignored by the switch.

OFPT_QUEUE_GET_CONFIG_REQUEST

OFPT_ERROR is generated in response.

OFPT_PORT_MOD

OFPT_ERROR is generated in response.

Emergency Flows (OFPFF_EMERG) OFPT_ERROR is generated in response.

Queue Statistics (OFPST_QUEUE) OFPT_ERROR is generated in response.

For supported flow-match and flow action parameters for each flow type, refer to FlowTypes.

The following section provides a list of actions that are not supported for any flow types. All of the following commands generate an OFPT_ERROR message.

• OFPAT_STRIP_VLAN

• OFPAT_SET_NW_SRC (set src-ip)

• OFPAT_SET_NW_DST (set dst-ip)

• OFPAT_SET_TP_SRC (set tcp/udp src-port)

• OFPAT_SET_TP_DST (set tcp/udp dst-port)

• OFPAT_ENQUEUE

• OFPAT_OUTPUT to OFPP_IN_PORT

• OFPAT_OUTPUT to OFPP_TABLE

• OFPAT_OUTPUT to OFPP_NORMAL

• OFPAT_OUTPUT to OFPP_LOCAL

Limitations

• OFPAT_OUTPUT to OFPP_FLOOD and OFPP_ALL are supported on the S4810 only. These commands are not currently supported on Z9000.

• Multiple output ports are supported on S4810 only. Multiple output ports are not currently supported on Z9000.

• The set/modify actions must precede the “output ports” actions. This means that the switch cannot transmit different copies if you specify multiple output ports.

Page 6

Page 7

Exceptions

This section describes the constraints of OpenFlow.

• Dell Force10 switches can operate as Hybrid switches (switches running OpenFlow and legacy functions simultaneously). You cannot enable Legacy functionality (switching and routing) on OF ports or OF VLANs, as these interfaces are controlled by an OpenFlow controller and are not available.

• Stacking OpenFlow switches is not supported for the S4810. If stacking is configured but disabled in preparation for future stacking, the stack unit number must be zero to enable OpenFlow on S4810 switches.

• For OF ports and OF VLANs, the VLAN IDs used for OpenFlow must be unique; the VLAN IDs cannot be used for legacy functionality on the same switch.

• Dell Force10 does not recommend using global spanning tree protocol (STP) instances on ports with both legacy VLANs and OF VLANs.

• Transport Layer Security (TLS) connections are not supported.

• Because controllers typically run their own version of link layer discovery protocol (LLDP), legacy LLDP should be disabled by the administrator on OF ports.

• To avoid session timeout issues if the system clock is changed, all existed OF instances should be disabled, then re-enabled .

• Controller high availability (HA) is not supported.

• Emergency flows are not supported.

• Packet buffering is not supported.

• Data Center Bridging (DCB) and iSCSI are not supported on OpenFlow interfaces.

• The following packet types can only be copied to the controller and cannot be forwarded from a physical switch port:

– STP BDPU

– LLDP

– GVRP

– ARP Replies

– 802.1x frames

– untagged broadcast packets received on an OF port

ACL Flow Exceptions

• Flooding (action “output=all” or “output=flood”) is supported on S4810 only.

• By default, ACL flows override flows installed in the L2 or L3 tables.

• ARP opcode, sender IP, and target IP matching are not supported.

L3 Flow Exceptions

• Non-zero integers for the idle timeout are not supported and are ignored for L3 flows; L3 flows are not aged out.

• For L3 flows, flow priority is not applicable; instead, the dst-ip network mask length is used to prioritize the flow. For example, a L3 flow with a dst-ip network mask length of 32 has priority over a flow with a dst-ip network mask length of 31.

Page 8

• TTL is decremented for traffic forwarded using L3 flows.

L2 Flow Exceptions

• If you specify a non-zero idle timeout value for an L2 flow, the flow is aged out according to the MAC address table aging time configured on the switch if there is no activity or traffic. The idle timeout value specified in individual flows is ignored. If the idle timeout value is zero, the flow is not aged.

• Flow priority is ignored for L2 flows.

Learning Bridge (LB) Flow Exceptions

• If you specify a non-zero idle timeout value for an LB flow, the flow is aged out according to the MAC address table aging time configured on the switch if there is no activity or traffic. The idle timeout values specified in individual flows are ignored. If the idle timeout value is zero, the flow is not aged.

• Flow priority is ignored for LB flows.

• Dell Force10 does not recommend station moves in an LB flow configuration.

• Parallel links or paths may not work in an LB flow configuration; Dell Force10 recommends using port channels instead.

Page 9

Flow Types

Dell Force10 switches support four types of flows:

• Access Control List (ACL)

• L2

• L3

• Learning Bridge (LB)

The following sections describe the mandatory match fields, optional match fields, mandatory actions, and optional actions for each flow type.

ACL Flows

Parameter Type Parameters

Mandatory match fields

None; any of the match parameters can be wildcards.

Optional match fields All 12 match fields defined in OpenFlow (OF) 1.0 are supported.

Mandatory actions None.

Optional actions

• set_vlan_id

• set_vlan_pcp

• set_dl_src (set src-mac)

• set_dl_dst (set dst-mac)

• set_nw_tos

• output to one or more switch ports

NOTE: For output action limitations, refer to OF 1.0 Support.

L3 Flows

Parameter Type Parameters

Mandatory match fields

• You must specify dl_dst (dst-mac) as the switch’s port mac.

• You must specify dl_type (ether-type) as 0x800.

Page 10

Parameter Type Parameters

Optional match fields

• nw_dst (dst-ip)

• All fields other than the ones listed in “Mandatory match fields” and “Optional match fields” must be wildcards.

Mandatory actions

• You must specify set_dl_src (set src-mac) as the port mac (local mac) for the swtich.

• set_dl_dst (set dst-mac)

• Single OFPAT_OUTPUT action to a switch port.

Optional actions OFPAT_SET_VLAN is optional for OpenFlow (OF) ports and mandatory for OF virtual local area

networks (VLANs).

L2 Flows

Parameter Type Parameters

Mandatory match fields

• dl_vlan (input vlan id)

• dl_dst (dst-mac)

Optional match fields All fields other than dl_vlan and dl_dst must be wildcards.

Mandatory actions Single OFPAT_OUTPUT action to a switch port.

Optional actions None.

Learning Bridge (LB) Flows

Parameter Type Parameters

Mandatory match fields

• dl_src (src-mac)

• dl_dst (dst-mac)

• LB flows will only be installed in the L2 table if bidirectional traffic is present.

Optional match fields All fields other than the ones listed in “Mandatory match fields” must be wildcards.

Mandatory actions Single OFPAT_OUTPUT action to a switch port.

Optional actions None.

Max Limits

This section defines the maximum number of permitted flow types. The number of available flow types varies depending on the type of flow.

• You can provision up to eight OF instances on each switch.

• The number of flows supported on each switch depends on the flow type.

Page 11

Flow Type Max Limit

ACL 256 or 512 (depending on ACL content addressable memory [CAM] carving)

L2 48,000

Learning Bridge (LB) 24,000

L3 6,000

Page 12

Page 13

Flow Setup

This chapter describes the configuration options required to set up flows.

Sample Topology

In the following sample topology, two OF instances are shown. of-instance 1 has an interface type of

port

and

demonstrates ACL and L3 flows. of-instance 2 has an interface type of

VLAN

and demonstrates ACL, L2, LB, and L3

flows. LB and L2 flows are supported on OF VLANs only.

Figure 1. SDN Sample Topology

Use the show running-config openflow of-instance 1 command to display the following information:

FTOS# show running-config openflow of-instance 1 ! openflow of-instance 1 controller 1 10.11.205.184 tcp flow-map l3 enable multiple-fwd-table enable no shutdown FTOS#

show openflow of-instance 1

Instance : 1 Admin State : Up

Interface Type : Port

DP Id : 00:01:00:01:e8:8b:1a:30 Forwarding Tbls : acl,mac,route Flow map : l3 LB assist : disabled EchoReq interval: 15 seconds Connect interval: 15 seconds Number of Flows : 1 (rt:1) Packets (acl) : Bytes (acl) : Controller 1 : TCP, 10.11.205.184/6633, connected (equal)

Page 14

Controller 2 : Port List : Te 0/7 (8), Te 0/31 (32) Vlan List : Vlan Mbr list :

To display information for the second OF instance, use the show running-config openflow of-instance 2 command:

FTOS# show running-config openflow of-instance 2 ! openflow of-instance 2 controller 1 10.11.205.184 tcp flow-map l2 enable flow-map l3 enable interface-type vlan learning-switch-assist enable multiple-fwd-table enable no shutdown FTOS#

show openflow of-instance 2

Instance : 2 Admin State : Up

Interface Type : Vlan

DP Id : 00:02:00:01:e8:8b:1a:30 Forwarding Tbls : acl,mac,route Flow map : l2,l3 LB assist : enabled EchoReq interval: 15 seconds Connect interval: 15 seconds Number of Flows : 0 Packets (acl) : Bytes (acl) : Controller 1 : TCP, 10.11.205.184/6633, connected (equal) Controller 2 : Port List :

Vlan List :

Vl 200

Vlan Mbr list :

Te 0/0 (1), Te 0/1 (2)

ACL Flows

By default, all flows are treated as ACL flows. No additional configuration is required to set up ACL flows. You can view per-flow and aggregate statistics for ACL flows using the show openflow of-instance and show openflow flows of-instance commands.

To clear these statistics, use the clear openflow statistics of-instance command . The following sample ACL flow was configured using a controller. It matches by dmac, ether-type, ip-protocol, and tcp-dst-port, then sets the VLAN ID to 111 and forwards the packet from Te 0/31.

FTOS#show openflow flows of-instance 1 Instance: 1, Table: acl, Flow: 1, Cookie: 0xa000003c435722 Priority: 32768, Internal Priority: 32768 Up Time: 0d 00:02:34, Hard Timeout: 0 seconds Idle Timeout: 0 seconds, Internal Idle Timeout: 0 seconds Packets: 1, Bytes: 64 Match Parameters: Valid Match: Etype,DMAC,IP proto,DPort In Port : * EType : ip SMAC : * DMAC : 00:11:11:11:11:11 VLAN id : * VLAN PCP : *

Page 15

IP TOS : * IP proto : udp Src IP : * Dest IP : * Src Port : * Dest Port : 8900 Actions: Set VLAN id: 111 Output: Te 0/31

FTOS#show openflow of-instance 1 Instance : 1 Admin State : Up Interface Type : Port DP Id : 00:01:00:01:e8:8b:1a:30 Forwarding Tbls : acl,mac,route Flow map : l3 LB assist : disabled EchoReq interval: 15 seconds Connect interval: 15 seconds Number of Flows : 1 (acl:1) Packets (acl) : 1 Bytes (acl) : 64 Controller 1 : TCP, 10.11.205.184/6633, connected (equal) Controller 2 : Port List : Te 0/7 (8), Te 0/31 (32) Vlan List : Vlan Mbr list :

For complete ACL flow formats, refer to FlowTypes .

L3 Flows

To use L3 flows, you must enable the multiple-fwd-table and flow-map l3 commands, as shown below. If you do not enable either of these commands, L3 flows are added to the ACL table.

FTOS#show running-config openflow of-instance 1 ! openflow of-instance 1 controller 1 10.11.205.184 tcp

flow-map l3 enable

multiple-fwd-table enable

no shutdown

The entry for dst-mac in the match field and set-src-mac in the action set must use the switch’s port MAC address. All ports on a Dell Force10 switch are associated with the same MAC address, which you can view using the show

interface command.

FTOS#show interfaces tengigabitethernet 0/0 TenGigabitEthernet 0/0 is up, line protocol is up Hardware is DellForce10Eth, address is 00:01:e8:8b:1a:32 Current address is 00:01:e8:8b:1a:32 ...

You can configure L3 flows on OF ports as well as on OF VLANs. You must specify the set-vlan-id option in the action set for OF VLANs. As shown in the following example, the L3 flow in of-instance 1 transmits packets from OF port Te 0/31:

FTOS#show openflow flows of-instance 1

Instance: 1, Table: route, Flow: 2, Cookie: 0xffffffffa17177b0 Priority: 32768, Internal Priority: 0 Up Time: 0d 00:00:13, Hard Timeout: 0 seconds Idle Timeout: 0 seconds, Internal Idle Timeout: 0 seconds

Page 16

Packets: -, Bytes: Match Parameters: Valid Match: Etype,DMAC,DIP In Port : * EType : ip SMAC : * DMAC : 00:01:e8:8b:1a:32 VLAN id : * VLAN PCP : * IP TOS : * IP proto : * Src IP : * Dest IP : 1.1.1.0/24 Src Port : * Dest Port : * Actions: Set SMAC: 00:01:e8:8b:1a:32 Set DMAC: 00:00:00:00:00:11 Output: Te 0/31

The following example shows the sample L3 flow in of-instance 2 transmitting packets from the OF VLAN port Te 0/1:

FTOS#show openflow flows of-instance 2

Instance: 2, Table: route, Flow: 3, Cookie: 0xffffffffa4cb6a2e Priority: 32768, Internal Priority: 0 Up Time: 0d 00:00:11, Hard Timeout: 0 seconds Idle Timeout: 0 seconds, Internal Idle Timeout: 0 seconds Packets: -, Bytes: Match Parameters: Valid Match: Etype,DMAC,DIP In Port : * EType : ip SMAC : * DMAC : 00:01:e8:8b:1a:32 VLAN id : * VLAN PCP : * IP TOS : * IP proto : * Src IP : * Dest IP : 2.2.2.2/32 Src Port : * Dest Port : * Actions: Set VLAN id: 200 Set SMAC: 00:01:e8:8b:1a:32 Set DMAC: 00:00:00:00:00:22 Output: Te 0/1

For complete L3 flow formats, refer to FlowTypes .

L2 Flows

L2 flows are only supported on OF VLANs. In the following example, of-instance 2 is used to demonstrate an L2 flow. To use the L2 flow table, you must enable the multiple-fwd-table and flow-map l2 commands, as shown below. If you do not enable either command , L2 flows are added to the ACL table.

FTOS#show running-config openflow of-instance 2 ! openflow of-instance 2 controller 1 10.11.205.184 tcp

flow-map l2 enable

flow-map l3 enable interface-type vlan learning-switch-assist enable multiple-fwd-table enable no shutdown

The example below demonstrates a sample flow in of-vlan 200:

FTOS#show openflow flows of-instance 2

Instance: 2, Table: mac, Flow: 4, Cookie: 0xffffffffac2dbbf2 Priority: 32768, Internal Priority: 0 Up Time: 0d 00:00:09, Hard Timeout: 0 seconds

Page 17

Idle Timeout: 0 seconds, Internal Idle Timeout: 0 seconds Packets: -, Bytes: Match Parameters: Valid Match: DMAC,Vid In Port : * EType : * SMAC : *

DMAC : 00:22:22:22:22:22

VLAN id : 200 VLAN PCP : * IP TOS : * IP proto : * Src IP : * Dest IP : * Src Port : * Dest Port : * Actions: Output: Te 0/1

For complete L2 flow formats, refer to FlowTypes .

Learning Bridge (LB) Flows

Learning bridge flows are only supported on OF VLANs. In the example below, of-instance 2 represents an LB flow. To use the LB flow table, you must enable the multiple-fwd-table and learning-switch-assist commands, as shown below. If you do not enable either command, LB flows are added to the ACL table.

FTOS#show running-config openflow of-instance 2 ! openflow of-instance 2 controller 1 10.11.205.184 tcp flow-map l2 enable flow-map l3 enable interface-type vlan

learning-switch-assist enable multiple-fwd-table enable

no shutdown

The example below shows a sample flow in of-vlan 200:

FTOS#show openflow flows of-instance 2 Instance: 2, Table: lb, Flow: 5, Cookie: 0xffffffffac2dbc22 Priority: 32768, Internal Priority: 0 Up Time: 0d 00:00:03, Hard Timeout: 0 seconds Idle Timeout: 0 seconds, Internal Idle Timeout: 0 seconds Packets: -, Bytes: Match Parameters: Valid Match: InPort,SMAC,DMAC,Vid In Port : Te 0/0 EType : * SMAC : 00:00:00:00:00:11 DMAC : 00:00:00:00:00:33 VLAN id : 200 VLAN PCP : * IP TOS : * IP proto : * Src IP : * Dest IP : * Src Port : * Dest Port : * Actions: Output: Te 0/1

For complete LB flow formats, refer to FlowTypes .

Packet Trace

Enable OpenFlow protocol packet tracing by using the debug openflow packets packet-type {of-id} command.

Page 18

Page 19

Configuring ACL CAM Carving on S4810

Dell Force10 switches can operate in Hybrid mode, which enables OpenFlow and legacy functionality on the same switch. By default, ACL CAM space is not allocated for OpenFlow. To enable OpenFlow, you must reserve CAM space for OpenFlow using the following commands.

NOTE: The commands to allocate CAM space for OpenFlow on S4810 differ from the commands used for Z9000.

1. Enter a value for cam-acl.

Select one of the following values for cam-acl:

– 0 (default): No space is allocated for OpenFlow. You must change this value to four or eight to enable

OpenFlow.

– 4: Allocates space for up to 242 flow entries (14 entries are reserved for internal purposes from the 256

available flows, leaving 242 entries for use by OpenFlow).

– 8: Allocates space for up to 498 flow entries (14 entries are reserved for internal purposes from the 512

available flows, leaving 498 entries for use by OpenFlow).

The following sample S4810 configuration reserves 512 entries for OpenFlow:

FTOS(conf)#cam-acl l2acl 1 ipv4acl 2 ipv6acl 0 ipv4qos 0 l2qos 2 l2pt 0 ipmacacl 0 vman-qos 0 ecfmacl 0

openflow 8 fcoeacl 0 iscsioptacl 0

2. Enter a value for cam-acl-vlan.

Select one of the following values for cam-acl-vlan:

– 0 (default): No space is allocated for OpenFlow. You must change this value to 1 to enable OpenFlow.

– 1: Enables OpenFlow functionality.

The following sample configuration shows a value of 1 for cam-acl-vlan:

FTOS(conf)#cam-acl-vlan vlanopenflow 1 vlaniscsi 1

NOTE: You must reboot the switch after changing the cam-acl and cam-vlan-acl values. If you do not reboot the switch, the configuration changes do not take effect.

If BMP 3.0 is enabled, use the command reload conditional nvram-cfg-change to perform a reload on the chassis to upgrade any configuration changes that have changed the NVRAM content.

Page 20

Page 21

Configuring ACL CAM Carving on Z9000

NOTE: The commands to allocate CAM space for OpenFlow on Z9000 differ from the commands used for S4810.

Enter a value for cam-acl.

Select one of the following values for cam-acl:

– 0 (default): No space is allocated for OpenFlow. You must change this value to four or eight to enable

OpenFlow.

– 4: Allocates space for up to 242 flow entries (14 entries are reserved for internal purposes from the 256

available flows, leaving 242 entries for use by OpenFlow).

– 8: Allocates space for up to 498 flow entries (14 entries are reserved for internal purposes from the 512

available flows, leaving 498 entries for use by OpenFlow).

The following sample Z9000 configuration reserves 512 entries for OpenFlow:

FTOS(conf)# cam-acl l2acl 2 ipv4acl 2 ipv6acl 0 ipv4qos 0 l2qos 1 l2pt 0 ipmacacl 0 vman-qos 0 ecfmacl 0

openflow 8

NOTE: For Z9000, the cam-acl-vlan value is set to 1 (enabled) by default; no additional configuration is required.

NOTE: You must reboot the switch after changing the cam-acl values. If you do not reboot the switch, the configuration changes do not take effect.

If BMP 3.0 is enabled, use the command reload conditional nvram-cfg-change to perform a reload on the chassis to upgrade any configuration changes that have changed the NVRAM content.

Page 22

Page 23

OpenFlow Instances

This section describes how you can use OpenFlow instances on a switch.

• You can use up to eight OpenFlow instances on a switch; the OF ID range is 1–8.

• Only Transmission Control Protocol (TCP) connections are supported on Dell Force10 switches. Transport Layer Security (TLS) connections are not supported.

• Currently, you can configure only one controller IP and one TCP port for each OF instance.

• The connection is established when you enable the OF instance using the no shut command.

NOTE: You cannot modify the OF instance while it is enabled. To make configuration changes, you must use the shut command on the OF instance, as shown below.

FTOS#show running-config openflow of-instance ! openflow of-instance 1 controller 1 10.11.205.184 tcp shutdown FTOS#

• The

show openflow of-instance command displays details on the instance, as shown below:

FTOS#show openflow of-instance 1

Instance : 1 Admin State : Down Interface Type : Port DP Id : 00:01:00:01:e8:8b:1a:30 Forwarding Tbls : acl Flow map : LB assist : disabled EchoReq interval: 15 seconds Connect interval: 15 seconds Number of Flows : 0 Packets (acl) : Bytes (acl) : Controller 1 : TCP, 10.11.205.184/6633, not-connected Controller 2 : Port List : Vlan List : Vlan Mbr list :

Page 24

Page 25

OpenFlow Interfaces

This section describes how you can apply OpenFlow to specific interfaces.

• You can use the S4810 and Z9000 as Hybrid switches, allowing both OpenFlow (OF) and legacy functionality simultaneously.

• By default, all ports are available for legacy functionality.

• To enable OpenFlow, associate a port or VLAN to an OF instance. You can only do this when the OF instance is disabled (in a “shut” state).

• OpenFlow is supported with link aggregation groups (LAGs); for example, you can configure port channel interfaces as OF ports or as members of OF VLANs.

OF Ports

The following configuration example associates two ports (Te 0/7 and Te 0/31) to of-instance 1:

FTOS(conf)#interface tengigabitethernet 0/7 FTOS(conf-if-te-0/7)#of-instance 1 FTOS(conf-if-te-0/7)#interface tengigabitethernet 0/31 FTOS(conf-if-te-0/31)#of-instance 1 FTOS(conf-if-te-0/31)#

To see the list of ports associated with an OF instance, use the show openflow of-instance command. The number displayed in parentheses is the port ID sent to the controller (for example., Te 0/7 is sent to the controller as ofport 8, as shown below).

FTOS#show openflow of-instance 1

Instance : 1 Admin State : Up Interface Type : Port DP Id : 00:01:00:01:e8:8b:1a:30 Forwarding Tbls : acl Flow map : LB assist : disabled EchoReq interval : 15 seconds Connect interval : 15 seconds Number of Flows : 1 (acl:1) Packets (acl) : 0 Bytes (acl) : 0 Controller 1 : TCP, 10.11.205.184/6633, connected (equal) Controller 2 : -

Port List :

Te 0/7 (8), Te 0/31 (32) Vlan List :

Vlan Mbr list :

OF VLANs

Instead of assigning an entire port to an OF instance, you can assign a VLAN to an OF instance. You must do this when the VLAN is created. You must enter OF VLAN members in the same way as a legacy VLAN.

Page 26

NOTE: You can only create OF VLANs when the associated instance is disabled (in a “shut” state).

There is an “interface-type” parameter in each instance. By default, this parameter is set to “port,” indicating that the instance is used for OF ports. To use an instance in OF VLANs, change this parameter to “vlan,” as shown below:

FTOS(conf)#openflow of-instance 1 FTOS(conf-of-instance-1)#interface-type vlan FTOS(conf-of-instance-1)#

To use both OF ports and OF VLANs, set the interface type to “any.”

NOTE: Dell Force10 does not recommend using the interface type “any” unless both OF ports and OF VLANs are required in a single instance. If you use the “any” interface type, the number of ACL flows available to the controller is reduced by half (for example, to 128 of 256 available entries or to 256 of 512 available entries).

The following configuration example associates VLAN 100 (with tagged members Te 0/0 and Te 0/1) to of-instance 1:

FTOS(conf)#interface vlan 100 of-instance 1 FTOS(conf-if-vl-100)#tagged tengigabitethernet 0/0 FTOS(conf-if-vl-100)#tagged tengigabitethernet 0/1 FTOS(conf-if-vl-100)#no shutdown FTOS(conf-if-vl-100)#

Use the show openflow of-instance command to display the OF VLANs and OF VLAN members associated with the OF instance, as shown below:

FTOS#show openflow of-instance

Instance : 1 Admin State : Up Interface Type : Vlan DP Id : 00:01:00:01:e8:8b:1a:30 Forwarding Tbls : acl Flow map : LB assist : disabled EchoReq interval: 15 seconds Connect interval: 15 seconds Number of Flows : 0 Packets (acl) : Bytes (acl) : Controller 1 : TCP, 10.11.205.184/6633, connected (equal) Controller 2 : Port List :

Vlan List : Vl 100 Vlan Mbr list : Te 0/0 (1), Te 0/1 (2)

Page 27

SDN Commands

The following commands are for Software Defined Networking (SDN) OpenFlow commands.

• connect retry-interval

• controller

• debug openflow packets

• flow-map

• interface-type

• learning-switch-assist

• multiple-fwd-table

• of-instance (Interface)

• openflow of-instance

• show openflow

• show openflow flows

• shutdown

connect retry-interval

Configure the timed interval (in seconds) that the OpenFlow (OF) instance will wait after requesting a connection with the OpenFlow controller.

Z-Series, S4810

Syntax

connect retry-interval interval

Parameter

interval

Enter the number of seconds the OF instance will wait after attempting to establish a connection with OF controller. Range is 10–

60.

Defaults 15 (seconds)

Command Modes OPENFLOW INSTANCE

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Usage Information

After the interval time lapses, the OpenFlow instance will reattempt to establish a connection to the OpenFlow controller.

Related Commands

openflow of-instance Create or modify an OpenFlow instance.

Page 28

controller

Specify the OpenFlow controller configuration that the OpenFlow instance uses to establish a connection.

Z-Series, S4810

Syntax

controller {controller-id}{ip-address}[port port-number]tcp

Parameter

controller-id

Enter the controller number (must be 1).

ip-address

Enter the IP address of the controller.

port

port-number

Enter the keyword port followed by the port number to use for the connection. Range is 1 to 65535.

Defaults Default port number for the TCP connection is 6633.

Command Modes OPENFLOW INSTANCE

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Usage Information

The controller number must be entered as 1 to enable OpenFlow. Currently, only TCP connection is supported.

Related Commands

openflow of-instance Create or modify an OpenFlow instance.

debug openflow packets

Enable debugging for OpenFlow packets.

Z-Series, S4810

Syntax

debug openflow packets {packet-type packet-type} of-instance {of-id}

Parameter

{packet-type

packet-type

}

Enter the keyword packet-type followed by one of the following packet types:

all Enable debugging for all packets.

barrier-reply Enable debugging for barrier-reply packets.

barrier-request Enable debugging for barrier-request

packets.

echo-reply Enable debugging for echo-reply packets.

echo-request Enable debugging for echo-request packets.

error Enable debugging for error packets.

Page 29

features-reply Enable debugging for features-reply

packets.

flow-mod Enable debugging for flow-mod packets.

flow-removed Enable debugging for flow-removed

packets.

get-config-reply Enable debugging for get-config-reply

packets.

get-configrequest

Enable debugging for get-config-request packets.

hello Enable debugging for hello packets.

packet-in Enable debugging for packet-in packets.

packet-out Enable debugging for packet-out packets.

port-mod Enable debugging for port-mod packets.

port-status Enable debugging for port-status packets.

queue-getconfig-reply

Enable debugging for queue-get-configreply packets.

queue-getconfig-request

Enable debugging for queue-get-configrequest packets.

set-config Enable debugging for set-config packets.

stats-reply Enable debugging for stats-reply packets.

stats-request Enable debugging for stats-request packets.

vendor Enable debugging for vendor packets.

of-instance {

of-id

} Enter the keyword of-instance followed by the OF instance ID.

Defaults None

Command Modes EXEC

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Usage Information

If debugging needs to be enabled for all packets, use the debug openflow packets packet-type all command.

Related Commands

reload conditional nvram-cfg-change

Page 30

flow-map

Specify if flows installed by the controller should be interpreted by the switch for placement in L2 or L3 tables.

Z-Series, S4810

Syntax

flow-map {l2|l3} enable

Parameter

l2 Enter l2 to interpret Layer 2 flows.

l3 Enter l3 to interpret Layer 3 flows.

Defaults None (not enabled)

Command Modes OPENFLOW INSTANCE

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Usage Information

L2 flow-mapping is not supported on OpenFlow instances with an interface-type of “port.”

Related Commands

openflow of-instance Create or modify an OpenFlow instance.

interface-type

Specify the type of interface (port, VLAN, or any) for the OpenFlow instance.

Z-Series, S4810

Syntax

interface-type {any|port|vlan}

Defaults

port

Parameter

any

Enter the keyword

any

to enable configuration of physical interfaces,

LAGs, and VLANs on the selected OF instance.

port

Default. Enter the keyword

port

to enable configuration of LAGs or

physical interfaces on the selected OF instance.

vlan

Enter the keyword

vlan

to enable configuration of VLANs on the

selected OF instance.

NOTE: You must associate the OF instance with the VLAN when the VLAN is created.

Command Modes OPENFLOW INSTANCE

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Page 31

Example (VLAN interface type)

FTOS(conf)#openflow of-instance 1 FTOS(conf-of-instance-1)#interface-type vlan FTOS(conf-of-instance-1)#

Usage Information

Dell Force10 does not recommend selecting

any

for the interface-type unless both of-ports and

of-vlans are required in a single instance. If

any

is selected for the interface-type, the number

of available ACL flows is reduced by half (128 of 256 entries or 256 of 512 entries).

Legacy LLDP must be disabled on of-ports to avoid conflicts with the controller’s version of LLDP.

Dell Force10 does not recommend configuring global STP instances on ports using both legacy VLANs and OF VLANs.

Related Commands

openflow of-instance Create or modify an OpenFlow instance.

learning-switch-assist

Specify if learning bridge flows need to be interpreted by the switch.

Z-Series, S4810

Syntax

learning-switch-assist enable

Defaults Disabled

Command Modes OPENFLOW INSTANCE

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Usage Information

This command is used for OpenFlow instances with an interface-type of either vlan or any to allow the switch to interpret flows and update L2 tables to reduce the number of flows installed for VLANs.

Related Commands

openflow of-instance Create or modify an OpenFlow instance.

interface-type Select the OpenFlow instance interface type (port, VLAN, or any).

multiple-fwd-table enable

Advertise all forwarding tables (IFP, VLAN, L2, and L3) to the controller.

Z-Series, S4810

Syntax

multiple-fwd-table enable

Defaults Disabled

Command Modes OPENFLOW INSTANCE

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Page 32

Usage Information

This is a vendor-specific CLI.

Related Commands

openflow of-instance Create or modify an OpenFlow instance.

of-instance (Interface)

Add a physical interface or LAG to an OpenFlow instance.

Z-Series, S4810

Syntax

of-instance of-id

Parameter

of-id

Enter the OpenFlow instance ID. Range is 1 to 8.

Command Modes INTERFACE MODE

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Example In the following example, the ports Te 0/7 and Te 0/31 are associated with of-instance 1:

FTOS(conf)#interface tengigabitethernet 0/7 FTOS(conf-if-te-0/7)#of-instance 1 FTOS(conf-if-te-0/7)#interface tengigabitethernet 0/31 FTOS(conf-if-te-0/31)#of-instance 1 FTOS(conf-if-te-0/31)#

Usage Information

To enable OpenFlow, associate a port or a VLAN to an OF instance. Ports and VLANs must be associated when the OF instance is created and in a “shut” state (shutdown).

LAGs or port-channel interfaces are supported as of-ports or of-vlan members on OpenFlow.

By default, all ports are available for legacy functionality.

The following features are not supported on physical interfaces associated with an OpenFlow instance:

• Dot1x

• Ethernet

• GVRP

• IPv4

• IPv6

• MAC

• MTU

• Port-channel protocols

• Spanning-tree protocols

• Switchport

The following features are not supported on LAGs associated with an OpenFlow instance:

• Ethernet

Page 33

• GVRP

• IPv4

• IPv6

• MAC

• MTU

• Spanning-tree protocols

• Switchport

Related Commands

openflow of-instance Create or modify an OpenFlow instance.

openflow of-instance

Create an OpenFlow (OF) instance or modify an existing OpenFlow instance.

Z-Series, S4810

Syntax

openflow of-instance of-id

Parameters

of-id

Enter the number of the OF instance. Range is 1 to 8.

If you are creating a new OF instance, enter the number you want to assign to the OF instance.

If you are modifying an existing OF instance, enter the number of the instance you want to change.

NOTE: You must disable the OF instance before making any configuration changes.

Defaults none

Command Modes CONFIGURATION

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Usage Information

• Stacking for S4810, controller High Availability, and VLT are not supported on OF instances.

• To enable OpenFlow on S4810, the stack unit number must be zero.

• Up to eight OF instances can be created.

• To establish a connection with the controller, you must enable the OF instance using the no shutdown command.

• To modify the OF instance, you must disable the OF instance first using the shutdown command.

• One controller IP and one TCP port can be configured for each OF instance.

• The number of supported flows depends on the flow type. The following table provides the number of supported flows for each flow type:

Flow Type

Maximum Number of Available Flows

ACL 256 or 512 (depending on ACL CAM carving)

Page 34

Flow Type Maximum Number of Available Flows

L2 48,000

LB 24,000

L3 6,000

• If the time or date on the system clock is changed, you must disable and re-enable all existing OpenFlow instances to avoid session timeout issues.

Related Commands

shutdown — Enable or disable the OpenFlow instance.

show openflow — Display general information about OpenFlow instances.

controller — Specify the OpenFlow controller configuration that the OpenFlow instance uses to

establish a connection.

show openflow

Display general information about OpenFlow instances.

Z-Series, S4810

Syntax

show openflow [of-instance[of-id]]

Parameter

of-instance

of-id

(OPTIONAL)

Enter the keyword of-instance to display information such as administrative state, interface-type, and operational state for all OpenFlow instances.

(OPTIONAL) Enter the keyword of-instance followed by the OF instance ID to display details for the specified OF instance. Range is 1 to 8.

Defaults None

Command Modes EXEC

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Example

FTOS#show openflow of-instance 1 Instance : 1 Admin State : Down Interface Type : Port DP Id : 00:01:00:01:e8:8b:1a:30 Forwarding Tbls : acl Flow map : LB assist : disabled EchoReq interval: 15 seconds Connect interval: 15 seconds Number of Flows : 0 Packets (acl) : Bytes (acl) : Controller 1 : TCP, 10.11.205.184/6633, not-connected Controller 2 : Port List :

Page 35

Vlan List : Vlan Mbr list :

Usage Information

Use the show openflow command to display general information such as version, capabilities, and supported actions.

Related Commands

openflow of-instance Create or modify an OpenFlow instance.

show openflow flows

Display detailed information about OpenFlow instances.

Z-Series, S4810

Syntax

show openflow flows[of-instance{of-id}][table{acl|lb|mac|route| vlan}flow-id{flow-id}]

Parameter

of-instance

of-id

Enter the keyword of-instance followed by the OF instance ID to display details of all flows installed for the specified OF instance. Range is 1 to 8.

table

acl | lb |

mac | route | vlan

flow-id

Enter the keyword table followed by the table type and the keyword flow-id followed by the flow ID to display details for the specified flow:

acl Display ACL table information.

lb Display learning bridge table information.

mac Display MAC table information.

route Display routing table information.

vlan Display VLAN table information.

Defaults None

Command Modes EXEC

Command History

Version 9.1(0.0) Introduced on Z9000 and S4810.

Related Commands

show openflow Display general information about OpenFlow instances.

shutdown (OpenFlow Instance)

Enable or disable the OpenFlow instance.

Z-Series, S4810

Syntax

[no] shutdown

Page 36

Defaults Disabled (shutdown)

Command Modes OPENFLOW INSTANCE

Command History

Version 9.1(0.0) Introduced on the S4810 and Z9000.

Usage Information

Use the no shutdown command to enable the OpenFlow instance. When the no

shutdown

command is used, the OpenFlow instance sends a request to the OpenFlow

controller to establish a connection.

Use the shutdown command to disable an OpenFlow instance. You must use the shutdown command before making any configuration changes to the OpenFlow instance.

All OpenFlow instances are disabled by default.

Related Commands

openflow of-instance Create or modify an OpenFlow instance.

controller Configure the controller used by OpenFlow.