Matching restrictions
VLAN matching
Table 1 describes the VLAN matching restrictions when an OpenFlow instance is associated with VLANs.
Table 1: VLAN matching
VLAN | Mask | Matching packets |
|---|---|---|
- | - | All packets in the VLANs that are associated the OpenFlow instance. |
0 | - | Packets without a VLAN tag. The PVID of the ingress port must be associated the OpenFlow instance. |
0 | Value | Unsupported. |
Valid VLAN | -/Value | Unsupported. |
0x1000 | -/Value(except non-0x1000) | Unsupported. |
0x1000 | 0x1000 | Packets with a VLAN tag. The VLAN ID of the VLAN tag must be associated with the OpenFlow instance. |
Valid VLAN | 0x1000 | -/Value | Matching packets by the combination of the VLAN ID and VLAN mask. The VLANs obtained through the combination of the VLAN ID and VLAN mask must be associated with the OpenFlow instance. |
Other | Other | Unsupported. |
Protocol packet matching
If protocols are enabled, protocol packets (except LLDP frames) are processed by the corresponding protocols instead of the OpenFlow protocol.
For more information about LLDP frame matching, see "LLDP frame matching."
Metadata matching
Metadata is used to pass matching information between flow tables. The controller deploys metadata matching entries only to non-first flow tables. If the controller deploys a metadata matching entry to the first flow table, the switch returns an unsupported flow error.