Service Ingress Policy Configuration Considerations - Alcatel-Lucent 7210 SAS M OS Quality Of Service Manual

Overview

Service Ingress Policy Configuration Considerations

The num-qos-classifiers parameter cannot be modified when the policy is in use (for example,
when it is associated with a SAP). Other parameters in the SAP ingress policy can be changed.
When changing other parameters (for example, fc meter map or fc classification match criteria
entries) for a policy which is in use, the system recomputes the resources required due to
accomodate the change. If the resources required exceeds the configured value for num-qos-
classifiers, then the change is not allowed.
If more resources are needed than what is configued in num-qos-classifiers for a existing policy,
then the following options are available.
•
•
•
•
•
Page 236
Copy the existing policy to a new policy, modify the num-qos-classifiers parameter,
modify the match criteria entries suitably, and finally modify the SAP configuration to
associate it with the new policy.
Ensure the existing policy is not in use by any SAP (if required change the SAP
configuration to disable the use of the QoS policy with the no qos form of the command),
change all the required parameters and finally modify the SAP configuration to use the
policy again.
Note that both these options have side-effects, for example, it resets the statistics
associated with the meters and can potentially cause existing traffic classification not to
take effect. But, the system will ensure that default policy is in use during the intermittent
time when a policy changes are being made following the steps given above.
In releases prior to release 3.0R1, the software always the computes the number of
resources (like classifiers and meters) required by a policy assuming it will be used in a
VPLS service. This allows the policy to be applied to either an Epipe or VPLS service.
From release 3.0R1 onwards, on creation of SAP ingress policy, software does not
compute the number of resources required by a policy and validate it against resources
available in the system. The software validates the resources needed only when the SAP
ingress policy is attached to a SAP. If enough resources are available the association
succeeds, else the software fails the CLI command. Based on the service (i.e. Either VLL,
VPLS, and so on.) the SAP is configured in, for the same SAP ingress policy the amount
of resources required is different. The software validates that the amount of qos resources
specfied with the command num-qos-classifiers is sufficient for the match criteria,
forwarding class and service specified and the resources are available in hardware. On
failure of the validation, the software disallows the association of the SAP ingress policy
with the SAP.
The match criteria type (that is, mac-criteria, ipv4-criteria and ipv6-criteria) cannot be
changed when the SAP ingress QoS policy is in use. For example - if the match-criteria is
set to ipv4-criteria and the policy is associated with a SAP then the ipv6-criteria or mac-
criteria cannot be enabled in the same policy. If there is a need to change the criteria, then
7210 SAS M OS Quality of Service Guide