The association rules work differently for network egress IP interfaces than they do for access SAPs. Because the network QoS policy does not directly reference the queue group names, the system is unable to check for queue group template existence or queue ID existence when the forwarding class queue redirection is defined. Configuration verification can only be checked at the time the network QoS policy is applied to a network IP interface.
The system keeps an association counter for each queue group template and an association counter for each queue ID within the template. The system also keeps an association counter for each queue group created on a port.
When a network QoS policy is applied to an IP interface with the queue group parameter specified:
If the queue group name does not exist as an egress queue group template, the QoS policy application fails.
If a redirection queue ID within the policy does not exist within the egress queue group template, the QoS policy application fails.
If the IP interface is bound to a port (or LAG) and the specified queue group name does not exist on the port, the QoS policy application fails.
If the preceding operation is successful:
The system increments the association counter for the queue group template with the same name as the queue group specified when the QoS policy is applied.
The system increments the queue ID association counter within the queue group template for each forwarding class redirected to the queue ID.
If the IP interface is currently bound to a port (or LAG), the association counter for the queue group on the port is incremented.
When the queue group parameter is removed from an IP interface:
The system decrements the association counter for the queue group template with the same queue group name that was removed from the IP interface.
The system decrements the queue ID association counter within the queue group template for each forwarding class that had previously been redirected to the queue ID.
If the IP interface is currently bound to a port (or LAG), the association counter for the removed queue group on the port is decremented.
When a network QoS policy egress forwarding class redirection to a queue ID is removed or added, the redirection fails if a redirection is being added to a forwarding class and the queue ID does not exist on the queue groups for IP interfaces where the QoS policy is applied.
If the preceding operation is successful:
The system finds all IP interfaces where the policy is applied.
The system finds all affected queue group templates based on the queue group associated with the QoS policy on each interface.
If removing, the queue ID association counter is decremented within each queue group template based on the queue ID removed from the policy.
If adding, the queue ID association counter is incremented within each queue group template based on the queue ID added to the policy.
When an IP interface associated with a queue group is bound to a port, the port binding fails if the specified egress queue group does not exist on the port.
If the preceding operation is successful, the system increments the association counter for the queue group on the port.
When an IP interface associated with a queue group is unbound from a port, the system decrements the association counter for the queue group on the unbound port.