There is one default service ingress policy. The default policy allocates a single queue and maps all traffic to the ‟be” (best-effort) FC. The default policies can be copied and modified but they cannot be deleted. The default policies are identified as policy ID 1. The default policies are applied to the appropriate interface, by default. For example, the default SAP-ingress policy is applied to access ingress SAPs. You must explicitly associate other QoS policies. For information about the tasks and commands necessary to access the command line interface and to configure and maintain your 7210 SAS devices, see the ‟CLI Usage” chapter in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide.
In a service ingress QoS policy, a user can define up to eight queues or 16 policers/meters per policy, with up to two queues or two meters per FC.
For VPLS, the following types of forwarding are supported:
unicast
multicast
broadcast
unknown
Multicast, broadcast, and unknown types are flooded to all destinations within the service while the unicast forwarding type is handled in a point-to-point manner within the service. All these traffic types use the same queue or meter (in other words, a separate queue or meter for multicast, broadcast, and unknown unicast traffic types cannot be defined).
Unicast and multipoint traffic can be defined to use the same queue or meter or different queues or meter per FC. In other words, eight queues and 16 policers are shared by unicast and multicast traffic types and if a user allocates a dedicated multicast queue for BUM traffic, the number of queues available for unicast traffic reduces. Similarly, up to 16 meters can be shared by unicast and multicast traffic types.