Basic Configurations - Alcatel-Lucent 7450 Quality Of Service Manual

Basic Configurations

Basic Configurations
Configure an egress and ingress MLPPP profile.
834
Table 68, or Table 69
parameter value the edited profiles have at that point in time.
• A maximum of 128 ingress QoS profiles and 128 egress QoS profiles can be created
on the system.
• The values of the ingress per-class re-assembly timer are configured in the ingress
QoS profile.
• The mapping of the system forwarding classes to the MLPPP Classes are configured
in the egress QoS profile. There is a many-to-one relationship between the system FC
and an MLPPP class. See
4-class egress QoS profiles is selected.
• The maximum size for each MLPPP class queue in units of msec at the available
bundle rate is configured in the egress QoS profile. This is referred to as max in
Figure 51 and as max-queue-size in CLI. The out-of-profile threshold for an MLPPP
class queue, referred to as oop in
50% of the maximum queue size rounded up to the nearest higher integer value.
• The MLPPP class queue scheduling parameters is configured in the egress QoS
profile. The minimum information rate, referred to as MIR in
CLI, applies to Class 1 queue only. The MIR parameter value is entered as a
percentage of the available bundle rate. The WRR weight, referred to as W1, W2, and
W3 in Figure 52 and weight in CLI, applies to class 1, class 2, and class 3 queues.
W1 in Figure 52 is not configurable and is internally set to a value of 1 such that Class
1 queue shares 1% of the available bundle rate when the sum of W1, W2, and W3
equals 100. W2 and W3 weights are integer values and are user configurable such
that Class 2 queue shares and Class 3 queue shares of the available bundle rate.
• The user applies the ingress and egress QoS profiles to a 4-class MLPPP bundle for
the configured QoS parameter values to take effect on the bundle.
• The following operations require the bundles associated with a QoS profile to be
shutdown to take effect.
→ A change of the numbered ingress or egress QoS profile associated with a
bundle.
→ A change of the bundle associated ingress or egress QoS profile from default
profile to a numbered profile and vice-versa.
• The following operations can be performed without shutting down the associated
bundles:
→ Changes to any parameters in the ingress and egress QoS profiles.
for the egress QoS Profile #1. This is regardless of the
Table 67 for the mapping when one of the three predefined
Figure 51, is not directly configurable and is set to
Figure 52 and mir in
Quality of Service Guide