This chapter describes the details of OpenFlow via CrossFlow mode. CrossFlow mode allows traditional L2/L3 and OpenFlow protocols to run simultaneously on the same physical switch.
On N3048EP-ON, N3048ET-ON, N1148T-ON and N3132PX switches, run "save_config" command when set Crossflow commands. Otherwise, the Crossflow configuration will be lost after PicOS reboot. For detail, please refer to Configuration Saving Guide.
CrossFlow mode has been greatly improved starting in PicOS 2.6.2. Now, most of the OVS mode commands are available in CrossFlow mode.
OVS features that are available in the CrossFlow mode:
OVS features that need to be configured in Xorplus mode:
The OVS features which are unavailable in CrossFlow mode:
The Switch Hardware Architecture page describes the meaning of some terms used here, such as TCAM or FIB.
In CrossFlow mode, switches can achieve most of the functions that exist in OVS mode, including: basic flow function, meter, group, multi-table, Q-in Q and so on.
● Like in PicOS OVS mode, in CrossFlow mode, OpenFlow 1.0, OpenFlow 1.1, OpenFlow 1.2, OpenFlow 1.3, and OpenFlow 1.4 are supported. User can configure any supported version in the CLI.
● After PicOS 2.6.2, ports in the switch can be configured in any one of these three modes: Legacy, Crossflow or Openflow. The difference in configuration is:
Legacy port: disable crossflow
Crossflow port: enable crossflow and enable local-control
Openflow port: enable crossflow and disable local-control
● After PicOS 2.4, Openflow can also support the multiple-table control, which means that Openflow can configure some flows in FIB (mac address table and routing table). The flow should match some conditions to install them in FIB. Please refer to the manual in the PicOS Openflow Configuration documentation.
As the figure above shows, the switch ports working status in Crossflow mode is shown. The Openflow flow can look up two tables including TCAM and FIB (multiple tables). The ports in Crossflow mode can be summarized as follows:
In Crossflow mode, user can enable L2/L3 mode as a PicOS OVS multi-table function. If the L2/L3 mode is enabled, the FIB table resource will be shared by legacy ports and Crossflow ports, and data traffic cannot mix between the different type ports. User can allocate the resource for special ports as the following command shows.
set interface stm firewall-table ingress 100 set interface stm mac-table 20000 set interface stm ipv4-route 6000 set interface stm ipv6-route 1000
The first command, set interface stm firewall-table ingress 100, means allocate the TCAM resource for ingress ACL rule, and part of the rest of resource for Crossflow port and Openflow port;
The second command, set interface stm mac-table 20000, means allocate the FDB table resource for legacy port, and the rest of resource for Crossflow port and Openflow port.
The last two commands, set interface stm ipv4-route 6000, and set interface stm ipv6-route 1000, means allocate the route table resource for legacy port, and the rest of resources for Crossflow port and Openflow port.
In Crossflow mode, traffic can only be forwarded in the OpenFlow or Legacy network domain (as shown in the following figures). The traffic between Openflow port and Crossflow port forwarded by Tcam flow table default, if user wants to forward by FIB, enable multi-table and configure L2/L3 flow entries. The traffic between Crossflow port and Legacy port is forwarded by FIB.