Service ingress classification — IP and MAC packet fields

The IP and MAC match criteria can be very basic or quite detailed. IP and MAC match criteria are assembled from policy entries. An entry is identified by a unique, numerical entry ID. A single entry cannot contain more than one match value for each match criteria. Each match entry has an action which specifies the FC of packets that match the entry. The entries are evaluated in numerical order based on the entry ID from the lowest to highest ID value. The first entry that matches all match criteria has its action performed.

The following tables list the packets fields used for match-criteria used for access SAP-ingress classification.

Table: Service ingress QoS policy IP match criteria
IP criteria	Services applicable on 7210 SAS-K 2F1C2T	Services applicable on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
IP DSCP	Access SAPs in Epipe, VPLS, IES, RVPLS services	Access SAPs in Epipe, VPLS, IES, VPRN, RVPLS services
IP source address and mask, IP destination address and mask, IP protocol, TCP/UDP source port and fragment field TCP/UDP destination port	Access SAPs in Epipe, VPLS, IES, RVPLS services	Access SAPs in Epipe, VPLS, IES, VPRN, RVPLS services

Table: Service ingress QoS policy IPv6 match criteria
IPv6 criteria	Services applicable on 7210 SAS-K 2F1C2T	Services applicable on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
DSCP value, Destination IPv6 address and mask match, Destination port TCP/UDP port match, Source IPv6 address and mask match, Source port TCP/UDP port match	Access SAPs in Epipe, VPLS, RVPLS services	Access SAPs in Epipe, VPLS, RVPLS services

Table: Service ingress QoS policy MAC match criteria
MAC match criteria	Services applicable on 7210 SAS-K 2F1C2T	Services applicable on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
IEEE 802.1p/dot1p value/mask (for both inner and outer tag separately), Source MAC address/mask, Destination MAC address/mask, EtherType Value/Mask, outer VLAN, and inner VLAN tag value	Access SAPs in Epipe, VPLS, RVPLS services	Access SAPs in Epipe, VPLS, RVPLS services

The following table lists the Packet Fields available for match in QoS classification policy and ACL policy for different SAPs.

Table: Packet fields available for match in QoS classification policy and ACL policy
Ingress SAP type	Packet contents (only Ethernet–II frames)	MAC address match	Inner VLAN ID and dot1p match	Outer VLAN ID and dot1p match	Etype match	IPv4/IPv6 criteria match
NULL SAP	Null tag	Yes	No	No	Yes	Yes
	Priority tag (both VID and dot1p)	Yes	No	Yes	Yes	Yes
	Single tag	Yes	No	Yes	Yes	Yes
	Two tags	Yes	Yes	Yes	Yes	Yes
	Three or more tags	Yes	Yes	Yes	No	No
dot1q SAP (includes dot1q explicit null SAP and dot1q Default SAP)	Null tag	Yes	No	No	Yes	Yes
	Priority tag (both VID and dot1p)	Yes	No	Yes	Yes	Yes
	Single tag	Yes	No	Yes	Yes	Yes
	Two tags	Yes	Yes	Yes	Yes	Yes
	Three or more tags	Yes	Yes	Yes	No	No
dot1q SAP (includes dot1q SAP, dot1q range SAP)	Null tag	Invalid	Invalid	Invalid	Invalid	Invalid
	Priority tag (both VID and dot1p)	Invalid	Invalid	Invalid	Invalid	Invalid
	Single tag	Yes	No	Yes	Yes	Yes
	Two tags	Yes	Yes	Yes	Yes	Yes
	Three or more tags	Yes	Yes	Yes	No	No
QinQ SAP - 0.* SAP (matches only null and priority tag packets)	Null tag	Yes	No	No	Yes	Yes
	Priority tag (both VID and dot1p)	Yes	No	Yes	Yes	Yes
	Single tag	Invalid	Invalid	Invalid	Invalid	Invalid
	Two tags	Invalid	Invalid	Invalid	Invalid	Invalid
	Three or more tags	Invalid	Invalid	Invalid	Invalid	Invalid
QinQ SAP (. Default QinQ SAP)	Null tag	Yes	No	No	Yes	Yes
	Priority tag (both VID and dot1p)	Yes	No	Yes	Yes	Yes
	Single tag	Yes	No	Yes	Yes	Yes
	Two tags	Yes	Yes	Yes	Yes	Yes
	Three or more tags	Yes	Yes	Yes	No	No
QinQ SAP (includes Q1.* SAP)	Null tag	Invalid	Invalid	Invalid	Invalid	Invalid
	Priority tag (both VID and dot1p)	Invalid	Invalid	Invalid	Invalid	Invalid
	Single tag	Yes	No	Yes	Yes	Yes
	Two tags	Yes	Yes	Yes	Yes	Yes
	Three or more tags	Yes	Yes	Yes	No	No
QinQ SAP (includes Q1.0 SAP)	Null tag	Invalid	Invalid	Invalid	Invalid	Invalid
	Priority tag (both VID and dot1p)	Invalid	Invalid	Invalid	Invalid	Invalid
	Single tag	Yes	No	Yes	Yes	Yes
	Two tags (inner tag is a priority tag)	Yes	Yes	Yes	Yes	Yes
	Two tags (inner tag is not a priority tag)	Invalid	Invalid	Invalid	Invalid	Invalid
	Three or more tags	Yes	Yes	Yes	No	No
QinQ SAP (includes Q1.Q2 SAP)	Null tag	Invalid	Invalid	Invalid	Invalid	Invalid
	Priority tag (both VID and dot1p)	Invalid	Invalid	Invalid	Invalid	Invalid
	Single tag	Invalid	Invalid	Invalid	Invalid	Invalid
	Two tags (inner tag is a priority tag)	Invalid	Invalid	Invalid	Invalid	Invalid
	Two tags (inner tag is not a priority tag)	Yes	Yes	Yes	Yes	Yes
	Three or more tags	Yes	Yes	Yes	No	No

The 7210 SAS does not support configuring of the frame-type match criteria and the default frame type configured is Ethernet - II; see the following table.

Table: MAC match Ethernet frame types
Frame format	Description
802.3	IEEE 802.3 Ethernet frame. Only the source MAC, destination MAC and IEEE 802.1p value are compared for match criteria.
802dot2-llc	IEEE 802.3 Ethernet frame with an 802.2 LLC header. Only the source MAC and destination MAC address are compared for match criteria.
802dot2-snap	IEEE 802.2 Ethernet frame with 802.2 SNAP header. Only the source MAC and destination MAC address are compared for match criteria.
Ethernet-II	Ethernet type II frame where the 802.3 length field is used as an Ethernet type (Etype) value. Etype values are two byte values greater than 0x5FF (1535 decimal).

Note:

The default frame type configured is Ethernet-II.

The following table lists the criteria that can be matched for the various MAC frame types.

Table: MAC match criteria frame type dependencies
Frame format	Source MAC	Dest MAC	IEEE 802.1p value	Etype value
802.3	Yes	Yes	Yes	No
802dot2-llc	Yes	Yes	Yes	No
802dot2-snap	Yes	Yes	Yes	No
ethernet-II	Yes	Yes	Yes	Yes