Deployment Guide

22
4.3.2.4 Bridging Flow Table
The Bridging Flow Table supports Ethernet packet switching for potentially large numbers of flow entries
using the hardware L2 tables. The default on a miss is to go to the Policy ACL Flow Table.
Note: The Policy ACL Flow Table is preferred for matching BPDUs.
The Bridging Flow Table forwards based on VLAN (normal switched packets) using the flow entry types in
Table 17.
Table 17: Bridging Flow Table Flow Entry Types
Type
Description
Unicast
VLAN
Bridging
Matches switched unicast Ethernet frames by VLAN id and MAC_DST. MAC_DST must be
unicast and cannot be masked. VLAN id must be present and nonzero. Tunnel id must be
masked or omitted.
Multicast
VLAN
Bridging
Matches switched multicast Ethernet frames by VLAN id and MAC_DST. MAC_DST must
be multicast and cannot be masked. VLAN id must be present and nonzero. Tunnel id
must be masked or omitted.
DLF VLAN
Bridging
Matches switched Ethernet frames by VLAN id only. MAC_DST must be field masked and
match any destination. Must have lower relative priority than any unicast or multicast
flow entries that specify this VLAN. VLAN id must be present and nonzero. Tunnel id
must be masked or omitted.
Note: Exact match rules must be given higher priority assignments than any wildcard rules. In any event,
exact match rules are evaluated before any wildcard rules.
4.3.2.4.1 Match Criteria, Instructions, Actions/Action List/Action Set, Counters, Flow Expiry
Match fields for flow entry types are described in the following tables.
Table 18. Bridging Flow Table Match Fields
Field
Bits
Maskable
Optional
Description
ETH_DST
48
Yes
Yes
Ethernet destination
MAC, allowed values
depend on flow entry
type. Exact match only
(mask must be all 1’s if
supplied).
VLAN_VID
16
Yes
Yes
VLAN id, allowed
values depend on flow
entry type. Exact
match only (mask
must be all 1’s if
supplied).
Default next table if no match is the ACL Policy Flow Table.