Restrictions for Port-Shaper and LLQ in the Presence of EFPs
-
Due to NCS 520 hardware limitations, functionality of Egress QoS policy that is applied on the EFP shall not work as expected, if all the conditions mentioned below occur together:
-
Unknown unicast, multicast, and broadcast stream is received for the same EFP in the ingress direction.
-
Unknown unicast or multicast or broadcast traffic and other traffic that is targeted for same EFP, are classified under same class-map of the policy that is configured on the EFP.
-
Combined transmitted traffic rate (#1 and other traffic that is targeted for same EFP) for the EFP is higher than the configured shaper value.
-
-
For port-shaper in the presence of EFPs, policy on the port must be applied first followed by policy on EFP. Applying policy on EFP first followed by the port does not work.
-
If you configure a class-based policy on the port, then you cannot configure service-policies on Ethernet Flow Points (EFPs).
-
Attaching a service policy to the BDI is not supported.
-
Usage of bandwidth remaining percentage (BRP) in the absence of priority class, allocates the available bandwidth in an iterative way. For example, the bandwidth is allocated for the first BRP class as per the percentage of share that is configured in the respective class-map and the remaining bandwidth is iteratively allocated to all other BRP classes until the bandwidth is exhausted.
-
When the port is down, if you manually change the port speed then it may result in unexpected behavior.
-
You must remove bandwidth statement from the child policy before it is removed from the parent policy.