Table of Contents
Advertisement
Overview of service ingress policy on 7210 SAS-K
•
•
•
•
•
•
•
For calculating the number of classification entries per FC for a SAP in a VLL service or IES
service with PIM disabled, the following rules apply:
•
•
Given the number of traffic types to use per 'FC in use', the following rules apply for an SAP in a
IES and VPRN service enabled with PIM/multicast enabled to arrive at number of classification
entries per FC in use:
Page 240
This requires one classification entry in hardware. This assumes default mulitpoint meter
#11 is not created by the user.
If a FC is in use and is created without explicit meters, use default meter #1 for unicast
traffic and default meter #11 (assuming meter "11" is created by the user), for all other
traffic types (that is, broadcast, multicast and unknown-unicast). This requires two
classification entries in hardware.
If a FC is in use and is created with an explicit unicast meter, use that meter for unicast
traffic and for all other traffic types (that is, broadcast, multicast and unknown-unicast).
This requires one classification entries in hardware. This assumes default multipoint meter
"11" is not created by the user.
If a FC is in use and is created with an explicit unicast meter, use that meter for unicast
traffic and use default meter #11 (assuming meter "11" is created by the user) for all other
traffic types. This requires two classification entries in hardware.
If a FC is in use and is created with an explicit unicast meter and explicit broadcast meter,
use these meters for unicast and broadcast traffic respectively and use the unicast meter for
all other traffic types (that is, multicast and unknown-unicast). This requires two
classification entries in hardware. This assumes that the default multipoint meter #11 is
not created by the user.
If a FC is in use and is created with an explicit unicast meter and explicit broadcast meter,
use these meters for unicast and broadcast traffic respectively and use meter #11
(assuming meter 11 is created by the user) for all other traffic types. This requires three
classification entries in hardware.
If a FC is in use and is created with an explicit unicast meter and explicit multicast meter,
use the unicast meter for unicast traffic and multicast meter for all other kinds of traffic.
This requires two classification entries in hardware.
If a FC is in use and is created with an explicit unicast meter, an explicit broadcast meter,
and an explicit multicast meter, use these meters for unicast, broadcast and multicast
traffic types respectively. Unknown unicast traffic type will use the explicitly defined
multicast meter. This requires three classification entries in hardware.
Multipoint meters cannot be used. Multipoint meter configured in a policy is not used
when the policy is applied to a SAP in an Epipe service.
All FCs in use and associated with a meter always use the unicast meter. Therefore, all
FCs in use utilize only one classification entry in the hardware.
7210 SAS D, E, K OS Quality of Service Guide
Advertisement
Table of Contents
