The num-qos-classifiers command 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 that is in use, the system recomputes the resources required to accommodate the change. If the resources required exceed the configured value for num-qos-classifiers, the change is not allowed.
If more resources are needed than are configured in num-qos-classifiers for an existing policy, the following options are available:
Copy the existing policy to a new policy, modify the num-qos-classifiers command, modify the match criteria entries, 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 using the no qos form of the command), change all the required parameters, and finally modify the SAP configuration to use the policy again.
Both these options have side-effects; for example, they can reset the statistics associated with the meters and potentially cause existing traffic classification not to take effect; however, the system ensures that the default policy is in use during the intermittent time when the policy changes are being made after the two options are performed.
In releases before Release 3.0R1, the software always 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, when creating a SAP ingress policy, the 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, otherwise the command fails. Based on the service (VLL, VPLS, and so on) in which the SAP is configured, for the same SAP ingress policy the amount of resources required is different. The software validates that the number of QoS resources specified with the num-qos-classifiers command is sufficient for the match criteria, FC, and service specified, and the resources are available in hardware. If the validation fails, 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 type is set to ipv4-criteria and the policy is associated with a SAP, the ipv6-criteria or mac-criteria cannot be enabled in the same policy. If there is a need to change the criteria, the user must remove the association and then change the SAP ingress policy to use the new match criteria.
See Resource allocation for service ingress QoS policy classification rules for more information.