Versions Compared

Old Version 1

changes.mady.by.user Tracy Yang

Saved on

compared with

New Version 2

changes.mady.by.user Tracy Yang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

Note
Configuration Notes:
  • Only Openflow ports can be added to an Openflow lag as members, and only Crossflow ports can be added to a Crossflow lag as members. All lag's members are configured in Switching CLI.

  • All LACP packets are handled by Switching.

  • Besides LACP, all other protocol packets received from Openflow ports will be sent to OVS. For the packets received from Crossflow ports, user can configure either Switching or OVS to handle the packets. By default, these packets are handled by Switching.

  • All port speed, mtu, VLAN members, and other information is configured in Switching CLI as usual, and these configurations in OVS CLI will not take effect.

  • When add flow with matching mpls,mpls_label cannot be configured as 0-15.


Info

Warning:

On S5810-48TS-P, 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.


The Switch Hardware Architecture page describes the meaning of some terms used here, such as TCAM or FIB.

...

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.

...