A target is an entity where a policy is applied, and a wired target can be a port.
The following are the restrictions for applying QoS features on a device for a wired target:
-
For a type queueing policymap, a maximum of eight queuing classes are supported on a device port for a wired target.
-
For a nonqueueing policymap, policer is only supported in ingress. Up to 32 policers are supported per ingress policymap per
port. Each policer has counter for conform, exceed, and violate.
-
A maximum of only 1599 policymaps can be created.
-
A total of eight priority levels (0 to 7) are supported, but only one priority level can be configured for each classmap.
A class without priority level configured is priority level 0, which is referred to as nonpriority class.
-
In a hierarchical policy, overlapping actions between parent and child are not allowed, except when a policy has the port
shaper in the parent policy and the queuing features in the child policy.
-
For hierarchical QoS (H-QoS) applied in the ingress direction, policing in both the parent and the child is not supported
in a QoS hierarchy.
-
Marking in both the parent and the child is not supported in a QoS hierarchy.
-
Empty classes are supported.
-
The conform action must be transmit under a policer within a policy map.
-
Marking action is not supported in the egress type queueing policy. To support remark on egress, a new policy map must be
attached, which can be based on DSCP or PREC or CoS or MPLS EXP or QoS-group, but not based on ACL.
-
For Generic Routing Encapsulation (GRE) tunnel interface, a policymap can be attached only to physical members, and not on
the logical tunnel interface.
-
Classification counters have the following specific restrictions:
-
Classification counters count packets instead of bytes.
-
Filter-based classification counters are not supported.
-
Only QoS configurations with marking or policing can trigger the classification counter.
-
The classification counter is only port based, and aggregation is not performed.
-
As long as there is policing or marking action in the policy, the class will have classification counters.
-
When there are multiple match statements in a class, the traffic counter is cumulative for all the match statements in the
class.
-
A class without policer in ingress or egress policymap is assigned to a classification counter. For an ingress policy, 32
unique counters per port are supported, and for egress policy, eight unique counters per port are supported. If an ingress
or egress policy has more than 32/8 classes without policers, the extra classes will share the same match counter. A maximum
of 256 classes are supported per policy on the wired port for the wired target.
-
The device supports 15 unique combinations of policer exceed markdown and policer violate markdown tables. A policymap must
use the same combination, which means different classes in the same policymap must use the same table map for exceed markdown.
The same is applicable for violate markdown.
-
Overlapping and marking actions are not supported in H-QoS policy.
-
Policer value can only be configured in either the parent or the child, not both.
-
Queuing actions are supported only on DSCP, CoS, QoS-group, IP precedence, and EXP based classification.
-
Application Visibility and Control (AVC) and Network Based Application Recognition (NBAR) based QoS are not supported.
-
Classification is not supported for the following:
-
Virtual Private LAN Services (VPLS)
-
Layer 2 and MAC
-
Packet length for fixed and range
-
Real-Time Transport Protocol (RTP) for header and type
-
Access control entries (ACEs)
-
Conditional markdown using multiple table-maps in the same policy-map is not supported.
-
GRE tunnel QoS for policing and marking is not supported.
-
Locator ID Separation Protocol (LISP) QoS is not supported.
-
QoS ACL ternary content addressable memory (TCAM) for egress is not supported.
-
QoS metadata for App-ID entries are not supported.
-
Security group tag (SGT) aware QoS is not supported.
-
StackWise Virtual Link (SVL) QOS is not supported.
-
Policing in egress direction is not supported.
-
Policing and queueing are not supported on SVI and tunnel interfaces.
-
Object group-based ACLs with QoS ACL based classification are not supported.
-
Remark with ACL based classification is not supported in egress direction.
-
For Broadcast, Unknown unicast and Multicast (BUM) traffic, QoS Queue statistics visibility is not supported in show policy-map type queue interface command.
-
Only 2 output queuing statistics can be viewed for multicast traffic.
-
Only 8 queuing per port are supported for queuing of traffic.
-
Queuing policy-map can be classified only using traffic-class, and the set option in queuing policy-map is not supported.
-
Classification using IPv6 based ACE using tcp flag in it is not supported
-
Egress remarking or set option is supported based on DSCP, CoS, precedence, or MPLS EXP. A new policy-map must be defined
and applied on the interface in egress direction. In case of MPLS, the egress remarking policy on label imposition node works
only if there is an EXP based marking policy on the ingress interface.
-
The table map should be of the same QoS type tag. For example, table map from DSCP to CoS and CoS to precedence are not supported.
-
Aggregate policing for egress is not supported.
-
Policing is not supported for outgoing packets.
-
Control-plane policy packet counter statistics update is not supported.
-
For hierarchical QoS (HQoS) police applied in the ingress direction, child-level policing is not supported. Policing of traffic
is based on the police rate value defined in parent-level policing.
-
Egress police with QoS group classification along with DSCP/PREC/COS/EXP based classification are not supported.
The following are the restrictions and considerations for applying QoS features on EtherChannel and channel member interfaces: