Hybrid OpenFlow Switching
660 Router Configuration Guide
Caveats:
• Please refer to the Release Notes for a full list of GRT/IES/VPRN/VPLS interfaces
that support OF control for multi-service mode.
• The 7x50 H-OFS always requires sros-cookie to be provided for FlowTable
operations and will fail any operation without the cookie when switch-defined-
cookie is enabled.
• OF no-match-action is not programmed in hardware for system filters, since system
filters are chained to other filter policies and no-match-action would break the
chaining.
• An H-OFS instance does not support overlapping of priorities (flow_priority value)
within a single sros-cookie (type+value). The supported values for priority differ
based on a value for switch-define-cookie:
→ H-OFS with switch-define-cookie disabled
— Valid flow_priority_range 1 to max-size – 1
— flow_priority_value 0 is reserved (no match action)
→ H-OFS with switch-define-cookie enabled
— Valid flow_priority_range 1 to 65534
— flow_priority_value 0 is reserved (no match action)
• flow_priority must map to a valid filter ID. The following items show how
flow_priority is mapped to a filter policy entry ID:
→ H-OFS with switch-define-cookie disabled
— filter entry ID = max-size – flow_priority + embedding offset
Support OF on VPLS access and
network interfaces
No (lack of native OF service
virtualization)
Yes
Support port and VLAN in flowtable
match (see the following section)
No Yes
Support OF control of System ACL
policies
No Yes
Traffic steering actions Forward, drop, redirect to LSP,
Layer 3 PBR actions only
All
Scale Up to ingress ACL filter policy
entry scale
Up to OF system scale limit per H-
OFS instance, and up to 64534
entries per unique sros-cookie
value
Table 66: Differences Between GRT Mode and Multi-service Mode (Continued)
Function GRT Mode
(no switch-defined-cookie)
Multi-service Mode
(switch-defined-cookie)
To Next Page
Loading...
