OpenFlow Hybrid Port Mode Prerequisites and Capabilities

The following prerequisites and capabilities apply to OpenFlow hybrid port mode:

  • IPv4 and IPv6 unicast routing are supported on OpenFlow protected and unprotected VLANs.
  • Packets tagged with a protected VLAN ID are forwarded by IPv4 and IPv6 unicast routing, if IPv4 or IPv6 routing is configured on the VLAN. If IPv4 or IPv6 routing is not configured on the VLAN, such packets are dropped.
  • Packets tagged with an unprotected VLAN ID are subject first to OpenFlow flows. If there is a match on an OpenFlow flow, the packet is forwarded according to the flow actions. No further IPv4 or IPv6 routing is supported for packets that are forwarded by OpenFlow flows. If there is no match on any OpenFlow flow, the packet is forwarded by IPv4 or IPv6 unicast routing if IPv4 or IPv6 routing is configured on the VLAN. If IPv4 or IPv6 routing is not configured on the VLAN, those packets are either dropped or sent to the controller, according to the OpenFlow configuration.
  • Because routing is enabled on a port in OpenFlow hybrid port mode, OpenFlow traffic or unprotected VLAN traffic sent with the destination MAC address as the port's MAC address and matching IP route entries on the port can potentially find the VLAN and MAC address modified unless the OpenFlow rules explicitly set the VLAN and destination MAC address in the outgoing packet.
  • Policy-Based Routing (PBR) is not supported.
  • Protected VLAN traffic that does not have matching IP route entries is dropped.
  • Multiple interfaces cannot be part of a VE interface created on a port in OpenFlow hybrid port mode with a protected VLAN.
  • The BGP4+, OSPFv2, OSPFv3, RIP, and RIPng protocols are supported on protected VLANs.
  • When protected VLANs are configured but the port is not part of the VLAN, the traffic coming on the port with the protected VLAN is dropped.
  • Link aggregation is not supported.
Parent topic: OpenFlow Hybrid Port Mode