A 4-class MLPPP bundle can be configured. This feature cannot be used with MC-MLPPP bundles with fewer than 4 classes.
The following describes the parameters and the configuration processes and rules:
The user creates an ingress QoS profile, mlppp-profile-ingress, to configure the wanted value of the ingress per-class reassembly timer. Ingress QoS profile #1 is reserved to the predefined profile with parameter values in Table: MLPPP ingress QoS profile: reassembly timers (ms). The user is allowed to edit this profile and change parameter values. However, the default value of a parameter when a user creates a profile with a profile-id higher than 1, or performs the no option on the parameter, is always the one in Table: MLPPP ingress QoS profile: reassembly timers (ms) for the ingress QoS Profile #1, regardless what parameter value the edited Profile #1 has at that time.
The user creates an egress QoS profile, mlppp-profile-egress, to configure the wanted values for the per-class queue and queue scheduling parameters. The user is also able to configure the mapping of the system forwarding classes to the MLPPP classes. Egress QoS profiles #1, 2, and 3, are reserved to the predefined profiles with parameter values shown in Table: Packet forwarding class to MLPPP class mapping , Table: MLPPP class queue threshold parameters, or Table: MLPPP class queue scheduling parameters . The user is allowed to edit these profiles and change parameter values. However, the default value of a parameter when a user creates a profile with a profile-id higher than 3, or when the user performs the no option on the parameter, is the one shown in Table: Packet forwarding class to MLPPP class mapping , Table: MLPPP class queue threshold parameters, or Table: MLPPP class queue scheduling parameters for the egress QoS Profile #1. This is regardless of the parameter value the edited profiles have at that 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 reassembly 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 Table: Packet forwarding class to MLPPP class mapping for the mapping when one of the three predefined 4-class egress QoS profiles is selected.
The maximum size for each MLPPP class queue in units of ms at the available bundle rate is configured in the egress QoS profile. This is referred to as max in Figure: MLPPP class queue thresholds for in-profile and out-of-profile packets and as max-queue-size in CLI. The out-of-profile threshold for an MLPPP class queue, referred to as oop in Figure: MLPPP class queue thresholds for in-profile and out-of-profile packets, is not directly configurable and is set to 50% of the maximum queue size rounded up to the nearest higher integer value.
The MLPPP class queue scheduling parameters are configured in the egress QoS profile. The minimum information rate, referred to as MIR in Figure: MLPPP class queue scheduling scheme and 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: MLPPP class queue scheduling scheme and weight in CLI, applies to class 1, class 2, and class 3 queues. W1 in Figure: MLPPP class queue scheduling scheme 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 as percentage 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 the other way around
Changes to any parameters in the ingress and egress QoS profiles can be performed without shutting down the associated bundles.