WB.15.15

Figure 4 Integration with OpenFlow

OpenFlow and Service Tunnel Restrictions

1. A tunnel interface cannot be part of a multi-port output action.

2. A flow-rule’s output action of sending packets to a tunnel cannot be combined with “Normal”

or “SendToController” actions.

3. A tunnel interface cannot be part of FLOOD action.

4. Re-directing packets to SI tunnels on an OpenFlow 1.0 instance is not supported. Tunnels are

only supported on OpenFlow 1.3 instances.

5. OpenFlow pipeline is bypassed for packets coming back on a tunnel. The device forwarding

tables are used to determine how to forward these packets.

6. The switch does not remove the flows referencing tunnels when tunnel interfaces are deleted.

The controller has to come back and delete those flows.

7. The tunnel interfaces are only supported on the Policy Engine (TCAM) tables and not with the

software tables.

8. In the event of management card failover (on platforms with redundant management card

support), tunnel interfaces are removed but OpenFlow does not delete any flows referencing

tunnel interfaces. Once the application recreates those tunnels, traffic forwarding to tunnels

will resume.

9. OpenFlow Port mod requests are not supported on tunnel interfaces.

10. A tunnel interface cannot be used as a match parameter in any flow programmed by the

OpenFlow controller.

11. When using Service Insertion, VLAN interfaces that have a DHCP address and OOBM interfaces

cannot be used to create a tunnel between device and the application.

Hardware IP Tunnels 7