Alcatel-Lucent 7210 SAS-X - Qos Policies; CPU Qos for IES Access Interfaces in Network Mode

Internet Enhanced Services
Page 631
An ICMP ping mechanism is used to test the connectivity. If the connectivity check fails and the
static route is de-activated, the router will continue to send polls and re-activate any routes that are
restored.
QoS Policies
When applied to 7210 SAS IES services, service ingress QoS policies only create the unicast
meters defined in the policy. The multipoint meters are not created on the service. With IES
services, service egress QoS policies function as with other services where the class-based queues
are created as defined in the policy.
On 7210 SAS ingress, only meters are supported on all the platforms. On 7210 SAS-X, the user is
provided with an option to use unicast ingress queues (and can be used instead of meters).
Note: QoS policies only create the unicast meters defined in the policy if PIM is not configured on
the associated IP interface; if PIM is configured, the multipoint meters are applied as well.
Note that both MAC and IPv4 criteria can be used in the QoS policies for traffic classification in
an IES.
CPU QoS for IES access interfaces in network mode
Traffic bound to CPU received on IES access interfaces are policed/rate-limited and queued into
CPU queues. The software allocates a policer per IP application or a set of IP applications, for
rate-limiting CPU bound IP traffic from all IES access SAPs. The policers CIR/PIR values are set
to appropriate values based on feature scaling and these values are not user configurable. The
software allocates a set of queues for CPU bound IP traffic from all IES access SAPs. The queues
are either shared by a set of IP applications or in some cases allocated to an IP application. The
queues are shaped to appropriate rate based on feature scaling. The shaper rate is not user
configurable.
NOTE: The instance of queues and policers used for traffic received on network port IP interfaces
is different for traffic received from access port IP interfaces. Additionally the network CPU
queues are accorded higher priority than the access CPU queues. This is done to provide better
security and mitigate the risk of access traffic affecting network side.