
Multi-Service IronWare SDN Configuration Guide 5
53-1003034-02
Overview of OpenFlow
1
Brocade devices support the actions listed in Table 4.
OpenFlow Controller
Multiple controller connections can be used for redundancy purposes, such as when using a single
controller with multiple addresses. Multiple controller connections can also be used to support
active-standby controllers.
Regardless of the intended use of multiple controller connections, the Brocade device allows all the
controller connections to concurrently manage the flow table. That is, flow entries in the flow table
are not identified as belonging to any specific controller connection. In an active-standby controller
deployment, controllers themselves must coordinate their actions and active-standby states. The
Brocade device will respond to all connected controllers without distinction.
The Brocade device supports two types of controller connections (also called modes): active and
passive. An active connection is one for which the Brocade device will initiate (seek) the TCP
connection to a given OpenFlow Controller address. With a passive connection, the Brocade device
will passively wait for the controller to initiate (seek) the TCP connection to the Brocade device.
Active mode is commonly used with production controllers, while passive mode is commonly used
for testing purposes in experimental environments. Optionally, a controller connection can also use
SSL encryption.
OpenFlow counters
Brocade MLX Series and Brocade NetIron XMR devices record the number of received packets and
bytes on a per-flow basis. However, recording the number of received bytes on a per-flow basis is
only supported on ports on the 8x10G or 100G cards. Brocade NetIron CER and Brocade NetIron
CES devices record only the received packets on a per-flow basis—these devices do not record the
number of bytes per flow.
TABLE 4 OpenFlow actions supported on Brocade devices
OpenFlow action Brocade MLX
Series
Brocade NetIron
XMR
Brocade
NetIron CER
Brocade
NetIron CES
Forward a packet to a set of ports Yes Yes
Drop the packet Yes Yes
Add, modify, or remove VLAN ID or priority on a per destination port basis Yes Yes
Modify the IP DSCP (for a flow sending a copy of the packet to multiple
destinations, the DSCP modification must be the same for all destinations.
Modifying IP DSCP is only supported on ports enabled with Layer 3 mode.)
Yes No
Modify the source or destination MAC address (for a flow sending a copy of the
packet to multiple destinations, the MAC address modification must be the
same for all destinations).
Yes No
Send the packet to the controller (Packet In) Yes Yes
Receive the packet from the controller and send it to ports (Packet Out) Yes Yes
Kommentare zu diesen Handbüchern